Yo guys,
I flashed the resurrection remix ROM for my zenfone 2 (Z00A) last month but its been a big pain in the a$$. Firstly,I get a lot of bootloops. Secondly, the phone sometimes shows no range on cellular service even though I should be getting it (I'm sure as heck cuz I used to get it in my house). Due to that i restart my phone and encounter the bootloops until finally I get it to work somehow. Sometimes I would even have to WIPE everything (DATA,System,Dalvic cache,etc excluding Internal and External Data) and flash the ROM,g apps , SuperSU again. These problems were encountered in 5.6.5. I recently upgraded the ROM to 5.6.6 by downloading and flashing the ROM but the same problems along with new ones :crying: came up. I usually charge my phone in the night and turn the charge off for use immediately after I wake up. The following problem was not there in 5.6.5 but in 5.6.6 the phone restarts itself in the night (probably when I'm asleep) and it just gets stuck in bootloop and is extremely hot and my hand starts to hurt probably from the radiation or something but then when I just hold on to the power button, turn it off and back on again, it works like normal and has 100% charge. Please suggest a good ROM (other than cyanogenmod as that too has the problems except the bootloop from 5.6.5) if you guys can't figure out the problem.
P.S. Yes I've tried fixing permissions
Phone: Asus Zenfone 2 (4GB RAM Edition) Z00A
Related
Hello, the problem start when I using resurrection remix 5.1.1, I using it with agni kernel for 2 months without any problem until yesterday when I browsing using wifi, suddenly my wifi won't detect any networks, it keeps searching the networks, also bluetooth and tethering suddenly not working as well. If I turned on the Bluetooth I got error message "Bluetooth share has stopped working".
I think this caused by the rom so I clean install the rom, wiped everything except external sd card, but the problem still persist.
Then I trying to flashed DN4 rom but I got bootloop, it stucks at Samsung Note II screen, this rom was working great before I move to RR rom.
Now I go back to RR rom, but the problem getting worse now, every time I put my phone to sleep the phone get restarted, so I let the screen turn on, set the sleep time to 30 min. Someone tell me to try restoring stock rom but since I have limited bandwidth, I want to fix this without downloading stock rom. Please guide me how to fix this, is this hardware issue?
Sorry for wong English.
Sent from my GT-N7100 Resurrection Remix
Hi guys this problem finally solved by doing this method http://m.youtube.com/watch?v=QiiH5b82eew
I just don't believe, I just don't know what should I do, so I just try it, this method does not make sense but yes, it's working [emoji28] sorry for the trouble.
Sent from my GT-N7100 Resurrection Remix
A fair number of unlucky LG G3 owners using AOSP/CM-based ROMs, myself included, have a major problem with the issue where a reboot/power-on cycle results in the phone getting stuck at the LG or boot splash screen ad infinitum.
The only way around it is to do a battery pull, sometimes several times, before the phone eventually recovers, but not until after it's gone thru its "Optimizing" or "Upgrading" apps, which takes 5-10 extremely annoying minutes.
I'm using a D851 and have this issue with every ROM I've used (Xenon, Exodus, AICP, to name a few).
This is not a battery issue as I've had the same problem using batteries from 3 different manufacturers. I've also had the same problem when plugged in.
If anyone knows of a fix - would be greatly appreciated (please don't say factory reset or root back to stock - I've already done this and it doesn't fix this issue).
I also have this problem with aosp and cm roms, i also get bsod sometimes. I think that maby the battery is broken, but im not sure since i dont got any problems on stock. When i get money for a new battery i will reply here with results.
I got my new battery today and it bootet up instantly
I had this issue on my d852 running cm12.1. It turns out using autorec is what caused it for me. I fixed it by flashing a kitkat tot then installing twrp using flashify. Once I had twrp installed I flashed the modem.bin from a lollipop d852 kdz. I haven't had a shutdown/reboot hang in a week now.
I have the same problem D851, it happens on latest builds of exodus and aicp. candy and blisspop works fine without any issues. I have changed the battery but the problem persist on exodus and aicp
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now ,
.......
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
This problem is a little confusing and beyond me, but I have to ask and suggest one thing.
Instead of doing OTA, Have you tried to just use odin to flash the Marshmallow firmware you want?
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
Odin MM like suggested.. Don't do any mods. If it persist, then you might be looking at faulty hardware ie main board.
i just flashed MM after reading your replay , and will test it out.
any tips on what to do with the phone if it's a hardware problem ?
so right at the first boot i had this error shown in the images (attachment)
i removed the battery and restart the phone and it booted correctly , the same problems began to show freezing random restart and it keeps booting to recovery and i had to add and remove the battery a couple of times to turn the phone on .
i returned to stock 5.1.1 apparently it's the most stable thing i can use right now , honestly i'm puzzled on this problem i'm quite sure it's hardware and software somehow and if i send it to a local shop they probably will say "i don't know what seem to be the
problem "
so i'm just going to keep using it until it becomes a replacement parts for his other brothers . :crying:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
akira6968 said:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
Click to expand...
Click to collapse
Here is the thing though (I have the same issue). If you remove the battery and put it back in, say 30 seconds later, it won't turn on. If you remove the battery for like 5 minutes and then put back in, it might turn on. I'm talking about the first little vibrate it does when holding the power button to turn on. It really acts like a hardware issue to me. The only work around that has worked for me is an app called wakelock. Using this app and selecting partial partial wake lock makes the phone run completely normal.
What REALLY sucks right now is that I have an OTA update waiting for me and the phone needs to reboot to install. The phone won't reboot. When it turns off, it won't turn back on without removing the battery for 5+ minutes.
IT is the MM Update
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
gbennett21 said:
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
Click to expand...
Click to collapse
Yes having the same issue as well but now even the wakelock app won't keep it. The phone wil stay for maybe an hour, then reboots and will continue to reboot until I take the battery and then start it again afterwards. The length of time the phone stays on varies really and it could be as long as 3 or 4 hours, but it will definitely reboots itself, I cannot got 1 day without this happening. At this point the phone is unusable. I am on another phone at the moment.
I did flash the MM updates (even went back 3 or 4 older versions) using ODIN and same issue. I am debating whether I flash an older Lollipop version and see if that makes a difference.
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.
The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.
Hi there,
I'm new to this thread,
I own a one plus three for 1.5 years, i have rooted by phone and flashed many custom roms, recently i flashed franco's kernel to test out the battery life. The next day mrng my phone started rebooting on its own,it kept on rebooting every minute or so,it never went past the one plus logo at many times. I tried flashing stock rom with recovery ,tried stable stock oos rom ,no effect.
My friend thinks it is a hardware pblm ,however i have never dropped the phone and handle it with care. Kindly give me ur suggestions...Thanks in advance
whenever Wireless LAN was turned off or disconnected, a kernel panic due to a netfilter bug (or similar), caused a reboot. And I don't know how to fix it.
Hmm