yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
I understand that, but the main point for me is to get the phone running at all, without bootlooping. The standard kernel so far for me equals bootloops. This is a used g930v that I got off of ebay, but it so far seems to be working fine otherwise... Maybe there is something with this specific phone. I dunno... I will try one more or two more times, as I would prefer to use the stock kernel as well. I will try again with the standard kernel, but if I can't get it to work, I will likely just edit the aroma script to how I want it, add the engboot at the end of the flashboot process and call it a night.

I have been playing with the phone for the last few hours with the engboot kernel and I am so far happy with it. It seems to run just fine, with no lag so long as I don't actually run the root process itself.

EDIT: I have noticed that NON-HLOS.bin is no longer included in the vzw folder on the zip. Is this intentional? I am reading that it has something to do with the modem... While it may not have been updated in this build, perhaps it is required, especially since we are trying to run a tmobile rom on the verizon network with a verizon phone? I may try injecting that file back in to see what happens... I am already getting tired though, and each go-round is such a long process.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
This is correct. The NON_HLOS.bin is not updated in this ROM. I haven't noticed a significant difference when using the TMobile NON_HLOS.bin that is embedded in the Odin process. As for injecting it into the zip, I doubt there is a line in the script to write that particular partition. You can add it if you'd like, but it won't be as simple as putting it in the directory.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
Hold off on trying again. I was finally able to duplicate your issue. I'm working on it now to see if I can figure out a method so you don't have to keep going through failed attempts.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
Huh! Do tell? What are you finding? I have not yet tried... I am currently modifying the playstore sections of the scripts more to my liking. I am also planning on flashing stock verizon qa4, just to get the build.prop, so I can incorporate JKruse's changes into that...

Is there a quicker way of getting the build.prop? Is it possible to just mount/browse system.img.ext4? I have a windows machine and a bunch of linux boxes...
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I'm not going to lie. This has turned into one massive PITA. I can't get the phone to boot either no matter what I do yet, except flashing the root kernel. I'm still playing with it and looking for a workaround, but we are both in the same boat at this point, and I can assure you that I'm more motivated than ever to get it resolved lol.

Great minds think alike. I want to pull the build.prop from QA4 as well. There is a way to mount and browse system.img.ext4, but it's a long and lengthy process, and I don't remember all the steps. I did this a year or two back when I was playing with making an S6 update.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I think I got it figured out!!! Also, don't worry about pulling the build.prop. I already pulled it from QA4 and QC1 during my attempts to solve this issue. You are welcome to them if you'd like.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
Happy to hear that SOMEONE is having the same issue as me! Well, I will post the build.prop in a few ... I am about to flash qa4. Also, when I mentioned going with defaults in Aroma, I was thinking that maybe there was something to do with the way the hosts file was implemented. Are you choosing the default there? I have been choosing to go with the default (no ad blocking) hosts file because I like using adhell instead...

Aside, while I would prefer to use the stock kernel as well (less risk of stability issues I guess?), the root kernel so far seems to work pretty well...

---------- Post added at 10:37 AM ---------- Previous post was at 10:34 AM ----------

Okay, very cool! What did you find? I would be happy to edit the build.prop if you are not going to do it... Are you planning on posting another zip, or is there something procedural that is killing us?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I chose no ad blocking as well, because I use Adguard. I finally got it figured out. Using the TMB_CSC was the killer. Odin flash all four QA4 files, but use the HOME_CSC. Then start over from step 1 in this thread, also using HOME_CSC. It took forever, but I got everything working normally and passing SafetyNet. :)
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
Okay, so to make sure we are on the same page, are you saying to use the HOME_CSC_VZW file in both cases, or use the HOME_CSC_TMO file during step 1?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
When you use Odin to flash Verizon QA4, use the Verizon HOME_CSC. I'd also like to note that I wiped the cache and did a factory reset right after it booted. Then when you use Odin to flash QC1, use the TMobile HOME_CSC. There will be a recovery error when you do this, but boot back into download mode and flash TMobile HOME_CSC again, and all will be well. Then continue the process exactly per the instruction.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
Uh oh ... Now I am getting a new error. When flashing the Verizon AP, it says on the phone in red text:

Volume Size is too big 1254400 < 1354240

ODIN : Invalid ext4 image

... ODIN has the repartition checkmark under the options tab. I am tempted to use it but also a bit scared... The phone is still not bricked as I am still able to reboot into download mode at this point...

Please tell me if your filesizes match mine:

TMobile QC1 AP 4.40 GB (4,728,535,236 bytes)

Verizon QA4 AP 4.99 GB (5,359,800,516 bytes)

Here is my ODIN log ...

<ID:0/006> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Odin engine v(ID:3.1203)..

<ID:0/006> File analysis..

<ID:0/006> skip file list for home binary

<ID:0/006> persist.img.ext4

<ID:0/006> Home Binary Download

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> SingleDownload.

<ID:0/006> emmc_appsboot.mbn

<ID:0/006> lksecapp.mbn

<ID:0/006> xbl.elf

<ID:0/006> tz.mbn

<ID:0/006> hyp.mbn

<ID:0/006> devcfg.mbn

<ID:0/006> pmic.elf

<ID:0/006> rpm.mbn

<ID:0/006> cmnlib.mbn

<ID:0/006> keymaster.mbn

<ID:0/006> apdp.mbn

<ID:0/006> msadp.mbn

<ID:0/006> cmnlib64.mbn

<ID:0/006> sec.dat

<ID:0/006> NON-HLOS.bin

<ID:0/006> boot.img

<ID:0/006> recovery.img

<ID:0/006> system.img.ext4

<ID:0/006> FAIL! (Ext4)

<ID:0/006>

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] joebro84:
I'm currently on QB1 and I am very happy with the way my phone is running. What's been improved in QC1, and , if I update and choose 'no wipe' in Aroma, will I still have all my apps or would I have to reinstall them?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
Those file sizes match mine. You are Odin flashing all four files at the same time, right?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] gunz.jones:
This happened on the two i flashed when i didn't include the csc file.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
Okay, that did it. I had to flash the NON HOME version of the Verizon CSC before it would allow me to flash the HOME version. I have now successfully flashed all four Verizon QA4 files (with the HOME_CSC) and it is booting up...
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
Super cereal?!? YAY!!!! You are almost halfway there!
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] spearoid:
I'm hoping I'm missing something stupid and simple...but ODIN fails for me pretty much as soon as I hit start....I'm on QA4...just took the update yesterday. I didn't see in the OP any special instructions for the checkboxes in Odin. I wonder if I need a newer version of ODIN or need to change some checkboxes. I'm using ODIN 3.09
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] thefirst__noel:
Under the "OLD QB1 ROM" section in the OP, there is a link to a newer version of Odin. I would give that a shot.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
Okay ... let me say this ...

BOOTLOOP.

Just kidding!!!!

Everything finally went as you instructed in your OP. I am booting up into the playstore version right now! FINALLY!!! Now to edit the build.prop (I grabbed it while booted into QA4), make my own changes and reflash, now that I know this works!!! Only three days to flash a ROM! Not bad!!! :laugh:

The light at the end of the tunnel ... Thanks for taking the time to break your phone and figure things out yourself!
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] spearoid:
You were quite right. Thank you!
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] spearoid:
So yeah... This is amazing... I really cannot even believe I'm using the native hotspot feature on Nougat one day after updating and discovering FoxFi was permanently screwed!

I do IT for a few small companies... Many of the executives have unlimited data plans and I was just about to prepare them for the bleak future with the S8 and not being able to use the FoxFi hotspot method.

Whatever magic was discovered to allow the rom install we're doing here.... Is there good reason to think this approach can work on these upcoming new phones?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
Allright!!! Even modifying your zip works really well. The build.prop stuff went without a hitch. I basically just merged the build.prop tweaks jkruse made with the qa4 build.prop and all is good.

Of couse, I went a bit overzealous this first time around with stripping things out. It is much quicker being able to start with the root kernel and not have to odin back to the start though! Probably going to take a few go-rounds here!
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] vrahn:
There is one thing that I did notice. When I went to open the camera app there is no mode option available. I tried rebooting the phone I tried clearing out the data and cache and to no avail nothing worked. Someone in a different thread had suggested reflashing the camera apk but I'm not sure if I want to go down that road. Because I would like to be able to use the different options for the camera.

Does anyone here have any suggestions for that?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
After reflashing, testing, remodding and rinsing and repeating quite a few times today, adding and removing more apps, I came up with a custom zip that installs the rom just the way I want it. Most of the Verizon apps and the Samsung payment stuff was all removed, even a few Google apps I don't use. I also added back the rosemary don't (I got used to having it!) and fully functioning Samsung camera and gallery apps, including all the modes. The end result is cleaner than the playstore choice, and is so far working correctly. That camera nx app did NOT run very stable for me, crashing in photosphere and slow motion modes, so that is what prompted me to start rebuilding the Samsung camera app.

Build.prop is also more appropriate to our phones.

Anyway, if anyone is interested, I can look into posting my version. Keep in mind that I just finished building it, and I may find more problems as they come up...
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] joebro84:
Swipe right for camera modes.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] vrahn:
I did that, but i do not have tye mode option next to the camera button like i use to. I want to use panaorama and it isnt there. Swiping right only changes the picture style
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] appye:
Camera modes are not installed unless you go with the slight debloat option... I went through this today while building my personal version of the ROM.... I will go over the changes I made in a bit, if someone wants to change the ROM to their own liking...
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] vrahn:
Would i need to reformat the phone again and go woth full rom in order to get panoramic? Or just download another camera app
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] joebro84:
Did you swipe left, too?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] vrahn:
Swiping left only shows a Auto camera at the bottom
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] vrahn:
View attachment 4098318
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] Theroose:
I'm having the same problem does anyone know the package that these camera modes are under?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] rarecarpenter:
Can you please share your rom?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] gunz.jones:
Do you know specifically which apps are needed for fully functioning gallery amd camera? Or did you only keep the camera?

Edit: Is there a way to root and unroot without destroying safetynet?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] vrahn:
So I guess my question is this.

Will going full stock give me panorama? Or will your edits give me that and make the rom better? If so then can you supply your rom? Then I will use that in my reflash?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] GartimusPrime:
So I flashed this rom and love it so far but because I flashed it on a device not supported in this forum (us cellular) I can only seem to use 3g. Is there a way to fix that or no?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I apologize that I haven't been around much to answer any questions the past few days. I've been sick. I'll go back through the posts later today and answer any questions I can.

You guys ready for V10? I updated the latest. This one does not have any build.prop changes, so it will say G935 for the time being. I am working with someone on doing build.prop changes that will hopefully be incorporated into the next update.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] joebro84:
I did the 70 app debloat and I have panorama.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] storm81456:
Ok, I decided to try this last night. I'm starting from stock VZW nougat. So I've gone through this procedure following the steps from the beginning. My problem is that when it comes to running flashfire, it tells me the phone has rooted but it's not a usable method. The latest version of flashfire says I'm not rooted at all. Any ideas? Also, none of my data was wiped in the process of following any of these steps which I found odd. Any ideas? I've tried re-flashing the eng kernel and re-running the batch file several times but flashfire still refuses to work with the not rooted error. I'm, about to start all over again from the first ODIN. Any ideas?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] gunz.jones:
Check that you allowed adb rsa access when hooking to the computer and running the root.bat. It should create root and install supersu
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] storm81456:
Wasn't an option, I think the phone still remembers from before (part of the all my data is still present). From what I can tell in the dos window, all the parts of the batch file complete successfully.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] gunz.jones:
Did supersu get installed?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] storm81456:
I updated my last post with a screenshot from the batch file.

---------- Post added at 12:49 PM ---------- Previous post was at 12:46 PM ----------

SuperSU is installed, if I open it, it gives the binary needs to be updated message, but if I try to it fails.

Flashfire says:

Root was found, but access could not be acquired! Supported roots:

<list 3 types>

Found root:

(null)
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
In developer options, turn off verify apps over ADB, then rerun root.bat, maybe even run it as administrator in case something is causing an issue.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] storm81456:
It's already not selected. I ran the batch file from the shift right click "open cmd prompt here" method and from just clicking the file. It looks like the batch file does everything it's supposed to, no errors in the messages.

Other than doing a complete wipe, is there some other way of rooting I could try so I can accomplish the flashfire portion and get this up and running?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I haven't run into an issue like yours before, so I haven't had to find another method. I may have some ideas. Are you still on Verizon QA4 or have you already flashed to TMobile?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I'd like to add that I flashed v10 for testing earlier today, using the new/latest FlashFire app, so I can confirm that this method still works. There has got to be something screwy with yours that's causing an issue.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] storm81456:
Pretty sure I'm on the tmo, that's what the first step ODIN flash installs, model shows up 930T and build shows up as BQC1. I'm stuck right before the first flashfire step. It seems the root isn't taking. Looking in the original jklruse thread, I saw one reference made to the problem I'm having in post #184, but I'm a few pages past the post and it hasn't been addressed.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
Yes, you are on TMobile. Let me research that post and see what I can come up with.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
That post was resolved by flashing the root kernel. Your root.bat runs, indicating the root kernel has already been flashed. If the root kernel is not flashed, it just says null.

I sent you a PM [MENTION=839429]storm81456[/MENTION]
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] vrahn:
By chance when can we expect an update and updated op
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
Probably earlier tomorrow. Someone is sending their build.prop mods. I'm going to test it out before incorporating it into the latest build and uploading it.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] gunz.jones:
So this works. I used the steps to flash the qb1 ap and the last package i downloaded last week for the debloat. I wanted to get mock locations back.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] vrahn:
Awesome. Cant wait. Keep us posted. I would love to test it out
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] cognitivedissonance:
Hey, thanks for your comment, I've been scouring this thread trying to find confirmation that this re-enables WiFi hotspot tethering for Verizon grandfathered UDP users who took the Nougat OTA.

Even more interesting is the fact that this doesn't need to use the engineering kernel and thus avoids all the performance and battery drags.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] t1231:
Does anyone know what apk I have to remove from the play store debloat to keep the emergency broadcast notifications? Or am I just overlooking it in the settings? Thanks
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] gobluefanjp:
Is it possible to get the edge feature on the flat model with this rom, or is that only possible with root?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I think the edge feature is available, but I can't find it in the BS_Free variant that I'm running, so it may have been debloated. Try one of the lesser debloat options and see if the edge feature works.

I have had the edge feature working on a past ROM, so it's possible.
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] gobluefanjp:
Sorry for the noob question and if this is not an appropriate place to post this, feel free to delete it.

I want to preserve some of my app data, and possibly/alternatively preserve the unique device ID (which changes after a wipe). There are two apps I use the accounts if which I can't access if I wipe/reset the phone and then have to contact the developers to get it fixed (pretty annoying), but this is solved by preserving the unique device ID. Titanium Backup does this if you're rooted (I am not).

Long story short: would it be possible to root in order to preserve data before wiping, wipe and install this rom, restore data with Titanium Backup, then unroot and still have official status?
[Verizon Samsung Galaxy S7 ROMs, Kernels, Recoverie] CVertigo1:
I'm familiar with what you are talking about. What build are you currently on?
[LeEco Le 2 Questions & Answers] piku 123:
Hi Guys,

When i try to unlock my le 2 bootloader through AIO toolkit i am getting error waiting for device then nothing happens.:crying:

I am on win 10.
[LeEco Le 2 Questions & Answers] piku 123:
Guys please help
[LeEco Le 2 Questions & Answers] Prateekmvd​:
Same problems found
[LeEco Le 2 Questions & Answers] Mads71:
Boot Le2 In To Fastboot Mode Manually
[LeEco Le 2 Questions & Answers] Dhruv Dhawan:
Run fastboot as administrator

When opening aio toolkit, open it as administrator

Hope that helps
[LeEco Le 2 Questions & Answers] lambhurricane:
If u are using windows the device is failed to find the driver so manually install adb drivers after that connect the phone then it will search for driver and it will say not found so got device manager and click le2 and u will find adb with ? Mark open it and press update driver and press manual search and type c drive . this search help you install adb drive
[LeEco Le 2 Questions & Answers] piku 123:
Google bootloader driver needed to be installed to run fastboot commands.My win 10 automatically downloaded google bootloader drivers after that i can run fastboot commands.
[LeEco Le 2 Questions & Answers] ankushxingh:
Just reboot your device manualy in boot loader by pressing power button + volume down ..And don't forrget to turn on usb debugging and ome unlock which you can find in developer menu
[OnePlus 2 Q&A, Help & Troubleshooting] Rocken222:
I am a newbie on Op2 device I want to root my Os and installing Xposed on it...i have lots of questions on it like Dose it properly Xposed work on it...?

I want to install few modules which are shorted below pls tell me if those three are working properly on OOS 3.5.6.

1-FLAT STYLE STATUS BAR

2-Android N-ify

3-Greenyfy

P.s - I don't want to install Nougat based os because of they're camera are neither fetured packed nor quality based... i am very satisfied with OOS camera.

If anyone use these modules pls give me your suggestions i really appreciate thatttt...

Thank you very much GuYs.
[OnePlus 2 Q&A, Help & Troubleshooting] Yousvel:
The title of your thread is wrong. You put H2OS when indeed you are referring to OOS.
[OnePlus 2 Q&A, Help & Troubleshooting] Rocken222:
Sorry for that...its OO actually,

Is there anyway to edit that
[OnePlus 2 Q&A, Help & Troubleshooting] mhd athiq:
If u really like customizations on ur device i would recommend Resseruction Remix or AICP both have wide range of options..Yes i agree the camera is not proper...but u can always flash OOs camera zip which i do after installing any ROM to get the stock camera.. In fact the battery backup is better in both these roms and also they have a substratum theme engine
[OnePlus 2 Q&A, Help & Troubleshooting] Rocken222:
Ok, thanks for your kind word...