[AOSPA 4.4.4 KTU84P] ParanoidAndroid 4.4+ G2 [06/28]
- Thread starter houstonn
- Start date
I have tried to install this rom and the installation is finished without any problem. But when i reboot the phone it was stuck in the boot lg logo. After some minutes if i touch the screen i feel the touch vibration. What can i do?
p.s. I come from the optimusg3, i also tried to install the slimkat and mahdi rom and all work.
p.s. I come from the optimusg3, i also tried to install the slimkat and mahdi rom and all work.
Make sure your baseband matches. PA test builds tried JB baseband for a bit, and then back to KK baseband on beta6.
Yeah the kk baseband was right beacause i also tried to install the baseband after i flashed the rom and the problem wasn't gone.
So where is the stable build? I don't find it in the d802 folder
Look at these latest additions, they also flashed the testbuild that wasn't meant for them. Pff lots of careless ppl out there!
btw are there per panel type beta versions? Maybe i did miss that.
http://xdaforums.com/showpost.php?p=56783831&postcount=1697
http://xdaforums.com/showpost.php?p=56833147&postcount=1703
Last edited:
Either ask in the Q&A thread or read a few posts/pages back.
Sent from my LG-D802 using Tapatalk
For the people who had the screen issue after flashing the last beta, what kind of recovery do you have, twrp o cwm?
OMG! Already downloading! Is this the real deal?
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
522
AOSPA 4.4+ PARANOIDANDROID
Kitkat 4.4.4 KTU84P android-4.4.4_r1
D800 / D801 / D802 / D803 / VS980 / LS980
Download ROMS from DOWNLOADS
make sure you are on the latest TWRP (there are issues with CWM - u may try unofficial CWM)
DOWNLOAD LATEST OFFICIAL LG KK MODEM FOR YOUR VARIANT & FLASH AFTER rom/gapps
1. DOWNLOAD YOUR ROM
2. DOWNLOAD THE LATEST PA 4.4.4 GAPPS PACKAGE - always check/use up to date Gapps unless otherwise noted
https://www.androidfilehost.com/?w=files&flid=15797 - - RECOMMEND mini modular PA Gapps latest
http://goo.im/devs/paranoidandroid/roms/gapps
damage screen thread - visit here - http://xdaforums.com/showthread.php?t=2769770
Wipe Fresh Clean Install (you all know the procedure)
3. COMPLETE CLEAN WIPE - *includes system*
4. FLASH ROM & GAPPS
5. WIPE CACHE & DALVIK
6. RUN INITIAL SETUP & REBOOT
U MUST BE ON OFFICIAL LG KK MODEM TO BOOT
Let boot take as much time as needed. This will help avoid boot issues.
*not responsible for any damages..*
ParanoidAndroid Website
153PLEASE GO HERE FOR Q&A and let's keep this thread for development thanks..
DONATIONS,
to molesarecoming
to D4rKn3sSyS
to jaybob413
to aaronpoweruser
CREDITS,
AOSP/Google, Cyanogenmod, Goo, XDA, Krebsmilk, giannisgx89, Liquid,
AOKP, our users, supporters and donators, everyone who's helped us in the past,
heartfelt thanks to all of you!
Personal Thanks:
IOMonster
Shelnutt2
Jank4AU
slick_rick
Ayysir
xboxfanj
autoprime
Wootever
rchp
zachf714
Dees_Troy
BANNERS,
LINKS,
Website & Changlelogs: https://plus.google.com/b/107979589566958860409/107979589566958860409/posts
Github: www.github.com/paranoidandroid
Gerrit: review.paranoid-rom.com
Please watch the 2 videos provided below before posting in this thread. thanks
81New builds are building . 4.4 beta1 . you guys will be the first non nexus device with pa using 4.4 beta1 unless released unofficially by a non pa member. You need to completely do a clean flash. Last night merges were over 300 files with about 20000 lines of code , so it took me a few hours.
Also the bakedin kernel is my custom kernel with no changes in display or gpu . I've rebased it until we know exactly what the issues are. What I don't understand is why are other ROMs getting them 2 if they are on DR's kernel source. (If they are) .
I've looked at lg's complete stock comparing the variants panel dtsi files and although some are same some are different. I'll investigate more.
I truely believe that a huge main issue is that we are still using 4.2 bootloader since its the only way we can use Loki and have custom recovery . bootloaders and our bootstack plays a huge roll in all updates. Also KitKat changes to bootstack has every bit to do with display panel related stuff. That's also why we can't boot the new kernel on the 4.2 bootstack without adding the codes that jackpotcalvvin discovered to boot the new kernel. If u look at hammerhead it even comes with newer bootstack or some of it when 4.4.3 and that's only a jump from 4.4.2 .
There are a lot of play when a kernel dev does a kernel. Everything needs to align up properly. Like if a kernel dev builds off caf based and the ROM doesn't build with caf base it mostly isn't 100% compatible. Also even updating GPU drivers need the depending repos built along with proper blobs supporting them. Just like using older camera drivers in kernel requires older binary blobs.
By anyways enjoy new release and I'll look more into this.
Sent from my LG-D803 using Tapatalk
