I set it to auto update at 3AM, instead it started to update at 3PM @20% battery, I was not able to stop it in time and it tried to update, entered bootloop forever, left it charging for 2 days, nothing still looping.
Tried flashing firmware with odin, flashes successfully but tried turning on-get bootloop, again.
Can go into recovery, can go into download, can’t do anything else.
Can I get data back in any way?
I heard chip-off recovery is not an option anymore since they are encrypted.
SM-G965F/DS THA
SM-G965FZBHTHL
Thank you!
If you can't get past the bootloader without formatting the phone, chances are you can't do any other way. Anyway there are the copies of the samsung cloud, drive, etc.
any joy? same issue and samsung wont honour my warranty as run out 2 days ago
Related
Hello. I have a Sprint M9. It had been acting flaking lately (I would try to install the latest update, and it would reboot without installing and report that the phone had recovered from an error and ask if I wanted to send to HTC). Tonight, I was trying to use DLNA to play video from my phone to my TV, I was in settings and gave DLNA permission to access my storage. As soon as I did that the phone rebooted without warning and continues in a loop of displaying the HTC logo, then restarting over and over.
I can get into bootloader, download, and recovery mode by holding down the volume down key. I have tried Wipe Cache Partition and Wipe Data, but the phone still will not get out of the loop.
Phone is stock. I have never tried to root or disable S-on or load my own recovery.
What, if anything, can I do to get my phone working again?
Just tried doing what I think is called RUU? I downloaded the .exe from this site:
http://www.htc.com/us/support/htc-one-m9-sprint/news/
It found my phone, and rebooted into download mode. It tried to flash my rom, but shortly after trying to send the file (progress bar jumped from 0% to 100% in 1/2 second). The utility gives me a Error [155]: Unknown Error. I've tried a couple times and get the same problem each time.
The utility reports I have version 3.41.651.21 and tries to flash to 3.41.651.31
Great, now it is telling me my software has been modified. (it hasn't) The only things I've done is run the RUU and reboot into recover to clear cache/data. Bad NAND?
Well, found out why RUU wouldn't work. Low battery. Apparently it ate a lot more battery than I realized while it was in the reboot cycle. Tried manually flashing the firmware and fastboot told me the reason it was failing. C'mon HTC, if the CLI can tell me there's not enough battery to proceed, your GUI utility should be able to as well.
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
shawndoc said:
Still leads to the question of:
- Why did this happen in the first place
- This is actually the second time I've had a problem with OTA, with the phone thinking the system had been modified. So either the OTA failing somehow modified the system before failing, or there's a bigger issue afoot. (as noted above, this phone is stock, I've never tried to root, install a custom recovery, or anything else)
Click to expand...
Click to collapse
Same thing happened to me. The update that Sprint pushed last Wednesday completely bricked my HTC One M9. Same failure mode that you experienced. Sprint technical center was unable to do anything with it, so they are replacing it, allegedly ( been waiting a week for said replacement ).
I talked to a few other people who had the same problem, by the way. Someone in Sprint's QA team completely dropped the ball on this update.
Well, even after RUU it says my system has been modified and the phone will no longer boot into recovery. Just errors back to Download with the message that recovery couldn't launch.
I've also now got intermittent problems with the com.android.settings crashing. So I've thrown in the towel and purchased my first non HTC phone since the original Windows Mobile days.
Hello there. The same problem has come to my mind and the phone has been off for almost a month. Did you solve your problem? If you could solve it, how did you do it? I sent you above the original stock rom set. Nothing changed. The phone developer rum works. but the original 0pja200 rom is starting again.
my phone soft bricked, unlocked bootloader and S-off. Whether it is possible without blocking bootloader flashed RUU rom?
Hey guys, not sure if there was another thread with this issue but I couldn't find it.
Yesterday at work my phone suddenly froze and then restarted into a bootloop and this is what I did:
I pulled the battery out for a good 10 minutes and tried it back again and it was the same thing again with the bootloop.
I tried to put it in Safe Mode and it started up and then after awhile it froze again and jumped back into the bootloop and wouldn't go back into Safe Mode again.
This time I tried clearing the cache and that didn't work.
Next thing I tried was to Factory Data Reset the phone and it came up after that where I had to go through the whole setup wizard and everything like it was a new phone again. But not long after the phone was running fine it started restarting every couple minutes or if I go in What's App or something else.
I figured that something is wrong with the system itself so I downloaded the 22A update for the VS990 on my laptop (where the version 11B was currently on the phone) to try and update it and honestly that was a bad move because when I tried to flash VIA LGUP, the phone restarted during the process and now I'm getting this on at the top left corner of the logo screen then it reboots continously:
Boot verification failed!!
- cause: MISMATCH_SIG_LEN
Can anyone please help me out, love this phone so much and not looking to get a new one or change it anytime soon :crying::crying:
Are you in warranty or have insurance with extended warranty? Sounds like you'll have to contact VZW and get a replacement. Hopefully you're covered.
Sent from my VS990 using Tapatalk
I'm really not sure as I bought the phone 2nd hand from Ebay, bought it in August so probably., so would have to contact the original owner and see what he has to say. Sigh only if I could get it to stay on the logo screen at least without restarting I could try flashing it again.
Hello all, got a bit of a strange issue here. So I was using the 30b release from runningnak3d, https://forum.xda-developers.com/tmobile-lg-v10/development/h901-t-mobile-nougat-v30b-twrp-t3639203
I was selling my v10, so I did a reset, skipped or hit next to everything, and verified that all was working. I sold the phone and a couple days after the buyer got it, he told me it was bootlooping. I asked what he did and of course the first time he said nothing, just turned it on. After more conversation, he said when he got it it booted and after a while told him an upgrade was available. He said he accepted the upgrade, and afterwards got the bootloop.
I got the phone back today to try to fix it and give it back to him. Here's what I have found. Definitely bootlooping, stops at T-Mobile logo and reboots. It does still have the unlocked bootloader, still shows the warning right at boot. TWRP is gone! I booted to recovery, answered Yes to those 2 questions, and it did a reset instead of loading TWRP.
I really have no idea what he did, whether is was an OTA update or maybe he tried to load something on his own.
So, is there any hope of getting this thing going again? So far I was able to boot it into download mode, but it won't respond to any fastboot commands. My computer detects it, but in computer management it says LGE USB modem or something like that. When I try to regular boot, the computer does detect the phone, but it doesn't get far enough along to issue ADB commands. I'm thinking it's a paperweight at this point, so I'm game to try whatever.
So I've reached out to this forum as I've tried a million and one things but can't seem to get my phone to boot.
Here's the situation:
I fell asleep watching a video on my phone and my phone died. I plugged it into the charger and it wouldn't boot, would just endlessly be stuck in a boot loop. Looked it up and saw this is a common issue. Went through the standard fixes:
Wiped the cache
Factory reset the phone.
Attempted to boot in safe mode. (Wouldn't work, still boot looped)
After all this failed I thought I would just flash it using Odin v3.14. T-Mobile is my carrier and I'm based in the US so I used this firmware: SM-N950U TMB, LINK(https://updato.com/download-samsung...sa/sm-n950u/B094B9DAF04A11EAB4A2FA163EE8F90B/)
It still didn't work after this. It booted up and the startup process began asking me to agree to the terms and conditions. Before even getting to agree, the phone crashed. I tried this again and it just kept failing and crashing. I did this all while plugged into a charger. What I did begin to notice is that the phone would get hot on the left side, where the battery sits. I'm not sure if this is related to the crash or just the fact that its been discharging and charging a lot while I troubleshoot it. I have tried different firmware as well just in case I had the wrong one, but nothing has been working. When I update the firmware I used the CSC file and not the HOME_CSC and I also use the USERDATA file since at this point I kind of accepted I'm not getting my pictures and files back and I'm just trying to get the phone to work once again, thus just trying to factory restore it. Also, when the phone does start booting it says optimizing apps on the bottom each time I boot it I feel this number is changing. I'm not sure what else to do or if anyone has any suggestions? Thank you in advance
IDK if this is the correct area for this, but Imma try here anyways. My friend upgraded his old S8 to the S21 5G about 2-3 months ago and has been having problems since a Samsung firmware update said his device had an error that needed to be repaired and had pronmpted min to check for an update, which it apparently found, and he had attempted to download and install it while he slept. Well, he woke up to find that his phone was now on the Odin screen for some reason. He took it to a T-Mobile tech center and they were able to get past the Odin screen by doing a Soft-Reset (Power+Vol Down, then Power=Vol Up after the device shut off) and it had worked for about a month. Queue the current issue... He's right back where he started, supposed device error, update found, attempted download and install while he slept, and waking up to the Odin screen. Only this time, doing a Soft-Reset does nothing. We've tried multiple tech centers and they all say the only solution is a full firmware reinstall, or to send the device in to be serviced, either way, that's the cause of the next issue. He has never used a Cloud service of any kind to back up anything on his device, and in doing a reset or service, he'll lose everything on his device, which includes numbers of recent friends and co-workers, photos that had been transfered from his old S8 to the internal storage since the S21 doesnt have Sd/Tf support, and a ton of other important infot hat he can't just lose in the process. Is there anyway to figure out how to potentially install a firmware w/o losing all the internal storage or some off-device program that could remove them. I have tried many different programs that say they can do what we're trying to do, but none have worked or have been up-to-date enough to even support the S21. I'll attach a couple files to show what I recorded of the kernel and the boot screen issue from my phone of his phone.