yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] IJoxer:
Oh I've read plenty, clearly you're not understanding the issue. I'm not going to clutter the thread with flaming, so let's just agree to disagree.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
I understand the issue just fine, it's you piping into it that's the problem. If I'm not understanding please correct me, because so far you've only brought up things already discussed. Also that's funny you would say you have no problem cluttering the thread, as everyone should read the entire thread apparently, but if you hadn't chimed in in the first place there wouldn't be any clutter.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] IJoxer:
Christ, are you 3? Go away!
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] lickwid:
Thank you. I found your post stating that. I must not have chosen stock SystemUI. I'll live with it for now, as I don't feel like re-flashing until a new update comes out. Overall, this runs pretty smooth and the battery is good. I tether a lot, so I do lose more battery than normal, but no big deal. No more lag playing some graphic intensive games either, which I was having on the previous non-U build.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
So much for civility. "Go away!" Sounds like a three year old to me.... When he looses an argument rather then admit he is wrong, points and makes claims as to the maturity of his opponent. Yup. I'm definitely three.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] IJoxer:
Are you still talking? I said many posts ago that we should agree to disagree, and you carry on and on and on. I'm not even sure why I continue to feed into your nonsense, maybe a mod will kindly clean up this unnecessary conversation. I won't respond to you again, I can only hope you'll take the same advice.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
Clarifying false information isn't unesscary. Wasn't that the whole reason you responded? I certainly hope a mod will kindly clean up this conversation, simply to avoid confusion for others who read through the thread.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I lost the game.

My post wasn't meant to be an attack by any means. If anything, it's my fault for not making a new post to begin with. I couldn't update the OP for some reason when I uploaded the ROM, so I just posted it within the thread. Someone mentioned flashing the U-firmware with Odin and you mentioned that using FlashFire instead worked for you, so I was under the impression that you were aware of and had been running the U-ROM. Flashing back and forth between U-firmware and Verizon can be finicky at times, so I find it best to use Odin to flash the full firmware and boot it before installing the ROM. I lot of people run into bootloops when going the dirty data approach, which makes it hard to figure out what caused it after the fact. If the U-firmware won't boot correctly when flashed with Odin, then I can guarantee it won't boot correctly when flashed with FlashFire alongside the ROM. The Odin full firmware first before root and flash method was created to cut down on the questions pertaining to bootloops. It may not be the quickest approach, but it has a higher success rate.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] spodemaster:
This how too could be a little bit more thorough and updated. I had two major issues one minor while updating with the SM-G930V.

Trying to run the root.bat as administrator didn't work at all. The window opens and closes for a split second, Flash Fire can't gain access to root.

The only way it worked was just opening it normally. The window would appear to hang, then reset the phone. After that Flash Fire will find root.

The Flash Fire APK that is linked is outdated or doesn't like the SM-G930V it closes after establishing root. I had to log into the google play store and updated it, so in this case you have to log into the play store.

Nowhere does the instructions does it mention the "Choose Verizon or Other" Stage Choosing Verizon Rooted eng boot will lock down the phone and you will have to re-odin the Rom again. This is a really sloppy over site and should be in the instructions.

I'm shocked this hasn't specifically been mentioned in the forum. The phrases "Choose Verizon or Other" or "S7 Variant" do not show up in this thread at all.

I had to re-odin the nougat_S7_Flat to reinstall SU.

Everything seems good now, but since this is posted on the Verizon board it really seems to be lacking in some very important specific instructions pertaining the the VERIZON PHONE we're working on.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] j0hnh0lmes:
Read the damn thread..

Feel free to copy paste my post. =)

Again read the thread. Your making yourself look like an ass. Move on.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] lepa71:
just a silly question. can i just flash 930u fw and stay on it? will this work on verizon?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
Ok stop. This is ridiculous. I shouldn't need to reread 10 + pages of thread to answer a question, for which the information applies to all firmwares. Again CVertigo1 doesn't recommend it because others had issues, but it worked for me. That is all. So by calling me an A** you're only making yourself look like one.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] j0hnh0lmes:
I'm guessing English is new to you. I never called you an ass. ;)

Laziness is no excuse. I've read all 70 pages.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] jrkruse:
Come on guys. Enough arguing over here.

---------- Post added at 09:37 AM ---------- Previous post was at 09:33 AM ----------

Hey when you get a chance you need to post a link to the RomControl source code from my main thread in your OP so you don't get in trouble. How's everything going. Seems like some good arguments going on here so something's happening
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] IJoxer:
I saw your update and was going to suggest that to [MENTION=6697968]CVertigo1[/MENTION] as well, obviously got a little side tracked. There wasn't much of an argument, just one person who insist on having the last word, while refusing to read the entire thread, which would have clarified his arguments.

Either way, back on topic. Apologies for my part in said arguments, and a huge thank you to both of you for your hard work on these roms.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
Reading through the thread will tell you that I could not update the OP, so I did not put the updated FlashFire in the instructions. You can also download the latest FlashFire apk from the internets without needing to log into Google Play. It's not that the app has issues on this phone in particular, but the time it's run. Chainfire essentially programs kill dates into the app that make it force close if you pass that date, and this can be solved by going into the system settings and setting your date back a few weeks.

I guess most people didn't need special instructions stating to choose Verizon stock when flashing on a Verizon phone. I guess that's something I'll have to add to the OP when I can update it. The ROM can be run with other carriers, so this ROM isn't completely specific to Verizon.

Here's a tip, since you're using a VERIZON phone, select Verizon stock. If you choose roots, it should flash the root kernel, but if it didn't you can just use Odin to flash the root kernel without needing to re-Odin the ROM again. (I'm assuming you mean the firmware, not the ROM)

I most likely will.

I'm going to have to do that. I'll be honest, I haven't tried updating the OP since those first couple of days where it wouldn't let me. It took so long to get the instructions worded right, then it wouldn't post them, so I gave up lol. Looking back, I should have saved the instructions in a text document to copy and paste. Things are going well. I think arguing is just a part of forum life at times lol. How about yourself?

I appreciate it. As for the arguments, I think they go hand in hand with any forum lol.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] eeisenberg95:
I'm having th3 same problem on the newest version. Mine doesn't seem to ring at all. Possibly the dual speaker mod? Works great otherwise even with samsung browser
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
Now that I think about this, I do remember this issue, but it's not really an issue. You have to go into call settings and choose a ringtone lol.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] eeisenberg95:
I had done that. The default is silent. Not only that but it does not vibrate either. The vibrate option is turned on.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
Which ROM are you currently on?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] eeisenberg95:
Newest one posted in the comments here. It works amazing other than this. Smooth as butter and so freaking fast.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] neilwashere:
Been away from this thread for a while and honestly don't remember what version I flashed (QA4 I think?) I was using condensed display scaling and I turned on power saver for a bit then turned it off and it switched back to normal display scaling and now I can't find the setting to turn it back. Is the display scaling option in this rom? I've been looking for the setting and can't locate it. Any help is appreciated.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I haven't been able to duplicate this. My ringer is working great, as is vibrating when ringing. You did wipe data and start clean, right?

I don't remember where it is on the old ROM off the top of my head, but in the latest U-ROM the setting is under display, and it's called screen zoom. I would start by looking there. Let me know if it's there. If not, I can tell you the backdoor way of condensing the display.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] eeisenberg95:
Yes I did. It did not happen right away worked for a day or two then tapered off. I know it's not a hardware thing because I get notifications for texts and such.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] neilwashere:
Thanks for the quick response. Weird I don't even have the option. I thought it was in here too. Is the backdoor way doing the Nova launcher activities thing? Cause I've tried that and the setting isn't even there either...
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] spodemaster:
I'll have to look up what distinguishes a rom from a firmware.

There is specifically an option to install Verizon Rooted. I don't think it's reasonable to expect people to read through 10 pages of a forum to learn that installing that option will trigger the secure boot feature.

I searched through the forum Searching for the key phrases relevant and found nothing before proceeding.

Also don't know if there is an easier way to reinstall SU, but I did need to re-odin the Nougat_S7_Flat_EngBoot

And run the root script again to get SU back on.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] spearoid:
I'm still on QA4 and wanted to ask if anyone has had trouble with NFC bumping / photo sharing, or with sharing photos with another Galaxy phone through the Samsung Connect / Phone Visibility method. Been on this ROM for a while now and love it... Only recently tried to share photos with my wife's vanilla GS6 and ran into all kinds of problems. The NFC handshake starts but fails.... Same thing with the Samsung Connect method.

Thinking maybe I need to try this latest release, but don't really need to if the issue persists.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] jamus28:
If you're looking to run this as an unrooted generic firmware (which is how it should be run), select the "verizon" stock option in aroma. I'm using a G930P, on the Cricket network. All the LTE bands are enabled on the U firmware anyhow.

The rooted options will have the eng kernel problems obviously.

Also, I've attached the Ufirmware photo editor and camera shooting modes apk's, deodexed and signed, so that anyone can install them, if they're missing (instead of reflashing the rom).

@C1vertigo: I'd suggest making a new thread away from this madness :silly:
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] rkmFL:
I realize this will get me flamed, but I sympathize with [MENTION=4975544]spodemaster[/MENTION]'s post.

When the instructions advised against allowing root to be re-installed, I thought it was one of those traditional CF/TWRP/Aroma failsafe's that you see at the end of the process.

I didn't realize it meant that we should not use the "Verizon Rooted" option of Aroma; I had just assumed it would not be an option if we were not to use it (although I understand now this is not the case).

Before I installed, I spent over 2 hours going through this thread because the install was different than all ROM's I've installed in the past. As a result of stumbling on [MENTION=4975544]spodemaster[/MENTION]'s post, I installed without root.

Next I plan on using Odin to re-flash the Nougat Kernel (included in OP), followed by the root.bat.

Everything seems to be working great non-rooted; however, I use Titanium Backup, some root-features in ES File Explorer, and the ROM Manager itself.

Thanks [MENTION=6697968]CVertigo1[/MENTION] for your work on this and thanks [MENTION=4975544]spodemaster[/MENTION] for clarifying the "Verizon rooted" issue.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
It's not that I'm lazy. I just don't need to spend a bunch of time rereading a thread to answer a question. I'm busy, I saw someone ask, what I thought would be simple enough to answer.

They were already clarified before people started to argue with me -_- [MENTION=6697968]CVertigo1[/MENTION] had clarified for me.

You are right not much of an argument, just people refusing to understand each other. Again, usually it's not really important to reread everyone else's questions, help and answers that have already been delt with, that's why I felt I didn't need to read it. After [MENTION=6697968]CVertigo1[/MENTION] mentioned the ROM having been updated based off of the u firmware, and people having issues installing it with flashfire, I said ok, my mistake, just trying to be helpful. This past day, I went back and updated the ROM using flashfire, and installing firmware with flashfire before ROM. It worked fine. Which goes to show again, it A) it worked for me B ) it wasn't worth not trying if data is really important to you, push comes to shove, the worst that happens is he Odin's the firmware and reinstalls ROM.

It's not that I refused to not have the last word, it's that I felt, still do, that it was necessary to clarify, as people were/are smearing my good name. Even if it's just a user name on a thread website.

In conclusion, information I provided was irrelevant to firmware, as it worked in both places. Second, yes [MENTION=3438983]j0hnh0lmes[/MENTION] you called me an A**, even if you didn't out right say I was an A**, saying I was making myself look like an A** is the same thing. Third, it's still not necessary to read through everyone else's problems that have been resolved, as XDA should hopefully help [MENTION=6697968]CVertigo1[/MENTION] update the op, or if he decides to make a new one, because information in the OP should be up to date. I apologise for whatever I did to irritate everyone to the point of blatantly refusing to except whatever information I gave, and or name calling. I really don't have time to read through tons of thread posts. Not lazy, just busy, only ever have about an hour of free time. Can we all agree to in the future be more open minded?

This whole thing seems to be blown out of proportion just as large as stangs private conflict with [MENTION=1949695]jrkruse[/MENTION]

P.S. backhanded comments about someone's intentions, is a good way to reinstigate an argument. Also, please don't respond with "if you have so little free time, why are you posting this at one in the morning?", Simply put I'm a christian, and I don't believe in leaving conflicts unresolved. (Yes even if anyone thinks it was resolved before, it wasn't as stated before backhanded comments reinstigate)
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] jrkruse:
Me and [MENTION=4840281]stang5litre[/MENTION] are perfectly fine there is no private conflict going on
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
See what I mean? Backhanded comments....
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] mcvoss:
I'm still on the original Q4 Rom posted here but I have two problems, I'm curious if anyone else has these.

1) With VVM I can only hear Voicemail if I put it on speaker

2) When I make calls I can not hear the ring in the earpiece, even though it is ringing on the persons end. I can hear them once they answer. If I am hooked to Bluetooth I can hear the rings.

Any suggestions?

Thanks
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] IJoxer:
I apologize, regardless of how the situation looked. I sincerely felt you were being aggressive, and apparently I misunderstood your responses. I'm over it, as I'm sure most are, life's too short to sweat the small stuff. Let's just bury this and move on with what we're all here for, geek stuff.

Stay beautiful my friends!
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] stang5litre:
I have no issues at all with [MENTION=1949695]jrkruse[/MENTION]. Let's get this cleared up. I am talking to jrkruse right now.. No issues what so ever. Recent events had nothing to do with the public and I was given false info. Everything has been resolved in a civil manner and i never had anything bad to say about jrkruse. Let's get back to Android. The devs got this. :svetius:
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] neilwashere:
Think it's the same issue for both. Turn the volume down one notch when you're calling someone or for voicemail. Same thing happens to me. If the volume is maxed out there is no dial tone and I can't hear anyone on the other line. If it's one notch below the max it works fine. Weird bug.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] j0hnh0lmes:
Which was via pm. If you want to continue acting like a child feel free. I sent it via pm because the stuff isn't needed on the forums. Quit being a troll, put your big boy pants on and focus on your homework.

If you feel you need to continue this sent it via pm so I can ignore you there and everyone else doesn't have to deal with your Magikarp style failings.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
Not trolling. Being honest. Sorry if you can't take that. Maybe you should take your own advice. Everyone else is willing to drop it. The only Magikarp failings is the person cussing like a sailor, telling people to grow up, and then referencing a child's video game... Put on YOUR "big boy pants" then, Let it go.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] jrkruse:
Can I help you with something?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
No... Why?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] jrkruse:
You seem to not be getting the answers you want. I just thought I might be able to answer your question
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
What answers? What questions? I haven't asked any....
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Indyultra:
Ok, are there any other steps in this process? From page 61, post 608, i think. Seems like I read somewhere about wiping again In flashfire. Running the qc1 now.

---------- Post added at 08:53 PM ---------- Previous post was at 08:51 PM ----------

This one,

I forgot to mention a step I took that may be related. For the final step of the FlashFire instructions, add a wipe---wipe cache, format cache, and wipe SuperSU. Try that and let me know if it makes a difference. I jump back and forth between the Flat and Edge forums, and the cache format step is mentioned there, but I forgot to put it here.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] jrkruse:
Then why are you fighting with evryone? If you have a specific question I am the guy to ask. I was just offering my help
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
I'm not fighting with everyone. Clarifying information. -_- only one guy seemed so hell bent on picking a fight with me....
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] jrkruse:
Ok you had no questions then
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Cm4nXD:
Yes. Only answered questions so far, and asked a couple, but they have already been answered.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] paul.miner:
Thanks for this, I got my phone running this firmware and while I miss having root, it runs so much smoother and faster, and I get a few perks (network speed in the status bar is one I was going to miss anyway since I didn't have Xposed).

It did take a few tries, so I wanted to document some of the things I ran into:

The FlashFire APK linked in the OP no longer seems to work. It starts up, goes through all the checks, then exits. I think I had read somewhere that this program expires periodically? Ended up using the copy from the S7 rooting guide thread.

I started with this process with the G930U firmware, and everytime I got past the last step (Aroma finished, final reboot), the phone would bootloop. I ended up loading some G930V firmware (QC9), then starting over from step 1, and that worked.

The first time I tried booting using the hybrid firmware loaded in step 1, I kept getting application errors saying "IMS service has stopped" and "com.sec.epdg has stopped", and I think something about wi-fi calling too. They were non-stop, made the UI lag, and prevented me from going through the initial setup. After booting into recovery and wiping data and cache, the errors went away.

During this process, I had gone into recovery a few times using the Power+VolUp+Home combination and was presented with a menu. However, after reflashing to stock 930V, I was presented with a screen that simply said "No command". I eventually found out that if I just left it on that screen, it was actually working and 30-60 seconds later it would go to the recovery menu (not sure if I had to press anything, but the point is that this wasn't a dead-end like I initially thought it was). This might be superstition, but it also seemed like the "Custom" icon on bootup remained even after flashing to stock, until I had entered the recovery menu.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] starboys7:
i just want to say this is the only rom and firmware that has correctly worked on my g930v, amazing work cvertigo, im a total newbie to all of this but through this thread and jrkruse root method, i was able to make my s7 great again. (i first tried installing a exynos rom and freaked out when it bootlooped though i had bricked my phone) :rolleyes:

its a shame that this has to be hidden on page 61 its really good rom, hopefully soon you can fix the OP so more people can use this setup.

i would like to ask a question, im using this rom the "playstore" version unrooted i keep hearing that rooting using the engboot again to have a rooted/rom'd s7 is bad and has "problems" can anyone explain what those problems are compared to this rom?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] hunteditor:
Return to Stock?

So..... I followed all the instructions and was able to install the U-ROM on my new S7 fairly painlessly and was loving it. Unfortunately, the damn phone will not recognize an SD card. I tried three different cards, including formatting on a PC first, and none worked. Kept getting an "Unsupported SD Card" message. Anyway, I'll need to return the phone. Does anyone know if I can return to stock by following the return-to-stock instructions in the root guide? I guess I should clarify I mean the root guide in the Guides section of the forums and not this OP.