My att note 5 is out of warranty. I sent it to samsung for repair. They said the software failed. This happened after my last update. This also happened last august and samsung repaired it for free. The want to charge me $170 to fix it this time. They explained parts need to be replaced including the screen. I had no issues with the screen.
It stopped fast charging, it would autoload google vr app, self reboot, load a recovery screen on its own. I thought it was a broken usb plug on the phone when this happened last year, but samsung confirmed that it was a software issue.
How can I fix it myself? A hard reset did not clear any of the issues.
Official tool: https://www.samsung.com/us/smart-switch/
Semi Pro tool: https://odindownload.com/
Related
Ok so this s6 i have had for less then 1 month is becoming a huge hassle. First it kept restarting by itself even during bootup. Sent in for repair samsung said nothing was wrng with it and sent it back... Got it back first startup it rebooted... Then after uaing it to 2% i charged it up and booted the phone, got a message "unauthorized att softwsre detected". Went to att they tried to reflash didnt help, told me to go to bestbuy samsung kiosk, they tried to reflash nothing... Told to call samsung and they would fix it, sent it in and they said thwy cant do anything cause its rooted. What can i do? And how did this even happen.
Did you buy it new, or used?
Brand new was orderd from att direct.
I actually have a video of the system saying it was custom then after i rebooted it went back to offical.
Actually starting to think samsung repair rooted the phone cause they couldnt repair it...
I'd contact Samsung again, explain the situation, and see if they'll replace it.
Tried they said cause its rooted they can't even touch it and since its rooted it voids the warranty and any connection to them... like WTF? My friend is on the phone with some manager at samsung right now :/. But my hopes are low. How does a company like this have such retarded policies. They can't even check the phone if its actually rooted...(they said they can't touch it cause the knox counter was tripped) I assume the binary somehow got messed up, hardware related? I bet if they just checked the software it would be official with chunks of code missing or something. I have video proof of it going from custom to official by itself without me having it plugged into anything. I have no clue who i can go to about this issue anymore, Phone is brand new (one month) and im still paying for it under ATT Next program...
Have AT&T check the serial and imei of the phone against your original order. Perhaps you got sent back the wrong phone from the repair depot? AoN
I checked the serial once i recieved it, it was the correct phone. I have video proof of it "rooting" it self. Basically the phone said it was custom then it a d it was offical after i rebooted it.(of course this was taken in two videos but u can see the time so no tampering could have occured.)
https://m.youtube.com/watch?v=WpxGI644OXA
https://m.youtube.com/watch?v=XJva5kmFLjE
So i figured out why it says i have a custom software... The BestBuy Samsung Rep flashed the wrong build to my device. They flashed "G925AUCU1AOE2" which i don't think is released yet or at least not pushed to my device. So any suggestions to what i can do? They cased my warranty to be voided and i still have the restarting issues.
I am having a boot loop issue. I have T-Mobile G4 that is NOT rooted. I bought it on release day. I too would get random reboots, particularly after the recent security update. I also noticed that the operating temperature was really high, a lot lately. I thought it was a rogue app (clean master). Anyway, I updated a few apps and installed a few watch faces. Suddenly, my phone was drained prematurely. Plugged it into a quick charge charger when all the fun begins. Early on it would boot to the home screen but would reboot a minute or two later. Then it stopped booting to home. On two occasions that I caught, it was starting up like a firmware update just installed with the "Android is starting 1 of 143 apps" type of line. After seeing that and still not getting to home, I figured I might as well factory reset it. Well I was amazed to discover that a factory reset yields the same boot loop. All I get is the LG logo.
Defeated. I go to my local TMo retailer where I bought the phone only to find out that I have to wait for delivery of a replacement( I smell refurb). I'm in Jump btw. I did notice that when the phone will boot to home screen for whatever length of time, the LED would work. The LED does not work during a boot loop. My research on this issue uncovered an alarming trend on the Internet. No solutions other than replacement. No cause has been identified either. Without proof, these are my top suspicions: Quick charge, 128G SD, apps moved to SD. My hunch is quick charge. All of my chargers are Qualcomm certified quick chargers. and I use them 95% of the time. I would hate to add LG to my list of boycotted Android vendors under Samsung.
Things I tried:
Recovery mode
Download mode
No SIM, Battery and/or SD
Swapping batteries
Safe mode (once)
This happened to me yesterday. I was listening to music through the bluetooth at the gym and it stopped playing. When I walked over to the phone it was already in a boot loop.
Reflashing does nothing nor does a factory reset. They are sending me a new one as well.
Funny thing is once it did make itself passed the boot screen to: "updating apps" This smells like an update is bricking phones. I went to the store and the agent said he couldn't find any data on a recent update but I think he wasn't looking at the right place. If there's an update bricking phones I will be livid. I'm 40 days away from a Jump upgrade and they said I can't exchange it early anyway because it "has to be in working condition." Well no ****, YOU can do the warranty replacement...give me a new phone! I too abandoned Samsung after the Lollipop Note Edge upgrade made the phone discharge in 3 hours or less and run as smooth as gravel. LG has suddenly made me sour too.
Same exact issue as you described.
Also tried everything you did. I went with TMO's replacement, and to my surprise, it was a new phone rather than a refurb.
Hello,
I highly doubt that it is caused by Magisk because of the history of the device, but I would rather be sure by asking to some advanced users
So, I have a Samsung Galaxy S4.
3 or 4 years ago, I installed LineageOS 14.1 (Android 7.0) on it with TRWP, and I rooted using the files provided by LineageOS when they still did it. It worked fine despite one crash/reboot every month.
Somewhere in 2020, overnight (I really mean it), it became a bit more erratic. When I plugged it to recharge the battery, my S4 started up the screen as usual, but didn't shut down it anymore so I had to do it manually, and I got probably 3 or 4 crashs/reboots a month. I thought about a software issue as this is LineageOS and it can be unstable. Still, as it wasn't that big of an annoyance, I used it this way until the last few weeks.
Because yes, few days ago, I decided to upgrade it to LineageOS 17.1 + MicroG. I rooted it using Magisk, following the procedure for that.
But it became way worse than before. It rebooted maybe 15 times in 3 days even by doing nothing special. At some point, the SD card crashed and I had to format it. I got a new battery because I thought it may be the culprit but it didn't change anything.
Then, at the end of the week the device refused to boot anymore.
I cannot start it using the Power button. I have to remove/replace the battery and it will start by itself... two seconds, just the time to show the S4 logo.
If I plug the device to my computer just before replacing the battery, it doesn't even react. Can't start it, no image, no vibration, nothing.
I tried to start TRWP but to no avail. I can start the DOWNLOAD mode but the screen shut down within seconds. If I plug it shortly after replacing the battery while starting said mode, ODIN doesn't see the device.
In short, it is dead.
Ok, I accept that, I knew the risks. But in your opinion, is it dead because Magisk, or because of a hardware issue ?
Hardware issue 100%. Software can't kill hardware like than. Atleast Odin mode should be stable
Ayan Chakraborty said:
Hardware issue 100%. Software can't kill hardware like than. Atleast Odin mode should be stable
Click to expand...
Click to collapse
I agree, it should be that.
Well, I still had the previous unit but with a broken screen... so I transferred the previous motherboard to replace the defective one. The unit is working fine again.
The defective motherboard will go to the nearest electronic waste center.
Thanks for your help.
So The redmi note 10 pro atleast in India( redmi support has admitted to it) had this front camera issue where after the MIUI 13.0.5 update cameras had stopped working, also my Snapchat and instgram camera parts totally died. This was annoying but I was just going with it because I don't have the time to go to the repair shop for the "free fix".
Now yesterday I was just doing my thing using my phone browsing something when the app I was using ( think it was Gmail) crashed so i restarted the app and then it kept being extremely slow and finally the phone just died like froze and that system UI crashed thing was being shown but I couldnt do anyhting on the screen so I just held my power button expecting it to restart.
Now the issue began, the phone refused to boot up, after the original MI logo and a run of the theme's boot up animation it would freeze and the whole thing would happen again. It kept happening for a long time so then I went into safe mode, dad deleted all apps he thought are unsafe (they aren't mostly) and then rebooted but it wouldn't start so he said factory reset it. I went ahead and took whatever back up I could on safe mode and did that but now the phone would just boot into "system UI crashed" and be unresponsive.
I'm not sure at this point if I could boot in safe mode but i had given up and it was on another bootloop when I just removed the sim to out it into this trash phone and I did but after like 5 minutes I have no clue how it just booted into setup like a first day phone. Went ahead and set it up even rebooted to see if it's flawless and it was fine. Guess what even after all that the camera issues were still there. Today morning the phone was acting a little up but I didn't give it much thought. School got over boot it up and it wouldn't boot up again, went into safe mode and rebooted somehow that worked, reached home and voila using an app and this time it decides to reboot on its own and again back to zero.
I was so fed up and this is where first paragraph comes in I assumed this is all because this 13.0.5 is absolutely garbage for my phone and I should go back to another version of MIUI so I started watching videos on that.
Downloaded mi unlocked tool, pretty sure i did the OEM unlocking thing and mi account thing( i did all this in safemode because normal wouldn't boot) and went into fastboot but it wouldn't show up in the unlocker app. Thought I did something wrong tried again and failed again. But now it decided to not even open in safemode and then I gave up. My dad did something and wiped data and when it boots up now it just says device is locked in an unresponsive state where I can't type in the pass word (obviously because system UI has crashed) and it won't stop booting into this same screen. I can't enter safemode now but I'm not sure about fastboot. Please help I'm new here and I'm sorry for the extremely long post. If there are other places I can post and get help please tell.
To me my friend you sound like youre in a spot, I think personally, youre best solution is a service centre repair, warranty or not, sounds like you have some major issues there that are beyond simply flashing, and the more you mess the worse it gets. If it is a new phone i would be returning it for repair or replacement, if Xiaomi have admitted to camera problems then they should be liable for repairing the phones that suffer with this problem, you need to contact them to find out what you are entitled to.
gazza35 said:
To me my friend you sound like youre in a spot, I think personally, youre best solution is a service centre repair, warranty or not, sounds like you have some major issues there that are beyond simply flashing, and the more you mess the worse it gets. If it is a new phone i would be returning it for repair or replacement, if Xiaomi have admitted to camera problems then they should be liable for repairing the phones that suffer with this problem, you need to contact them to find out what you are entitled to.
Click to expand...
Click to collapse
Hmm so just I'll let it be until I can visit a service center
Nwing said:
Hmm so just I'll let it be until I can visit a service center
Click to expand...
Click to collapse
Xiaomi India offers free repairs for Redmi Note 10 Pro/Max camera issues after MIUI 13 update - Gizmochina
Xiaomi India has acknowledged that the latest MIUI update of the Redmi Note 10 and Redmi Note 10 Pro Max may have led to the frequent camera crashes that have been reported by users. Several users of the two smartphones had reported their cameras crashing whenever it was opened. Other users had...
www.gizmochina.com
Got up this morning to a black screen. At first power + down volume would show the Samsung boot screen, but it would never fully boot. One time it did make it to the the home screen but froze almost immediately. After that it has only showed the Samsung boot screen a few times while holding down power + down volume. I have tried tried power + down volume or up volume several times now and can never get it to show anything any more. The phone should also have power as it has been charging all day. After doing some reading I was going to flash it with Odin, but it only shows up as QUSB_BULK_CID... and Odin doesn't see it. This is after installing Samsung USB drivers v1.7.59. Is there anything else I can do?
hello colleague
Reading this post makes me think about making periodic backups.
since I also have an S20 FE 5g TMO.
I hope I have a solution to the problem.
but apparently I think it will be hardware problems.
I have investigated and there is also a publication of an s20 with the same problem.
greetings
Can you point me to the S20 with the same problem? I really hope it isn't a design issue with the hardware as I have 3 other S20FE's. All bought at the same time. The phones are only a few months past 1yr old. Would be nice if it is a software issue. Since I couldn't figure anything out with it, I dropped it off at a replace called ubreakifix by asurion. They were listed as a repair center on Samsung's website.
I got the phone back today. At first the shop said they couldn't reproduce the problem after I left it there. It was just slow to start up. Gave it back and didn't charge me anything. After I left I just started open and closing stuff. And the UI would freeze some, plus I would get System UI not responding and Process system isn't responding errors. I took it right back with the error. They were able to scan it again. This time there Samsung software said it had corrupt memory. They said the board would need to be replaced and that would cost what a new phone would cost. So, I just ordered a refurb S20FE from Back Market. I am still going to try and wipe and flash it. But, I don't know if I trust it now.
Just looked in the software update menu and noticed it updated the system on 2/7 at 12:10pm. The phone had the black screen on the morning uf 2/8. The alarm didn't go off at 6:00AM. So, it started acting up less than a day after the update. Coincidence?