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
Related
Mates, the problem is there, we should admit that, had it on Galactus rom twice ( reflashed the rom again after full wipes to make sure ), and had it also on the stock LSZ with its stock kernel, and also on Cassie's rom.
Nothing solves the problem apart from wiping data.
Is it the preload ? the kernel ? defective JB from Samsung ? I really don't know.
The only thing I would really like to mention is that on Cassie's rom, had the issue surprisingly occuring on odd restarts not the even ones ! the first restart gets stuck, the other goes on !
Tried all the tricks in the book (restart to recovery, reinstalling bootloader, overinstalling the same rom, wiping everything keeping data, nothing worked.
Unless data gets wiped, the problem persists.
BTW, I had the same problem on all the previous leaked versions before the official ones.
Back to ICS while discussing here.....
i have no bootloop on the LSZ. been on it for couple of days and many reboots later....no issue.
i flashed the .md5 file from samfirmware link via odin ...let it boot and settle....then flashed philz LM5 4.35 kernel for root...
then i changed my build.prop for lcd density and installed the xposed installer and xposed app settings etc...
no lag and no bootloop.
also uninstalled a couple of the german apps that came with the firmware.
looks good!!
I (luckily) resolved it by
pressing POWER BUTTON for about 5 seconds while on samsung splash screen bootloop...
or
reboot to recovery>>advance>>reboot to recovery(again)>>>reboot system now..
or
making nandroid backup and restoring it
Recognized Distributor™
I have not flashed the latest stock ROM yet, but my understanding after reading various threads is that it seems like the issue is appearing only if you restore data using TITANIUM backup(or any other type of of data restoration).
Is this common for all which faced the issue?
I mean is there any one that wiped everything just installed the ROM and then did not restored anything from a backup and faced the issue?
thanks,
Panagiotis
I think bootlops are caused by the use of /preload partition for some .apk since JB rom like xxls7 that didn't use preload like RRv3 aren't affected by them.
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
zai89 said:
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Exactly, especially the 7 sec power button restart, almost 100% bootloop state.
Sent from my GT-N7000 using Tapatalk 2
pbirdas said:
I have not flashed the latest stock ROM yet, but my understanding after reading various threads is that it seems like the issue is appearing only if you restore data using TITANIUM backup(or any other type of of data restoration).
Is this common for all which faced the issue?
I mean is there any one that wiped everything just installed the ROM and then did not restored anything from a backup and faced the issue?
thanks,
Panagiotis
Click to expand...
Click to collapse
Had the issue on clean roms without any 3rd party app whatsoever, just the rom itself on the device before even restoring contacts through gmail.
Sent from my GT-N7000 using Tapatalk 2
jaguaralani said:
Had the issue on clean roms without any 3rd party app whatsoever, just the rom itself on the device before even restoring contacts through gmail.
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ohh...I see.. This is what is keeping me away of flashing the official ROM.. i will just wait for the issue to be found before i flash it.. Thanks for the info!!
Official JB is quite stable.. on XLSC (ultimate rom) my phone face sudden bootloop while it on my pocket, longest use on XLSC is 2 or 3 days before it bootloop by it self...only can be solve by restoring nandroid backup, something happen when I make force reboot or force shutdown...
But on XLSZ I only got bootloop on 1st reboot (after force reboot & force shutdown)....on 2nd reboot my phone will reboot normally..and never face suddent bootloop.. But yes bootloop bug is still there..
My XLSZ now is on:
+stock kernel
+rooted
+odexed/stock official
+some system apps is on preload partition
+no system/data restored by TB..
Sent from my GT-N7000 using Tapatalk 2
Here it explains why does bootloop happen and how to solve it
https://github.com/jeboo/initramfs_XWLSD/commit/95a98729983e71a3310c04e147994143651fe62c
We need to have the JB kernel sources in order to get rid of the bootloops
Sent from my GT-N7000 using xda premium
zai89 said:
Before reporting that you never have bootloop bug you should do this..
1. Force reboot, press power button about 7 sec...lets see if you phone past the N7000 logo or not..
Or
2. Force shutdown, pull out your battery while phone is ON..
Please make Nandroid backup 1st..
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Ok....so I tried both your methods of getting a boot loop.
1. After holding down power button till it came to the Sammy screen, it stuck there. I held power button down until screen went blank and let go....within a second phone came back on and rebooted normal.
2. Same as what happened in 1.
But this happened before where it would sometime get stuck at Sammy logo..in other versions of android and even inn my i9000 before....but it boot up fine after so no problems here.
Sent from my GT-N7000 using Tapatalk 2
ssss69 said:
Here it explains why does bootloop happen and how to solve it
https://github.com/jeboo/initramfs_XWLSD/commit/95a98729983e71a3310c04e147994143651fe62c
We need to have the JB kernel sources in order to get rid of the bootloops
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Thanks for the info mate, this clearly shows that it is a Samsung problem.
Sent from my GT-N7000 using Tapatalk 2
Now we need someone who is already stuck on the logo to flash Philz LSZ kernel and tell us if it fixes it or not.
Sent from my GT-N7000 using Tapatalk 2
jaguaralani said:
Now we need someone who is already stuck on the logo to flash Philz LSZ kernel and tell us if it fixes it or not.
Click to expand...
Click to collapse
Not fixed mate, already at PhilZ LSZ. Need someone to translate the github commit above to laymen terms. Seems that we need to format /data and then edit the fstab.smdk4210??
Anyway, based on that here is what I do, in CWM rather than wipe data/factory format, I just format /data and then using advance nandroid restore to restore just /data partition. It's not a solution but at least my setup is still there and data is intact. Of course you must do a nandroid backup in the first place! I take this trouble because to me XXLSZ is way snappier and smoother than the previous ROMs.
Edit: After successful reboot to system I went back to recovery and tried to reboot from there. Still stuck at boot logo, however pressing the power button for 7 seconds will clear it. Only tried few times though.
I've never had bootlop with LS7 and LSA and LSZ only few bootlops with lsc but i do wipeing cash and dalvik and works again
Verstuurd van mijn GT-N7000 met Tapatalk
kopitalk said:
Not fixed mate, already at PhilZ LSZ. Need someone to translate the github commit above to laymen terms. Seems that we need to format /data and then edit the fstab.smdk4210??
Anyway, based on that here is what I do, in CWM rather than wipe data/factory format, I just format /data and then using advance nandroid restore to restore just /data partition. It's not a solution but at least my setup is still there and data is intact. Of course you must do a nandroid backup in the first place! I take this trouble because to me XXLSZ is way snappier and smoother than the previous ROMs.
Edit: After successful reboot to system I went back to recovery and tried to reboot from there. Still stuck at boot logo, however pressing the power button for 7 seconds will clear it. Only tried few times though.
Click to expand...
Click to collapse
Thanks for the info mate...
today I'm updating my friend phone from stock ICS DXLR5 to XLSZ (free of chrge) using PC ODIN..while on stock XLSZ kernel I make a force reboot on my friend phone and its stuck on N7000 logo and boot find after second reboot (without any wipe or restore) , same things happen to my phone to...after that flash new Philz XLSZ kernel on my phone & my phone too from stock recovery...and what is surprise me is my friend phone survive when I make a force reboot but my phone not...maybe its time to reflash, will report again..
I have faced this problem many times before and the only cure sometimes was to make a nandroid backup and restore it
but if the backup failed at the data partition that means the data is corrupted and you must wipe your data ...
but one solution for sure worked for me with all roms I've tried ... do not use the preload partition ....
I do not use it at all ... even if i downloaded a rom which uses preload partition I modify the rom to use
only system partition ... with this I've never faced any boot loop with JB again.
Super Prince said:
... even if i downloaded a rom which uses preload partition I modify the rom to use
only system partition ... with this I've never faced any boot loop with JB again.
Click to expand...
Click to collapse
Care to share how to do this?
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:
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.
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.
Hi, I'm desperate today. I've been without my phone since a few days.
In the first place, I wanted to flash another custom ROM. I hadn't change anything to my N4, I was using AOSPAL. You know that F2FS has come, so I wanted to test it. After some fails, some resets, I succeeded to make my phone clean & fast (F2FS & custom kernel). Now I can tell you about my problem.
I noted that, after many tests/flashs, my phone can't boot after turning it off. I stuck at "Google" logo, the ROM apparently disappeared from my phone, or something else went wront. I don't know what.
Then I did a new factory reset, I flashed a ROM/Kernel without any changes to FS, but I got the same problem. If I reboot (reboot from adb, ROM...) my phone, it works. But if I turn it off, I'll stuck at "Google" logo the next boot.
I've actually no ideas, and Google gave me no results...
I'll try to make a new reset, or try another kernel... I don't know where I'm going.
Thanks for help and I wish you to have a nice day.
PS : I'm not a newbie, I already did more than hundreds flashes, some bricks, but I've never seen a similar problem.
Why don't you try flashing the factory image and start over. That should clean everything up
Sent from my Nexus 5
hi
try use nexus tool kit for restore fone bootloop flash rom stock
jd1639 said:
Why don't you try flashing the factory image and start over. That should clean everything up
Sent from my Nexus 5
Click to expand...
Click to collapse
I've already done that each time before flashing any custom mod, since I got that problem.
eltonpestana said:
try use nexus tool kit for restore fone bootloop flash rom stock
Click to expand...
Click to collapse
This isn't the problem... I flashed the factory image many times. It works, but when I turn my N4 off and I want to boot it, I stuck at "Google".. When I reboot from the ROM or adb, there's no problems...
Diaruga said:
I've already done that each time before flashing any custom mod, since I got that problem.
This isn't the problem... I flashed the factory image many times. It works, but when I turn my N4 off and I want to boot it, I stuck at "Google".. When I reboot from the ROM or adb, there's no problems...
Click to expand...
Click to collapse
I assume you've done a factory reset in the stock recovery too? If so I think something is wrong with your phone. Is it still under warranty.
Sent from my Nexus 5
jd1639 said:
I assume you've done a factory reset in the stock recovery too? If so I think something is wrong with your phone. Is it still under warranty.
Sent from my Nexus 5
Click to expand...
Click to collapse
Mhhh when I tried F2F2 and wanted to try something else, I've not done a factory reset in the recovery (did you mean the format partitions in ext4fs or the wipe data/cache/dalvik ?). I used fastboot in order to erase all my partitions, then I flash the factory image archive through fastboot command "-w update".
I don't know whether something is wrong with my phone or not, but I've never seen that problem. It appeared when I did some tests with F2FS. That's all, that's so weird...
Diaruga said:
Mhhh when I tried F2F2 and wanted to try something else, I've not done a factory reset in the recovery (did you mean the format partitions in ext4fs or the wipe data/cache/dalvik ?). I used fastboot in order to erase all my partitions, then I flash the factory image archive through fastboot command "-w update".
I don't know whether something is wrong with my phone or not, but I've never seen that problem. It appeared when I did some tests with F2FS. That's all, that's so weird...
Click to expand...
Click to collapse
I would definitely try to flash the factory image again, then boot into the stock recovery and do a factory reset. F2FS may have borked something. I've never tried it since it does mess with the positions
Sent from my Nexus 5
hi'
I'm not sure if this can work. But it never hurts to try. After flashing stock ROM with CWM. Enter recovery and make full format of all partitions. System and Data partitions and cache and all. After that reinstall the stock rom using nexus tool kit for flashing mode in bootloop. after that flashing custom recovery again and do cleanup, but not the only formates cleanings. I believe you are having trouble reading recognition, partition boot. Uncompensated You must have notice a conflict of partitions on the system format.
eltonpestana said:
Uncompensated You must have notice a conflict of partitions on the system format.
Click to expand...
Click to collapse
I was wondering the same thing...
Thanks guys for your help, I'll flash stock again, and then I'll format correctly the partitions. I hope that's the good way...
Next time its stuck on the Google logo just try plugging in you're charger.
I had the same problem but not down to using F2FS but it did hang on the logo during boot.
After plugging in the charger it booted and hasn't stuck since.
Don't ask my why as I haven't a clue but it worked.
Sent from my Nexus 4 using XDA Premium 4 mobile app
bladebuddy said:
Next time its stuck on the Google logo just try plugging in you're charger.
I had the same problem but not down to using F2FS but it did hang on the logo during boot.
After plugging in the charger it booted and hasn't stuck since.
Don't ask my why as I haven't a clue but it worked.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
FYI this could indicate a problem with your battery
@Diaruga did you ever find a solution?
Sent from my Nexus 5
I plugged my N4, then I tried to flash the factory image again. That was fine. After flashing a custom ROM + custom kernel, still no probems after turning my phone off.
I can't explain why...
Thanks to all, my problem has been solved.
Diaruga said:
I plugged my N4, then I tried to flash the factory image again. That was fine. After flashing a custom ROM + custom kernel, still no probems after turning my phone off.
I can't explain why...
Thanks to all, my problem has been solved.
Click to expand...
Click to collapse
Thanks, glad you got it working again
Sent from my Nexus 5