I was installing the latest update on my 7T and it got stuck on the reboot animation. I waited about half an hour and it was still stuck on the animation screen so I held Power+Volume Up to force reboot, nothing happened. Got into recovery mode and deleted system settings and cache still the same. Drained it and powered it up again still nothing works. And my laptop doesnt recognize it if I plug it into the USB port. I can access both fastboot and recovery mode. I need to extract some very important data. Please please help.
Try reflashing the ROM manually. There should be a guide somewhere in the 7/7T forum.
Related
Today I was going to update my CM10.2 20131127 to CM11 20131207. They are both official nightlies. I checked the md5 after downloading. So I booted into recovery, backuped, and did a full wipe. Then I tried to use adb sideload to flash the zips. This is the first time I used sideload. I followed all steps on the TeamWin website. After transfering the zip to the device, it started flashing. After a couple seconds, the color of the screen changed and dimmed slowly. I waited a while and then unplugged the device and the battery. Then the device is completely unrespondsive. No bootloader, no download mode, not even responding when I plugged it in. ADB and fastboot shows nothing. Can anyone help me?
P.S. I am using TWRP 2.6.3.2
doing a fastboot of the factory images do nothing? what about the battery? is it charged at least?
Good luck
Charging does nothing. I followed the steps for OMAPFlash. After that I am able to boot it sometimes. The screen will freeze and dim after booting into both android and bootloader. My computers won't recognize it when I boot into bootloader. So flashing is not possible.
So I reset it again using OMAPFlash. I will crash after a second or two. I plugged it in, ran the fastboot devices command before it crashed. Fastboot can recognize the serial number before it crashes. 12 ? or nothing after it crashed. Should I restore it to factory and lock it or just send it to some specialist?
P.S. When I charge it, it shows the battery with thunderbolt icon and crashes.
hi guys, I did something stupid with my G3 Cat6 and need help. After a wipe and fresh flash, I did my steps wrong and froze the LG Launcher before restoring my usual launcher. Now after a reboot it is stuck in the bootup animation (because it's trying to boot to a launcher that doesn't exist).
I can't get to recovery manually (holding pwr+volDown, then volUp+VolDown, combination for the Cat6), and ADB doesn't recognize my device, despite that my PC does see it in the device manager. When the phone is looping the boot animation, it reacts to connecting it to the usb cable, but Android Studio doesn't recognize it either.
Is there a third way to get to recovery? I need to get to recovery to flash the rom again... but I am stuck.
I have JZ Schminer recovery, and flashed radeon maya 1.7.1. I can't understand why the physical buttons combination doesn't work to get to recovery....
download mode works, but I don't know what to do with it
Thanks.
edit. Ok I just realized that USB debugging is off because it's a fresh flash and I didn't activate it before freezing the launcher and rebooting...
I fixed it. Somehow I managed to enter recovery in the 100th attempt. I wiped, flashed, and rebooted normally. Phew.
Mods, please close or delete the thread
I am stuck with bootloader. Couldn't not enter recovery. Flashing from bootloader again and again didn't work. Couldnt enter download mode either. It goes into download mode then starts restarting. Tried RUU, it says low battery. When tried power off it and put to charge, charging icon comes and then restarts again and again.
N.B. DDR test looping, message on fastboot screen
itsmelutfor said:
I am stuck with bootloader. Couldn't not enter recovery. Flashing from bootloader again and again didn't work. Couldnt enter download mode either. It goes into download mode then starts restarting. Tried RUU, it says low battery. When tried power off it and put to charge, charging icon comes and then restarts again and again.
N.B. DDR test looping, message on fastboot screen
Click to expand...
Click to collapse
I think you are the 4th or 5th member whom has posted about this issue. I don't think any of them came to any solutions, but search for the threads, I haven't been keeping up. Sorry to hear this and hope you get it resolved.
Hi everybody, yesterday I was playing with my old Galaxy A50 trying to install a custom rom unsuccessfully.
I repeated the procedure three times installing TWRP and then Havoc OS but every time I tried to reboot from TWRP to OS I was stuck at the warning screen saying that the phone bootloader was unlocked and booting into download mode to reflash TWRP was blocked as it showed "only official binaries can be installed" (yes I installed Samsung disabler but still).
Still I was able to get the phone into download mode and reinstall the stock firmware as it seemed to be the only way to install and boot TWRP.
But at 4th time repeating the process I got frustrated, shut down the computer and left the phone on the warning screen still connected to computer usb cable.
Then I got back and noticed the phone was off as the battery died.
Indeed the battery died, so I put the phone in charging and after it reached 100% I tried to boot into download mode again to reflash stock firmware.
But here's the strange thing, I cannot boot into download mode anymore as pressing vol up+vol down while connecting usb cable, shows the lightning charge logo for 5 secs and then reboots infinitely with the same pattern.
If I force reboot by pressing vol down+power it shows the Samsung logo with the warning below it, then skips to another screen with another warning suggesting to press power button to continue (which does nothing) and after a while reboots to samsung logo.
So it doesn't seem it is bricked, it looks more like a battery controller fault, so I tried to detach the battery flex from the board, hoping it would reset the controller but it's still the same.
Also I tried with the flex detached and still no download mode is possible.
Was the download mode somehow erased? (if it's even possible considering it's the motherboard firmware)
If you need photos, videos or even a call on zoom, Skype, webex I would be glad to show you
same i got the same problem i can't find nothing for this when i press volume up and down and put the otg cable its simply charges but it gets stuck on the logo image there's no way to fix this but the only way is to open the phone,change the emmc and put one from samsung,close the phone flash a custom rom and you are done.
If you can enter recovery, do it. As soon as your phone gets into it, select the power off variant and then try to enter the download mode.
It seems like you did not unlock the bootloader, did you?
The bootloader Is unlocked i can't enter in the recovery because the phone locks on charging logo and its fully charged but when i try without charger It doesn't start.
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.