Related
I was trying to put TWRP on my G3 (D855) but it failed for some reason but the stock recovery was deleted. So there was no recovery in phone. I gave it to a friend to try putting TWRP in it, he also failed and somehow corrupted the partition. He said the phone is completely bricked now and is not even turning on.
Any suggestions what I should do?
Too few details provided.
Can you enter download mode?
elixir_pr said:
I was trying to put TWRP on my G3 (D855) but it failed for some reason but the stock recovery was deleted. So there was no recovery in phone. I gave it to a friend to try putting TWRP in it, he also failed and somehow corrupted the partition. He said the phone is completely bricked now and is not even turning on.
Any suggestions what I should do?
Click to expand...
Click to collapse
Flashtool,
goodluck
bender_007 said:
Too few details provided.
Can you enter download mode?
Click to expand...
Click to collapse
I can't enter download mode. The phone is not turning now...the screen remains black.
Gerhard.M said:
Flashtool,
goodluck
Click to expand...
Click to collapse
How? Which tools to use?
Its neither turning on, also no LED light when I put in the charging cable with adapter. When I plug it into laptop USB, it shows "LG Android USB Device" in Device Manager - with yellow exclamation mark. Please help.
elixir_pr said:
Its neither turning on, also no LED light when I put in the charging cable with adapter. When I plug it into laptop USB, it shows "LG Android USB Device" in Device Manager - with yellow exclamation mark. Please help.
Click to expand...
Click to collapse
1
bender_007 said:
1
Click to expand...
Click to collapse
This did not help me.
I noticed one thing. Even though on the cover it says D855, but when I opened the phone, on the mother board I saw D851. What does this mean?
The motherboard should be right, its tmobile. Did you have fm radio on it? If not then tmobile for sure
Poslano sa mog LG-H815 koristeći Tapatalk
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Did you install it thru TWRP?
thekingestkong said:
sooo, I gues something went wrong... since the new marshmallow images was posted today, there was a thread on reddit on how I can just download the image and rename it and flash it as OTA. The phone reconginzed the image and went half way through the install and then went black. now it wont even buzz or register the charger. Does nothing when connected to the computer either so I assume there is nothing that could be done. Quite a shame, the phone worked quite nicely until is killed it . Anything I can do?
Click to expand...
Click to collapse
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
no, the phone picked up the update from the internal storage
dc959 said:
There is one thing I recommend trying as there is a bug in official firmware where the phone when connected to a computer can turn off randomly and not charge or boot. What you need to do is disassemble the phone and unplug the connector at the top of the phone to disconnect the battery and then plug it in.
Click to expand...
Click to collapse
thanks, I'm aware of that. Some folks experiencing the same issue tried that with no success. My phone is still under warranty and the screw securing the backplate has a seal on it that I dont want to tamper with.
I guess I'll be sending the phone for to Asus for repair...
Don't lose hope.
My phone was in a similar predicament.
No response to any buttons, nothing on screen, no buzzing or LED's at all.
I was able to get it recognized in the xFSTK Downloader and showing up in windows device manager as a Moorefield device.
I tried many times to get it to put the images on the phone through the xFSTK tool and it failed many times.
I was about to give up and tried again this morning and miraculously the writing succeeded and now my phone is in a bootloop (I think the battery may have been completely drained with my attempts to save it's life.)
I have it on charge currently so hopefully when there is enough juice I should be able to flash the raw file and be back up and running.
I see, you can follow the unbricking tutorial in the general section. Works fine for me and saved me from sending it to the service center.
krazy23 said:
Did you install it thru TWRP?
Click to expand...
Click to collapse
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
galagala2 said:
I did! And now my phone is dead! But it buzzes when I press the power button for some seconds.. But it's always black
Click to expand...
Click to collapse
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
krazy23 said:
That's what happened to my phone, you can follow this thread this worked for me. Unbricking Method
Click to expand...
Click to collapse
do you lose the data this way?
thekingestkong said:
do you lose the data this way?
Click to expand...
Click to collapse
Unfortunately, yes. Because I ticked the "wipe data" checkbox in the ASUS Flash Tool. Not sure what will happen if I don't. :fingers-crossed:
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfon
I also bricked my phone and used the method to fix my phone. Make sure you have all the required drivers installed in your pc/laptop before doing this. I took help of DriverMax to solve the drivers related issues. Make sure before installing and running the XFTSK tool all the drivers and everything is installed otherwise you will see blank forms in the Tool.
Hi everyone
I having this problem with my lg g3 d855 ... My phone was at 5% then i wanted to remove kingroot because i wanted to flash super su. After uninstalling kingroot (in the app) the app crashed ant after few seconds my phone turned off... i was thinking my phones battery just died, but i was wrong. My phone wont turn on now :/... Only response i get from it then i plug it in the charger without battery (it show no battery error)... then i put battery in, screen goes blank.
And also i installed twrp using app from store (Forgot the name, but for d855 model)
*LG G3 D855 Android 6.0 official* (if needed.)
i tried:
holding power button for 15sec without battery and then charging it... Didn't work :/.
Putting another battery (Galaxy s3... Charged to 30% at least. I don't have another lg battery ), same result.
New battery also doesn't do anything...
EDIT:
i tried method in http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359 but i can't find nor make .tot file :/ anyone can link mby?
and there's exclamation mark near Qualcomm HS-USB QDLoader 9008(COM13) in device manager. Maybe there's a problem with that?
Help guys
EDIT V2!!:
Thanks for nothing
i fixed my lgg3 with this tutorial http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
and flashed files in this order http://forum.xda-developers.com/spr...very-guide-t3132359/post65291398#post65291398
after that i put phone into download mode and flashed kdz file i had
at least someone responded to this post :/
It works now!..
The problem was autorec... i tried to install recovery using autorec for lollipop and that screwed everything
I have exactly the same problem.
Hamtero said:
I have exactly the same problem.
Click to expand...
Click to collapse
i fixed my lgg3 with this http://forum.xda-developers.com/sprint-lg-g3/general/guide-fix-hard-brick-recovery-guide-t3132359
and flashed files in this order http://forum.xda-developers.com/spr...very-guide-t3132359/post65291398#post65291398
(i installed slb1 without battery and then unpluged phone, put battery, hold volume up, putted usb back into phone and tried to put phone into download mode. IT WORKED!! )
And Thanks for replay
I was in the middle of unbrick my g3 from hard brick to soft brick. I flash firmware using lg up at 99% then the phone died as it tried to reboot. It won't boot at all. As you said when remove the battery and connect charger, i can see my motherboard working with exclamation mark. As soon as i put the battery, motherboard out and no sign of life. Is this sign of bad battery or what. I don't have spared battery
I recommend first, to users with similar problems, to try first my guide in following link and after the pins in motherboard-tot files
https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268/page116
Superuser_ said:
I recommend first, to users with similar problems, to try first my guide in following link and after the pins in motherboard-tot files
https://forum.xda-developers.com/lg-g3/general/root-twrp-marshmallow-d855-30b-t3286268/page116
Click to expand...
Click to collapse
I have D858HK hard bricked for 2 month and i use v10d to flash every partition. Then it won't boot into recovery. When i use v985 .tot, it successfully boot into recovery. Also on LG Smart Board diagnostic, my model not detected. Even if i manually select, nothing happen when it reboot. Right now, i have no idea whats wrong as i spent countless of hour on google and XDA.
anip_aniki said:
I have D858HK hard bricked for 2 month and i use v10d to flash every partition. Then it won't boot into recovery. When i use v985 .tot, it successfully boot into recovery. Also on LG Smart Board diagnostic, my model not detected. Even if i manually select, nothing happen when it reboot. Right now, i have no idea whats wrong as i spent countless of hour on google and XDA.
Click to expand...
Click to collapse
Have you try my guide?
Superuser_ said:
Have you try my guide?
Click to expand...
Click to collapse
I already follow your guide. The thing is, my device not detected on LG Smart Board Diagnostic. When i manually select my device, everything ok then it boot with blank screen with red and blue led. I can't even enter download mode. I use win 10 64bit with all driver installed and disable integrity checks and everything
Hi to all,
yesterday I attempted to install LineageOS on my LG G4 h815.
I followed this tutorial -> https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Everything went fine. I was able to boot under LineageOS reinstall my apps etc, etc.
This morning when I woke up everything seemed normal too. But, few minutes ago, I sent an SMS via Google Messages the phone froze and then black screen.
When it froze I had 97% battery.
Ï tried to reboot it with power button -> Nothing.
I tried to remove the battery put it back on and pressed the power button -> One tiny vibration but nothing
I tried several times the same last process and finally I managed to get the screen with "Bootloader state : Unlocked !", but I cannot go further.
If I connect the phone with a USB cable, wether he's "turned on" or turned off no led is blinking.
Does someone have a clue to fix this or has ever encountered this issue ?
Tanks in advance and do not hesitate to refer to an old post. I wil check (but found no same case).
Jérémie.
Monkeypox95 said:
Hi to all,
yesterday I attempted to install LineageOS on my LG G4 h815.
I followed this tutorial -> https://forum.xda-developers.com/g4/general/howto-complete-guide-to-unlock-twrp-t3370003
Everything went fine. I was able to boot under LineageOS reinstall my apps etc, etc.
This morning when I woke up everything seemed normal too. But, few minutes ago, I sent an SMS via Google Messages the phone froze and then black screen.
When it froze I had 97% battery.
Ï tried to reboot it with power button -> Nothing.
I tried to remove the battery put it back on and pressed the power button -> One tiny vibration but nothing
I tried several times the same last process and finally I managed to get the screen with "Bootloader state : Unlocked !", but I cannot go further.
If I connect the phone with a USB cable, wether he's "turned on" or turned off no led is blinking.
Does someone have a clue to fix this or has ever encountered this issue ?
Tanks in advance and do not hesitate to refer to an old post. I wil check (but found no same case).
Jérémie.
Click to expand...
Click to collapse
Take note of what version of recovery you have you at need to try a few different versions or your device has the dreded boot loop issue........
---------- Post added at 10:38 AM ---------- Previous post was at 10:22 AM ----------
stinka318 said:
Take note of what version of recovery you have you at need to try a few different versions or your device has the dreded boot loop issue........
Click to expand...
Click to collapse
This at help to........
https://forum.xda-developers.com/g4/help/installing-twrp-issue-t3606772
stinka318 said:
Take note of what version of recovery you have you at need to try a few different versions or your device has the dreded boot loop issue........
---------- Post added at 10:38 AM ---------- Previous post was at 10:22 AM ----------
This at help to........
https://forum.xda-developers.com/g4/help/installing-twrp-issue-t3606772
Click to expand...
Click to collapse
Not sure to understand but how can I try different versions of TWRP if I can't get to Recovery mode ?
Monkeypox95 said:
Not sure to understand but how can I try different versions of TWRP if I can't get to Recovery mode ?
Click to expand...
Click to collapse
What version did you flash.......
stinka318 said:
What version did you flash.......
Click to expand...
Click to collapse
I flashed this img twrp-3.0.2-1-h815.img
Monkeypox95 said:
I flashed this img twrp-3.0.2-1-h815.img
Click to expand...
Click to collapse
Is there another version that you can try found on Samsung device sometimes flashing a older version may work.....
stinka318 said:
Is there another version that you can try found on Samsung device sometimes flashing a older version may work.....
Click to expand...
Click to collapse
I really would like to try another version but how ? I can't even get to recovery mode... I'm stuck on the first LG logo.
Monkeypox95 said:
I really would like to try another version but how ? I can't even get to recovery mode... I'm stuck on the first LG logo.
Click to expand...
Click to collapse
If you can get it in to download mode use you laptop to flash recovery this is probably why it has failed.......remember Google s your friend.
stinka318 said:
If you can get it in to download mode use you laptop to flash recovery this is probably why it has failed.......remember Google s your friend.
Click to expand...
Click to collapse
Just to perfectly understand.
Are you advising me to flash my recovery with an older version via my laptop (I imagine via adb/fastboot) despite I can't even get my LG be recognized by my laptop ?
Will the adb/fastboot command be functional as the LG seems not to be recognized on the PC?
Monkeypox95 said:
Just to perfectly understand.
Are you advising me to flash my recovery with an older version via my laptop (I imagine via adb/fastboot) despite I can't even get my LG be recognized by my laptop ?
Will the adb/fastboot command be functional as the LG seems not to be recognized on the PC?
Click to expand...
Click to collapse
The best way to get your laptop I recognize your phone is to get LG up running then with the usb plugged n drop the battery out then put battery back in then close off LG up.
Then start it again and when it go's into download mode the pull usb and close off LG up Then plug it back in with dos prompt open............
stinka318 said:
The best way to get your laptop I recognize your phone is to get LG up running then with the usb plugged n drop the battery out then put battery back in then close off LG up.
Then start it again and when it go's into download mode the pull usb and close off LG up Then plug it back in with dos prompt open............
Click to expand...
Click to collapse
Thanks for your reply and your time. I didn't know this software "LG Up", I will give it a try this evening (in France ^^') and give you feedback then.
Monkeypox95 said:
Thanks for your reply and your time. I didn't know this software "LG Up", I will give it a try this evening (in France ^^') and give you feedback then.
Click to expand...
Click to collapse
LG UP had no effect on the phone.
However, now the phone seems to have 0% battery and when I try to boot it I get the graphics to plug the phone on a source of energy. Once I do that the front led is blinking in orange (I guess because I had less than 1 or 2% o battery) and now the front led is still lit on in orange. Is this a good news or I'm hoping for nothing.
Anyway tomorrow I will try to get it back to my retailer.
Does anyone succedeed to get it replaced by LG even if the bootloader is unlocked ?
Thanks.
After a little journey to the repair shop of my retailer everything seems to work correctly, for the moment, with LineageOS !
Thanks everyone for your help !
Hi Guys,
Yesterday during an official update of my oneplus 5t (using the update manager from the phone itself), the phone got bricked and i dont know why....
So after some research i found it is hard bricked ( basically i cant do nothing, power on i cant, power +volume UP/DOWN too, and even when i plug the charge cable i have neither vibrations nor LED on)
So i follow this tutorial to unbrick the phone:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
I could get the phone recognize by the PC by pressing UP to see the phone as QUSB-BULK and then QUALCOMM QD LOADER after driver's update.
But when i run MSMDownloadTool ( V4.0.27 dumpling 43_0.36_180613) as administrator and click on start, the process get stuck in "waiting for device"
the status of connection before click on start was "connected" and after click and some process it turn to N/A
the status of communication is "memory size....."
status of last communication is "waiting for device"
I have tried several time and always the same result..... stuck in the waiting device
does someone have an idea on how to solve this? because i really need to unbrick the phone....
thank you in advance
EDIT:
I tried another version of MsmDownloadTool (dumpling_43_O.06_171206) and this time, the downloading of cache image failed....
I dont know what to do
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
DaRk-L0rD said:
Thing are much easier with the unlocked bootloaders!
Charge your phone all night long even if you don't see any sign of life (green or red led light).
Then hold together the Volume UP button and the power button for few seconds into the fastboot mode (hold both buttons for at least 10 seconds) and let me know.
Click to expand...
Click to collapse
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
rokusho32 said:
Thanks for reply.
No i was on official oxygen OS, not rooted or custom installed and when i start to download the update, i was 80%.
Click to expand...
Click to collapse
rokusho32 said:
I tried this before and nothing happened....
then when i connect to the pc by pressing UP+ power button, the pc detected it as QUSB_BULK then i install the qualcomm driver and finally i could see the phone in the usb device.
But after MSMDownloadTool step, the process got stuck and display "memory size" as explained in the thread.
Click to expand...
Click to collapse
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
DaRk-L0rD said:
Go here:
https://forum.xda-developers.com/showpost.php?p=74504343&postcount=3
Follow the instructions for the adb drivers installation.
Once done that, let me know
Click to expand...
Click to collapse
I have installed the ADB drivers
which version of MSMDownloadTool should i use?
DaRk-L0rD said:
You were in a custom rom or kernel when you tried to update from the official channel?
Your phone was rooted? Magisk installed?
Battery percentage?
Click to expand...
Click to collapse
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
rcbjr2 said:
I know this is an old thread, but I'm hoping you have an idea. I have bricked my rooted OnePlus6. I did have Magisk installed. Bootloader was unlocked. I was able to factory reset the phone, but the bootloader was still locked (I had TWRP installed and factory reset using it). I then used Fastboot to relock the bootloader, and that's when my troubles started. I could only get into Fastboot. I found a solution on the web, installed the Qualcomm drivers (and they recognize my device, which I connected by holding down the volume up button before connecting to the USB cable), and started the OnePlus 6 (MSM) unbrick tool. However, it just sits there saying "waiting for device". I actually seem to have two entries for the device, one saying Index and one saying "1" (although I think the device is on COM3). Should it take forever? How can I get it past "Waiting for device". Thanks.
Click to expand...
Click to collapse
I have same situation.. did you resolve this problem?
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
I contacted OnePlus and I sent them the phone and they reinstalled the operating system. I was never able to fix it myself. I even had an online session with OnePlus and they couldn't get the MSM software to recognize the phone (even though it was truly connected to my laptop). I also had an issue with my OnePlus 8T that got messed up doing something with Magisk, and OnePlus reinstalled the operating system as well. I still can't boot from the A partition though; just the B partition.
piechu11 said:
I have same situation.. did you resolve this problem?
Click to expand...
Click to collapse
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
At first, I chose WWAN-DHCP - which caused problem with connection
piechu11 said:
Okay, for anyone facing same problem as me, i found solution (working for me). Before using MSM Tool, you need to install Qualcomm USB Drivers.
During instalation you need to choose second option "ETHERNET-DHCP"!
View attachment 5511425
At first, I chose WWAN-DHCP - which caused problem with connection
Click to expand...
Click to collapse
Thank you this solved my problem exactly.
i was restoring my metro by tmobile oneplus nord n10 BE2025 model with build tag BE88CF