So i have been using Android L pv-79 Developer preview since it first came out flashing updates and kernels without an issue. Today i flashed a newer kernel by defconoi switched on intelli thermal and uv by 75, everything was running normal for hours. I take my phone out of my pocket and its on the google boot logo. Tried booting into recovery but it still stuck on the google boot logo. So i fast booted cam recovery nothing happened then i fast booted the 4.4.4 stock image successfully and I'm still stuck.. some assistance on this matter would be really helpful. Need to fix this before work.
Thanks
Edit: Fastbooted 4.2.2 and still the same issue.
Related
Hey there! I was updating my version of Paranoid Android and my kernel and it seemed fine at first but It yield some odd problems. I went into Clockworkmod recovery and Flashed my rom and kernel I then proceeded to wipe my cache and dalvik cache. I have done this many times before on many devices. I encountered a problem when I rebooted for the second time, I got the Android is updating apps display and I continued to get it every time I booted. The device would also randomly turn off when the screen dimmmed. I proceeded to set out and fix it. Here are the steps I took and the problems it caused.
Flashed stock rom-would not boot properly
Flash RESET kernel-I messed up and though this was a real kernel, my problems escalated from here.
Flashed stock rom and recovery.
Flashed reset kernel and then real kernel-Still had problems.
Flashed stock rom
My problems from all this accumulated somewhat and I can barely boot into fastboot. I get weird static screens and weird white noise sounds. It does not always let me boot into android and will get to the google logo 1 out of ten tries.
These is really unnerving and I have no clues whats what.
Note: I am using Faux123's kernels and his reset kernel.
Thanks a lot for any help!!!
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
schmidty455 said:
I have scoured the internet to find someone with the same issue as me, and I haven't found enough to fix the issue, so I'm placing a plea for help here. I have installed TWRP 2.6 recovery, and I am trying to flash OmniRom 4.4.2 nightlies. Originially I was trying to flash cyanogenmod 11, but I had this same problem. It appears to be any kit kat rom that causes the problem (I haven't tried flashing stock or any non-kitkat roms, but I was running on rooted stock before I tried to flash CM11). Anyways, When I flash I am wiping dalvik, cached, system, and data. Then flashing the rom, then flashing Paranoid android gapps. It will boot the first time fine. My phone will work just fine afterwards. However, if my battery dies or I restart, I will be unable to boot back into the rom and my phone becomes a soft brick. It will just stay stuck at the galaxy s 4 logo for as long as I leave it on. I have left it on for more than 30 minutes and there are no changes. I can't have my phone being just a dead battery away from being bricked, so I am asking for your help! Anything is much appreciated!
One other side note: I had my phone just lock up on me once in the middle of it running just fine. Afterwards it turned off on its own and tried to restart, but it resulted in the same issue. I don't know if this is related or just a bug in the rom.
Click to expand...
Click to collapse
Omni clearly states that it is an alpha, so you mileage may vary considerably.
Sounds kernel related. Have you tried just reflashing the kernel and seeing if it'll boot after that. Or trying a different kernel?
Thanks for the reply! I actually just fixed the problem on my own. I used Odin to flash a newer version of TWRP and then flashed omni, and it looks like everything is working just fine. I read a few people saying that they were having issues flashing kit kat roms with older versions of recovery, so I figured it was worth a shot.
Hi,
I was using a CM11 4.4.2 Rom for a few months now, and this morning I found it stuck at the CM boot animation loop.
So I went ahead and downloaded latest version of CM11 20140717, I wiped cache/dalvik/data and flashed new rom. And it was still stuck in Animation bootloop.
Then I used safewipe to wipe then flashed 20140717 rom a few times and the same thing kept happening. (I waitad for good more than 15mins for it to boot up).
Later I also tried flashing with 20140616 CM11 build, it also had the same result.
Only difference was 20140616 build has the circular boot animation while for 20140717 build I noticed the Android text flashing as it ised to be in the stock rom.
Can you guys help me, what do I need to do, Flashing stock ROM (sbf) would be the last thing I want to do, Do I need to do that ?
solved
karan4 said:
Hi,
I was using a CM11 4.4.2 Rom for a few months now, and this morning I found it stuck at the CM boot animation loop.
So I went ahead and downloaded latest version of CM11 20140717, I wiped cache/dalvik/data and flashed new rom. And it was still stuck in Animation bootloop.
Then I used safewipe to wipe then flashed 20140717 rom a few times and the same thing kept happening. (I waitad for good more than 15mins for it to boot up).
Later I also tried flashing with 20140616 CM11 build, it also had the same result.
Only difference was 20140616 build has the circular boot animation while for 20140717 build I noticed the Android text flashing as it ised to be in the stock rom.
Can you guys help me, what do I need to do, Flashing stock ROM (sbf) would be the last thing I want to do, Do I need to do that ?
Click to expand...
Click to collapse
Surprisingly I found an exact same thread like mine Not sure why I did not find it all the time when I was searching this evening.
http://forum.xda-developers.com/showthread.php?t=2296965
And to solve this I used the same solution i.e. flash the sbf
So today my nexus 4 shut off at around 20 percent batter i didn't really think any of it because that happens often and i just reboot and its back on after charging it. This time however it was different it wouldn't boot it was just stuck on the paranoid android boot animation. I searched online and found out that clearing cache and data all that works so i tried it to no avail. I did the same this again but this time re flashed the rom and still nothing. I then pushed cm 11 into the nexus 4 flashed that rom and nothing. So then the last thing i though about was fully unrooting and going back stock with nexus root toolkit. I tried it and went through but then when good ol kitkat animation started it continued forever. Im out of options now and i don't even have custom recovery anymore what can i do.
I was running Paranoid Android build version 4.45 with hells core kernel.
EDIT---------------------------------------------------
I have clockwork mod recovery back up were do i go from here please help.
Please Help Thanks
skype:ApexDreamZ
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
MATTHEWLONG said:
Good morning.
I was running 7.1.1 Dev 1 until yesterday afternoon.
The upgrade to Dev 2 popped up and I said no.
When I came back to my phone it was stuck in a boot loop.
I turned the device off and back on but it still was in a boot loop.
I decided to flash Stock NBD90X.
There was no issue with the flash.
The phone though is still in a boot loop and I am unsure where to go from here.
When I was running Dev 1 7.1.1 it was rooted and running Google assistant with the Pixel build prop. Could that be the issue?.
Any help gratefully received.
Matt
Click to expand...
Click to collapse
This has been an ongoing thing with the 6P and 5X, there are multiple threads on this bootlopop issue some recoverable, some not. Check this out see if it helps..
http://forum.xda-developers.com/android/help/guide-revive-angler-bootloop-t3454938/page5
Thanks for the support, I will take a look.
I've read too many threads about 7.1 and the beta program causing boot loops and bricks....this is ridiculous!
Do you have a nandroid on hand? If so, try restoring it and see if that works.
I have only boot looped twice with this phone. Each time I went into TWRP and did a full wipe (everything except internal storage). I completed the full wipe three times consecutively. After the third wipe I boot into fastboot and flash the latest stock images from Google. Reboot.
Let the phone sit for 10-15 minutes then boot back into fastboot to flash custom recovery (TWRP). Then boot into recovery to flash SuperSU. Reboot. Let phone sit for another fifteen before continuing with setup.
I know wiping the device three times probably doesn't do anything extra than wiping once before flashing but it's what I've always done and what's always worked for me.