Develop Bugs

lg e975 stuck in clockworkmod boot loop

I recently installed miui from official website for lg e975. My phone is lg f180 so they both are same.
It was working fine till this morning it asked for update. I allowed. It retarted and now it starts shows google logo. Then goes to recovery.
I flashed my original backup rom. Then even flashed miui rom. Nothing changes. I wiped cache. Data dalvik a lot of times.
It just starts shows google logo. Goes to recovery. Please help
Im sorry if this thread doeant belong here. Mods please move

Thought i should add.
I dont have any other access but cwm recovery
I only have a backup of my original rom through cwm. No kdz files.
I have a miui zip rom on phone as well

awais3344 said:
Thought i should add.
I dont have any other access but cwm recovery
I only have a backup of my original rom through cwm. No kdz files.
I have a miui zip rom on phone as well
Click to expand...
Click to collapse
Flash stock zip kernel from artmod thread.

the problem is. I can't upload any files to mobile phone. if i connect to pc, it turns on, goes to recovery, so I click on mount storage, and other mount option, nothing happens. My computer detects phone as F180L with a exclamation mark.
If i go to download mode, and then try to flash any KDZ file from all the f180 KDzs. It gives me errors.
LG Support Tool on entering serial number and model name says "check out serial number and model"
ADB never detects my phone. So I can't upload anything.
No option to upload files via SD Card.

ok, so I have no clue what happened :crying: phone was in download mode. I did nothing, but only installed LG Support Tool USB driver, while the mobile connected.
Then I installed Microsoft .net framework 4.0. And my phone is now qhs_usbdload. it's officially bricked now. I have no clue what happened. This is all that happened before I restarted and selected "reboot to bootloader" and its dead. So there's nothing left to do but throw it out

WTF OKAY! I have no clue!
But, after seeing that qhs usbdload. (i have seen that before with other phones). I complete lost any hope.
So I for feeling contended, downloaded qpst, and emmc software download, and selected MPRG8064.hex and msimage.bin.
Then like I expected it threw an error "image download failed, cookie if present not received"
so I lost hope disconnected my phone and put it there. After a few minutes thought I should try one last time.
so I connect it my pc and VIOLA it turns ON!?
now I have that same rebooting to recovery problem. I have no explanation for whatever has happened to phone in past 3 hours. I have been with phones for years. This is the weirdest thing to happen ever :angel:
Now someone, please help me?

1. Why is this in Development section?
2. You can't mount internal SD as USB storage. Use adb push or adb sideload instead, that will help you to get the files onto your phone.

awais3344 said:
WTF OKAY! I have no clue!
But, after seeing that qhs usbdload. (i have seen that before with other phones). I complete lost any hope.
So I for feeling contended, downloaded qpst, and emmc software download, and selected MPRG8064.hex and msimage.bin.
Then like I expected it threw an error "image download failed, cookie if present not received"
so I lost hope disconnected my phone and put it there. After a few minutes thought I should try one last time.
so I connect it my pc and VIOLA it turns ON!?
now I have that same rebooting to recovery problem. I have no explanation for whatever has happened to phone in past 3 hours. I have been with phones for years. This is the weirdest thing to happen ever :angel:
Now someone, please help me?
Click to expand...
Click to collapse
Some user got that problem before. I am not sure about how they solve it but I guess that they flash their original KDZ back. If your phone can enter download mode, you should try LG Flash tool 2014 and flash your original kdz to restore incorrect system image.
About adb cannot find your phone, try to remove adb driver from device manager and reinstall LG usb driver.

artit said:
Some user got that problem before. I am not sure about how they solve it but I guess that they flash their original KDZ back. If your phone can enter download mode, you should try LG Flash tool 2014 and flash your original kdz to restore incorrect system image.
About adb cannot find your phone, try to remove adb driver from device manager and reinstall LG usb driver.
Click to expand...
Click to collapse
My phone is acting weird. Sometime it would start. Sometime the red light would blink. Sometimes the red light wouldn't blink at all. Then sometimes, it starts. And then it doesn't.
I have no clue what is going on with it.
But it went to download mode many times again, it would go to fastboot, bootloader, recovery etc. Then sometimes it will not respond to any buttons at all! I know its battery is down, but idk if it's charging or not?
I don't know how to know whether the phone is charging or not. I left it charging for 30 minute, and it didn't even buzz. :crying:

awais3344 said:
I know its battery is down, but idk if it's charging or not?
I don't know how to know whether the phone is charging or not. I left it charging for 30 minute, and it didn't even buzz. :crying:
Click to expand...
Click to collapse
One thing you can do (I've done it in the past a couple of times) is to crack your phone open, disconnect the battery, and charge it with an external charger. That would at least give you a full battery to start with...

Regarding the charging problems, I had that once. I was able to startup the phone by simply using a 2A charger instead of the LG's 1.2A.

When I had this issue it was charging while in recovery. Please look at this post and flash your kdz.
http://forum.xda-developers.com/showthread.php?p=54934779. This one helped me http://forum.xda-developers.com/showthread.php?p=53728658
Sent from my LG-E975 using XDA Free mobile app

kt-Froggy said:
One thing you can do (I've done it in the past a couple of times) is to crack your phone open, disconnect the battery, and charge it with an external charger. That would at least give you a full battery to start with...
Click to expand...
Click to collapse
thanks. but after charging it. I couldn't turn the screen off because it goes in recovery. I turned off the phone after good 30 minute charging. Then went to sleep. And in the morning I connected it to pc. by holding volume buttons for download mode. It didn't go to download mode. Only it's red light is blinking. and no display.

awais3344 said:
thanks. but after charging it. I couldn't turn the screen off because it goes in recovery. I turned off the phone after good 30 minute charging. Then went to sleep. And in the morning I connected it to pc. by holding volume buttons for download mode. It didn't go to download mode. Only it's red light is blinking. and no display.
Click to expand...
Click to collapse
Hey man. I have exaxt same prolem when update miui. Just do this when you got your recovey. Connect your phone to pc, let your pc update driver. Use adb sideload to flash stock zip kitkat e975 lgviet. Goodluck.

huy_gm said:
Hey man. I have exaxt same prolem when update miui. Just do this when you got your recovey. Connect your phone to pc, let your pc update driver. Use adb sideload to flash stock zip kitkat e975 lgviet. Goodluck.
Click to expand...
Click to collapse
Hi, regarding that. I was able to sideload exitrecovery.zip file. It goes to 100% then nothing happens. Nothing happened on phone screen as well.
And can you send me link to that stock zip kitkat? i have a miui.zip and few other roms that I have not tried. thanks
Edit: also what should I do about adb, am i doing correct?
Becuase in adb devices, my device is displayed with deviceID sideload
And i have only pasted adb folder, with a dll and a zip file, there is nothing else, do I need to install SDK?

I tried lg flash tool 2014 again, and it flashed, I swear yesterday I tried to flash it, and after clicking on it, it never showed me country and language selection menu, so it would sit there and do nothing. now I don't know how but it did it :laugh:
thank you so much you'all

LG G4 bootloop.... Need expert help... Ready to pay the price

Hello,
I had been using a H815T, locked bootloader, running Seven HD rom v6.1 for more than 2 months flawlessly. Suddenly yesterday my phone was in charge and it restarted and went into bootloop. Since I tried many things and I went to some local technicians as well as one LG engineer, but all failed to gimme any solution. And I don't have any warrenty, I couldn't ask for a replacement for anyone.
So here's what I tried:
1. Flashing international KDZ
2. Flashing default KDZ
3. Formatting from recovery mode
4. Changing battery
Here's what works:
1. Download mode
2. Recovery mode
So I am ready to pay if anyone gimme a solution out of this. Any help will be appreciated as I am in real trouble coz I cannot afford a new phone now.
With thanks

nipun1110 said:
Hello,
I had been using a H815T, locked bootloader, running Seven HD rom v6.1 for more than 2 months flawlessly. Suddenly yesterday my phone was in charge and it restarted and went into bootloop. Since I tried many things and I went to some local technicians as well as one LG engineer, but all failed to gimme any solution. And I don't have any warrenty, I couldn't ask for a replacement for anyone.
So here's what I tried:
1. Flashing international KDZ
2. Flashing default KDZ
3. Formatting from recovery mode
4. Changing battery
Here's what works:
1. Download mode
2. Recovery mode
So I am ready to pay if anyone gimme a solution out of this. Any help will be appreciated as I am in real trouble coz I cannot afford a new phone now.
With thanks
Click to expand...
Click to collapse
that block at 9% and told you to remove batery unplug phone etc etc?

i have same problem and no 2nd phone here -.- we need a Updated LG Flash Tool 2014 to flash the 20A.kdz

fr33kiLL said:
i have same problem and no 2nd phone here -.- we need a Updated LG Flash Tool 2014 to flash the 20A.kdz
Click to expand...
Click to collapse
unfortunaly we can wait a long time maybe ...

nipun1110 said:
Hello,
I had been using a H815T, locked bootloader, running Seven HD rom v6.1 for more than 2 months flawlessly. Suddenly yesterday my phone was in charge and it restarted and went into bootloop. Since I tried many things and I went to some local technicians as well as one LG engineer, but all failed to gimme any solution. And I don't have any warrenty, I couldn't ask for a replacement for anyone.
So here's what I tried:
1. Flashing international KDZ
2. Flashing default KDZ
3. Formatting from recovery mode
4. Changing battery
Here's what works:
1. Download mode
2. Recovery mode
So I am ready to pay if anyone gimme a solution out of this. Any help will be appreciated as I am in real trouble coz I cannot afford a new phone now.
With thanks
Click to expand...
Click to collapse
stock recovery or twrp..

Google~Android said:
stock recovery or twrp..
Click to expand...
Click to collapse
we have not access at twrp anymore .... and kdz method doesnt work . phone recognized in all lg software ... support tool 9% and issue

shudoha said:
we have not access at twrp anymore .... and kdz method doesnt work . phone recognized in all lg software ... support tool 9% and issue
Click to expand...
Click to collapse
did you have an unlocked bl or not?

Google~Android said:
did you have an unlocked bl or not?
Click to expand...
Click to collapse
of course for flash first twrp and after flash all autoprime files and after this .. impossible to have access at twrp . hard reset work . but nothing happens boot loop kdz for rollback doesnt work too . still blocked at 9% on the tool and 0 on my phone and ask me to remove the battery etc etc i did that too much time . but for nothing and the worst . bridge .. support tool recognize my phone like H815 then no driver problem

i have unlocked BL but didnt have access to ADB and Fastboot(idk why) and got stock recovery after flashing so no chance to go in TWRP

Does the phone freeze at random times? Like no matter where its at, sometimes it boots to the operating system?

Hardware
It's starting to sound more and more like a MEM BLOCK corruption..

Have you tried this: Firmware to Stock with kdz and tot?

Noo

shudoha said:
that block at 9% and told you to remove batery unplug phone etc etc?
Click to expand...
Click to collapse
No..nothing like that

mr turtle droid said:
It's starting to sound more and more like a MEM BLOCK corruption..
Click to expand...
Click to collapse
What's that and what's the remedy? And usually what causes it?

martinsavvy said:
Does the phone freeze at random times? Like no matter where its at, sometimes it boots to the operating system?
Click to expand...
Click to collapse
To me it used to happen sometimes while charging. I had to manually switch off the screen and when i switched on the screen, it became normal for a while. I thought it was due to heavy xposed customizations.

michael08071984 said:
Have you tried this: Firmware to Stock with kdz and tot?
Click to expand...
Click to collapse
That's the KDZ method. Yah I tried it as I mentioned.

michael08071984 said:
Have you tried this: Firmware to Stock with kdz and tot?
Click to expand...
Click to collapse
tested but like i told you .... blocked at 9% and remove battery unplug etc etc and nothing happend

Try this:
copy all zip files you need to reflash (10D or similar) to a memcard
Also download latest twrp and copy it to the directory where you have adb.exe
Open a Command prompt on your PC (where adb is located) and powerup the phone,
open up the Device Manager on your PC to see when the adb device is there,
in the moment where you see the adb device fire up the comand:
adb reboot bootloader
if that works enter the comand:
fastboot boot twrp-2.8.7.0-h815.img
this will boot directly into Twrp without flashing twrp and you can try things from twrp
I hope this will help here, helped me with the phone from a friend of me who had a similar problem.

fire3d said:
Try this:
copy all zip files you need to reflash (10D or similar) to a memcard
Also download latest twrp and copy it to the directory where you have adb.exe
Open a Command prompt on your PC (where adb is located) and powerup the phone,
open up the Device Manager on your PC to see when the adb device is there,
in the moment where you see the adb device fire up the comand:
adb reboot bootloader
if that works enter the comand:
fastboot boot twrp-2.8.7.0-h815.img
this will boot directly into Twrp without flashing twrp and you can try things from twrp
I hope this will help here, helped me with the phone from a friend of me who had a similar problem.
Click to expand...
Click to collapse
problem boot loop when i open my phone even with hard reset that change nothing and adb said : device not found when all program like lg support or bridge recognize my phone like h815 ... then not solution

Soft Bricked LG G3 D855, Please Help

I am not new to rooting and unlocking Androids. My LG G3's UI would randomly freeze where I had to reboot the device to have it working again. Today I decided to flash the vanilla unicorn rom in recovery. I downloaded the rom and copied it over to the phone but the copy process kept getting stuck at some point, that I always had to cancel it.
So I decided to wipe cache and data to just reinstall the official d855 CM13 rom I had earlier on the device's storage, the wipe got stuck for at least 20 mins. I got impatient and removed the battery trying to reboot into recovery, but I was stunned and stuck on the LG Splash screen logo, I kept trying to reboot into recovery but couldn't get past the LG splash screen.
I then decided to try rebooting into fastboot, I was able to boot into fastboot the normal way without any issues but every attempt at getting TWRP just wasn't yielding anything useful. The closest I've gotten to seeing TWRP since then was with the fastboot command
Code:
fastboot boot recovery.img
which reboots showing the TWRP splash screen image without actually showing TWRP, but I've noticed I can access adb while the screen is stuck on the TWRP splash screen image.
I can't do any sideload of the zips on my computer because TWRP just stays there stuck on the splash screen so I can't enable sideloading. I have spent hours with this and it has taken too much of my time, attempts at
Code:
fastboot flash recovery recovery.img
just returns with an error in cmd with FAILED (remote: flash write failure).
I can't figure out what to do anymore, I'm left with a phone that can't boot into the rom and recovery, only the fastboot and download mode works. I just need the phone to let me boot into recovery so I can flash the files I need to and have my phone back to its earlier state.
I'll really appreciate everyone's support, thanks!

geek-x said:
I am not new to rooting and unlocking Androids. My LG G3's UI would randomly freeze where I had to reboot the device to have it working again. Today I decided to flash the vanilla unicorn rom in recovery. I downloaded the rom and copied it over to the phone but the copy process kept getting stuck at some point, that I always had to cancel it.
So I decided to wipe cache and data to just reinstall the official d855 CM13 rom I had earlier on the device's storage, the wipe got stuck for at least 20 mins. I got impatient and removed the battery trying to reboot into recovery, but I was stunned and stuck on the LG Splash screen logo, I kept trying to reboot into recovery but couldn't get past the LG splash screen.
I then decided to try rebooting into fastboot, I was able to boot into fastboot the normal way without any issues but every attempt at getting TWRP just wasn't yielding anything useful. The closest I've gotten to seeing TWRP since then was with the fastboot command which reboots showing the TWRP splash screen image without actually showing TWRP, but I've noticed I can access adb while the screen is stuck on the TWRP splash screen image.
I can't do any sideload of the zips on my computer because TWRP just stays there stuck on the splash screen so I can't enable sideloading. I have spent hours with this and it has taken too much of my time, attempts at just returns with an error in cmd with FAILED (remote: flash write failure).
I can't figure out what to do anymore, I'm left with a phone that can't boot into the rom and recovery, only the fastboot and download mode works. I just need the phone to let me boot into recovery so I can flash the files I need to and have my phone back to its earlier state.
I'll really appreciate everyone's support, thanks!
Click to expand...
Click to collapse
Does your computer recongnise your phone. If it does you (probably) can use LG up tool to flash kdz file

dusan17 said:
Does your computer recongnise your phone. If it does you (probably) can use LG up tool to flash kdz file
Click to expand...
Click to collapse
I have tried using the flash tool, but I can't get into Download mode to use the LG Flash tool to get back to stock. All I get is fastboot.
There was a tutorial about using two wires on the emmc, but I haven't been able to get the Qualcomm HD_USB 9008 to show up in Device manager.
Sent from my ONE A2005 using Tapatalk

geek-x said:
I have tried using the flash tool, but I can't get into Download mode to use the LG Flash tool to get back to stock. All I get is fastboot.
There was a tutorial about using two wires on the emmc, but I haven't been able to get the Qualcomm HD_USB 9008 to show up in Device manager.
Click to expand...
Click to collapse
I have the same case with my old LG L90. I spent a lot of time trying to get it back to life without success . I have read another post similar to this but the wire thing worked. I really don't know then.

dusan17 said:
I have the same case with my old LG L90. I spent a lot of time trying to get it back to life without success . I have read another post similar to this but the wire thing worked. I really don't know then.
Click to expand...
Click to collapse
What kind of wire did you use in getting it to work?
And how were you able to get windows to show the QLoader usb com port. ?

geek-x said:
What kind of wire did you use in getting it to work?
And how were you able to get windows to show the QLoader usb com port. ?
Click to expand...
Click to collapse
I didn't want to mess around with motherboard so i gave phone to my uncle because he is better than me in that stuff. But sadly we didn't bring it back to life.

dusan17 said:
I didn't want to mess around with motherboard so i gave phone to my uncle because he is better than me in that stuff. But sadly we didn't bring it back to life.
Click to expand...
Click to collapse
Damn.

geek-x said:
Damn.
Click to expand...
Click to collapse
I saw people unbrick devices that way we propably did somenthing wrong. For the wires i would use copper wires.

Do you have Qualcomm drivers installed in pc?
I have unbricked many mobile using this pin shortening trick.it's simple.just make sure you are shortening the right pins.

Jahanzaibawan said:
Do you have Qualcomm drivers installed in pc?
I have unbricked many mobile using this pin shortening trick.it's simple.just make sure you are shortening the right pins.
Click to expand...
Click to collapse
I can't get the Qualcomm drivers to show up in Device Manager, even after installing the Qualcomm drivers and I have enabled test mode and all that. My com ports don't show anything Qualcomm at all.

Jahanzaibawan said:
Do you have Qualcomm drivers installed in pc?
I have unbricked many mobile using this pin shortening trick.it's simple.just make sure you are shortening the right pins.
Click to expand...
Click to collapse
Does it also matter that I am using a USB 3.0 port? My laptop has no 2.0 ports.

This might be helpful http://forum.xda-developers.com/spr...fix-hard-brick-recovery-guide-t3132359/page59

dusan17 said:
This might be helpful http://forum.xda-developers.com/spr...fix-hard-brick-recovery-guide-t3132359/page59
Click to expand...
Click to collapse
Thanks for that post. I'll give it a try again tonight, I just need the Qualcomm 9008 drivers to come up.
Cause I noticed every time attach the wire to the board, windows recognizes the phone with an error "USB device not recognized" and in device manager a yellow warning mark next to one of the USB device icons.
Sent from my ONE A2005 using Tapatalk

geek-x said:
Thanks for that post. I'll give it a try again tonight, I just need the Qualcomm 9008 drivers to come up.
Cause I noticed every time attach the wire to the board, windows recognizes the phone with an error "USB device not recognized" and in device manager a yellow warning mark next to one of the USB device icons.
Click to expand...
Click to collapse
I that case right click chose update drivers and chose drivers manualy. Something like that should help you get device recognized

dusan17 said:
I that case right click chose update drivers and chose drivers manualy. Something like that should help you get device recognized
Click to expand...
Click to collapse
What directory will I choose to install the drivers from, the Qualcomm installation directory doesn't seem to contain the actual driver files.

geek-x said:
What directory will I choose to install the drivers from, the Qualcomm installation directory doesn't seem to contain the actual driver files.
Click to expand...
Click to collapse
Uf, i don't know it should be listed.

geek-x said:
Does it also matter that I am using a USB 3.0 port? My laptop has no 2.0 ports.
Click to expand...
Click to collapse
Yup.mostly 3.0 doesn't work.80% 3.0 cause the problem.

Jahanzaibawan said:
Yup.mostly 3.0 doesn't work.80% 3.0 cause the problem.
Click to expand...
Click to collapse
I'll try to get a USB 2.0 laptop to try this on. I just hope it works this time.

ZenFone 2 Bootloader problem. Need help.

I recently recoverd from a brick using the usual xfstk downloader asus flash tool ect... i think i quit the asus flash tool too early and it left me with a buggy android. my problem is. there is no bootloader! when i try get to it ( even through adb) theres nothing there! but theres a fully working android. I tried to use xfstk downloader again, and when it says "continuing to os" all it does is put me in android with no bootloader. I really want a way to fully wipe my device so i can start fresh again. Is this safe? is there a better way?

that's why i always recommend to use commands method to flash after xfstk. any ways enable developer option and usb debugging. then connect to pc and run command adb reboot recovery. most probably you will boot into recovery factory reset there and sideload latest firmware downloaded from asus website.
if you are rooted then you can flash bootloader via dd commands

sukhwant717 said:
that's why i always recommend to use commands method to flash after xfstk. any ways enable developer option and usb debugging. then connect to pc and run command adb reboot recovery. most probably you will boot into recovery factory reset there and sideload latest firmware downloaded from asus website.
if you are rooted then you can flash bootloader via dd commands
Click to expand...
Click to collapse
I tried to do the adb thing. and it just took me into the os
i am not rooted. is there any hope for me?

aceaidan said:
I tried to do the adb thing. and it just took me into the os
i am not rooted. is there any hope for me?
Click to expand...
Click to collapse
then do xfstk again and flash raw via commands

sukhwant717 said:
then do xfstk again and flash raw via commands
Click to expand...
Click to collapse
I know it sounds like allot, but can you tell me how to do these things. I'm a total noob and you sound like a nice guy.

sukhwant717 said:
then do xfstk again and flash raw via commands
Click to expand...
Click to collapse
Also the xfstk won't complete because when it says continuing to os. It just takes me back to android.

I recommend to use this guide
https://forum.xda-developers.com/showthread.php?p=68477856
It's the only way to get my ZE551ML run again.
After using xfstk, go forward without AsusFlashTool and do all steps manually as described in the guide. It helped me to get my bricked ZF2 run again with newest MM.
Good luck.

aceaidan said:
Also the xfstk won't complete because when it says continuing to os. It just takes me back to android.
Click to expand...
Click to collapse
here are few things you can do! wipeout ifwi on emmc. and then use latest MM ifwi on marshmallow. if still same open back panel of the phone disconnect battery connector and place small paper under connector leave it like 7 days and after that try xfstk again with original files

mobil_z said:
I recommend to use this guide
https://forum.xda-developers.com/showthread.php?p=68477856
It's the only way to get my ZE551ML run again.
After using xfstk, go forward without AsusFlashTool and do all steps manually as described in the guide. It helped me to get my bricked ZF2 run again with newest MM.
Good luck.
Click to expand...
Click to collapse
Can you please link me to the manual files for mm in stuck on the first stock android.

aceaidan said:
Can you please link me to the manual files for mm in stuck on the first stock android.
Click to expand...
Click to collapse
didnt get you point!
what does you mean by first stock android?
what files you are asking for MM?
what exactly you want to do?

aceaidan said:
Also the xfstk won't complete because when it says continuing to os. It just takes me back to android.
Click to expand...
Click to collapse
It may be a fault in some other guides by addressing in xfstk.
The right address is 0x80000807, some other guides show 0x800000807, one 0 too much!
The guide I linked to does it right.

sukhwant717 said:
didnt get you point!
what does you mean by first stock android?
what files you are asking for MM?
what exactly you want to do?
Click to expand...
Click to collapse
My acrossim running android 5.0 and I want my bootloader back and then I want the mm files like system.img ect... So I can get mm

aceaidan said:
So I can get mm
Click to expand...
Click to collapse
If you finally want to go to MM, you can install it directly if your phone is broken now. So you will get a very clean MM without messed up from updading from LP! Really recommend.

hey ,i have same problem with my asus zenphone 2 , had you got any perfect solution? please help!!
every time i tried to flash files using xfstk is show countinuing to os and then show error - enable to connect with device!!

No way to unbrick this phone

Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?

Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2

dmilz said:
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3405700/amp/
That always works.. use method 2
Click to expand...
Click to collapse
Not this time... That is the tool I mentioned, only gets me back to the bootloop

Robert1852 said:
Not this time... That is the tool I mentioned, only gets me back to the bootloop
Click to expand...
Click to collapse
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again

dmilz said:
I know what you talking about.. Went through that too when i used method one.. use method 2..it will flash stock OOS and you will boot successfully
If you already did..try once more..download the tools over again
Click to expand...
Click to collapse
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..

Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Ooh ok.. i see.. hope you will find a way out

Robert1852 said:
Yeah already tried method 2 multiple times, downloaded the tools again but it still doesn't work on this phone..
Click to expand...
Click to collapse
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?

Xceeder said:
Probably a stupid question but have you tried flashing oxygen os recovery and then tried to flash stock ROM?
Click to expand...
Click to collapse
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked

Robert1852 said:
That unbrick tool also flashes the stock recovery. I cant flash anything using fastboot because the bootloader is locked
Click to expand...
Click to collapse
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.

Puddi_Puddin said:
And why is it locked then? Why would you ever relock your bootloader? You should be able to unlock it anyway without going in to settings. Are you sure you are using the correct drivers? Windows installs the wrong once by default.
Click to expand...
Click to collapse
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers

Robert1852 said:
It has never been unlocked. In the settings is the "Allow OEM Unlock" option which you should check before you can unlock the bootloader. As long as I can't boot the phone I can't check this option, or someone must know a workaround. Yes I'm pretty sure I'm using the correct drivers
Click to expand...
Click to collapse
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?

Puddi_Puddin said:
If you plug your phone in how does it show up under Device Manager? Have you also tried "fastboot OEM Unlock"?
Click to expand...
Click to collapse
When it's in the bootloader menu it shows up as "Android Bootloader Interface", when it's in EDL mode it shows up as "Qualcomm HS-USB QDLoader 9008 (COM3)". It connects fine with the pc and flashes everything without problems as far as I can see. Yeah it says "FAILED (remote: oem unlock is not allowed)" probably because the allow oem unlock option in the settings isn't checked.

Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.

ZVNexus said:
Most likely won't do anything, but have you tried a different computer? Seems like it would make no difference but tiny things like that have saved me in the past.
Click to expand...
Click to collapse
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...

Robert1852 said:
Yea I know what you mean I tried it on a few different computers, even with different cables but it doesn't make a difference...
Click to expand...
Click to collapse
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.

Puddi_Puddin said:
Pretty sure you are using wrong drivers. You should be able to unlock the bootloader even tho it is remote. When I first bricked my phone I forgot about the drivers aswell. My phone booted up and showed. System: Failed, Userdata:Failed. This means it failed to detect those partitions which you can find in unbrick program itself called system.img, userdata.img. You can actually flash these manually with fastboot flash system system.img but I also got the "Remote is not allowed error". After booting into disabled Driver Signature Enforcement mode and changing the drivers from on the guide I could actually flash these partitions. Your phone has to show up as Qualcomm 9008 or something close and not as Android Interfere Device. I have helped multiple people fixing their phone with this guide and they also had a locked bootloader and they also did not have the correct drivers.
Boot into https://www.google.com/amp/s/www.ho...so-that-you-can-install-unsigned-drivers/amp/ then install the driver linked on the Unbrick Guide. Your phone should show up correctly. Then run the unbrick guide as admin and it should go through flawless.
Click to expand...
Click to collapse
Tried everything it says in the guide about the drivers (even the last part about installing the certificates) but it just keeps showing up as qualcomm hs-usb qdloader 9008, even though I'm pretty sure they are installed correctly. It just won't show up as Qualcomm 9008, as it is supposed to, whatever I try. But it looks like these drivers are only for the EDL mode, and as far as I know it is normal for the phone to show up as Android Bootloader Interface when it's in the bootloader menu. And you can't use fastboot from EDL mode... Will try it later again on a different pc though, really hope you are right about the drivers after all

Hi Robert,
I am having same problem with my oneplus3. I also tried both unbrick methods and tried different oxygen ROMs.
Are you able to fix your phone?
Thanks in Advance,
Anil

Have you tried this http://www.androidbrick.com/oneplus-one-two-3-3t-5-mega-unbrick-guide-twrp-flashing/

Robert1852 said:
Hey guys,
I've got a Oneplus 3 that freezes every time it tries to boot. Fastboot and recovery are still working, factory reset makes no difference. After sideloading the latest OxygenOs the screen just goes blank after the Oneplus splash screen and recovery doesn't work anymore. The MsmDownloadTool only gets me where I started, back at the bootloop. So the old OOS gives me bootloop with recovery and fastboot while the new OOS only gives me fastboot and a blank screen.
New system with old working boot and recovery gives "md5 checksum failed".
The bootloader is locked and as long as I can't get in the settings there is no way to unlock it, so my options are pretty limited here.
I've contacted Oneplus but they aren't really helping either.
Is there any way to get this thing back to life?
Click to expand...
Click to collapse
Hi
Go back to an older Version...3.xx
worked for me
be warned ..3.xxx formats internal memory

I also have the same problem, I'll try to restore to old version too.
Do you also have artifacts on the screen?