Related
Hi, I just recently rooted my phone and I am having a weird problem every couple of days the phone will reboot and just get stuck in a reboot loop, it wont go past the HTC splash screen I have to pull the battery out to get it to start normal. It seems to happen every 2 days or when I am doing something that I guess uses alot of memory like Netflix. Anyone got any ideas on how to fix it? I tried uninstalling all apps that are for rooted uses but still nothing. Even put the processor back to 1ghz.
Did you read the ARHD Q&A thread? You know, the one where this question should have been posted.
Inspired4g said:
Hi, I just recently rooted my phone and I am having a weird problem every couple of days the phone will reboot and just get stuck in a reboot loop, it wont go past the HTC splash screen I have to pull the battery out to get it to start normal. It seems to happen every 2 days or when I am doing something that I guess uses alot of memory like Netflix. Anyone got any ideas on how to fix it? I tried uninstalling all apps that are for rooted uses but still nothing. Even put the processor back to 1ghz.
Click to expand...
Click to collapse
yes, if your question is concerning a specific ROM please use the respective Q&A thread. Random restarts can be any number of things. Typically they're either due to OC/UV or a bad battery. If you have another battery that you know is good, try it and see if that remedies the situation. Also make sure your kernel is not UV'ed.
What they ^^^^ said
Thread closed
Hello XDA! Even though I love technology, I tend to tread lightly when diving into outside-the-box programming topics. That being said, I recently decided to dip into the rooting pool and I've enjoyed the experience so far. I rooted my S3 (SCH-I535) and added the MOAR rom on July 4th, and everything ran smooth for the first week. Recently, I'm running into an issue where the phone freezes on the lock screen and then goes into a soft reset. It's happened a couple times a day for the last three days or so but once it boots back up it seems to work okay for a while. I've also noticed that the phone turns the screen back on when I hit the power button, repeats about three times before stopping. Is this problem related to the root and rom process at all? I've had the lock screen problem briefly when I had my Droid 2 Global, not sure what happened to fix that (if it fixed at all...). I would ask the MOAR rom forum, but I'm a noob (not sure if it's rom related either). Any help would be appreciated!
p.s. will be loading the new version of MOAR later tonight, maybe that will help?
Disable Ripple Effect
CasualCore said:
Hello XDA! Even though I love technology, I tend to tread lightly when diving into outside-the-box programming topics. That being said, I recently decided to dip into the rooting pool and I've enjoyed the experience so far. I rooted my S3 (SCH-I535) and added the MOAR rom on July 4th, and everything ran smooth for the first week. Recently, I'm running into an issue where the phone freezes on the lock screen and then goes into a soft reset. It's happened a couple times a day for the last three days or so but once it boots back up it seems to work okay for a while. I've also noticed that the phone turns the screen back on when I hit the power button, repeats about three times before stopping. Is this problem related to the root and rom process at all? I've had the lock screen problem briefly when I had my Droid 2 Global, not sure what happened to fix that (if it fixed at all...). I would ask the MOAR rom forum, but I'm a noob (not sure if it's rom related either). Any help would be appreciated!
p.s. will be loading the new version of MOAR later tonight, maybe that will help?
Click to expand...
Click to collapse
Try disabling the ripple effect in your lockscreen settings. That is a known issue with any lockscreen other than the stock one.
Seriously a new version of MOAR? Dang it seems like every time I downloaded the new version they're putting up a new one. Which isn't a bad thing but still. Did they say this on the thread?
CasualCore said:
Hello XDA! Even though I love technology, I tend to tread lightly when diving into outside-the-box programming topics. That being said, I recently decided to dip into the rooting pool and I've enjoyed the experience so far. I rooted my S3 (SCH-I535) and added the MOAR rom on July 4th, and everything ran smooth for the first week. Recently, I'm running into an issue where the phone freezes on the lock screen and then goes into a soft reset. It's happened a couple times a day for the last three days or so but once it boots back up it seems to work okay for a while. I've also noticed that the phone turns the screen back on when I hit the power button, repeats about three times before stopping. Is this problem related to the root and rom process at all? I've had the lock screen problem briefly when I had my Droid 2 Global, not sure what happened to fix that (if it fixed at all...). I would ask the MOAR rom forum, but I'm a noob (not sure if it's rom related either). Any help would be appreciated!
p.s. will be loading the new version of MOAR later tonight, maybe that will help?
Click to expand...
Click to collapse
What kernel are you using?
airmaxx23 said:
What kernel are you using?
Click to expand...
Click to collapse
Where can I find the kernel information?
So with a couple tests, I found that the phone tends to soft reset twice if I enter the wrong swipe password, not sure why it has to freak out like that but it's annoying. That's the only time it's been resetting now. The other issue, screen turning back on after I turn it off with the power button, is still persisting but isn't happening in any discernable pattern.
Okay so I found the kernel information, it says
"3.0.31-1152558
[email protected] #1"
People in the MOAR forum (Verizon S3) have had problems on the reboots with the Blackberry lockscreen, but I'm on Rotary so that doesn't help.
I have no idea what happened to my phone. I was running the new Adrenaline rom for a week or so and it was working perfectly, but a few days ago my phone lost service and kept restarting over and over again. I tried to flash a new rom, but it still did the same thing. I even did the newest RUU and it worked perfectly, but my phone still is not able to recognize my sim card and also restarts randomly. It will stop restarting for a while, but then it will do it repeatedly until I shut it down. I have no idea how to fix it, so if you could help I would really appreciate it!! If I left out anything you would need to know, let me know!
Thanks!!
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
dorlow said:
I can't figure out what I'm doing wrong. The last time, how I loaded it was I installed the factory rom. Then I rooted it. (I paid one click root to do it the right way.) I then found a debloated rom and reimaged it without the bloat. After that, it was debloated but unrooted. So, I rooted it the same way one click root rooted it. (I recorded the screen as they did it the first time.)
Everything was working great. The phone worked wonderful for weeks. All the sudden this morning, my google play started crashing over and over. I wasn't sure why, so I rebooted the phone. It was stuck on the AT&T logo for 15+ minutes and the phone was heating up and appearing to be dead. So, I then forced rebooted it a few times with no luck. So, then I rebooted it into recovery and factory reset it.
The one thing I'm confused about that part is I did recover it this morning using the factory recovery. It seems like that would've put the directv app back on and exactly as if it was factory. But it didn't.
But none the less, it's back working. It's still running the debloated rom but unrooted. Not sure if I feel like re-rooting it. But, does anyone have any theories why a phone would be working just fine for weeks on end, then randomly one morning google play starts crashing non-stop. reboot the phone and it's dead? I swear I didn't do anything else. I'm really trying to refrain from messing with it. I just wanted it debloated so the battery life could be better. (The battery life is pathetic.) Today the battery life wasn't too bad. But, I'll pretty much guarantee that within the next few weeks, something will go haywire out of the blue.
Click to expand...
Click to collapse
It is the fault of the rom you installed. Since it is de-bloated, then the developer of that rom might have accidentally removed an important app or service which is the cause of all of your problems. It can be fixed it by installing the stock rom via odin, rooting the phone and installing a different rom.
You paid to root your phone?
This particular crash was the first time it happened on this pre-debloated rom. The previous ones have all been on the stock rom.
ok, last night my phone required an att update. It attempted to update and rebooted. Stuck in a boot loop. Couldn't get out of it. Would just sit at the AT&T logo indefinitely. This was with the stock ROM rooted. So, I had to reload stock room unrooted again. Does anyone else have this problem with the rooted stock rom? Basically it runs for a few weeks. Then AT&T attempts to update and crashes the OS.
You can't OTA update a rooted phone
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
dorlow said:
So what does everyone do about this? My phone pops up the update now or later message 3-4 times a day. I can't block the Ota update. If I ignore it, it prompts constantly.
Click to expand...
Click to collapse
Freeze the updater service / process / app, clear the cache to remove the downloaded update
Can u explain further how to freeze the updater service?
Ok, I looked up how to freeze the updater service and did that. I re-unrooted the phone, rooted it, then froze the updater service. My phone never updated. This morning an app was crashing. Rebooted it and same thing. Stuck on the at&t logo and won't boot. I'm having to re-default it again. The phone never updated from AT&T. But something crashed it last night. No clue. Problem is when this happens, the phone never boots back up so I can't look at it to find out why it happened.
Hi everyone!
I have a international version of the s7 that I bought in France.
Since 1 week, my phones crash randomly and also every time I try to update or download an app on the store. It happens with two different roms (superman and galaxy project).
But not happy to only crashing, it also bootloop after it, sometimes during 20 minutes before booting correctly. And it makes the phone's temperature going up a lot. With all the issues with the note 7 heating and blowing, I fear for my s7.
Also, I can't just return it, because I'm not in France anymore, and it costs a lot to pay the taxes if I want to send it for a check (especially if they do nothing on it)
I was wondering if the cpu clocks on the roms has something to do with it.
If you have any suggestions, I'll wait for it.
Thanks
Sacher_Masoch said:
Hi everyone!
I have a international version of the s7 that I bought in France.
Since 1 week, my phones crash randomly and also every time I try to update or download an app on the store. It happens with two different roms (superman and galaxy project).
But not happy to only crashing, it also bootloop after it, sometimes during 20 minutes before booting correctly. And it makes the phone's temperature going up a lot. With all the issues with the note 7 heating and blowing, I fear for my s7.
Also, I can't just return it, because I'm not in France anymore, and it costs a lot to pay the taxes if I want to send it for a check (especially if they do nothing on it)
I was wondering if the cpu clocks on the roms has something to do with it.
If you have any suggestions, I'll wait for it.
Thanks
Click to expand...
Click to collapse
Hi
Do a factory reset , do not restore anything see if it works ok , if so then it maybe an app causing the problem
or you could flash a stock rom to test the phone and make sure there is no hardware issues
Thank you for your answer.
I'll take a try this weekend with a stock rom as I have the issue with 2 custom roms so far.
If anybody has other ideas until that, please let me know
Little feedback. I flashed the stock Samsung rom two days ago and it seems to work fine for now. But it was also quite fine with the custom rom at the beginning, so I will do another feedback after one or two weeks.
Well... The phone froze and rebooted 5 times in 10 minutes after trying to update some apps itself...
I had the same problem. At the end I was not able to boot Android. I had to claim my cell phone to seller. After one month it was repaired. The final verdict was SOFTWARE problem. They said that EFS was corrupted. One of Samsung firmware has bug which cause problem with EFS.
I also had that problem. I also had to send my phone to the repair center. In my case they replaced the mainboard.
I bought one early september and after two weeks it started doing just that. I tried everything, then sent it to the seller (ebay seller...) and the repair shop couldn't anything about it. I only got my money back yesterday. Back when I invesitgated the issue, nobody was talking about it. So since I liked the phone, I bought a new one from another place (less shady) yesterday... I now think I shouldn't have. Anybody knows more about this ?
Edit: I'm thinking that if I root the phone and backup the EFS and all sensitive partitions before starting using it (or even getting updates) I should be safe...
Yeah, that would be great, but your KNOX will be 0x1. So you will have problem to return this phone back with status 0x1.
Odoslané z SM-G930F pomocou Tapatalku
Hello everybody,
Sorry for the very late reply. I actually sent my phone to another shop here in Japan. But this week, they send me a mail to say that they were not able to fix the issue. But still they taker me 50$ for the time...
I was thinking about buying a new one, but now that some of you are talking about an EFS issue, I'll try to fix again. I will look for some tutorial for that, but if you know how to procede, just reply here
Merry Christmas guys !
hello, i've been having a similar issue.
My phone would be fine for 2 weeks, maybe a month then Suddenly it would reboot to no end, it even reboots from TWRP.
It doesn't reboot while in Download mode. Then what i do to fix it is flash a stock rom from ODIN, sometimes the first couple or 5 times it will reboot during initial first boot up of this stock Rom. I would leave it alone for a while like half day then try it again in the evening or the next day.
Today for example, it started boot looping late last night and I installed Stock ROM with PIT FILE and Nand ERASE and Repartition ticked, boot loop, again, boot loop, tried it again, also rebooted before it started up to stock recovery and factory reset. Then it started up fine and has not rebooted so far.
But this has happened many times and it'll happen after 2 weeks or 1 month. When it does, i first go and delete cache and delvic cache to see if that would fix it, but it doesn't.
Right now it works, but for how long i don't know, when it works, everything is fine with the phone, no imei or calling or heating issues.
I can't guess whats wrong, is it really EFS that got corrupted but not fully but eventually its finding a problem and causing boot loops or something if that makes sense??