After having re-installed my apps from Google Play, my device went on loop boot (or almost).
It takes 2 or 3 loops to be able to boot correctly.
First boot only take 10 seconds after the Samsung logo. Once on lockscreen, the device restart, takes longer time to boot, and then reboot ...
And when GNote3 finishes correctly the boot sequence, some of the folders i have created are empty.
Another bug is the lockscreen ink effect : colors changes are not taken in account.
I thought that the boot issue was due to one of my app (but what the hell ! all of them were running smoothly on my previous GNote2) but i think the problem could be related to bad data management ...
Nani said:
After having re-installed my apps from Google Play, my device went on loop boot (or almost).
It takes 2 or 3 loops to be able to boot correctly.
First boot only take 10 seconds after the Samsung logo. Once on lockscreen, the device restart, takes longer time to boot, and then reboot ...
And when GNote3 finishes correctly the boot sequence, some of the folders i have created are empty.
Another bug is the lockscreen ink effect : colors changes are not taken in account.
I thought that the boot issue was due to one of my app (but what the hell ! all of them were running smoothly on my previous GNote2) but i think the problem could be related to bad data management ...
Click to expand...
Click to collapse
I had a continuous boot loop problem after installing a few apps. It freaked me out as I spent a long time getting everything looking good on the phone. I thought it was going to be a case of hard resetting.
I removed the SD card and suddenly all was OK! I had been using the card in a different phone. So I removed any system folders from the card and everything worked fine. That is until I reinstalled some other things and the problem came back. So I reformatted the card in the phone and now it all seems to be working.
I also had problems with changes not sticking on the lock screen. They too are now working after I did the above.
Hope this helps.
Related
Hi
Few days ago, my device started to give me problems with a infinite loop boot.
The device boot, but when it is loading all the apps, or a little after that, the device makes a "mini" reboot, the screen goes black, the music goes on and the device tries to load again all the apps and the UI, and I lost the connectivity.
I don't know if its a device, sd card or any new app or upgraded one. How can I know that? Any possibility to monitor the boot and looks what is the problem?
Any other idea?
Hello everybody.
I am a Defy Red Lense user with a recently flashed PA 2.14 build (coming from 2.00 version of same ROM). At first 3-4 boots everything was ok, till I made some changes on phone config (namely enabling 16 bit transparency as recommended by it's maker, and then some small changes in Paranoid Android Settings) and asked me to reboot. Ok so I went to reboot and as usual, it booted me into bootmenu, and I chose "boot" and "2ndinit" as usual. After a odd bootloop (where the phone wouldn't go through the blue, then green LED sequence and would then reboot, show Moto logo boot animation, rinse and repeat, etc) that I ended by pressing vol - and entering, again, into bootmenu, I chose again boot and 2ndinit and then something really weird happened:
After almost half an hour i'm still stuck at the very ROM booting animation (the Paranoid Android one, no the Moto logo), just like the guys that tried that new kernel that were reporting 15+ min first boot times. As a clarification, my first boot with just flashed 2.14 took, at most, 5 minutes. And there is another odd vehaviour, concerning the PA boot animation: it gets randomly stuck for a few secs and continues as usual, with no looping from 0 just like the normal loopboot.
So here comes the questions:
- What is really happening? is it really booting or the phone is just stuck in ROM bootanimation? How long should I wait to consider shutting it down?
- Is there some way to get out of it/shutting it down without damaging the device? Can I just pull the battery off without bricking the device?
Looking fowardd for some theories behind this issue :good:
Well, seems like it was OK to unmount the battery while on ROM booting animation, since I haven't had mayor problems after doing so and rebooting. Now the phone works just fine.
Tho im still curious the reason behind this pseudo-bootloop. Thanks for reading anyways :good:
I rooted my Note and all was good for a while, but i think i must have changed a setting in Wanam Xposed, but i can't put my finger on what...Whenever I restart my Note, I go through the boot animation and then the lockscreen shows for a brief second before it goes into a second boot. The animation is the same both times (I have changed my boot animation in the system folder). I'm not sure why it started doing this. Any help would be appreciated.
bilichjl said:
I rooted my Note and all was good for a while, but i think i must have changed a setting in Wanam Xposed, but i can't put my finger on what...Whenever I restart my Note, I go through the boot animation and then the lockscreen shows for a brief second before it goes into a second boot. The animation is the same both times (I have changed my boot animation in the system folder). I'm not sure why it started doing this. Any help would be appreciated.
Click to expand...
Click to collapse
I started having the same issue on a 100% stock phone. Found resolution here (not enough posts for a link yet): androidforums.com/samsung-galaxy-note-3/791631-note-3-booting-boot-so-nice-does-twice.html. Turning off "Always allow scanning" from the advanced wifi menu stopped mine from booting. It almost seems like the first time it boots it crashes and has to reload TouchWiz or something. Not sure how the wifi scanning affects booting, but it worked for me.
http://forum.xda-developers.com/lg-g2/help/phone-bricked-t3380584 is the start of this.
The story is: two identical D802s purchased at the same time. One works fine. (DirtyUnicorns 6.0.1 v10.2). The other had the problems in the link above. Currently, when it boots, it looks like it it getting into a boot loop: black screen --> LG Logo --> Black Screen --> LG Logo. It does the LG logo a random number of times, sometimes 2 or 3, sometimes 10 but eventually the OS loads (DU logo) and it's fine from there. So, it is not a true boot loop.
What I have done is done a full TWRP backup of a working phone, copied it to the other and then restored all partitions except EFS. When I reboot the dodgy phone, it still does it pretend boot loop thing and eventually boots up. (The working phone of course boots normally.) I'm not sure where the differences are. If I swap the SIMs between the working phone and the dodgy one, the problem remains with the dodgy phone. Faulty phone hardware maybe?
(NOTE: for non-native English speakers: "dodgy" = not completely broken but partially broken!)
Any thoughts?
No one?
Hey everyone,
So my phone died and then I got it charged and turned on and it booted up to the encryption lock screen where it says to start up your device, enter your pin. So I enter my pin and then its says, "verified" and then "starting android". and then a padlock appears on the screen, it opens, and there's like a load up circle going around it. At first, I let the phone sit to see if it would do anything but after an hour, I figured something is wrong. I dont know why this happened, I think I might have accidentally turned on the secondary encryption, but this really sucks, I don't want to have to factory reset and lose all my pictures and data. I can boot into recovery mode but sometimes when i turn it on it shows a screen that says installing update and has like a google ring looking thing that should be spinning around but it looks like its glitching out, after that screen it will go to a no command screen, and then it will eventually reach recovery mode. I really hope someone can help or knows what is going on because, I really dont want to lose all my stuff.
Thanks for your time
I tried posting link but im new, if you look up s7 edge frozen encryption, its the first link , another person describes the same issue.
I had this issue. In recovery, tell it to clear the delvic cache. Then try a reboot.
It too a few attempts before the phone would not boot directly into recovery. But once i got it to do a normal boot, it started normally.
Then after it's running, back it all up, boot into recovery, and do a system restore.
Hi I wonder if anyone can help me. I restarted my phone, it asks for my pin which I enter correctly. It then gets stuck on spinning padlock. I've tried a soft reset (I think that's what it's called, holding down power and volume keys). It restarts, I enter pin, it says starting android then gets stuck again. I'm not very tech minded (typical girl). Can anyone help. I'd rather not lose all my photos and apps. Thank you so so much in advance. Toni x
I am facing the same issue, but with a Samsung Galaxy S8.
- Safe mode: doesn't boot
- Recovery mode: works, clear cache doesn't solve the problem.
So since nothing worked to make it work (except the Factory Reset, but I didn't tried this option), I decided to wait in the padlock screen. After 3 hours the phone started.
I guess that the phone is decrypting some big file during startup. Indeed, some days before before this problem happens, I downloaded some big files via torrent (~2-4 GB video files).
I'll delete these files and make some tests to understand the source of this problem.
Have same issue after recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.
Have exactly the same issue..Please help
After recent update, tried clearing cache and safe mode but didn't help, been on padlock for about 10 hours now, any solutions/experiences?
ps: on stock rom with stock recovery, no root or anything of that sort at all.