Hi,
So today i reboot my tab 3 7" and it doesn't show anything on screen, but i can hear the boot animation and when I lock and unlock the screen.
I didn't install / flash anything, its stock ROM.
I tried rebooting with pressing power button for a while, tried to get into recovery (i think i can enter but i can't see anything), and I don't know what else to do, please help anyone.
Also, i tried to connect to PC and it works, i can save all my stuff, but this is not the point.
I even unplug the battery and reconnect it...
For reference it's happening what you can see in this video (its not mine):
(youtube) /watch?v=oT2JpMI0BA8
help please
Related
So, it's been a fun couple of days.
I was 'tabling' away, as usual, and my tablet suddenly reboots (if it matters, I was just opening FPSE, as I'd done dozens of times before; Skype was on background; every other process was finished). 'Ok', I thought, 'that's weird'. When the tablet's done rebooting, the lockscreen shows up, and when I try to unlock it, the scren just freezes. Couldn't turn off the screen, nothing. So, I force a shutdown by pressing the power button.
When I try to turn it on again, it just stays stuck at the Google logo screen. I tried going in through recovery, but the result is the same. Select recovery, Google logo shows up, little android with exclamation point doesn't.
I tried formating through fastboot -w, but the process just keeps endlessly deleting, while doing nothing at all. I have to quit command line, shut down tablet or unplug the USB cable with a command line message showing up (I once left it while I went for a coffee; two hours of deleting nothing at all). Same thing with trying to unlock bootloader to maybe going to recovery after flahsing a custom recovery.
I don't mind losing everything I had. All pictures are recuperable and the rest is either in the cloud or in my phone/PC. The most annoying thing would be to set up the whole thing again, wich is no trouble at all (that and going through PvZ2 and TD Bloons 5 from the start :crying: ).
I was using Android 4.4 (KRT16S), everything stock.
Is it bricked, soft-bricked, did the aliens get it? I am e-mailing with someone from the store I bought it from, hoping for a solution or (worst case scenario) RMA, but I would rather solve this without having to.
Try flashing system.img, recovery.img, and boot.img, by hand.
Your emmc likely got corrupted
How do I do that with a locked bootloader and no access to recovery? Is it possible?
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.
I have three (3) Samsung Galaxy Tab Kids T2105 tablets. All are running the latest firmware, T2105UEAOE1.
None of them will boot into recovery. The tabs work, they will boot normally, and then will boot into Download mode. But they will not boot into recovery.
* If I hold down Power+VolUp+Home, or Power+VolUp, continuously, the Tab turns on, and then, about 5 seconds later, turns back off.
* If I hold down Power+VolUp+Home, or Power+VolUp, and release them when the Samsung Logo appears, the device boots normally.
* If I hold down Power+VolUp+Home, or Power+VolUp, and release Power when the Samsung Logo appears, and then continue to hold VolUp and/or Home, the device sits on the Samsung Logo for 20 seconds, then the screen goes blank for a second, then the logo comes back on and sits for 20 seconds, then the screen goes blank... and this cycle repeats until I release the buttons, at which point the device boots normally.
I have done factory resets (through the normal mode settings menus). I have reflashed the latest firmware with Odin3. Nothing seems to fix this problem.
I've been searching the net for hours for this. I see a number of other people who have reported this problem. But nobody has offered a solution. One person stated that he uses "adb reboot recovery" - which is a fine, if ugly, hack - but the fact remains that, for many people, apparently, Stock Android Recovery is not accessible from the Samsung Galaxy Tab Kids T2105.
Does anyone know of an actual solution for this, to restore recovery functionality to this tablet?
Hello,
I have the same tablet, same problem (no stock recovery). None of the button combinations work, and the logo just keeps repeating. My situations is that my 9 yr old daughter locked herself out and can't remember her lock screen password. It's a totally stock tablet (never been rooted or flashed). Because I can't get into the tablet, I'm not sure what firmware version it has, and it does not have USB debugging enabled.
I tried booting into the stock recovery to do a factory reset (since we can't do it in the Settings). I tried flashing the same firmware you mentioned using Odin. It goes through the motions successfully and reboots. But it boots back to the lock screen and its still "locked" (we still see her personal wall paper) - which tells me the flash is not taking. Even though my Odin set up is fine, it does not work (even though everything passed with green lights). I tried going into Safe Mode to try bypassing the lock screen, but even in Safe Mode it still asks for the password. My thinking was to go into Settings and initiate a new password or do a factory reset.
(BTW - the Safe Mode button combination was different for me. Holding Power + Volume Up did not work. Instead I had to hold Power + Volume Up & Down until the logo showed up. Once the logo disapeared, then I had to let go of the Power button only - but continue holding the Volume Up & Down until it fully booted into Safe Mode).
I tried ADB in order to use a password reset/erase command line. But because the USB debugging is not enabled, ADB doesn't see the tablet. There is no other way to enable it via Odin or ADB. And I can't even sideload any Lock Screen Hack apps becuase the table is not rooted, or not USB debugging enabled, or can't get into recovery to flash an .apk or image.
So I am stuck. Why would Samsung block recovery mode??? I have been trying for more than 8 hours. If anyone can help, me and my 9 yr old daughter will greatly appreciate it. My last attempt will be to try Google Device Manager and see if it can somehow unlocks it. Or try Kies (although everything I have read so far says that these have not worked either).
HELPPPPPPPPPP!!!!!!!
ggee
wfire said:
I have three (3) Samsung Galaxy Tab Kids T2105 tablets. All are running the latest firmware, T2105UEAOE1.
Does anyone know of an actual solution for this, to restore recovery functionality to this tablet?
Click to expand...
Click to collapse
Hello,
I'm not sure which one of these did the trick for me, but I was able to get into recovery mode. I'm not sure if your three tables are rooted or not, but I don't think it matters. Try these two methods:
Method #1:
Technically, I think I just stumbled on to this one after successfully completing Method #2 (below). But it's worth trying it first before moving on to Method #2.
-Hold the Home + Volume Up + Power buttons together at the same time (just like the normal process).
-Now, you will probably need to try this next step a couple of time before you get it right. This is because it happens pretty fast and you need to time it perfectly.
-Notice that when the screen turns on, the actual first thing that happens is that the the screen backlight turns on and glows first. This happens first and a split second later the first Samsung logo flashes.
-You need to let go of all three buttons at the same time as soon as you see the backlight turn on, but before the Samsung logo flashes.
This is the sweet spot, and it happens pretty fast. But once you do it at the right time, the tablet will go black again and then the recovey mode will show up. It works for me every time.
Method #2:
I thought somehow the recovey mode portion of the firmware had become corrupter somehow. So I decided to flash a custom recovery using Odin (since at that time I hadn't stumbled onto Method #1 yet). Make sure to use gr8nole's custom recovery version for the SM-T210 and SM-T210R (these are the equivalent wifi versions of our Kids tablet). His versions have fixed some known bugs that CWM/TWRP have with the wifi version of our tablets. Make sure to download and flash the CWM or TWRP .tar file for Odin (I personally have always liked CWM over TWRP).
Here is his link: http://gr8nole.blogspot.com/
Also mentioned here: http://forum.xda-developers.com/showthread.php?t=2437219
-Make sure you have all the correct USB drivers for the tablet installed on your computer.
-Open Odin and load the .tar file that you downloaded from gr8nole into the PDA or AP slot (depending on your Odin version).
-Let Odin check the m5d verification for successful authorization.
-Once Odin is ready, then boot the tablet into Download Mode (Home + Volume Down + Power button)
-Connect the table to a USB cable that is attached to your computer's main USB port.
-Odin should now recognize that the table it connected to a valid COM port.
-Click <Start> button on Odin and it should flash the costum recovey .tar file pretty quickly.
-The tablet will simultaneously flash a progress bar and start to automatically reboot (also pretty quickly).
-Disconnect the tablet from the USB cable now.
If the tablet does not automatically reboot to the new custom recovery screen, then just power off the tablet completely. Wait 30 seconds, and then boot the table to recovery mode use the Method #1 shown above. You should now be able to go into the new custom recovery mode you flashed with Odin (CMW or TWRP). It should all work now.
From this point you can download and install SuperSU to add root (if you want to).
Let me know if this works for you.
ggee
Hello,
I bought a "bricked" Galaxy Tab S4 on ebay. The only info I got was, that it is stuck in a bootloop since the last automatic update.
The bootloop is similar to this one. The tablet starts with the Samsung logo, then nothing happens and after a while I end up in recovery mode. Further, if I restart or hardreset the tablet, the screen stays black. The only way to boot it up again is to empty the battery while it is stuck in the bootloop. Afterwards I can enter download mode by holding "vol up and down" and plugin the usb cable.
In download mode this text appears at the bottom left:
#reboot recovery cause [unknown]
API: 3
manual mode 1.0.0
(Similar to this thread.)
OEM lock is on and of course I can't change this being stuck in the bootloop, or can I?
I successfully flashed the stock rom T830XXU5CUE2 with Odin3_v3.14.4 and latest samsung drivers. Unfortunately it does not help or fix anything. (I used virtualbox, but it worked and said "PASS" at the end).
After some research I would like to try my luck with a combination rom, but I can't find a U5 version which I should use because of T830XXU5CUE2, is that correct?
Any ideas how I could proceed from here? With OEM lock I guess there is no chance to flash TWRP on it?
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.