Hi!
Is not my first time flashing a custom ROM but... Since a couple weeks ago I received flashed No Limits and usually in 3-4 seconds my OP5 booted up now needs 10 seconds approximately...
I already wiped everything included the internal storage and re flashed it because I had a problem with Google wakelocks, now everything is smooth and cool except the boot up
May somebody have any idea of a possible solution?
Thanks guys and have a nice day!
VSMiguel said:
Hi!
Is not my first time flashing a custom ROM but... Since a couple weeks ago I received flashed No Limits and usually in 3-4 seconds my OP5 booted up now needs 10 seconds approximately...
I already wiped everything included the internal storage and re flashed it because I had a problem with Google wakelocks, now everything is smooth and cool except the boot up
May somebody have any idea of a possible solution?
Thanks guys and have a nice day!
Click to expand...
Click to collapse
Ten seconds sounds normal for a proper reboot. Three to Four seconds sounds like you were using the 'Hot' reboot option before.
Nothing here to be concerned about.
Related
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
ChameleonGeek said:
Hello i have a serious problem
I have infinite bootloop in every ROM, every baseband/radio, and in stock. I tested the (4.2, 4.4, 5.0) and any of this works. I wiped the system/data/cache/dalvik a lot of times and installed the CM11 in 4.4 baseband but still not working.
The bootloader is unlocked and fastboot working well. I spent all the day testing solutions of my knowledge but dont work.
Any idea?
Click to expand...
Click to collapse
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
acejavelin said:
Have you tried just flashing the full factory images? Or booting TWRP via fastboot and looking at the results of a manual wipe to ensure all partitions are "good"? Often when I hear about an "infinite bootloop" on every rom, it means the internal storage is bad, sometimes flashing the factory images helps, and sometimes it's just time to put the poor thing to rest... :/
Click to expand...
Click to collapse
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
ChameleonGeek said:
I solved it with a rare solution, i install the stock Android L wait for the bootloop and i press the power button until the phone power off later i restart and works and it works in every stock ROM. Sounds weird but works.
Click to expand...
Click to collapse
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
acejavelin said:
Definitely weird... How long are you waiting for this "bootloop"? The reason I ask is because the first boot on lollipop takes an extremely long time since it is ART, 10-15 minutes for first clean boot, or over 30 minutes with a dirty flash isn't unheard of, and the first boot doesn't give the "Android is updating", just the swirling circles, if you interrupted it you could have other issues later on.
Click to expand...
Click to collapse
I wait several times more than 10 minutes. I wipe data/cache after restart the phone. I found the solution in Google Forum: https://productforums.google.com/forum/#!topic/nexus/D2vKK9rLgh8[1-25-false]
You should only have to wipe /cache from recovery to get out of it. I believe wiping /data is unnecessary (so you can avoid losing your data if you are concerned.
Hello there xda.
I have a Samsung Galaxy Note 4 SM910F.
So what is happening to my phone is that whenever I am in any random app lets say reddit or even chrome for example. It will like freeze for a minute or two and then unfreeze.
In more extreme cases it will reboot.
So this happened randomly because I flashed a Stock unbloated 5.1.1 ROM from here back in december and everything was working smoothly and stuff. I had xposed installed and all my apps. Then in February it started with this random freeze/reboot. I had not installed anything else apart from what I had for the last 3 months.
So I restarted the phone, changed the battery and stuff to see whether that will fix it. However it didn't. So I formatted the phone (the soft type) just so I can install another ROM. So I tried another ROM, flashed the correct CP and BL and stuff and then just installed chrome and whatsapp. After an hour or two the same thing happened. So this time I factory reset he phone, like a complete wipe and I installed the unbloated ROM once again with few apps. Same thing happened...
So my last resort was to install Cyonagen Mod. After an hour or two same thing happened...
I don't know what is the problem. I read about some peoples phones emmc failing and thus the freezing, but I am not sure yet.
Please could you guys explain what I should do to fix this?
Thank in advance!
I have the same problem. Starting on mid january. I'm on stock 5.1.1 with root and twrp recovery
Tried backup and factory reset
I went back to stock after I factory reset the phone. And still had the same problems.
People say that its a hardware problem... So I guess I'll have to send it back to Samsung soon.
I think I tripped the knox. I just have to unroot and get it back once again to stock and send it back. I hope that they accept it.
i have the same problem. my model is SM-N910W8 and I bought it from 2nd hand, so no receipt and no prove of purchase.
can I still send it back to samsung to fix it?
same problem as you and now my phone died completely .
my phone was 4 months and he has not supported any longer he died naturally lol.
my operator gave me another free under warranty because the phone had a faulty motherboard and after several back galaxy note 4
This started happening to me a week or so ago and my phone just got stuck in a boot loop after it froze and rebooted. I'm on the latest stock firmware. Tried factory reset, reflashed stock firmware, nothing helps. It still reboots (sometimes it almost gets booted completely, other times it reboots after 2 seconds.
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
EclipseX said:
Just disable finger print. Yes that magic feature offered by Samsung is causing more hungry that happiness since S5
Click to expand...
Click to collapse
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
HXOY said:
Many thanks. This was driving me mad for a few days, I had tried three different ROMS, completely wiping everything. I eventually went back to stock, which I'm still running and it was the same; it would run fine for a few hours and then start to lock up until eventually it would either reboot or stop responding and I'd have to pull the battery to restart it.
Just not selecting fingerprint security doesn't work, you have to force stop "Fingerprints" in Application Manager (All).
Click to expand...
Click to collapse
EclipseX said:
just do not setup the finger print lol. I was having those problemes too when I bought the note 4 until someone tell "do not setup the finger print" lol, not I'm a happy user.... I hope that android 6.0.1 solve the probleme
Click to expand...
Click to collapse
Spoke too soon, it's started rebooting itself again.
Same problems here since 2 days. I was on original 5.1.1 software... Very strange all those people with the same problems
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Davids said:
did the problem was resolved ? started to have the same problem 3 days ago ! was on 6- flashed stock with full wipe..nothing ! downgraded to 5.1 with full wipe via odin...again nothing !
WTF [email protected]!
Click to expand...
Click to collapse
Still having the same issue around the same time everyone else started experiencing it.
I also was rooted and had xposed installed on 4.4.4 before the issue started happening.
Try the solution provided here & report back..
http://forum.xda-developers.com/note-4/help/note-4-sm-n910f-freeze-restart-issue-t3439111
Hey there,
I am having a recent issue with my phone, where everytime I reset it or do a power off and reboot, the phone will constantly get to the boot logo (in this case cyangemod) and reboot after 5-10 seconds.
It ends up working but only when I let it do this cycle for about 30 minutes or so.
I have looked everywhere, I cannot find someone who is having a similar problem as me.
I am running the latest Cyangemod nightly rom, because I thought the issue was the ASUS rom, I have tried wiping cache, doing a factory reset etc... but no luck.
I also have the latest TWRP recovery and unlocked bootloader.
Any help would be gladly appreciated, Thank You.
Let me know if any video evidence is needed to further clarify, the problem I am having.
Fa7aLX__x said:
Hey there,
I am having a recent issue with my phone, where everytime I reset it or do a power off and reboot, the phone will constantly get to the boot logo (in this case cyangemod) and reboot after 5-10 seconds.
It ends up working but only when I let it do this cycle for about 30 minutes or so.
I have looked everywhere, I cannot find someone who is having a similar problem as me.
I am running the latest Cyangemod nightly rom, because I thought the issue was the ASUS rom, I have tried wiping cache, doing a factory reset etc... but no luck.
I also have the latest TWRP recovery and unlocked bootloader.
Any help would be gladly appreciated, Thank You.
Let me know if any video evidence is needed to further clarify, the problem I am having.
Click to expand...
Click to collapse
Sorry I don't have good news or a solution for you. Just wanted to chime in that you aren't alone. This randomly happened to me on Sunday in the car - I noticed that I suddenly had no signal in a pretty well developed area that I frequent, so I tried restarting and I've been down ever since. Unlike you, I didn't wait it out too long, maybe 5 minutes at the most, when the phone started to get warm.
I have tried going back to stock recovery and firmware and have seen no success. Contrary to other people reporting problems, I hadn't done anything to my phone leading up to this. I think I upgraded the modem several days before, but other than that, everything was running pretty smoothly.
same thing was happening to me after a bad flash. Stock recovery, stock lolipop, wipe data and cache, boot once, reboot to recovery, flash latest MM package on asus's site.
This is the only thing that fixed the bootloops.
Hello all,
I recently went through the process of installing CM 14.1 on my Verizon-Unlocked Galaxy S5.
Everything was working fine until about 3 weeks ago when I started messing with the system settings.
My phone started freezing and crashing, so I attempted to reinstall CM 14.1 multiple times.
I have wiped everything on the phone multiple times through TWRP (System, Data, SD Card, Everything...) and I am still having the same issue.
The phone boots fine, and I am able to get through the first two menus in the initial setup, but then the screen freezes and the phone restarts.
I have tried replacing the battery, thinking that would fix the problem, but it didn't...
Should I revert back to the stock ROM and start from there, rooting and such, until I make my way back to CM?
Thanks everyone, Luke
If youre still having problems, try reflashing your rom and then flash an older version of opengapps, I think I used the one from 01/16/17. The new opengapps were giving me the same exact problem.
Dang, I wish I would have seen this sooner... I went ahead and flashed back to the stock Verizon ROM with root. Thanks though! Maybe this can help someone else.
Hi all, earlier this morning, my phone was working perfectly fine. Somehow, 5 mins later after checking my phone, the screen was unable to be switched on, so I decided to hold onto my power button. My phone came alive subsequently, but all my apps were missing, and all that's left were the MIUI apps. I've attempted to reflash 10.3.15 xiaomi.eu but to no avail. My "other files" shows that it's 20gb as well, so could it be that my old files were there? Anyone has any encounters or solutions for this?
I experience same problem. But the thing is im using official MIUI and havent done any bootloader unlock. I dont know if this is hardware problem or what.
Same issue here. Stable Rom on the 9T (10.3.11). Phone just went dead this afternoon. Screen wouldn't power up. Held down the power button... Took a few extra seconds to start up then a few minutes to boot.
I lost all my settings, my data, my whatsapp messages, all my apps... And the phone started with just my miui apps. Ironically, sms were still there, fingerprint still loaded, call settings gone... Weird.
This is concerning since their hasn't been a Rom update in months and this issue popped up out of nowhere... And it's happened to a few of us.
LYZQ said:
Hi all, earlier this morning, my phone was working perfectly fine. Somehow, 5 mins later after checking my phone, the screen was unable to be switched on, so I decided to hold onto my power button. My phone came alive subsequently, but all my apps were missing, and all that's left were the MIUI apps. I've attempted to reflash 10.3.15 xiaomi.eu but to no avail. My "other files" shows that it's 20gb as well, so could it be that my old files were there? Anyone has any encounters or solutions for this?
Click to expand...
Click to collapse
For some reason partition was corrupted.
Happen usually when FSYNC is off.. but it should not on stock ROM.
I would suggest to flash another ROM, even if stock since your version must have this nasty bug
Or you just booted to safemode? Just reboot it normally and you get all of your apps back.
Rebooting doesn't replace the apps. They are gone. The file manager showing that the phone has 10GB more available storage reinforces that. Whatever the bug is, it's affected 2 different official roms and a xiaomi.eu rom. This isn't good.
i experience the-same thing on miui 10 eu stable. that's why i switch on miui 11, even if it is beta i think it is most stable yet so far.
Same here. On stock ROM, over the last months, my phone crashed and was hot. I had to press the power button during 10 seconds to reboot. It happened 4 times, and the last time it happened, all my apps were gone. I contacted xiaomi support via chat, they told me to ask for a RMA if it happens again.
I unlocked the bootloader & installed xiaomi.eu MIUI 11.0.3.0 yesterday, I'll give it a few weeks to see how it evolves. If it crashes again, I'll ask for a RMA.
Hello does any one knows why is this happening?
Yesterday happen to me.