Database Info

Hard Brick (possible hardware failure)

I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?

WildZontar said:
I was wondering if I've encountered a common failure mode with my Verizon Galaxy S3 and if there are any possible solutions.
A week before it bricked, the phone was acting rather odd, rebooting itself spontaneously and at random; I didn't really think much of it until the following week. Applications on the phone had been running VERY slow and would often crash or hang; in addition, the phone was rebooting itself several times an hour at this point.
The last reboot hung for a while at the "Samsung Galaxy S3" screen before going to the home screen. At this point I realize there may be something serious going on, so I attempt to SSH into it and retrieve important information off it. Unfortunately, it proved to be too late; login attempts failed with "Argument list too long". A few minutes after my ill-fated attempt to save data, the phone crashed in the app launcher and initiated a reboot again; only this time, the Samsung logo never came up. Since then, I have been unable to power it on, enter recovery, or otherwise get any life out of it.
It's long out of warranty so I'm basically wondering what my options are to revive it and possibly get important info off it. Reinserting the battery does not work and neither does plugging it in. All options to enter recovery or any other sort of mode fails; it essentially acts like there's no battery inside and does nothing. Is this a common failure state for S3 units and is there a known solution? Has anyone ever used JTAG to retrieve information off the storage inside?
Click to expand...
Click to collapse
Plug it into your computer, or a wall outlet with the battery out. See if it mounts as a strange drive or the led light flashes for a second.

Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.

WildZontar said:
Oh wow. Yes it does have the red light when I plug it into the wall outlet without battery. Haven't tried the PC as I'm leaving for work and my USB wire is in the car but I'll assume that will work when I try it.
Click to expand...
Click to collapse
At least it isn't completely fried, this method should work:
http://forum.xda-developers.com/showthread.php?t=2581166
Make sure it has no other sign of life first.
If you were on 4.1 then make sure you don't use a 4.3 file and lock your phone. Might have to do some digging around to find them, but they are around here somewhere.

Unlocking Rogers Galaxy S7

I had a small hardware shop unlock a Rogers Samsung Galaxy S7 (SM-930W8) and many things have straight-up stopped working. Keyboard, back and recent apps vibration feedback is always weaker than usual. I have already factory reset this phone 5 times out of frustration now, and have tried to also back up a phone from Smart Switch, but all Smart Switch is giving me is a "Failed to connect to device, the connection to this device has timed out." Another difference from before and after is Knox giving me a Security notice, details are "Unauthorized actions have been detected." When I tap the notification, it brings me to the Device security part of Settings, and says that there is a Threat found and I have to restart the phone to undo any unauthorized changes, upon restarting the same error appears in the notification pane everytime I try this process. I have also noticed unexplained slowdowns while launching apps and hitting back and the phone actually doing something. Yet another thing I have noticed is that the phone does not seem to remember any WiFi connections that I connect to and takes excessively long to turn on WiFi and excessively long to connect to any WiFi connection. Another different thing that happens is whenever I reboot the phone, a process called "LoggingService" always crashes. There are still several issues I have noticed, and it's only been 3 hours since unlocking the phone. The device is not rooted.

My dad has been unable to unlock his S7, despite trying to do so directly with Rogers. Did you unlock the phone yourself? Were you able to figure out what went wrong after the unlocking?

Boot loop after update, last ditch request for help!

Hey everyone, I've exhausted all my options (verizon, samsung, friends, google, etc) in recovering my phone. Hoping you can help.
What happened: verizon galaxy S6, stock, unsure if USB debugging was enabled (unlikely but possible, cant remember if I enabled it with this phone or my last one). I woke up and saw there was an OS update that downloaded overnight, and without thinking about it, just began the installation. The next message I saw said "installation failed" or something along those lines, can't remember exactly. After that, rebooting the phone froze on the verizon logo, and would stay until the battery died.
What I tried and what i CAN do:
Get into maintenance boot mode.
Safe mode: no change.
Simulated hard reboot: no change.
Erasing cache: No change.
Odin on phone: able to get into this from android recovery, but no program on my computer has been able to pull files or flash a rom without doing a factory reset.
Verizon wireless update assistant: Recognizes phone but can only do a factory reset, will not recover data.
Samsung smartswitch: same as above
Other details: Definitely not backed up through verizon, google, samsung (yes I am kicking myself for not going through any of these convenient services that were practically shoved down my throat).
Using a macbook, but I can get access to a PC if absolutely necessary.
When I turn my phone on, I have a yellow triangle with an exclamation point, an android with Xs for eyes rotated 45 degrees, and it goes to system recovery. When I reboot from there, it goes to a normal boot, but freezes on the verizon logo and gets stuck there.
I don't give a crap about this phone, but I have pictures from the first year of my daughter's life on it that I don't want to lose, and I was too stupid to back them up. If you can help I would be incredibly grateful. If it makes you pity me more, I've been using an iPhone 4 for a couple of weeks while I tried to sort this out on my own. I don't want to factory reset this and move on if I can save the pictures.

One last thing I tried: heimdall/jodin/flashing a stock firmware. I can consistently load odin mode and get to download mode, but jodin can't obtain the PIT file so I can't go any further.
I appreciate any help. I can just factory reset and move on, but I really don't want to lose the pictures of my daughter if I don't have to.

Assistance with (partial)Bootloop and Locked Bootloader.

Hey there forums.
I've been an active browser of XDA but never really created an account but I've done so to have assistance with a particular situation with my device.
So the other week, i had spent 150 dollars on a Sony Xperia XA F3115 from Vodafone, Australia and it turns out that the bootloader was locked because of Vodafone and i wasn't going to pay 50 dollars to unlock it. I alternated and browsed the internet (Mostly XDA but other sources aswell) to figure out if there were any methods of bypassing this, whether it be easy or not - I was willing to try anything that seemed like it had a chance to work, without a 100% failure rate. Reading responses to particular methods, i was drawn into one method of just reflashing the stock firmware onto the device and then rooting, flashing and doing everything from there (as the device was no longer locked by Vodafone at that point).
I have completed this task as of this morning, and the device booted successfully. As soon as i unlocked my device, i had received the general android setup window but half way through, i got spammed with "Name has stopped responding" countless times to the point where the phone was literally unusable, it would just pop up again right after closing it - So i decided to restart the device. This was probably a big mistake, it booted fine but it said "Android is updating" and had the whole "Applications updating 100 out of 255" stuff happening. Then it booted to the lock screen, which i had previously setup before i flashed the device which didn't really surprise me too much.
Then it rebooted. Now every single time i boot the device, it reboots to the "Optimizing apps blah out of blah" and then will reboot upon the notification bar popping up, but no lock screen. I decided that my best cause of action was to download another firmware and try that one instead, but I'm unable to boot my device into bootloader mode as it's impossible to happen. I turn off my device, plug it in and hold the volume down button but it refuses to work anymore.
Now that the situation has been explained, I'd really like your help to see if i can have this resolved. I'm baffled as to why Vodafone even locked it to begin with, since the phone was prepaid and had nothing to do with any sort of plans - nor was it even available as a plan. I don't have the money to buy a new phone, and they have already denied me a refund. I need this phone for work and the mistakes i made were stupid - Please, i need assistance. You're all hopefully more tech savvy than i am in the field of mobile phones.

HELP needed. Galaxy 8+ MobileIron lock out.

Sorry if this is in the wrong location but it's been a long time since I've been here and everything looks different with the forum, lol. I couldn't find anything after searching the forum so making this post.
Here's my issue. I have a very old Galaxy S8+ issued by my employer. I left the company back in Jan 2020. Since then my son has been using the phone at the house to play games on and watch YouTube, etc. Whenever it would get running too slow I would just do a factory reset to clean everything out and my son was good to go again. UNTIL YESTERDAY. I did a factory reset like usual but when it restarted and I began the initial set up like you do with a new phone I got a message after connecting to my WiFi that "This device is managed by your organization". It then had a pop up for username/password for MobileIron. Never got that before so only thing I can think is that my old company started using this MDM software sometime between the last time I did a reset and yesterday. I don't have any sign in creds as I don't work for them anymore. Rebooted into "safe mode" to uninstall the app but cannot because the option is grayed out.
Is there any way to root this phone and get rid of the MDM software or install a ROM or something so that the phone is usable again? Obviously, I can't boot the phone up either than in "safe mode" Or is the thing a paperweight now. Just wanted to check before I chuck it in the trash. Any help is greatly appreciated. Thanks in advance.

I just saw my signature. LMAO! I think it's a little outdated.