[Q] Phone Won't Reboot Without Looping. - Galaxy Note 3 Q&A, Help & Troubleshooting

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.

Related

Process System isn't responding

Hi
I'm having issues with my I9505 Galaxy S4. The phone was rooted and after trying a few ROMs (Omega) etc I returned to a NAND backup with was basically rooted stock (via TWRP). Over the weekend strange lock-ups kept happening and I keep getting - Process System isn't responding. When I try and make a call the phone either reboots and hands for a minute and returns that error. This morning I have flashed via ODIN a rooted stock rom then a standard stock ROM - both do not fix the issues, I still have the same errors which is odd.
Can anyone make any suggestions ?
Thanks, Nick
NickBeswick said:
Hi
I'm having issues with my I9505 Galaxy S4. The phone was rooted and after trying a few ROMs (Omega) etc I returned to a NAND backup with was basically rooted stock (via TWRP). Over the weekend strange lock-ups kept happening and I keep getting - Process System isn't responding. When I try and make a call the phone either reboots and hands for a minute and returns that error. This morning I have flashed via ODIN a rooted stock rom then a standard stock ROM - both do not fix the issues, I still have the same errors which is odd.
Can anyone make any suggestions ?
Thanks, Nick
Click to expand...
Click to collapse
bump
NickBeswick said:
bump
Click to expand...
Click to collapse
did you try wiping data and cache??
samersh72 said:
did you try wiping data and cache??
Click to expand...
Click to collapse
Yes many times
NickBeswick said:
Yes many times
Click to expand...
Click to collapse
if you are rooted, flash custom recovery, format system via recovery, then flash a custom rom or stock firmware.
samersh72 said:
if you are rooted, flash custom recovery, format system via recovery, then flash a custom rom or stock firmware.
Click to expand...
Click to collapse
Hi - thanks for the information but again I have already tried this a few times.
Nick
NickBeswick said:
Hi
I'm having issues with my I9505 Galaxy S4. The phone was rooted and after trying a few ROMs (Omega) etc I returned to a NAND backup with was basically rooted stock (via TWRP). Over the weekend strange lock-ups kept happening and I keep getting - Process System isn't responding. When I try and make a call the phone either reboots and hands for a minute and returns that error. This morning I have flashed via ODIN a rooted stock rom then a standard stock ROM - both do not fix the issues, I still have the same errors which is odd.
Can anyone make any suggestions ?
Thanks, Nick
Click to expand...
Click to collapse
Sorry, just saw that you did all these already.
You have to be VERY careful. It is already reported that the wipe in TWRP might screw things up.
So, I recommend you that you install a prerooted stock ROM, and the stock recovery. Then do a factory reset (from the phone!).

[Q] Unable to Reboot

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:

Got rooted, installed custom recovery, lost root, now i'm confused...

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.

Bricked S4?

So I have been trying to get multiple roms to work and it seems as only the TouchWiz roms worked for me (getting LTE) Jellybean wouldn't let me connect to any LTE but gave me data.
So I tried to do a few wipes, I deleted my backups (like an idiot) and now I'm stuck with just being able to get into TWRP.
I get into TWRP factory reset and wipe everything then do a internal wipe and install a rom the rom installs but when i go to reboot the rom it gets stuck at the Samsung Galaxy s4 screen and won't move.
What do I do?
I just want to have a jellybean rom...
I can get into TWRP
How long have you let it boot? The first boot can take a long time.
jd1639 said:
How long have you let it boot? The first boot can take a long time.
Click to expand...
Click to collapse
It was sitting for atleast 7 mins... way too long
and the fist boot was already finished this was the first Reboot after me being on the rom
honeyp0t said:
So I have been trying to get multiple roms to work and it seems as only the TouchWiz roms worked for me (getting LTE) Jellybean wouldn't let me connect to any LTE but gave me data.
So I tried to do a few wipes, I deleted my backups (like an idiot) and now I'm stuck with just being able to get into TWRP.
I get into TWRP factory reset and wipe everything then do a internal wipe and install a rom the rom installs but when i go to reboot the rom it gets stuck at the Samsung Galaxy s4 screen and won't move.
What do I do?
I just want to have a jellybean rom...
I can get into TWRP
Click to expand...
Click to collapse
You need to read about TWRP before using it. You should not be wiping "everything" with it.
honeyp0t said:
It was sitting for atleast 7 mins... way too long
and the fist boot was already finished this was the first Reboot after me being on the rom
Click to expand...
Click to collapse
Can you get into download mode? If so you might want to odin the stock firmware.
jd1639 said:
Can you get into download mode? If so you might want to odin the stock firmware.
Click to expand...
Click to collapse
yeah i can i never used odin before.
if i do this will i be able to re-root? or will it update me to mf3?
EDIT: i just let it sit there and got my old recovery back. im on tw 4.2.2 goldeneye. let me check if i can reboot it without it getting stuck.
EDIT2: ok i just let it reboot and it now reboots fine..
I have read 3 of your posts, you really need to start reading before you go any further...if your phone boots on 4.2.2 GoldenEye, stop there until you find more information on what you are trying to do. If you don't you will for sure be using Odin soon, may want to read up on that also...
Good luck.
BTW, you do not need to make a different thread for every question, go back to one of the threads you started, and ask ALL of your questions there...

S5 Won't turn off, won't boot into recovery

I tried 2 ROMs: Alliance and Extreme Debloat. If I try to turn off the phone it gets stuck at the booting down logo. This happens when I try to restart it, when I try to boot into SafeStrap, or any other way I attempt to power off the phone.
If I pull the battery & boot up, at the SafeStrap splash screen, even when hitting the "Recents" button it does not let me get into SafeStrap.
How do I fix this? What's the cause?
Haloman800 said:
I tried 2 ROMs: Alliance and Extreme Debloat. If I try to turn off the phone it gets stuck at the booting down logo. This happens when I try to restart it, when I try to boot into SafeStrap, or any other way I attempt to power off the phone.
If I pull the battery & boot up, at the SafeStrap splash screen, even when hitting the "Recents" button it does not let me get into SafeStrap.
How do I fix this? What's the cause?
Click to expand...
Click to collapse
Odin back to stock, re-root and try it again. I'm not sure what causes this but it happened to me a few times with my old Note 3 and SafeStrap.
Misterxtc said:
Odin back to stock, re-root and try it again. I'm not sure what causes this but it happened to me a few times with my old Note 3 and SafeStrap.
Click to expand...
Click to collapse
Doing this now. Thanks for the prompt reply.. I've been going insane
How I rooted originally: Installed towelroot successfully, then installed safestrap, booted into recovery, backed up system, created ROM slot #1, and installed a ROM.
Did I do something incorrectly?
edit: p.s. nice avatar
Haloman800 said:
Doing this now. Thanks for the prompt reply.. I've been going insane
How I rooted originally: Installed towelroot successfully, then installed safestrap, booted into recovery, backed up system, created ROM slot #1, and installed a ROM.
Did I do something incorrectly?
Click to expand...
Click to collapse
Not really but I stay away from ROM slots because there is a bug with having to pull the battery on reboot. Re-download the latest SS because the first one had a problem with memory corruption witch sounds like happened to you. If you can get into stock recovery try clearing cache or factory resetting from there. Either way you will have to reset. It's safe to flash to the stock slot as long as you have a good backup.
Edit: Thanks on the avatar, quite a few people like it. Hopefully it helps someone out.
Misterxtc said:
Not really but I stay away from ROM slots because there is a bug with having to pull the battery on reboot. Re-download the latest SS because the first one had a problem with memory corruption witch sounds like happened to you. If you can get into stock recovery try clearing cache or factory resetting from there. Either way you will have to reset. It's safe to flash to the stock slot as long as you have a good backup.
Click to expand...
Click to collapse
So after I ODIN I should:
1. Re-root
2. Re-download & install SS
3. Backup, then wipe everything & install in the main ROM slot
?
Haloman800 said:
So after I ODIN I should:
1. Re-root
2. Re-download & install SS
3. Backup, then wipe everything & install in the main ROM slot
?
Click to expand...
Click to collapse
Yup, run towelroot and update SU from SS.
Worked perfectly. Thanks!!
Haloman800 said:
Worked perfectly. Thanks!!
Click to expand...
Click to collapse
Cool, I'm glad it worked for you.

Categories

Resources