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!!!
Related
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.
So this issue has persisted throughout wiping data/factory resetting. I'm really not sure what this is.
Basically what happens is that my phone will gradually get slower and slower until it freezes and then reboots. However, after it reboots, it will go into a boot loop. What I will then need to do is basically wait it out by shutting it off. Then, I wait for an hour (maybe more) before I try turning it back on again, at which point it returns to normal.
Any idea? I thought it might be a memory leak? But how would that affect rebooting? I'd like to also mention that at one point my recovery somehow disappeared as well. I managed to re-flash TWRP using Flashify, but I haven't dared going back into the recovery, because last time when I had lost my recovery, I ended up thinking that I had to wipe my phone completely (because even Download Mode wasn't working correctly).
By the way, I'm running an AT&T LG G2 d800, on the "d80010q" firmware 4.2.2. I'm rooted, with Xposed modules running, as well as the camera mod flashed. No other modifications have been made except for buildprop and systctl (kernel) changes through android tuner.
Same issue
Hello,
I am having this exact same issue. Did you ever find a fix for this? I have been searching for hours. I have tried numerous things, flashing back to stock with lg flash tool, installing different roms, it happens on all roms.
Thanks
Ive been running CM12 for a long time, but today I noticed I had a few missed calls and my phone hadnt rung. I rebooted the phone and it went into a boot loop. I cleared cache, but still bootlooping, dirty flashed the latest nightlie and then a full wipe - all of which resulted in the boot loop.
I restored my phone using the TOT method, but it would get to the setting up google account/wifi etc and reboot.
I used KDZ to install 30b lollipop ROM this seemed ok until reboot and then it would factory reset, optimise apps every time and be back to the setup screen.
I managed to install KK using KDZ and this seems more stable so used IOROOT and Autorec. I then flashed CM12 and GAPPS again, but it started to boot loop again.
I hadnt done anything to my phone prior to the problems - ie. no new ROMs, kernels or even apps.
Any suggestions or does it sound like something more physically wrong?
I have managed to get Cloudy G2 2.2 working without any problems except it isn't recognising my SIM. Does anyone have any thoughts or is this a dead phone?
Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!
Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?
tank0412 said:
Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?
Click to expand...
Click to collapse
Yup. Tried all this.
Just format again and re flash rom with xposed it fixed my bootloop.
The solution is,
Go back to stock rom. ???
Can anyone tell me how to back stock ROM from resurrection remix???
yasin0005 said:
Can anyone tell me how to back stock ROM from resurrection remix???
Click to expand...
Click to collapse
Download latest firmware from Asus' Support Page. And flash it via adb sideload.
I m now on Stock Rom without any problems no screen freeze no bootloops ...
Hello together,
I'm using official RR ROM 7.0.2 on my G900F, until recently with latest tuned kernel. I suddenly got some random freezes with reboots without knowing the reason. Then after some crashes it resulted in a bootloop, meaning that the RR bootscreen is loading forever (already tested for hours).
Flashing RR ROM again fixed the issue completely, but when I flash tuned kernel again I immediately end in bootloop. Flashing boot.img of RR ROM once again fixes the problem. Then I tried Intelli-Kernel and it boots, however the first unlock screen is very laggy, system ui takes long time to load after unlock (after that it works normal) and I get here and then sudden reboots. After some crashes/reboots I end up with bootloop with Intelli-Kernel.
Once again: flashing boot.img of RR fixes all the problems.
It's unlikely that the kernels itself are at fault, as they are working for many others and also worked for my device until recently.
So why am I unable to use custom kernels suddenly and how can I fix it?
I'm grateful for any hints you can give to pinpoint the reason. I already asked in the kernel Telegram group but sadly they weren't able to help me.
- I'm clearing dalvik/cache every time,
- tried TWRP repair feature for /data partition
- and as far as I can say I removed all remands of boeffla config app, but even if there are some they should load after system boot so obviously kernel settings aren't applied when I stuck on boot screen.
I don't overclock but for the same reason it shouldn't matter even if I do.
If possible, I would like to avoid a full wipe.
Thanks in advance.
Have you tried backing up your entire phone, wiping and installing RR, letting it boot etc before rebooting to recovery and installing a custom kernel again? If that fails, then either the version of RR you are using is incompatible, or you have some sort of hardware failure somewhere.