[Q] D803 stuck on bootanimation with any AOSP rom - G2 Q&A, Help & Troubleshooting

Plz help. Somebody has the same issue ? I've tried with CM11, CM12, PA4.6, Liquidsmooth, etc. with the lastest TWRP (v2.8.2.0) and kitkat baseband. All give me the same result. I've to say that when i acquired the G2, it has the screen broken, so i can't use TWRP, then i decided to flash PhilZ, but when i wiped system, it also wiped EFS. I didn't knew that would even happen, 'cause i've used that recovery on several phones and never happened that before. Anyhow, what is done is done, so i need to know if someone here get through the same issue. Thanks in advance

Related

[Q] imei problem after rom flash

If someone could help me I'd be very grateful.
I have cwm 6.0.3.2(0611) but was running TWRP previously. The first custom rom I installed was crdroid and today I tried to install graviton rom. I did this using TRWP. However, after installing, my SIM was not recognised and I had no IMEI and the baseband version showed 'unknown'.
I then flashed CWM and tried to re-install crdroid with the latest version but came up against the same problem. However, after installing this I also had no bootanimation. After browsing this forum for an answer, I couldn't really find anything that helped too much so I did a nandroid restore.
This worked and put me back to my stock rom.
I then tried to reflash the latest crdroid but the problems have all returned again.
Can anyone help me? I'd like to be able to flash the roms I want again but it seems that anything I'm doing is wiping the IMEI/baseband/bootanimation.
welshyoot said:
If someone could help me I'd be very grateful.
I have cwm 6.0.3.2(0611) but was running TWRP previously. The first custom rom I installed was crdroid and today I tried to install graviton rom. I did this using TRWP. However, after installing, my SIM was not recognised and I had no IMEI and the baseband version showed 'unknown'.
I then flashed CWM and tried to re-install crdroid with the latest version but came up against the same problem. However, after installing this I also had no bootanimation. After browsing this forum for an answer, I couldn't really find anything that helped too much so I did a nandroid restore.
This worked and put me back to my stock rom.
I then tried to reflash the latest crdroid but the problems have all returned again.
Can anyone help me? I'd like to be able to flash the roms I want again but it seems that anything I'm doing is wiping the IMEI/baseband/bootanimation.
Click to expand...
Click to collapse
You could try backing up your EFS partition and grabbing the Modem you had in your stable ROM. Once you flash, you could try to restore the EFS (on the rom that you have the issue on) and flash the modem if the unknown baseband/lost imei continue after that.
Cheers, I did think of something like that - I saw a few threads which suggested flashing the modem (twice?) but it seemed to me that I should be able to flash a rom without having to backup efs and restoring each time (the issue happens with every rom flash now for some reason). I saw a few similar threads but nothing with the exact same problem, and no real solutions so far.

[Q] Bootloop on L7. Help pls!

Hello,
First, sorry for my bad english and knowledge on flash/root.
I flashed Slimbean on my P700, everything worked fine, expect of the modem. I tried other ones, but didn't work.
So I decided to change the ROM and flashed CM10.2 on my L7 which was working fine until battery was empty. After loading my phone, I wanted to start it, but it stayed in a bootloop on the boot animation. I tried everything, wipe/dalvik wipe, flashing slimbean --> still bootloop
Now I thought, maybe CM11 could work, but still the same problem, I formated everything expect of sd, wipe/dalvik wipe, flashed the ROM, Gapps and kernel, but still the bootloop...
Any ideas?
It may take a while on first boot. But if it don't load you could restore a backup of you have one or flash a kdz or use LG update tool to fix your issue. Other than that make sure you have word everything in recovery and format system, data and cache before flashing a rom. Do not flash kernel before first boot unless it's required.
I can add to that to flash ROM only without gapps just to get OS to boot correctly.
I already solved it.
I whiped everything, formatted everything except of external sd and than first only flashed the ROM and rebooted, all worked, than i installed the Gaps, rebooted, and last i flashed the kernel, now it works fine but i will never ever reboot my phone or let battery get empty ^^ no more
thanks for your help

Hi. My recovery "disappears", or some issue..

Hi. Writing from my Phone now. Im running cm 11. I installed or flashed philz touch...
Then installed cm11.
I want to do a nandroid backup..
But when i tried restarting to recovery, it skipped that part and went to cm11..
Normal reboot.
Before i flashed cm i had latest stock rom from samsung.
I flashed philz touch that time to..
But when i then installed cm, something went wrong, got some error on cm.
Uid's something. Forgot. I could not boot in recovery, so i used odin, flashed philz touch.
Factory reset and my Phone was fine!
Cm and recovery.
Now it seems i cant get into recovery again...
Anyone know whats the issue?
Locked bootloader? Have not read up on that yet...
Its wierd if recovery just fails or whats the issue.
Pardon the blurry explenation and my bad english/spelling. Im tired.
Thanks in advance.
It was the Quick boot app. Since i set developer options in cm to restart into recovery through CyanogenMod.
But the Buttons did not work last time i tried.
But its kinda solved. Flashed the latest recovery with rashr yesterday...
So i will just use cm to boot into recovery..
Thanks anyways.

[Q] Custom ROMs not booting (boot loop)

I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
VegasIdaho said:
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
Click to expand...
Click to collapse
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
v.konvict said:
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
Click to expand...
Click to collapse
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
VegasIdaho said:
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
Click to expand...
Click to collapse
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Choristav said:
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Click to expand...
Click to collapse
Thanks for your reply. After reading the response from v.konvict above, I thought that CM12 would be caf, but it isn't. I've got several more ROMs working now by using different bootstacks, but it is trial and error with some of the ROMs.

Flashing another ROM turned into some bigger problem

Hi guys, the times has come for me to open up my own account - I screwed up. I hope this is the right sub forum and apologize if it is not.
LG G2 Germany, formerly: TWRP recovery, Paranoid Android 5.1.1
Loved the rom but there were some issues like the screen turning off and on randomly, wouldn't accept pin right away, so I decided to go for CM 12.1.
Booted into recovery, factory wiped, tried to flash the .zip, but neither the rom nor the gapps would even begin to flash. It just said error.
Went crazy, tried some other CM versions, none of them worked. I've never had this issue before, when I flashed PA it all went just peachy.
Went even crazier and I can't really remember what I did in my panic spiral, but I somehow ended up with a soft-bricked phone. Managed to re-install the LG firmware .kdz, however, only the 4.2 one worked (4.4 gave me a bootloop.)
Now, getting this bad boy rooted and ready to flash custom roms is somewhat of a problem. I managed to get it into recovery though (after some issues with the recovery image), but flashing CM still won't work. Same error as before. I think there may be something wrong with the recovery image. I still had the image .apk from the first time I rooted my phone (also with 4.2) and it worked just fine so I figured I'd just use it again and do it like I did it last time. However, I am able to get into recovery mode. I've tried ClockworkMod and TWRP, but as a result of my panicking, it's just really a big ol' mess right now. I hope I've included all the info needed.
Please help, I'm actually lost.
Are you flashing the latest TWRP which is 2.8.7.1?
http://blastagator.ddns.net/twrp.html
Hey, thanks for replying. At the moment it only boots into recovery, unfortunately. ADB does not work, even after re-installing the usb drivers. My computer recognizes the device now though, but I can't get any files onto that thing at the moment.
Edit: It's not the latest TWRP
If you install the latest TWRP, you may be able to boot into TWRP and copy over a ROM to flash.

Categories

Resources