Related
I never had a random reboot on ICS now on JB I'm having it at least once a week...not a lot, I know but still something is not right. The last time this happened I tried looking further into it and the only thing I see that may be causing the issue is signal loss. I am 100% stock and have maybe 25 downloaded apps, if that. Is there an app for STOCK that will backup some of my data? I really don't think a factory reset will help but I'll give it a shot. Any other ideas? I freaking love this phone and this is my only complaint....would love to fix the problem. Thanks.
Here's a shot of the signal before the reboot.
Is it worth trying a factory reset? I feel the chances of it doing any good are very slim. Switch to a different modem?
Sent from my SCH-I535 using xda premium
I'm having the same issue, and a reset did not help.
Sent from my SCH-I535 using xda app-developers app
Thanks for the reply. As long as it does not get worse it's not a huge deal. Maybe the next update will fix it?
Sent from my SCH-I535 using xda premium
Not sure what the right word is (hotboot?) but today my phone rebooted (not fully) while I was using it. No fc's or freeze ups, just the reboot. I'm currently on the no wipe leak which ended up being the official ota.... Since the no wipe was modified would it make any sense to install the full wipe version to see if the problem is resolved?
Sent from my SCH-I535 using xda premium
Flashed full wipe via Odin. In case anyone else has this problem I will post back with results in a week or so.
Sent from my SCH-I535 using xda premium
I'm having the same issue. It seems that something is causing JellyBean-enabled SGS3's to just jump into "interrupt heaven". It's always a quick boot, never resets the "Up time" counter, and only takes a few seconds to get back to normal, but it's a real pain in the arse!
Any ideas what the culprit is, guys? I'm running a newly replaced (ordered it on January 2nd and the first thing it does was download and upgrade to JellyBean "VRBLK3" before I could even start get it loaded, basically as soon as I activated the phone, it started to download the OTA before I could even get to anything else). I know in my case I have a couple of mods installed - maybe one or more of these is common amongst those of us having issues? I have the "4x5 scrolling" mod and the "BLK3 Logo fix" mod that removes the stupid VZW drum-beating and pulsating display on boot-up. Other than that, my phone is rooted (using method involving loading the older ICS bootchain so you can install the latest CWM recovery), has CWM Touch 6.0.2.3 and that's about it, other than your usual rooted toolkit programs. Anything common to the rest of you?
Oh, by the way - I've already tried reformatting the cache, blowing away the dalvik cache and even a complete factory reset, which seems to make it less jumpy, but it always comes back within a day or two if not just a few hours.
I had the same problem with mine rebooting when I had very bad signal. Last Friday I did a factory reset then Odin to 4.0.4 and let the phone update to 4.1.1 and the problem seems to have gone away. I am not willing to call it cured yet, but it hasn't rebooted since. This went from where I was rebooting constantly all day long at work and when on the road in bad signal areas.
So far so good.
By the way, I looked EVERYWHERE and couldn't find anyone complaining of this earlier so I figured it had to be a bad download of the update.
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Factory reset (and everything else) - it still reboots
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
ratledge said:
Well, something in a factory reset helps, but it doesn't last. First, just to be thorough, I used "ROM Manager" to 'fix permissions', then I did a complete flush of the system, removed the micro-SDXC card, did a format of the cache partition, flushed the Dalvik cache, then did a factory reset and reinstalled everything. I seemed to help for a while, but eventually it started to reboot randomly - sometimes when it was just sitting idle not even being used at all.
That indicates to me there's something funky in the JB (VRBLK3) firmware, especially since I was seeing reboots even while I was booted in safe mode, where nothing loads except factory-installed programs.
Fortunately, it never reboots while it's in recovery or download mode... :silly:
Ah, I forgot to note: this is the second phone that acts exactly the same way with the VRBLK3 (Jelly Bean) ROM update. Symptoms of the problem are identical, down to the spontaneous combustion that started this thread. Mine's not "in pocket" as per the OP, but - I don't think that has anything to do with it.
Click to expand...
Click to collapse
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Ryno77 said:
Thanks for thoroughly trying different things to try and figure out the issue. Your problem seems worse than mine... I was getting reboots every few days. All day today was fine after installing full wipe but that's not a thorough test for what I was experiencing.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
New SIM?
SlimSnoopOS said:
You could also try getting a new sim from Verizon to see if that helps with connectivity to towers. You've already Odin flashed stock images and wiped pretty much everything significant at that.
Click to expand...
Click to collapse
Well, unfortunately I've done that - twice in the past ten days, the latest one came Tuesday afternoon. No change, still just reboots while I'm not even using the phone, and it's not the phone, it's the software. I can't say for absolute certain that it is in the VRBLK3 / JB code, but I can say for sure it _is_ something I am running, but the fact that it does reboot in safe mode indicates it's not anything downloaded or added to the base system as shipped.
ratledge said:
It's something in Jelly Bean update itself. I tried booting my phone in "Safe Mode" - which only loads factory programs, and it still happens. I sure wish I could put a finger on anything in the way of a pattern, but - so far there's nothing I can single out that seems to make any difference. I'll do the system/factory reset and re-install everything one more time just to see if it helps.
Weird...
Click to expand...
Click to collapse
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
6 Pebble Blue 32MB phones in about 8 months
jaymattt said:
Irrelevant question -- can't help my curiosity. How is it that you're on your 6th GS3? You get a new one every month?
Click to expand...
Click to collapse
Heheh... Well, I got one on "day 1" by pre-ordering it from Verizon, after two months the power button fell off. They sent me a "CLN" one, it lasted ten days and started randomly rebooting (even if reloaded with 'virgin' unrooted OS), the third (another "CLN") was delivered with no power button and the volume rocker fell off while I was taking it out of the box. At that point, I got kind of pizzed and did the 'good customer for 10 years' and elevated it through three levels until I finally got them to ship me a brand new one. That one lasted two months until my wife left it on top of my car and I backed over it in my driveway. I used my Asurion (insurance) to get #5, which arrived rebooting from the moment I started it up. Within a few days after monkeying around with their tech support (they ain't the brightest bulbs - instructions include "remove the battery and dial yourself and hit the 'Send' key three times" - not kidding) I managed to get #6 shipped out, and it's first act of life was to suck down the VRBL3 (Jellybean) software update and I've mucked around with it for two weeks, tried loading it with various combinations of "No Wipe" and "Factory Reset" versions of VRBLK3, removed a bunch of programs I've had installed but never really used and it still just vibrates about once an hour (and it's totally random, sometimes lasts 6 hours, sometimes 6 minutes before rebooting), jumps to the "warm/quick start" and recycles without resetting the "time up" counter. I'm thinking it's something I fed it (i.e. a nasty program or interaction between programs) - but I've come up empty-handed so far as running it to ground.
Does anyone have any knowledge of known interactions or "bad programs" that just don't play well together under JB?
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Sadly my friend, you need CLN #7. Nothing here is going to resolve that.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Well, normally - I would agree. But this makes three phones that act exactly the same in a row. The first of which was my 2nd "New" GS3, updated OTA to Jellybean - which immediately started the rolling reboots. The problem with the "CLN" phones are that they were all defective in one way or another, or they wouldn't be recertified. I don't really think VZW does a good job recertifying these phones, there are just too many of them coming out every single day, and - lord knows Asurion probably is behind that curve. :silly:
All three phones have been identical in their behavior - "down to the letter" since VRBLK3 was released. :fingers-crossed:
Question: now that I've used my insurance, do I _have_ to go back to Asurion for replacement, or since I'm still in my first year, will VerizonWireless entertain sending me another? It seems like reading the information that comes with the Asurion phones, they are the ones that are now guaranteeing my phone for a full year from the time it was sent (that would be this past Monday).
The phone has an Asurion sticker inside it, not a VZW one...
And the winner is: battery replacement. Every single VZW marked battery causes it to reboot, but a plain old Samsung battery (made in Korea - I've noticed almost all the VZW branded SKUs are made in China) works 100% and gives me an average of 12 hours moderate usage. The batteries I had from previous phones, VZW and Asurion all have the Verizon markings on them, and every single one of them causes it to reboot. This new one I got today straight from Samsung does not.
Curious, huh? I have one out of five batteries with VZW markings, and it does the same as the other four "made in China" ones. You've gotta wonder...
Glad you found a fix. Is it possible the new battery is slightly larger? Wondering if the old batteries were maybe a bit loose.
Sent from my SCH-I535 using xda premium
I've never had any major problems with my Infuse since I got it.
The battery is getting weaker but I bought a 2600Mah USB Backup Battery and that gives me another 7-8 hours for about 13-14 hours of use.
To make a long story short, I unlocked for use in Mexico City on TelCel and had some issues, so I returned the phone back to stock, unrooted.
Since that point however, while it would occasionally freeze before, its become a daily thing now and really bothersome because I can't even stop audio from playing via bluetooth. The touch screen becomes unresponsive and only a soft reboot or a hard reboot (removing the battery) returns the phone to a useful state.
It seems I have to do is every couple of hours now though, so I am posting here to get some suggestion on how to fix it.
Its been two years already since I got it so I am eligible for a new phone, but this one continues to work well besides this issue.
Thanks
djfourmoney said:
I've never had any major problems with my Infuse since I got it.
The battery is getting weaker but I bought a 2600Mah USB Backup Battery and that gives me another 7-8 hours for about 13-14 hours of use.
To make a long story short, I unlocked for use in Mexico City on TelCel and had some issues, so I returned the phone back to stock, unrooted.
Since that point however, while it would occasionally freeze before, its become a daily thing now and really bothersome because I can't even stop audio from playing via bluetooth. The touch screen becomes unresponsive and only a soft reboot or a hard reboot (removing the battery) returns the phone to a useful state.
It seems I have to do is every couple of hours now though, so I am posting here to get some suggestion on how to fix it.
Its been two years already since I got it so I am eligible for a new phone, but this one continues to work well besides this issue.
Thanks
Click to expand...
Click to collapse
1. your microSD may be going bad
2. if you haven't done so, back up all your stuff and try a factory reset...this may erase all existing info and bring the phone back to day#1
qkster said:
1. your microSD may be going bad
2. if you haven't done so, back up all your stuff and try a factory reset...this may erase all existing info and bring the phone back to day#1
Click to expand...
Click to collapse
I mentioned that in the post, I did it while in Mexico City. It worked fine until this week, late last week. The battery only gives me about 5 hours now with just 32% audio playback and about 10% web access.
I guess I'll order a Anker battery from Amazon.
I rooted the phone again last night but before I did that, the phone became unresponsive three times in an hour. Which microSD card are you talking about? I just bought a 32GB Class 6 card and that works fine, I play all my audio from it, no problems.
If you mean the internal microSD card, that could be possible. I assume I can crack open the phone and replace this easily?
I should mention it never does that while plugged into a power source, so maybe this is all battery related.
Possible Fix...
When I had to hard reboot the phone again this afternoon, a little forced closed window came up for TwLauncher.
After rebooting the phone I looking at Titanium Backup and cleared the cashe from TwLauncher and that seems to have solved the problem.
Somebody on here mentioned that after installing a ROM they had the same problem, was worth a try.
I will report back if the issue returns.
djfourmoney said:
When I had to hard reboot the phone again this afternoon, a little forced closed window came up for TwLauncher.
After rebooting the phone I looking at Titanium Backup and cleared the cashe from TwLauncher and that seems to have solved the problem.
Somebody on here mentioned that after installing a ROM they had the same problem, was worth a try.
I will report back if the issue returns.
Click to expand...
Click to collapse
My personal beliefs are that TB is good for causing a lot of problems.I used to use it,even bought pro,but even not restoring data when restoring apps I seamed to develop odd quirks or problems on about any ROM. Since not using it have much fewer problems.I am sure many people love it and think it's great, just thought I would give my $0.02
if your battery holds a charge...that is, it's letting you run the phone for more than several hours, it's unlikely to be the battery.
lags are usually due to apps misbehaving, media scan, wakelocks and wifi bugs...there are some others.
a factory reset ...complete reset..complete stock..will let you know if you have hardware of software issues.
qkster said:
if your battery holds a charge...that is, it's letting you run the phone for more than several hours, it's unlikely to be the battery.
lags are usually due to apps misbehaving, media scan, wakelocks and wifi bugs...there are some others.
a factory reset ...complete reset..complete stock..will let you know if you have hardware of software issues.
Click to expand...
Click to collapse
Thus far, that issue has not returned. Yes the battery holds a charge, but last only about 5-6 hours now, not 7-8 hours.
It seems it was a minor software issue. I did a factory reset, you keep missing that.
I did it in Mexico City (7 days ago).... Since that point and returning to the US, I have put my apps back on the phone. I had already updated to Gingerbread and it just reset to that.
I won't know more until I am out and about with my phone. I will be watching various auto racing events and don't plan on leaving the house this weekend.
Aussie V8's at COTA
NASCAR All Star Race @ Charlotte
World Challenge @ COTA
ELMS @ Imola
DTM @ Brands Hatch
WTCC @ Sazburg
Nurburgring 24 Sunday-Monday
elbscorp said:
My personal beliefs are that TB is good for causing a lot of problems.I used to use it,even bought pro,but even not restoring data when restoring apps I seamed to develop odd quirks or problems on about any ROM. Since not using it have much fewer problems.I am sure many people love it and think it's great, just thought I would give my $0.02
Click to expand...
Click to collapse
No problem, I've never had a problem with TB. I updated the rom to a rooted version of the AT&T Gingerbread release so I could even use it... lol
The phone was rooted for Froyo, I downloaded the AT&T Gingerbread from Samsung via Kies when it was released and it remained rooted.
But resetting it back to stock, TB didn't work until I put the rooted rom on the phone.
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
After you did the factory reset how did you put your apps back?
elbscorp said:
After you did the factory reset how did you put your apps back?
Click to expand...
Click to collapse
Exactly...you had to use TB or another restore. If you used TB on froyo and restored on GB or vice versa, you may run into issues.
and ...sigh... I did not miss the fact that you stated that you had reset the phone. I just had doubts that you understood what I was trying to say...from inside the phone..under settings/privacy..there is a reset option. make sure everything you wanted is already backed up. reset it..then put it into download mode and use one of the odin or heimdall package and flash it back to complete stock...run it stock and dont back up anything. download only apps from the play store or side load the apps if you had the apk's.
check the battery use to see if you have wake locks or android OS or android system eating up for battery..then you will know
elbscorp said:
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
After you did the factory reset how did you put your apps back?
Click to expand...
Click to collapse
Well like this, I will not go into the details but somebody else put Swipe Lock on the phone and of course I didn't know what he put into the phone. I was trying to resolve data issue on TelCel.
I had to do a hard reset outside of the operating system. Since the ROM was already upgraded to Gingerbread but unrooted, it went back to its unrooted state meaning I couldn't use TB.
So I re-downloaded apps from my memory. All of them are free so it wasn't an issue, just time consuming.
qkster said:
Exactly...you had to use TB or another restore. If you used TB on froyo and restored on GB or vice versa, you may run into issues.
and ...sigh... I did not miss the fact that you stated that you had reset the phone. I just had doubts that you understood what I was trying to say...from inside the phone..under settings/privacy..there is a reset option. make sure everything you wanted is already backed up. reset it..then put it into download mode and use one of the odin or heimdall package and flash it back to complete stock...run it stock and dont back up anything. download only apps from the play store or side load the apps if you had the apk's.
check the battery use to see if you have wake locks or android OS or android system eating up for battery..then you will know
Click to expand...
Click to collapse
See above.
I used download mode to get out of Swipe Lock. I never used Swipe Lock, a-hole wanted to charge me 120 pesos ($7) to wipe it and put it back to stock, I wasn't going to do it, I know enough about Android phones to do it myself.
Oh well, lesson learned, I believe wiping the cashe from TwLauncher has solved the problem.
I did re-install all the apps from the store. I wasn't able to use TB until Thurs night (5/16). I noticed the errors Friday afternoon, wipe the cashe and no issues since.
I feel like I've done everything that has been mentioned and I have still had no luck getting my camera to connect. It used to only happen maybe once a month or so and I would just restart my phone and the problem would be gone - no big deal. Now it's been 3 days and no camera. I've rebooted my phone, cleared the data, cleared the cache. Both cameras don't work. I'm out of ideas. Should I request a new unit be sent to me?
Did you try a factory reset (assuming you're on stock)??
If you're using a custom rom, dirty flash the rom or do a clean wipe/install and see if the problem goes away... If it doesn't, it's most probably a hardware issue.
Does anyone else know how to solve this ?
Have you got any more info? When did it start? App you installed recently that might be responsible? Tried the usual restart/clear cache/factory reset?
Nejums said:
Have you got any more info? When did it start? App you installed recently that might be responsible? Tried the usual restart/clear cache/factory reset?
Click to expand...
Click to collapse
I tried to do a factory reset but the lag still occured. When is Google going to release the next update ? The 1st of next month ?
Since the first week of owning (got in on the Verizon pre-orders), my pixel 2 will occasionally stall. It pauses for a few seconds and then resumes. Once or twice I get a system ui has stopped message, but typically not. It is most noticeable when scrolling, either in the news feed or Google Now or my texting app. But I've seen it while toggling a setting in the notification shade.
Updating to the Dec and then January update didn't help it. Unlocking 3 wks ago and installing a new kernel didn't help.
Is this similar to what you've experienced?
trimax84 said:
Since the first week of owning (got in on the Verizon pre-orders), my pixel 2 will occasionally stall. It pauses for a few seconds and then resumes. Once or twice I get a system ui has stopped message, but typically not. It is most noticeable when scrolling, either in the news feed or Google Now or my texting app. But I've seen it while toggling a setting in the notification shade.
Updating to the Dec and then January update didn't help it. Unlocking 3 wks ago and installing a new kernel didn't help.
Is this similar to what you've experienced?
Click to expand...
Click to collapse
Yes and I also find the camera to be very unstable. For example, when I take a picture and tried to zoom in, it doesn't do anything. I have to double tap and then I am able to pinch the screen
All this sounds extremely uncharacteristic if this is a stock / unrooted Pixel 2.
I've noticed that facebook and facebook messenger not only consume tons of battery, but they are usually the culprits of hard stalls.
if it persists after the factory reset, I'd try to reflash a stock image if you know how to do this. Factory reset wipes everything and starts from scratch from the stock firmware, either that or just hang tight as the next update is coming soon for Feb. I'd reflash the new Feb image. Probably just a bug. Mine lately has also been tripping out, not lagging, but just acting random like brightness toggling, etc......... they appear to be bugs.
mikeprius said:
if it persists after the factory reset, I'd try to reflash a stock image if you know how to do this. Factory reset wipes everything and starts from scratch from the stock firmware, either that or just hang tight as the next update is coming soon for Feb. I'd reflash the new Feb image. Probably just a bug. Mine lately has also been tripping out, not lagging, but just acting random like brightness toggling, etc......... they appear to be bugs.
Click to expand...
Click to collapse
Is it going to be released the 1st if the 5th of February?
Colday96 said:
Is it going to be released the 1st if the 5th of February?
Click to expand...
Click to collapse
Not sure generally it's within the first 5 days of the month. Personally I'd like to see it this Fri the 2nd but it could not be released until next Monday the 5th which seems more probable.
mikeprius said:
if it persists after the factory reset, I'd try to reflash a stock image if you know how to do this. Factory reset wipes everything and starts from scratch from the stock firmware, either that or just hang tight as the next update is coming soon for Feb. I'd reflash the new Feb image. Probably just a bug. Mine lately has also been tripping out, not lagging, but just acting random like brightness toggling, etc......... they appear to be bugs.
Click to expand...
Click to collapse
If it were a bug it would be happening to everyone. Very very doubtful that Feb update would do anything for you since it's not a common issue. Id do what has been suggested and reflash the stock image.
Step one apply factory image, step 2 factory reset. Don't install any apps and check for issues, if it still has issues exchange for a different device. If it has no issues, it is an app or mod.
ahoslc said:
If it were a bug it would be happening to everyone. Very very doubtful that Feb update would do anything for you since it's not a common issue. Id do what has been suggested and reflash the stock image.
Click to expand...
Click to collapse
Apparently it is not.
https://9to5google.com/2018/01/02/psa-google-pixel-2-users-lag-sideload-jan-sec-update-fix/
I have been facing this issue since yesterday. I am running OB7 with stock kernel. The phone's screen suddenly turns black and gives the lockscreen password screen as if the phone has rebooted and all the apps are killed.
Anybody has any solution or facing this?
Hey, actually using last OOS beta 7, facing the same issue since at least ytd.
Glad to see that i'm not alone
I have had that a couple times since the release of 9.0 and with 9.02 both Official, not OB. I try to reboot my phone every 2 or 3 days and sometimes I forget and it seems to happen if my phones up time is above 6 or 7 days.
I just wiped cache, will let u know if it worked or not
OnePlus 6 Rebooting Apps, Black Screen
My partner got her OnePlus 6 brand new one week ago, and just tonight it started experiencing the same problems as the OP described. According to her she updated to the latest OS software on day one, and it all worked as it should for the past six days until a couple of hours ago. It does that reboot-like thing about 8 times an hour right now. We're on the fence on if we should return it to the online retailer as we're on the last day. Reformatting to factory settings didn't fix anything. Hoping someone finds a solution.
Edit: It's a stock OnePlus 6 Mirror Black phone & operating system OOS 9.0.2, using common social networking apps. I just joined this forum and this is my first post.
Weird...
Actually, 0 reboot since the cache wiped
SmXme said:
Weird...
Actually, 0 reboot since the cache wiped
Click to expand...
Click to collapse
Hope that continues to work. As for us, we tried wiping the cache an hour ago. It didn't help in our situation. It's currently "rebooting" so much, it's unusable.
Ankit Chahar said:
I have been facing this issue since yesterday. I am running OB7 with stock kernel. The phone's screen suddenly turns black and gives the lockscreen password screen as if the phone has rebooted and all the apps are killed.
Anybody has any solution or facing this?
Click to expand...
Click to collapse
Had the same issue since yesterday
Only solution i found was to remove google and whatsapp from beta and to do a hard reset.
Reset solved my problem
Things i tried before reset-
1)Settings reset
2)clear cache
3)restart
Only solution was a reset without erasing internal.
Hope y'all come to the same result.
Still ni reboots since i wipe the cache, looks like it was enough for me... Hope it will
Hard resetting doesn't work in our case. As a last resort, I'm currently trying a OxygenOS ROM downgrade, or if I can't do that, upgrading to Open Beta 7. The latter of which I'm trying, but the phone restarts mid-update constantly. Not even safe mode stops the rebooting during the update.
Let us know if it worked,
Actually had 2 reboots since ystd cache wiped
SmXme said:
Let us know if it worked,
Actually had 2 reboots since ystd cache wiped
Click to expand...
Click to collapse
We had to return the OnePlus 6 before today ended because of the small 7 day store warranty (living in the Philippines). After I couldn't even install the ROMs in Safe Mode because of restarts every minute now, there didn't seem to be anything I could do. Hoping the next OnePlus 6 we get in three weeks doesn't have this issue.
I've had such issues with OB8 & OB9, probably with OB7 as well - can't remember.
Wiped cached many times, changed kernel and so on.
Actually, OB8 was a fresh install as well.
UPDATE
I reverted back to 5.1.11 and then updated to 9.0.2, so far so good. I'll post updates in the next few days.