so i used "reactor" from this thread http://forum.xda-developers.com/showthread.php?p=11791096 and now my phone is boot looping. ive used many different boot animations and NEVER had this problem. can a boot animation cause this? is there a way i can get into the system to delete this thing or am i looking at another reformat?
mrmako777 said:
so i used "reactor" from this thread http://forum.xda-developers.com/showthread.php?p=11791096 and now my phone is boot looping. ive used many different boot animations and NEVER had this problem. can a boot animation cause this? is there a way i can get into the system to delete this thing or am i looking at another reformat?
Click to expand...
Click to collapse
Nandroid Restore to a point prior to flashing this boot animation.
are you sure those bootanimations are compatible with our phone?
shame on me for not making a backup. i never flash roms so ive never used any backup programs except for tb. how do i tell if a boot animation is compatible with our phone? ive always just copied the boot animation over to the system with root explorer and never had an issue
i forgot to mention that the animation runs perfectly fine until the point where it would normally go to my home screen, then it just freezes, then reboots. not sure if that makes a difference
mrmako777 said:
shame on me for not making a backup. i never flash roms so ive never used any backup programs except for tb. how do i tell if a boot animation is compatible with our phone? ive always just copied the boot animation over to the system with root explorer and never had an issue
Click to expand...
Click to collapse
Screen Res is the thing to look for as long as it's 480*800 it should work.
neidlinger said:
Screen Res is the thing to look for as long as it's 480*800 it should work.
Click to expand...
Click to collapse
i downloaded it using absolute system tools. i believe it was 480x800 iirc
mrmako777 said:
i downloaded it using absolute system tools. i believe it was 480x800 iirc
Click to expand...
Click to collapse
That's odd. I use that app well and i've never had a problem. it should of been 480*800.
I'm experiencing the exact same problem. I used Absolute System Tools and then Root Explorer, anyhow, it plays, but then reboots. I got it to load the phone system and boot up correctly ONCE, then next time I rebooted, bootloop! Thankfully I used the recovery console to manually replace that bootanimation with the default system one and got right back into my phone!! Thankfully didn't have to reformat it!!!!!!!!!!!! Just went into ClockworkMod recovery and mounted system, then adb'd into there to fix it.
petermg said:
I'm experiencing the exact same problem. I used Absolute System Tools and then Root Explorer, anyhow, it plays, but then reboots. I got it to load the phone system and boot up correctly ONCE, then next time I rebooted, bootloop! Thankfully I used the recovery console to manually replace that bootanimation with the default system one and got right back into my phone!! Thankfully didn't have to reformat it!!!!!!!!!!!! Just went into ClockworkMod recovery and mounted system, then adb'd into there to fix it.
Click to expand...
Click to collapse
did you use the same boot animation i did or a different one?
petermg said:
I'm experiencing the exact same problem. I used Absolute System Tools and then Root Explorer, anyhow, it plays, but then reboots. I got it to load the phone system and boot up correctly ONCE, then next time I rebooted, bootloop! Thankfully I used the recovery console to manually replace that bootanimation with the default system one and got right back into my phone!! Thankfully didn't have to reformat it!!!!!!!!!!!! Just went into ClockworkMod recovery and mounted system, then adb'd into there to fix it.
Click to expand...
Click to collapse
how did you fix it and commands (all)? Thanks
Related
Just a little curious...
I have a i9000m from Bell, and somewhere between applying some lag fixes, overclocking, a trying to get into recovery via buttons (fail, only adb works), my boot logo now changes from "GT-i9000m" to "GT-i9000" ("m" disappears) during boot. I assume that's from applying things that are made around a i9000? And also I have no more boot/off animation. Guessing both of these things are from doing Mimocan's lag fix? I since then undid his and changed to RyanZA's one click v1 (update.zip version), but it all remains.
Wondering if anybody out there has some wisdom to share
I'm not too too worried about these things, but Its kinda lame with no animation If anything, I would remove the startup sound, but only when I get my animation back.
My boot animation also doesnt show up anymore But you can hear the swoooosh sounds and so on...
not sure if this applies to your problem.
I had a similar issue after lag fix, noticed that playlogos1 and playlogosnow files were exactly the same. I got the original playlogos1 file from another galaxy and renamed to playlogosnow, then replaced the dodgy playlogosnow from my phone.... that fixed it for me. (files are located in \system\bin\)
The way I understand it, the lag fix renames the original startup animation from playlogos1 to playlogosnow, then copies a script called playlogos1 in its place which ensure the fix is applied after reboot, the script also calls the animation "playlogosnow".... in my case I screwed up and ran the lag fix twice, which resulted in both files being exactly the same and the original animation getting wiped.
Hope that makes sense.
The poster above me is spot on. Just flash more roms to fix it i guest
Sent from my GT-I9000 using Tapatalk
playlogos1 is the boot logo, the mount on boot script for lagfix renames the boot logo to playlogosnow.
Somewhere along the line one of the devs may have included a logo that is used instead of your stock one, specially when reverting. ( Prevents problems if you try reverting without actually doing the lag fix. )
Old thread bump
I have similar behavior to OP.
My boot screen shows GT-I9000M for a few seconds, then it turns to GT-I9000 before going to the animation (the M disappears).
I first noticed this about a week ago when i started using Doc's roms, currently I'm running Docs' JPA v7 with no lagfixes.
I'd like to get the correct boot screen back with the "M", is it just a matter of getting an original copy of a bell bootlogos1 file and dropping it into /system/bin (overwriting the current one)?
Doesnt OCLF have the option to restore boot animation\logo??
alferret said:
Doesnt OCLF have the option to restore boot animation\logo??
Click to expand...
Click to collapse
I'm not sure if OCLF had that option, ive only ever played with the lagfix options in Clockwork Manager. I don't see any options to restore boot ani/logos there.
I don't know how I did it, but everyone else is trying to boot into Clockwork Recovery mode successfully...and the whole pull the battery mode doesn't work 100% of the time...buuuut...I CANT STOP!
I can't stop booting into Clockwork. Every time I turn my phone on, it boots into the Clockwork Recovery, without fault. I've rebooted almost 30 times now and every time its done the same thing. Once it reboots into recovery, it will allow me to reboot the phone and then it boots normally. I really want to fix it, its annoying. The phone still works without any issues, its just really annoying that I have to sit there and watch it boot up to get it to the actual phone.
I don't want to unroot and start over with it all because I've made so many small changes to the phone and made it my own.
Sooo, pleeeeeeeeeease anyone with any info or fixes; let me know!
Mine did that too so I flashed the SBF and started over from scratch. I am afraid to try the D2 Bootstrap again for that reason. For now I can live with it. Did you find a fix yet?
How does this work?
When your device boots up, there is a init.rc script in your boot image that runs various components found in /system. The Droid X recovery bootstrap mimics the "logwrapper" binary. The hijacker then looks for "/data/.recovery_mode", and if it finds it, it unmounts /system to prevent android from starting. It then starts up recovery instead.
That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
kwheel596 said:
Worked for me! Thanks for that!
Apparently it only happens randomly to some people. My roommate has a Droid2 and his never did it....weird.
Click to expand...
Click to collapse
Glad it worked. It happened to me too and I just used the sbf file to restore everything. Did you use any mount adb commands before you had that problem?
To be honest I have no idea, I've had android phones for a while so I was just flying through the commands and don't remember what was typed
Unable to remove "ClockworkMod Recovery"
[/QUOTE]That's from Koush's site. Have you tried to delete the .recover_mode file if it clears it up? If you do try may you please post back?[/QUOTE]
So, I looked throughout my sd card, and have been unable to find any ".recover_mode" file.. I still get the ClockworkMod Recover screen EVERY time I reboot my device.. I have rooted and unrooted multiple times to try and figure out this problem, as well as searched through this website for answers.. I am not finding any.. HELP!?
Ultimately, I would like to just restore my phone to factory so I can pass it on to a friend..
Thanks in advance for everyone's help!
Chenoaem
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
enkrypt3d said:
Im not able to get into recovery at all... even after flashing recovery using rom manager... and the koush flash doesn't work either. When I try to boot into recovery, it just shows the yellow triangle and the ! and the android icon.....what can i do to get around this? The device is rooted using z4root..... thx!
Click to expand...
Click to collapse
nevermind... forgot to hit the search key! doh!
I don't knwo where to post this exactly so here it goes.
I installed revolution 2.09 on my rooted HTC HD without any problems.
Run perfectly. Then today I installed a ROM of a theme from this forum as well called media 1.3 with rom manager.
After the reboot my phone only shows a the text android with a slight moving glow over it. It does not repsond to anything any more. I removed the battery but the same thing is happening.
Did I brick it? What can I do?
Willem Kloppenburg said:
I don't knwo where to post this exactly so here it goes.
I installed revolution 2.09 on my rooted HTC HD without any problems.
Run perfectly. Then today I installed a ROM of a theme from this forum as well called media 1.3 with rom manager.
After the reboot my phone only shows a the text android with a slight moving glow over it. It does not repsond to anything any more. I removed the battery but the same thing is happening.
Did I brick it? What can I do?
Click to expand...
Click to collapse
thats just the default android boot screen, looks like the theme messed up your framework... hold on i'll make a .zip you can flash from recovery to fix it
Thanks, but how do I get the zip on the phone? It does not react to anything anymore. I attahced it to my PC but nothing....
Willem Kloppenburg said:
Thanks, but how do I get the zip on the phone? It does not react to anything anymore. I attahced it to my PC but nothing....
Click to expand...
Click to collapse
im just downloading the rom for you now so i can extract the framework, if you pull your battery out, you can either plug in your charger while its off, this will bring up recovery, or while its off, hold vol down and press power, that will take you to bootloader, and just pick recovery from the list, now when in recovery, if you navigate to the mounts and storage menu, choose the option mount usb storage, you can now connect to a pc as a disk drive and copy stuff to your sd card
im having trouble uploading attachments to xda at the min dya want me to upload it to megaupload for you?
AndroHero,
Thank you for helping me out. I didn't know about the vol down press power option which allows you to acces the sd card and intall a new rom. I had the revolution rom 2.0.9 already. It's installing as we speak. Much thanks for the tips!
To early hooray. I choose the option with the revolution zip for a complete install. After the install I selected rebouut system now. Now it stays on the white HTC screen with the text HTC quitely brilliant. Flashing every 3 seconds or so....
What to do now?
Everything is resolved. revolution is up and running again. I had to un the fullwipe.zip and that did it!
THANKS a lot for all the tips....again
Willem Kloppenburg said:
To early hooray. I choose the option with the revolution zip for a complete install. After the install I selected rebouut system now. Now it stays on the white HTC screen with the text HTC quitely brilliant. Flashing every 3 seconds or so....
What to do now?
Click to expand...
Click to collapse
Did you do a full wipe before re-flashing your ROM? even if you did just repeat the process , full wipe /cache, /dalvik-cache, /system and then re-flash the rom fingers crossed it should work
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
mo123456789 said:
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
Click to expand...
Click to collapse
boot into recovery do a full wipe (system, data, cache and dalvik-cache) then re-flash your rom
mo123456789 said:
Hi,
I am having a similar problem. I tried flashing the cyanogen mod and after installing it the phone doesnt boot up. Its stuck on the t-mobile boot up logo. Ive tried restoring my back up but I get the same problem.
Any help would be great!
Thanks
Click to expand...
Click to collapse
Could it be possible that you installed cwm 3005 and tried a restore with that. I had the same problem. Went back to cwm 2.5.x and then restore worked.
Sent from my Desire HD
I think there will be a lot of scare because of this CWM 3x...
Same happened to me the other day, stupidly accecpted the update prompt from Rom Manager, did my backup and went to install Cyanogen 6... Got stuck at HTC logo next boot.
Thankfuly, had Leedroid 2.0 on the SD, too, and that one flashed properly
Thing is that when I try to downgrade the Recovery to 2.5x I get an error and really can't be bothered with ADB pushing stuff around, so using Cyanogen 7 for the time beeing
Anyhow, CWM 3.x is likely your problem, easy to fix ^^
Wanting to change my theme on the Samsung spica I had theexact problem on cyanogen mod. Had to redo the whole rooting and installing the Rom again to get to work.
Sent from my Desire HD using XDA App
yes, is some script...back to recovery 2.x
Need some advice, phone running NexusHD2-ICS-CM9-V2.7, backed up using CWM and tried to flash nexus jellyBean by changing partirion to 400mb, phone would not boot passed cyanogenMod screen, wiped system changed back to 250mb partition and restored system but now phone will not boot passed ICS screen, have tried reflashing ROM but still same problem, any thoughts please.
I believe I should have said that the phone is in ICS animation and that is it, cannot get passed this, have tried everything apart from dropping the phone in a bucket of water. Have cleaned out everything but the restore will not work.
Is there a solution?
IMO you should try a fresh installation of whatever ROM you want: wipe everything(including microSD, but before do a backup) and install it from scratch!
Good luck!
bib*oops said:
IMO you should try a fresh installation of whatever ROM you want: wipe everything(including microSD, but before do a backup) and install it from scratch!
Good luck!
Click to expand...
Click to collapse
does not seem to recognise computer or show charge now, I have made a full backup but even after a full restore with everything loading okay still cannot get past ICS animation screen.
hardav said:
does not seem to recognise computer or show charge now, I have made a full backup but even after a full restore with everything loading okay still cannot get past ICS animation screen.
Click to expand...
Click to collapse
This is getting very frustrating having checked dozens of posts cannot find a logical solution, tried every possible solution I can find. I can get into all features of system,2.08HSPL shows, CWM, MAGLDR, usb screens okay, in short everything okay bar cannot fully load any ROM past animation screen, have tried task 29 but will not load RUU just sits at HTC with bar and the has communication error. Can the the phone be bricked when all functions are available? Any suggestions would be appreciated.
Can you run SD roms past boot anim?
Have you performed a NAND check from MAGLDR? Might be bad NAND blocks.
Well guys after hours of trying to sort this out I have come to the sad conclusion the phone is stuffed which has left me depressed, I have tried:
Restore from my original backup all loads good but does not bootup
task 29 (error 262) does not seem to recognise windows sync
Tried loading from cd using nbh but tri-colour boot loader will not search for file
It is a shame as I can get into all the bootloaders which people tell me should load but no luck
Thanks for your help HD2 goodby
hardav said:
Well guys after hours of trying to sort this out I have come to the sad conclusion the phone is stuffed which has left me depressed, I have tried:
Restore from my original backup all loads good but does not bootup
task 29 (error 262) does not seem to recognise windows sync
Tried loading from cd using nbh but tri-colour boot loader will not search for file
It is a shame as I can get into all the bootloaders which people tell me should load but no luck
Thanks for your help HD2 goodby
Click to expand...
Click to collapse
you're probably using too big an SD card, is it bigger than 8gb?
If so, put the LEOIMG.NBH file on an 8gb or smaller card, and get into tricolor, it should load.
Yes I am using a 16gb card, in the meantime I have managed to restore the phone back to ics nexus v2.7, not sure how I did it but in case anybody has the same problem here goes'
I had to get back to WM 6.5 no matter which ROM I tried could not get the custom RUU to load, (probably due to the sd card size) but I noticed I had a custom RUU sitting on my desktop (not sure why there but probably from past messing about) as a last resort I loaded this and bingo within a short time windows loaded up and from there reflashed ICS and restored from backup, working perfectly what a relief. Goes to show ignorance sometimes wins. Details of the custom RUU used.
LEO CUSTOM RUU
[email protected]
File 1.1.0.0 921KB
This worked with the 16gb card, I would like to go to jelly bean but am I pushing my luck. Can you just reload CWM with a 400 partition?
Have a nice day
Cheers from kiwiland
hardav said:
Need some advice, phone running NexusHD2-ICS-CM9-V2.7, backed up using CWM and tried to flash nexus jellyBean by changing partirion to 400mb, phone would not boot passed cyanogenMod screen, wiped system changed back to 250mb partition and restored system but now phone will not boot passed ICS screen, have tried reflashing ROM but still same problem, any thoughts please.
I believe I should have said that the phone is in ICS animation and that is it, cannot get passed this, have tried everything apart from dropping the phone in a bucket of water. Have cleaned out everything but the restore will not work.
Is there a solution?
Click to expand...
Click to collapse
I had a problem with that one, so i decided to use this one:http://forum.xda-developers.com/showthread.php?t=1584160, and i think that is working much better than Nexus.
So i have the I337m, canadian model S4 on Bell Mobility network, and I"m running SlimRoms with 2.5.0.2 twrp recovery.
Every other reboot, the phone gets stuck on the splash screen, I have no problem to go into recovery mode or anything, this is simply a problem when rebooting and gets stuck on the "Galaxy S4" screen. Here's what I've tried, tried both with TWRP and CWM and TWRP seems better, I don't get stuck on the splash screen as often as CWM. I've reverted back to the "stock ROM" and rerooted and loaded the TWRP recovery, and while it seems better at first, it slowly gets stuck more and more at the splash screen.
I'm running out of ideas, no knowing what do to to improve this problem...
Anyone else having this problem? I'm positive this is not a "ROM" related problem but a recovery problem, yet maybe it's just my phone that's being the problem.
JP
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
jproy12 said:
I'll also add that I've never formated data on TWRP... since I've read it gives that problem.
Click to expand...
Click to collapse
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
jd1639 said:
You have to do a factory reset, wipe data, or you will get a boot loop. Do that and I'm sure you'll get past the boot loop. If you're concerned about the version of twrp you're on, update it.
http://forum.xda-developers.com/showthread.php?p=41010145
Click to expand...
Click to collapse
I'm not getting boot loops actually, I get stuck on the "splash screen" and when I hold the "power" button for +/-10sec it reboots and most of the time it's fine.
When I install any roms, I always do a factory reset... So I doubt it's that
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
h_khan said:
i had the same issue. im running the same s4 on koodo/telus. how i got it to work took a while but it fixed the problem. full back up through recovery but i wasnt gona use it..i only had it for safety. used titanium to back up all the apks. then grabbed a stock rom from the Canadian stock roms page and used odin to flash it. rooted and added recovery (twrp). downloaded my rom to the sd, wiped everything and installed the rom. once done then used titanium to restore the apks. im still learning the basics to all this so in no way am i an expert and theres probably a better way around all this but this is what worked for me. maybe it helps who who knows
Click to expand...
Click to collapse
Yea, I had done this before, but I'm giving it another shot tonight to see if it'll fix my problem for good...
Still having the same problem... Running out of ideas
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
jproy12 said:
Still having the same problem... Running out of ideas
Click to expand...
Click to collapse
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Talabis said:
I was having a similar problem to your's. I found the cause of my issue. It was TWRP 2.6.0.0. More specifically, it was using TWRP 2.6 to format my /data partition. After doing some trouble shooting, I found that my /data partition was the cause of my S4 hanging at the S4 splash screen. Like you, I was able to get into Android on the first boot, but if I tried to reboot, I was get stuck at the splash screen. So, long story short (solution), I restored one of my nandroid backups, got into Google Play, downloaded ROM Manager and installed CWM. I used CWM to format my /data partition and ONLY my /data partition. Once I did this, I rebooted my phone. Android loaded, I had to go through the initial setup process since I formatted the /data partition, but after this, I was able to reboot my phone 5 times in a row without issue and shut down twice with no problems booting back up.
Here is my thread: http://forum.xda-developers.com/showthread.php?p=45448596#post45448596
There's a bit of reading. Hope this helps.
So my issue was caused by TWRP 2.6.0.0 and using it to format my /data partition.
Click to expand...
Click to collapse
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
h_khan said:
i think the rom is the cause of this issue. i myself am running goldeneye rom which is the best rom ive used so far...perfectly balanced performance and battery life. id definitely recommend it.
Click to expand...
Click to collapse
I've been running Slim for a year now, and won't go back to anything else, it's stable and fast, I doubt it's a ROM problem, but a recovery problem.
i think you're right. a problem with the recovery makes more sense.
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "boot screen"?
Click to expand...
Click to collapse
So it seems like this wasn't exactly my problem... I've reverted back to stock and I'm doing a couple shutdowns and reboot and see if I still get stuck at the splash screen.
I've been doing reboots and shutdowns on the "stock" rom and "stock" recovery, and all is good, so I can rule out the fact that it's the phone and it's hardware issues...
Now, just need to figure out the actual problem
jproy12 said:
Thanks, I'll give that a try, but it seems like this is/was my problem, is your problem fixed for good now? No getting stuck on the "booscreen"?
Click to expand...
Click to collapse
So far so good. I rebooted many times since I made the post in this thread. Haven't got stuck on the splash screen yet.
I'm still having the problem, being on either the TWRP, CWM or Philz recovery, so I'm really not sure what it could be. I'm on the latest modem and still have the problem, is none else having these issues?
I'm getting annoyed and really want to get this fixed.
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
emckai said:
I think any ROM built on AOSP or CyanogenMod have this issue. It's already a known issue to CM.
Use CWM and you'll have to deal with it less.
Click to expand...
Click to collapse
I've never seen anyone really mentionning this for the Galaxy S4 from my numerous searches...
jproy12 said:
I've never seen anyone really mentionning this for the Galaxy S4...
Click to expand...
Click to collapse
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
emckai said:
If you look in the cyanogenmod thread, it's located in the known bug (post #2)
Any custom roms built on top of CM10 will probably have this issue.
Click to expand...
Click to collapse
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
jproy12 said:
You are right! I guess it's one of those bugs, just never noticed anyone really mentioning anything about it
Click to expand...
Click to collapse
Yeah, but I don't think its a big deal anyway. How many times do you turn off your phone and turn it back on in a day?