Develop Bugs

[Q] Nexus stuck in boot loop. how get to install drivers?

Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!

dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.

First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?

dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.

cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?

dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.

Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium

WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.

Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium

ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.

dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!

bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......

Anything at all? Anyone?
Sent from my Nexus 4 using xda premium

dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.

bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?

dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.

bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.

Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.

rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...

[Q] Can my N7(2013) still be saved?

Hi, my N7 is bricked and I wanted to fix it.
I tried to flash ROM but couldn't do it since my computer wont recognize my N7 (except in Recovery Mode-> Sideload).
I think it has something to do with the "developer options -> need to check USB Debugging", however, I can't do that since my phone when turned on, Google Logo appears, then afterwards, BLACK SCREEN (and now in a loop, but there is no X logo just plain black).
My phone is rooted & unlocked. Out of curiousity (My fault), I bricked my N7.
I've read a lot of article on how to unbrick my N7 and I think I now know how to do it- through Android SDK/ADB Tool. I've also read the a guide on how to change drivers (and tried it in all possible ways I can think of), and it did install the driver. However searching my N7 through ADB Tool doesn't go through.
adb devices
List of devices attached
(**nothing follows**)
But if I turn my N7 to Recovery Mode->apply update from adb:
will show the result:
adb devices
List of devices attached
**serial number** sideload
I don't know what other ways in order to unbrick my N7.
I hope you can help me with it.

You can enter bootloader, right? Then try to use fastboot to flash a new rom.

Use wugs program but tick tablet is in bootloop.

Can you boot a brick in to recovery mode? No...so you aren't bricked...

Thanks for the info man!
AnarchoXen said:
Can you boot a brick in to recovery mode? No...so you aren't bricked...
Click to expand...
Click to collapse
Hi, thanks for the info... I already solved my problem.. If only I have read your post earlier I could've saved xx hours in my research!! LOL
donb1 said:
Use wugs program but tick tablet is in bootloop.
Click to expand...
Click to collapse
I tried, but N7 isn't recognized by PC. So the main problem is really how to make my N7 recognized by PC (ADB/bootloader).
But problem fixed now. Thanks!
Calvin Gross said:
You can enter bootloader, right? Then try to use fastboot to flash a new rom.
Click to expand...
Click to collapse
Before I fixed my N7, this is what I tried. But the problem is, PC wont recognize/find my N7 when I do:
adb devices nor fastboot devices
But, I already fixed my problem. Thanks for the response! Greatly appreciate it!

[q] lg g3 d855 hard bricked no download mode or recovery!

Hi all, I come to you as my last resort.
I have spent hours on google trying to find a solution to my problem.
This is what happened.
I store my ROMS on an external SD and sometimes i get the error that it is being removed unexpectedly...sometimes..anyway.
I booted into my TWRP and went to flash DarkKnights ROM..this ROM was something like 1.7 GB i think and after completely wiping the device (System, data and cache) i proceeded to flash the new rom..However it flashed very very quickly which i found strange but proceeded to restarting my device.
After that my phone has been completely dead!
What i think happened is that the EXTERNAL SD malfunctioned during the installation and im left with absolutely nothing on my phone.
I cannot enter recovery or download mode!
The only sign of life is when i plug it into my computer and it installs a driver that is the androidnet driver not the qualcom driver that some people have had and fixed.
I am open to any suggestions as you truly are my last resort.

Haven't really got much to say in the way of helping you mate, sounds like you're in a real Pickle :/
I'm sure someone here has a solution, there'd surely be SOME way to resolve it, we've got some pretty talented devs that do some amazing stuff so someone should be able to help ya somewhere.
All the best man, if you need help we're here

Look at here : http://forum.xda-developers.com/sprint-lg-g3/help/bricked-ls990-access-recovery-download-t3053985/post60106965#post60106965
try fastboot mode.
For that install this : http://forum.xda-developers.com/showthread.php?t=2588979&nocache=1
after you can apply fastboot commands
If you want to find custom recovery, flash kitkat aboot, kitkat laf and twrp recovery
you can have all this files in this post : http://forum.xda-developers.com/lg-g3/general/d855-one-click-root-twrp-recovery-t3072767/post59895642#post59895642
Download the script and extract it. In the folder there are all files (aboot, laf and recovery)
But of course , the fastboot command has to work ...
After that you should find recovery and download mode

Fastboot doesnt work for D855...
You can try flashing the TOT file with the old LG Flash Tool but im doubtful it will work

Are you sure you have no recovery access by Power+Vol—

jac10000 said:
Look at here : http://forum.xda-developers.com/sprint-lg-g3/help/bricked-ls990-access-recovery-download-t3053985/post60106965#post60106965
try fastboot mode.
For that install this : http://forum.xda-developers.com/showthread.php?t=2588979&nocache=1
after you can apply fastboot commands
If you want to find custom recovery, flash kitkat aboot, kitkat laf and twrp recovery
you can have all this files in this post : http://forum.xda-developers.com/lg-g3/general/d855-one-click-root-twrp-recovery-t3072767/post59895642#post59895642
Download the script and extract it. In the folder there are all files (aboot, laf and recovery)
But of course , the fastboot command has to work ...
After that you should find recovery and download mode
Click to expand...
Click to collapse
I will try as soon as possible and let you know if anything happens!
itsbighead said:
Fastboot doesnt work for D855...
You can try flashing the TOT file with the old LG Flash Tool but im doubtful it will work
Click to expand...
Click to collapse
I will keep that in mind as well thank you!
jac10000 said:
Are you sure you have no recovery access by Power+Vol—
Click to expand...
Click to collapse
Yes im sure! my phone is completely dead and the only sign of life as i said is when the driver gets installed on the computer when i plug it in.. Thank you for your reply though.

Try LG mobile support tool (old version) : http://tool.xcdn.gdms.lge.com/client/app/B2CAppSetup.exe
Even if you have not download mode, you can try. Install the tool
Try to boot on download mode, you have error message
run LG mobile support tool
choose Additional functions then Upgrade of the recovery after error
At one moment the tool will say that there is not of g3 connected, reattempts starting in download mode or presses on the button to power. Try several times both.
If it work, the software is going to download the last one kdz available for your device and him(it) to fall in love by following
You can always try this solution, with a little luck ...

I have tried all your suggestions but i still have no luck..i tried the tot method as well and it comes up with an error message of 'download fails'..there must be some way to fix this!!im left with the driver AndroidNet being installed on the computer and a phone that cannot enter recovery or download mode. however i can hear the phone working on the inside if i listen closely..if you have any other suggestions please share!

Update:
I was playing around with the phone and when i plugged it into the computer the screen came on and showed me battery low..also the led light on top started flashing red as it does when the phone's battery is low..I dont know if this will help in finding a fix but im hopeful.. :/

HELP
PeterGeorgiou said:
Update:
I was playing around with the phone and when i plugged it into the computer the screen came on and showed me battery low..also the led light on top started flashing red as it does when the phone's battery is low..I dont know if this will help in finding a fix but im hopeful.. :/
Click to expand...
Click to collapse
What had you done to wake up the screen and led light.. plz let me know.. because i have the same situation like you before rite now.. Please i need your help ! thank you

li545044579 said:
What had you done to wake up the screen and led light.. plz let me know.. because i have the same situation like you before rite now.. Please i need your help ! thank you
Click to expand...
Click to collapse
Hello my friend..All i did was plug the wire into the computer and then into my phone..and because my battery was very low the screen turned on and showed me the battery low screen..then the led started flashing..and finally the phone switched off completely..Thankfully i have another battery to continue my testing and trying to fix it..but apart from that that happened with the battery im back to square one where my phone is completely dead again and the only response i get is the AndroidNet USB driver being installed on the computer.

PeterGeorgiou said:
Hi all, I come to you as my last resort.
I have spent hours on google trying to find a solution to my problem.
This is what happened.
I store my ROMS on an external SD and sometimes i get the error that it is being removed unexpectedly...sometimes..anyway.
I booted into my TWRP and went to flash DarkKnights ROM..this ROM was something like 1.7 GB i think and after completely wiping the device (System, data and cache) i proceeded to flash the new rom..However it flashed very very quickly which i found strange but proceeded to restarting my device.
After that my phone has been completely dead!
What i think happened is that the EXTERNAL SD malfunctioned during the installation and im left with absolutely nothing on my phone.
I cannot enter recovery or download mode!
The only sign of life is when i plug it into my computer and it installs a driver that is the androidnet driver not the qualcom driver that some people have had and fixed.
I am open to any suggestions as you truly are my last resort.
Click to expand...
Click to collapse
You could try this method :- http://forum.xda-developers.com/showthread.php?t=2831668
Make sure your Battery is charged and hope and pray your Phone will have USB Debugging enabled.
Good luck and tell us how you progress, if at all.....:fingers-crossed:....

Same Problem
PeterGeorgiou said:
Hello my friend..All i did was plug the wire into the computer and then into my phone..and because my battery was very low the screen turned on and showed me the battery low screen..then the led started flashing..and finally the phone switched off completely..Thankfully i have another battery to continue my testing and trying to fix it..but apart from that that happened with the battery im back to square one where my phone is completely dead again and the only response i get is the AndroidNet USB driver being installed on the computer.
Click to expand...
Click to collapse
Hi friend, yeah, that was low battery screen pop out. Doesn't help after you charge you phone. And also, i getting theLGE AndroidNet USB driver just like you. i still keep searching up for solution. Hope it can fix it as soon as possible. I am so thankful for your suggestion. Thank you

573v3 said:
You could try this method :- http://forum.xda-developers.com/showthread.php?t=2831668
Make sure your Battery is charged and hope and pray your Phone will have USB Debugging enabled.
Good luck and tell us how you progress, if at all.....:fingers-crossed:....
Click to expand...
Click to collapse
thank you for your post but the link is dead..also my phone cannot be recognized in order to use fasttboot. :/

HI, friend, have you find any solution yet.. ? i tried, but still cant fine one. Hope people can upload a solution to solve that.

li545044579 said:
HI, friend, have you find any solution yet.. ? i tried, but still cant fine one. Hope people can upload a solution to solve that.
Click to expand...
Click to collapse
Nothing yet..im still searching and trying every possible method there is but no luck

PeterGeorgiou said:
Nothing yet..im still searching and trying every possible method there is but no luck
Click to expand...
Click to collapse
You can explore this solution : http://forum.xda-developers.com/showthread.php?t=2582142
It's for the G2 but can be adaptable for G3 ...

jac10000 said:
You can explore this solution : http://forum.xda-developers.com/showthread.php?t=2582142
It's for the G2 but can be adaptable for G3 ...
Click to expand...
Click to collapse
Don't get it with >>>>Open terminal in ubuntu then type: do i open terminal in computer or in the phone. If open in the phone, its impossible because the problem we had right now is when we connect the phone with PC, the only thing show up on computer is LGE AndroidNet USB Serial Port. but our phone screen still off even the system is boot in.

jac10000 said:
You can explore this solution : http://forum.xda-developers.com/showthread.php?t=2582142
It's for the G2 but can be adaptable for G3 ...
Click to expand...
Click to collapse
Thank you very much for the thread you posted..i tried it but the thing is..my phone has literally nothing on it so when i put each file manually into the phone i dont know which sdb to put it through to..as the thread says it should give a lost of all the system partition files but since my one doesnt have anything on the phone it does not find them...
However, i did manage to establish a connection between the phone and the terminal in linux so im thinking maybe i have to flash each file manually that i can get from a system dump of a g3 and maybe thay will work..what do you think??

PeterGeorgiou said:
Thank you very much for the thread you posted..i tried it but the thing is..my phone has literally nothing on it so when i put each file manually into the phone i dont know which sdb to put it through to..as the thread says it should give a lost of all the system partition files but since my one doesnt have anything on the phone it does not find them...
However, i did manage to establish a connection between the phone and the terminal in linux so im thinking maybe i have to flash each file manually that i can get from a system dump of a g3 and maybe thay will work..what do you think??
Click to expand...
Click to collapse
Here the same method on Windows : http://forum.xda-developers.com/lg-g2/general/choise-unbrick-qhsusbbulk-qualcomm-9006-t3093844
Yes if you can establish a connection between the phone with the Terminal (linux) or AOMEI Partition Assistant (windows) , you can flash the partitions (aboot, boot, laf) to have after download mode and then apply a kdz
other method ... http://forum.xda-developers.com/lg-g3/general/unbrick-lg-g3-qhsusbbulk-qualcomm-9008-t3072091
and can be ... : http://forum.xda-developers.com/lg-g2/general/lg-g2-unbrickable-fix-real-hard-brick-t2904404

LG G3 dead. Black screen. No booting. Help????

Hi,
I tried to install a custom rom on my LG G3 d858hk model. I was in twrp recovery and trying to install rom. Suddenly the phone got stuck. I waited for some time and then pulled the battery out and reinserted it. But still no light etc. Even nothing happens when I plug in charger. Looks like its completely dead. Any body any idea, how can i recover it from the black screen.
Regards,
Khurram.

http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 follow this guide just download ure files

Hi. am facing the same issue. Is there any other way to fix it, that doesn't include opening up the phone?

antony990 said:
Hi. am facing the same issue. Is there any other way to fix it, that doesn't include opening up the phone?
Click to expand...
Click to collapse
Do you have a warranty for you phone ? do you tried to download mode, fastboot mode and not working? In case the phone is completely dead, I can suggest you the option boarddiag (open phone) and jtag.

cesarandres_8911 said:
Do you have a warranty for you phone ? do you tried to download mode, fastboot mode and not working? In case the phone is completely dead, I can suggest you the option boarddiag (open phone) and jtag.
Click to expand...
Click to collapse
Yes I have a warranty. But I had installed a custom ROM (cloudy g3), so I guess that violates mine. The phone is dead, and shows up in device manager as LGE AndroidNet USB Serial Port. Don't even know why its showing up like that
Okay, am i'm searching for any available software fix that's gonna work for me at least before I resort to opening up the phone
Let me shed some light on what caused my phone to go dark, to save someone else from repeating the same mistake... I was trying to upgrade twrp from version 2.8 to 3.0. I thought using autorec would help me achieve that. But once it had finished, I attempted to boot to recovery and since then my phone has gone completely dark

OK, you could try to carry the cellphone to LG support and you can tell that after an upgrade, your phone has not returned to turn on. Usually, they change the motherboard. If you want to do it through BoardDiag, here is an explanation:
http://forum.xda-developers.com/showpost.php?p=65003040&postcount=300

cesarandres_8911 said:
OK, you could try to carry the cellphone to LG support and you can tell that after an upgrade, your phone has not returned to turn on. Usually, they change the motherboard. If you want to do it through BoardDiag, here is an explanation:
http://forum.xda-developers.com/showpost.php?p=65003040&postcount=300[/url]
Click to expand...
Click to collapse
Thanks for your help. Ive been able to get my phone to 9008 mode. So, am getting the part where I have to use the boarddiag tool, but am abit confused. What should be the value of my target dir, and AP chipset?. For the chipset, i'm thinking I should use the value that's similar to the one at this guide
http://forum.xda-developers.com/spr....
My phone is an LG g3 d855, so please guide

antony990 said:
Thanks for your help. Ive been able to get my phone to 9008 mode. So, am getting the part where I have to use the boarddiag tool, but am abit confused. What should be the value of my target dir, and AP chipset?. For the chipset, i'm thinking I should use the value that's similar to the one at this guide
http://forum.xda-developers.com/spr...and "TARGET DIR" should be the same location.
Click to expand...
Click to collapse

cesarandres_8911 said:
The first thing you should do is download the .tot file corresponding to your Variant (D855), I think that you can find it here: http://forum.xda-developers.com/lg-g3/help/tot-dll-file-d855-t2859828
Follow this guide to use boarddiag:
http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
In the "Image EXTRACTION" sections, in "BIN" must locate the file .tot that you downloaded.
In "DIR" you put the location where will be extracted the content of the .tot file.
Note that "DIR" and "TARGET DIR" should be the same location.
Click to expand...
Click to collapse
Yes. Iam following the guide you provided. But am stuck at this error. Check the image attached

antony990 said:
Yes. Iam following the guide you provided. But am stuck at this error. Check the image attached
Click to expand...
Click to collapse
And then, every time I unplug the device and plug it back into the PC, the device ends up being undetected by windows, and I have to redo the shorting procedure again. Is this normal behaviour, or something is wrong??
Also, when I put the battery back, and plug the device, it shows up as LGE androidnet usb

Anyone explain to me what this means. Please check the image attached

antony990 said:
Anyone explain to me what this means. Please check the image attached
Click to expand...
Click to collapse
I have the same error, and have tried about everything including 4 different computers and OSs, different cables, different versions of BoardDiag 2.99a - 3.99c, and still the same error.

singingandroid said:
I have the same error, and have tried about everything including 4 different computers and OSs, different cables, different versions of BoardDiag 2.99a - 3.99c, and still the same error.
Click to expand...
Click to collapse
It could also mean your device isn't in EDL mode 9008.

TheMadScientist said:
It could also mean your device isn't in EDL mode 9008.
Click to expand...
Click to collapse
I believe I am in the right 9008 mode. Screenshot is attached.

singingandroid said:
I believe I am in the right 9008 mode. Screenshot is attached.
Click to expand...
Click to collapse
I had be not dealt with edl on LG in a long time been on Samsung for a while that being said i could suggest maybe be uninstall the current 9008 driver and try to find a different source or updated and or try other usb ports. We on s8 have a lot of issues with usb 3.0 ports on pc's

TheMadScientist said:
I had be not dealt with edl on LG in a long time been on Samsung for a while that being said i could suggest maybe be uninstall the current 9008 driver and try to find a different source or updated and or try other usb ports. We on s8 have a lot of issues with usb 3.0 ports on pc's
Click to expand...
Click to collapse
Yeah, I've tried pretty much everything, but thank you for the reply.

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?