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.

Galaxy note 4: Serius problems with root!!!

Hi everyone guys, my nickname is AndresPiggy but you cal call me just Piggy as my friends!! :cyclops:
My problem is this:
I used to have my phone perfectly rooted with chainsfire(SuperSU)!! But... A time ago, I installed KingRoot accidentally and the apk started to install the root, after the root instalation failed, the Superuser(Apk from KingRoot) of KingRoot was there in my phone installed and that ruined the root on my phone, I tried to eliminate it but I can not, then, the SuperSU started having problems manage the aplications that need root access, after that I verify my root in my root checker and it said "Sorry! Root access is not properly installed on this device".
"Root Checker App" : i66.tinypic.com/2re79n9.png
All these after I installed accidentally the KingRoot... After all this mess, I made a reset factory, but saddly, the Superuser was still there, and the SuperSU too. Now I dont know what to do I and searching help from you guys. :crying:
Searching more information from another apps I saw this:
"Simply Unroot App": i66.tinypic.com/ht5khv.jpg
"Unroot My Phone App": i68.tinypic.com/10ng7sp.jpg
"Superuser App" By ChainsDD: i63.tinypic.com/25gqc1w.png
I hope those pics help :good: Now I have the Kingo SuperUser deactivate it, and thats another thing, when I wanna install the bin of SuperSu, its failed, I tried by teh 2 ways and failed.
What Can I Do?

Hi Piggy! (As your friends call you)
The only thing I could think of in this case is to flash the stock firmware again. (Will cause a full wipe of the device though, so make sure you back up your stuff!). Unless your problem is solved by now of course.
-RFB

Just like @RealFreddyBananas said. Flash a new stock firmware via odin. Then you can root your device again.

root g870a ph2?

Someone I work with has the s5 active model g870a that has received the marshmallow 6.0.1 update. Something has happened that for some reason has wiped all of the pictures from her phone. I was going to see if I can recover anything from the phone, however I will need root access if I am going to examine the empty parts of the drive to see if I can recover anything. Does/can anyone tell me an effective rooting method for this phone? Does anyone have any idea how I can attempt a recovery of the photos without root?
*Edit*
I see there is a cf autoroot for SM-G870W. I feel like if I try this method I'm going to be looking at a bricked phone.

It can not be rooted, live and learn.... bu next time...

(Soft?)-Bricked My S7 with a Flashfire Update, Need Help to Fix It?

So I've been rooting me phone for a while and have managed to never f*** up, till now, and I sincerely hope you guys can help me.
After rooting my S7 a while back, I just recently noticed SuperUser telling me that I didn't have root anymore, so I decided to follow these instructions to re-root my phone:
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I successfully followed all the steps to get root, but when I opened Flashfire it told me I could install a new update while maintaining root, so since my android is at 6.0.1, I did that and it bricked my phone.
On boot it says "Startup Failed - Use the Verizon Software Repair Assistant . . . " and on top it also says "Custom binary blocked by SECURE BOOT." I have tried going into recovery mode and deleting the system cache, but that doesn't do it. So is there any way to get the phone to properly boot while not deleting my data? I was rooting my phone precisely so I could use Titanium Backup again, so I don't have any backups stored anywhere. I have heard that flashing a recovery image with Odin can work, but would that delete my files? Someone please lend me your expertise.
My phone is a Verizon S7.

Fixed
I am surprised that no one responded to me, but what's important is that, miraculously, I managed to un-brick the phone myself without losing any data! What I did was, as my last hope (since Odin wasn't able to flash the stock image, a la the traditional soft-brick fix), decide to follow the on-screen instructions my phone was giving me and to download and run something called the "Verizon Software Repair Assistant," which can be found in the top google results after searching for the quoted name (xda doesn't let me post the link).
After putting my phone into download mode, I plugged it in, ran the software and let it work overnight. Checking on it in the morning, I found my phone, not only completely functional and working, but updated to Android 7.0 (it was 6.0.1 previously before the failed Flashfire OTA update) and still holding all of my data intact.
So, the interesting thing that I learned is that flashing to stock via Odin to fix a soft-bricked phone should not be the default resolution for potentially most people, as the carrier's default (in my case, Verizon's) repair utility managed to completely fix my phone without any side effects or data loss.
Is there anyone who could chime in on why the Repair Utility did not wipe my phone's memory, even though it warned it would?
**Note**
Verizon links to the Windows version of the repair assistant on their site, but to get the Mac version (which I used), the only way you can get it is by changing the end of the url they mention within the thread from "Win" to "Mac."

Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here

*Detection* said:
Pleased you managed to fix it, and thanks for posting the method for others
As for replies, if you stick around XDA you'll see replies can take days sometimes, patience is the key here
Click to expand...
Click to collapse
I guess I am not acquainted with this forum enough then, thanks!

Most likely the cause of the fault would be updating via FlashFire and keeping root. When the update was flashed, it most likely flashed the stock kernel and patched it for root, which is not a compatible root for our devices. Flashing the root kernel with Odin probably would have made the phone boot normally.

P8Lite removing encryption

Hi,
I think I made a big mistake when playing around with an branded P8 Lite. Unlocking went well and I was able to install TWRP ( Elite Dev. 3.2.1 ) Sofar so good. But since I did not assign an screen unlock code before it is not possible to remove the encryption at all. So not possible to flash a different ROM, tried several tips I found but nothing worked. Since the phone was never used before there is nothing on it which might be worthwhile to back up. Endresult is that I can access the phone via ADB and fastboot. But that's it.
Anybody with a clue on how to proceed ?
Tks
Henning