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.
Related
Hi Guys
When I turn my phone on, after the Galaxy S first screen, the screen is multi-colored for about 1 second before going to the boot animation. Once the boot animation appears the screen is fine.
That's not a problem. What is a problem is booting into recovery, the top of the screen has a few blue lines. It still operates as if it is in recovery, as if I press the power button it reboots - but if I press down once, then power, it's not rebooting. So it looks like it's just the screen can't display what's being sent to it. So I can't do anything in Recovery like installing the auto-phone record, screen capture service or extended power menu. It will also be a problem if I come to install another ROM.
Does anyone know why? It started happening after I flashed a new ROM - I flashed the new ROM because the phone was constantly freezing when running certain apps (and needed the battery removed to restart the phone) - it's no longer freezing.
thanks
I'm not sure but,i think it because you don't have the good bootloader.For example,if you flash a rom from Froyo to gingerbread,you need to choose a rom with the gingerbread sbl(bootloader) include.
So to avoid this problem,just re-flash the entire rom with boot loader included.
Just go there http://forum.xda-developers.com/showthread.php?t=1102881
thanks I'll try that
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:
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.
So I was running CWM (Philz) I believe, and I had been running into issues while on rooted 4.2.2 D800 stock ROM. There were force closes and random reboots, etc. I've only installed xposed mods. I've also used android tuner to adjust some of the build.prop and kernel presets.
However, after my phone got stuck in what I thought was a boot loop, I finally got it up and running. What happened next was odd. I tried booting into recovery -> the "LG" splash screen showed up and it went into another infinite boot loop.
I'm assuming I somehow corrupted or lost my recovery. Any advice on what to do? I don't know if I should follow the original instructions for flashing a recovery here - http://forum.xda-developers.com/showthread.php?t=2633150.
Edit: Jesus christ my phone infuriates and confuses the hell out of me. After attempting to enter the recovery again, I am now stuck in a permanent boot loop. The last time I fixed it was by turning my phone off....and then *WAITING*.
What? That doesn't make sense you say? Of course it doesn't. But that's still what worked. I waited 12 hours, and then tried turning it on again. When I did, oh look, the AT&T screen!
CONFUSING. help please...
Double edit (Hard Mode): Going into download mode when I'm in this constant bootloop = nothing happens. That little icon that says "Download Mode" with the 5 blue circles just stays there, and my laptop ends up not recognizing anything. This happened the last time too, and all I was able to see on my laptop was "QHSUSB_BULK". I thought this meant that I would have to do a complete wiping process through Linux (found on another thread somewhere), but apparently waiting 12 hours also fixed the problem.
Hi guys,
Something strange is happening to my zenfone. When I want to switch it off, and I click the "power off" option my phone activates offline mode, then the screen just dimms instead of going full black. When I try to switch it on again, everything is okay except that my phone doesn't vibrate and goes straight to boot animation, there is no loading system circle, phone boots up in 3 seconds. I don't need to enter pin too. When I choose restart option everything goes as normal. Any help is appreciated
Zf5
Not rooted
Android 4.4 kitkat
Gumak11 said:
Hi guys,
Something strange is happening to my zenfone. When I want to switch it off, and I click the "power off" option my phone activates offline mode, then the screen just dimms instead of going full black. When I try to switch it on again, everything is okay except that my phone doesn't vibrate and goes straight to boot animation, there is no loading system circle, phone boots up in 3 seconds. I don't need to enter pin too. When I choose restart option everything goes as normal. Any help is appreciated
Zf5
Not rooted
Android 4.4 kitkat
Click to expand...
Click to collapse
Its a common issue.
Just wipe everything from bootloader, like system, data,cache, then flash recovery.img from .44 update and then reboot to recovery and sideload the .54/.540 update.
everything will be fixed.
Me and my friend faced the same issue about a year and a half ago,and this fixed the issue.
What does 'sideload' mean? Sorry I am new here :v