Develop Bugs

[Q] DHD almost dead - only vibra tones and led.

Hi!
Sorry for my English but i use my whole life only German
I have a big problem (specially for me):
When I speak using DHD a few dew sweat are on my LCD.
I saw that Volume + button doesn't work, and I want to reset my phone.
When I reset him, hi didnt work :/
If I want to start it normaly - only power button:
Hi give a three (3) vibra tones, and orange led blink all time.
If I want to start him with Volume - and start button:
Hi give five (5) vibra tones, and green led shine all time.
Any idees? I haved ROM: ARDH 5.1.17.
I don't know what too do.
Please help...
Ps. LCD is still black, i have no Idee - meybe is broken becouse i talk when i have sweat on my head?

Can you access the bootloader? Hold the volume-down button down when you power the phone on.
Sent from my HTC Desire HD using XDA Premium App

I have no idee. If I start phone with Volume - and power, He only do 5 vibra tones and green led is stil shining.
LCD is all the time black.

Could be the volume buttons acting up. You could try this:
- Turn the phone on to whatever state it boots up to
- Follow this guide until you have done point 7.
leith51 said:
7. Type: "adb reboot bootloader"
The adb reboot bootloader will take the device directly to fastboot And I can confirm that this method works also with non Sense roms.
Click to expand...
Click to collapse
You can skip this part:
leith51 said:
5.Download the radio you want to use from the links above .Then Drag and drop radio.img you have downloaded in to radio flash folder.
Click to expand...
Click to collapse
I'm not telling you to flash a radio, but this way you can get to the bootloader without using the phone.
Report back how it worked out.

Hmmm.
If I turn phone on and plug to the PC:
"adb reboot bootloader"
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Click to expand...
Click to collapse
"adb devices"
List of devices attached
Click to expand...
Click to collapse
BUT!
If I take of battery, plug it again (battery) and I plug phone to the PC (PHONE IS OFF)
and if in command line:
adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT0A8RX00397 recovery
Click to expand...
Click to collapse
adb reboot bootloader
nothing
When i write adb reboot bootloader, on command line is nothing and my phone give 3 vibra tones and orange led is blinking

What happens if you write:
adb reboot recovery
instead?
Sent from my HTC Desire HD using XDA App

Nothing, when I write adb reboot recovery:
Phone vibring 3 times and orange led blinking...

If I use android commander i can see all folders on the phone.
In "boot" folder i have any files.
DHD have a partitions? Maybe boot partition is dead?
Any idees how too repair phone using Android Commander?
Btw. If I doo this steps:
C:\Program Files\Android\android-sdk\tools>fastboot update PD98IMG.zip
Whoops: didn't find expected signature
read_central_directory_entry failed
Ř▼▓ôŇ˝»Č▲\►É┐Ý+╚⌂Áޡ┐Ý◄°´ŽÂĚ5♥~6BAN∟◄♫¸´↨!JJł(☺⌂■'
Click to expand...
Click to collapse

Try to download an RUU and that should probably fix it. All you do is plug your phone into the computer and the compuer does the rest. Search around for an RUU, there will be a guide in the thread.

I can't.
My PC see pheone when phone is plugged in OFF mode.
When I turn phone ON, PC can't find drivers for Qualcomm CDMA...
And when I turn phone ON MY PC doesn't see nothing
Automatically when I start RUU upgrade procedure, program tell me that He can't find device :/

is it possible that you used ROM Manager to partition your SD Card?
I'm asking because CWM/ROM Manager sometimes causes bricks on some devices.

I don't think so.
I only install new ARDH 5.1.17 ROM using EXT4 script.
That's all.
And +/- 2/3 weeks later my phone is dead...
Propably i send DHD tomorrow to the service. It is passible that service know about ARDH, root etc.?

[Q] One x touch screen fail

Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.

bump

thebarran said:
Searched many places for my problem but cannot find it specifically and this forum seems to be more clued up than most so here goes.
One x screen started to occasionally freeze on unlock screen (volume buttons worked also the volume pop up came on so screen itself not frozen just couldnt touch input i presume) but would fix with either a full power down or a few presses of the top button. Over the course of a day or two this has progressed to virtually always freezing and finally to where i couldnt unfreeze it even after powering down.
Did a factory reset which did give me access to my phone again but still the problem persists.
From my research it could possibly be some sort of cache problem. Also noticed after factory reset with no apps or data installed, apart from the preinstalled ones, am using 4.7 gb of internal memory with only htc sense running. this seems excessive to me but never checked it before so not sure if this is about right. If not then the cache theory could be right.
So can anyone help me please.
Click to expand...
Click to collapse
Did you try RUU?

Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.

thebarran said:
Not rooted my phone so was hoping to find a fix without rooting in case i have to send it back.
Click to expand...
Click to collapse
Try following this:
http://forum.xda-developers.com/showthread.php?t=1859714
No need to root / unlock bootloader
EDIT: follow option 2

following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked

thebarran said:
following option 2 but stuck.
Make sure that USB debugging is enabled (Settings/Developer options). In order to determine which ruu file you require, boot your device into bootloader mode (Power off and then restart device by holding Power and Volume Down button together). Connect to pc via USB and check that device shows FASTBOOT USB on screen. Enter the following command in command prompt:
fastboot getvar version-main
But when i enter that in Command prompt i get fastboot is not recognised command etc using windows 8. Any help
Note: my phone is locked
Click to expand...
Click to collapse
Can you try running fastboot on a different OS? Windows XP/7, Ubuntu? Something else?
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?

davidk-il said:
EDIT: BTW, are you sure you are running the fastboot command from the fastboot folder?
Click to expand...
Click to collapse
not doing this what do you mean?

thebarran said:
not doing this what do you mean?
Click to expand...
Click to collapse
Navigate on your PC to the fastboot folder lets say "c:\fastboot".
Shift+right click on any blank place and choose open command window here(or something like that my OS is not in english now).
Try using fastboot commands .

ah nice works, thanks. stay with me in case i get stuck again.

thebarran said:
ah nice works, thanks. stay with me in case i get stuck again.
Click to expand...
Click to collapse
Sorry,
Gotta get some sleep =)
If after running RUU nothing changes take the phone to service.

more problems
Ran and installed the ruu but got an
error[152]:image update error
The ROM update utility cannot update your android phone.
Please get the correct ROM update utility and try again
But i have the correct version already 3.14.401.31 it just wont install and now my phone is stuck on a black screen with htc in centre and nothing else.

Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode

Mr Hofs said:
Did you run the ruu.exe as a administrator ?
Right click the ruu exe and select that.....and put the phone in the bootloader/fastboot usb mode
Click to expand...
Click to collapse
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle

thebarran said:
tried it in admin mode still no good and cant get to any other screen on my phone now other than the black screen with htc in the middle
Click to expand...
Click to collapse
Phone for sure in fastboot usb mode?

davidk-il said:
Phone for sure in fastboot usb mode?
Click to expand...
Click to collapse
it was when i first did it biut cannot check no more

Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights

Mr Hofs said:
Hold the power button and the volume - button together until it reboots and boots into the bootloader, hook the usb cable and you should see "fastboot usb" in red text. At that point you run the ruu with administrator rights
Click to expand...
Click to collapse
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.

thebarran said:
i cannot. all that happens now is that it powers down and comes back to the black htc screen. cannot get to boot screen anymore.
Click to expand...
Click to collapse
Try shutting of the phone, powering on when holding power button+volume down for about 8s.
You will get a hboot, choose fastboot connect usb cable and try ruu with admin permissions

finally did get to hboot screen by letting the phone shutdown itself but couldnt ruu as battery power to low so i powered down and recharged battery but back to square one where i cannot get to boot screen just constant black htc screen and cant power down again.
So ill let my battery run down again to power off completely open boot screen then stay on that til i power up enough to try ruu again.
Il let you know what happens when this is done later.

[Q] HTC Desire HD Bricked bootloader not loading and cannot connect to pc need help

Good day!
After searching everywhere in the web and using different methods, I decided to create an account and ask you guys how to solve my problem
Basically, I have a HTC Desire HD phone, this is unlocked, rooted and using cm-Jellytime_42_R11 ROM. I decided to change ROM and go back to Android Revolution. What I did first was I deleted a couple of folders in my clockwork folder, I deleted both backup to free space. Afterwards, I was trying to connect my phone to my laptop but to no avail (it only charged) then I decided to just boot into recovery. After a couple of tries trying to access and going to bootloader/recovery mode it just wont push through. So I decided to normal boot, then the phone won't boot anymore. It just hanged in the Jellytime loading screen.
Note: I removed the battery a couple of too many times since I was trying to boot into recovery.
Thanks in advance to anyone who can help me with this problem

I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?

Gussta said:
I didn't understand very well.
Can you now go to Hboot screen volume (-) + power button?
And where you get now stucked when you just power on phone?
Click to expand...
Click to collapse
no, i couldnt go to Hboot while holding down volume - and power.
The phone gets stucked in the Jellytime loading screen. It just stops. help me please

What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?

bananagranola said:
What does it do when you try to go to hboot? Is it detected in fastboot? Is it detected in adb when you try to boot normally?
Click to expand...
Click to collapse
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.

richardrip10 said:
it does nothing. It just cant go to hboot. it wont normal boot too. so stuck.
Click to expand...
Click to collapse
WHen it getts stuck in the roms boot animation, connect usb to the phone and try
Code:
adb devices
Most devices show up via adb during the boot animation.
If the device shows up there, enter
Code:
adb reboot bootloader
then go here and download 4ext recovery.
extract the .img file from the zip. Rename it to recovery.img and place it in your adb directory and enter this whiles in fastboot
Code:
fastboot devices
to make sure your device shows up
then
Code:
fastboot flash recovery recovery.img
after it has successfully flashed reboot to recovery ad try and flash the rom u want.
hope i helped. Click on the thanks buttton.
You can ask if you still have problems.

computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.

richardrip10 said:
computer doesn't recognize android. laptop doesnt even make sound that a device has been connected. I checked the device manager but to no avail. but the phone is charging.
Click to expand...
Click to collapse
What recovery were you using before this happened?

mickeyasamoah said:
What recovery were you using before this happened?
Click to expand...
Click to collapse
cwm sir.

richardrip10 said:
cwm sir.
Click to expand...
Click to collapse
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.

mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
sorry, it still didn't work. Is this a bricked phone?

mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
btw, my computer really cant detect my phone. It doesnt make any sound when it is connected through USB. but other devices can be detected by my computer. I tried inserting the usb into a 2.0 and 3.0 usb.

mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
hey bro, I actually made it work. problem is when im flashing the recovery, it shows Failed<remote: not allowed>
what should I do?

mickeyasamoah said:
I dont know if this is going to work with CWM but it works on TWRP and 4ext.
Remove the battery and re-insert it.
Now connect the usb to the device.
Dont press the power button.(leave it off)
After the the charging light comes on, the device should be discoverable by adb.
Now try
Code:
adb devices
It should be detected by adb.
Click to expand...
Click to collapse
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:

richardrip10 said:
no worries now brother! was able to fix my phone now! THANK YOU SO MUCH! :good::good::good:
Click to expand...
Click to collapse
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.

mickeyasamoah said:
Okay Brother.. Guess you should post how you fixed it in the OP so that others with the same problem can look it up.
Click to expand...
Click to collapse
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.

richardrip10 said:
Ok, so basically, the problem why i can't do the power button + vol (-) is that my volume buttons are broken. (sad) Second, the reason why my computer wasn't detecting my phone is that my phone's charging slot is dirty and I had to clean it with a needle to remove the dust, at the same time, the cable I was using was broken. When I was able to clean the slot and change cables, I then followed the steps by mickeyasamoah (thanks bro) with the adb procedures. Although it failed when it was in the flash recovery line (dunno why), I just proceeded into flashing a new ROM and voila, it worked.
Click to expand...
Click to collapse
I am happy i was able to help.
Instead of saying thanks only, you could actually hit the thanks button.
Have a nice day.

[Q] [Q ]!HELP! After RUU wildfire s can't boot

I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
I will pay 20 Euros, if someones solution works.

You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.

cortezthekiller said:
You might want to take a look at this.
http://forum.xda-developers.com/showthread.php?t=1622178
Hope that helps.
Click to expand...
Click to collapse
Thanks a lot, but i have already known this thread.
The guy, B3NJY, with same problem, could not solve it. At least he sent his phone to repair service.
Maybe someone else knows how to unbrick a softbricked wildfire s.?
I flashed a lot and know how to use fastboot etc., ....
Like i said, backlight is working but nothing else.

appyleptiker said:
I flashed a RUU for wildfire s, everything seems to be fine.
But after it finished and told me your phone will now restart............---------> only the screen turns on and off, on and off.
Nothing else. I cannot go into bootloader or start the phone, no htc logo... nothing =(
I pulled the battery and tried to restart the phone, restarting into bootloader, connecting to fastboot, flashing ruu again, but nothing worked.
No connection to pc at all and no signal on the phone. Only: background light turns on and off, turns on and off.
What can i do ?
Please help me.
I am happy for any replies.
Click to expand...
Click to collapse
I think you flash wrong RUU. Before flash RUU 100% confirm about it. Otherwise you will lost your device. Anyway let's begin...
[WARNING: PLEASE DON'T TRY THIS WITHOUT HAVING GOOD ENOUGH KNOWLEDGE !! BE SURE TO CHOOSE THE RIGHT RUU OR THIS MAY HARM/BRICK YOUR DEVICE !! I AM NOT RESPONSIBLE FOR ANYTHING !!]
Before you start, you will need to set up your computer to properly recognize the device. You probably did this when rooting originally, but just in case... Install SDK tools for Android, Java runtime, and HTC Sync (only for USB drivers). Make sure that HTC Sync is not running in the background when this process is ongoing. To kill that you can use "Task Manager in Windows"
:cyclops: Do step by step: :cyclops:
1. Download the correct RUU for your device from Here and please 100% confirm you are downloading right RUU for your device. Make sure you download a Marvel_C RUU for a CDMA device (no sim card) or a Marvel RUU for a GSM device (uses a sim card)!! Also make sure you get the correct RUU for your carrier.
2. Charge the battery above 80%. If the battery dies during the flashing process, you could hard brick the phone!
3. Run the RUU until the wizard comes up (step 1). While the RUU wizard is open, don't do anything. Just find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Copy that and keep it on another location. Close the RUU wizard.
Now, open ROM.zip with 7zip and extract "System, Boot and recovery img's" [.img file/s]. Put it in the location were you've installed Android SDK tools.
4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.
5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Flash the stock recovery, boot, system img's using the following command/s:
step by step
For recovery
Code:
fastboot flash recovery recovery.img
For boot
Code:
fastboot flash boot boot.img
For system
Code:
fastboot flash system system.img
Now go back to device recovery and DO FACTORY RESET and reboot your device.
If everything done perfectly then the phone will booted normally on STOCK ROM! Remember Now bootloader is UNLOCKED but NOT rooted. Don't worry, you can root your device and also install CWM as before.
Hope this method will solve your issue.

Thank you very much testmasterbd =) , for this excellent description.
But..... i can`t start my phone into the bootloader. The phone turns on (only seeing the backlight) and suddenly it turns off (again the backlight). It does this ever and ever again until i pull out the battery . =(
how can i get into the bootloader? volume down and power doesn`t work anymore.
Maybe i can connect the phone to the pc, not via usb but via other contacts. Or is there another way to get the phone into fastboot mode?

Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?

testmasterbd said:
Try this
Remove and reinsert the battery [don't press the power button of your device, that's means device should be turned off]
Plug it into a computer via USB cable
Wait and see if the computer detects it
If it does, then - Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools.
Code:
adb devices
See if it shows up or not.
I am not sure about your device get hard brick.
---------- Post added at 10:30 PM ---------- Previous post was at 10:12 PM ----------
I forgot to ask one thing :silly:
Did your device vibrate when you pressed the power button for normal boot?
Click to expand...
Click to collapse
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day

appyleptiker said:
You are very friendly.
But i cannot power off the phone. It turns only off if i remove battery =)
When i plug in the usb cable while the phone is off, after some seconds, it turns on - shows its backgound light - and turns off and again on, like a turn signal. no vibration at all.
When i type in windows command adb devices it shows:
C:\android>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
but no device is listed =(
so it should be hard bricked!?
Damn it.
thanks a lot for your help and wasted time.
i am sorry
have a nice day
Click to expand...
Click to collapse
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck

testmasterbd said:
If it is then, you need an expert who is capable for JTAG repairs. So find someone in your place. You can get an idea from HERE.
Good luck
Click to expand...
Click to collapse
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:

appyleptiker said:
Yeah, thanks a lot.:good: Luck is what i need. But i don`t think that it will be too easy to repair. :silly:
Click to expand...
Click to collapse
It is don't be frustrated

Accidentally installed cloudy for a G2 on my G3. Stuck in Fastboot

Now my phone thinks it's a D800. I was able to get into download mode and tried using LG Flashtool. I used the 850 dll and .tot but got an error.
Download Fail!
Device model is different.
Check phone or dll.
I read something about using a modified .dll but cant find more info on it. Feeling pretty stupid for possibly ruining a $400 device with such an idiotic mistake. Any advice you guys can give me is truly appreciated.
Thanks Guys

Muuust said:
Now my phone thinks it's a D800. I was able to get into download mode and tried using LG Flashtool. I used the 850 dll and .tot but got an error.
Download Fail!
Device model is different.
Check phone or dll.
I read something about using a modified .dll but cant find more info on it. Feeling pretty stupid for possibly ruining a $400 device with such an idiotic mistake. Any advice you guys can give me is truly appreciated.
Thanks Guys
Click to expand...
Click to collapse
I had a similar issue but it was my d800 lg g2, i flashed a diferent rom by accident that wasn't made for the phone. I'm assuming you tried twrp and it didn't let you enter it?

theinspector said:
I had a similar issue but it was my d800 lg g2, i flashed a diferent rom by accident that wasn't made for the phone. I'm assuming you tried twrp and it didn't let you enter it?
Click to expand...
Click to collapse
Sorry if this is an absolutely stupid question, but you can get into twrp from download mode? I had an app that rebooted into twrp, that's the way I did it. Sorry for the noob answers, I'm completely new to rooting.

Muuust said:
Sorry if this is an absolutely stupid question, but you can get into twrp from download mode? I had an app that rebooted into twrp, that's the way I did it. Sorry for the noob answers, I'm completely new to rooting.
Click to expand...
Click to collapse
If you pull the battery so the phone is full powered off, press and hold the volume down button, and the power button down at the same time until you see the LG logo, then release just the power button, keep holding the volume down button, and then quickly press power and hold it again, you will be brought to a factory reset page, that tells you it will wipe all your data, don't worry about it, nothing will wipe, scroll down with the volume key to the yes button, hit power to accept it, it will ask you to confirm it, hit power twice and it should boot into twrp. If it boots into twrp, like it should, then you can either sideload a rom, flash an existing one you have on the phone, or hopefully you have made a twrp backup of your previous rom to restore. If instead of going into twrp, it puts you back into fastboot or download mode after agreeing to the factory reset, then there is a few more things to try.

theinspector said:
If you pull the battery so the phone is full powered off, press and hold the volume down button, and the power button down at the same time until you see the LG logo, then release just the power button, keep holding the volume down button, and then quickly press power and hold it again, you will be brought to a factory reset page, that tells you it will wipe all your data, don't worry about it, nothing will wipe, scroll down with the volume key to the yes button, hit power to accept it, it will ask you to confirm it, hit power twice and it should boot into twrp.
Click to expand...
Click to collapse
ok ya, I tried that earlier. It takes me back into download mode after I confirm yes with the volume buttons.

Muuust said:
ok ya, I tried that earlier. It takes me back into download mode after I confirm yes with the volume buttons.
Click to expand...
Click to collapse
Have you tried using the fastboot boot command from your computer, to boot into twrp?

theinspector said:
Have you tried using the fastboot boot command from your computer, to boot into twrp?
Click to expand...
Click to collapse
My G3 shows up in Device Manager under Portable Devices for about 40 seconds, then it gets a yellow triangle and says "This device cannot start. (code 10)"
It doesn't show up in "Computer" where all the HDD and other devices show up. So I can't access it.

theinspector said:
Have you tried using the fastboot boot command from your computer, to boot into twrp?
Click to expand...
Click to collapse
Did a little searching and I'm trying to install ADB right now. That's what I need right?

theinspector said:
Have you tried using the fastboot boot command from your computer, to boot into twrp?
Click to expand...
Click to collapse
In cmd I entered adb devices and got back "List of devices attached" but my phone doesn't show up here either.

Muuust said:
In cmd I entered adb devices and got back "List of devices attached" but my phone doesn't show up here either.
Click to expand...
Click to collapse
You'll want to get the fastboot drivers, not just the adb drivers. Under device manager after you get the fastboot drivers installed, makes sure the Windows device manager shows your device, and replace the default installed driver for it with the new fastboot one you installed, open a command window with cmd, and search for "fastboot devices" and it should show a long number come back under that list now.
Also, if your computer shows the device for a short period before it disappears, you may have to go into your computers settings to disable auto-driver install, then you can just manually choose the fastboot drivers.

theinspector said:
You'll want to get the fastboot drivers, not just the adb drivers. Under device manager after you get the fastboot drivers installed, makes sure the Windows device manager shows your device, and replace the default installed driver for it with the new fastboot one you installed, open a command window with cmd, and search for "fastboot devices" and it should show a long number come back under that list now.
Also, if your computer shows the device for a short period before it disappears, you may have to go into your computers settings to disable auto-driver install, then you can just manually choose the fastboot drivers.
Click to expand...
Click to collapse
I gotta head to work soon so it'll probably be a bit before I get back to you. But I sincerely want thank you for taking time to help me out. Truly appreciate it.

Muuust said:
I gotta head to work soon so it'll probably be a bit before I get back to you. But I sincerely want thank you for taking time to help me out. Truly appreciate it.
Click to expand...
Click to collapse
Yeah it is no problem, i remember having this same issue and couldn't find a whole lot of information on the issue, so I'm glad to help.

fastboot
I was stuck on fastboot yesterday, used fastboot boot laf.img to go back to download mode and then used lgflashtool to flash a new rom.

unspokenname said:
I was stuck on fastboot yesterday, used fastboot boot laf.img to go back to download mode and then used lgflashtool to flash a new rom.
Click to expand...
Click to collapse
I'm stuck in download mode now. And I cant use the LGFlashtool because my g3 comes up as a G2 in Flashtool. So when I choose the D850 dll and tot, I get an error saying it's the wrong model.

Muuust said:
I'm stuck in download mode now. And I cant use the LGFlashtool because my g3 comes up as a G2 in Flashtool. So when I choose the D850 dll and tot, I get an error saying it's the wrong model.
Click to expand...
Click to collapse
For me, flashtool is incredibly finicky and it takes me many different tries to make it work properly, i would try downloading the latest twrp for your G3, and extract from the .zip file the recovery.img and then try to fastboot boot that recovery to your device like i have previously explained. If that does not work for you, and flashtool does not then you can use fastboot flash commands and flash each of the partitions of your phones stock rom.

theinspector said:
You'll want to get the fastboot drivers, not just the adb drivers. Under device manager after you get the fastboot drivers installed, makes sure the Windows device manager shows your device, and replace the default installed driver for it with the new fastboot one you installed, open a command window with cmd, and search for "fastboot devices" and it should show a long number come back under that list now.
Also, if your computer shows the device for a short period before it disappears, you may have to go into your computers settings to disable auto-driver install, then you can just manually choose the fastboot drivers.
Click to expand...
Click to collapse
After some searching it looks like you can't disable auto driver install in windows 7 Premium. When I uninstalled the driver and plugged the phone back in, I get "Device driver was not successfully installed" In that window, I choose "change settings" and choose "Never install driver software from windows update", but it does anyway. When I go to update driver--> Browse my computer for driver software-->I choose my folder with the fastboot drivers, I get "The best diver software for your device is already installed". Now my phone comes up as LGE Android Net MTP Device, it doesn't show as G3 anymore. Also when I enter fastboot devices in cmd I get 'fastboot' is not recognized as an internal or external command, operable program or batch file. No matter what i do, my phone goes to the Firmware Update screen with the USB symbol on it. IN the small box below the progress bar, it reads: User 50.0 AS0.0 B40 UHS
S U LG-800 04.4.2 Hrev_10
CloudyG2 2.2
I don't know if this is helpful at all.

Pm me, also it would be helpful if to have team viewer so that I can help you.
Sent from my LG-D800 using XDA Free mobile app