Related
idk why.. sometimes ill be on google maps getting directions and navigation my phone will reboot and boot loop over and over.. i have to take out my battery and like wait 3 minutes.. then theres a 65% chance it wont reboot again.. idk why..
Are you over clocking? flash a different kernel...rom?
Myns warm 2.2
netarchy-toastmod-4.2.1-cfs-bfq-havs-more-smartass-universal-signed
but this never used to happen before.. only started after i flashed a new splash screen..
Awkward...and you did correctly, all the right values, ect?
yea everything works perfect except random gps boots..
i wish i could record it an dput it on here..
ever since i did the splash screen the gps part has been out of wack reboot.. but ONLY if i open the maps and start playing with them.. about 10 minutes into navigation itll do it..
or if my phone gets to over loaded itll reboot and boot loop
Have you tried re-flashing the rom with a clean wipe? Backed up your apps and home screen settings, and when you restore, don't restore system settings, only apps and data.
yea.. i even flashed a whole new rom.. MIUI but kept getting random reboots with that rom.. so im guessing it was the splash screen change..
It might be. I would say try changing it, and see what happens. And I know with MIUI, if you don't change your wifi sleep policy it will give you reboots...
anyway you know of that i can get the stock splash screen again?
and what do you mean the wifi sleep??
Its attached. And by the sleep policy, I believe it is how your wifi turns off or refreshes [that line] ; I've never used it, so I couldn't tell you where the setitng is exactly.
well i really appreciate it.. i hope this stops the reboots ima flash it and play with the gps and try to over work my phone.. ill reply if anything..
Alrighty,I'll be floating around.
its not the original stock splash.. its the droid incredible splash is what you gave me..
i need the original stock one..
Woopsies...gimme a minute; My bad.
http://forum.xda-developers.com/showthread.php?t=727574&highlight=stock+splash+screen
In the first post, download the zip. The original is located in there, and you can delete the others, and then flash it.
cool thanks man i appreciate it..
Anytime man.
Hey did you ever get the reboot prob fixed? I am having the same issues.
Flash a new kerrnal or do a full wipe
rconnjr said:
Hey did you ever get the reboot prob fixed? I am having the same issues.
Click to expand...
Click to collapse
What's your exact problem?
Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled
Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled
devnulled said:
Sorry for putting this here, but do not have enough posts to reply to the official thread over in development forum.
I did a clean install of TOB after rerooting, getting S-off and downgrading to froyo then upgrading it back to gingerbread while retaining S-off. Seems I had to get S-off for custom roms to work correctly when verizon sent me a new phone due to the 2am loop boot happening every night for a week even doing a full wipe/factory reset.(they know it is a known issue and sent me a new phone as mine wouldnt stop looping. I installed the last RUU available to take it back to stock and it still did it.
Walked in the bedroom this morning and the softkeys lights were on, figured I had gotten a notification or update or something. Watched it for a few, when it went to the TOB boot animation. would get loaded to home screen, then the loading animation would start again, happened continuously over a 30 minute time frame before I finally pulled the battery to get it to stop. tried to use the phone as it loaded and it started to do it again. Going to attempt to get into recovery and fix permissions, format data/cache, and see if that fixes it.
Anyone else having that problem?
Also are there any mods like the older stock+ that wont show the darned nag screen about there being an update available?
Thank you in advance for any advice/help.
devnulled
Click to expand...
Click to collapse
The 2am reboots are not a phone issue, it is a known issue with the latest ota. I cant believe they would rather give you a new phone than to admit they sent out a messed up ota.
Try fixing permissions and wiping data as you said.
If 2.2 is installed you should not get a nag to update, as its based on the latest ota.
devnulled said:
Also wanted to ask if the verizaon backup assistant is/can be fixed? it FC's whenever I try to load it. When I try to sync contacts on the VZW website I get a few texts with junk characters but no more contacts. Already did a fix permissions in CWM recovery, and through CWM itself. Thanks again for your help. Will update if anything Ive done fixes the problems.
Devnulled
Click to expand...
Click to collapse
Vzw backup was removed from the rom as most people dont use it. If you want it back, flash this http://dinc.does-it.net/APKs/VZW_Backup.zip, thru recovery.
Thank you cmlusco,
clearing cache and fixing permissions has fixed it, sorry for saying there was a problem. Verizon almost got back 3 phones (an eris that i was given, my old palm pre plus, and my incredible) at the same time with a certified letter having me cancel my contract 6 months early when the phone started rebooting back around the 4th of july. They replaced it last summer/fall when they rolled out gingerbread and my phone got half of it installed when it locked up and would not finish the update but was enough there to lock it from being fixed by ruu even.
I agree that it was not the phone, I told tech support I had it rooted for different skins and roms and to fix buggy software and they suddenly wanted to send out a new phone under warranty. I think they just wanted to get out a phone that was a little harder to root and get s-off rather than fix what was obviously a software bug issue. the new phone was supposed to be fully updated, but it wasnt installed, was still on the prior OTA and had a helluva time getting it to accept a custom recovery to begin with. Would goto the white HTC screen, then flash once or twice and go black with white bars down each side. took 3x to get it to accept it and ended up having to flash an older version first .92 i think (was 3 weeks ago now).
I will flash the backup software this time as my contacts were all edited on the website. Thank you again for the best rom Ive played with in a long time.
(forgot to add when I asked about the mods, I meant in a stock rooted rom that was similar to the old stock+ in use/appearance, but didnt get a nag screen, not that touch of blue did not have it. sorry for the confusion)
devnulled
Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?
dibmem said:
Apologies for resurrecting an old thread, but I'm experiencing this issue too.
Getting overnight boot loops on Touch Of Blue 2.2.
I can temporarily fix it by booting to recovery, then wiping cache and dalvik cache.
Unfortunately, this is a daily ritual since updating from Stock+
I wiped our phones per rom install instructions ("Wipe dalvik-cache and format everything in the mounts and storage menu except emmc and sdcard before flashing."), so I'm not sure what's going on.
Seems to correlate with any 'pushed' updates from the Google Play store, but that's just my personal observation...
Any new developments (or permanent resolutions) on this issue since it was reported before?
Click to expand...
Click to collapse
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.
cmlusco said:
No i looked into it, but couldnt figure out what was causing it. Tob is my daily driver and for some reason i have never gotten these reboots. It must have to do with a stock app that i have removed or something. Mabey gmail, i always remove that as i use maildroid. Wish i could be more help, i will install fresh and not remove anythimg and see if i get the reboots. Then it will be easier for me to trouble shoot.
Click to expand...
Click to collapse
Thanks for the reply... I wonder what's doing the damage - The dedicated Gmail isn't on my phone. My wife is running TOB as well with the same symptoms. She runs a lot more apps than I do and we were looking for the ext4 fix when I found TOB.
Maybe it's another app? Let me know if you want a list...
Planning to load your rooted stock this weekend and see how things go.
If, in the meantime, you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.
dibmem said:
Thanks for the reply! I saw your rooted stock build - Most likely will go with that.
I wonder what's doing the damage - I could pull Gmail off for the evening and see if mine is stable. My wife is running TOB as well with the same symptoms. We were looking for the ext4 fix when I found TOB.
If pulling Gmail doesn't work - I'll load your rooted stock and see how things go.
If you need a guinea pig for any possible fixes, let me know - I don't mind installing stuff via recovery. I'm a little rusty on adb, but I could do that as well.
Click to expand...
Click to collapse
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.
cmlusco said:
You can just flash back to tob 1.3. Same thing just not based on 4.08.605.15. Still has all the same features and look.
Click to expand...
Click to collapse
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?
dibmem said:
Can I flash that build directly over 2.2 or do I need to do a full wipe beforehand?
Click to expand...
Click to collapse
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
cmlusco said:
Just wipe dalvik-cache and the cache partition and flash over. I have done it before and had no issues. That being said, if stuff starts acting goofy you may need to wipe and flash from scratch.
Click to expand...
Click to collapse
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)
dibmem said:
Loaded 1.3 per your instructions. Also flashed the stop OTA and stock unlock patches. All is well this morning. No symptoms of a reboot present.
Observations: I noticed when I updated my phone, upon reboot, it wanted to immediately update various software in Google Play.
Perhaps the whole lockup / reboot issue is directly related to how the market pulls down updates(?)... On 2.2, I was doing a morning ritual: I would install market app updates, boot to recovery and do the following: Wipe cache, then dalvik cache. (Last couple of days, I ran 'fix permissions' as well). The process, albeit slightly tedious, worked with varying success - yesterday, it took a few TOB boot screen boots before the phones were stable (wife and mine).
Today, all seems to be fine. After installing 1.3, I did all my updates last night - nothing new pulled down in the market for me.
My wife's phone had one pending update that I left to see if the phone was stable overnight - Still there this morning. So, no 2 am reboot.
Hope this helps with development in some way.
Thanks much for your help and input - I'll keep an eye out for a future build of TOB for problem child phones.
---------- Post added at 05:03 AM ---------- Previous post was at 04:48 AM ----------
Any pointers on upgrading the radio? Currently on 2.15.00.07.28
(Not in a rush - I see there's a few warnings on bricking your phone - unfounded or true?)
Click to expand...
Click to collapse
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.
cmlusco said:
If your s-off you can flash just the radio thru hboot. If s-on you would have to do a whole ruu in order to upgrade it. A bad radio flash can brick a phone. That being said, i have done it many many times with no issues. Just make sure to verrify the md5 sum, and never interrupt or run out of juice while flashing.
Click to expand...
Click to collapse
Results post: Ended up flashing TOB 1.3, radio 2.15.10.12.20, and CMW 5.0.2.0. Updating the radio via hboot ended up being very easy (as long as I verified md5 beforehand.) Our phones are stable overnight - no reboots. Signal sucks here at home, but seems to be slightly better - hopefully will be better around town. If not, there's plenty of other radio versions to try out.
Does anyone think the 2am bootloop has something to do with v6 supercharger. My phone wasn't looping until after i ran v6. I ran touch of blue rom for a week or more with no looping, last evening i ran v6 and then lastnight was woke up at 2am with the phone looping.
dandl9 said:
Does anyone think the 2am bootloop has something to do with v6 supercharger. My phone wasn't looping until after i ran v6. I ran touch of blue rom for a week or more with no looping, last evening i ran v6 and then lastnight was woke up at 2am with the phone looping.
Click to expand...
Click to collapse
I don't. People have reported this issue happens on pure stock.
tiny4579 said:
I don't. People have reported this issue happens on pure stock.
Click to expand...
Click to collapse
The only other things i did yesterday was to install titanium backup and update the script manager app to the latest version.
I use V6 and have for a while now, and have no issues, and have never gotten the 2am boot loop. With the latest ota a new script erase_dirty_fat was introduced. It cleans up the emmc and sdcard, and is then ment to reboot. However for some reason random people get the issue where it dosent reboot correctly but instead boot loops. You say at first it worked great with no bootloops, did you happen to install the Gmail app around the time you started getting the bootloops? Or mabey some other common app you remember installing around that time? I believe it is app related as some get it and some dont. Gmail comes to mind as it is a stock app that i have removed from my TOB setup, and i have never had the boot loops. My phone does unmount the sd and emmc at 2am and then a few minutes later reboots without issue as it is ment to. I wish i could figure it out, it turns a lot of people away from my rom.
cmlusco said:
I use V6 and have for a while now, and have no issues, and have never gotten the 2am boot loop. With the latest ota a new script erase_dirty_fat was introduced. It cleans up the emmc and sdcard, and is then ment to reboot. However for some reason random people get the issue where it dosent reboot correctly but instead boot loops. You say at first it worked great with no bootloops, did you happen to install the Gmail app around the time you started getting the bootloops? Or mabey some other common app you remember installing around that time? I believe it is app related as some get it and some dont. Gmail comes to mind as it is a stock app that i have removed from my TOB setup, and i have never had the boot loops. My phone does unmount the sd and emmc at 2am and then a few minutes later reboots without issue as it is ment to. I wish i could figure it out, it turns a lot of people away from my rom.
Click to expand...
Click to collapse
Mine had something to do with v6. when is started looping i couldn't get it to stop, tried wiping cache and dalvik. battery pull etc all this while being quite tired at 3am. Finally just went to v6 in script manager and clicked the kill button. It stopped rebooting and made it past 2am last night error free.
I have read other post but i forget. It seems caused by some folder searching while booting and system check at 2am.but my fault to remember what folder and what post. Sorry
Sent from my ADR6300 using xda app-developers app
OK guys, long read but I really need some advice. Device is op3 running 3.2.8, magisk, phh superuser and exposed. Issue started while I was reading in news app, screen froze the the phone reboots. 1st time this has happened since I got the phone in June. Didn't think much if it. So I go back to reading in same app and after 5 min it happens again. Now I'm suspecting an issue. So I try one more time with same result. I figure an app update or something must be the problem so I reboot to TWRP(latest official version) and restore my last backup from the previous day. I boot up the phone and decide to just try some browsing. About 5 mins in, it freezes again, but doesn't reboot. I have to hold power to get it to reboot. So now I boot into twrp and decide to try a clean flash, I go to factory reset and I got error message can't mount system or cache. This worries me so I try rebooting to recovery to try again and it will not boot into recovery or system now all I get is fastboot. I have to work the next day so I just put device away and go to bed. The next morning I check the phone and it boots into system no problem. About halfway through work the phone starts all over again with same issue freezing and rebooting until only fastboot works. So I try unbrick tool, everything says OK I boot up and immediately freezes and after a couple boots I can again only get to fastboot. So I start RMA and send device off, when I get it back, the paper says they reloaded the OS. I think well its probably not fixed but I'll try it. I go through process of setting everything up as it was before and it worked fine. Until the fourth day, I'm installing an app and it freezes and reboots. Then exact same story as before, the longer I mess with it the less functional it gets, if I let it sit overnight it will work a while the next day. I have tried all the different twrp versions as well as stock recovery, I have tried other ROMs also, everything ends with same result. So I resubmitted the RMA and now I am waiting to get it back again, but I'm afraid all they are doing is reinstalling the OS again. So anyone experience anything like this before or have any suggestions/ideas what is happening. Thanks for reading and for any help provided.
budbay said:
OK guys, long read but I really need some advice. Device is op3 running 3.2.8, magisk, phh superuser and exposed. Issue started while I was reading in news app, screen froze the the phone reboots. 1st time this has happened since I got the phone in June. Didn't think much if it. So I go back to reading in same app and after 5 min it happens again. Now I'm suspecting an issue. So I try one more time with same result. I figure an app update or something must be the problem so I reboot to TWRP(latest official version) and restore my last backup from the previous day. I boot up the phone and decide to just try some browsing. About 5 mins in, it freezes again, but doesn't reboot. I have to hold power to get it to reboot. So now I boot into twrp and decide to try a clean flash, I go to factory reset and I got error message can't mount system or cache. This worries me so I try rebooting to recovery to try again and it will not boot into recovery or system now all I get is fastboot. I have to work the next day so I just put device away and go to bed. The next morning I check the phone and it boots into system no problem. About halfway through work the phone starts all over again with same issue freezing and rebooting until only fastboot works. So I try unbrick tool, everything says OK I boot up and immediately freezes and after a couple boots I can again only get to fastboot. So I start RMA and send device off, when I get it back, the paper says they reloaded the OS. I think well its probably not fixed but I'll try it. I go through process of setting everything up as it was before and it worked fine. Until the fourth day, I'm installing an app and it freezes and reboots. Then exact same story as before, the longer I mess with it the less functional it gets, if I let it sit overnight it will work a while the next day. I have tried all the different twrp versions as well as stock recovery, I have tried other ROMs also, everything ends with same result. So I resubmitted the RMA and now I am waiting to get it back again, but I'm afraid all they are doing is reinstalling the OS again. So anyone experience anything like this before or have any suggestions/ideas what is happening. Thanks for reading and for any help provided.
Click to expand...
Click to collapse
"I'm installing an app and it freezes and reboots"... What app were you installing, specifically?
I put my trust in XDA devs more than OnePlus devs, so... I suggest you flash FreedomOS. It's based on OxygenOS, but... tinkered by a very cool French guy . Oh, flash ElementalX kernel, too. Always better than stock. You never know
Formhault said:
"I'm installing an app and it freezes and reboots"... What app were you installing, specifically?
I put my trust in XDA devs more than OnePlus devs, so... I suggest you flash FreedomOS. It's based on OxygenOS, but... tinkered by a very cool French guy . Oh, flash ElementalX kernel, too. Always better than stock. You never know
Click to expand...
Click to collapse
Thanks for the reply! The last time that it froze, i was installing firefox from playstore. One of the ROMs I tried was freedom with elemental. It seems no matter what ROM I would flash, device would only work so long before freezing up, the main thing that seemed to matter was how long I waited before booting again, the longer I waited the longer I could use it before freezing up again.
budbay said:
Thanks for the reply! The last time that it froze, i was installing firefox from playstore. One of the ROMs I tried was freedom with elemental. It seems no matter what ROM I would flash, device would only work so long before freezing up, the main thing that seemed to matter was how long I waited before booting again, the longer I waited the longer I could use it before freezing up again.
Click to expand...
Click to collapse
Interesting...
Okay, this may sound weird, but try using the phone without the SIM card in it for a while, see if it freezes up. Or, get the SIM card replaced (if you can). Back when I had the HTC EVO 3D, the phone would lock up at times. Wasn't ROM related, as I experimented heavily with it and... eventually, it turned out to be the SIM card's fault. The guy at the store said he experienced that several times with other customers, but it's an extremely rare occurance. Some bad pin or God knows what. That was 4 years ago (actually, 5. Jesus! ).
Sounds hard to believe, I know. But you never know
Still, I believe there may be something wrong with your device's hardware. Try RMA'ing it again - if you dare going through the process again and risk having to deal with OnePlus' extremely lacking customer service several times a day, like I did .
PS: I see you're new here. You should know that there's a "thanks" button next to each post, which you can press so you don't post a single "Thanks!" every time. For the future, you know.
Formhault said:
Interesting...
Okay, this may sound weird, but try using the phone without the SIM card in it for a while, see if it freezes up. Or, get the SIM card replaced (if you can). Back when I had the HTC EVO 3D, the phone would lock up at times. Wasn't ROM related, as I experimented heavily with it and... eventually, it turned out to be the SIM card's fault. The guy at the store said he experienced that several times with other customers, but it's an extremely rare occurance. Some bad pin or God knows what. That was 4 years ago (actually, 5. Jesus! ).
Sounds hard to believe, I know. But you never know
Still, I believe there may be something wrong with your device's hardware. Try RMA'ing it again - if you dare going through the process again and risk having to deal with OnePlus' extremely lacking customer service several times a day, like I did .
PS: I see you're new here. You should know that there's a "thanks" button next to each post, which you can press so you don't post a single "Thanks!" every time. For the future, you know.
Click to expand...
Click to collapse
Good to know, I actually considered the sim. I've been using it since my HTC onex. Might try that when I get device back, however it is working in my opo as we speak. You mentioned you've going through rma before. Any advice on how to get them to take a different action other than continuing to reload the os?
budbay said:
Good to know, I actually considered the sim. I've been using it since my HTC onex. Might try that when I get device back, however it is working in my opo as we speak. You mentioned you've going through rma before. Any advice on how to get them to take a different action other than continuing to reload the os?
Click to expand...
Click to collapse
No idea, honestly. The RMA I did was for a replacement, since it was within 14 days of purchase, so I got to choose to get a replacement. Should have chosen the refund, wait another month and get the 3T... had I known it was going to be released. Oh well.
In your case... I guess you can do another RMA and hope for a better intervention. Perhaps explain to them... more thoroughly? Or just go with the flow - they'll reload the OS, you'll report the same issue again... Maybe they replace it, I don't know.
Interesting that they did the OS reloading IN SERVICE. Usually, this procedure is done via remote control... So they don't have to pay for shipping when such a thing can be done via a remote session, you know... Weird.
Hello,
Got an S9 wich has been smoothly running SoLdierR ROM for a couple of weeks. Until two days ago, when my phone decided otherwise. If I restart the phone, the freezing stops for a bit and isn´t noticeable until I start opening apps and that´s when it starts getting really annoying. After that the freezing starts occuring in intervals every 10sec for 3-4 sec. This is making me miss messages/voice calls if these occur during freezing intervals. If I remembers correctly, this started right after I cleared phone memory a couple of days ago. Is there any way to resolve this without me having to backup data and restoring phone?
What I've tried doing so far:
Restarts, shutting down phone for longer periods of time, booting in safe mode (still freezing), booting in recovery mode and deleteing cache/dalvik, deleting apps recently installed, inactivating google apps (google, google play, google services) and deleting cache then unstalling update and then reactivating them, removed root.
yarmannen said:
Hello,
Got an S9 wich has been smoothly running SoLdierR ROM for a couple of weeks. Until two days ago, when my phone decided otherwise. If I restart the phone, the freezing stops for a bit and isn´t noticeable until I start opening apps and that´s when it starts getting really annoying. After that the freezing starts occuring in intervals every 10sec for 3-4 sec. This is making me miss messages/voice calls if these occur during freezing intervals. If I remembers correctly, this started right after I cleared phone memory a couple of days ago. Is there any way to resolve this without me having to backup data and restoring phone?
What I've tried doing so far:
Restarts, shutting down phone for longer periods of time, booting in safe mode (still freezing), booting in recovery mode and deleteing cache/dalvik, deleting apps recently installed, inactivating google apps (google, google play, google services) and deleting cache then unstalling update and then reactivating them, removed root.
Click to expand...
Click to collapse
when you installed your custom ROM, did you delete the folder on internal storage named "android"?
youdoofus said:
when you installed your custom ROM, did you delete the folder on internal storage named "android"?
Click to expand...
Click to collapse
I believe I did, used TWRP and wiped everything before installing my custom ROM. I'am starting to think about doing a clean install all over again however, that won't mean that this issue won't come back later?
yarmannen said:
I believe I did, used TWRP and wiped everything before installing my custom ROM. I'am starting to think about doing a clean install all over again however, that won't mean that this issue won't come back later?
Click to expand...
Click to collapse
considering there arent that many variables that go into ROM installation, its likely just some one-off situation. If it wasnt, there would be a ton of folks reporting the same issue. Sometimes dropping fat man or little boy and starting over is all thats left. Been there so many times with the S3 and S5, i cant even begin to tell you.
youdoofus said:
considering there arent that many variables that go into ROM installation, its likely just some one-off situation. If it wasnt, there would be a ton of folks reporting the same issue. Sometimes dropping fat man or little boy and starting over is all thats left. Been there so many times with the S3 and S5, i cant even begin to tell you.
Click to expand...
Click to collapse
Yepp! I doing a clean install atm. Got another question wich is a bit off-topic. I'am using soliders latest ROM, I noticed he did release a new firmware update. Is it enough flashing the ROM or do I have to flash firmware by itself later? Or do I simply do nothing after flashing the ROM? Sorry if I'am asking obvious question but this a all still new to me.
yarmannen said:
Yepp! I doing a clean install atm. Got another question wich is a bit off-topic. I'am using soliders latest ROM, I noticed he did release a new firmware update. Is it enough flashing the ROM or do I have to flash firmware by itself later? Or do I simply do nothing after flashing the ROM? Sorry if I'am asking obvious question but this a all still new to me.
Click to expand...
Click to collapse
no worries mate, we all try to take a look at members post count before casting judgement on them for the question they asked. For that matter, we try to avoid casting judgement period, and im saying that as a member, not a moderator.
im not directly familiar with the soldier run of ROMs, but if the firmware version has changed, it is wise to install the full firmware.
Also, i wouldnt consider what you asked to be off topic at all.
youdoofus said:
no worries mate, we all try to take a look at members post count before casting judgement on them for the question they asked. For that matter, we try to avoid casting judgement period, and im saying that as a member, not a moderator.
im not directly familiar with the soldier run of ROMs, but if the firmware version has changed, it is wise to install the full firmware.
Also, i wouldnt consider what you asked to be off topic at all.
Click to expand...
Click to collapse
Good to know
I've run into a problem after flashing the custom ROM. I'am stuck on the Samsung logo, what should I do? Would appreciate a step by step explanation.
yarmannen said:
Good to know
I've run into a problem after flashing the custom ROM. I'am stuck on the Samsung logo, what should I do? Would appreciate a step by step explanation.
Click to expand...
Click to collapse
well, you have TWRP and magisk installed, i assume. Correct?
youdoofus said:
well, you have TWRP and magisk installed, i assume. Correct?
Click to expand...
Click to collapse
Yes! TWRP is installed. Magisk got installed with the ROM.
yarmannen said:
Yes! TWRP is installed. Magisk got installed with the ROM.
Click to expand...
Click to collapse
to be perfectly honest, if youve done all the things in the OP and its still doing that, its time to drop fat man or little boy and start from stock tar.md5. Boot to DL mode and flash the stock firmware. Obviously something is awry and the usual tricks didnt help so far. Mushroom cloud time