Develop Bugs

[Q] Galaxy Note 2 completely dead

Hello,
Here's what happened: I noticed that my Galaxy Note 2 wasn't showing up notifications, which was happening frequently after restarting my device, and I restarted it (held power button and selected "restart") to get the notifications to show up again - which always worked for me. But this time I got stuck in the Samsung Galaxy Note II logo, then I took out the battery, re-inserted it and tried to turn my device on again, but it has not responded at all. I thought it was a "battery bug", since I had it calibrated yesterday with an app I always use and I thought that when I would get home and plugged the charger in it would start normally, but It hasn't.
Here are the facts:
- It is rooted, but I use the default 4.3.0 ROM
- It has the Xposed and a few modules installed, but It always worked fine
- It won't start in recovery mode (home + volume up + power) nor in download mode (home + volume down + power)
- After reading a few topics/posts and a few websites I found on Google, I tried starting it on some "I don't remember the name mode", which is volume up + volume down + power for 2 minutes, but it didn't work either.
- I tried botting it up via Unified Android Tool Kit, but it says "error: device not found". And yes, I have the drivers installed.
- It had around 80-90% of its battery charge when it happened.
Is anything else I can do? Has anyone of you passed through anything similar?
Thanks in advance!

BUMP

Galaxy Tab S SM-800 stuck with flashing TWRP logo

I was provided this device to try and help resolve the issue. I am not sure how it got to this point. I believe that it was rooted with a custom ROM, then the individual tried to install a stock ROM (method unknown).
The current situation is:
Galaxy Tab S 10.5 SM-T800 stuck in a bootloop with the TWRP logo on the screen. I can not get the tablet to go into download mode. I have tried all of the different methods to enter download mode, i.e. Power & Vol - & Home, Drain the battery > Plug into PC while holding Vol - & Home, Power & Vol + & Vol -. None of these combinations do anything. The only thing I can do to get a response is to press Power & Vol +, which reboots the device right back into the TWRP loop after the Samsung Logo. Power button alone does nothing.
The device is seen by Windows with the Samsung Drivers but is not mounted to a drive letter, and I can not mount it.
ADB , fastboot and Odin do not see the device.
I would like to flash a new rom either custom or stock, but I need to be able to get the device into download mode so it can be seen by odin.
Any help would be great.
Mike

Probably just timing and pilot error this one. I've never known of any Samsung device boot but be incapable of booting to download mode as download mode is bootloader related.
No working bootloader means dead device.
No matter what state the device is in at the moment with the usb cable removed, hold POWER + VOL DOWN (not up) + HOME until the Samsung boot logo comes up, hold for another couple of seconds then release. Download mode should appear.

I know it should be easy....
I know it should work but it is not, I will make a vid of the process and post. I can not make heads or tails.
Mike
ashyx said:
Probably just timing and pilot error this one. I've never known of any Samsung device boot but be incapable of booting to download mode as download mode is bootloader related.
No working bootloader means dead device.
No matter what state the device is in at the moment with the usb cable removed, hold POWER + VOL DOWN (not up) + HOME until the Samsung boot logo comes up, hold for another couple of seconds then release. Download mode should appear.
Click to expand...
Click to collapse

Is the home button actually working, are you pressing it firm enough?
If the home button doesn't register then the tablet will simply reboot.
Its a bit odd why twrp doesn't fully boot though unless it's the wrong one.
Does it hang at the twrp logo or continually reboot?

Galaxy Tab 3 NO Power, boot loops when plugged in. Otherwise nothing Video attached.

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.

Samsung Galaxy Tab 3 7 Kids T2105 T-2105 can't access recovery mode

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

unable accessing ADB Debug Mode - broken screen

Hi all,
i'm trying to access my broken phone (Samsung Galaxy A5 (2017)) by adb. Sadly - the device wasn't never set to debug mode // developer mode enabled. The display is broken - completely - you can't see anything but the device is responding to hardware keys. I'm able to start and shutdown the device. In normal mode - the device is detected on my pc - but only in charging mode. I can't access the storage drives at all.
I tried to start the download mode (as far as google search helped) by
- turning the device off (pressing & hold power % vol down)
- just before it vibrates - release the keys and press & hold power + home + vol down
- waiting a short time
- pressing vol up
this should start the device in download mode - and i'm able to see it at the device manager in windows 10.
BUT - if i start ADB devices - it's not listed / nor i'm able to connect at all.
Do you have any idea whats wrong - what i'm doing wrong to get a grip on the device?
My plan is - to access the device via ADB and enable the debug / developer mode. Then - starting it up again and bridge the screen via scrcpy to my computer. Then - in theory - i would be able to access the device via scrcpy and setup the sync.
If somebody got any other idea how i can access the phone - please let me know. Please keep in mind - the touchscreen is not working at not all.
Thank for your feedback
FatBulldog

Hi, I am in a similar situation and just starting to scan this forum. Phone has ~8G of pics/vids etc. so if you find a solution that forgoes a screen replacement let me know.

Likewise. I bought a cheap USB-C to HDMI connector but it won't work on my SM-520F. I have an OTG and a USB keyboard does work but I can't see a picture so the keyboard is pretty pointless!
Is there any method of doubling the screen when you can't see it on the phone?

I wound up biting the bullet and buying a new screen.