Database Users

Sos! Help: Broken download mode

Hi guys, so I flshed a wrong kdz file on my D801 wind canadian variant, no my phone stuck on LG logo boot screen with green led, i have no fastboot mode, no twrp recovery, I can just access default recovery to hard reset, when i try to enter download mode by pressing volume+ while pluging the phone to pc, it goes just to frst screen, i mean the download mode logo with blue dots!!!!
Please any help would be appreciated, I'm ready to pay for fixing it as i live in a country where my phone won't be fixed otherwise. please please.

Helppppppppppppppppppp Please please just answer me

Up up up up up up up up up up

devdassi said:
Up up up up up up up up up up
Click to expand...
Click to collapse
bud same thing happened to me. and unfortunatly there is no fix for this. everytime i turned my phone on i got the little android guy then it would stay on lg screen with blue and green LED. try download mode it goesto the first screen of little blue dots.
since warrenty should not be able to tell anything about root or etc. i sent it in. in the mean time i called my carrier company and they sent me out a new phone for 35$. but i have to send old one back wether it ges fixed or not.
sorry bud but there is no way back from that. even tho your computer gives it a port its not fully booting so you cant flash anything..... here is one last thing you can try................ this could be your only hope.......it didnt help me but it might work for you...
good luck
http://forum.xda-developers.com/showthread.php?t=2582142

jester12345 said:
bud same thing happened to me. and unfortunatly there is no fix for this. everytime i turned my phone on i got the little android guy then it would stay on lg screen with blue and green LED. try download mode it goesto the first screen of little blue dots.
since warrenty should not be able to tell anything about root or etc. i sent it in. in the mean time i called my carrier company and they sent me out a new phone for 35$. but i have to send old one back wether it ges fixed or not.
sorry bud but there is no way back from that. even tho your computer gives it a port its not fully booting so you cant flash anything..... here is one last thing you can try................ this could be your only hope.......it didnt help me but it might work for you...
good luck
http://forum.xda-developers.com/showthread.php?t=2582142
Click to expand...
Click to collapse
thank you so much sir for replying, what is really wierd is that when i connect it to my pc, kingo root detects it, and gives me the option to root, then the rootin process stops at fetching scripts.

I cannot read.

Gnarfsan said:
If you can do that, you should be able to fix it via that Ubuntu guide to restore the partitions I think...?
Link: http://forum.xda-developers.com/showthread.php?t=2582142
Sent from my LG-D802 using xda app-developers app
Click to expand...
Click to collapse
I was able to connect to pc like he was. And kingo saw it but about 2 mins everything failed. No matter what port name i gave is. Any flash tool as well. And ubuntu did not work for me. Altho i did suggest that ubuntu method just incase it does work for you. Exhaust all options before giving it up for repair or warrenty exchange good luck and i hope you are more secessful then i was. Altho rogers did send me out a new phone good luck

thank you guys , my phone when on lg logo, and connected to pc, i can see it in device manager under modem as LGE android net usb modem,
and under ports as LGE android serial port com 8, any chance or sign of live to my phone, as mentionned before, there is no waranty services in our country.

@ jester12345 Did ubuntu read your phone when you tried the method of flashing partitions?

devdassi said:
@ jester12345 Did ubuntu read your phone when you tried the method of flashing partitions?
Click to expand...
Click to collapse
No ubuntu did not see my phone. Only my pc did even tho my phone wouldnt finish booting.

Could there be a paid fix? I'm ready to pay to bring my phone to life again.

LG Flash Tool crashed while flashing, phone bricked

Hi,
I was about flashing stock rom (following this thread and using CSE Flashing mode), when suddenly LG Flash Tool crashed on windows (I hate windows). Flashing progress stuck at 16%, so I press and hold power button to power phone off. but when I tried to enter to Download Mode, phone start too boot, and after LG logo, screen keeps going on and off (showing black screen)
I tried to enter to recover or factory hard reset, but it going to Factory data reset, even if I confirm reseting data it would try to boot same as when I tried to get Download Mode.
adb does not work
I followed this thread, but /dev/sdb1..36 just available for a few second and then disappear, after a while they are available and then disappear, and this will going on, (I think this is related to that screen on and off thing)
Would someone help me?
Sorry for my bad english, I'm a little nervous right now

Ok, finally I could see sdb1...36 and do what have been said here, and now I stuck at LG logo at boot.
still cannot get the download mode
factory hard reset is back but it'll stuck at "Factory reset processing..."

I have really lost my respect to flashtool after this kind of errors. If someone solve that issue it would be great for our community

please help

IM SORRY
we have the same scenario before, identically as yours.. and im sorry to tell you that you bricked your G2 so bad. i need to take mine to service center and they said that it needs the board to be replace, luckily im still on warranty. hope you still have yours as well

berceniqgil said:
we have the same scenario before, identically as yours.. and im sorry to tell you that you bricked your G2 so bad. i need to take mine to service center and they said that it needs the board to be replace, luckily im still on warranty. hope you still have yours as well
Click to expand...
Click to collapse
Yes I'm still have warranty.
But I hope I can fix it myself

Mine just got this issue too. Repair center denied the phone for repairs, claiming it is user damage.
So yup, I have a neat paperweight now.

berceniqgil said:
we have the same scenario before, identically as yours.. and im sorry to tell you that you bricked your G2 so bad. i need to take mine to service center and they said that it needs the board to be replace, luckily im still on warranty. hope you still have yours as well
Click to expand...
Click to collapse
Zulake said:
Mine just got this issue too. Repair center denied the phone for repairs, claiming it is user damage.
So yup, I have a neat paperweight now.
Click to expand...
Click to collapse
Somewhere in the forum i saw that you can detect your phone as a adb device on ubuntu or etc. Have you tried that? Im really feeling sorry about hearing that issue. As advice use old flashtool method that is harder but safer

abdulkadiro said:
Somewhere in the forum i saw that you can detect your phone as a adb device on ubuntu or etc. Have you tried that? Im really feeling sorry about hearing that issue. As advice use old flashtool method that is harder but safer
Click to expand...
Click to collapse
Ubuntu is running in a VM, so I would need Windows to find the phone first.
Unfortunately, Windows never sees the phone.
It's weird though. TWRP got successfully flashed during the QHSUSB_BULK guide method, but I cannot boot into it.

Zulake said:
Ubuntu is running in a VM, so I would need Windows to find the phone first.
Unfortunately, Windows never sees the phone.
It's weird though. TWRP got successfully flashed during the QHSUSB_BULK guide method, but I cannot boot into it.
Click to expand...
Click to collapse
Maybe you had a bad download try an another base

abdulkadiro said:
Maybe you had a bad download try an another base
Click to expand...
Click to collapse
I lost QHSUSB_BULK mode now, the PC won't see the phone anymore and all modes are gone.
No download mode, no recovery, no ADB, no fastboot, factory reset freezes, nothing works.

Zulake said:
I lost QHSUSB_BULK mode now, the PC won't see the phone anymore and all modes are gone.
No download mode, no recovery, no ADB, no fastboot, factory reset freezes, nothing works.
Click to expand...
Click to collapse
If you see the lg logo maybe you will have a change. A guy who had the same results like you brings his phone plugged for 10-15 minutes than he have find his phone in download mode. Of course he plug the cable while holding the down button. I hope you will get your phone back with its functions

abdulkadiro said:
If you see the lg logo maybe you will have a change. A guy who had the same results like you brings his phone plugged for 10-15 minutes than he have find his phone in download mode. Of course he plug the cable while holding the down button. I hope you will get your phone back with its functions
Click to expand...
Click to collapse
Well, that's worth the try.
I just connected it while holding volume up.
Hopefully it will still charge when connected.
//Well, it's been about 15 minutes now and it still displays the LG logo.
Guess I'm outta luck on this one.

Zulake said:
Somewhere in the forum i saw that you can detect your phone as a adb device on ubuntu or etc. Have you tried that? Im really feeling sorry about hearing that issue. As advice use old flashtool method that is harder but safer
Click to expand...
Click to collapse
I tried that on my ubuntu laptop, ubuntu did not detect the phone
Zulake said:
Well, that's worth the try.
I just connected it while holding volume up.
Hopefully it will still charge when connected.
//Well, it's been about 15 minutes now and it still displays the LG logo.
Guess I'm outta luck on this one.
Click to expand...
Click to collapse
I read this post one more time, this guy who had download mode after 10-15 minute, have discharged the phone then do what he said. have you try that?
I have discharged my phone, but I'm going to work right now, later today I will try and let you know if it was fixed or not

Behzadsh said:
I tried that on my ubuntu laptop, ubuntu did not detect the phone
I read this post one more time, this guy who had download mode after 10-15 minute, have discharged the phone then do what he said. have you try that?
I have discharged my phone, but I'm going to work right now, later today I will try and let you know if it was fixed or not
Click to expand...
Click to collapse
I won't dare doing that, as it doesn't seem to charge anymore.
I'm gonna retry sending it in today, otherwise it's going into the bin.

I tried one more time last night when phone was fully discharged. nothing has been changed.
Zulake said:
I won't dare doing that, as it doesn't seem to charge anymore.
I'm gonna retry sending it in today, otherwise it's going into the bin.
Click to expand...
Click to collapse
Hopefully it start charging.

Qualcomm hs-usb qdloader 9008 nexus 6P (HELP!)

Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?

attempted to apply for heat some to the device then re flash ?

blackcell1 said:
attempted to apply for heat to the device then re flash ?
Click to expand...
Click to collapse
Sorry, I don't quite understand what you mean?

Clarkeofcurtis said:
Sorry, I don't quite understand what you mean?
Click to expand...
Click to collapse
Use a hairdryer to warm up the back of the phone.

Are you pulling my leg? Warm it up then reflash?

nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method

blackcell1 said:
nah im not trying to make you destroy your phone, being rather serious with this method. i use it on a daily basis to solve phones that fail during restoring factory images. i wouldn't know how long to give it with a hair dryer as i have access to a heat gun/heat mats .
just think of it as a cheap mans re balling method
Click to expand...
Click to collapse
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice

Clarkeofcurtis said:
Sorry haha, I'm a noob with most of this android stuff bar rooting and flashing a few devices prior! I shall give it a go now and get back to you - thank you for the advice
Click to expand...
Click to collapse
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.

blackcell1 said:
good luck, id give it a good couple of minutes on the highest setting, just so its a little hot to the touch. and attempt the flashing of the files when its still hot/warm.
Click to expand...
Click to collapse
thank you so much that worked, it has said flash successful, first time I got a google logo but now nothing, what would be my next step please?

if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
---------- Post added at 04:50 PM ---------- Previous post was at 04:49 PM ----------
but from my personal experience with having to heat a phone up to restore factory images, it kinda means the phone is nearing the end of its life and id start thinking about buying your next phone before it sh*ts the bed.

blackcell1 said:
if the bootloader is unlocked then you can directly flash the firmware. but if its not google "nexus ota" and then on your phone jump into the recovery and check the firmware model number and download the same ota and adb sideload it.
im not 100% sure on the next step as I've never had a nexus 6p with a dead bootloader. but thats what id do.
Click to expand...
Click to collapse
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc

Clarkeofcurtis said:
Thank you for the reply and continuing to help, after seeing the google logo just once I'm getting nothing again - I'm even more determined now though as It's been dead for 2 months so this is the furthest I've gotten - the application of heat is what did it for me and fixed the error I was getting, can't get into recovery now though holding power + down etc
Click to expand...
Click to collapse
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.

blackcell1 said:
yeah can you access the bootloader at all ? does it say that the bootloader is locked ? from trying to restore LG's it sometimes has to be re heated a few times, but yeah if you need to re heat it to get further into the phone then its pretty much a lost cause. the only reason i do it is to remove the data so we can resell the device.
Click to expand...
Click to collapse
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?

Clarkeofcurtis said:
I can get into the andriod screen where you can select recovery and such, with the BL, Baseband product variation and such, where should I go from here?
Oh right, so even once restored to firmware, will it be useless do you think if I can even manage to?
Click to expand...
Click to collapse
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply

blackcell1 said:
Sorry if you can't access the recovery from the bootloader and its in locked state then your a member of the lovely group of BLOD (bootloader of death) if you hit recovery does it show a little android logo and sit there?
Sorry for the late reply
Click to expand...
Click to collapse
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay

Clarkeofcurtis said:
I believe so, I can just about get into the bootloader at the best of times and when I do I can select options but once proceeding to start said mode phone freezes so can't get into recovery mode :/
Thank you for your continuous help, only way i can get it into bootloader is by heating it up so does that mean for the device to ever work It'll need heat every time? looking like a spares and repairs listing on ebay
Click to expand...
Click to collapse
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:

Is it possible to send me the guide you used? Thanks.
Clarkeofcurtis said:
Hi there, I've been browsing through the threads related to unbricking of the Nexus 6P stuck in qualcomm hs-usb qdloader 9008 mode, really desperate to get my device working again if even possible however I've tried for about four days now different ways and files and I've had no luck.
My bootloader is locked and no ADB etc managed to get my device showing as the 9008 port so I think it's stuck in EDL.
Following guides, this is the furthest I've yet to get (In screenshot)
Could anyone shed some light and some assistance please? what am I doing wrong!?
Click to expand...
Click to collapse

Hey there sorry for slow replies, will be back on my desktop in an hour I'll send you links for what I followed and such, I think the only reason my device was in EDL mode was due to a hardware fault? As my device is faulty indefinitely as I had to use a hairdryer to warm it up while flashing this then allowed it to enter firehose state which a lot of people seem to error with - after all my attempts and research I'm to velieve there's a fault with the phone itself the only way I could get it to even power up was applying heat to it after removing the back panel
As blackcell said deballing or something? Worked a treat!
Furthest I've managed to get now is into my boot loader however everything is locked - when I press enter recovery my handset just freezes ?

5.1 said:
Hello....
How did you manage to get in to EDL mode..? I'm really curious. With stock bootloader? Since you can't access recovery
Also what is exactly displayed in Windows device manager?
You are using an outdated QFil version... It is from 2014 àr 2015.
Do a google search with: QPST_2.7.453.0 . This version seem to be from 2016.
Use the first link from the result. I analysed the files with virustotal, those seem clean or malware...
Also when plugging your usb cord to your PC, does your phone vibrate? Or does the LED blink in red?
You may have to press power button when plugging the usb cord or press power button for a certain amount of time before you plug the usb cord. I'm not completly sure, but your phone may not be in the "proper" EDL state to accept the QFil flash.
Good luck... :good:
Click to expand...
Click to collapse
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader

Clarkeofcurtis said:
Thanks pal if you check last post I wrote about my EDL mode forgot to tag you my apologies, as for my LED I've never seen that light up since I bricked it, even when google logo came up etc and while in the boot loader
Click to expand...
Click to collapse
Light usually a red LED blink while in proper EDL state as far as I know. Could be something else on the N6P. Well, it looks like you are SOL. Sorry, I don't know what else to say, since you exhausted all possibilities...
Good luck...

I have totally bricked my zte axon 7 a2017g and i seriously need help!!

So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx

Daan_K said:
So guys, i have tried to downgrade my phone from android 7.1.1 to 6.0 which ended in a softbrick, after that i tried 2 flash a stock rom but that completely bricked it and now my phone wont dont anything anymore except for some kind of mode that my computer can detect in device it sees the qualcomm port 9008 device but there a thing it just wont work miflash doesnt recognize it and i cant find any sollutions online please help
tnhx
Click to expand...
Click to collapse
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...

Choose an username... said:
I wonder:
-Which is your phone model, as stated on the back of the phone?
-Which is the file that you used to downgrade?
-Which stock rom did you try to flash?
The fix is pretty simple but seeing how you borked three simple procedures I'd like to know everything and lay it out for you precisely. You have to have done something horribly wrong to softbrick a phone with the stock updater system...
Click to expand...
Click to collapse
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.

Daan_K said:
Okay at first my phone model on the back of my device is, as i mentioned before, "zte a2017g" thats the european version of this phone, chinese is "a2017" and the us version is "2017u".
The file i used 2 downgrade was the stock rom from the official website of zte
it was the full edl file buildnumber b10.
and again i once sofbricked it, i know how 2 fix that, but now it hard bricked, well i think so at least, i cant get it to boot into bootloader, recovery or anything, when i hold the power button it shakes the device, and it shows the zte logo for about 2 seconds then it disappears, and nothing happens but my computer does recognize it as a connected device but i cant use miflash of something else because those programs dont see it.
Click to expand...
Click to collapse
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears

Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much

Daan_K said:
allright allready thanks loads for your support but could you maybe send the right file to flash because i have no idea, and please, the files for a2017g not a2017 or a2017u thankyou so much
Click to expand...
Click to collapse
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09

Choose an username... said:
they are in the guide. at the top, there's a link to WesTD's EDL flashable files. Get one for A2017G, for example B09
Click to expand...
Click to collapse
Allright, thankyou so much my dude

Choose an username... said:
all right. it's still freaking weird. Use my DFU unbrick guide but only do step 4 and 5 (but use the files on the top anyways)(you just have to hold Vol+ and Vol - and insert the cable instead of taking the phone apart and shorting pins). After that check the driver, if it is still Qualcomm HS-USB QDLoader 9008 then flash with MiFlash, if not, tell me what appears
Click to expand...
Click to collapse
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back

Daan_K said:
aight, as i thought this didnt work, i tired it but miflash basicly just gave me an error notification.
also when i go into device manager i can see that my device is connected but i show the name with a yellow triangle with a ! in it i have no clue what this means can u please help me with this. i rlly want my phone back
Click to expand...
Click to collapse
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"

Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.

RedWave31 said:
Don't bother? That guy is using XDA as a free emergency support without looking for one second.
He probably would like you to do a teamviewer while he's watching football with a beer and not even say thank you.
I'm horrified.
Click to expand...
Click to collapse
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that

Daan_K said:
rlly m8. im just a guy who needs help with his phone the guy "choose a username..." i helping me with it, ive been unable 2 fix my phone with any of the other threads i just need some help and i have said thanks alot, dont call me that
Click to expand...
Click to collapse
Sorry, I don't believe you for one second. Like litterally THOUSANDS of people here and here opening "bricked plz hlp" threads, you didn't even have the BASIC, LOWEST courtesy of writing more than 10 words of gibberish whining about your situation, without a single usefull element of context.
Proof of that in the NUMEROUS questions asked about ELEMENTARY elements about your situation. You're litterally the kind of person that would go to a car mechanic, drop the keys on the counter saying "my car is broken, fix it" and just leave without a single word added. That's RUDE and, yeah, I'm tired AF of people like you who can't READ THE DAMN XDA RULES and got NOT education whatsoever.
Nd writng frm a phone in T9 mde dsnt rlly bring nythng mre on the tble either.
Too bad you found somebody to help, as it's only encouraging that kind of behaviour.
//Rant off//

@Daan_K this EDL Tool can help https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759

Choose an username... said:
First of all, if you get an error TELL ME what it says!
Send me a screenshot of the device manager, i can do very little with "yellow triangle"
Click to expand...
Click to collapse
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool

Daan_K said:
this is a screenshot of my device manager, and what I meant with yellow triangle, also it doesn't work with the edl-tool nor the axon7tool
Click to expand...
Click to collapse
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)

https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly

IvI97 said:
https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898
if you can only get to dfu mode and nothing else, use thise guide, you'll have to dismantle your phone. Had to unbrick mine with this from a hardbrick, worked flawlessly
Click to expand...
Click to collapse
Hey, a couple of things: one, i've updated the guide, it's around, much simpler to use. just saying. Two, this guy has the right driver. Don't confuse him with DFU while at least for now it is not.

Choose an username... said:
Okay, let's try two things:
First right click on it and uninstall the device, also delete driver software for the device (it will be a checkbix asking for that after you hit 'uninstall device'). After that, hold Volume up, Volume down, and Power until the Device manager refreshes. After that the driver should reinstall itself. If it still shows with the yellow triangle, right click it, click on Properties, and send me a screenshot (or translate me what it says on the status part)
Click to expand...
Click to collapse
omg the triangle is gone, thankyousomuch, but what can I use now 2 fix it further?? is that in your guide maybe?

choose an username... said:
hey, a couple of things: One, i've updated the guide, it's around, much simpler to use. Just saying. Two, this guy has the right driver. Don't confuse him with dfu while at least for now it is not.
Click to expand...
Click to collapse
omygod it ****ing working, choose an username man, i can't thank you enough, seriously ur the best man lots of love for doing this

9.0.5 Bricked itself?

Hey guys, I have the T-Mobile 6T, unlocked and rooted, worked perfect until today.
Today it took the 9.0.5 OTA, it downloaded, installed, rebooted and left me with
"<!> BUILD VERSION and HW VERSION IS NOT MATCH"
Any chance someone can help?
I can't get it into recovery or anything.

The MSM download tool will help you.
https://forum.xda-developers.com/on...t-mobile-oneplus-6t-msmdownloadtool-t3868916/

I had hoped that it would. Unfortunately, I can't get it to work..
it seems that the phone just keeps rebooting before the tool can actually do anything.
The most I get is "Start download firehose binary" and the the phone disconnects.
Next is "Sahara Communication Failed."

after a few dozen more tries, I got a bit more. Now it says "Images do not match the phone!"

Try restarting into qcom mode as well as plugging into diff USB ports. Mine was doing that as well and eventually was able to get it to work.

How do I get into qcom mode?

intrusdave said:
How do I get into qcom mode?
Click to expand...
Click to collapse
Hold Power, Vol up, and Vol down. Screen will be completely black but phone will be recognized in device manager and will give you a COM port.
Also make sure you're using the Tmobile MSM Download Tool and not the one for international version. See link above that I posted.

Looks like it was the usb cable.
but I'm still stuck at "Images do not match with the phone!"
This is the T-Mobile variant, flashed with the global rom.

intrusdave said:
Looks like it was the usb cable.
but I'm still stuck at "Images do not match with the phone!"
This is the T-Mobile variant, flashed with the global rom.
Click to expand...
Click to collapse
Are you using the T-mobile tool? https://forum.xda-developers.com/oneplus-6t/how-to/tool-t-mobile-oneplus-6t-msmdownloadtool-t3868916

I thought I was, but I will re-download and see.

That was it, thank you! I don't know where the hell I got the wrong copy from!
You really bailed me out, thank you very much.

intrusdave said:
That was it, thank you! I don't know where the hell I got the wrong copy from!
You really bailed me out, thank you very much.
Click to expand...
Click to collapse
No problem. There's two tools in the guides section and the threads have similar names so it's easy to get mixed up.
In the future if you're going to international 9.0.5 or 9.0.6 make sure to use the full rom and not just OTA.

I have the Same problem
intrusdave said:
Looks like it was the usb cable.
but I'm still stuck at "Images do not match with the phone!"
This is the T-Mobile variant, flashed with the global rom.
Click to expand...
Click to collapse
Hi, i have the same problem. what do you do to get it work?

Hi, I lost all my photos by doing this . is there any way i can get all my data back ?Phone is up and running but lost my all data

[email protected] said:
Hi, I lost all my photos by doing this . is there any way i can get all my data back ?Phone is up and running but lost my all data
Click to expand...
Click to collapse
Oh boy, look what I found right in the thread about the MSM tool! Please see attached screenshot.

I have this issue on the international variant of the phone (Yes mine truly is the international model, it has dual sim, although its refurbished so the refurbishers borked something)

mang0 said:
Hold Power, Vol up, and Vol down. Screen will be completely black but phone will be recognized in device manager and will give you a COM port.
Also make sure you're using the Tmobile MSM Download Tool and not the one for international version. See link above that I posted.
Click to expand...
Click to collapse
I used the international version on mine (T-Mobile 6T) since was in software and hardware error. You don't have to come back to TMobile software mandatory.

mang0 said:
Hold Power, Vol up, and Vol down. Screen will be completely black but phone will be recognized in device manager and will give you a COM port.
Also make sure you're using the Tmobile MSM Download Tool and not the one for international version. See link above that I posted.
Click to expand...
Click to collapse
I've tried the different tools to no avail. also holding power, vol up and down will only go into fastboot mode. I believe just holding vol up and down is the qcom mode and inserting the usb c cable after about 10 seconds of holding those two buttons. otherwise the device will just keep rebooting into fastboot