Develop Bugs

Zenfone 2 does not turn on

Good morning, I have a big problem in my Zenfone 2 and would very much like your help.
Yesterday in the morning he hung up, I thought I had downloaded but I tried to turn it when he called saw the battery was at 50%, I found strange but ok, then the screen locked and the phone started to vibrate and I had to off it. When I called, the battery was at 50%, was saying that the phone was connected and there do not leave sound and saying he was carrying. I thought it might be the rom and turned it on PC to back up and exchange of rom, only the USB no longer recognized the connection to the PC. Was saying that tava carrying, I took the USB and stopped "load" when I called he carried again, just not giving connection to the PC. Anyway I did not back up and changed the rom, he continued the same thing (I was in the AICP (LP) and put the RussiaNBear (LP)).
So I was following a tutorial that I had used before to repair another error (I could not post the tutorial link here, but it's on youtube: (Tutorial - Zenfone 2 unbrick / Restore (ZE551ML / ZE550ML) - In the Droid Will channel)), but I gave soft to do so because the part of the AFT (Asus Flash Tools) it does not recognize the phone, having to disconnect the usb and connect again, and then I screwed me, 'cause the uSB connection was not working. After a few unsuccessful attempts, it seems I agravei even more the situation because now I turn the USB cable pressing volume down and it goes in "Moorefield" and the PC identifies a good, open the xFSTK and can pass the DNX, but when you finish spending DNX the phone should reboot and a screen appears with the symbol of a uSB connection, but that's not what happens. I spend the DNX, the phone restarts and vibrates, there is the xFSTK waiting to pass the OS, but not USB screen appears, the xFSTK does not recognize the phone more in "Moorefield" and I can not do anything else on the device.
I have already connected the phone on another pc, I have changed the cable and nothing. I think it is the mobile usb, if not it would not recognize the first part of xFSTK.
Apologies if I have not posted in the right place, for my English (Google Translate) and the text size, only tried to leave everything well explained so that everyone can understand. Thank you very much, beforehand to help you and I really hope we can solve this problem.
Thank you.

No one ?
no one can help me?

LG G3 in download mode not detected by Windows

Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
In order to fix this soft-brick I first tried to use recovery by pressing VOL - & POWER. In the menu, I could select and confirm to recover to factory settings, but after some seconds the boot loop appeared again with (seemingly?) no change having been made. The error kept appeaing over and over again.
After trying recovery mode, I attempted to start the phone in download mode by pressing VOL + on the (switched off) phone and connecting a USB cable. The respective menu also opened, here, showing "Firmware Update" and "Do not unplug the USB connection until the process is complete". According to many tutorials I found on the internet, when having installed the required drivers (I used LG United Mobile drivers from here), this procedure should allow you to flash a recovery image through LG's flashing tool (which one can also find on that page).
However, when I connect the LG G3 (D855) to a computer the driver is installed on, there is no new device shown in the Device manager. I tried this out with Windows 10 x64 and Windows 7 x64 and disabled driver validation on both systems and enabled test signing on Windows 10, respectively. Additionally, I followed these instructions, but in this case the screen stays dark and the device is not detected either. It seems like there are not so many people experiencing this error, but I hope we can find a solution.

nVentis said:
Dear xda-developers-community,
I'm trying to get a phone of a friend of mine working which just reboots whenever the phone is started. The resulting boot loop can only be interrupted by taking the battery out or wait until it is depleeted.
Click to expand...
Click to collapse
This may sound like a dumb question, but have you tried a new battery yet? If it is one of the original batteries it could have gone bad & started bootlooping...like mine did a few months ago.
As far as the PC not recognizing the phone you can try downloading USBDeview and uninstall anything that has the vendor ID's of 1004 & 18d1(pretty much anything that says android or LGE in the description) & reboot the PC. Hopefully it'll recognize your device and install the drivers the next time you plug it in. If it doesn't find the drivers automatically for you then install LG drivers manually.
Link for usbdeview: http://www.nirsoft.net/utils/usb_devices_view.html
Link for LGE drivers: http://www.lg.com/us/support/software-firmware-drivers
Good luck :fingers-crossed:

Help Unbrick Please - LGVS985 Verizon - Detailed Description of Issues

Hello, so I'm the go to guy for helping with phones, I've been on XDA a few years now, always a nexus nerd, so I'm slightly in a foreign territory as I try to help my brother unbrick his LG G3.
Situation:
- Brother claims he had app updates, and he had the TWRP app installed, he was running Turbo ROM - (https://forum.xda-developers.com/lg-g3/development/rom-turbo-rom-layers-t3346477) latest version Turbo-vs985-4.0-OFFICIAL-20160509.zip (I have the ZIP) - and that he allowed the apps to update, and the TWRP app did it's thing. (I'm not clear weather it was just the APP update, or if he tried to update the Recovery partition via app).
- Next he said either after a restart or crash, the phone just refused to boot. It stayed off, totally (seemingly)
- He did note that he had battery issues few months back, that his battery bloated on him, but he replaced it.
- When I went to pick up phone, he had it off/battery out for a few days, I think the battery still had a charge. we did a Vol Down/Power with charger plugged in, battery in, and it turned on the screen, I think we were looking at stock recovery if I recall correctly. Few seconds later it turned off and never came back on.
My Observations:
- when plugging into computer, I see a device "Qualcomm HS-USB QDLoader 9008 (COM4) - no device "visible" under my computer. (screen never on)
- fastboot and adb both show no devices.
- I used LG Smart Boot Diagnostics Tool 1.3.1 (from guide http://www.androidbrick.com/unbrick-recover-your-dead-lg-g3-g2-all-variants/ ) to try and diagnose it, but every time I choose the right model from the drop down (LGVS985_AVRZ_VRZ), and confirm, it seems to connect correctly, and it starts to display results as OK (there are more to scroll down to see), but then it quickly disconnects, not allowing me to see other results.
- guide seems to be aware of the issue ..."In these situations Smart Boot Diagnosis seems can’t reaching the emmc and 9008 port shuts itself down and comes back (you hear it, like usb unplugged and back in).".... - and recommends using another step highlighted by this guide ( https://forum.xda-developers.com/lg...3-qhsusbbulk-qualcomm-9008-t3072091?nocache=1 )
- This is where I get lost, @willcracker seems to illustrate a need for a tot file, which from what I can gleam is LG's original version of firmware format. And that I need to get the exact version of the TOT that was installed with the ROM?
- I browsed the ROM forum, can't find mentions of a TOT file, but my brother did keep a backup of the Turbo ROM on his internal card, as well as a total TWRP backup of a ROM "2016-06-17--21-31-26_MRA58K" that contains boot/data/system/ .win .win000 .win001 etc. backups, as well as xdabbeb_stock_vs98547a.zip and xdabbeb_vs98535b_bootstack.zip -
SO.... I think I might have all the files Except the TOT to unbrick this thing, but I'm not sure what to do about the TOT part.
Any help is appreciated. Thank you for reading this Wall of text.
PS. He mentioned he was more interested in just grabbing photos from the internal storage, vs fixing the device, but getting the photos and fixing it would be an awesome surprise!
:fingers-crossed:

Oneplus 3 just died out of no where

So i was using my phone and decided to restart it after updating my adaway files but my phone never turned back on. The two press the power button screens did not show up either. I tried to uses the MSMdownload tool since i thought my phone was somehow bricked but that didnt work either, it just kept restarting the download process after everything was completed. my computer makes a sound when its connected and it connects correctly as a quallcomm 9008 device but even after all this nothing is working. has anyone experienced something like this or does anyone have any advice?

did you try to long press both power button and vol up ...you should feel a vibration...
maybe it's not turned of maybe it's error causing the screen to be off... also is there any heat?

Which method of the unbrick tool did you use? First or second? If the first, then maybe you should give the second also a try.
Sent from my ONEPLUS A3003 using Tapatalk

I've tried everything and I used th me second method yet nothing happened. I can see my phone get recognized by the computer and get listed on the MSN device list yet nothing happens after it finishes the process. After the green line shows up telling me that it's completed everything the process restarts writhing a few minutes unless I unplug it. No vibration no nothing the phone just died on me after I restarted it .

Try doing MSM on a different PC with all drivers installed , hope it helps

Try to repeat flashing again, there is no other way. Use method 2only. Extract tool again and try flash.

When I was used Xperia Z1, I bricked my phone with a soft brick. So I installed driver in my PC and flash Kernel though FASTBOOT(ADB) either it's not show Device in my PC (I show just "Unknown Device").
After that my phone can connect to my PC again (Now It shown C9303 or something that meant it know it's a phone).
So I can flash by Flashtools again. Soft brick is not scary as Hard brick, you'll find some way to bring it back easily.
Hope this help!
PS. Bricked Phone is WEAK in Battery, always connect it with charger.

Problems to install stock rom (Lenovo vibe K5 Plus)

Hello everyone! I hope you're doing well. I'm new here and I'm facing a problem that I can't seem to solve, so I'm here to ask for your help.
CONTEXT: My girlfriend had a phone whose screen broke. She couldn't afford to buy a new one, and neither could I help financially. But I had two old devices: a Motorola G1 (which I used to store some things and do simple tasks) and a Lenovo Vibe K5 Plus, which was the one I was using. Since I had just graduated from college and she hadn't, she had a greater need than me for a slightly better phone. So I gave her my Lenovo and I'm using the Motorola. When the Lenovo was still with me, I had put a custom ROM on it from Lineage (I think it was Android Nougat, if I'm not mistaken) and it also had TWRP. Before giving it to her, I only did a quick format of the phone.
A few days ago, there was a problem with the Lenovo and Android no longer worked. The phone turned on, entered the Lineage boot screen, but when it tried to turn on Android, a message appeared saying that Google's text-to-speech had continuously failed, and the phone turned off. She brought it to me yesterday and I thought about installing the original stock ROM on the device. With difficulty, I managed to get the laptop (Windows 10) to recognize the phone when it turned on. The difficulty was because when I tried to turn it on, the screen kept flashing on the Lenovo. I opened the device, took out the battery, waited for a while, and miraculously managed to turn it on. When it turned on, the laptop installed the device before it turned off. Through ADB, I managed to get the device to reboot directly to recovery, since I couldn't access recovery through the physical buttons on the device.
So, I managed to make a backup of the files that were important to my girlfriend and that were on the phone's internal memory. After that, I formatted the device through TWRP using the "format data" button. Still, I used the wipe to erase everything except for "USB-OTG" and the memory card option (which I had removed along with the SIM card before trying the procedure). After that, I restarted the phone to enter TWRP directly.
PROBLEM: After doing this, I tried to install the stock ROM using ADB sideload, but it said there was something wrong with the image I was using. The sideload gave an error message and said that the phone needed to be restarted. I restarted it from this screen by sliding my finger to the right, and... the phone no longer turned on and wasn't recognized by the laptop! I can't access TWRP through the physical buttons (at least not through the traditional method I know, which is the volume up button and the power button), ADB doesn't recognize the phone, and I don't know what else to try.
QUESTION(S): How can I force the laptop to recognize the device so that I can make it reboot directly to TWRP, since the device doesn't turn on for long enough for Windows to try to check the drivers? Or has TWRP been corrupted? If so, how can I install TWRP again? Is there any other way to access recovery? Is there any other way I can use to install the stock ROM? We can't afford to take it for repair at this time (the situation here in Brazil is very bad), much less afford to buy a new device. Does anyone have any other ideas on how I can access recovery or how I can install a ROM without necessarily turning on the device? Or any other ideas?
I really appreciate anyone who read this far and, in advance, I thank anyone who can help me. Gratitude!