Database Users

[Q] Unable to boot Stock based ROMS [D800]

Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA

vish9 said:
Hey everyone, sorry if this question has been answered already. I have sifted through pages and pages in this forum and haven't found a solution for my D800.
My G2 is rooted, with TWRP installed. I was successful in flashing Paranoid Android v4 beta 4, and 5. The problem arises when I try to flash LG Stock based ROMS. After TWRP says flashing was successful and I try to reboot, the screen shows LG logo for a second and turns blank!! That's it just a clear black screen, and the ROM doesn't boot at all.
The ROMs I tried and failed to boot:
1. Aeon
2. Korean stock based rom
3. Scott's CleanROM
4. Rayglobe 3.2
5. Rayglobe Flex ROM v4
Now, I know that sometime ROMs take time to boot on the first run, so I even tried leaving it at the blank screen for 15-20 mins with no result. Since it has been the same result for multiple ROMs, it definitely isn't a bad install or a bad ROM download either. I hope not
Is there anything I am missing in the steps? All ROMs were installed after factory resetting through TWRP (no dirty flash). I am baffled with this, please let me know if I need to revert to software version "d" for these ROMs to work?
TIA
Click to expand...
Click to collapse
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?

sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also

joebob296 said:
Did you factory reset after as well? If I recall correctly Paranoid Android is AOSP. What kernel are you running?
Click to expand...
Click to collapse
Exactly, AOSP ROMs are booting up fine but not the Stock based ones.. I am not flashing any kernels, just the ROM, so I'm assuming it will run on either the stock kernel or the kernel included in the ROM zip?
Have you been successful in installing such ROMs? Am I missing something in the wiping part? Only been doing the factory reset in TWRP before installing any ROM.

Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk

rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Oh, I hadn't thought about anything being wrong with the recovery.. Always assumed it gets the work done
How do I find previous versions of TWRP compatible with D800?

joebob296 said:
Check m
And make sure that you are running the stock kernel. Are you on the 10o update?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yes I am on 10o.. Does it have issues with installing other Stock ROMs? If yes, I'll try to follow the thread on using LGFlash tools, I've never done that before. Hopefully its not much difficult to follow the instructions.

That is one of the easiest guides to follow. Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk

joebob296 said:
That is one of the easiest guides to follow. Me sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Thanks.. I'll try to do it tonight and post my results here.

joebob296 said:
Be sure to follow the correct set of instructions(depends on carrier) and download the the 10d version.
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
I'm stuck in the process! Can't change the com port number to 41. The guide is pretty easy to understand. But when I put my phone is download mode and try to change the com port number, it says I don't have the write privileges for this device's setting. I've tried it on both Win 7 and Win 8 laptops, with LG mobility drivers installed.
Is there something in the phone settings I need to enable so that I get the write privileges to change com port number?

Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk

SOLVED!
joebob296 said:
Do you have administrator privileges?
Sent from my LG-D801 using Tapatalk
Click to expand...
Click to collapse
Yay!!! Finally did it!
Issue 1: If faced with write privileges for com port (tried successfully in Win 8)
Solution: After going in to com port properties, click "change settings" and there is the option to change com port number.
Issue 2: Once the port number was changed to 41, rest of the instructions are easy to follow on this thread http://forum.xda-developers.com/showthread.php?t=2633150
Once on D80010d, I rooted with ioroot22, and installed recovery using FreeGee. Just installed Rayglobe 3.2 minutes ago, and it finally booted up!!!
So, the bottomline is that go back to D80010d if you wanna play with Stock based ROMs! I flashed with TWRP 2.6.3.3, so the fault is not with the recovery. That much I can confirm
Thanks for the suggestions guys. Thread solved I guess.

Great. Glad to hear it.
Sent from my LG-D801 using Tapatalk

rquiett said:
sounds like you are onn the 10o update. You will need to flash back to stock 10d with lg flash tool and then root and install recovery again. Then you should be good to go on flashing roms. I know that some of the newest versions of TWRP and Philz have issues flashing some roms too so that may also be the cause. If you downgrade the recovery you have to the version right before it may fix your issue also
Click to expand...
Click to collapse
Thanks for the input. Before I flashed back to D80010d today, I installed older versions of Philz and TWRP but neither helped. So downgrading was sort of a compulsion, in my case at least.

and the moral of the story is, unless you are getting an android version upgrade in the update, do not take the update.

[Q] How to enter TWRP on stock Kitkat firmware?

Hi Guys,
So I tried the new stock Kitkat firmware for my d802. Flashed the KDZ through support tool. I lost root as expected.
Then I started to miss root and control over my phone, so I wanted to go back to Jellybean.
After some difficulties I got the support tool working in offline mode. Flashed Jellybean stock KDZ.
Rooted the phone again and installed recovery.
Converted the stock KitKat rom to a flashable zip, and copied it to SD card.
I flashed the zip and all went fine.
Anyhow, when I wanted to return to recovery it did a factory reset instead, and now I can start all over.
Do we have a solution to this problem?
Thanks.
A

szaboagoston said:
Hi Guys,
So I tried the new stock Kitkat firmware for my d802. Flashed the KDZ through support tool. I lost root as expected.
Then I started to miss root and control over my phone, so I wanted to go back to Jellybean.
After some difficulties I got the support tool working in offline mode. Flashed Jellybean stock KDZ.
Rooted the phone again and installed recovery.
Converted the stock KitKat rom to a flashable zip, and copied it to SD card.
I flashed the zip and all went fine.
Anyhow, when I wanted to return to recovery it did a factory reset instead, and now I can start all over.
Do we have a solution to this problem?
Thanks.
A
Click to expand...
Click to collapse
We are waiting for LG to release KitKat kernel sources for D802 before a solution can be made, but it does require you to go back to JB again and then flash a KitKat rom with the modified kernel in order to keep your custom recovery

GizmoKaca said:
We are waiting for LG to release KitKat kernel sources for D802 before a solution can be made, but it does require you to go back to JB again and then flash a KitKat rom with the modified kernel in order to keep your custom recovery
Click to expand...
Click to collapse
Thanks. I thought that if it was a flashable zip, I could always return to custom recovery, but of course it is the content of the file that needs to be modified. I'll wait.

GizmoKaca said:
We are waiting for LG to release KitKat kernel sources for D802 before a solution can be made, but it does require you to go back to JB again and then flash a KitKat rom with the modified kernel in order to keep your custom recovery
Click to expand...
Click to collapse
it would not be just a modified kernel it would be an entirely modified zip with parts from 4.2.2 and 4.4.2 so that it can support custom recovery like in jb but be able to boot into kk in fact the only reason we need the kernel source is because we have to add some lines so it can allow jb and kk partiotions to work together
---------- Post added at 11:30 AM ---------- Previous post was at 10:33 AM ----------
D802 kit Kat kernel source just came out a few hours ago so soon you guys should see a stock kk Rom with root and recovery support
Sent from my LG-D800 running kitkat using XDA Premium 4 mobile app

Can't wait to see that. Is there any downsides to this method or is all working well with this work around?
Sent from my LG-D802 using Tapatalk

ephumuris said:
Can't wait to see that. Is there any downsides to this method or is all working well with this work around?
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I have been using it but for att and have not experienced any troubles and I also know of a few people who have already flashed roms whitput trouble also it seems like the g pro 2 rom might be the first to seeing custom recovery on d802 since someone there already made a patch but has not tested it yet and thus has not released it yet

[Q] CM11 Problem.. Help Needed

Hi all,
I am interested in the CM11 ROM. Last night I spent 6hrs trying and failed, epically.
Here is what I did already:
1. Downgraded from 4.4.2 back to factory
2. Successfully rooted
3. Installed ROM Manager
4. Successfully downloaded CM11 and latest GApps
Then when I tried to boot into recovery it kept going to a screen with a little android guy lying on his back with a red triangle!!! I tried six times.
I got frustrated and just updated back to 4.4.2 and have been dealing with it. I am still rooted and have been able to remove my bloatware and other things you need root access for.
Any thoughts or help as to how I can install the CM11 rom?? I am happy running NovaLauncher and using DynamicNotifications to approximate it but really want to try out CM11.
Cheers and thanks!

Lucky there is no way to root on 4.4.2 yet or atleast no Recovery's yet it could be worse you're atleast rooted and it didn't brick your phone
Sent from my VS980 4G using Tapatalk

Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.

JRJ442 said:
Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.
Click to expand...
Click to collapse
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!

follow this step..
http://forum.xda-developers.com/showthread.php?t=2681205

android_nashville said:
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!
Click to expand...
Click to collapse
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.

My first guess was that you missed the flashing the custom recovery step, which people above me have already helped ya out on. For being new to Android you did fairly well, you just missed that one step.
Good luck!

JRJ442 said:
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.
Click to expand...
Click to collapse
thanks, forgot to mention it was only for D802 :good:

zekurosu said:
thanks, forgot to mention it was only for D802 :good:
Click to expand...
Click to collapse
I have an ATT D800 running 4.4.2. I can't decide whether its worth it to flash back to 4.2.2 to try again. Pretty happy with NovaLauncher + widgetlocke and fairly closely approximates what I am looking for.
For what its worth, I was in 4.2.2 when I tried the first time and failed. I think mackster is right, I didn't flash the custom recovery. I basically flashed back to 4.2.2->rooted->tried to boot into recovery (OVER and OVER) then gave up and upgraded back to 4.4.2.
Thanks for all the help. At least I now have a rooted phone and have been able to do some cool stuff with that. My goal is to get nexus 5 software in an LG G2 body (battery, camera, etc)

@android_nashville There's a way to have the best of both worlds. You can flash back to 4.2.2 (10d preferably) root, flash a custom recovery with Flashify or FreeGee. Both available on the play store. Then actually update to 4.4.2 following this thread http://forum.xda-developers.com/showthread.php?t=2483043. Eventually, if you want to flash custom ROMs you're going to have flash back to 4.2.2 and do this process regardless. The 4.4 aboot image (bootloader) can't be bypassed with Loki. Its been blocked. But some brilliant devs basically found out they can make a hybrid setup, with the 4.2.2 aboot, and everything else 4.4.2. This way you can have the ability to flash custom recovery, kernels and ROMs.

Easy steps

I'm new to the g2 tinkering scene....
I have rooted my d802, installed and ran autorec and updated TWRP. And my Android version is 4.4.2
I want to change the rom, however on this phone everything seems so difficult....with having to change bootloaders and radios etc etc
What's the easiest way for me to begin? Is there a rom that I can flash with ease without having to mess about too much until I have learnt a little more

Bump anyone?

Nope not really. The easiest thing to do first is download the bootloaders and the modems. I suggest for you to download nevax bootloader changer and just google lg g2 d802 modems.
Just read every OP carefully while flashing and you will be fine. You can't flash roms in the lollipop bootloader so you have to first downgrade with autorec d802.
First root with lgroot it should work.
Downgradecusing autorec then you should also be able to enter twrp. Enter twrp using the recovery combination for jellybean. So with power+ volume down. ( small note, jellybean and kitkat have different recovery mode key comhinations butnthe kitkat20h should have the same as jb I believe.)
Once you entered recovery and downloaded the right bootloader, bootstack, modem then you will be able to flash the roms ya want. Ofcourse all for d802.
Some additional information
Download all the things for the d802, another model can cause so soft or even hardbricks so do it carefully.
Download autorec for d802 as the wrong version could cause an hardbrick.
Read every OP good and everything from what you are downloading. It will be hard from the beginning but after a while you can just do it like chewing gum.
If you are flashing a rom and it says that it fails and something about loki then you need jellybean bootloader.
Bump roms are all for kitkat bootloader.
Most of the newer roms are all using kitkat bootloader so I suggest to stick with the new roms so you don't have to change everything.
Watchout with the weird named vietnamese stock roms as some of them may contain bootloaderstack (additional files next to the bootloader itself) which could cause other rome not to work properly after yu flashed it so you will have to use autorec, some revert zip or some bootloaderstack zip for the d802.
Lonf stort but I hope this is all the information you need.
Verstuurd vanaf mijn LG-D802 met Tapatalk

wulsic said:
Nope not really. The easiest thing to do first is download the bootloaders and the modems. I suggest for you to download nevax bootloader changer and just google lg g2 d802 modems.
Just read every OP carefully while flashing and you will be fine. You can't flash roms in the lollipop bootloader so you have to first downgrade with autorec d802.
First root with lgroot it should work.
Downgradecusing autorec then you should also be able to enter twrp. Enter twrp using the recovery combination for jellybean. So with power+ volume down. ( small note, jellybean and kitkat have different recovery mode key comhinations butnthe kitkat20h should have the same as jb I believe.)
Once you entered recovery and downloaded the right bootloader, bootstack, modem then you will be able to flash the roms ya want. Ofcourse all for d802.
Some additional information
Download all the things for the d802, another model can cause so soft or even hardbricks so do it carefully.
Download autorec for d802 as the wrong version could cause an hardbrick.
Read every OP good and everything from what you are downloading. It will be hard from the beginning but after a while you can just do it like chewing gum.
If you are flashing a rom and it says that it fails and something about loki then you need jellybean bootloader.
Bump roms are all for kitkat bootloader.
Most of the newer roms are all using kitkat bootloader so I suggest to stick with the new roms so you don't have to change everything.
Watchout with the weird named vietnamese stock roms as some of them may contain bootloaderstack (additional files next to the bootloader itself) which could cause other rome not to work properly after yu flashed it so you will have to use autorec, some revert zip or some bootloaderstack zip for the d802.
Lonf stort but I hope this is all the information you need.
Verstuurd vanaf mijn LG-D802 met Tapatalk
Click to expand...
Click to collapse
Well that's a fair bit to take in, I will read everything you wrote a few times over before I do anything.
I was looking at a rom, it doesn't say anything about bootloaders etc....and its 4.4.2, so can I not flash this without changing anything?
http://forum.xda-developers.com/showthread.php?t=2758437

mrcarlxx said:
Well that's a fair bit to take in, I will read everything you wrote a few times over before I do anything.
I was looking at a rom, it doesn't say anything about bootloaders etc....and its 4.4.2, so can I not flash this without changing anything?
http://forum.xda-developers.com/showthread.php?t=2758437
Click to expand...
Click to collapse
Its an old rom so it's based on jellybean sourcecode so I suppose that you need jellybean bootloader and bootstack. And probably lg g2 d802 kitkat aosp modem.
Verstuurd vanaf mijn LG-D802 met Tapatalk

wulsic said:
Its an old rom so it's based on jellybean sourcecode so I suppose that you need jellybean bootloader and bootstack. And probably lg g2 d802 kitkat aosp modem.
Verstuurd vanaf mijn LG-D802 met Tapatalk
Click to expand...
Click to collapse
Damn it, nothing is ever easy lol

mrcarlxx said:
Damn it, nothing is ever easy lol
Click to expand...
Click to collapse
Nope it isn't but once you know it it is easy and custom rom flashing is worth it. You'll enjoy it
Verstuurd vanaf mijn LG-D802 met Tapatalk

[Q&A] LG G2 Bootstacks

Q&A for LG G2 Bootstacks
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for LG G2 Bootstacks. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Rashed97 said:
Should be the same key combo. I use the same on on my D802
Click to expand...
Click to collapse
so the D802 BUMPed zip is also JB bootloader,right? I compared the aboot.bin of the bump one with the loki one, it's the same MD5. Could you please replace the JB bootloader in bump zip to KK bootloader? Because if we need JB bootloader we will flash the loki zip instead of the bump one,but if we need KK bootloader we have nothing to flash.

tblinshi1234 said:
so the D802 BUMPed zip is also JB bootloader,right? I compared the aboot.bin of the bump one with the loki one, it's the same MD5. Could you please replace the JB bootloader in bump zip to KK bootloader? Because if we need JB bootloader we will flash the loki zip instead of the bump one,but if we need KK bootloader we have nothing to flash.
Click to expand...
Click to collapse
Sure, thanks for pointing it out
Sent from my HTC One M9 using Tapatalk

Can I flash one of the two bootstack independently from the bootloader that I' m using right now? Because I' m running KK bootloader and I dont' t understood if I can flash the bootstack with JB bootloader without troubles

ironmaiden97 said:
Can I flash one of the two bootstack independently from the bootloader that I' m using right now? Because I' m running KK bootloader and I dont' t understood if I can flash the bootstack with JB bootloader without troubles
Click to expand...
Click to collapse
Yeah it doesn't matter
Sent from my SM-P607T using Tapatalk

I have cloudy g2 3.3 5.0.2
If I want flash cm 12.1 muat flash boot stack
Loki or bump?

Hello, I'm running cm12.0 on ls980 . came from stock kk , used autorec , recovery is now 2.8.6.1. So I assume I need to flash the kk bootstack. If that's correct, do I flash bootstack first then cm12.1? Do I need to wipe cache after flashing bootstack and before flashing 12.1. Or do I not wipe cache at all? And do I need a different gapps then what I've been using for 12.0? So sorry for being a pain. Thanks in advance
Sent from my Lenovo TAB S8-50F using XDA Free mobile app

purpleurkle said:
Hello, I'm running cm12.0 on ls980 . came from stock kk , used autorec , recovery is now 2.8.6.1. So I assume I need to flash the kk bootstack. If that's correct, do I flash bootstack first then cm12.1? Do I need to wipe cache after flashing bootstack and before flashing 12.1. Or do I not wipe cache at all? And do I need a different gapps then what I've been using for 12.0? So sorry for being a pain. Thanks in advance
Sent from my Lenovo TAB S8-50F using XDA Free mobile app
Click to expand...
Click to collapse
Or can somebody possibly tell me what bootloader I have. Kk or jb?
Sent from my LG-LS980 using XDA Free mobile app

I'm running AICP 5.1.1 on my LS980. The only thing other than the ROM and gapps that I ever had to flash was a modem. What is a bootstack? Would it improve my experience? If so, which one should I flash?

wich one i have or how doi check. i had lollipop 5.0.2 d800 30c i think..now on cloudy 3.3

not sure what to do
ok so let me start off with that i am sorry if this answer can be found on another forum or has been already answered, i have been looking for hours and have not found an answer. so the question is what happens if the bootstack fails to flash what steps can i take to fix this? and if my LG G2 doesn't boot after flashing this would there be a way to fix that? btw i wouldn't like to have to get a jtag repair if i mess this up. thanks in advance!

Hi guys.. I have a question. I am on cloudy g2 3.3 and i want to try CM 13.. I have done a full backup or the rom. If, after the flash of CM, I would go back to cloudy, have I to flash some bootstack or bootloader?
Inviato dal mio LG-D802 utilizzando Tapatalk

Dear Helper,
This question might not belong here, but I'm looking for an experienced response.
I was on cloudyG2 2.2 KK on LG G2 D800 (AT&T). Updated bootloader to "bootstack-d800-KK_20y-v1.1-blastagator-signed.zip" via TWRP 2.8.7.1 and then flashed CloudyG2 3.3 LP. Now facing a problem which is;
When I reboot the phone from within the OS or turn it on from an off state, it goes into a bootloop on LG logo, every time. I then have to enter TWRP via hardware button combo and reboot system from within TWRP and only then the phone boots into OS. Besides the bootloop, the phone is working perfectly on Cloudy once in the OS.
Where did I go wrong? Did I flash something that I shouldn't have? Did I break something? Any way I can fix it?
Any help will be appreciated.