Develop Bugs

[Q] HTC Desire Stuck at Why so serious?

hi i have used evo3 on my htc desire to root and then used alpharev and boht said succussfull. Now phone starts and only shoes joker and written why so serious? doesnt go further at all. any help please
Regards

got a bootloop.. try running an RUU file (this will flash back to stack, get rid of root)
then try to root again, just a different method?
hope this helps!

how to flash with ruu if your phone is stuck not even being detected by PC. any detail please thanks regards

faisal_sherry said:
how to flash with ruu if your phone is stuck not even being detected by PC. any detail please thanks regards
Click to expand...
Click to collapse
First of all: be sure you know what you're doing. The below listed solutions might help but might also end up bricking your phone dead.
If you can enter fastboot (back while powering on the phone) and if you have a nandroid backup, you can try to flash it back using the fastboot flash command.
OR
It's possible to run the RUU update while in fastboot or hboot usb mode (back button while powering on the phone) I had the modified usb drivers installed http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install, not sure if that is needed - but the original drivers didn't work very well with my setup in general: Win7 x64 , also I uninstalled HTC Sync.
OR
If that fails, you can try to extract the rom.zip from the RUU and flash it manually (help on extracting http://lukasz.szmit.eu/2010/04/extracting-rom-files-from-htc-android.html ) JUST DON'T USE THE ROM FROM THAT TUTORIAL, THE LINK IS JUST FOR REFERENCE ON HOW TO EXTRACT THE rom.zip
The offcial RUU are in this thread, just BE SURE TO USE THE CORRECT ONE http://forum.xda-developers.com/showthread.php?t=695667
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip rom.zip

@quanchi, thanks for your help i'll try and let you know tomorrow thanks again
Regards

hi i have tried the method putting phone in fastboot mode pressing back and power phone was detected and then flashed with this rom 'RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed'' and it was successufll now my phone is not turning on when i press power it vibrates but nothing on the screen but good thing is when i connect the phone with pc it still detects it its not brick yet i think any help
Regards

faisal_sherry said:
hi i have tried the method putting phone in fastboot mode pressing back and power phone was detected and then flashed with this rom 'RUU_Bravo_TMO_UK_1.21.110.4_Radio_32.36.00.28U_4.06.00.02_2_release_127570_signed'' and it was successufll now my phone is not turning on when i press power it vibrates but nothing on the screen but good thing is when i connect the phone with pc it still detects it its not brick yet i think any help
Regards
Click to expand...
Click to collapse
Is your phone SLCD? I reckon you may have flashed an incorrect RUU, in which case you'll need to get a more up-to-date one and flash it again. In case that's the most recent one for T-Mobile, you'll need to make a gold card and then flash a generic RUU. Hope that helps.

hi thanks for your reply i don't know what is slcd? and let me tell you the stat of the phone now
when i press power phone vibrates i can see button lights on the phone but nothing on the lcd screed. Phone is not going in boot mode when i press back and power nothing happens, volume up and power nothing happens. Phone is being recognized in device manager as a usb mass storage and i can see battery light on the top of the screen as well. I dont know what is the real state of my phone and what do you call it but its a t mobile UK phone that's what i know and what should i do now thanks
Regards

SLCD is a type of display present in some Desires, earliest Desires had an AMOLED display. You most probably flashed your SLCD Desire with RUU prepared for an AMOLED Desire, hence the display problems. Search the forum for "SLCD BRICK". Your phone should be able to enter fastboot/hboot, but doesn't display anything because the display handling is screwed up. Before trying to resolve your situation BE SURE TO READ ALL THE INFO ON SLCD UNBRICKING.
I have no experience with SLCD models so can't help you much on the subject, but there are numerous threads on xda detailing dealing with this particular issue.
I don't want to sound rude or holier than thou (as I had my share of bricks and semi bricks) but I did write that you should make sure you get the correct RRU...
best of luck
Sent from my HTC Desire using XDA App

hi thanks for your reply i'll try n post the result here
Regards

So here I will describe what I did to solve the exact same issue.
Remove the battery from the phone
Copy the proper RUU file to the root of my SD card naming it PB99IMG.zip
Insert battery
Power on phone holding the power and the back buttons until the fastboot menu opens
Choose recovery
Then it will go through a bunch of stuff and ask you if you want to flash the file you put on the SD card, I said yes then a few minutes later Bobs your uncle I was back to factory.

faisal_sherry said:
hi thanks for your reply i'll try n post the result here
Regards
Click to expand...
Click to collapse
Faisal, it seems apparent that your device is an SLCD Desire. When you put Alpharev on it, it did S-OFF and your boot got corrupted for some reason and looped. When you ran the RUU (which was incompatible for your SLCD, and actually meant for an AMOLED Desire), you effectively unrooted it, though not restoring it.
Check my thread for a similiar problem.
If you had made a Goldcard earlier, you're in luck. You can restore your device with a generic SLCD RUU available for your device, by either running the RUU or by flashing the rom.zip from the RUU.exe file (Tip. This file gets extracted to %TEMP% folder when you run an RUU)
Things you need to know before you try solving your problem:
Know how to use adb from the command prompt,
Search for the links to shipped-roms site containing the list of Bravo (Desire) ROMS
How to create and use a goldcard
How to navigate to the temporary folder of your Windows PC
How to turn your device on into Recovery mode and Fastboot without seeing the screen
Simple search on XDA can unravel these simple mysteries.
Now, the steps to go about solving your problem:
Find out if you have a generic unbranded HTC Desire, or a branded one. A branded Desire has a special Code which prevents you from flashing a ROM meant for any other brand and also blocks a Generic RUU. If you're from India, it is branded with HTC Asia_India. If you're unbranded, things are looking much easier for you, as generic RUUs for SLCD are easily available.
Check if you have a goldcard (A goldcard is a special microsd card you made while your device was in working condition. It will allow you to restore your device using a generic RUU or an OTA)
If you dont have a goldcard, you might try to see if Recovery can be booted up. Poweroff phone, then power it on by pressing Vol- and Poweron key, then wait 30sec and press Vol Down and Poweron button again. At this time, phone gets detected in Windows (as shown by the icon in the bottom right of taskbar and a notification sound.
Type:
Code:
adb devices
If this displays a code SH**** after "List of devices", you're in luck. You can issue an adb command and get a CID of your device, following which you can create a goldcard.
After creating a goldcard, it will allow you to run a generic SLCD RUU. Check my thread for a latest RUU.
If you dont have a goldcard, and adb doesnt show the device in Recovery mode, it means Recovery is corrupted too. In this case, Power off device. Then Poweron by pressing Back key and Power on key. Again try adb devices command. If it shows the device, follow the steps of previous step.
You can also create a goldcard by putting your microsd card into a friend's phone and following the steps needed to create a gold card
If adb doesnt show your device in either Fastboot (previous step) or in Recovery, then you're in trouble. The only way to unbrick your softbricked device is to get a Generic RUU for your device (Check shipped roms site, or search XDA), and flash it. There is also a method if you have the original OTA zip for your device. Check teppic74's posts on XDA for this method.
If you have an Indian Desire, you're done for as I found out. If you dont have a goldcard for an Indian Desire, or the OTA zip, you have no option than to return it to HTC. Dont worry about Warranty being lost if it is a new phone. HTC has to repair it according to their Warranty policy.
Goodluck. I've summarized all methods available to unbrick an SLCD. For more details on any one method, try searching with the appropriate keywords from my post. It's all on XDA.

@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
"switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery."
pc detects the phone but when i run ruu it doesn't find the phone and i have OTA downloaded as well and i have copied to micro sd but i dont know how to use this OTA. i'm sorry for being very basic
Regards

faisal_sherry said:
@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
"switch off phone. press and hold volume down. press power. release volume down after 5 seconds. wait for 30 seconds. press volume down. press power. the phone should vibrate. wait 40 seconds. the phone should be in recovery."
pc detects the phone but when i run ruu it doesn't find the phone and i have OTA downloaded as well and i have copied to micro sd but i dont know how to use this OTA. i'm sorry for being very basic
Regards
Click to expand...
Click to collapse
@Faisal,
No prob. Everyone is a newbie at the beginning!
But, you need to search and find out some things on XDA, and there are a lot of newbie centric guides over here which explain procedures step by step..
You need to do these by yourself though:
1. Install Android SDK. It just involves downloading the setup file, running it, and finding out where in Windows it has been installed. In the main installation folder, there is a Folder called Tools. You need to open a command prompt in that folder and run adb.exe for most of the procedures. Follow this guide to install the SDK.
2. After you have the sdk installed, boot your phone into recovery using the procedure you quoted. As you said, the phone will be detected in Windows. At this point, run the following command from a command prompt in your tools folder.
Code:
adb devices
This will output "List of devices" followed by a code starting with SH. If it does, you're in luck. You can now create a goldcard, and proceed. Follow this guide for this.
3. If the "adb devices" does not show any devices (in recovery/Boot mode), and you dont have a goldcard, you've run out of luck, pal. Honestly, no one on any forum has solved the issue with this combo.
There would still be a solution, if you have the RUU. I dont see why your RUU does not run. Try to run it in one of the following modes.
a. Switch off phone
Switch it on by pressing Back key followed by Back+Power key, then slowly releasing Powerkey while keeping Back key. This is the bootloader mode.
b. Recovery mode. Power off, power on by Vol down + Power key, then slowly release Power key. After 30 sec, press Vol down once, then power key once. Wait 1 min and see if pc detects device. Else press power key once again.
In either of these modes, the RUU you downloaded should down. If it is the incorrect RUU for your location, it will give a customer id error. If it has an incorrect bootloader version, it will show a Bootloader version error. In either of these cases, try the newest generic SLCD RUU from shipped roms. If this still gives one of the above errors, your phone is a branded phone. In this case, you WILL NEED a gold card to work.
Note that if adb devices shows your phone, then you can create a goldcard at this point.
If adb does not show your devices, and the latest generic RUU does not run, and you cant find a correct RUU for your device, then tough luck. I am yet to find a solution to this problem. Return it to HTC.

faisal_sherry said:
@droidzone, hi thanks for your time and reply here. the thing is i am very very basic user. Can you please tell me do i have to install htc sync first and i dont have any gold card before rooting. after following this procedure
Click to expand...
Click to collapse
Yes, you need to have HTC sync installed for the drivers. But the HTC sync main program should not remain in the system tray (bottom right). If it is, close it by rightclicking and Exiting.
The problem with what devin mm said is that an SLCD desire doesnt show anything on screen if bricked. Yet, recovery may be selectable for some, without seeing anything. But if you ran the RUU, then most probably the recovery itself is corrupted and selecting a zip file on memory card wont be possible at this point.
Sorry that I wont be able to follow this thread for the next few days. I'm travelling, and since my Desire is with HTC repair centre, no Net. Hopefully, someone else on XDA can help out with any more qns..

Note 2 N7100 - broken android out of thin air/ no solution

Hello guys,
I've got a problem, I cannot find solution to. I've been stuck on this since like 8 hours.
I was watching a movie, when my note 2 turn off and it won't boot again. There is this white galaxy note 2 screen and then nothing happens. When I charge the phone, there is empty battery screen (no signal of battery being charged, but yet the phone is on when I try working with Odin, so I believe it's charging).
I've entered recovery mode but I cannot do anything there, all processes are in red font, wipin out data is impossible, recovery is not possible too. Nothing can be done succesfully.
I cannot connect to kies, even when the recovery downloading is possible, then there is this final screen saying kies was unable to connect to the phone, but I can connect to odin, but still I got "nand write start!" resulting in "fail!" and once I got "can't open the serial (com) port..
What should I do? It doesn't matter for me, which system version I work on, I just want my phone working.
Thanks for any help, I can make a photo using my second phone (old HTC).

If you are able to push files via Odin....there is hope....to include a PIT partitioning of the device again.
If no Odin or KIES....it's not good...
Sounds like partition damage or EMMC failure....g

gregsarg said:
If you are able to push files via Odin....there is hope....to include a PIT partitioning of the device again.
If no Odin or KIES....it's not good...
Sounds like partition damage or EMMC failure....g
Click to expand...
Click to collapse
cannot do pit partitioning.
A serviceman told me that there is no hope. I can repair it for 60 bucks (central europe prices) but no guarantee. I'm gonna buy a new phone then. Thanks for a reply.

accidentally format bootloader

I accidentally formatted bootloader, and now my device unable to detect,boot or anything. Is there anything I can do of ?
(might try everything to work it out )

Can you boot into the preloader with volume up and power pressed?

flash ROM via FlashTool

BlueFlame4 said:
Can you boot into the preloader with volume up and power pressed?
Click to expand...
Click to collapse
no, i could not

Kittehdispenser said:
no, i could not
Click to expand...
Click to collapse
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?

BlueFlame4 said:
Sounds like a hard brick, which means your phone is destroyed. What exactly did you do?
Click to expand...
Click to collapse
welp, i tried to install custom rom ( which need to download the rar and paste it into INTERNAL) but i accidentally paste it to my SD card. Then i start to install it.
Then i said it's uninstallable, I just restart my phone and everthing went normal buy my wallpaper screen turns black and unable to read it tho USB ( Just the standby screen shows wallpaper)
Then my brothers came out and said that all you need to do is format it again and reinstall. We tired countless times . But then it have another option which above Format everything but not bootloader and another is Format everything and bootloader.
Then my bro press it and ... It became bricked.
it's still warrantyable so .. I plan to play dumb to the warranty company if I can't fix it.
( even if i play dumb idk what reason I need to come off, if i say yesterday the battery from 70% drop to 0% then it unable to open again )
PS: before this happen my battery happens from 70% drop to 0%, after charged. it's fine
PPS: give me a good excuses to play dumb C::

Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what you've done? I'm pretty sure you're missing something.

Soft Bricked HTC Desire 616
BlueFlame4 said:
Wait, wait. How did you format the bootloader? No recovery should have this option! The only possible option to hard brick the P8000 is to pull out the USB cable in the exact moment when the SPFlash Tool writes it. So, can you elaborate a bit more about what done? I'm pretty sure you're missing something.
Click to expand...
Click to collapse
Hi,
I did something similar with my HTC Desire 616. I choose "Format All + Download" option with SP Flash Tool. The phone soft bricked. Later I tried "format whole flash (including bootloader)". It's still soft bricked...
Is there a way to revive my phone back??? :crying:

I had the same problem - but it is possible to set the phone to a special bootloader mode called META mode - see this video: https://www.youtube.com/watch?v=A3TmXtOA0IA
To do so you have to open the phone and disconnect the battery. You can find a howto easily on youtube.
Then set up everything to flash the phone (SP-Flashtool, scatter file, etc.) and push the volume down button while connecting the phone to the computer. This switches the phone to META mode, the computer can recognize the phone, installs the preloader driver and finally flashes the phone
Maybe you have to do the procedure twice because on the first connection only the preloader driver will be installed.
This worked for my P8000(B) which I treated with SP-Flash Tool and "Format All + download"
Be aware that you formatted the NVRAM and lost your IMEI's

FrauHofrat said:
P8000(B)
Click to expand...
Click to collapse
What the meaning of (B)? Just asking because i have (W)

Tecno spark 3 pro clone flash file mt6570 android 9.0 firmware
Hi
I need your assistance, please help me find the firmware for the above phone. I recently tried to flash it with a Spark 3 clone firmware i got online but it gives an error STATUS_PARTITION_NOT_FOUND and also i accidentally formatted the bootloader on SP Flash Tool so the phone is a brick, it can't charge, and it can't turn on. I have screenshots of the About section when the phone was working, which contains the phone's features model and build but on opening the back cover of the device, i realized its a clone phone and i cannot determine its real model to get the exact right flash file.
Thanks

Lg g4 h815 bricked! Qualcomm 9008

My phone is bricked,when i connect it to pc its show in device manager Qualcomm 9008 mode.How to unbrick it!
Best regards! :crying::crying:

Dzeki064 said:
My phone is bricked,when i connect it to pc its show in device manager Qualcomm 9008 mode.How to unbrick it!
Best regards! :crying::crying:
Click to expand...
Click to collapse
same here

try if you have warranty.. or try jtag box.. there isnt a way to fix this yet.. funnt thing on G2 shortening a circuit brings back to life..

there's no way to fix it? really o,O

I wrote a guide a few months ago for the Lg G3, isn't it possible to use it with the right DLlL and TOT/KDZ file?
https://open-freax.fr/guide-unbrick-your-lg-g3/

emmc chip is faulty or corrupt.
I fixed mine by heating up with hot air soldering gun until solder reflow.

cloud1250000 said:
there's no way to fix it? really o,O
Click to expand...
Click to collapse
Same here on my h811. I followed instruction almost exactly but missed 1 thing. It looks like there is no way to fix it by reflashing. Having soft bricked Samsung,Moto and LG g2 and finding ways to recover all of them,it was a shock that this happened to my g4. Androidbrick.com also mentions that we are out of luck.
Other people have sent it back and got it fixed. You can go to LG website to apply for repair. Did the same today and will update the outcome.

When I tried to reverse the sbl1 image, I saw some instruction about booting from mmc1 (I have no clue if it's from a usb stick or the sdcard)...
(since I have really ****ty skill, I had no success in reversing anything related to the bootchain, but I can still read clear string...)
I guess it should be possible to write a copy of the g4 system on it and then boot from it. Unless lg kept the code in their bootloader but patched it out.. (would be stupid tho...)

cloud1250000 said:
When I tried to reverse the sbl1 image, I saw some instruction about booting from mmc1 (I have no clue if it's from a usb stick or the sdcard)...
(since I have really ****ty skill, I had no success in reversing anything related to the bootchain, but I can still read clear string...)
I guess it should be possible to write a copy of the g4 system on it and then boot from it. Unless lg kept the code in their bootloader but patched it out.. (would be stupid tho...)
Click to expand...
Click to collapse
That's pretty much exactly how to fix the problem from what I seen from the people who are withholding information. I was able to get as far as make the phone turn on and Secure Boot Error 1006. I also at one point got it to detect as LGE Android NET device, unfortunately I didn't make a backup of the SD card before flashing another partition to try and go further. I also got the recovery to popup and attempt to restore default settings, but it just reboots into the 1006. I also created the entire G4 system partition table and everything from a US991 KDZ file and got the same SBE 1006 as I did with the LS991 dump.
I think perhaps LG is working with a universal unlocked boot loader on the SD card to bring up download mode and flash whatever stock firmware. They are for sure plugging into the SD card and then flashing via USB

Noksucow1 said:
That's pretty much exactly how to fix the problem from what I seen from the people who are withholding information. I was able to get as far as make the phone turn on and Secure Boot Error 1006. I also at one point got it to detect as LGE Android NET device, unfortunately I didn't make a backup of the SD card before flashing another partition to try and go further. I also got the recovery to popup and attempt to restore default settings, but it just reboots into the 1006. I also created the entire G4 system partition table and everything from a US991 KDZ file and got the same SBE 1006 as I did with the LS991 dump.
I think perhaps LG is working with a universal unlocked boot loader on the SD card to bring up download mode and flash whatever stock firmware. They are for sure plugging into the SD card and then flashing via USB
Click to expand...
Click to collapse
If it can help I had the 9008 problem on my LG G4 H811. First there was no dump to do jtag , I found mmcblk0 files somewhere on xda , so I took a 32 gb SD card, flashed it with PrimaryGPT ( taken from extracted 10N H811 firmware) using win32diskimager and then I flashed each of the 50 first mmcblk0 to the SD card using dd command of Ubuntu, put the SD card into the phone and bam, phone is alive and it can entre download mode. I tried to flash a 10N firmware but the firmware goes to the SD card, I finally flashed a custom recovery, custom rom, the phone internal memory became the SD card, listing /dev/block folder does not show any trace of the emmc, so I think that my emmc is dead
bottom line, like you, I think that the solution is with the SD card method, the inspiration came from the optimus g pro boot repair with some creativity, but I think that something is missing .

leptdre said:
If it can help I had the 9008 problem on my LG G4 H811. First there was no dump to do jtag , I found mmcblk0 files somewhere on xda , so I took a 32 gb SD card, flashed it with PrimaryGPT ( taken from extracted 10N H811 firmware) using win32diskimager and then I flashed each of the 50 first mmcblk0 to the SD card using dd command of Ubuntu, put the SD card into the phone and bam, phone is alive and it can entre download mode. I tried to flash a 10N firmware but the firmware goes to the SD card, I finally flashed a custom recovery, custom rom, the phone internal memory became the SD card, listing /dev/block folder does not show any trace of the emmc, so I think that my emmc is dead
bottom line, like you, I think that the solution is with the SD card method, the inspiration came from the optimus g pro boot repair with some creativity, but I think that something is missing .
Click to expand...
Click to collapse
YES! This is exactly what I wanted to test, even if the emmc is dead, your phone is still "fine." Use the sd slot and it will rise from the dead.

cloud1250000 said:
YES! This is exactly what I wanted to test, even if the emmc is dead, your phone is still "fine." Use the sd slot and it will rise from the dead.
Click to expand...
Click to collapse
to do such thing, we need a database of phone dumps for now i need H815 partitions (mmcblk0)

yeah maybe we'll have more chance if we make a thread in the dev place.
it could help alot of people with bootloop problem..

I can fix these phones talk me on WhatsApp +918989874040
Sent from my LS-4004 using Tapatalk

https://mega.nz/#F!yZ9iERoa!q9eoP4uQoPLRqyiabBIHaA

I have got a H818P bricked
Anyone can provide a solution on how to unbrick it? as this thread just provides H815 unbrick solution:crying:

:crying:

I had no luck at all with mine. Theres no indication the card is being read, phone just gets to boot screen then turns off again after 15-20 seconds then does nothing till the battery is taken out and left for a while. Then the same thing again.

mickrick said:
I had no luck at all with mine. Theres no indication the card is being read, phone just gets to boot screen then turns off again after 15-20 seconds then does nothing till the battery is taken out and left for a while. Then the same thing again.
Click to expand...
Click to collapse
Have you tried starting your phone in download mode?

hiker123 said:
Have you tried starting your phone in download mode?
Click to expand...
Click to collapse
Better still, I got it repaired under warranty.

Green Screen of Death [DemiGod Crash Handler: HW Reset!]

woke up to this green screen of death, pulled out the battery, and phone is dead since then.
no combination of buttons does anything.
The only picture i get the phone to display is when i plug it into the pc without a battery i see the yellow triangle next to the empty battery.
Whenever i put the battery in its solid black, not even the leds light up.
Anyone know of any way to get it into download mode? or is it dead?

Necromancer3 said:
woke up to this green screen of death, pulled out the battery, and phone is dead since then.
no combination of buttons does anything.
The only picture i get the phone to display is when i plug it into the pc without a battery i see the yellow triangle next to the empty battery.
Whenever i put the battery in its solid black, not even the leds light up.
Anyone know of any way to get it into download mode? or is it dead?
Click to expand...
Click to collapse
You can try shorting a pin on the motherboard, getting into qualcomm 9008 mode, and then manually loading the proper partitions via the board diag tool listed in the instructions here... https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
To be honest though...it may be time for a new phone. If it randomly crashed on you and went to the Demigod most likely one of the chips is dead/dying or the solder has opened up(common g3/lg problem). You can test if it is a solder issue by putting light pressure on the board near the SoC, memory, and/or PMIC chips and powering it up; if it shows any signs of life then you have bad solder connection and need a new board.

startswithPendswithOOH said:
You can try shorting a pin on the motherboard, getting into qualcomm 9008 mode, and then manually loading the proper partitions via the board diag tool listed in the instructions here... https://forum.xda-developers.com/verizon-lg-g3/general/how-to-hardbrick-guide-using-test-t3276928
To be honest though...it may be time for a new phone. If it randomly crashed on you and went to the Demigod most likely one of the chips is dead/dying or the solder has opened up(common g3/lg problem). You can test if it is a solder issue by putting light pressure on the board near the SoC, memory, and/or PMIC chips and powering it up; if it shows any signs of life then you have bad solder connection and need a new board.
Click to expand...
Click to collapse
So there is no way i can make adb work from download mode? The device is recognized but in the list of driver installed does not appers "adb". I have some importants file on it and really need to recover it

marsio95 said:
So there is no way i can make adb work from download mode? The device is recognized but in the list of driver installed does not appers "adb". I have some importants file on it and really need to recover it
Click to expand...
Click to collapse
What is the device recognized as? If it is listed as a qualcomm device you are probably stuck and need to follow the tutorial I linked previously. If you see androidnet, LGE, or something that looks like your device then you may get lucky and just need the right driver(s) for your PC.
If you can find a way to get download mode working again(shorting the pin and loading the proper partitions should work) you should be able to recover your files by flashing a kdz and choosing the "normal flash"
option with the LG flash tool(CSE option &/or TOT flash will erase everything)... https://forum.xda-developers.com/showthread.php?t=2797190
*Just try to flash the same version of the software you were running at the time so you can avoid any conflicts; if you can't remember the exact SW version at least flash the correct android version (kit kat, lollipop, marshmallow, nougat).

startswithPendswithOOH said:
What is the device recognized as? If it is listed as a qualcomm device you are probably stuck and need to follow the tutorial I linked previously. If you see androidnet, LGE, or something that looks like your device then you may get lucky and just need the right driver(s) for your PC.
If you can find a way to get download mode working again(shorting the pin and loading the proper partitions should work) you should be able to recover your files by flashing a kdz and choosing the "normal flash"
option with the LG flash tool(CSE option &/or TOT flash will erase everything)... https://forum.xda-developers.com/showthread.php?t=2797190
*Just try to flash the same version of the software you were running at the time so you can avoid any conflicts; if you can't remember the exact SW version at least flash the correct android version (kit kat, lollipop, marshmallow, nougat).
Click to expand...
Click to collapse
maybe you give me the solution !!! Yes i can get in the download mode anytime i want ; the device is recognized as Lge driver . O i try to flash the right kdz file and hope it will good