Help me bring back to life my phone - G4 Q&A, Help & Troubleshooting

Hello,
So, i was trying to install root on my LG G4, version H815 (no letters/numbers after)
I did successfully unlocked my bootloader (info message on left top corner when booting) - official LG unlock
Booted into TWRP - twrp-3.0.2-0-h815 from ADB
- Installed UPDATE-SuperSU-v2.46.zip (which is located on internal storage) from TWRP - https://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip
- Clear cache (dalvik)
- Reboot
Phone started booting, and got stuck on the LG logo
I did try to get it recognized in download mode and I did try to enter recovery mode (but I didn't install TWRP, only boot into it.. so I was left with the "default" one)
My phone doesn't enter recovery mode (I get the dead android bot with red exclamation mark)
At this step, somehow ADB recognized my phone, and I tried installing SuperSU again, and once again same thing happened.. I got stuck on LG logo
After this until now, I'm not able to:
- see my phone in ADB
- download mode with LGFlashTool2014.exe to flash .kdz "Europe OPEN H81510D.kdz" - getting error on LG Mobile Support Tool - "Upgrade stopped due to an error'"
I was following this: http://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
Currently I'm trying all the steps from here http://forum.xda-developers.com/g4/help/lg-g4-stuck-bootloop-t3268734
I just wanted to ask, is there a better way? Is there a working way?
Thanks, any help appreciated!

What firmware were you on? LP or MM. If the firmware was MM then you should have used SU 2.52 otherwise you end up as you are now.
Sent from my LG-H815 using Tapatalk

Stransky said:
What firmware were you on? LP or MM. If the firmware was MM then you should have used SU 2.52 otherwise you end up as you are now.
Sent from my LG-H815 using Tapatalk
Click to expand...
Click to collapse
I was on MM didn't saw that part..
Thanks for pointing it out!

BrainCrasher said:
I was on MM didn't saw that part..
Thanks for pointing it out!
Click to expand...
Click to collapse
You should also have flashed any custom kernel first that will allow you to not boot but install TWRP and then easily root. To flash firmware for G4 we use LG UP, nor Flashtool2014 and Mobile Support Tool ( G4 is not even compatible with it! It says on their website that you have to download LG Bridge)

I fixed it by using LG Bridge
- Update error recovery option
It installed android 6.0 on it
Then I used BETA-SuperSU-v2.67-20160121175247.zip for root, and everything seems to be fine
Thanks for your help!

Related

Device ID'd as "palman" or "awifi" - cannot flash ROM

So, I have root (confirmed), unlocked bootloader (I guess), TWRP 2.7
I tried:
- omni-4.4.2-20140514-v500-HOMEMADE.zip
- cm-11-20140618-NIGHTLY-v500.zip
- cm-11-20140619-INFECTED-v500.zip
But it always says, that my device is a "palman" and no "v500". I made it to get the Slim-v500-4.4.3.build.5.9-INFECTED-20140616-1124.zip installed once, but then I ended up in a Boot-Loop wit the original "LG Logo - Security Error" screen. So I reverted everything with TWRP. Now I can only boot in TWRP and cannot get any ROM to run.
Any suggestions?
Addition:
Now I was able to Flash cm-11-20140618-NIGHTLY-v500.zip, although i edited the update script and removing the first line where it verifies the model. So it flashed the ROM correctly, but upon restarting, I ended up with the 'official' "LG Logo - Security Error".
So I did a restart via Power+Vol- into All three buttons. The Factory Reset screen comes up, when I hit Vol+ twice I gets me back into TWRP, but on the way there it also shows up the
Secure booting Error!
Cause : Device Unlock!, so Boot Success!!!
.... and now?
Aight, Now with the LG Mobile Support Tool and using Download-Mode on the device, I am hopefully able to go back to stock... Needs to DL 1,2 gig though -.-
So I guess I'll stick with the stock, except anyone is able to tell me where I went wrong...
I'm thinking:
1. towelroot
2. flashify for TWRP
3. choose rom and flash
right? Or do I have to do something extra to the bootloader?
AhNe said:
Aight, Now with the LG Mobile Support Tool and using Download-Mode on the device, I am hopefully able to go back to stock... Needs to DL 1,2 gig though -.-
So I guess I'll stick with the stock, except anyone is able to tell me where I went wrong...
I'm thinking:
1. towelroot
2. flashify for TWRP
3. choose rom and flash
/right? Or do I have to do something extra to the bootloader?
Click to expand...
Click to collapse
If you have the palman device, you have the Google Play edition, and should not be trying to install Roms for the 500 device. All that is out for the palman device is the sleekai kernel, and a base ROM with no extras. If you have the palman device, install the sleekai kernel and exposed and you will be better off anyway.
Is palman is the one have v510?? so awifi is v500 that i have, lol.
I got it to work after all and was able to install the latest CM nightly. After I did the reinstallation of everything (with the LG tool), I did the following:
- root via towelroot
- installed TWRP 2.7.0
- installed TWRP 2.7.1
- installed CM via TWRP 2.7.1
Still, I have no idea why it was recognized wrong during the first tries...
AhNe said:
I got it to work after all and was able to install the latest CM nightly. After I did the reinstallation of everything (with the LG tool), I did the following:
- root via towelroot
- installed TWRP 2.7.0
- installed TWRP 2.7.1
- installed CM via TWRP 2.7.1
Still, I have no idea why it was recognized wrong during the first tries...
Click to expand...
Click to collapse
Good to hear bro.
@AhNe
Just to get it clear. You have a v500 and you rooted it with towelroot and flashed the recovery sucessfully with Flashify ?
something wrong in Loki, try to give it a search...
Sent from my LG-V500 using Tapatalk

VK810 Download Mode Boot Loop =(

Here's the situation.
-gpad on official verizon kitkat. rooted with TWRP installed.
-tried doing the OTA update
-upon reboot for OTA update, boot loops to twrp
-flashed stock recovery.img from TWRP terminal
-boot loop fixed and able to boot into original OS before OTA update attempt
-tried OTA update with stock recovery but fails @ 5% with error code ERR:0x13E
-used the LG Mobile Support tool to try and manually update
-goes into download mode
-update fails
-now only reboots to Download Mode
-tried all button combinations to get into any other mode. fails.
-even tried taking apart and pulling battery
Result: still stuck in download mode.
Any suggestions guys?
Just in case someone else is having this issue, I'm not deleting this post.
looks like I got it fixed.
I ran lg mobile support tool on a diff computer and this time it went through.
All up and running again.
I got myself in this same bootloop. Mind sending me the recovery.img file or showing me the way to the correct LG Mobile Support Tool?
eldiablo1 said:
Just in case someone else is having this issue, I'm not deleting this post.
looks like I got it fixed.
I ran lg mobile support tool on a diff computer and this time it went through.
All up and running again.
Click to expand...
Click to collapse
How did you get it to up and running again?
I'm stuck in twrp...
alphakp295 said:
How did you get it to up and running again?
I'm stuck in twrp...
Click to expand...
Click to collapse
I had to wipe FOTA... thanks to id10terror
1. Boot into TWRP
2. Go to Advanced, then Terminal Command
3. Browse to Folder: /dev/block/platform/mdm_sdcc.1/by-name
4. Hit Select button
5. Now in the text field type "dd if=/dev/zero of=./fota" without quotes and Hit "Go"
6. Reboot system
You are a life saver! Thanks.
Thanks a lot from me as well, got me out of the boot loop I created by trying to update using an OTA on my rooted LG G Pad and these commands got me back up and running..
Just ran it now thank you Sir! ?
Pad boot in Download mode only.
What version of LG Mobile Support tool need for restore firmware?
Automatically don't install devices in windows (Win8) after connect.
Alexander Kalinin said:
Pad boot in Download mode only.
What version of LG Mobile Support tool need for restore firmware?
Automatically don't install devices in windows (Win8) after connect.
Click to expand...
Click to collapse
Hi! What variant of the G Pad 8.3 do you have? I would use LG Flash Tool 2014 instead of the official tool, and download the latest official KDZ file to use with it, made for your variant.
You'll have to download the drivers for your variant from LG's website, reboot the PC, then plug the tablet into the PC while it's in Download mode. Can take 1 to 10 minutes to load the driver. Then use the flash tool I mentioned.
Sent from my VK810 4G
Thanks! VK810.
Properly install driver on another PC and recovery by Support Tool.
Alexander Kalinin said:
Thanks! VK810.
Properly install driver on another PC and recovery by Support Tool.
Click to expand...
Click to collapse
You're welcome. So you got it sorted out?

G3 D855 - System ok - Stuck in TWRP logo - Stuck in Download Mode

Guys I have serious problems with my LG G3 D855 - From Brazil
A long time ago I can't enter download mode because the phone can't pass the download mode logo (?), just like 'd.jpg'.
That wasn't a problem till the same occours in the recovery, just like 't.png'. No matter how much time, the phone keeps stuck in this screen.
My system is CM 13, I can't install any update or kdz or tot file. The system boots ok, the problem is that CM 13 is nightly and some apps doesn't work properly. I've tryed flash original recovery, the new twrp 3.0, the old twrp 2.8.5, and still get this. Tryed clear cache from adb but no sucess.
ADB through system still work fine, that can be a path to my solution.
Anyone can give a hand?
Anyway, Thanks!
Download mode might be about driver
Twrp did you install right version
Reccommend reinstall whole system kdz or tot flash
Sent from my LG-D855 using Tapatalk
Duckscreen said:
Download mode might be about driver
Twrp did you install right version
Reccommend reinstall whole system kdz or tot flash
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Can you show me the correct driver? I've already installed two drivers for this phone and the Google adb drivers

Lg g3 700 fastboot mode started when going to recovery

Hello I hope someone could help me.
I have an lg g3 D855 international version, with kit kat 4.4.2 and its the 10e version.
I've root my device in order to install new custom rooms. At first I wanted to go to android marshmallow official and wanted to do the flashing with lg flash tool, but in every computer I have, it does not working, its either stuck in 2% and then it fails, or 4% and then it fails, and I tried to erase an install the new drivers and the old ones in the computer... But I couldn't get it to work. So I decided to root my device, and install twrp recovery, so I did. First I try to install the latest version of twrp, this I did it directly from the phone via TWRP manager. It was supose to work... But when I finish installing and went to recovery.. It went to a black screen saying "[700] fastboot mode started" or sometimes "[760] fastboot mode started" to my surprise the phone is not softbrick. I removed the battery and then reboot the phone and it works... But everytime I go to recovery or tried to install a new bump recovery... Because i thought that was the problem is still the same. I tried to install a new recovery with ADB but when I put the file path in order to install it... It said it couldn't find the recovery img in the path... But it was there... And I tried, but couldn't get it to work. I have some experience with custom roms on samsung galaxy s3, but change my phone, and this lg g3 is really making me crazy.
Thank you very much in advanced.
Any updates? Im having the same exact problem (d851)
In which computer you are trying the process. Which windows is installed on computer that you are using for installing stock rom.
Which guide you are following to install stock rom. Have you unlocked your device for bump, if not follow the guide.
http://forum.xda-developers.com/lg-g3/orig-development/bump-unlock-lg-g3-twrp-d852-d852g-f400-t2900614
I am dead sure that your board is not d855.open your phone to confirm this.that is the reason your twrp is not compatible with your board.
droidrzr1610 said:
Any updates? Im having the same exact problem (d851)
Click to expand...
Click to collapse
Same problem for me.
I was using TWRP for weekly update of LineageOS 16.1 on D855 with no problem.
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App.
Then I tried to boot in Recovery mode and I got black screen with the message:
[700] fastboot mode started
I tried older version with no success installing them with ADB or TWRP App.
---------- Post added at 06:55 AM ---------- Previous post was at 06:32 AM ----------
Polex73 said:
Before updating to Lineage17, I updated it to twrp-3.4.0-0-d855.img (https://eu.dl.twrp.me/d855/) using TWRP App..
Click to expand...
Click to collapse
I noticed the twrp-3.4.0-0-d855.img file was corrupted.
I downloaded from the https://eu.dl.twrp.me/d855/ directly to the phonr.
Problem solved

TWRP for LG G3 D855 - Lollipop

LG G3 D855 (***Lollipop***) Phone is rooted, and TWRP was installed. Recovery version currently installed is 3.0.0-0. When I try to go to recovery mode the phone displays ' Secure boot error' followed by a black screen. The light blinks red and blue. Could anyone help me with the right recovery file. I want to install Fulmics ROM(UX 5.0)
Did you install twrp using autorec?
Sent from my LG-D852 using XDA Labs
I try to install with Flashify and AutoRec and have same result. My phone have stock Lollipop 5.0 and its rooted.
lg g3
djilija.eeprom said:
I try to install with Flashify and AutoRec and have same result. My phone have stock Lollipop 5.0 and its rooted.
Click to expand...
Click to collapse
does it goes in downloadmode?
does it working normally or only getting security error when u enters in recovery
kalpesh patil said:
does it goes in downloadmode?
does it working normally or only getting security error when u enters in recovery
Click to expand...
Click to collapse
Only getting security error. Blinking led in two colors and I must put battery out...
Try pressing on the Volume Down a few times when you get stuck there. Please let me know if anyone has a solution for this problem. In my case I used King Root to gain root access. I believe it`s related to the root access itself.

Categories

Resources