Related
Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial
Did you try to flash via ODIN? Maybe it will help you to boot it to normal.
The_Unofficial said:
Hey guys,
I need help. Badly. My trusty SCH-I535 has pretty much gone to pot over the last three days. It started with the lockscreen/power button becoming so loose and sensitive, that the screen was perpetually turning on and off. However, my warranty expired last Thursday. Aside from that, the software was functioning beautiful (Carbon ROM, unknown August 4.3 nightly). Today however, the phone decided to freak out. Suddenly, it began displaying the incorrect time, wouldn't show me new messages, and applications were incredibly unstable. In an attempt to fix the issue, I decided to re-flash the ROM. This however, made no change. Therefore, I made the decision to finally update to the most recent stable version. After doing this, the phone wouldn't boot past the carbon boot animation. I rolled back to an older build, and had the same issue.
Here's where it gets sucky. After rolling back didn't do anything, I was in the process of re-flashing 1.8. During install process, TWRP crashed. This left me without a bootable system partition. As the night has worn on, it's become worse and worse. Now, TWRP is crashing often before the splash screen, at the "Samsung Galaxy SIII" screen. Occasionally it will load, but always locks up and crashes before finishing the install process. Same deal with CWM. I have tried several versions of both recoveries and none have made a single bit of difference. I've scoured the forums, and can't seem to find an identical problem/working fix. I've tried everything I can find, and so far, nothing productive has happened. It's 3:25AM over here, and I'm exhausted. I'm at my wits end. Any input would be fantastic.
Thanks so much,
The_Unofficial
Click to expand...
Click to collapse
Your broken power button is probably the issue. The reason your recoveries are crashing is likely because the power button is triggered and it's making the phone turn off in the middle of the process.
It's unfortunate your warranty just expired, but you can get it fixed through a website, then you should be good from there. Also I would try to call up Samsung and tell them what you think the problem is, they might give you a break and fix your phone anyway since it's only a week after warranty.
Sent from my SCH-I535 using Tapatalk 2
Details...
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.
The_Unofficial said:
Alright guys. More details. Sorry it took so long to reply. Apparently I had Gmail set to send XDA emails to spam. Silly me.
The more times I attempt to boot to recovery, the earlier TWRP will freeze.
TWRP rarely makes it beyond the "Installing System" process
TWRP NEVER makes it beyond the "Creating Symlinks" phase
I'm using TWRP 2.6.3.0
If I let the phone sit, it gets farther in the installation process before hanging
Bad Username, I tried contacting Samsung and Verizon. Neither one of them would replace , or fix it for me. Have any specific resources for repairing the button? That would be excellent. I just ordered a cheap $3 case on Amazon to see if that would help fix the problem. I don't, however believe this is causing the problem. TWRP has a lockscreen. It never goes to the lockscreen, it just hangs, then eventually force reboots. Almost as if some temporary RAM storage is being filled up. It's quite strange.
skyss07 I would REALLY prefer not to flash to stalk. Like, REALLY. This would mean losing all my files and pictures. I'm not too keen on that. I'm saving that as a final resort only.
Click to expand...
Click to collapse
Mobile tech videos would do it, not sure what the cost would be, I'd try contacting them.
Sent from my SCH-I535 using Tapatalk 2
Hey guys I've had my N5 for almost a year now but it seems to have gone kaput on me recently...
On Monday I was on a skype call, (just audio) when my phone suddenly restarted, I didn't pay much mind to it as that happened before and it would usually just cut back on, but this time, it restarted, and restarted and just didn't stop. That lead me to think its the power button being stuck so i checked it out and made sure its not being depressed and well yeah it wasn't. And soon after that the phones screen was sometimes on during the reboots and sometimes off. I knew it was rebooting because the N5 vibrates a bit when Google pops up on the loading screen in a certain way, but yeah now the screen doesn't light up at all, there's still vibrations and sounds like when I call or when I say Okay Google a few times, the LED will even light up during a call. I know the phone is "on and working" in the background but the screen doesn't light up and as such I can't touch it, any ideas and or advice friends?
bump de bump?
Possibly your backlight burnt out? Water damage?
if you are running cyanogenmod, you could be experiencing sod "sleep of death". thats when you know the phone is on and working, but the screen doesnt turn on. ive been reading lots of complaints about cm and the sod.
TheROMGuy said:
Possibly your backlight burnt out? Water damage?
Click to expand...
Click to collapse
As the phone kept rebooting it went from seeing everything, to seeing nothing but the back light to dark, so maybe? It was just by me on my desk too so I was doubtful about the water damage but I put it in the sealed rice bag for about 24 hours just in case but still no luck.
I actually am running cyanogenmod and whenever I do have a problem I always feel that its related to CM as the phone doesn't have any physical damage...maybe I should look into that, any other ideas friends?
P.S I am using the ElementalX Kernel and UNFORTUNATELY I turned on the FAST CHARGE USB option and that makes the phone play funny with the computer, if you guys have any advice as to how I could turn off that option please do let me know
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
dynamo147 said:
http://forum.xda-developers.com/goo...l-06-03-14-one-click-factory-restore-t2513937
I used this tool to try and remove anything that could be bothering my phone, software wise, and I'm not sure if it wiped away Kernels and Roms but thought you guys should know, my computer now recognizes the phone and I can see folders and such, which are now empty.
Click to expand...
Click to collapse
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
simms22 said:
all it does is completely wipe your phone and install an older android version. flashing the factory img will do the same, except youll get the newest android version. don't use these tools, doing things the right way will be more beneficial to you. anyways, since cm is having issues, try a different rom, or just go stock.
Click to expand...
Click to collapse
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
dynamo147 said:
Thats my problem though my screen is still untouchable or see able and it makes it hard to flash stuff since I can't properly use TWRP, and having the fast charge hack on my computer doesnt really sense im in USB Debug but I guesssss its off now though, but still no screen loving
Click to expand...
Click to collapse
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
simms22 said:
if still no screen, its probably physically damaged(hit or factory damage). is an exchange possible?
Click to expand...
Click to collapse
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
dynamo147 said:
Well i got mine through the Play Store and I did think about an RMA, I know there was that free screen replacement thing going on but the customer rep sounded like he had no idea what I was talking about. and I'm thinking its a flex cable issue as my phone hasn't incurred any damage from drops or bumps or anything since i make it a point to be stationary while using phone, but....where the sim card tray is, that "bridge" or thin piece on the bottom side toward the phone has split as a result of my bad sim card ejecting, but that was when i first obtained the phone, also there is another split, inside the phone there is a canopy above the charging port that is split but i still know that occurred long before this, and its not even an electrical piece along with the sim card bridge thing.
BUTTT yeah im afraid if I RMA they will use that as an excuse to charge me $400, even though I know it's not playing any sort of factor in my screen acting up....Is there a policy on that?
Click to expand...
Click to collapse
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
simms22 said:
ive rma'ed before, google is really good about it. i sent my nexus 7 back with a custom recovery, rom, kernel.. and the thing going on with google and exchanging the n5 once without question, isnt about the screen, its for anything.
Click to expand...
Click to collapse
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
dynamo147 said:
I suppose I might as well shoot for it? Is there a way to decline paying for the device if they decide that I should pay?
Click to expand...
Click to collapse
send back the rma? honestly, i dont know. i dont know anyone thats ever had to pay. unless its obvious that you did something, youll be fine.
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
I will chat it up with one of the customer service peeps and see what they think then, and maybe even hopefully one will know about the replace anything deal
anactoraaron said:
So when you hold down the power button and the vol - for about 15 seconds the bootloader screen doesn't show up? If so, yeah try to RMA.
Click to expand...
Click to collapse
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
dynamo147 said:
and yup Ik its in bootloader mode though because the computer beeps and tries installing drivers and what not and also because it does that single vibrate, but yeah the screen is still dark so I can't see my selections, I believe I can still actually make a selection though, just unable to see them
Click to expand...
Click to collapse
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
anactoraaron said:
Check to make sure you have the newest drivers (there's a sticky in the general section with all the useful info). If you bought it from the play store see if you can get an RMA - Google seems to have a good rep with this. It wouldn't hurt to flash a factory image to erase everything either before sending it off (privacy and whatnot). If you have the newest TWRP (2.8.0.1) if you boot into recovery and you should be able to access the internal storage without having to select anything (in case there's anything there not backed up). Boot to recovery is volume down twice and power I think.
Click to expand...
Click to collapse
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
dynamo147 said:
Well now that I used that tool I'm not sure if my recovery is still TWRP or if it's stock, it flashed a stock factory image I'm told, but that doesn't remove the Kernel and Recovery too does it? I wanna get it as stock as possible before I sent it out. At this point I believe it has a factory image but I can't say for sure about anything else
Click to expand...
Click to collapse
See here http://forum.xda-developers.com/showthread.php?t=2513701.
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
IrrationalBanana said:
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
Click to expand...
Click to collapse
Did you already tried to format your whole phone so also SD card / system/cache/ etc just make it completely clean and connect your phone to your PC while in recovery paste darkobas rom (or other rom ofcourse) on your sd-card and gapps flash it and start really clean.
Just my 2 cents
check ur phone hardware for damage as u had changed everything multiple time and still no profit which means problem is not on surface maybe its deep and i am irrational that any change of rom would help , that said maybe try to flash good firmware through fast boot ,take help from cc or more persons . i may be wrong but i had concluded this - it seems that the connection between gpu or cpu with os is kinda broken which doesn't make sense as u had changed it multiple times but still feels like it.
moneyvirus said:
Did you already tried to format your whole phone so also SD card / system/cache/ etc just make it completely clean and connect your phone to your PC while in recovery paste darkobas rom (or other rom ofcourse) on your sd-card and gapps flash it and start really clean.
Just my 2 cents
Click to expand...
Click to collapse
I have formatted everything and I believe I have removed everything useless from the memory. I have also flashed multiple roms and the issue is still there
IrrationalBanana said:
I have formatted everything and I believe I have removed everything useless from the memory. I have also flashed multiple roms and the issue is still there
Click to expand...
Click to collapse
Does the problem also occure when you have 0 extra apps installed so just rom and gapps?
It sounds like some background proces
IrrationalBanana said:
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
Click to expand...
Click to collapse
Have you tried flashing the stock rom via fastboot? If that doesn't solve your problem, it might be hardware related. You can find the latest fastboot update here: link
Keep in mind that if you want the latest cos13, you'll have to update your device via the ota. This method will also completely erase your device, including /sdcard
If there is no background processes, try to install Cynogen OS 12.0.
If the phone have the same issue, then it is hardware.
Sent from my A0001 using Tapatalk
moneyvirus said:
Does the problem also occure when you have 0 extra apps installed so just rom and gapps?
It sounds like some background proces
Click to expand...
Click to collapse
Problem is there even after many completely fresh ROM installs (formatted all data from memory)
What are the files that re absolutely necessary for the phone to operate? Could there be some hidden junk in the internal memory Im not seeing?
yeah, NAND trimming is important. But not for a fresh install
eng_saad said:
If there is no background processes, try to install Cynogen OS 12.0.
If the phone have the same issue, then it is hardware.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Phone became stuck on bootlogo after installing CM 12 snapshot
IrrationalBanana said:
Phone became stuck on bootlogo after installing CM 12 snapshot
Click to expand...
Click to collapse
firmware
IrrationalBanana said:
Phone became stuck on bootlogo after installing CM 12 snapshot
Click to expand...
Click to collapse
The best solution in my opionion is to restore the stock ROM [COS 12.1 / 12.0]
Follow the steps in this thread
NOTE that your data will be deleted.
IrrationalBanana said:
HI all!
I have an OnePlus One. A month ago it became unusably slow, where all animations took the phone 5-10 seconds to go through. Sounds and haptic feedback are immediate (pressing a button/typing), but the screen seems to lag behind.
One interesting example comes when rebooting the phone. The Android marshmallow bootlogo (CM13) takes at least 20 seconds to finish, but I can actually swipe up on the screen while the marshmallow logo is still on there and hear the screen unlock sound.
I have tried many different ROMs (SlimSaber, OxygenOS, CM13/12), deleting data, cache, dalvik and doing many, many factory resets. Nothing seems to help at all.
Anything that can be done to fix this little bugger? Setting the three animation settings to 0x seemed to help a little bit, but not all that much. Is there a completely animationless rom out there?
Click to expand...
Click to collapse
I had a similar problem on my lg g2. Some things to look out for before taking my advice:
-Is the animation/screen the only thing that's slow, but the background processes normal? (Like, if you type a bunch of letters, it registers all of them but the animation is slow).
-Prior to the problem, did you drop/bend your device, expose it to water, or take it apart?
If both (or one) of the top pertains to you, it's most likely a hardware issue. My g2 had the same problem, and it turned out to be a faulty flex cable that attached the screen output to the motherboard (I accidentally pulled too hard on it). Seeing how the OPO screen has a long black cable, that could possibly be the problem. If all else fails, and you have a bit of money to spend, get a replacement screen.
chikin said:
I had a similar problem on my lg g2. Some things to look out for before taking my advice:
-Is the animation/screen the only thing that's slow, but the background processes normal? (Like, if you type a bunch of letters, it registers all of them but the animation is slow).
-Prior to the problem, did you drop/bend your device, expose it to water, or take it apart?
If both (or one) of the top pertains to you, it's most likely a hardware issue. My g2 had the same problem, and it turned out to be a faulty flex cable that attached the screen output to the motherboard (I accidentally pulled too hard on it). Seeing how the OPO screen has a long black cable, that could possibly be the problem. If all else fails, and you have a bit of money to spend, get a replacement screen.
Click to expand...
Click to collapse
Thanks for the suggestions!! You are spot on with everything, the screen got cracked a while back and I bought a new screen for it. It was a bit dodgy and didn't fit well in the casing, so maybe a cable got pulled out lately?
On the background process thing; the typing thing is exactly as you described it. When writing my long WiFi password for example, I tap in all of the 18 characters and numbers of the password in 5 seconds, and then the screen spends the next 20 seconds doing the animation/typing in the characters, whilst I am not touching the screen. Does this mean the cables theory is solid? Or is it another hardware issue?
Stellar suggestions, I will probably spend an hour or two picking at the phone today, updates coming later
My OPO has never been slow on any ROMs. You can try to format your phone...
No result after removing and reconnecting display cables Formatted everything and installed a fresh ROM right after as well, no improvement.
Thanks however! Still open for business/suggestions
IrrationalBanana said:
No result after removing and reconnecting display cables Formatted everything and installed a fresh ROM right after as well, no improvement.
Thanks however! Still open for business/suggestions
Click to expand...
Click to collapse
send It to cc already
Traace said:
yeah, NAND trimming is important. But not for a fresh install
Click to expand...
Click to collapse
I have been reading trimming here but never found best or safe method. a link to best tutorial will be appreciated
#sychrome# said:
I have been reading trimming here but never found best or safe method. a link to best tutorial will be appreciated
Click to expand...
Click to collapse
Some roms trim by themself, others do not. It really difficult to tell which does and which not. U can test it if fstrim takes long time to run then your system usually didn't got trimmed anytime before.
Get Trimmer (fstrim) from Play Store. Its not necessary to trim system at all. Set your focus on partitions who have large amount of write processes like data or even cache.
IrrationalBanana said:
No result after removing and reconnecting display cables Formatted everything and installed a fresh ROM right after as well, no improvement.
Thanks however! Still open for business/suggestions
Click to expand...
Click to collapse
In my opinion, I still think it is a hardware error. Since you described some difficulty in replacing the screen, the cables might have been damaged, either during replacement or after. I suggest you buy a new screen, preferably one that comes already glued on to a frame.
Hello, First time poster long time user of XDA, I some what experienced with flashing roms, recovery, kernels and modems but I ran into my first major issue.
I will start with how I obtained the phone and go from there, I think the more you know the more you could help.
I got the phone on ebay relatively cheap, its apparently google locked as he forgot his password, no biggie for me ill get around that.
He claimed he was replacing the screen and cracked the new glass while trying but not the lcd.
Anyway once I received it I turned it on and tried to see how far I could get in the initial set up.
I only got to the wifi selection screen, It would not turn on and when the button moved to the on position it would indefinitely load.
I assumed faulty rom flash.
I downloaded the latest rom from sammob and flashed to oreo, same Issue, I should point out at this point I had no data left on my sim to proceed on the phone without internet.
My friend who very experienced with the flashing seen suggested the modem.
I flashed one he suggested then no sim reception def no wifi.
ok damn.
I went to flash the oreo once again and for some messed up reason I wiped the nand only.
Well I wasnt to happy with myself to say the least.
To further ad to the pain, I can no longer access recovery or download mode to salvage this.
No button input seems to work.
It gets to the pulsing samsung logo and that its.
I even resorted to making a usb jig, It has no response to that but my spare note 2 boots to download no worries with it.
It does charge via usb, The buttons were working correctly when I was first in android at the beginning.
Does anybody have any suggestions or ideas?
Many thanks in advance, I will be following this post regularly and reply with feedback and report progress.
Cheers. r3al77
My Pixel 3 randomly restarts and gets stuck in long bootloops. The frequency is completely random, ranging from three times a day (rarely) to once a week or two (more common). There is no trigger, sometimes I have it in my hand, doing stuff, and it does that, sometimes it does it when it's sleeping.
The bootloop is always the same.
I see the bootloader message, then th Google logo, and the phone restars after about one second. I never counted to loops but sometimes it must be tens of them. There doesn't seem to be a way to stop them, or at least I am not awaer of any key combinations.
I presume the phone eventually boots into safe mode or something.
I've had it for several months, bought it used in good condition off Ebay, and other than this I never noticed anything off.
This is extremely frustrating and I have no idea what to do.
Does anyone have any idea?
I really hope it never been inside water. Try updating your OS, or change to Custom ROM. If it still occurs, then that's a big problem.
It's most probably an app that's causing this, try disabling/uninstalling some apps that you don't need.
Booting into safe mode is also an option, that way you can make sure if an app is actually causing this.
I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.
WalrusInAnus said:
I factory reset and later on completely reflashed the phone at one point in not too distant past and it didn't help one bit.
It's also completely untroubleshootable given how randomly the problem occurs, which also makes me sceptical about an app doing this
I'm inclined to think it could be a hardware problem.
Click to expand...
Click to collapse
It's highly unlikely for it to be hardware problem, unless you have water/dust/humid damage.
Or maybe your phone heats really fast and therefore some pin inside the motherboard gets shortened due to the heat. But what are the chances of this happening?
But just to be sure, what happens when you connect your device to a charger with output more than 2 amp?
Did you modify your device in anyway whatsoever? Anything the previous owner noted about the device?
I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm
WalrusInAnus said:
I didn't nodify it at all.
This is the charger I use https://www.alzashop.com/vention-dual-quick-30-usb-a-wall-charger-18w-18w-white-d6323711.htm
Click to expand...
Click to collapse
Yeah, just flash some different ROM on your device and we're good.
Make sure you backup everything through TWRP and that you're flashing your device specific ROM.
As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.
WalrusInAnus said:
As a test you mean? I am used to the stock ROM and last time I checked, there was no stable Android 11 (I think) ROM I would use.
Click to expand...
Click to collapse
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.
XDHx86 said:
Was the last time you checked a year ago?? A11 has been out for a good while now. Here: Stock A11 ROM (Blueline).
And not as a test, no, flash it and keep using it. You can also flash custom ROM if that's your thing.
Click to expand...
Click to collapse
But I said I flashed the stock ROM before with no luck. You're suggesting I do the same again. That makes very little sense.
What about the Google camera and LOS btw?