Hi everyone, bit of a long story this one so feel free to skip the next couple of paragraphs.
Got a new Samsung S4 mini and at the time was using a Samsung S2. So when the new phone came I wanted to get some stuff from my old phone to the new one. So I tried with the Smart Switch app, I downloaded and installed it onto the S4 without any problems, but when it came to trying to get it onto the S2, I wasn't even able to find it in the play store, because the version wasn't compatible.
So off I went to settings, to try and install the S2 into the latest Android version which downloaded fine, but for some reason it was failing during the installation stage. The phone told me to do it via KIES instead. So I got KIES onto my PC and tried updating the phone via that. This was when even more problems started, it seemed to update, but then on the phone there was a message something like "updating android apps" and it got on the final couple of apps and it never installed, it was basically frozen (I left it a while, maybe not long enough), so the installation of the apps was disrupted when the USB was taken out. The screen stayed the same so I just turned the phone off and tried to reboot it but it wouldn't power up at all.
I can not enter download or recovery mode, the phone doesn't even switch on. It's as if the battery is completely dead.
Long story short: Can I retrieve photos from the internal storage of a dead phone, somehow? I'm not fussed that the phone is/may be broke. All I want is the photos from it so I can transfer them to my new phone.
From what I've read over the last few days, updates etc shouldn't delete things like photos. So it's really annoying that the photos are there on the phone, I just can't get to them.
Related
Hi all
I tried going to a Lollipop ROM on my S2 but I only managed to change the recovery, the ROM didn't work (boot loop) so I used ODIN to revert back to the stock ROM (i9100XWLSW) wiped both the data and dalvik cache. I did also have Kingroot installed during all this and I installed it again after flashing the stock ROM but I've since removed that too with another write of the stock ROM via ODIN.
The problem I'm having now is Whatsapp and other apps won't actually do anything if the device is asleep. The WiFi appears to be connected, logo is present at the top if i wake the device but it takes about 10 - 30 seconds of being inside an app (such as Whatsapp) for anything to happen. I'm not sure if this is a WiFi issue or some sort of app issue across the board? I woke up today at 9am checked my phone there was nothing on it. It was only at 10:30am when I went to send a Whatsapp message to someone and opened the app manually that i had messages come in from 8am that morning. I also use Whatsapp Web and some times it won't connect to the phone via WiFi even if the device is awake. I have to reboot and try again. Although if it's connected via Whatsapp Web and asleep messages come in no problem at all both on the PC and the phone??!!!!
It's doing it constantly now, at the start it was touch and go but now it's all the time i have to constantly check the app for messages to come in. This happens on other apps too.
What's going on? Have i damaged my device some how from the flashing process? I'm pretty familiar with ODIN as I used to flash my old Galaxy Apollo all the time but never had this problem.
I was going to get a new phone but I actually really like my S2 and it actually keeps up with most of the phones in my price range and in some cases (camera, AMOLED screen, storage, sometimes RAM) it is better than the new stuff!
Any idea's please?
Never mind went and got myself a nice Note 3 instead...
Thanks guys.
Hello guys,
I own my Samsung Galaxy S4 I9515 (Value Edition) for about 2 years and since a few months I've been experiencing annoying issue: phone started to get restarted by itself. Sometimes it restarted just once or twice and started to work for few days, but then it restarted over and over again in the same time, like in the 'restarting loop' so I was not able to launch it in the end. Sometimes, but not always, taking the battery away helped, but few times even this didn't help as so I had to either reset the phone to factory settings (wipe) or even install the official Samsung software from scratch (using Odin for example). After such reinstallation it was working for few hours, but as soon as I managed to install all my apps it started to restart again.
Finally I decided to return the phone to official Samsung store for guarantee repair. First time, they told me the issue doesn't happen in their service so they only reinstalled the software (what I also did myself before). The same day when I got my phone back, I restored my apps from Google Play and it started to be restarting again. Because of that, I return the phone to Samsung again. This time they told me the same, that the problem didn't happen during their tests, but they advised me to buy a new battery as with the current one phone seems not to work correctly. So I bought brand new, original Samsung battery, restored my Google account on the phone again, and... It happened again, phone has restated for 10 times during one hour
Do you have any idea why may this happen? Or how can I check what is happening? Does Android store some logs somewhere to see why it crashes and restarts?
I suspected two things:
1. Memory card - I thought memory card could make it happening, as to Samsung I gave the phone without it, but I tested it yesterday with no sd card and the same happened.
2. Apps - as I mentioned before, every time I reinstall the software I add my Google Account and apps start to be installed from Google Play, and mostly after that phone starts restarting again. But how can I check that which app is causing that? On the other hand it would be weird, as I'm using my Google Account on the other Android phone with the same apps and nothing bad happens.
Maybe you have any other idea, would be appreciated, because neither me nor Samsung official service couldn't solve this issue.
Thank you in advance!
Hello to all genius mind.
I am writing here, to find a solution for my problem. I will start from beginning, to be as clear as possible.
This summer, during my vacation time, while diving, I found SG J5 in the bottom of the lake (sorry for the person who lost it like that...). Since I never had android smartphone in my hands before, I was wondering, can this device still work, since I have no idea how long it was under water and what can I learn from this process.
After opening it up, cleaning with 96% alcohol and drying it, devices finally showed some signs of life. Actually, almost everything was working, amazing...
Once I got this device running, I started to deal with software. Following some tutorials online, I was on the process to bypass RFP, but could not finish it, since I had other important matter to attend to. After I was back, and turned device on, for some reason, it booted into safe mode. I have been tried again SideSync method, but it was not working, since device did not reacted, after I plugged in to PC. Computer can recognize device and I can even browser the files in it. Weird thing is, that lower volume button stopped responding (I had theory that it could be jammed, once I removed it and cleaned contact, no changes was in the system, still in safe mode, so its not jammed button...), it was working before and all other buttons are working fine. Because of that, I cannot load recovery mode.
OTG method also did not worked, since nothing happen when I plunged usb into phone (safe mode block all external apps). I have tried to flash new ROM, with a help of "Samsung 300K Tool" I can launch download mode, but new ROM did not gave any result either, and RFP blocks all custom ROM's, that could modify system.
ADB do not find the device, since USB Debugging is probably off, and I don't know a way how to activate it from PC. The trick to disconnect WiFi, when it checks info for google account, did not worked either, since its not possible to select a text for sharing it.
After trying all the methods that I could find, I hit the brick wall. Phone works fine, but its completely locked. I am thinking, that new Samsung protection system is designed like this, to force phone in to safe mode after one hard reset and lock all posiblities to byass RFP, not sure though, it could be hardware problem to, but no idea where...
Does anyone here could help me out with this case
THANKS!
Best regards to all,
HG
Hello all,
I have a Moto Z Force Droid (XT1650-02). It's running on Android version 8.0.0, and build number OCLS27.76-69-6. It was acquired from Verizon. It is not rooted (sadly), and the bootloader is locked. It has 32GB of internal storage, however, I added an SDCard(64GB) to increase that storage space.
I'm having some problem(s) with my SDCard, or more so its usage as adopted storage. I've had the phone with the storage for quite a while and everything has been fine. However, 3-4 days ago was when the issues started. One night, my phone was acting really laggy. Which I just chalked up to tech being tech. I let it sit for a bit, tried rebooting it, etc. Well, as time progresses it seems to me that Facebook Messenger is what's slowing it down. So, I try uninstalling it. Of course, this isn't working and android just keeps giving me a helpful little notification that the app is uninstalling (for much longer than it *should* take). I figured I'd reboot into safe mode and try uninstalling it from there. The phone powers off and reboots fine. However, when I tried to unlock the screen, the entire phone froze and crashed after a minute or two. Once it reboots, it gets stuck in the bootloader (or, more specifically, where it says "DROID" and there are little shiny spots moving around the letters). So I used the power button to force the device off and try rebooting again. Again, boots up fine but it freezes at unlock and the cycle starts again.
Around 2 days ago I took it to a Verizon store. Originally I was just told I was going to have to factory reset (which I didn't want to because all the pictures I have and such would be lost. Apps are backed up by Google though). They told me to take out the SDCard, to help save what I could. Then, I got the bright idea to try booting without the card. This time the phone booted fine and unlocked like it should (the only problem now is that I had no internal storage and all the apps that were on the SDCard aren't loading since no SDCard).
When I leave the phone on and install the SDCard, I can browse the internal storage again. However, I can't see any of the files when I try transferring them to PC over USB. As well, after a while of using the phone, or even letting it idle, it will eventually crash and go back to the above botting and not-unlocking scenarios.
Based on how/when the problem started, and the logcats I've grabbed as the phone was crashing, I have reason to believe it has something to do with Facebook Messenger not being removed correctly. [Logcats in the comment below.]
Any help would be greatly appreciated. As well, please tell me if there's anything that needs clarification. (Sorry for the wall of text. I just don't know what else to do at the moment.)
Logcats:
View attachment First.txt
View attachment Second.txt
View attachment Third.txt
So. Bit of an update.
Turns out it's not actually just getting locked in the bootloader. It seems it's been doing a soft reboot.
I've been running "adb logcat" whilst trying different things, until the phone crashes. That's how I got the previous logcats. However, upon "rebooting" the adb logcat continues to run. I can provide a logcat for those, should anybod want it.
WeButterTheBread said:
Hello all,
I have a Moto Z Force Droid (XT1650-02). It's running on Android version 8.0.0, and build number OCLS27.76-69-6. It was acquired from Verizon. It is not rooted (sadly), and the bootloader is locked. It has 32GB of internal storage, however, I added an SDCard(64GB) to increase that storage space.
I'm having some problem(s) with my SDCard, or more so its usage as adopted storage. I've had the phone with the storage for quite a while and everything has been fine. However, 3-4 days ago was when the issues started. One night, my phone was acting really laggy. Which I just chalked up to tech being tech. I let it sit for a bit, tried rebooting it, etc. Well, as time progresses it seems to me that Facebook Messenger is what's slowing it down. So, I try uninstalling it. Of course, this isn't working and android just keeps giving me a helpful little notification that the app is uninstalling (for much longer than it *should* take). I figured I'd reboot into safe mode and try uninstalling it from there. The phone powers off and reboots fine. However, when I tried to unlock the screen, the entire phone froze and crashed after a minute or two. Once it reboots, it gets stuck in the bootloader (or, more specifically, where it says "DROID" and there are little shiny spots moving around the letters). So I used the power button to force the device off and try rebooting again. Again, boots up fine but it freezes at unlock and the cycle starts again.
Around 2 days ago I took it to a Verizon store. Originally I was just told I was going to have to factory reset (which I didn't want to because all the pictures I have and such would be lost. Apps are backed up by Google though). They told me to take out the SDCard, to help save what I could. Then, I got the bright idea to try booting without the card. This time the phone booted fine and unlocked like it should (the only problem now is that I had no internal storage and all the apps that were on the SDCard aren't loading since no SDCard).
When I leave the phone on and install the SDCard, I can browse the internal storage again. However, I can't see any of the files when I try transferring them to PC over USB. As well, after a while of using the phone, or even letting it idle, it will eventually crash and go back to the above botting and not-unlocking scenarios.
Based on how/when the problem started, and the logcats I've grabbed as the phone was crashing, I have reason to believe it has something to do with Facebook Messenger not being removed correctly. [Logcats in the comment below.]
Any help would be greatly appreciated. As well, please tell me if there's anything that needs clarification. (Sorry for the wall of text. I just don't know what else to do at the moment.)
Logcats:
View attachment 4613124
View attachment 4613125
View attachment 4613126
Click to expand...
Click to collapse
Hello guys, something really weird happened, heres a little background on events that may be related.
First of all the device is a rooted Samsung Galaxy S8+, yesterday I arrived abroad, and today I bought a local SIM card and had no issues with it, and later today I rented a car for a long trip and half way I realized that the car has Android Auto on its multimedia system, so I looked up the Android Auto app on the store and didn't find any so I googled it and downloaded the APK.
At first the car refused to even find my phone and did not want to connect to it, after a while I suspected that Developer Mode may be the culprit so I turned it off and voila, it connected, the rest of the ride went flawless with Waze on the car's screen.
When it was finally time to head back to the hotel, I got on the car, turned on Android Auto again, waze screen showed up but it completely froze, I tried messing around with it but nothing happened, screen is frozen shut, so I decided to try and restart my phone, the next thing I know it isn't booting up with a red "Custom Binary blocked by FRP Lock."
I've read online that I need to reflash the stock ROM, but keep in mind I'm in a foreign country with no access to a computer (writing this on my mom's phone's)
Is there anything I can do? Why did this even happen? And most importantly, would reflashing format my phone? I really don't want to lose my stuff.
Thanks in advance for any kind of support.
The only thing you can do is flash a stock rom using odin and you will lose all your data so i would advise you to flash recovery and do a backup then pull the backup file using adb after that you can flash your stock rom