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!
Thread closed / Duplicate
Related
Hi there,
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please help me to bring back my phone! This is literally driving me nuts, and I haven't so far found a solution that works! I would be happy to clarify and elaborate upon any point of information.
Thanks,
Sami
iamsami13 said:
Hi there,
I've got quite a peculiar problem with my Nexus 5.
Last night, I left my phone on charge. It was working normally and the software was functional etc. However, once I woke up, the phone was constantly restarting itself, and wouldn't load past the boot animation. I tried to load up fastboot to enter the TWRP recovery, however, the phone froze on the load screen. I should also add that my custom boot animation was replaced by the CyanogenMod mascot.
This problem has never occurred before, and I really haven't got a clue how to fix it. I tried to use WugFresh's NRT to flash a factory image of Android 6, however, the command terminal indicated that each process had failed. This did not restore the phone to its original condition.
I should also point out that I have been running a CM 12.1 nightly, which has been very stable and I have been using this nightly, without major problems (bar the infrequent system UI crashes) for a couple of months. It is obviously rooted and I have a Nandroid backup, which I can't access for aforementioned reasons.
Please help me to bring back my phone! This is literally driving me nuts, and I haven't so far found a solution that works! I would be happy to clarify and elaborate upon any point of information.
Thanks,
Sami
Click to expand...
Click to collapse
Hello, and thank you for using XDA Assist!
Looks like you made your way to the right spot. Cool!
Hope it helps.
Hi Guys,
Prelude : 2 months back, my pure stock Moto G experienced i guess a battery drain and refused to start the next time onwards. When it was powered on, it just got stuck on the M Logo of the bootup. After the help from @lost101 & others, i was able to flash the custom recovery & rom and got the phone to bootup atleast although faced the same issue which i'll be writing below now.
Since that event has happened, everytime I flash a custom rom, the installation happens without any glitch which includes the rom.zip & gapps_pico.zip. Now when the ROM bootups, the startup screen shows up after which it starts optimizing apps. That's where is the issue starts.
For eg. optimizing app x (single digit) of 101, it doesn't goes beyond that point even after waiting for 15-20 mins or so, and i've to manually reboot using the power button after which again the optimizing apps screen comes up and this time the figure is optimizing app xx of 16/17, and in this turn the phone successfully boots up to the setup screen and works as normal. But after a few moments when i'm done setting up all my apps and everything, random issues turn up for eg. the notification quick tiles won't drop down. And when i restart the handset, again it shows the optimizing apps screen, the phones boots up to home screen but random issues pertain.
I've tried ROM's like Stock Debloated (5.1.1) , CrDroid, CyanPOP, RessurectionRemix all based on 6.0.1.
Before installing any ROM, i do an advanced wipe and all format the data. Right now the handset is running CyanPOP but the main issue is i'm unable to access the notification dropdown. It doesn't goes beyond the header.
One more thing, I installed RR (xt1022 specfic) with same pico_gapps on my Moto E & the rom booted up in no time and working as smooth as butter till date with no issues whatsoever.
I'll be helpful if some one can diagnose the issue. Thanks
BBThumbHealer.
Did you try flash stock firmware and then flash a costum ROM ?
@Eurofighter_ty : when the issue first happened, what I remember is that I tried installing the debloated stock ROM of 5.1.1 and not the pure stock having all the unnecessary gapps. And similar issue was encountered. Same thing happened with other custom ROMs.
Today I've now reverted to a previous version of CrDroid 6.0.1 released in April and it at least runs fine when in use although a reboot causes the same issue. However, CrDroid June update and CyanPOP had the issue in which the quick tiles didn't drop down along with refusal of bootup.
Try to flash the stock ROM via fastboot with all files
Hi everyone. My Nexus 5 was running good until some days ago. Then it started bootlooping. It wasn't turning on , so I unlocked the bootloader and flashed the stock image. Nothing happened,so I flashed stock KitKat rom and after 2-3 hours it booted and lasted 30 minutes. I mean, after thirty minutes, it stucked to Google screen again. Then I somehow managed to flash lineage 14 and it booted again successfully.But as you all know that GOD Hates me a lot, after 2-3 hours it started the same drama again. And that's the story, I tried lineage,RR,aokp ... everything flashed successfully but doesn't last more than 4-5 hours or even less.But If I try stock, that never boots.
I just can't understand where is the problem.The power button is ok, I installed a kernel and underclocked it to see if there is problem with processor. No luck. This thing can boot ,but can't hold on that very long.
Another thing,when it start looping, it forget about TWRP too. I have to flash stock first,then install TWRP,then lineage /RR.
Can anybody say where is the problem??
I have used some nokias, samsung, even some Chinese phones,none of my phones died themselves, it was my only Google/LG and I faced this.
If the phone boots on a stock 4.4.2 room but gets stuck on the boot animation with a 5 or 6 stock ROM, the internal memory chip is probably failing or will fall.
audit13 said:
If the phone boots on a stock 4.4.2 room but gets stuck on the boot animation with a 5 or 6 stock ROM, the internal memory chip is probably failing or will fall.
Click to expand...
Click to collapse
What can I do?? Is it recoverable with pertitioning softwares or I should think about buying a grave plot for it?
Anyway,thanks a lot, man. You are the only one who atleast tried to help me.
Please help me out as I messed my phone up real bad recently and I need to fix it as soon as I can as I have interviews right now and need to be updated with them.
So here's what I did:
I was using Pixel Experience ROM on Android 12, with OrangeFox recovery, it was working fine with no major issues.
I really wanted to try out Android 13 though it's still in Beta but I have heard good things about it, specially the one by Project Elixir.
But since I was already using Pixel Experience and loved the ROM so much, I decided to be on the safer side and look if they have a Android 13 ROM for my phone.
That's where the story began, I mistook the Redmi Note 7 forum (lavender) as Redmi Note 7 Pro forum, I forgot how they were two separate devices.
So I flashed the Redmi Note 7 recovery on my phone and it it didn't boot into recovery when I tried it to, then I downloaded the original (correct one) from OrangeFox's official site and flashed it after which the recovery works. But then as I tried installing the new ROM, my adb sideload kept getting stuck at "Starting ADB Sideload feature" and I couldn't make it work, so I flashed the new OS from my sdcard. It was all fine, I set it up and was loving the experience until I plugged it out of the charger. After a few minutes of plugging it out of the charger, it literally started rebooting and it restarts just in the middle of the boot animation. And when I manually power it on by pressing and holding the power button, it displays that It has no charge left.
I tried flashing quite a few other ROMs too, even Android 12 and 13 both, and at a point for some reason it also showed "system has been destroyed. press the power button to shut down" while booting into recovery but it went away once I re-flashed the recovery, and after no luck, I flashed MIUI but the same thing still persists.
I read in a few forums that it might be a battery issue which I too thought at first but the fact that it happened exactly after I flashed the wrong recovery bothers me. I thought installing the stock MIUI rom through fastboot would solve it by replacing every corrupted files and partitions but the issue seems to persist.
What might have been the issue and what can I do to fix it, and can flashing a wrong recovery cause this even if I have flashed the right one just after that?
Hi guys I used PixelExperience 11 rom for 4-5 months last week phone freezed while charging I force rebooted it, after reboot, it freezed again I waited for the respond but phone turned off and not responded to anything until (charging, odin mode etc) phone charge finished and I booted with stock rom same thing happened again today. now I will wait again but I don't want this to happen again. what do you think is the problem? (so sorry for bad englsıh)
Note: this problem not happens on OrangeFox or TWRP recovery, only on system
please guys help
Try using some stable rom, kernel and recovery. Also while installing custom rom clear the system and other data neatly.