T-Mobile S8+ [G955U] -- Factory reset resulted in complete wipe & no longer boots up.
I have a Samsung galaxy S8 plus (T-Mobile) [SM-G955U]
Current Firmware:
G955USQU4CRE9
I'm using windows 7 to attempt to repair my phone.
My problem is as follows...
A few weeks ago my phone started giving me the dreaded:
"Unauthorized actions have been detected..."
error code and sending my phone to restart.
This has happened to me in the past on other phones so i thought, ok. restart and it should be fine. However, this kept happening... the next day and on the 3rd day it happened about 3 times in a row. At this point I was cautious and backed up all my files, turned on USB debugging and shut off my wifi & data.
I then proceeded to do a factory reset from the settings. Once it restarted I got a weird error stating something like no such recovery file could be found. When I saw this I knew I messed up because I didn't first take a backup of my system & recovery...
I got a hold of T-Mobile who walked me through their reset steps, none of which worked. They had me contact Samsung and I did but to no avail. Simply stated they mentioned they could fix it if I had warranty, if not I would have to pay for repair.
Either way I sent all information to Samsung and they have not gotten back to me even though they mentioned we'd hear back in 48 hours. (it's been about a week) I've tried to reach out since then but I haven't had a lot of time to sit on the phone with their elevator music...
Ever since then I've tried everything from Samsung Smart Switch to re-flashing through Odin with no luck.
I've tried all of the reset options...
Hard reset
Soft reset
Wipe cache (recovery mode)
Wipe and factory reset (recovery mode)
Simulated battery pull
etc., etc., etc.
Nothing works. Odin flashes correctly (i get "PASS") and the phone turns off but does not turn back on.
I've tried several tricks to get it to turn back on but it won't go past the boot screen (Samsung Galaxy S8+ screen)
I've flashed, re-flashed, wiped, reset, etc.
Now smartswitch doesn't even work on it because it does not recognize the device...
When i connect my phone now it just shows up as the qualcomm chip. I get "Qualcomm HS-USB QDLoader 9008" under devices...
ADB only works when it's in download mode or recovery mode but it doesn't recognize the device either...
Another problem is the increased time it takes to get into the boot menus (download or recovery).
Sometimes when I haven't touched my phone for a whole day I can get into download mode within 10 seconds or less but the more I try it and especially if I successfully flash stock software, the next time booting into recovery or download mode can take up to 5 minutes (holding the button combination). Recovery mode is worse.. even after 24 hours without touching the phone it will come up maybe in 3 minutes but has taken as long as 7 minutes... my fingers are in pain.
Essentially, even after successfully flashing my phone will not boot. and when i hold vol_down + power i can sometimes get the boot screen but it won't go past that.
Also, None of the above boot options work if my phone isn't connected to power--these options only work when it's plugged in. If my phone is not plugged in it will not vibrate, light up, boot up, or do anything other than behave as a paperweight.
I believed it may have been a charging issue so i left it plugged in overnight and even went to download mode and plugged it in for a few hours but that doesn't affect it at all. Even if i'm in download or recovery mode it'll turn off right when i unplug the device.
I'm trying to get it to the best buy that's approved for samsung repair but when I called they said they wouldn't repair it anyways because i didn't buy it there... -_-
Please let me know if I need to provide any other information. I'm trying to get an image of the recovery screen so you can see the error it gives me... Something about no file found. This is increasingly difficult though because some times it takes too long to get into these modes and I leave it alone and come back to it later.
Has this happened to anyone else? Can someone provide some sort of advice or a method to fix this?
thanks in advance.
Can you download the Qualcomm HS-USB QDLoader 9008 driver, and then see if you can fastboot oem-unlock and see if it unlocks your bootloader
Related
Hi all, I've been using XDA for years since the original O2 XDA's and I have never had to post anything as I've always found my solution. I'm hoping somebody can assist me with a problem I have on this stock galaxy tab 3.
The device was brought to me after being thrown down the stairs. I replaced the screen and built it back up,
Removed battery connector and reconnected = nothing happens
Press power = nothing happens
press download mode = nothing happens
press recovery mode = nothing happens
Plug USB into PC = nothing happens on PC or tablet
Plug in USB mains charger and it displays battery charging logo but it doesn't fill or animate the fill then it starts the samsung boot screen. It reboots and continues to do this constantly and never ends.
I've tried two batteries and both batteries work in another tab 3 but neither batteries changed how the device works.
Thank you for any advice in advanced!!
I just received a Tab 3 lite (SM-T110) for repair, it's having a similar problem.
It does automatically turn on when plugged into charger or computer.. It is stuck on a bootloop, requiesting a Kies recovery. It does reboot when given the three finger salute (center button, volume down, and power) - it will not enter recovery mode though - same firmware error message). The device is also full off or full on, no indication of it's it's recharging or no - let the battery run out, it's off - else it's on (does not turn on or off with power button). I don't have any info how it got into this state - most likely power loss during a firmware update, but haven't ruled out other possibilities (ie bad rooting job, a custom ROM upgrade went wrong, etc). I'm not 100% concerned about cause, but hopefully I can unbrick the thing.
Anyways, I loaded Kies onto my computer and put it into recovery mode and plugged it in - nothing. Exit the recovery mode of Kies, and all of a sudden the program goes nuts trying to connect and disconnect from the device. Hmm... Okay, disconnect it, uninstall Kies, install Kies3 and try again - same thing except it complains the device is too old when the program leaves recovery mode - but same thing otherwise - does not show up in recovery mode, connects and disconnects at huge rate when not in recovery mode....
Hmmm...
Now looking at the screen, it does indicate (in the upper left hand corner) that it's in ODIN mode... So my next step I figure I'll try ODIN (although I'm researching ODIN at the moment as I haven't used it before (never had to unbrick anything from Samsung prior to now).
Okay, that was painless - downloaded and installed ODIN 3.10.7, and then downloaded the latest firmware from Samsung, extracted the firmware, added it to ODIN's AP line, then hit start to push the latest firmware onto the tablet. Good as new again.
So, the other day my phone started acting weird. It randomly restarted, then worked another hour or so, and then started shutting down almost immediately after booting. I was running a Nexus 5X with rooted stock Android 7.0.0 (SuperSU root) and ElementalX kernel. It had been running this for a few months without any issues. I can't think of anything I did to trigger this. I didn't run any updates, I haven't flashed anything since I installed ElementalX couple months ago.
After a lot of troubleshooting (at first I could still get into the bootloader and recovery, but when I did, TWRP didn't recognize any partitions? I was unable to access the file system in TWRP), it finally got so bad that my phone is no longer recognized by my laptop other than "QHSUSB_BULK" device in the Device Manager (Windows 10 x64). Completely black screen, no response, no LED when plugging in adapter. One time I managed to get into the bootloader (randomly, no idea what triggered it) and I managed to put stock 7.1.1 on it, but soon after the installation of that, the exact same thing happened: random reboots, progressively getting worse to in the end: no recovery, no bootloader, only recognized as "QHSUSB_BULK". So I was back to the lowest point.
I read about a "hidden second bootloader" on the 5X, that would be accessable through Power+Both Volume keys, but that doesn't work at all for me (tried it for up to 1 minute of pressing).
After hours of searching (I probably read all the 5X + other phones's topics here that have this issue..), I came here: www.droidsavvy.com/unbrick-qualcomm-mobiles/
I followed those steps precisely, got my laptop to recognize the phone as 'Qualcomm HS-USB QDLoader 9008' by installing the Qualcomm drivers with driver signature verification turned off, but I just couldn't get the QFIL program to flash anything to my phone. It threw a "Download Fail:Sahara FailSahara Fail" saying it couldn't send the Flashing program to my phone. I tried several things here: attempted to power off the phone, then hold Volume up+plug in USB --> flash straight away, different driver/software versions, different laptop, but all to no avail.
I have no real way of telling whether the phone is on or off (it seems impossible to actually turn it off - if I hold power for 30 or so secs I do hear the USB disconnect-connect sound from my laptop, but the device is still shown as "QHSUSB_BULK" so it won't actually turn off properly).
My current hypothesis: it's a hardware fault (eMMC?) and as I'm still within warranty I can send it in for repair/replacement.
Perhaps there is a very slight chance that someone has also encountered this, and it's still a software problem which can be helped by me in some way?
Thanks in advance!
Its probably some part of the motherboard that is faulty. Take it into a repair center. Get it replaced.
Hello, I would like to first tell you the story my LG G4 has gone through and then I tell you the error.
So, at first my phone was working absolutely properly. I accidentally deleted some pictures and to do a recovery, I had to root it. And rooting would be useful for later so why not do it?
So I first unlocked the bootloader through the code from the LG site. After unlocking, the phone reset (because it would be just too good to make some memory changes and nothing more.) But allright. Then I was ready to root. I just booted the phone, everything was fine. I unlocked the developer mode and opened ADB. I rebooted to recovery through
Code:
adb reboot recovery
I was expecting to see some menu with buttons (but that would be just too good). However, I saw just android with a red triangle in the middle. Nothing more. No response to buttons, nothing.
So I thought. Allright, let's boot into recovery using hardware buttons (vol down + power) at startup. Unfortunatelly, it seemed like there is no such mode System just normally booted (and that was just after bootloader unlocking. Recovery mode goodbye.).
I tried to send commands to the phone using diagnostic port. Unfortunately, it responded by FAIL to every command.
I reboot to bootloader and booted an image: "boot-em.img" (from here: google: how-to-root-lg-g4-on-android-6-0-marshmallow-20a20b-firmware. I'm a newbie here. thx for understanding.)
After that the console uploaded the image and booted successfully. Then, however, system started to boot up and was endlessly booting (LG boot animation) till the battery was critical.
I was able to access the EMI number through volume-down button and volume-up button pressed simultaneously.
I was also able to access some factory-reset dialog by holding volume-down and pressing power-button several times. I choosed to reset everything and then accepted it with one more 'are you sure dialog'. System rebooted and was stucked in the LG boot animation.
Then I got to download mode, since recovery mode was lost in hell. Through LG-UP I flashed the original KDZ firmware and everything got back to normal, but recovery mode was still inaccessible through the hardware buttons. I got through the process of setting everything up, getting developer, rebooting to bootloader and I booted TWRP.
TWRP loaded and it responded to double-tap on screen to wake it up. I just checked the menus and let the phone sleep.
After several hours I went back to the phone and double-tapped on display. Nothing. Phone was not responding. I pressed the power button and the phone restarted (I think. It either restarted into the system or was not responding to power button.)
So I got to the system and again rebooted to the TWRP (through fast-boot). I tried to back-up one partition to the disk. During the process phone had turned the display off. So I double tapped. Nothing. I removed the SD card and the phone woke, saying that back-up process was not able to complete. Suddenly it stopped responding to double-tap. It woke up through an interrupt. I re-inserted the card, successfully backed-up the partition to the SD-card and I left the phone laying on the bed plugged in the charger. It stayed that way for 4 hours or so, doing nothing. All of a sudden, a yellow screen was there, (and that's a screen of absolute death that was never supposed to come. Little I knew.) saying that an unexpected critical error happened and to do a memory dump, insert a cable, set up some communication (I don't remember what it was, didn't take a picture of it.) and it could send the memory dump to PC or somewhere. I thought to myself. So, the application is not so stable after all. It said that to reboot just press the power button or something.
And now the problem comes:
The first start: Bootloader booted, LG animation went on and finished. The starting up apps dialog came rolling. Then, system restarted.
The restart: Bootloader booted, LG animation went on and freezed. Then, the phone restarted.
Second restart: The same thing as the first one.
Fourth restart up till now: Bootloader tries to boot and restarts before the LG animation.
I got to download mode and it restarted even there. After re-inserting the batterry I can sometimes get to the Firmware Update window and communicate. There I flashed the official firmware again.
No success, as if I didn't even do it. It restarts before the animation.
Can I do anything with the phone? Hopefully I can. No hardware problem occured (except for a situation where the error could fry the wires inside the mighty System On Chip.)
For the software state I cannot even tell but I might say it's cooked just wrong. That's why I came here.
I know I did some pretty stupid steps. But the error was not done by me. It worked fine and after the yellow screen which came by itself, it just (some bad words).
Thanks for replies.
Phone: LG-G4 H815, European market
Solution
So, I was looking around and believe it or not, this problem disconnected the pins on the motherboard's snapdragon 808.
I think this happened: The device, although it was heated many times during its life, it withstood that so far.
However, a longer run of the TWRP had finished it off. Memory got disconnected while running and it threw a yellow-screen.
Pins got disconnected and from then on it was just a standard common LG bootloop issue.
The continuous process of dying (First it partially loaded, then only animation, then nothing) is explained by this fact that the pins were so-so there and a couple of reboots just got it totaled.
Temporary fix:
Pre-heated the memory chip to 250°C using Hot-Air gun. After 18 seconds at this temperature I pressed the memory on top of the snapdragon down to the board while cooling.
Then I added a little metal square on the metal part that is covering the system on chip. This part is over the SOC where before there was just some tape.
This can work for several days in sleep mode or a couple of 'heat-demanding' operations on the phone.
Permanent solution should be to reball the memory chip on the snapdragon. That's my next step.
I'm really anxious and nervous about this so I'll simplify this as much as I can; recently my phone was turned on on top of my desk and randomly restarted. I thought little of it, as it quickly went through the OnePlus logo (it began to take longer the second time I restarted it) and Android splash screen, but then stopped on the circles animation and remained looping there. I have very important data on it that I'd like to recover and WILL NOT factory reset (flash) my phone.
The battery icon and percentage still show up when I plug in the device. I still have access to Recovery Mode, Fastboot, and Sideload through their key shortcuts. I previously had USB Debugging enabled but can't authorize ADB since I can't check the confirmation dialogue box (shows up as "unauthorized" in command prompt). I had very little storage (less than 250mB) for the last few days. I don't have root access, custom recovery, or an unlocked bootloader.
I already tried clearing my cache; if I restart after doing so it only takes a few seconds to pass the OnePlus logo as opposed to the ~20 seconds it previously took. This delay raises every few restarts. I've tried waiting many hours to see if anything would happen or if ADB would start functioning. I also tried fully draining my battery overnight and nothing happened. My files are not deleted/fully corrupt since I could still see them when flashing through internal storage from Recovery Mode. OnePlus chat support said I have to flash my phone and Twitter support refused to respond. Local data recovery centers said I could get my phone shipped to them for a free diagnostic, should I do so or is there a way to unbrick or recover my data at home?
Is there anything I can do? Thank you very much!... for now I'll just remain depressed...
TL;DR - My phone's stuck at the circles boot animation and I want to recover my files or fix the soft-brick without resetting. I don't have root access, custom recovery, or an unlocked bootloader.
UPDATE: I boot into Recovery Mode and "Reset System Settings"- my phone rebooted with 112 gigabytes of storage already taken up and all of my Android/data folders empty! I lost very little as I set my save folders to other locations! It looks like the error was not having enough storage! OnePlus chat support said that I had to factory reset my phone, DO NOT listen to them! MY PHONE IS UNBRICKED!
Check out other responses:
https://www.reddit.com/r/Oneplus5T/comments/ahfabg/data_recovery_for_softbricked_oneplus_5t/
https://forums.oneplus.com/threads/data-recovery-for-soft-bricked-oneplus-5t.986096
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
I would just like to reply here and add my own potential fix and also would like confirmation that it would work.
So I have a SM-G996B in a boot loop which returns a 'fs_mgr_mount_all' error. Possible to reboot into recovery mode, cleared cache and restarted bootloader etc with the same boot loop. Powered off and connected to PC for Download mode for ODIN recovery but upon pressing volume up, it then restarts again so Download mode recovery is impossible.
I know however that Developer options and USB debugging was enabled on the device as well as unlocked boot loader. I was able to download the correct original stock OS based on the PDA , CSC and Android version.
I have then installed the latest ADB software on my PC and Samsung USB drivers.
By then rebooting into recovery mode, I have the option of 'Apply update from ADB'. I have then confirmed the device connects using the ADB devices command.
I would like to clarify one thing however. I want to keep the user data at all costs. By using the stock firmware and renaming as update.zip, will it use the HOME_CSC and not the CSC file? If not would it work if I open the zip and remove the CSC before re-zipping to make sure?
Thanks
Reebee said:
Hello,
my wife got a S21 FE (SM-G990B/DS VD2). Yesterday it started to reboot over and over out of a sudden, showing the samsung logo first, followed by the knox logo, then shutting off and on again. Tried several guides to enter Recovery or Download Mode. The only thing that worked was entering download mode by pressing Vol up, down and power while a USB-Cable is plugged in, but as soon as i press the vol up button to pass the "warning screen", it shows some phone specs for a couple of seconds, shuts off and starts bootlooping again. After some hours, the phone once entered recovery mode when it lied next to me for about an hour. Tried to wipe cache, but just got an error I can't remember right now. Hoped it fixed itself when it made it to recovery and just rebooted to see if it works again, but then it just keept bootlooping again.
Since then I couldn't figure out why it once booted to recovery on it's own nor why I can't force it to enter recovery by pressing vol up + on.
Still hope it's just a faulty update or bug, but feels very much like it's a hardware related issue. Replacing the phone won't be an issue, but I'd really want to save data on the phone as my wife didn't make any backups and really wants to keep the photos.
As I just found guides that included recovery or DL-Mode, which are both no valid options for my case, I'd be thankful for any ideas to fix the phone or at least gain access to files before replacing it.
So.. did anyone come across similar issues and found a solution to revive the phone or are there any "unpopular" ways to recover samsung phones out of this state?
Edit:
Turned off completely overnight, booted once to system, looped again and now it's working like nothing ever happened. Got no clue what caused it or why it is working again. Saved everything for the case it happens again.
Wouldn't trust that device anymore, but my wife wants to keep it.
¯\_(ツ)_/¯
Click to expand...
Click to collapse
Similar issue with same phone. In a bootloop after trying to root. None of the button combinations have worked for me, for the past several days.
Tried powering the phone off for the whole night.
When connected to the PC shows phone is in recovery mode via adb (blank screen though).
Want to know how to get into DL-mode, guaranteed.
Got to DL mode by pressing vol up + down + power + usb cable connected in PC and phone. However, couldn't do anything there, but maybe you can
Also, phone is still working and I still have no clue what was the problem and what fixed it.