when i opened the camera app, the phone rebooted itself and now it is stuck on the bootanimation logo. This happened to me 3 times allready but it always goes back to normal. Anyone know what to do, i don't wanna factory reset it.
Tried restarting it with the power button, tried removing battery and i tried rebooting through phils CWM recovery and still always goes back to the bootanimation logo.
Plz help
I'm Using omega Rom V7 with the new adam kernel v1.3
Also my camera was fine with the stock kernel, i think the new adam kernel made my camera app worst.
Jason2k13 said:
when i opened the camera app, the phone rebooted itself and now it is stuck on the bootanimation logo. This happened to me 3 times allready but it always goes back to normal. Anyone know what to do, i don't wanna factory reset it.
Tried restarting it with the power button, tried removing battery and i tried rebooting through phils CWM recovery and still always goes back to the bootanimation logo.
Plz help
I'm Using omega Rom V7 with the new adam kernel v1.3
Click to expand...
Click to collapse
It might b problem of omega rom. Just reflash it while wiping data and caches.
Sent from my Disturbed™ Galaxy S4
Disturbed™ said:
It might b problem of omega rom. Just reflash it while wiping data and caches.
Sent from my Disturbed™ Galaxy S4
Click to expand...
Click to collapse
Can i re-flash omega rom, without wiping data? or will that cause trouble?
re: camera issue
Jason2k13 said:
Can i re-flash omega rom, without wiping data? or will that cause trouble?
Click to expand...
Click to collapse
If you don't want to do a full wipe don't even bother flashing it again.
The whole purpose of re-flashing is that you are having a problem with
the camera.
A clean install of Omega rom should clear it up.
But a dirty flash will make no difference at all.
Backup your apps using titanium backup or some other backup app so you don't loose your apps.
Good luck!
Misterjunky said:
If you don't want to do a full wipe don't even bother flashing it again.
The whole purpose of re-flashing is that you are having a problem with
the camera.
A clean install of Omega rom should clear it up.
But a dirty flash will make no difference at all.
Backup your apps using titanium backup or some other backup app so you don't loose your apps.
Good luck!
Click to expand...
Click to collapse
When i first flashed the omega rom, i did do a full wipe, worked fine until the camera app crashed for the 3rd time. I don't mind doing a full wipe, it's just i did some tinkering with my phone and i have to start again if i have to do a full wipe lol
Always do a full wipe when having problems.
I understand it can be time consuming, i have dirty flash many times and still had the same problems.
If the new flash doesnt work search the Rom thread, i read somewhere of a similar issue.
Related
Hey
After I read that the battery life could be improved by factoryreset-ing the sg2, i resetted it in recoverymode.
And now it stuck on the boot Logo, displaying the big animated endless looping
S
Samsung
GALAXY S II
.. and then i tryd to flash a new firmware, litening rom and I thought it would fix the problem, but no, it didnt.
I use the kernel from chainfire with Clockworkmod v3.0.0.5 + the other good stuff.
what can I do ???
edit: I try to restore my backup now
Ok cool.. the restore process works pretty good.
Everything is like it was tonight, when i backed it up.
Ok, now is the question, why does the factory reset does not work here ?
I'm pretty sure they are taking about resetting it from within the phone, ie settings, private, factory reset
Edit: It's working as intended, you wiped your data partition. Needless to say this renders the phone pretty much useless
Sent from my GT-I9100 using XDA Premium App
ok, i made a factory reset within the phone now
lets see..
Again.. same effect.. used the holy wcm to resque me.
maybe its because of the frozen sysapps that i instandly froze with TB after installing litening rom..
need to reinstall it again now.
Damn, i would like to have a real clean startup again.. and try if anything changes with the battery power.
My theory is, that many of us have a different hardware.. like battery type or a different screen or something..
Its like the 5 different firmwares for the mmols camera..
ok, i will now flash litening rom and configure it...
ps: don't forget to back it up yo!
(•.•) said:
Again.. same effect.. used the holy wcm to resque me.
maybe its because of the frozen sysapps that i instandly froze with TB after installing litening rom..
need to reinstall it again now.
Damn, i would like to have a real clean startup again.. and try if anything changes with the battery power.
My theory is, that many of us have a different hardware.. like battery type or a different screen or something..
Its like the 5 different firmwares for the mmols camera..
ok, i will now flash litening rom and configure it...
ps: don't forget to back it up yo!
Click to expand...
Click to collapse
how did u manage to solve it ..? i am facing with the same problem also ...thnaks!
Did you try to flash original kernel and then factory reset?
Had the same problem and downloaded from xda the original ke7 and installed it
problem solved. Then did a rooting again. Hope this helps.
It seems, that wiping the dalvic cache will produce that effect.
Because in the dalvic cache, there are many informations saved how your system is configurated..
For example your google account is also saved there within the google framework and the account and sync settings in the dalvic cache.
But not only there, there are some other places to.
Maybe i will make a tutorial in a while, how to change or delete the google account, because you can't delete or change it the normal way.
i solved this with wip data/cache
Hi guys. Need your help on this one. I flashed the latest omega rom and successfully restored my data. But whenever i reboot or power my phone off it can boot up past the samsung s4 logo. I would have to go back to recovery (twrp) format data. Then restore from back up then it can boot up. I would have to do it every time. I already tried reflashing the omega rom. After wipe but same thing the moment i reboot it will not het past the s4 logo. Any idea on this one. I really need help
mirvashstorm said:
Hi guys. Need your help on this one. I flashed the latest omega rom and successfully restored my data. But whenever i reboot or power my phone off it can boot up past the samsung s4 logo. I would have to go back to recovery (twrp) format data. Then restore from back up then it can boot up. I would have to do it every time. I already tried reflashing the omega rom. After wipe but same thing the moment i reboot it will not het past the s4 logo. Any idea on this one. I really need help
Click to expand...
Click to collapse
U can try two thing first
Go to recovery and wipe cache and dalvik cache and then reboot
Reboot and see if the problem is solved
If not the go to settings and reset the device and reboot this should clear that problem let me know what happens
Sent from my GT-I9500 using xda premium
123hiten said:
U can try two thing first
Go to recovery and wipe cache and dalvik cache and then reboot
Reboot and see if the problem is solved
If not the go to settings and reset the device and reboot this should clear that problem let me know what happens
Sent from my GT-I9500 using xda premium
Click to expand...
Click to collapse
Thanks! Currently trying that. Will let you know right away....
Same thing cant get past Samsung s4 logo...
I will try to go back to stick rom using http://forum.xda-developers.com/showthread.php?t=2265477
Hopefully this works.
I have just finish flashing the official stock rom for my country and the carrier. Went through all the Software update. BOOM! now working.... Im just wondering what happened. but i am so glad i have my s4 up and running again. No more bootloops for me
mirvashstorm said:
I have just finish flashing the official stock rom for my country and the carrier. Went through all the Software update. BOOM! now working.... Im just wondering what happened. but i am so glad i have my s4 up and running again. No more bootloops for me
Click to expand...
Click to collapse
Good to hear that & bootloop happens for some system files clashing Etc
And ya to to be out of the issues i suggest do a full reser from ur device if u have not done that :good:
Hello,
I have flashed Omega rom in my galaxy s4, however sometimes when I restart my device im stuck in the logo boot up. So my solution is to wipe the /data in recovery mode and it will start again.
But i don't want to wipe it every time i boot my device.
What do you think is the problem here? and how can i fix it?
rymngh said:
Hello,
I have flashed Omega rom in my galaxy s4, however sometimes when I restart my device im stuck in the logo boot up. So my solution is to wipe the /data in recovery mode and it will start again.
But i don't want to wipe it every time i boot my device.
What do you think is the problem here? and how can i fix it?
Click to expand...
Click to collapse
Try to wipe system, data, and cache again. Then reinstall the omega rom and see if that solves the problem.
Flowed from my GT-I9505 using xda-developers app
joelvn said:
Try to wipe system, data, and cache again. Then reinstall the omega rom and see if that solves the problem.
Flowed from my GT-I9505 using xda-developers app
Click to expand...
Click to collapse
i've done that 4 times already. and it is still not working..
last week, i flashed a rom and while flashing it the battery fell off because i removed the back cover while flashing it last week. maybe thats the problem why my data is not working properly?
rymngh said:
i've done that 4 times already. and it is still not working..
last week, i flashed a rom and while flashing it the battery fell off because i removed the back cover while flashing it last week. maybe thats the problem why my data is not working properly?
Click to expand...
Click to collapse
That probably isn't the problem. I recommend you to download the stock firmware of your phone and install that using Odin. Then if it works you can root it again, install a recovery and try it all again.
Flowed from my GT-I9505 using xda-developers app
So I used the Auto CF root and all went well. Next, I went back into recovery and installed the TWRP Recovery though odin. It installed fine. After that I noticed I no longer had root and I can't figure out how to get it back. Supersu was still installed, it just wouldn't work.
At this point, i've tried redoing the root process a couple of times and it says that it worked fine, but doesn't do the job. Anyone got any ideas on what to do?
If anyone's curious, I started on totally stock OTA MF9.
Thanks
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
ifly4vamerica said:
Just flash one of the stock rooted mf9 ROMs in the development thread pic one with no data wipe so you don't have to set everything up again.
SGS4 Sent
Click to expand...
Click to collapse
Thanks for the tip. Downloading the odexed version of this. Slow download so almost 2 hrs left.
[ROM][ZIP]Stock Rooted Deodexed/Odexed MF9 with SuperSU/Busybox 1.20.2
Hopefully it works. I tried wiping cache and dlvik cache and now when i turn the phone on it just keeps giving errors that this and that app can't open so the phone is essentially unusable. Didn't think wiping cache would do that.
Yeah sometimes things just go screwy. Have you tried fixing permissions? While you wait for a download you can wipe cache davlik and fix permissions its in the advanced menu of twrp. The odexed with no data wipe should fix you up I would recommend wiping cache davlik and system before you flash it. If it still gives errors you may have to wipe the data also and start fresh. You can also try TWRP version 5.0.2 if you aren't on it there is a flashable in the dev forum also. Some people have reported issues with the newer version. I think you will be fine flashing that stock odexed ROM though.
SGS4 Sent
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
iivisionii said:
Out of curiosity, would there be any danger in installing a custom rom while my phone is in this state? Downloading Blu Kuban Rom and it's going to finish much earlier than the stock rom. I know I would lose all my apps and need to reinstall those.
Click to expand...
Click to collapse
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preload before flashing to avoid issues. All the custom ROMs have root built into them so you should be good to go.
SGS4 Sent
ifly4vamerica said:
Nope no danger at all. In fact I recommend blu Kuban. Its a nice ROM. Just do a full wipe of system data cache davlik and preloaded.
SGS4 Sent
Click to expand...
Click to collapse
Thanks. I'll have an update soon. Either that or a panic attack and a question in roughly 30-45 minutes.
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
daniel4653 said:
Did you try to install super SU from the market. Maybe super user is acting up on you.
Sent from my SPH-L720 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
iivisionii said:
I tried installing supersu from the market. Next I even tried downloading it to my phone and loading the zip in recovery. No go both ways. I hoped wiping cache and delvick cache would help, but instead the phone is pretty much unusable now. It's really weird.
Click to expand...
Click to collapse
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
iivisionii said:
Here goes that frantic post. I installed the rom, worked fine. I did one of the updates for the status bar, now whenever it goes to boot it gets stuck at the samsung galaxy s4 screen. I've tried doing a full wipe, wiping cache and delvick cache and even trying to install the stock rooted rom or the blu rom on top of itself and i still get the same thing. Any ideas? I'm trying not to be too flash happy because I don't want a brick.
Click to expand...
Click to collapse
Have you tried the battery pull trick once frozen?
ObrienDave said:
Have you tried the battery pull trick once frozen?
Click to expand...
Click to collapse
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
iivisionii said:
I finally got out of the boot logo. I looked around the forums and found someone with a similar problem. Seems the recovery wasn't deleting all the files for him so he deleted everything manually instead of just wiping. I did the same and installed triforce rom and it's booted now.
Just for future reference though, would you mind explaining or pointing me to where I can read about the battery pull trick?
Click to expand...
Click to collapse
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
ObrienDave said:
Basically, quite a few people have recommended pulling the battery once frozen.
Even when you do a power off, you are NOT completely removing power from the system.
Disconnecting the power is the only way to accomplish this.
Click to expand...
Click to collapse
Ah ok. Good tip to know. I had tried that and it didn't work. Seems to be working ok now. I'm gonna be careful not to screw it up cuz its already 1 am, hehe. Thanks for everyone's tips.
I got my new Note 3 2 weeks ago and after a week of ownership decided to root it and install a custom rom.
Rooting went fine and then I installed my first custom rom Echoe Rom v.4.1 Full. But the problem I had was that, after installing all my apps, when I went to reboot the phone it just went into a continuous bootloop. So I thought I'd try another rom and installed Omega v4.0 and had the same problem, boot loop after rebooting.
So my question is why? Why are all roms causing me bootloops after I reboot? I'm having to either keep charging the phone and keeping it on 24/7 or if, for some reason it does power off, clearing davik cache and performing a factory reset to enable me to boot the phone up again and go through the whole install process over again.
Can I do anything to stop this or has anyone any idea why it is happening please?
Prozac69 said:
I got my new Note 3 2 weeks ago and after a week of ownership decided to root it and install a custom rom.
Rooting went fine and then I installed my first custom rom Echoe Rom v.4.1 Full. But the problem I had was that, after installing all my apps, when I went to reboot the phone it just went into a continuous bootloop. So I thought I'd try another rom and installed Omega v4.0 and had the same problem, boot loop after rebooting.
So my question is why? Why are all roms causing me bootloops after I reboot? I'm having to either keep charging the phone and keeping it on 24/7 or if, for some reason it does power off, clearing davik cache and performing a factory reset to enable me to boot the phone up again and go through the whole install process over again.
Can I do anything to stop this or has anyone any idea why it is happening please?
Click to expand...
Click to collapse
Check this thread
Dahdoul said:
Check this thread
Click to expand...
Click to collapse
Thanks but I've tried that and am still getting bootloops on all roms I install! I'm now trying [26.11.2013] X-NOTE v5.1 N9005 MJ7 and yet again, after going through the initial setup and installing my apps, I'm getting bootloop when rebooting the phone.
Prozac69 said:
Thanks but I've tried that and am still getting bootloops on all roms I install! I'm now trying [26.11.2013] X-NOTE v5.1 N9005 MJ7 and yet again, after going through the initial setup and installing my apps, I'm getting bootloop when rebooting the phone.
Click to expand...
Click to collapse
Check this ROM it fixes all my issues,Wipe/Factory reset from recovery mod then flash the first PreRooted rom via Odin 3.04 in the thread and make sure you unroot your device.
Dahdoul said:
Check this ROM it fixes all my issues,Wipe/Factory reset from recovery mod then flash the first PreRooted rom via Odin 3.04 in the thread and make sure you unroot your device.
Click to expand...
Click to collapse
Many thanks Dahdoul. I'm downloading the first PreRooted rom from the thread. Hope that's the right one! Do I need to unroot the phone before powering it up and, if so, how do I unroot it?
Prozac69 said:
Many thanks Dahdoul. I'm downloading the first PreRooted rom from the thread. Hope that's the right one! Do I need to unroot the phone before powering it up and, if so, how do I unroot it?
Click to expand...
Click to collapse
two ways to Unroot your device:
Go to superuser app in your phone then settings press on unroot completely option and you are ready to go.
OR
In recovery mod Wipe cache partitions and reset factory settings then flash the stock rom by odin.