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 ...
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.
First of all I'm not a very techy girl so please give me step by step instructions to recover my Yureka (Phone Details are given below). Few days ago (as usual) I restarted my phone and suddenly noticed a weird thing, It was stuck at YU-bootscreen/Logo for many minutes but suddenly started getting booted but I ignored it. I never knew it's going to be a big mess soon. After few days I again rebooted my phone but this time it refused to boot, the same situation. It was stuck at YU Logo. I waited for a long time but no gain. Screen was constantly on and it was literally scaring me. finally I ejected/removed the battery forcefully and reinserted it and restarted the phone and again after getting stuck at YU Logo/bootscreen for a while it got booted and it was a relief of sign. Here comes the main problem. Again after few days Yureka started hanging as usual and I again rebooted it but this time it was dead-end for me. It's again stuck at YU Logo Screen. I tried restarting/removing the battery many times but no luck. It's stuck at the screen forever. I am trying/restarting/reinserting-the-battery again and again but seems it's stuck forever at the bootscreen. It's been few days but no luck. I am totally frustrated and don't know what to do! I have important data in the phone especially App Data like Hike/WhatsApp and some GamesData/SMSes/Contacts etc. Please guys help me. How to revive my Yureka without damaging the precious data?
Things I tried to solve the problem:
1) I removed the battery many times. I did reboots many times.
2) I tried "Wipe cache partition" option in the recovery menu (Power+Volume Up+Volume Down) multiple times. But no gain.
What could be the reason of this problem? Is this faulty internal memory? Because my phone is behaving weird since the day I purchased it. Random App crashes happen multiple times regularly. This service stopped that service stopped blah blah. It's so annoying and counter-productive. It Started hanging and lagging a lot too. And finally bricked. I think this bricking problem only happens when you fiddle with your OS or try to root or install any unsupported custom ROM, But I am on stock ROM then why did it happen with me? Hardware defect? Did I get a faulty phone? I always ignored App crashes/Google services crashed /Random auto-reboots because I though Cyanogen OS is prone to bugs. But this is insanely odd! So many bugs are too much. Stock ROM has to be stable. I think YU gave me a faulty device! Please help me. What to do now to turn on my device without losing the data? I didn't try the Wipe data/factory reset OR Wipe media because it will remove all of my data which is very important to me.
P.S. Please note that my phone is stuck at YU Logo (NON-Animated logo) NOT on Cyanogen Logo.
One Another Indication of the problem:
When I tried to charge my phone by turning it off completely and then connected the charger with it the same YU logo came up and screen never went blank/off (screen with YU logo was constantly ON) and the Red LED light (charging indicator) didn't turn on, It means I can't even charge my battery because I think it's not getting charged cuz it's stuck on the same screen and never shows battery indicator while soft-pressing power button curiously just to check I removed the battery and tried connecting the charger without battery in the phone and the Red LED turned on normally.
Phone Details:
Phone Model: simple YU Yureka A05510 (NOT YU Yureka plus)
Cyanogen 11.0-XNPH05Q (Android KitKat 4.4.4) (NEVER updated Yureka)
NEVER rooted
Stock Cyanogen ROM
Stock Cyanogen Recovery
Are you sure it's still on KitKat?
Please confirm once again then I'll give you flashing guide.
saurav007 said:
Are you sure it's still on KitKat?
Please confirm once again then I'll give you flashing guide.
Click to expand...
Click to collapse
Yes it's KitKat 4.4.4
Download CM11 fastboot.zip and follow the flashing instructions from here.
This will erase everything from your device. If you don't want to lose data then download CM11 signed zip and flash it manually from stock recovery.
saurav007 said:
Download CM11 fastboot.zip and follow the flashing instructions from here.
This will erase everything from your device. If you don't want to lose data then download CM11 signed zip and flash it manually from stock recovery.
Click to expand...
Click to collapse
Hi! When the problem occurred I was thinking about the same solution, I mean flashing the ROM by putting it on a SD card. But I've two confusions on my mind
1. Should I directly flash CM 11.0 (the same ROM which I have currently) or the upgraded CM 12.0 (Lollipop)? I am confused
2. When this catastrophe happened, free space on internal memory was very low (I don't remember exactly but may be 100MB or 200MB or 300MB but very low). Will the ROM flashing process complete successfully?
Sarika CoolGirl said:
Hi! When the problem occurred I was thinking about the same solution, I mean flashing the ROM by putting it on a SD card. But I've two confusions on my mind
1. Should I directly flash CM 11.0 (the same ROM which I have currently) or the upgraded CM 12.0 (Lollipop)? I am confused
2. When this catastrophe happened, free space on internal memory was very low (I don't remember exactly but may be 100MB or 200MB or 300MB but very low). Will the ROM flashing process complete successfully?
Click to expand...
Click to collapse
1. COS12.1 Signed zip can be used to flash directly over COS11, but since there is lots of things happening in your phone, I'd suggest you to flash COS11 first.
2. 300MB is very low. Use external SD card because the size of signed zip is 500 MB.
Solution
Guyss plz plzz help me out, even my yureka has started behaving like this, im really fed up i tried many things but no use i tried the following things
1.installed stock rom using fastboot
2.flashed cm11 signed zip using recovery
3.clearing cache in storage
4.wiping dalvik and normal cache
Currently now i am using cm11 signed zip version
. For the past few days my phone has been crashing and turning off randomly, when the phone is off the charger. The screen just goes black and Shuts down. When I try to reboot the phone it will get upto the boot animation and then freeze and shutdown again. I have to connect my phone to a charger and then reboot, only then does it fully boot up. My battery is 100% btw.
What I have done so far is:
1) flashed the latest build of exodus
2) cleared dalvik and cache
3) flashed an earlier build (25/07) without flashing XPOSED and SUPERSU. However problem still present.
Can someone help please and tell me what other steps I can take. My phones important to me at the moment as I'm away in Turkey for an internship. It's a really strange problem I can't figure out what to do. Thanks alot
Did you try to go bacm for stock oneplus OS? Try to do a full recovery via the tool it will wipe root twrp back to stock. It may help.
Does it happens with other roms?
hi, i solved the problem by flashing stock oxygen. i tried flashing oxyslim and cyanogen however both of them still had the same problem. Anybody have a idea of why this might have happened? it was completely random, and if it was the kernel then it would have been solved when i flashed the other roms...strange
Zeeshansafdar1 said:
hi, i solved the problem by flashing stock oxygen. i tried flashing oxyslim and cyanogen however both of them still had the same problem. Anybody have a idea of why this might have happened? it was completely random, and if it was the kernel then it would have been solved when i flashed the other roms...strange
Click to expand...
Click to collapse
It could be that te ROMs u DL were corrupted. This happens, thats why is always good yo verify HASH from your dl ROM and HASH from the developers topic
So you haven't read up on the official CM13 thread about the latest unstable builds?
Hi there,
I started this topic because I am out of options and I don't know what to do at this point.
My Phone is a XT1562 DualSim.
I recently flashed http://forum.xda-developers.com/moto-x-play/development/rom-spetrum-mm-volte-t3462690 and I also installed "MODEM" (MPD24.107-70) from page 1, but not right away.
First I wiped everything expect "internal storage". The phone booted but it restarted during boot (which might be okay) but then it rebooted again during boot. The boot process finally finished and I got to the screen "Android is starting - Optimising app x of y." The phone rebooted even during that process and that is definitely not normal I think. So after a couple of reboots android did finally optimise all apps but the phone did still reboot withing the first 30 seconds after it was booted.
From here I did a lot of testing and doing. These are my findings:
- When I set phone to flight mode / airplane mode it does NOT reboot... Hurray!
- When I flash another ROM (Official CM 13, http://forum.xda-developers.com/mot...m-cyanogenmod-13-preview-moto-x-play-t3252255) the phone runs like a charm, NO reboots whatsoever.
- - But as soon as I flash gapps and the phone is booted, I get the reboots again (usually within the first 30 seconds).
- - Again setting the phone to flight mode prevents itself from rebooting.
- - Apparently it doesn't matter what version of gapps I flash. I even tested the light version (ARM, 6.0, Pico, from http://opengapps.org/). It still reboots. I also tried gapps mini and stock.
Oh and I don't think its MODEM (mentioned above) related, because I faced these problems already before I installed / updated the MODEM. Well I thought its MODEM related, that's why I went back to MODEM stock version MPD24.107-52 but that did't help either. I should mention that I am not sure if I had MPD24.107-52 installed originally but spetrum (the rom developer) pointed me to that version: http://forum.xda-developers.com/showpost.php?p=69129552
I also restored my working TWRP backup from an android I used for month and guess what, yep, reboots
brrrrr this is frustrating
I never experienced that before and frankly I am out of ideas.
Anything is welcome and appreciated
Thank you
If nothing helps reflashing the whole firmware is always an option
minimale_ldz said:
If nothing helps reflashing the whole firmware is always an option
Click to expand...
Click to collapse
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
I always go back to flashing stock rom with rsdlite whenever things went wrong and I can't solve it by flashing small fixes.
rancor187 said:
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
Click to expand...
Click to collapse
I mean full stock firmware you flash with fastboot or RSD. Roms are usually only system + kernel, so not very helpful in your case
Guys! Good news. I did go back to stock firmware and from there to official CM13. Of course I had to root and install TWRP again but it was worth it.
I lost a few days spending my time with it but I'm glad its all good now thanks to you.