Database Users

[Q] Having a problem with S4 "soft bricking"

Hello,
I recently tried to root my AT&T Galaxy S4 and install cyanogean mod on it. I screwed something up along the way but I'm not sure what. I tried rooting my phone with Kingo Root Tool, which it said I was successfully rooted. I made the mistake of then accepting an OTA, and of course that soft bricked my phone. I am able to get the phone out of soft brick mode by taking the battery out and putting back in, then entering download mode, and cancelling out. That fixes it every time. As I'm on android 4.2.2, and I understand that I need 4.4.2 for CM11, I thought that I would un-root using the tool, and then try the update again. I un-rooted, it said that it was successful at this. I then tried to install the OTA again, unfortunately it softbricked my phone again. I reset it back to normal, then I figured my best option would be to try and do a factory reset. When I tried the reset, it once again soft bricked my phone. I've reset it back to normal, and everything is working fine, however I'm a little confused as to what's going on. My amateur assumption is that by rooting, it tripped some file rooted deep inside the phone, and now it knows that I tried rooting, therefore it'll block me from updates. If someone could help me this, and possibly help me try and fix it I would really appreciate it. Thanks in advance.

How to Recover Data on S5 from AT&T

Guys,
I accidentally deleted an important video on my S5 that i want to recover.
I have tried several recovery programs but nothing seems to find anything. I Tried Dr.Fone (didnt work), I tried Tenorshare Android Recovery didnt work.
When i try to connect with ADB i get connection closed. Since the S5 is new there is no root yet.
Can anyone help recover a video file on the S5?

Tied in linux and windows. No way to mount MTP as a drive. Cant get root. Cant adb.. Looks like its a lost cause. Any one?

Help me flash stock ROM back please.

It all started when I rooted my phone (Samsung J5 2016 - SM-J510FN), installed TWRP through Odin, did a reset and flashed Extreme UX (9.0). Everything worked so as a noob I decide to turn off USB Debugging and OEM Unlock. I reboot my phone and get the message "Custom Binary blocked by FRP". So I decide to look up how to fix it. Kies didn't work so I go through sammobile and download the Stock ROM. I searched SM-J510FN and filtered for my country (Greece). I downloaded the first ROM I found and flashed it through Odin. I was really excited. Then I unlock my phone. I get dozens of popup messages of "x has stopped working" and the launcher wasn't working properly. I would appreciate any help. Is it a firmware problem? Should I do a hard reset and try installing stock again? Thanks.

dot777 said:
It all started when I rooted my phone (Samsung J5 2016 - SM-J510FN), installed TWRP through Odin, did a reset and flashed Extreme UX (9.0). Everything worked so as a noob I decide to turn off USB Debugging and OEM Unlock. I reboot my phone and get the message "Custom Binary blocked by FRP". So I decide to look up how to fix it. Kies didn't work so I go through sammobile and download the Stock ROM. I searched SM-J510FN and filtered for my country (Greece). I downloaded the first ROM I found and flashed it through Odin. I was really excited. Then I unlock my phone. I get dozens of popup messages of "x has stopped working" and the launcher wasn't working properly. I would appreciate any help. Is it a firmware problem? Should I do a hard reset and try installing stock again? Thanks.
Click to expand...
Click to collapse
Doing factory data reset should clear out those errors

Thanks for your answer. I don't really know how to do a factory reset because I can't access the device's settings.

Anyone that knows how to do a factory reset without accessing the device's settings?

dot777 said:
Anyone that knows how to do a factory reset without accessing the device's settings?
Click to expand...
Click to collapse
recovery

Just finished the factory reset. Setting up the phone now. I'll update if any errors happen next. Thanks for your help

Problem updating and pc connect

Hello everyone.
A few days ago i tried to update my rooted MiA1 but with no success.
I lost my root access and now i can´t update normally. I wiped my phone and nothing changed.
My PC cant recognize my phone too.
It's all working fine as a smartphone, but this issues i want to fix, because i want to root/update again.
Can someone help me?

dennismac said:
Hello everyone.
A few days ago i tried to update my rooted MiA1 but with no success.
I lost my root access and now i can´t update normally. I wiped my phone and nothing changed.
My PC cant recognize my phone too.
It's all working fine as a smartphone, but this issues i want to fix, because i want to root/update again.
Can someone help me?
Click to expand...
Click to collapse
Hey, al already had this problem.
Try to boot the TWRP using BootLoader with command bootloader boot_a file.img (i belive that the command is this one, if does't you can find on TWRP tread), and boot again the rom that had failed.
If doesn't work, you probably will need to boot files like modem.img, firmware or others that may be corrupted cause of flashing.
There are actually a lot of treads of similar erros that happens on honor phones or oneplus, you can use them as reference tho find witch are the files that cause the non recognition on USB after a failed flash.
If needed reflash stock, it will fix in last case.

SM-120 FN - problem with soft and root

Hello
I have a problem with my J1 (2016) SM-120FN
I wanted to upload a new soft to the phone.
Unfortunately, the phone did not have the correct root, even though I uploaded it correctly.
Show that root is not competent.
After uploading the software to the phone, there was an error.
Now the phone can't see the sim card, I can't call, enable developer options or disable debugging because the sysetm forbid me.
What to do?
I guess it would have to factory reset to enable debugging, but how do you do that?
And how to make a correct root, because the files I uploaded were not correct.