Related
Ok, so everything was working fine yesterday. I woke up this morning and decided to play a little 'world of photo'. It FC's, so I mess with it for a little bit before just trying to open my normal camera. When I try to open my camera, it puts the screen in sleep mode, so I have to hit the power button and unlock the screen like normal, then it gives me the error "Cannot connect to camera".
My phone is rooted and flashed with the latest Cyanogen business, but like I said, nothing was altered, updated, downloaded, etc. My camera just stopped working. Anyone have any thoughts or ideas? Really hoping to get this resolved without having to contact HTC, as I'm sure the unlocked bootloader screen will cost me a small fortune.
If I open an alternative camera app, it opens, but doesn't work. I can back out and then go to my default camera and it works until I close it. Then it won't open again without having to go through the steps of opening the other app, etc.
I'd try a nandroid restore.
Tried it already. Tried restoring back to original, wiping, everything else. Nothing worked. Camera wasn't working all morning, now all of a sudden it's working again. Guess I'll just count my lucky chickens and chalk this up as a win...
Well, my happiness was short lived. Still having the same problem. I'm really not sure what exactly it could be. But the fact it worked the one time today gives me hope.
also having this problem. tried a nand backup and also wiping and re-flashing the gapps and the cm-5.0.4.1 update.. still nothing
it seems my camera went bad somehow, tried even flashing the stock rom, nothing... i'm calling htc, crap my phone is unlocked.. wish me luck.
update: yeap, im getting a replacement. they put $529 on hold on a credit card, send you the device and once they get the "damaged" device they release the funds... meh..
Hey velazcod, you think we can get an update on his this worked out? I'm having the same camera problem and I too am bootloader unlocked. I'd like to hear how HTC handled your unlocked device.
sorry for not posting a status before... so here is what happened:
- Called HTC and they didnt have any issues replacing the phone since the issue seemed to he a hardware issue. They have been nice about this, depends on the hardware issue, I guess if you burn the motherboard they will probably get *****y.
- You can send it to get repaired or replaced, both are in warranty, unless they find some other issue (water damage, etc). However, if you decide to get it replaced they would take your credit card, and put $528 on hold for a few days until they get the original phone back. They dont actually charge it to the credit card, just an authorization, it all depends in your bank, for example my bank (chase) put the money back in my account after 5 days.
- Anyway, I got my "new" N1, and I double checked everything before unlocking the bootloader and doing our stuff. The phone was crap, it was slow and the sticker on the battery cover seemed like it was removed, maybe a refurbished unit. I called and *****ed about it, and they said I needed to send my original phone back, and then later on request another replacement. I kept *****ing because I could live with a bad camera for a few weeks, but not with a slow phone
- Anyways, in the end they allowed me to send back that refurbished unit. After a few weeks i had no response from them and I had to call them, a day after i got my new phone, this time it was good, so i unlocked it, did my thing, factory reset the original phone and sent it on its way.
- It all seemed good for a few weeks, until i got a call from HTC saying that I needed to pay for a repair fee ($60 something) because they had found the problem had been user damage. the girl had no idea how to back that up, and i kept saying that i had never drop the phone or broken the camera in purpose (which is true). She said she was going to escalate the issue and I would get a call back. Still waiting.
In the end I got my new phone and we are all happy, but be careful, I love HTC but don't let them screw you.
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
$60 isn't that bad. I would be interested in exactly what they found.
yes that isnt that bad. and i would pay it no problems if it really was my fault. but really, i take care badly of my phones and i had never drop or have done anything to my phone that would cause this camera issue.
besides, the girl that called me had no idea what really happened or what they found, when they call me i will post the info here.
Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.
moto211 said:
Quick update:
I was having the "cannot connect to camera" error. Turns out that it was an issue with my memory card. Apparently, the card was slightly mis-seated.
Prior to discovering that, I tried everything. I flashed other ROMs, nandroid flashed back to stock, and manually restored to stock.
The weird thing is that the memory card was still functioning properly in every other aspect. I could browse my phots in the gallery and browse the contents of the memory card in Astro. Prior to my discovery, I had also formatted the memory from the settings menu. On a whim, I shut the phone down, removed the memory card, reinserted the memory card, booted it back up and gave it a shot. To my surprise, it worked!
I just thought I'd let you guys know so anyone else having a similar issue can try reseating the memory card before giving up and paying HTC for repair.
Click to expand...
Click to collapse
Well, keep in mind that it could be a placebo effect, and you think you are fixing it by fiddling the SD card but its not real.
The reason I tell you that is because, when the issue started happening for me, I would get that error randomly, and then it started happening more frequently until it totally stopped working.
Also, the Camera app not detecting the SD card gets an error when you try to take a picture and it actually says the specific SD card error. Try taking the SD card out and try it out, you will get a visual of the camera on the display, but when you try to take the picture it gives out the "SD card not detected" error... on the other hand, you might be experiencing something totally different.
This error "cannot connect to camera" also comes with the camera app not loading completely and visual of the camera not loading on the screen. Also try loading up the Barcode Scanner, you should get a similar error and no visual of the camera.
I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.
moto211 said:
I agree that it could be placebo effect. But, I was experiencing all of the things you describe regarding the camera app not loading completely and barcode scanner not working properly. I know the error that you're talking about when you open the camera app without any memory card at all and that definitely was not what I was experiencing. Also, the was nothing random or intermittent my cannot connect to camera errors. It stopped working about four days ago and no ammount of reboots, reflashes, or nandroid restores could bring it back. It wasn't until I reseated the memory card that the camera was able to load and function again. My suspicion is that when a memory card is present and you open the camera app, it tries to do something with the card as part of the loading process. I suspect that the card being slightly mis-seated causes this to fail and prevents the camera from loading properly.
I will definitely keeps you guys posted. Hopefully this is a lasting fix and not a placebo.
Click to expand...
Click to collapse
I see what you mean. Makes sense, keep us posted.
Update:
So, although the fix I previously mentioned did work, I started having other issues that indicated that the actual camera hardware was failing. When I would start up the camera app the camera image displayed on the screen started showing color distortion. Sometimes it would do that and sometimes it wouldn't. I noticed that if it wasn't distorted, I could lightly squeeze the sides of the phone and the image would become distorted and would not go back to normal after I stopped squeezing. I figured that indicated hardware issues but decided to try a low level format on my memory card just in case it was an issue of bad blocks on the card. The format didn't fix anything. A few hours later, the camera died and never came back. I started a ticket with HTC for an advanced replacement. I received my new phone on Friday and am sending back the old one today. I restored it to unrooted factory ROM and recovery image. I will keep you guys posted as to what, if any charges they try to stick me with.
moto211 said:
Update:
So, although the fix I previously mentioned did work,......
Click to expand...
Click to collapse
crap, that's what i thought. that sucks. keep us posted :-/
Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.
moto211 said:
Final update:
I returned my phone with the broken camera on Monday. Tuesday I received an email stated that they had received my device and it had a link to website that I could use to get updates on the status of the repair/return. I checked in the following day with no change. Today it showed this:
Status: We have completed your case. If you can help us improve our service, or would like to comment, please contact HTC customer service representatives.
Service Type: Repair
Service Model: C4-On site exchange
Failure Description: C/x states can not open camera app-freezes or force closes
I even called HTC to make that the ticket was closed and that they didn't need anything else from me. They said that everything was good.
Click to expand...
Click to collapse
Good to hear that.
On my case, I was never contacted again by the "escalated rep"... but I just checked my ticket/case and it seemed to have been closed, so I guess good news.
Hello Guys,
I am having the same problem as you both had. Í am seeing the same symptoms such as not able to run the camera app. My phone screen goes blank when i try to open the camera app and the bar scanner program says it cannot connect to the camera and that I might need to restart my device. I have tried to use previous roms and removed the sd card but nothing seems to work. I am wanting to send it in for repair but I wanted to know what else I should do to my phone besides reflashing the stock rom. Did either of you have the amonRa recovery program and how did you remove it if you did. Is there anything else I should do?
Thanks.
I got the original shipping rom package from modaco and renamed it PASSIMG.zip and flashed it from the bootloader. It restored everything to stock...recovery, radio, and os.
Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.
i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run
Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.
I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.
nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later
I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.
read this
http://forum.xda-developers.com/showthread.php?t=793404
Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...
I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?
Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.
TL;DR: My phone is experiencing a very similar problem to the broken internal SD after Froyo update, except on eclair and is fixed (apparently temporarily) with a factory reset. I'm on Telus, bought the phone from somebody off craigslist and have a return receipt. What should I do?
So for the second time in a few days my Samsung Galaxy S (I9000M from bell, bought on craigslist running on telus) was having problems opening an app so I restarted it. (The first time Market would force close whenever I tried to open it, the second time it was Browser). After the app force closed a few times I did a restart. The first time I restarted it (when Market froze) it went to the lock screen, with the default background (it looked like my data was all wiped). After unlocking the screen, I got a perpetual series of force close messages. This happened each time. I had to do a factory reset and lost all my settings, photos, messages and everything (No backups, of course. Facepalm). Then today I pretty much had it back to the way it was before the reset, and Browser force closes repeatedly on opening. I restart the phone again and this time it only gets to the 'S' animation then goes black/restarts after the animation stops. The capacitive buttons sometimes light up. Similar to the issues from the Froyo update I think, except I didn't update to Froyo. I can get to the 3-button recovery screen and do system reset as well which seems to not help the froyo issue, I think. It's currently working but I'm not sure how long that will last. I'm not pleased about having a phone I have to re-setup every few days. (I'm actually pretty angry...)
Anyway, I have a "Mobile Device Repair and Return Receipt" from the seller from craigslist. It's still under warranty. Anybody else experience this? Can I take it to bell and have it fixed with the documentation I have? What would you suggest I do here?
Hi,
I am using an un-rooted Nexus One phone with Froyo (2.2.1).
The camera has stopped working unexpectedly.
Whenever I start the camera app, it gives me the error:
"Activity Camers (in application Camera) is not working"
It gives me the option to wait, force close or report.
If I select wait, it just hangs in there and pops the above msg again.
If I force close the app, and try to start it again, I get the error:
"Cannot connect to camera"
The phone did not fall down and is always handled properly.
This happened all of a sudden.
The last thing I did with the phone was to copy songs to the SD card.
I have factory reset the phone twice and formatted SD card, even swapped SD cards, but no luck yet.
I am based in India, the phone was bought in the US, I have no warranty.
Any help will be appreciated.
Thanks.
Sorry but I think your camera just died it is possible for the camera to die without any physical abuse but it is uncommon. The only other thing I can recommend would be to root and install a custom ROM (or at least a kernel) and see what happens but I don't think it will fix it.
Resolved....
Thanks Dude Random21..!!
Actually, I just resolved the issue about 30 mins ago.. Was downloading the apps and restoring its state as it was before I had factory reset it.
Well, after doing everything related to software to fix the issue, I concluded that it might be a hardware issue.
So, I started to search for threads involving camera hardware issues.
I took hints from the following post:
Google "Camera on my Nexus One not working - no flash either...all apps that use camera also not working - Help!?!?! " and you will be lucky..
(I cannot post links as I am a newbie)
Saw all videos on youtube about nexus teardown and just finished doing it.
I checked all the connections/internal wiring on the phone and once done, rebooted the phone and it worked..
Unfortunately my phone received a couple of scratches along the way, so others should be more careful about it.
Thanks for your help.
--- sent from my nexus one
No problem, I do what I can to help out. And good for you for having the guts to fix your nexus one's hardware cause I'm pretty sure that if I had an issue like that I would't have the guts to tear it down myself even with ifixit.
Remove (renaming is better) the DCIM directory from SDCARD. It is probably a corrupted (or incompatible with 2.3) file. After that, the camera cames back to life, then you can copy your “Camera” directory to the new DCIM directory created by your phone.
HTH
Hey all, searched the forum but 0 results for "Camera Failed"
So about a month ago I went swimming in the community pool with my S10. I went swimming and water park with my S8 and S9 never any issues. This time maybe I stayed in too long, haha.
So the next morning I did notice moisture on the front and rear cameras! Doh! Fired up the camera only to get "camera failed". No biggie, I have premium protection with TMo which does cover this ($99 deductible). I went to make a claim and there was an issue with the warranty not being added on my account, but TMo takes care of it's customers and added it for me and started to process the claim. A few days later the moisture disappeared, and then a few days after that the camera was resurrected!
My replacement didn't show up so when I logged in the rep said for whatever reason it didn't go through, but we were able to cancel the claim. Back in business!
Fast forward to 2 days ago when TMo pushed an update to the phone. I updated with the latest software and immediately noticed I'm back to "Camera failed". I have tried the basics like clearing cache, clearing app cache, booting into recovery to clear the cache, and in safe mode. Still no go.
The kicker is (and this was also apparent during the first failure) the camera app shows failed, and all apps that use the camera also throw an error about accessing the camera EXCEPT the Poshmark fashion marketplace app. It access the camera no issues, front and back! I also uninstalled Poshmark, cleared cache, and rebooted without success.
So I was wondering if anyone had any ideas before I try a factory reset because it takes a while to restore a lot of my settings and customization. And if that doesn't work I'll wait a few days and see if it comes back to life like last time and if it doesn't, file a warranty claim.
Thanks
I think I'd still do a reset and try the camera without restoring anything. If it fails then, you've already done the reset for the return. If it works still don't restore anything, live with it a few hours and keep trying different settings with both front and rear cameras. If you can't make it break, then do your restore. I know a restore is tough to do sometimes, but I hate those nagging problems you can't put a finger on.
Tel864 said:
I think I'd still do a reset and try the camera without restoring anything. If it fails then, you've already done the reset for the return. If it works still don't restore anything, live with it a few hours and keep trying different settings with both front and rear cameras. If you can't make it break, then do your restore. I know a restore is tough to do sometimes, but I hate those nagging problems you can't put a finger on.
Click to expand...
Click to collapse
Yeah I know there isn't a lot of options left at this point. But it's weird that the poshmark app has no problems accessing the camera when everything else does, and that after the TMO update it killed my camera again.
Thank you
Similar problem
Nurmi_CEO said:
Yeah I know there isn't a lot of options left at this point. But it's weird that the poshmark app has no problems accessing the camera when everything else does, and that after the TMO update it killed my camera again.
Thank you
Click to expand...
Click to collapse
Well I had the same problem on my s10, however it was being used in heavy rains and the next morning there was moisture in both the front &back cameras.
However it was still taking pictures (full of blur), no it wasn't showing any camera failed error. I took it to the service centre where they had the phone disassembled and heated up the camera module. The phone is working fine ever since, I recently got the June update (India) and my phone's camera is still working properly. Do try a factory reset and let me know as we whatever happens
Nurmi_CEO said:
Yeah I know there isn't a lot of options left at this point. But it's weird that the poshmark app has no problems accessing the camera when everything else does, and that after the TMO update it killed my camera again.
Thank you
Click to expand...
Click to collapse
T-Mobile should push another update with camera night mode, QR code and so on. At least we(people in US) are waiting for it! See if the upcoming update fixes the issue. Don't you use Samsung back up? It is built-in to your phone. I always use it and it saved placement of your home screen shortcuts, settings(most of them), your apps and other stuff.
pma1504 said:
Well I had the same problem on my s10, however it was being used in heavy rains and the next morning there was moisture in both the front &back cameras.
However it was still taking pictures (full of blur), no it wasn't showing any camera failed error. I took it to the service centre where they had the phone disassembled and heated up the camera module. The phone is working fine ever since, I recently got the June update (India) and my phone's camera is still working properly. Do try a factory reset and let me know as we whatever happens
Click to expand...
Click to collapse
I will and see what happens. Thanks!
Charkatak said:
T-Mobile should push another update with camera night mode, QR code and so on. At least we(people in US) are waiting for it! See if the upcoming update fixes the issue. Don't you use Samsung back up? It is built-in to your phone. I always use it and it saved placement of your home screen shortcuts, settings(most of them), your apps and other stuff.
Click to expand...
Click to collapse
Ok I will do a factory reset and see what happens and checkout Samsung backup. Thanks
pma1504 said:
Well I had the same problem on my s10, however it was being used in heavy rains and the next morning there was moisture in both the front &back cameras.
However it was still taking pictures (full of blur), no it wasn't showing any camera failed error. I took it to the service centre where they had the phone disassembled and heated up the camera module. The phone is working fine ever since, I recently got the June update (India) and my phone's camera is still working properly. Do try a factory reset and let me know as we whatever happens
Click to expand...
Click to collapse
No go on the reset. Same thing. Camera failed on every app except Poshmark.
I'm going to ride it out this week and if it's still dead by Sunday I'll file an insurance claim
I'm hoping it does start working, now even I'm worried about updates breaking my camera (I got no insurance on this). Still I don't understand why the camera failed popup came on your device in the first place ( even if it had moisture) because even I had gotten the camera full of fog however it was still working properly (I took it to the service centre In a day though). I'm attaching the most recent update that I received, this water damage thingy actually happened on the 12th of June
Hello, i had the Same issue after the May Update. I tried evertyhing Clearing Cache Reset Phone....
I went to an samsung store they changed my front camera as warrenty case so i paid nothing. Till today no problems, camera works fine again.
Nurmi_CEO said:
No go on the reset. Same thing. Camera failed on every app except Poshmark.
I'm going to ride it out this week and if it's still dead by Sunday I'll file an insurance claim
Click to expand...
Click to collapse
I have trouble wrapping my head around it working with Poshmark only. Outside of reflashing the rom I can't see anything else to try, yet it does point to a software and not a hardware problem.
Tel864 said:
I have trouble wrapping my head around it working with Poshmark only. Outside of reflashing the rom I can't see anything else to try, yet it does point to a software and not a hardware problem.
Click to expand...
Click to collapse
When I did a reset on the phone, I held the volume up + bixby to boot into the bootloader and selected "wipe data/factory reset".
It's been a while since I have been rooting and modding my phones since the S8 and up Snapdragons were non rootable for the longest time. Would it be a "cleaner fresher reset" if I used Odin to flash the stock firmware? Is Odin still a thing anymore with the newest Galaxies?
Nurmi_CEO said:
When I did a reset on the phone, I held the volume up + bixby to boot into the bootloader and selected "wipe data/factory reset".
It's been a while since I have been rooting and modding my phones since the S8 and up Snapdragons were non rootable for the longest time. Would it be a "cleaner fresher reset" if I used Odin to flash the stock firmware? Is Odin still a thing anymore with the newest Galaxies?
Click to expand...
Click to collapse
Yeah you're right Odin still works with modern Samsung phones (it did with my old j7 prime-exynos android 8.1). You can try reflashing the stock firmware and maybe downgrading it if that's possible. Honestly Samsung devices have become a disappointment now to me