Develop Bugs

[Q] 4.2.2 google screen/ stuck on custom rom flash

Search did not give any results i guess. Finally got the nexus up and running again / was on CM10 and had neglected to wipe data when flashing the 4.2.2 factory image. It was pretty weird, I think. The phone had sat on the 'X' screen time after time, minutes not counted.. I had at first vol up/ vol down / power and had gotten a red exclamation for some reason. Eventually got into fastboot, I had used the toolkit by mskip / reflashed the 4.2.2 image , made sure to clear data and all works fine. When flashing a custom rom it sticks on the google unlocked screen. Why? What is the problem? How does this fix itself or going about it to get it fixed? ....... Again, if this is a stupid question and you have easily found the answer by all means pass along the right keyword. If this is not a stupid question, you don't think, and are cool about helping me out, by all means, please do so.
Edit . I had flashed stock then custom rom on another device with only the usual, i guess, load time. The best advice search forums gave me was , just wait'.

http://forum.xda-developers.com/showthread.php?p=38127432
Flashed cm-10.1-20130217-NIGHTLY and got stuck on the "Google" logo on reboot. Booted to recovery and installed the Feb 16 build and all is good. Hopefully the next nightly works well.
From the CM thread.

Hello.
Try to flash the 2013.02.17 nightly AND some 4.2.2 kernel.
I tried with LeanKernel 6.0exp1 and it works
There are reports with working flashed 2013.02.17 with Franco's Kernel latest too.

vfmmeo said:
hello.
Try to flash the 2013.02.17 nightly and some 4.2.2 kernel.
I tried with leankernel 6.0exp1 and it works
there are reports with working flashed 2013.02.17 with franco's kernel latest too.
Click to expand...
Click to collapse
perfect work.

Reboot on start with CM roms

Hi there, like the title states my phone is rebooting every time it starts.. Basically I've tried this on
CyanogenMod 10 & 10.1 by miroslav_mm
CyanogenMod 10 & 10.1 from get.cm
Every time if I install GAPPS (made sure to install the right version), the phone will get to the "Welcome" screen and then once I press start(or next?) it locks up and reboots. If I don't install GAPPS its the same thing, the phone just makes it to the lock screen or home screen before rebooting. I've tried this all on the ROMs stated above, formatting /system or pretty much all I can but I just cannot get it to work.
Thanks in advance for any help.

dissonance01 said:
Hi there, like the title states my phone is rebooting every time it starts.. Basically I've tried this on
CyanogenMod 10 & 10.1 by miroslav_mm
CyanogenMod 10 & 10.1 from get.cm
Every time if I install GAPPS (made sure to install the right version), the phone will get to the "Welcome" screen and then once I press start(or next?) it locks up and reboots. If I don't install GAPPS its the same thing, the phone just makes it to the lock screen or home screen before rebooting. I've tried this all on the ROMs stated above, formatting /system or pretty much all I can but I just cannot get it to work.
Thanks in advance for any help.
Click to expand...
Click to collapse
Does the phone function properly with non-CM10.1 roms? Are you doing a full wipe of cache, data, and system?

audit13 said:
Does the phone function properly with non-CM10.1 roms? Are you doing a full wipe of cache, data, and system?
Click to expand...
Click to collapse
Thanks for the reply, sadly yes I've wiped pretty much everything but the sdcard in between installs. ROM's like OH!NO!'s v20 work fine.
Thing is I used to have CM10 installed before (and even had 10.1 but it was a bit unstable), until one day the phone had a random reboot and then would not stop boot looping. I stayed with v20 for a while before trying at CM10/10.1 again, and now here I am
EDIT: I just tried OH!NO!'s CM10 hypersonic which works great... until I reboot, and from that point on it just boot loops. I wiped data, cache and dalvik after that and now it's just like the others, reboots on pressing start >_<

Maybe there is something wrong with the hardware?

[Q] Sound and Wifi won't work

Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.

noahajohnson said:
Hi,
I've flashed PA many times before on my Nexus 4, and I was using PA 3.99 before I decided to try using CM11 (cause kitkat). Well, CM11 worked fine, but I wanted to go back to PA, however, when I tried flashing the rom, it took much longer than usual, and then when my phone finally booted up, neither the sound nor the wifi would work. I first noticed this when the phone was setting up, as the second thing a new android phone asks you to do is to turn on your wifi. My phone just said "turing on wifi" for a good five minutes until I skipped it. Once I finally finished setting the phone up, I tried turing up the sound but it wouldn't work. Of course, I can't really use my phone if the sound won't work at all, so I decided to flash CM11 again, and then everything was working properly. Since then I've tried PA and CM again, AOKP, and PAC rom, but CM is the only one that worked for my phone. The sound and wifi didn't work on any of the other three roms. If anybody could help, that'd be great!! Otherwise I'll have to stick to CM11 even though I'd like to go back to PA.
SOLUTION FOUND
For anyone with a similar issue: My problem was that I was running CM11, which uses android 4.4, so it seemed that the issue was caused by flashing to a rom that used an earlier version of android. I solved the problem by unrooting my phone and reverting back to 4.2. Then I rooted the device again and flashed PA 3.99, then everything was fine.
Click to expand...
Click to collapse
Thank you !!!
it's Work !

[SOLVED][Q] ART building bootloop - anyone else seen this?

Hi, Ive not long had my m9. When i got it it updated straight away and got the charging bug.
Since then I have s-off'd and tried various roms with not too much luck.
I now have a bug that occurs when i flash a new rom. This has happened when i flashed 3 different roms. Leedroid, Viper and android revolution. the rom flashes ok, then starts to boot, and builds art. It then finishes building art and starts to complete the boot process, and then it reboots and tries to build art again.
I flash back to my stock backup and everything is fine again. (apart from the damned charging bug)
Has anyone else experienced something similar?? am i missing something??

Go in twrp and make factory reset

just tried that, didnt work

Did you update your firmware? if you're still on 1.x firmware, those 2.x roms will reboot.

yeah. have tried matching roms to firmware and still get the same result. trying viper one currently. in a massive bootloop again. It boots enough to say "nfc service has stopped working" and thats what made me think it might be firmware, but it seems to make no difference.

cant even adb whilst its booting.. getting waiting for device.

What version of twrp are you using?

2.8.6.1

philicibine said:
2.8.6.1
Click to expand...
Click to collapse
Update to 2.8.7.0 and see if it continues.

I've solved this, and my charging issue. Finally!!
I decided to flash the earliest ruu I could find and then let it do all of the ota updates itself.
I then rerooted, flashed updated firmware and am now running leedroid.
Thanks for the help guys.

LG G Pro E988 Cyanogenmod Reboot Problem

Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before

Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
I'd try using the latest wild kernel.

g0at1 said:
I'd try using the latest wild kernel.
Click to expand...
Click to collapse
well i think i did try wild kernel with cm12.1 latest nightlies. The issue gotten worse. More random reboot occured.
Currently on slimLP with his zerkernel v1.7. I thought this one is perfect, but then out of nowhere the random reboot occured again. It's not as frequent as before but still happen.

Right now I'm using Mokee with wild kernel and everything is going well.

Oyongx said:
Hi. Im using LG G Pro E988 variant. I'm trying to flash cyanogenmod 12.1 nightly version. Everything went well and all but i got a problem where the phone likes to reboot itself. So i try to clean everything with the usual stuff (wipe data, even wipe system, cache, etc) and re-flash the same. The issue still persists so i thought maybe it's the problem lies within the cm12.1 itself so i move a step back. I flashed the latest Cyanogenmod 11.2 Snapshot version that was available from their site. The issue still happened and i got no clue what's going on. On my stock kitkat ROM, this issue never happened.
Anybody got the same problem? Thank you before
Click to expand...
Click to collapse
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app

hawkwind212 said:
Random rebooting is a common issue with all the cm 12.1 based ROM for lg ogp. The cm12. 1 in my opinion was never fully stabilized even by the time the devs were starting to switched to the newer hardwares. If you keep the number of apps you unstated to minimum, you may be able to keep random rebooting down, but this just my observation. I thought the latest bliss pop 4.03 had the rebooting issues sloved, but it rather just had the occurrence down to where it's less. But there are other issues such as the device getting extremely hot, which in turn causes shutdown. To the point where I give up on using LP once again on this device, and move back to kk. The kk may be an older rom, but at least it's stable. With the LP, I think issues with it unable to find the sim card, GPU issues that cause screen to flicker and blackout, all are never fully fixed. Rather, those issues were patched and rigged to make the rom run, but not smooth enough where you see issues such as rebooting and overheating.
Sent from my LG-E980 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yeah, i think the issue are only on cyanogen based ROM. When i use the lolipop such as Super Mini V6.5 by henrypham91 and lgviet team, it's all good. Deep sleep normaly, no sound delay when game on 2D graphics, and all. But then again, it's noticeably slower if you compare against CM head to head. I really love CM or AOSP based rom because they are so fast.
g0at1 said:
Right now I'm using Mokee with wild kernel and everything is going well.
Click to expand...
Click to collapse
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol

Oyongx said:
Never heard about Mokee. I'll look maybe and try that. Thanks Edit: it is an AOSP based rom! Might try that. Hopefully my phone survive lol
Click to expand...
Click to collapse
Mokee is a Chinese CM based rom.

g0at1 said:
Mokee is a Chinese CM based rom.
Click to expand...
Click to collapse
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:

Oyongx said:
The download link seems invalid. I don't understand chinese but on the downlaod the url there's an error 404 written. :silly:
Click to expand...
Click to collapse
Their website has an English version. There should be a British flag on the upper right side. Then download their history zip which is a kind of final release.