I am looking for the easiest way please to get my phone working again. LG G3 D855 from HongKong? LGD855XA9BK
I am not bothered about keeping anything on the phone, it can be formatted wiped, whatever.
When I Vol down and connect to pc usb, it takes about 7 seconds of a blank screen to the initial LG Lifes Good logo,, from there it sits another 15 seconds until the download mode logo pops up. This is up for approx 8 seconds (which my pc does not detect as a device) and then goes into fastboot which my pc does detect.
in a cmd window if I type fastboot devices command, the device ID appears as a single ' ? '
Gotten TWRP 2.8 for LG G3, If I type fastboot boot twrp.img then the twrp logo appears on the phone but goes no further - I have to battery pull. But..
keeping the twrp logo on the phone, if i type again fastboot devices from a cmd then there is no device listed.
still keeping the twrp logo on the phone if i type adb devices then the full device id appears as it should.
I'm going in circles and I'm not sure what cause the problem in the first place. I'll be happy with stock back on (tried the flash tool but pc won't detect the phone in fastboot, the lg recovery tool is the same) but I'm struggling where to start.
If this has been covered with success than I can't find it in the forums. If anybody can point me in the right direction then that would be great.
Thankyou in advance!
(p.s. I though I posted this question whilst not logged in to my account previously, so it is listed previously under a guest account which can now be deleted, but keeping this one. With thanks)
I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
pchuen said:
I have just flash the custom 5.0.2 ROM using philz touch 6.48.4.
After I flashed the ROM, I reboot to the philz recovery and flashed back to cwm 6.0.4.8.
However, the device stuck on the LG logo screen.
I have try to enter Download mode/Emergence mode/Hard reset mode/Recovery, but all of them I cannot go into.
Please help! Thank you for your helping!!
Click to expand...
Click to collapse
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
pchuen said:
Thank you for replying.
I cannot do anythings since I cannot enter into download mode.
I pressed volume key + and - and insert the usb cable to computer. There is nothing happened, computer dose not show the devices attached and the phone stay in the LG logo screen.
Also, I cannot use adb commands to force the phone enters into download mode as it shows nothings under "List of devices".
Is there any methods I can go into the download mode???
Thank you!
Click to expand...
Click to collapse
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
hawkwind212 said:
Your boot loader is broken. Gonna have to get to the down load mode and reinstall either the or the stock. You can probably flash the recovery with .IMG file with lg flashing tool. Nerdy blond's twrp is one of those files that you can use. You can even try installing it first with the adb shell command, you can get the instructions at the same place where you download.
http://forum.xda-developers.com/showthread.php?t=3144369
Click to expand...
Click to collapse
ShadySquirrel said:
If your phone shows LG start screen, it should go into Download mode. I had similar problem few days ago while I was testing some kernel patches, it just froze on the LG screen. Solution was to unplug it, remove it's battery, SIM & SD (you don't have to remove SIM & SD, I just work that way) , make sure it's off, return battery back, press Vol + & Vol - at the same time and plug-in the USB cable.
Before that, make sure you have installed LG Unified driver (can be obtained via LG's software from support site), because without that Windows won't recognise your device.
After that, once you make your phone usable with Freegee/whatever you use to install initial recovery, flash official TWRP, because others are too old - that Philz CWM is old but still working with Lollipop but not work good and is tends to lock itself into a bootloop if you use hardware keys to enter; that other one, from GPRO_recovery APK is not supported and not working well (for me since day one), so it should be replaced as soon as possible.
Also, I can suggest you to flash your phone from stock 4.1 (not KitKat), root, flash recovery via freegee and after reboot update to latest official TWRP via Flashify.
Click to expand...
Click to collapse
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
pchuen said:
Thank you for your detail reply.
I have tried to reinstall the LG driver and try to enter download mode again.
The screen is still stuck on LG logo and I cannot find the device in hardware manager (cannot recognize it).
I cannot do anythings until it can recognize it.
(Is it the bootloader is broken? and can I fix it?)
Thank you very much and waiting for your reply soon.:good:
Click to expand...
Click to collapse
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
ShadySquirrel said:
Which version of Windows are you using? It should be displayed under Serial ports in Device manager (named something like LGE Serial device) and LGFlashTool should recognise it immediately. I can't make you a screenshot/check for real name because I'm running Linux right now and can't reboot.
Also, try with another cable/port, remove all other android drivers you may have (Samsung's, Google's...) and disable antivirus.
Click to expand...
Click to collapse
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
pchuen said:
It does not work on Windows 7 and XP.
I did not find any LGE XXX under Serial ports part.
Thank you!
Click to expand...
Click to collapse
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
ShadySquirrel said:
Hm.... Phone shows that it have entered download mode? Black screen, centered gray message and "DOWNLOAD MODE" red text?
Click to expand...
Click to collapse
No... nothing happens, just showing LG logo...
pchuen said:
No... nothing happens, just showing LG logo...
Click to expand...
Click to collapse
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds, return battery
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
ShadySquirrel said:
OK, it doesn't enter download mode. So, step by step:
- remove battery and leave it for 15-30 seconds,
- press Vol+ and Vol- at the same time and keep them pressed,
- plug USB cable in while keys are pressed
It should immediately put you into download mode, with no LG screen, just black screen with gray box and red text I've described to you.
Click to expand...
Click to collapse
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
pchuen said:
I understand what download mode screen is.
I followed your methods, bur I still cannot enter it and the computer cannot recognize that.
Sorry for disturbing :crying:
Click to expand...
Click to collapse
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
ShadySquirrel said:
So, whatever you try to do, phone just shows LG logo, not even a message in an upper left corner?
I'm running out of ideas. I have exact same variant (E988) but only time it didn't want to enter download mode this way was when cable I was using was broken...
Click to expand...
Click to collapse
I have changed the cable, but it is the same.
I recently replaced my Cracked Screen on a Verizon m8. I was on a custom rom with twrp installed. After the initial boot, I was having problems with a speaker and went to try to boot to the bootloader to do a RUU, when I noticed that I can no longer access the bootloader screen. It was then when I noticed that not even my computer was recognizing the phone no more. It's as if the phone won't debug no more. I can still access my TWRP by rebooting straight to recovery thru a app or the apm it has on the custom rom im using. I've tried to flash other roms with no success to get access to these two things. I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms. Or if anyone has had this problem before or if any suggestions im open to anything to try and get to the bootloader screen. It also doesn't even boot the two or 3 second boot up screen until you get to the roms boot up screen. It also doesn't goto the bootloader screeen when it try's to access the bootloader. Even when booting straight to recovery stays black until twrp actually shows up. So it's as if bootloader is completely being bypassed. You cant use the volume keys to access the recovery cause everything is blank. Although on first attempt to access bootloader screen when I was stuck there in black. I had to figit the keys a bunch of times to reboot, hoping that I didn't activated something in that screen that caused the phone not to debug. Any suggestions is more then welcome and if someone has a stock twrp of recent stock rom 4.605.9 I believe it is would be more then great. Cant find one other then in zip or exe version. Hoping maybe that might reactivate those two things. Thanks for taking the time to read my problem.
Debugging or adb works within OS, and its not a mode in itself. I think you mean you can't access bootloader-fastboot mode.
Casetheace said:
I was wondering if anyone had a stock twrp of Verizon version. As for all my twrp are from custom roms.
Click to expand...
Click to collapse
You mean stock recovery. TWRP is a specific custom recovery, therefore always a custom one.
I don't think stock recovery will change anything. Bootloader is on a completely different partition.
Its odd that you can't access bootloader. It must still abe intact, otherwise the phone would not work at all.
Did you try (in OS): adb reboot-bootloader
Are you s-off or s-on?
The phone is S off. I was able to get the phone to USB debug. I took it out of the shell and plugged in the USB cord and it debug instantly . So I'm guessing with that I had to damage something when I either took the phone out of the shell originally or when I replaced the screen. Cause you literally have to take every piece of the phone off and then reasamble the phone from scratch. Once i put the phone back in shell, i couldnt get it to usb debug no more. But I still can't access the bootlader, nor is the first boot screen on power up before the main boot up screen starts. Also has no display if I reboot to recovery using a app from the phone. You don't see the screen where the red text would show up saying rebooting to recovery, display starts when it begins to show twrp on display. But when I had the shell off, and was able to access USB debug, I was able to use adb commands from my computer from fastboot mode , but phone had no display. Was able to run a RUU, was able to use adb to reboot to boot loader, then was able to fastboot get varall command. Even flashed a twrp recovery install in fastboot under command prompt . So that tells me that the boot loader is operational. That it has to be some sort of power failure in booting that nots powering the display on initial boot for 2 to 3 seconds , no power on bootliader display, no power rebooting to boot loader or rebooting to recovery until it boots recovery. Any ideas what would cause this failure of power of display during boot loader processes? By the way , have twrp 2.87 . Its a Verizon build, but I'm on a T-Mobile sim.
I've installed live boot and attached a log. If anyone can help or maybe know why this might happen. Believe there is two boots, each with a separate power. Main boot is the initial power up last two or three seconds, and then system boot.. Believe main boot is sending power off display and then power on display on system boot.
after trying unsucessfully many times to get LVM to work I decided to go back to stock oppo recovery. I saw an option to unify memory in the oppo recovery and clicked that. My screen flashed for 30min with no reboot. I shut it down. This could have where it went wrong.
Now I cant boot into any recovery. Just stays stuck on the oppo logo. i DO have fastboot mode though and I CAN execute commands via the terminal/cmd prompt using adb/fastboot.
If I flash twrp, i can see it tries to boot into twrp with a blue flash of a screen but immediately it goes back to the oppo logo and stays there forever.
If I flash oppo recovery again, i can see it tries to go into oppo recovery but then the screen starts flashing bits and pieces of what I can make out as the oppo recovery.
Tried the unbrick method. I assume my memory is messed up because i tried to unify memory via the oppo recovery? I cant seem to do the unbrick method here: http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067. Tried it with win10 on test mode and cant get his specific driver names to work/show up. Shows up on mine as Marshall London boot loader or Android bootloader.
Also used the repartition tool repair scripts: http://community.oppo.com/en/forum.php?mod=viewthread&tid=20271&extra=. That did nothing. Black screen for about 1hr. Still have fastboot right now though. Still doing the same thing.
Any way to solve this? Thanks in advance to the pros at XDA!
THIS WORKED!! It took me very long to figure this out!!
http://community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=&page=1
For that tutorial i had to deviate from the instructions ironically, if i held down power + up, it would take me to fastboot and i could NOT install the right drivers and it would come up as Marshall London Device (windows 10 with TESTSIGNING turned on). All I had to do was just plug into usb and NOT press or hold any buttons on the phone. Then it showed up as QHSUSB_BULK in device manager and I can proceed with this tutorial.
So Here are the steps
1. My bootloader got unlocked.
2. I Installed factory preloader and lk images.
3. Rebooted to Fasboot and flashed TWRP 3.3.1-0924 by wzsx150 (the only Android 9 recovery that didn't get removed immediately after flashing and rebooting for 1st time to get to recovery).
4. Formatted Data, Closed AVB 2.0 and Signed TWRP.
5. Rebooted to Fastboot and flashed stock EEA Android 9 (11.0.3.0) from Global (11.0.6.0) and reflashed factory preloader and lk.
6. Rebooted to recovery, Formatted Data, Closed AVB 2.0 and Signed TWRP.
7. Using ADB sideload from Twrp Installed EEA Android 10 (11.0.2.0).
8. Rebooted into fastboot Installed Updated TWRP-3.3.1-1210 (by wzsx150).
9. Rebooted into fastboot and flashed misc.bin from same zip (according to bat file inside it should get flashed after recovery but I forgot.)
10. BRICKED. Booted to Redmi logo for 3 seconds and rebooted infinitely.
This type of brick in 4pda.ru according to google translate can be mitigated by letting battery drain and then enter DA download mode using SP Flash Tool.
I've Used the tool several time so I thought Okay no big deal.
So This is what I tried:
11. Pressed download button
12. Connected USB Cable to phone.
13. Device pauses a second (Probably for SP Flash Tool to respond) then doesn't enter DA (Unlike previous times) and screen brighten for a second or two but then turns off and repeats this process forever.
I've been using Drivers provided by Microsoft Update Catalogue but tried all the drivers on 'MTK Usb Driver v1.0.8' and 'Mediatek_Driver_Auto_Installer_1.1352.00' after disabling Driver Signature Enforcement. but even though drivers are installed they don't get loaded and after force installing them in add legacy drivers they are their but have yellow triangles and their Location lists as 'Unknown' and status as 'This device cannot start. (Code 10)'. Tried Removing them after adding them as a site suggested but that didn't work either.
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
wang1chung said:
I learned the hard way to never mismatch partitions with this phone. I thought having the factory preloader and lk1/2 would protect me but no.
When you say brick, do you mean you have a completely black screen with only the notification LED turning on when you plug it in?
Grab a bootable Linux image and use that on a USB stick to eliminate the driver issue you're having. Interface is identical
Click to expand...
Click to collapse
So I tried Ubuntu. Problem isn't from Drivers. It's because my Windows or linux didn't ever got a chance to enter fastboot so they can load preload drivers properly.
In Windows, Mediatek USB Port is the only driver that get loaded, and that for only an instant then it disappears in Device Manager.
In Linux according to this Tutorial everything is fine but SP Flash Tool gives me a " ERROR : STATUS_ERR (-1073676287) , MSP ERROE CODE : 0x00. "
Based on this chinese site I should find my Vendor Id and Product Id specific to my system (or is it my chipset?) and then change some files but how do I get linux to recognize mediatek usb device first when It needs to enter fastboot for that to happen.
Is there any way to manually add it?
EDIT: So After some reading I realized that I have to get my phone to fastboot first to get the drivers recognized. In windows as far as I know there is no way for manually adding 'Location' to Drivers. what about Linux?
I think you're talking about a soft-brick and I'm talking about a hard-brick. If you can get to fastboot, it's a soft-brick.
Hold the volume down and power buttons simultaneously for 1min and see if your screen changes.
Don't worry about the Linux drivers, if your phone is in the correct mode, it'll work.
I don't think it's a Soft-Brick (unless Hard-Brick means even the display not turning up at all), Holding them for a minute with battery charged doesn't do anything. As soon as it boots back up it starts getting caught in Booting until Redmi logo and staying there for 2-3 seconds then reboots. I tried to hold Volume Down + Power for 3 minutes while caught in this bootloop but no fastboot. I'll retry when battery discharges again. first without usb cable attached then with.
Thanks for taking time to work this through with me. Nowadays with all service centers being closed it's really a nightmare to have something you need on internal storage and not being able to access it. First thing I'll do after this is to buy a 128GB SD card to store the important stuff.
By the way should I just use the Live Ubuntu or Install it to see if the problem is from being a live image.
When I hard bricked my phone, I didn't have anything but that white led when I plugged it in. If you have the redmi logo, should mean there is hope. I've only ever entered DA mode when I had a hard brick.
This might be one of those situations where letting the battery drop to 0% would allow you to access fastboot. MiFlash only works in fastboot and DA mode I believe. What happens when you hold volume up and power for a minute while plugged in to your computer? Run "ADB devices" to start the adb service first
I doubt it would make a difference live to installed, but it's your call if you have the time.
With Phone in Bootloop mode Holding Either Vl+ and Power or Vl- and Power doesn't make a difference.
With Phone Off and USB detached It's the same.
With USB attached Vol+ and Power for over 3 Mins result in Device Manger listing 'Mediatek USB Port' for as long as display remains 'dark but bright' (for 2-3 seconds then shuts down and turns itself back on). removing it when phone suddenly shuts down. when USB is detached phone remains shutdown.
With USB attached Vol- and Power for over 3 Mins result in Phone's Display Brightening for 5 seconds no device listing in Device Manager nor entering fastboot or being recognized by adb or fastboot (set on a permanent re-checking by a cmd script). then phone shuts itself down and back on.
LED situation:
With Vol+ and Power with USB attached LED when phone is Off is Fullbright. When Display Brightens It turns off.
With Vol- and Power with USB attached LED when Phone is Off Blinks Once Fullbright and then remains Semi-bright whether phone is on until shutdown and the Blinks Fullbright again.
I Live in Iran and with sanctions there is no way to pay anyone overseas. Unless they're willing to risk accepting cryptocurrencies from an Iranian , my only chance if I can't work it out is to wait till unofficial service centers here open.
Your phone only being detected for 5 seconds is supposed to happen. It checks for a signal from so flash and if it doesn't see it, drops off.
I'm not sure paying someone to remotely flash your phone will work if SP Flash isn't even trying or detecting your phone. With mine, it would detect and try to flash (red bar sitting at 100%) before throwing an error.
Try letting your battery die, if that doesn't work, maybe the test point mod will work. Otherwise, I think your only option is a service center.