Database Users

[UPDATED][10/23/2014] Bricked to the Bone D801 (T-Mobile LG G2)

LG D801 (T-Mobile) Bricked[/U][/B]
The device has been bricked and is in this condition:
Download mode shows as dots and is not recognized by Windows (only occasionally as "Unknown Device")
No custom recovery (it has been wiped in fastboot)
No ROM (system was wiped)
It makes a nice paperweight
Click to expand...
Click to collapse
This device does not allow fastboot, unless there is a software issue (which I cannot purposely cause without ADB in a custom recovery).
I have tried every set of drivers on Windows 7 Ultimate (64 bit) and am unable to change the COM port to 41 because the device isn't recognized at all (it was being recognized last night, but the version of Windows I have didn't have ANY options to change the COM serial port).
No, a rooting method will not work (I'm a Recognized Developer, so trust me).
I have Linux and Windows 7 dual-booting.
I have used everything [URL="http://storagecow.eu/index.php?dir=Xda%2FLG+G2%2FStock%2F"]HERE
Click to expand...
Click to collapse
.
I have also tried THIS driver method (when the device was actually visible on Windows, but the driver never successfully installed).
I manually repartitioned the device using this method on Ubuntu, but accidentally used the stock recovery image.
I am trying to use this method, for Windows, with no luck (because of the phone not being recognized on Windows).
I have tried a friend's desktop with no luck. I have used different USB ports and cables, as well.
Any help at all would be greatly appreciated. Especially if I could somehow trigger fastboot.
Click to expand...
Click to collapse
Thanks in advance,
Mike Criggs

So you flashed LG's stock recovery, can you actually boot into that?

savoca said:
So you flashed LG's stock recovery, can you actually boot into that?
Click to expand...
Click to collapse
It just sticks at the "Processing factory reset..." message.
I need a miracle here, haha.

Your download mode works if there are no blue circles when you start it.
Try installing ubuntu, knoppix etc under vmware and see if it gives you any errors.
also under windows watch the devices under device manager.

bender_007 said:
Your download mode works if there are no blue circles when you start it.
Try installing ubuntu, knoppix etc under vmware and see if it gives you any errors.
also under windows watch the devices under device manager.
Click to expand...
Click to collapse
Oh if his download mode is just hanging at the loading screen but never gets to the loading circle it's most definitely a goner, considering his recovery hangs that probably confirms he dd'ed the wrong bootstack.
@MikeCriggs Check if you have fastboot mode when you try loading recovery or download mode (as the bootloader's fallback) - if not you need to RMA. No big deal I've killed 2 so far via bootloadery mischief.

Is there a JTAG like device out there that can fix this phone's hard bricks?

tiguy99 said:
Is there a JTAG like device out there that can fix this phone's hard bricks?
Click to expand...
Click to collapse
JTAG is disabled for G2.

savoca said:
JTAG is disabled for G2.
Click to expand...
Click to collapse
Has the op tried this method?

MikeCriggs said:
LG D801 (T-Mobile) Bricked
Thanks in advance,
Mike Criggs[/SIZE]
Click to expand...
Click to collapse
Did you make sure that when you put your device in download mode that you changed the port to COM41 in device manager?

tiguy99 said:
Has the op tried this method?
Click to expand...
Click to collapse
Thank god I'm good with hardware! I'll give this a try tomorrow, thank you!!!

Updated!
Thank you all for your help so far!

Updated!
Thank you all for your help so far!

MikeCriggs said:
Thank god I'm good with hardware! I'll give this a try tomorrow, thank you!!!
Click to expand...
Click to collapse
No worries!
Keep us posted on how it goes.

Phone wiped clean with TWRP, not being recognized by ADB.

Good day to y'all!
So... I did a thing. I pressed a button in TWRP without knowing what I was doing, and accidentally wiped my whole phone. And I mean, like, the entire thing.
I'm pretty sure I even managed to wipe TWRP after this, as I can no longer find a way to boot into it.
I've tried several things to fix this, namely the following:
-Flashing stock firmware using power+vol up+vol down. (says the update package isn't valid, I have a VNS-L31 and have tried every version of L31 firmware I could find.)
-Downloading a firmware update using eRecovery. (says getting package info failed.)
-Using fastboot to install TWRP.
Now, on this last one is where I'm stuck. My phone isn't being recognized by ADB anymore (it was before).
I've tried reinstalling my fastboot drivers, and my phone's USB drivers with no luck whatsoever.
If I could manage to get ADB to recognize my phone, I'm pretty sure I'd be able to flash TWRP and then a different ROM with that.
As aforementioned, I have a VNS-L31, Europe, Dual SIM w/ 3GB of RAM.
Very much lost on what to do, any help will be much appreciated!

Nantonix said:
Good day to y'all!
So... I did a thing. I pressed a button in TWRP without knowing what I was doing, and accidentally wiped my whole phone. And I mean, like, the entire thing.
I'm pretty sure I even managed to wipe TWRP after this, as I can no longer find a way to boot into it.
I've tried several things to fix this, namely the following:
-Flashing stock firmware using power+vol up+vol down. (says the update package isn't valid, I have a VNS-L31 and have tried every version of L31 firmware I could find.)
-Downloading a firmware update using eRecovery. (says getting package info failed.)
-Using fastboot to install TWRP.
Now, on this last one is where I'm stuck. My phone isn't being recognized by ADB anymore (it was before).
I've tried reinstalling my fastboot drivers, and my phone's USB drivers with no luck whatsoever.
If I could manage to get ADB to recognize my phone, I'm pretty sure I'd be able to flash TWRP and then a different ROM with that.
As aforementioned, I have a VNS-L31, Europe, Dual SIM w/ 3GB of RAM.
Very much lost on what to do, any help will be much appreciated!
Click to expand...
Click to collapse
adb only works if the phone is booted to android, if you can boot onto fastboot you should be able to flash twrp and then flash oeminfo for your phone, and then use the dload/update.app to flash the stock rom

mjz2cool said:
adb only works if the phone is booted to android, if you can boot onto fastboot you should be able to flash twrp and then flash oeminfo for your phone, and then use the dload/update.app to flash the stock rom
Click to expand...
Click to collapse
That's what I was trying to do. Thing is, I can't connect it to my PC at all. I can boot into fastboot (by holding the vol down button and then connecting it), but my PC doesn't detect anything.

Nantonix said:
That's what I was trying to do. Thing is, I can't connect it to my PC at all. I can boot into fastboot (by holding the vol down button and then connecting it), but my PC doesn't detect anything.
Click to expand...
Click to collapse
(if you use windows) have you tried looking in device manager? is the device recognized?

mjz2cool said:
(if you use windows) have you tried looking in device manager? is the device recognized?
Click to expand...
Click to collapse
It isn't, no. I have the USB drivers installed.

Nantonix said:
It isn't, no. I have the USB drivers installed.
Click to expand...
Click to collapse
i had a similar issue a while back, mine showed up in device manager with an error, and i uninstalled the driver from there, then completely uninstalled hisuite, and then reinstalled hisuite, after that, it did get recognized and i could use fastboot flash again. (however, i did have to oem unlock eventhough the phone said it was unlocked)

mjz2cool said:
i had a similar issue a while back, mine showed up in device manager with an error, and i uninstalled the driver from there, then completely uninstalled hisuite, and then reinstalled hisuite, after that, it did get recognized and i could use fastboot flash again. (however, i did have to oem unlock eventhough the phone said it was unlocked)
Click to expand...
Click to collapse
I'll try doing so later today! I'll report back once I have, to let you know if it worked or not.

mjz2cool said:
i had a similar issue a while back, mine showed up in device manager with an error, and i uninstalled the driver from there, then completely uninstalled hisuite, and then reinstalled hisuite, after that, it did get recognized and i could use fastboot flash again. (however, i did have to oem unlock eventhough the phone said it was unlocked)
Click to expand...
Click to collapse
Alright, so. Minor progress has been made.
I uninstalled HiSuite, and my fastboot drivers successfully. I then reinstalled HiSuite, and when I connect my phone in fastboot/rescue mode, HiSuite starts.
I, however, haven't been able to reinstall my fastboot drivers. The device is under the "unspecified" section, is called "Fastboot2.0", and windows reports there aren't any drivers installed.
Any idea where I can find the proper fastboot drivers?

Nantonix said:
Alright, so. Minor progress has been made.
I uninstalled HiSuite, and my fastboot drivers successfully. I then reinstalled HiSuite, and when I connect my phone in fastboot/rescue mode, HiSuite starts.
I, however, haven't been able to reinstall my fastboot drivers. The device is under the "unspecified" section, is called "Fastboot2.0", and windows reports there aren't any drivers installed.
Any idea where I can find the proper fastboot drivers?
Click to expand...
Click to collapse
hisuite should install the proper drivers, try updating the driver in device manager (right click - update). i will take a look on my own pc when i get home

mjz2cool said:
hisuite should install the proper drivers, try updating the driver in device manager (right click - update). i will take a look on my own pc when i get home
Click to expand...
Click to collapse
Okay, so.
I installed the latest version of HiSuite, and my drivers have now been installed. (or so it seems.)
The device is still listed as "unspecified", but in the properties tab it says "Name: Android Sooner Single ADB Interface - Type: Android Phone".
However, ADB still does not detect my device, and HiSuite says it isn't connected.

Nantonix said:
Okay, so.
I installed the latest version of HiSuite, and my drivers have now been installed. (or so it seems.)
The device is still listed as "unspecified", but in the properties tab it says "Name: Android Sooner Single ADB Interface - Type: Android Phone".
However, ADB still does not detect my device, and HiSuite says it isn't connected.
Click to expand...
Click to collapse
did you use adb devices? or fastboot devices? it is correct that both adb and hisuite don't detect your device as it isn't booted into android

mjz2cool said:
did you use adb devices? or fastboot devices? it is correct that both adb and hisuite don't detect your device as it isn't booted into android
Click to expand...
Click to collapse
OH!
I got confused there, bahaha. I was using adb devices.
After typing fastboot devices, it now detects my phone.
I'll try flashing TWRP, I have a recovery.img left over on my desktop. Report back once I've done so!

mjz2cool said:
did you use adb devices? or fastboot devices? it is correct that both adb and hisuite don't detect your device as it isn't booted into android
Click to expand...
Click to collapse
SUCCESS! TWRP has been flashed onto my phone.
Apparently though, the battery's drained >_>
I'll leave it to charge for a few minutes as I throw stock firmware onto my microSD, and then try to install it, as I have a southeast asia VNS-L31 firmware package saved.

Nantonix said:
SUCCESS! TWRP has been flashed onto my phone.
Apparently though, the battery's drained >_>
I'll leave it to charge for a few minutes as I throw stock firmware onto my microSD, and then try to install it, as I have a southeast asia VNS-L31 firmware package saved.
Click to expand...
Click to collapse
if you flash oeminfo for c432, you can use the europe version of the update.app, and put that in dload, it should be around here somewhere on this forum

mjz2cool said:
if you flash oeminfo for c432, you can use the europe version of the update.app, and put that in dload, it should be around here somewhere on this forum
Click to expand...
Click to collapse
I've been searching for the Europe update.app, couldn't find it anywhere.
Any idea where I can find southeast asia OEMinfo? I wouldn't mind using it that way. The only disadvantage would be I can only use one SIM, which I do anyway.

mjz2cool said:
if you flash oeminfo for c432, you can use the europe version of the update.app, and put that in dload, it should be around here somewhere on this forum
Click to expand...
Click to collapse
I found the C432 OEMinfo, and the Europe-bound UPDATE.APP.
However, I have absolutely no ****ing clue how to flash the OEMinfo onto my phone. Could you guide me through the process?

Well, Never mind.
I managed to install Meticulus' TWRP, and CyanogenMod.
Everything is working as intended again! ^^

Nantonix said:
Well, Never mind.
I managed to install Meticulus' TWRP, and CyanogenMod.
Everything is working as intended again! ^^
Click to expand...
Click to collapse
if you decide to flash stock, you can flash the oeminfo file with twrp, and then put the update.app in dload on your sdcard.
btw, how is cyanogenmod working for you? i've tried it before, but the batterylife seems to be quite less than i'm used to with emui.
also, when you turn on the screen, does it still show static for a fraction of a second?

mjz2cool said:
if you decide to flash stock, you can flash the oeminfo file with twrp, and then put the update.app in dload on your sdcard.
btw, how is cyanogenmod working for you? i've tried it before, but the batterylife seems to be quite less than i'm used to with emui.
also, when you turn on the screen, does it still show static for a fraction of a second?
Click to expand...
Click to collapse
Everything's working fine for me! Battery seemed bad at first, but after having charged a few times the drain slows down drastically below 50%. It takes about 6 hours to get from 50 to 0 with full use. It probably just isn't displaying correctly.
Apart from that, everything works! Running it with a custom theme/navbar and everything. No problems whatsoever

Nantonix said:
Everything's working fine for me! Battery seemed bad at first, but after having charged a few times the drain slows down drastically below 50%. It takes about 6 hours to get from 50 to 0 with full use. It probably just isn't displaying correctly.
Apart from that, everything works! Running it with a custom theme/navbar and everything. No problems whatsoever
Click to expand...
Click to collapse
okay thanks! will try a few days more this time ^^

[Hard Brick] Nexus 6P 7.1.2 Beta 2 [Solved]

Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.

@rmorris003
You said the phone won't even power on. You mean no Google? Hold the power button down for a couple of minutes and see if it will reboot. If not put it on a charger, and after fully charging try the long press power button again. If you can get it to start, try to put it in fastboot mode. (ie. power+vol dn). If you can get to bootloader you can send fastboot commands and fix it. If you can get to this point, there are instructions here.

rmorris003 said:
Hey guys I just installed the full image of 7.1.2 beta 2 over top of beta 1 using Flashfire without the bootloader and modem selected and all went fine until I decided to use Flashfire to upgrade the bootloader and modem forgetting that we must use Fastboot as I am new to Flashfire and I was reading all through the beta thread before I did it and didn't understand we still must use Fastboot so anyways I am stuck in a hard brick now with the phone not powering on at all and can't do anything to restore it as my Windows 10 now detects the phone as unknown device (device descriptor request failed) is there anything I can do at this point as I just bought this phone used.
The error that I got in Flashfire was that the device storage is full when updating the bootloader as the modem went fine.
Click to expand...
Click to collapse
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...

5.1 said:
Hello... Well if your device is recognized as unknown, you could try to give this a shot:
https://forum.xda-developers.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838
Try to install Qualcomm driver first check the device manager. If you see your phone recognized as:
HS-USB QDLOADER 9008
You may be lucky!
Good luck...
Click to expand...
Click to collapse
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.

rmorris003 said:
I will try this when I get back from work, I just cant get my pc to see it as anything other than unknown device as it says this is the best driver for it.
Click to expand...
Click to collapse
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...

5.1 said:
I see... There's a txt file in the driver folder. Follow its instructions.
Good luck...
Click to expand...
Click to collapse
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.

rmorris003 said:
I am stumped, I have disabled driver enforcement and can't get any drivers to see my phone so I am not sure what to do.
Click to expand...
Click to collapse
You disabled driver signature and rebooted your computer? Then installed Qualcomm drivers from the thread I linked you to? I think you have to reboot your computer once more...
Good luck...

I held the power and vol down and now it shows up under com ports so this is a good sign.

Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.

rmorris003 said:
Ok got bootloader back and now put twrp on, I had to use qfil with nexus6p_fix_bricked but it got stuck at writing system.img but atleast the phone is on now.
Flashed the 7.1.2 beta 2 full image using the fastboot method included and all is back to normal.
Thanks so much for the help.
Click to expand...
Click to collapse
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...

5.1 said:
Wow glad it worked for you... You might push the thanks button in the OP of the thread where you found the debrick tools and thanks @tenfar since he offered the solution. He already saved a few N6P devices. I only linked you to his thread which you could have found yourself anyway...
Cheers...
Click to expand...
Click to collapse
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.

rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
You could report your experience in the other thread. Maybe it could help other users who faced the issue you had. :good:
Cheers...

rmorris003 said:
I'm pretty sure I was reading it before but I had to do some extensive reading on how to get the driver to read properly. I work night shift so I was kinda tired yesterday.
Click to expand...
Click to collapse
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!

Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT

Clarkeofcurtis said:
Hi there, I'm extremely new to Forums and the whole android scene please could you help?
I have the same issue with my Nexus 6P Hard bricked, only detected as a 9008 Port, no vibrations no power nothing!
I've tried to follow so many guides for the past three days however I've managed nothing. I've tried to do as you mentioned in the first posts, used the nexus6p_unbrick in Qfil but Sahara download fails.
Please Please Help, No Warranty just a Brick!
Click to expand...
Click to collapse
Falitheman said:
I have the same exact problem, everytime i try to flash with qfil it says it can't connect to my COMPORT
Click to expand...
Click to collapse
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...

5.1 said:
Hello,
Someone mentioned this in another post:
Hold volume up and plug the USB cord to.your computer and start qfil flash. Keep holding volume up until the flash ends...
Good luck...
Click to expand...
Click to collapse
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:

Falitheman said:
So i have some good news...it connects now. it says start sending programmer but then it says download failed: unable to download flash programmer using sahara protocol and then it fails. Any help?:crying:
Click to expand...
Click to collapse
Hey,
What version of qpst did you install?
Good luck...

5.1 said:
Hey,
What version of qpst did you install?
Good luck...
Click to expand...
Click to collapse
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back

Falitheman said:
I am using 2.7.441
Update: It seemed to be working for a second but then it says download failed: qsahara server fail: process fail. Any idea what that means? I really need my phone back
Click to expand...
Click to collapse
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...

5.1 said:
Hey,
Google qpst 2.7.453
It's easy to find. Scan the files on virustotal.com though.
Maybe the older versions are incompatible...
Good luck...
Click to expand...
Click to collapse
I tried with the version you suggested and i got the same error i just had. Can you send me your version so i can see if that works?

Hard Bricked 6T (No TWRP, OEM locked, MSM not working)

Hello dear community,
I've been playing with my 6t for a long time, hundreds of custom roms, kernels, etc..
Lastly I went to official oxygen 10. I tried to install twrp via fastboot but every time I tried to push the files, I would get a error. I reinstalled drivers, tried different ports, different tools..
I got mad and blindly followed some article where someone suggested putting "persist" in the fastboot command, I tried it, I thought it is some kind of "force push" the file and that is how I probably corrupted persist partition. DUMB
Phone not booting of course and I went to restore it with Msmdownload tool.
It did not fixed it.
I tried different versions of msm, I tried going to Hydrogen, tried different USB ports, tried type C ports, different PCs...
No luck, phone is stuck at bootloop, with no TWRP and bootlocked.
I read somewhere that Msmdownload tool is not flashing persist partition and I assume that is the reason why my phone can't be restored.
Fastboot commands are not working anymore and EDL mode is probably the only possible way to communicate with the device.
I live in Montenegro and I can't send phone to oneplus to repair it.
I searched the threads and noticed that some users with similar problem eventually succeed to restore the phone by flashing it with Msm multiple times. I am still trying to do it but no luck.
I would really appreciate help from dev mastermind.
Thank you!

If your bootloader is locked again, i think it is not possible to use Msn tool. I think the only way is to send it for repair if you can't boot the phone.
But maybe i'm wrong and someone else know the sollution.

Deurklink73 said:
If your bootloader is locked again, i think it is not possible to use Msn tool. I think the only way is to send it for repair if you can't boot the phone.
Click to expand...
Click to collapse
Thank you for response, but I think that msmdowload tool is made mainly to be able to flash even locked bootloaders, although I am not 100% sure...

Papagaj said:
Thank you for response, but I think that msmdowload tool is made mainly to be able to flash even locked bootloaders, although I am not 100% sure...
Click to expand...
Click to collapse
You are correct. Msm tool will work on locked bootloader.

Man that sucks. Seems like you might be screwed. I screwed up a couple times getting to A10 but I was able to get msm tool to work for me. You are using it while your phone is powered off, correct?

Try different version of android with msm tool. Like try using the Android 10 msm tool then try the Android 9 msm tool

GeekMcLeod said:
You are using it while your phone is powered off, correct?
Click to expand...
Click to collapse
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...

jamescable said:
Try different version of android with msm tool. Like try using the Android 10 msm tool then try the Android 9 msm tool
Click to expand...
Click to collapse
I tried several versions. I was hoping to find Android 10 tool for oneplus 6t but it is still not available.

Papagaj said:
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...
Click to expand...
Click to collapse
Sounds like a driver problem to me. Try gathering a few (by Google, OnePlus, perhaps even Samsung) and keep trying different ones. I had to do this on my OnePlus One years ago. Then suddenly I found one that worked and I could revive it back from the dead. Not saying that it would work for you but it might. In my case it was a Qualcomm tool. If you still end up with nothing but dead ends today, I'd initiate a chat with OnePlus on this page (select your country at the bottom of the page first).
Wrapped with delicious Fajita [emoji896]

The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
If you decide to do it (remember you WILL LOSE YOUR IMEIs and WIDEVINE L1!) follow this:
1.- Run MSMDownloadTool.
2.- Click on Verify and wait till it says "MD5 Check OK!".
3.- Then click on SMT Mode.
4.- Then click on Start like you would normally do with upgrade mode.
5.- The you need to enter as password "te123" and select your phone's capacity.
6.- If it says something like "Port disabled by user", go to the top left corner and click on "SMT", "COM Setup" and check everything, then click on the left button, and retry steps 4-5.
7.- When the process finishes the phone won't reboot, so you'll need to hold VolumeUP+Power until it powers on, then wait around 5 minutes and your phone will be back to life!!
8.- If you have an IMEI backup, just follow this guide (https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789) (I don't know if this is the correct way to post links)
I hope you get your phone fixed.

Papagaj said:
Hi GeekMcLeod, That's right, I boot it in bootloader mode, select "turn off" just to be sure that phone is shut down. And then I hold volume up and volume down together and plug the cable so it goes in EDL mode. Windows recognize it just as Qualcomm HS-USB QDLoader 9008, and that is all right I think.
Then I start MSMdownload tool and it flashes everything in around 200 seconds. I leave phone pluged in while it try to boots, but it never boot up. I left it for 45 minutes but still nothing...
Click to expand...
Click to collapse
Don't go to edl mode. Just have your phone powered off and use msm tool. I used it a couple times while getting to A10 and I only ever had to power my phone off.

amt911 said:
The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
If you decide to do it (remember you WILL LOSE YOUR IMEIs and WIDEVINE L1!) follow this:
1.- Run MSMDownloadTool.
2.- Click on Verify and wait till it says "MD5 Check OK!".
3.- Then click on SMT Mode.
4.- Then click on Start like you would normally do with upgrade mode.
5.- The you need to enter as password "te123" and select your phone's capacity.
6.- If it says something like "Port disabled by user", go to the top left corner and click on "SMT", "COM Setup" and check everything, then click on the left button, and retry steps 4-5.
7.- When the process finishes the phone won't reboot, so you'll need to hold VolumeUP+Power until it powers on, then wait around 5 minutes and your phone will be back to life!!
8.- If you have an IMEI backup, just follow this guide (https://forum.xda-developers.com/oneplus-6t/how-to/guide-oneplus-6t-unlock-bootloader-t3851789) (I don't know if this is the correct way to post links)
I hope you get your phone fixed.
Click to expand...
Click to collapse
@Papagaj do this....thats the only fix....I purposely wipe persist for to test something and I did that to recover from the boot loop.. persist store sensor information that vital to getting phone to boot....that's why it not booting..kernel is look for the sensor info but can't find it

Timmmmaaahh said:
Sounds like a driver problem to me. Try gathering a few (by Google, OnePlus, perhaps even Samsung) and keep trying different ones. I had to do this on my OnePlus One years ago. Then suddenly I found one that worked and I could revive it back from the dead.]
Click to expand...
Click to collapse
Timmmmaaahh I am so glad to see you on my thread! I learned fundamentals of flashing on your guides back in Bacon days, and never bricked it even once! But this A/B partitions really gave me headaches....
It is highly likely that drivers are causing problem, I tried to flash it with msm tool on fresh windows where I let it to automatically download required drivers and the msm progress appear to be same as when I used drivers which are recommended by msmtool developer. I will try several more and will be back with results within few hours.
amt911 said:
The only solution is to use smt mode inside msmdownloadtool, which will restore persist partition, but with some disadvantages.
Be aware that you WILL LOSE YOUR IMEIs and WIDEVINE L1, use it at your own risk.
8.- If you have an IMEI backup, just follow this guide
Click to expand...
Click to collapse
Is there a way to backup IMEI and WIDEVINE L1 at this moment? I think it is highly unlikely because functionality is limited to EDL only....
Or is there a way I can restore it later if I manage to fix a device with smt mode?
GeekMcLeod said:
Don't go to edl mode. Just have your phone powered off and use msm tool. I used it a couple times while getting to A10 and I only ever had to power my phone off.
Click to expand...
Click to collapse
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.

Papagaj said:
Timmmmaaahh I am so glad to see you on my thread! I learned fundamentals of flashing on your guides back in Bacon days, and never bricked it even once! But this A/B partitions really gave me headaches....
It is highly likely that drivers are causing problem, I tried to flash it with msm tool on fresh windows where I let it to automatically download required drivers and the msm progress appear to be same as when I used drivers which are recommended by msmtool developer. I will try several more and will be back with results within few hours.
Is there a way to backup IMEI and WIDEVINE L1 at this moment? I think it is highly unlikely because functionality is limited to EDL only....
Or is there a way I can restore it later if I manage to fix a device with smt mode?
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.
Click to expand...
Click to collapse
Nope....just rewrite you IMEI with a Qualcomm tool..quite a few available

Papagaj said:
How do you mean? I can't get phone connected with msm tool if it is not in EDL mode.. It is not recognized when in stock recovery, bootloader or trying to boot up OS, that is only three states this phone can be at the moment.
Click to expand...
Click to collapse
Oh. The few times I used it I just powered off my phone and connected it to my computer. Started msm tool and it did its thing.

Papagaj said:
this A/B partitions really gave me headaches
Click to expand...
Click to collapse
You and me both! ? lol...

I recently got stuck in a weird bootloop thing with a, what i think was, corrupted boot.img. Try finding a stock android boot.img, boot to fastboot, and run the command fastboot flash boot <boot.img> on both partition A and B. If you can't find a stock boot.img, i managed to find one and can link to a download.

All right, here is the situation.
I finally managed to boot up the phone. amt911 gave working instructions on post #10. Thank you bro, you are awesome, and Thank you Tech_Savvy for confirming the method, you are badass who deletes partitions just for fun!
All right I got the phone booted up but as amt911 mentioned, I lost my IMEI numbers, without IMEI numbers you can't dial numbers, receive calls or use mobile data.
BACKUP IMEI NUMBERS FOLKS, you never know when the partitions will screw you over!
I was dumb one without backup and I had to contact Oneplus support for help. I was suprised how quickly I got into communications with one of the assistants.. in less than 10 seconds.
They ask you to do full reset via stock recovery and some other basic troubleshoots, after nothing, obviously, fix the missing IMEI they will arrange remote session to get your phone fixed.
You have to persist on remote session as some of assistants told me that I have to send the phone to repair.
Before they arrange session for you, you need to show them "proof of the purchase" ALSO KEEP THAT FOLKS I lost mine long time ago but luckily I found photo of invoice I took when I bought phone, phew*
I didnt have it at first when I contacted them and they say there is nothing they can do without a proof! DON'T STEAL PHONES FOLKS and then ask for support...
They will contact me for session within 48 hours and I will share the experience here.
Thank you again people!

JTVivian said:
I recently got stuck in a weird bootloop thing with a, what i think was, corrupted boot.img. Try finding a stock android boot.img, boot to fastboot, and run the command fastboot flash boot <boot.img> on both partition A and B. If you can't find a stock boot.img, i managed to find one and can link to a download.
Click to expand...
Click to collapse
Thank you JTVivian for helpful suggestion, but that method would not work. When your bootloader is locked, fastboot commands are useless, you can't flash anything.

Papagaj said:
Thank you JTVivian for helpful suggestion, but that method would not work. When your bootloader is locked, fastboot commands are useless, you can't flash anything.
Click to expand...
Click to collapse
Ah you're right, i wasn't sure if that was the case but i thought i'd throw out the suggestion anyways.

Screen dead after wrong firmware update

Hi all,
So basically I was trying to install Pixelexperience to my Note 7 today and I messed it up big time. So I was having some issues with TWRP and one of the solutions (according to posts I found on Google) was to update the phone firmware. So I went to do that. Downloaded the lavander firmware for my Note 7, put it in the folder with other stuff I was downloading. One of these was firmware for Redmi A5 (which I didn't notice) and ended up flashing that. Now my phones screen is dead (I guess the rest of it also?). When I plug it in to PC the PC produces the sounds that something connected but running fastbood / adb devices doesn't return anything. I tried multiple times booting to fastboot / recovery but I have no idea when the phone is on or off. So it just produces sound on PC that it disconnected and connected like 1 second after but nothing still shows up on fastboot.
Did anyone had similiar issue and is there anything I can do? Or should I go look for a new phone?
Thank you for your time

Try to flash the whole rom again.

VD171 said:
Try to flash the whole rom again.
Click to expand...
Click to collapse
Well, I thought about that, but I don't know how to flash it since it seems I can't boot into fastboot. I've tried countless times and failed every time

vivida said:
Well, I thought about that, but I don't know how to flash it since it seems I can't boot into fastboot. I've tried countless times and failed every time
Click to expand...
Click to collapse
Try any tool:
Xiaomitool: https://www.xiaomitool.com/V2/​Miflashpro: https://miflashpro.com/​Miflashtool: https://xiaomiflashtool.com/​

VD171 said:
Try any tool:
Xiaomitool: https://www.xiaomitool.com/V2/​Miflashpro: https://miflashpro.com/​Miflashtool: https://xiaomiflashtool.com​​I have tried but I just can't get the devices to boot into fastboot and I have no idea in what state it is since the screen doesn't show anything
Click to expand...
Click to collapse

Can you enter in recovery ?

VD171 said:
Can you enter in recovery ?
Click to expand...
Click to collapse
No, the same thing is happening. I just get the sound on PC and that's about it. It isn't recognized by the PC or any software that I tried to use

Try to get new cable and it will work

Eslamloka said:
Try to get new cable and it will work
Click to expand...
Click to collapse
After that's make your phone in edl mode then flash stock miui with miflash tool

Eslamloka said:
After that's make your phone in edl mode then flash stock miui with miflash tool
Click to expand...
Click to collapse
I receive cannot receive hello packet error message now

vivida said:
I receive cannot receive hello packet error message now
Click to expand...
Click to collapse
Sorry but i can't understand,,,is u tried to change a cable and it's working or not

Eslamloka said:
Sorry but i can't understand,,,is u tried to change a cable and it's working or not
Click to expand...
Click to collapse
I tried changing it but it doesn't work. The problem is I can't flash anything on MiFlash because it requires something like technicians account

vivida said:
I tried changing it but it doesn't work. The problem is I can't flash anything on MiFlash because it requires something like technicians account
Click to expand...
Click to collapse
before miflash firstly you must connect your phone with pc or laptop