Database Users

(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.

H910 Second Attempt at rooting and flashing help appreciated

Hey folks,
So I'm on my second H910 now, I went into the first one all confident and what not having done this sort of thing before on old Samsung Galaxy phones, only to learn that LG is a whole different sort of beast.
I followed this guide https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 and managed to kill the modem. I didn't do a backup (this time I will) and I just have a few questions before I start the process this time around. This Ebay seller has no returns so this is do or die (or lose a couple hundred bucks rather).
I believe the problem was, besides not having done a backup in LGUP, my first H910 had the H91010L software version, I upgraded my new H910 to the H91010t version, but I'm not sure if I should keep going or not. Am I safe to follow this guide: https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500 with H91010t?
I then plan on flashing the version of TWRP in this thread https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239 and flashing the Alpha Omega rom 1.1.8 https://forum.xda-developers.com/v20/development/alpha-omega-rom-oreo-vs995-h910-ls997-t3847510.
Should I be fine doing this after following the guide in my first question above or should I expect to lose my modem or any other issues?
Lastly, if I run into issues with celluar service again and try going back to stock with my LGUP backup, will that restore my modem/service or is the actual hardware fried? I've tried restoring the modem with fastboot and files downloaded on this website and reddit and didn't manage to fix the first phone.
Thank you for any help and feedback!
Edit: I stayed at 10t, went ahead with everything as planned and everything went smoothly, enjoying my new V20.

[SM-T580 TAB A 10.1] Newblood needs some love with bricked FRP/Custom

Hi guys. Hoping for some direction here. Can't be sure on region flashed with. Purchased in U.S. on ebay. I attached an image with what i thought would help some.
Says "T580NZKXMAR" at time of purchase on the image attached below... And i guess this is just a model number, not a actual build. So really no hope here for me. believe I flashed with a ROM from the UK afterwards sometime last year.... or so "I think" it was as I was struggling to find roms for the U.S.A......
So getting to the problem. I followed tech alpha's youtube video for rooting. My goal was to get oreo 8.1.
After a couple of days on root, I was in settings looking at things, and then the display kept flickering with red blocks all over the screen. So my dumb ignorant self, disabled developer options just for sake, and the problem disappeared.
Then it became a little sluggish and then I decided to restart my tablet. Bam! Soon earned myself an FRP right after a restart of tablet .
Not sure where to begin or how to approach resolution of problem. Pretty sure tablet is just a stock build from uk using latest method for root with magisk and twrp on 7.0. I believe it came with marshmellow at time of purchase. I Have a couple of backups from smart switch that state its currently 7.0 through navigation of files.
Think my main problem right now is I'm unable to get Odin to recognize my tablet and all the videos I've watched seem to direct me on this route.. Not sure if this is because I recently formatted my computer or not and that it hasn't been initialized yet?? So hoping for a lot of love and some direction here and a place to at least start this. Afraid i'm going to do something wreck-less if i act too hasty. So wanted to be sure before i made any more mistakes. A big thank you to those wanting to help!

kcaJoC said:
Hi guys. Hoping for some direction here. Can't be sure on region flashed with. Purchased in U.S. on ebay. I attached an image with what i thought would help some.
Says "T580NZKXMAR" at time of purchase on the image attached below... And i guess this is just a model number, not a actual build. So really no hope here for me. believe I flashed with a ROM from the UK afterwards sometime last year.... or so "I think" it was as I was struggling to find roms for the U.S.A......
So getting to the problem. I followed tech alpha's youtube video for rooting. My goal was to get oreo 8.1.
After a couple of days on root, I was in settings looking at things, and then the display kept flickering with red blocks all over the screen. So my dumb ignorant self, disabled developer options just for sake, and the problem disappeared.
Then it became a little sluggish and then I decided to restart my tablet. Bam! Soon earned myself an FRP right after a restart of tablet .
Not sure where to begin or how to approach resolution of problem. Pretty sure tablet is a rooted 7.0 currently. I believe it came with marshmellow at time of purchase. I Have a couple of backups from Samsung that state its currently 7.0 through navigation of files.
Think my main problem right now is I'm unable to get Odin to recognize my tablet and all the videos I've watched seem to direct me on this route.. Not sure if this is because I recently formatted my computer or not and that it hasn't been initialized yet?? So hoping for a lot of love and some direction here and a place to at least start this. Afraid i'm going to do something wreck-less if i act too hasty. So wanted to be sure before i made any more mistakes. A big thank you to those wanting to help!
Click to expand...
Click to collapse
For odin to recognise your device you need the Samsung USB drivers installed first.

Sorry, Should've mentioned. This was done very early after install of Smart Switch. Thx. Please advise on a next step, Sir. Thank you.

Unable to root

Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.

Visseroth said:
Long story short I'm working on loading a new (has not been used) LG V20 with Lineage OS and obviously have to pre-root the phone but I'm having problems and any help would be appreciated.
I'm currently working on trying to get DirtySanta working but in the command line when I run "run-as con" during ./step1.sh I get, "run-as: unknown package: con"
My questions are...
What am I missing?
Are there step by step instructions for completely re-loading these phones to LineageOS from factory to fully running?
The phone has the factory Android 8.0.0 and has NO data on it that needs to be saved. FastBoot is NOT working, I've tried many times.
Enable OEM unlock is not a option in the developer options on the phone.
Click to expand...
Click to collapse
If you took the time to the dirty santa thread then you'd know that your phone's security patch date is date where ds has been patched, you need to be on a security patch date prior to Dec 2016
Sent from my LG-H910 using XDA Labs

Now I remember why I didn't post on these threads much. People just assUme that the posting person is a COMPLETE idiot.
This is a HELP forum where people come to get HELP and information, there's no reason to point fingers. A simple, "BTW that version you're running is a patched version, you'll need to roll it back to a prior, follow these links..." version would have done just fine.
With that I'd reply........
I realized I needed a older firmware last night when I was fighting with it for hours. I rolled it back to a firmware, dated 12-24-2016 and managed to get BadSanta to work but it caused my phone to go into a non-stop vibrate, it wouldn't complete boot and was basically bricked. I then found from another site that explained EXACTLY how to put the phone in download mode and then re-flashed the ROM (BTW, for those that don't know, you power off, hold the volume up and then plug in your data cable) but then put Android 7.0 Build number NRD90M.
The problem I am running into is everyone's information isn't is sync.
Some say how to proceed but don't say on what build number to proceed.
Some say to roll back to Android 7 Naugut but don't say which version because there are many versions of that version.
Personally I don't understand why a ROM can't be flashed via the download mode but then again I'm not a programmer.
So with that, after many hours I've made some progress but I am disappointed in how complicated and time consuming it is. I'm seriously considering a Pinephone for me and this phone (once completed) for my wife.
Right now I'm in the process of following this thread....
https://forum.xda-developers.com/v20/how-to/lgv20-vs995-verizon-aio-post-06-19-2017-t3624326
Later, after I get some work done.
Thanks for the reply though.

Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410

Visseroth said:
Well seems the BadSanta isn't working on my phone, as soon as I get past step3 and it reboots the screen is all scrambled and the vibrate motor runs continuously.
I've managed to get into TWRP once and followed the instructions but it bricks the phone at the LG startup screen.
Reloading the fastboot image doesn't do any good.
So seems I'm stuck with the stock firmware.
Can't say I didn't try.
Instructions I followed are here...
https://forum.xda-developers.com/v20/development/ls997vs995h910-dirtysanta-bootloader-t3519410
Click to expand...
Click to collapse
The vibration is normal if it's the VS995, which I'm sure you are using, right?
And the phone is not bricked, it's normal to see that warning at the start-up screen (about the device being corrupt....). Just be patient and give it time to boot.
The scrambled screen (static on boot) is also normal, just flash lineage 17.1, afaik it doesn't have static on the vs995
On a side note: double check the dirtysanta thread, you'll find most of these there

Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.

Visseroth said:
Really? I tried for many hours, multiple times and no go.
Yes it is the VS995, I guess I forgot to post that.
I did at one point get to a point where I could see a image behind all the garbled corruption on the screen and I did know that the corrupt notification was normal, that's how I made it to the TWRP once but I just couldn't get the screen fuzzy corruption to go away and the phone was still stuck vibrating non-stop.
Maybe I'm missing something?
And I only managed to get to the TWRP bootloader once.
Are all the features on the phone working on LineageOS 17.1?
I really wanted to get the phone not only up to date but limit the spying as much as possible with a device already designed to spy.
This phone is really for my wife, I'm thinking of ordering myself a PinePhone and giving that a whirl.
Click to expand...
Click to collapse
On stock, after it is done booting, press the power button once to turn off the main screen, then cover the upper left corner with your hand till the second screen turns off (abt 5 - 7 sec). Turn the screen back on and use your phone.
About lineage,

Need help. TWRP says i have no os anymore and i cant get in android anymore

Long story short i used odin to try and root my galaxy s8 using twrp 3.5.3_9-0, rmm-state_bypass_mesa.zip and magisk 16.1.zip.
Somewhere in the process i accidently wiped the os it seems. My phone cant get in android now anymore i need some help please getting my os back on. It seems rooting is far too complex and the amount of tutorial/guides on the internet and youtube is overwhelming and some say contradictorary results.
I just want to get android 8.0.0 back on my phone and running can someone tell me what steps to follow please.