Database Info

[N7100 4.3]N7100 XXUEMJ2_XXUEMJ2_LBEMJ2 PreRooted-Deodexed

MUST READ BEFORE PROCEED
- This ROM is AP N7100 XXUEMJ2 CP XXUEMJ2 CSC LBEMJ2 and beleved to be PreOfficial
- This ROM have KNOX security effect on bootloader
- I have flashed this ROM with bootloader and even after that I was able to downgrade MG1 ROM as well reflash this ROM again.
- Pre and post flashing EFS backup highly recommended
- This ROM have bootloader and you have to flash separately (Edit : Now you can use this ROM without bootloader too, read installation instruction)
- Recommend to wipe data (factory reset) before flashing ROM
- No one here on XDA is responsible for any bad effect on your device, You are flashing this at your own risk.
Installation Instruction
- Download Prerooted,Deodexed,Zip aligned N7100XXEMJ2 Here Direct MIRROR (Thanks to @MojoManagement ) here is other MIRROR (thank to @kunals.shah for mirror)
- Download Philz recovery if you don't have already. (you can use other but I have tested this one only)
- Copy ROM zip file to SD card and flash it with CWM.
- After Installation of this ROM, you want have WIFI working, You have to Download This Patch and extract to get patch.tar.md5 and flash with PDA tab of Odin to get wifi working. (remember this patch I have tested on MJ2 and using on other ROM may cause serious issue.)
PS : Who have already flashed bootloader and want to get rid of bootloader follow this steps
Downgrade to 4.1.2 (I have tested MG1 My prerooted)
Flash Philz latest recovery
Flash MJ2 from above said link
Flash above said patch
- Reboot normally
Special Notes
- SuperSu zp won't work to root this ROM, though you need not to do it, as This rom is already prerooted.
- If you restore app with Titanium backup, many of applications may not work, but need not to worry, follow this to make it work.
Install terminal emulator from Play store. open it, execute superSu permission and follow below said command
Code:
su
restorecon -R -v /data/data
After this you can close terminal and you will have working app which you have restored with titanium.
Remember you have to follow this everytime you restore data from titanium backup.
To All My Dr.Ketan ROM users, If you can't hold your horse, proceed with this and you will be able to flash my update based on this ROM most probable without wipe, Can't promise but may be before week end.
Reports coming Note3 packages from titoo doesn't working
Click to expand...
Click to collapse
Enjoy latest preofficial ROM

AOSP Theme for this ROM
Flash with CWM.

reserved too

two more

last

Thank you for all your work mate, I know how anoying is to upload 1.6 GB every time

Should we wait for this or continue with your custom rom since it has all N3 stuff and features..since its new so i guess it wont have all features and especially air command.
I am asking this because my bandwidth wont allow me to download after 15gb and i've already used 13gb(dr.ketan's custom rom is already in downlaoding queue)

#Respect
We will reading OP very clearly Before flash it. We understand the risk factor.. Heartfelt thanks bro.. No words to express our feeling .

Seems way too risky with KNOX integrated into this.

if you get cold feet after flashing mj2 rom before entering download mode to flash the new bootloader you can just get back into phillz recovery and restore your last nan i guess,....you have time to decide till then

Mj2? There was a leak I missed?

Thx u very much! Our team still w8 for u @namfat

this is kind of scary. never happen to me before. i was excited to try out the new leak, but having read dr's instruction. i felt uneasy...feels like having an icrap device which can't be downgraded either...

My only mumbling in my head now is..."will the current Note 3 mods work on this pre-release?

There is no reason for not to work

When Samsung will release Kernel Source for this 4.3?

SandeepEmekar said:
When Samsung will release Kernel Source for this 4.3?
Click to expand...
Click to collapse
They need to release 4.3 first ^^
Sent from my GT-N7100 using XDA Premium 4 mobile app

Moe5508 said:
My only mumbling in my head now is..."will the current Note 3 mods work on this pre-release?
Click to expand...
Click to collapse
its working fine. i have already test it

63%

edan1979 said:
its working fine. i have already test it
Click to expand...
Click to collapse
Any difference way to install with MI6 version ? or the same ?
And u try to take some mod with xposed modules, these work well or not :good:
And @dr.ketan what's about ur mod for MI6, it still working well ?

[NotBooting][Dev]TekROM - D850 - Stock 20f - Lollipop - Deodex/Root/Busybox

NEW THINGS ARE COMING. KEEP AN EYE OUT.​
Hello!
I have taken the system.img and boot.img from the flashable zip for 20f that @autoprime made and made a ROM base. It is prerooted, deodexed, has busybox, and has support for ArchiDroid Init.d (basically Init.d found in the ROM, not the kernel). It should be ready to flash as is, but a more experienced dev may want to look through my updater-script. It was created using ArchiKitchen (Busybox and ArchiDroid Init.d) and JoelDroid Batch Deodexer (Deodex system apps, priv-apps, and framework). Please flash with caution. I believe everything is kosher, but I haven't attempted to flash it myself. Just like with autoprime's flashable zip, please flash the modem before flashing this if you are upgrading from KitKat. Feel free to use this as your ROM base, just give me credit if you use it.
It's been pointed out to me that I didn't mention whether it was debloated or not. I ran the archi and romcleaner debloat scripts found in ArchiKitchen on it. I am not sure if this wiped the at&t specific apps or not. I also believe Carrier IQ is still enabled. I wasn't sure how to clean Carrier IQ out.
The Q&A thread is here. Not sure why it isn't accessible from the bar at the top like usual.
Instructions for flashing:
REMEMBER TO MAKE A BACKUP!
1a. If coming for KitKat or AOSP Lollipop ROM, wipe data/facory reset and wipe system.
1b. If already on stock Lollipop, dirty flash SHOULD be ok.
2. Wipe Cache and Dalvik Cache (optional).
3. If coming from KitKat, flash updated modem for 20f.
4. Flash ROM.
5. Rewipe Cache and Dalvik Cache (optional).
6. Reboot to system.
To fix issues with xposed, after flashing the xposed zip, download and flash the zip here to stop the Force closes. Alternatively you can freeze quick circle and the weather widget apps prior to flashing xposed.
Links: AndroidFileHost - Mega
Credit:
@autoprime - His flashable zip of .img files
@JustArchi - His kitchen
@joeldroid - His batch deodexer for lollipop
@Unjustified Dev - His root method for G3 stock lollipop
whoever dumped the .img files for the lollipop build
XDA:DevDB Information
TekROM, ROM for the AT&T LG G3
Contributors
TekGadgt, cmulk, that-squirrel
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: D85020f modem
Based On: Stock D85020f
Version Information
Status: Testing
Created 2015-03-16
Last Updated 2015-03-26

Reserved
Looking for anyone that has some dev experience and might want to work on this with me. Just PM me if interested.
Also, if anyone tests this before I get a chance to. Would you please report back here? and if it boots fine, please PM me screenshots to add to the database.

Reserved

Thank you for the work, excited to see lollipop development take off

Is it a debloated stock?

ski21 said:
Is it a debloated stock?
Click to expand...
Click to collapse
I ran the ArchiKitchen debloat scripts on it, but I'm not sure what all it killed off. I completely forgot to check that. Sorry. Will make a note on the OP.

sick a new stock rom, any extra added tweaks added to it?

omaralkha99 said:
sick a new stock rom, any extra added tweaks added to it?
Click to expand...
Click to collapse
Not really. I'm not a true dev per say. I just set this up as a base for other devs to use. got the basic stuff out of the way. As I mentioned in the OP. I haven't flashed this yet, so exercise caution when flashing. Everything should be fine, but it does include the boot.img, so if everything isn't proper, it may be bad. Either way, if you decide to flash, please make a backup before and keep the KitKat restore file readily available.

TekGadgt said:
Not really. I'm not a true dev per say. I just set this up as a base for other devs to use. got the basic stuff out of the way. As I mentioned in the OP. I haven't flashed this yet, so exercise caution when flashing. Everything should be fine, but it does include the boot.img, so if everything isn't proper, it may be bad. Either way, if you decide to flash, please make a backup before and keep the KitKat restore file readily available.
Click to expand...
Click to collapse
Well good work anywyas, though im not going to flash till some one tries it out first. I dont want to go through headaches if it doesnt flash correctly. Also Im glad we have a new developer, just keep learning and add great stuff to this rom if u figure out. Good luck

omaralkha99 said:
Well good work anywyas, though im not going to flash till some one tries it out first. I dont want to go through headaches if it doesnt flash correctly. Also Im glad we have a new developer, just keep learning and add great stuff to this rom if u figure out. Good luck
Click to expand...
Click to collapse
I've been around for a while now. Attempted several large projects, but usually ran out of time. As such, I generally only deodex and such for other devs to use, but if I can find the time, I will definitely try to expand this. I will also post a truly debloated version at some point. I might attempt to flash it soon. It only affects system and boot.img, so if the boot.img is set to extract to the proper block (I checked against my own D850 for the proper mount block), everything should go fine.

i will flash and see wish me good luck..Lol

keeps boring into twrp
Tried flashing this and kept on booting into to recovery.

vampyro said:
i will flash and see wish me good luck..Lol
Click to expand...
Click to collapse
i tried just dont boot... sent me back to twrp recovery

vampyro said:
i tried just dont boot... sent me back to twrp recovery
Click to expand...
Click to collapse
Same

elry567 said:
Same
Click to expand...
Click to collapse
vampyro said:
i tried just dont boot... sent me back to twrp recovery
Click to expand...
Click to collapse
wsherman1983 said:
Tried flashing this and kept on booting into to recovery.
Click to expand...
Click to collapse
I did warn that it was untested and that I would prefer if someone checked through my stuff first. I will look in to fixing the issues as soon as I can. Any way someone can get a Logcat?

Sounds like a boot image issue.

TekGadgt said:
I did warn that it was untested and that I would prefer if someone checked through my stuff first. I will look in to fixing the issues as soon as I can. Any way someone can get a Logcat?
Click to expand...
Click to collapse
TekGadgt. Thanks for doing this. I look forward to a working release.

This same issue happened when folks with a custom recovery tried to take the ota for Stock Lollipop. I wonder if the same fix for that will work here.
*** edit** Here is the link http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508

derekedw said:
Sounds like a boot image issue.
Click to expand...
Click to collapse
That's odd and somewhat unlikely, since I flashed the exact same one from autoprimes system.img and boot.img. Did everyone that flashed upload their modem as well? And did everyone wipe properly?

Dretti said:
This same issue happened when folks with a custom recovery tried to take the ota for Stock Lollipop. I wonder if the same fix for that will work here.
*** edit** Here is the link http://forum.xda-developers.com/lg-g3/development/fix-stuck-custom-recovery-trying-ota-t2907508
Click to expand...
Click to collapse
I gave this a shot and it did hang at the LG logo with blinking l.e.d. a little longer, but still returned to recovery

[SOLVED] - Failed zip update instalation via TWRP - wrong build issue

Hi all
I have a strange situation with flashing zip update via TWRP.
I'm on YNG1TAS17L and this morning i downloaded update from http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-e816218e8a-to-30bd462d41-signed.zip. This update provides fixes for the following items: Touchscreen sensitivity; Bluetooth connectivity with several in-car systems; MMS sending on several carriers. So, when I tried to flash it I got an error message that i have 4.4.2 build. As on screenshot. Checked build.prop, I'm on 5.0.2. I understand that i can flash a full rom from http://builds.cyngn.com/cyanogen-os...0bd462d41/cm-12.0-YNG1TAS2I3-bacon-signed.zip, but i was wondering from where updater script got info about 4.4.2 build so that i can avoid such issues in future. Thanks in advance.

Loreane Van Daal said:
Hi all
I have a strange situation with flashing zip update via TWRP.
I'm on YNG1TAS17L and this morning i downloaded update from http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-e816218e8a-to-30bd462d41-signed.zip. This update provides fixes for the following items: Touchscreen sensitivity; Bluetooth connectivity with several in-car systems; MMS sending on several carriers. So, when I tried to flash it I got an error message that i have 4.4.2 build. As on screenshot. Checked build.prop, I'm on 5.0.2. I understand that i can flash a full rom from http://builds.cyngn.com/cyanogen-os...0bd462d41/cm-12.0-YNG1TAS2I3-bacon-signed.zip, but i was wondering from where updater script got info about 4.4.2 build so that i can avoid such issues in future. Thanks in advance.
Click to expand...
Click to collapse
I am not sure about where is the footprint info located (maybe others can shed some light), but if you are updating or flashing to a new ROM without the "official" package (flashing zip files), the fingerprint remains.
For example, I am using 5.1.1 Exodus, but in TWRP an TB I have bacon-user 5.0.2 LRX22G, while in build.prop it is 5.1.1 LMY48B
EDIT: So it is the custom recovery. Anyways, you can not install the official Cyanogen OTA from TWRP as it also expects Cyanogen recovery.

Loreane Van Daal said:
Hi all
I have a strange situation with flashing zip update via TWRP.
I'm on YNG1TAS17L and this morning i downloaded update from http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-e816218e8a-to-30bd462d41-signed.zip. This update provides fixes for the following items: Touchscreen sensitivity; Bluetooth connectivity with several in-car systems; MMS sending on several carriers. So, when I tried to flash it I got an error message that i have 4.4.2 build. As on screenshot. Checked build.prop, I'm on 5.0.2. I understand that i can flash a full rom from http://builds.cyngn.com/cyanogen-os...0bd462d41/cm-12.0-YNG1TAS2I3-bacon-signed.zip, but i was wondering from where updater script got info about 4.4.2 build so that i can avoid such issues in future. Thanks in advance.
Click to expand...
Click to collapse
PLEASE UPDATE YOUR BUILD.PROP HERE...WILL CHECK AND UPDATE YOU THE PROBLEM
Sent from my A0001 using XDA Free mobile app

ansaziz777 said:
PLEASE UPDATE YOUR BUILD.PROP HERE...WILL CHECK AND UPDATE YOU THE PROBLEM
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
If you think to post build.prop line those are this two
°ro.build.description=bacon-user 5.0.2 LRX22G YNG1TAS2I3 release-keys
°ro.build.fingerprint=oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys
But as @davebugyi explained it's recovery fingetprint it has nothing to do with build.prop. So for this issue we have to use stock recovery and than flash OTA. Than, optionaly, re-flash TWRP.
As you can see, i have updated build by flashing full rom, it was faster solution. Than, as being curious by default, restored nand, made all steps from above and OTA went through.

I get the same when I try and use the incremental zip. I am just going to dirty flash the full version instead.

indesisiv said:
I get the same when I try and use the incremental zip. I am just going to dirty flash the full version instead.
Click to expand...
Click to collapse
Yup, as i did at first. Just dirty flashed full rom, reflashed TWRP 2.8.6.0, flashed xposed FW and SuperSu. After optimising apps all is ok. Regarding root, it can't be done from stock recovery. This info is for those who prefere longer path with flashing stock recovery.

indesisiv said:
I get the same when I try and use the incremental zip. I am just going to dirty flash the full version instead.
Click to expand...
Click to collapse
But as @davebugyi explained it's recovery fingetprint it has nothing to do with build.prop. So for this issue we have to use stock recovery and than flash OTA. Than, optionaly, re-flash TWRP.
As you can see, i have updated build by flashing full rom, it was faster solution. Than, as being curious by default, restored nand, made all steps from above and OTA went through.[/QUOTE]
Loreane Van Daal said:
Script from zip:
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys" ||
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys" ||
Yours:
ro.build.description=bacon-user 5.0.2 LRX22G YNG1TAS2I3 release-keys
°ro.build.fingerprint=oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys
This incremental update is for YNG1TAS17L, It seems you have the latest,check both get prop and yours are not same...
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse

Clarification
ansaziz777 said:
But as @davebugyi explained it's recovery fingetprint it has nothing to do with build.prop. So for this issue we have to use stock recovery and than flash OTA. Than, optionaly, re-flash TWRP.
As you can see, i have updated build by flashing full rom, it was faster solution. Than, as being curious by default, restored nand, made all steps from above and OTA went through.
Click to expand...
Click to collapse
Loreane Van Daal said:
Script from zip:
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys" ||
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys" ||
Yours:
ro.build.description=bacon-user 5.0.2 LRX22G YNG1TAS2I3 release-keys
°ro.build.fingerprint=oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys
This incremental update is for YNG1TAS17L, It seems you have the latest,check both get prop and yours are not same...
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Seems that we got lost in translations or in misreading. I know that I have latest. Now. As I said, I have updated build by flashing full ROM. In OP I stated that I have YNG1TAS17L, and that was before update. So I posted updated build.prop lines and told you that I have updated ("As you can see, i have updated build by flashing full rom"). Only difference in those lines would be YNG1TAS17L instead of YNG1TAS2I3. And that don't have anything to do with recovery fingerprint.

Loreane Van Daal said:
Seems that we got lost in translations or in misreading. I know that I have latest. Now. As I said, I have updated build by flashing full ROM. In OP I stated that I have YNG1TAS17L, and that was before update. So I posted updated build.prop lines and told you that I have updated ("As you can see, i have updated build by flashing full rom"). Only difference in those lines would be YNG1TAS17L instead of YNG1TAS2I3. And that don't have anything to do with recovery fingerprint.
Click to expand...
Click to collapse
Its for avoiding the conflicts...
Scripts will check the build.prop to avoid problems...it has something to do with build.prop
Getprop..command itself for pulling the build.prop contents
Sent from my A0001 using XDA Free mobile app

I know it's late for the solution, but it's ROM dependent and some lines are actually in build.prop are responsible for the issue marked as DO NOT PARSE. They can be edited, but may cause unwanted system behavior (I Guess that's why they are commented as do not parse).
On the other hand, you can just edit the updater script in the update file and comment out the check for version.

davebugyi said:
I know it's late for the solution, but it's ROM dependent and some lines are actually in build.prop are responsible for the issue marked as DO NOT PARSE. They can be edited, but may cause unwanted system behavior (I Guess that's why they are commented as do not parse).
On the other hand, you can just edit the updater script in the update file and comment out the check for version.
Click to expand...
Click to collapse
Those lines i pasted are from "do not parse" part. I have searched build.prop and there were no mentions of 4.4.2. Also, on Oneplus one forums there is a thread that explains that recovery update dependencies. Since we don't update stock recovery script is reading the last one's fingerprint. That's why we have that package error.
Just checked that with Nexus 7, same thing is when I try to flash 5.1.1 OTA. When I flashed appropriate recovery factory image OTA can pass through. With same build.prop.
OFC, editing dependencies part in script is always a solution

I have reverted to stock recovery but still having the same error, besides flashing full rom, any other ways?

ansaziz777 said:
But as @davebugyi explained it's recovery fingetprint it has nothing to do with build.prop. So for this issue we have to use stock recovery and than flash OTA. Than, optionaly, re-flash TWRP.
As you can see, i have updated build by flashing full rom, it was faster solution. Than, as being curious by default, restored nand, made all steps from above and OTA went through.
Click to expand...
Click to collapse
Loreane Van Daal said:
Script from zip:
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys" ||
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys" ||
Yours:
ro.build.description=bacon-user 5.0.2 LRX22G YNG1TAS2I3 release-keys
°ro.build.fingerprint=oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys
This incremental update is for YNG1TAS17L, It seems you have the latest,check both get prop and yours are not same...
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Hi
so deleting the lines
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys" ||
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys" ||
abort("Package expects build fingerprint of oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys or oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
from the updater-script file should solve the problem ?

epynic said:
Hi
so deleting the lines
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys" ||
getprop("ro.build.fingerprint") == "oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys" ||
abort("Package expects build fingerprint of oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS17L:user/release-keys or oneplus/bacon/A0001:5.0.2/LRX22G/YNG1TAS2I3:user/release-keys; this device has " + getprop("ro.build.fingerprint") + ".");
from the updater-script file should solve the problem ?
Click to expand...
Click to collapse
Copy your build.prop lines here and it Will work...
DO AT YOUR RISK!..BACKUP YOUR ROM BEFORE TRYING THIS FOR AVOID DATA LOSS!
Sent from my A0001 using XDA Free mobile app

Recap
Hi all,
Though I have read all the posts above, I'd rather check with you before screwing up my phone.
My OPO is on 11.0-XNPH44S, TWRP is installed and phone rooted. I would like to update it to YNG1TAS2I3 (I use the full one, not the incremental) but when I do it, I get the message E:Error executing updater binary in zip ' /sdcard/cm-12.0-YNG1TAS2I3-bacon-signed.zip'
If I got it right, I does not work because I am not using the official recovery.
So there are 2 solutions :
-reinstall the official recovery, install the update, then optionnaly flash TWRP again and root again
-change the build.prop file to make it work with TWRP (but I did not understand what I had to change exactly)
Is this right?
Thanks in advance guys

mikemyerslyon said:
Hi all,
Though I have read all the posts above, I'd rather check with you before screwing up my phone.
My OPO is on 11.0-XNPH44S, TWRP is installed and phone rooted. I would like to update it to YNG1TAS2I3 (I use the full one, not the incremental) but when I do it, I get the message E:Error executing updater binary in zip ' /sdcard/cm-12.0-YNG1TAS2I3-bacon-signed.zip'
If I got it right, I does not work because I am not using the official recovery.
So there are 2 solutions :
-reinstall the official recovery, install the update, then optionnaly flash TWRP again and root again
-change the build.prop file to make it work with TWRP (but I did not understand what I had to change exactly)
Is this right?
Thanks in advance guys
Click to expand...
Click to collapse
If you download the full ROM, it can be installed from TWRP. What version do you have ? (Try using 2.8.6.0). It also can be a corrupted download.

That was it !
davebugyi said:
If you download the full ROM, it can be installed from TWRP. What version do you have ? (Try using 2.8.6.0). It also can be a corrupted download.
Click to expand...
Click to collapse
You nailed it ! I was using TWRP 2.8.0.1
It worked. I am now running Lollipop
Thank you !

I am also suffering with same problems. Unable to update cm12 incremental. Plz helhp me out what to do.

DISCONTINUED [VZW_Stock Based TW Rom][5.0 Lollipop BOK3 Build Odex/Deodex]

Stock Verizon 5.0 BOK3 Based Lollipop Rom
Updated: 2-25-16
I added a new zip that uses an options.prop that is located in the zip. You can extract this and use notepad++ to edit it to add the features you want then copy the options.prop to the root of your sdcard or internal storage
You have the option for odexed or deodexed rom
You can choose to debloat
You can choose to add the features listed below or you can keep totaly stock
This flashes an untouched system.img so this can also be used to get back hd calling if you lost it on a rom flash
Here is an example of how to use options.prop You simply change the values in red
Code:
###Deodex Rom###
# Yes=1 Deodex Rom #
# No=0 Leave Rom Stock #
deodexed.rom=[COLOR="Red"]0[/COLOR]
###Debloat Rom###
# Yes=1 Debloat Rom #
# No=0 Leave Rom Stock #
debloat.rom=[COLOR="red"]0[/COLOR]
###Mod Rom To Add Some Features###
# Yes=1 Mod Rom #
# No=0 Leave Rom Stock #
mod.rom=[COLOR="red"]0[/COLOR]
###Remove Knox From Rom###
# Yes=1 Remove Knox #
# No=0 Leave Rom Stock #
removeknox.rom=[COLOR="red"]1[/COLOR]
###Add init.d Support To Rom###
# Yes=1 Add init.d support #
# No=0 Leave Rom Stock #
initd.rom=[COLOR="red"]1[/COLOR]
Features (Extra Mods Must Be Chosen In options.prop)
Rooted/Busybox/Init.d
Deodexed (If you Choose To)
Debloated (If YouChoose To)
Fixed Tethering
Fixed Private Mode
Added SBrowser
SD Card Fix
Device Status Official
Updated All apps
Super SU 2.67 Beta
Flashlight Toggle
Call Recording
Call Message Blocking
Call Button added to call logs
Download Rom
VZW_BOK3_ODEX_DEODEX_V2.zip New Version!
VZW_BOK3_STOCK_ROM_DEODEXED.zip
Paches/Updates
Extra_toggles.zip Use To Add Flashlight Toggle
SafeStrap Flashable Firmware Update For This Rom
This will Update Modem And NON-HLOS.bin And Kernel. No bootloaders will be updated, so device can still be downgraded.
BOK3_Firmware_No_Bootloaders.zip
SafeStrap Flashable Kernel For This Rom
G900V_OK3_Stock_KERNEL_SafeStrap-Flashable.zip
Odin Flashable Full Retail Tar Image With BOD5 Bootloaders
If your comming from KitKat or cannot get HD Calling working you may have to flash this VZW_BOK3_RETAIL_TAR_IMAGE_WITH_BOD5_BOOTLOADERS.tar.zip then activated HD calling then Flash NCG_Rescue_Tar_And_NCG_For_Root.tar and start over with rooting procedure
Install And Upgrade Instructions
All Firmwares and all Instructions for Upgrading from KitKat Or Lollipop rom can be found Here
XDA:DevDB Information
S5 Lollipop 5.0 Rom, ROM for the Verizon Samsung Galaxy S 5
Contributors
jrkruse
ROM OS Version: 5.0.x Lollipop
ROM Firmware Required: BOC4 or later
Version Information
Status: Stable
Created 2015-12-29
Last Updated 2015-12-28

saved

i am looking forward in trying this out
I got the download working now

I literally just flashed your BOG5 today...can I ask what this has that one didn't?

bryank29 said:
I literally just flashed your BOG5 today...can I ask what this has that one didn't?
Click to expand...
Click to collapse
Just some security fixes other than that they are pretty much the same

So if my goal is simply to access safestrap, I run the Safestrap Recovery, it reboots, I do what I need (such as make a nandroid), then flash the Safestrap safe kernel, reboot and everything remains fine?

bryank29 said:
So if my goal is simply to access safestrap, I run the Safestrap Recovery, it reboots, I do what I need (such as make a nandroid), then flash the Safestrap safe kernel, reboot and everything remains fine?
Click to expand...
Click to collapse
In my rom its called Lollipop Safestrap just click on it and hit Recovery Reboot it will take you right to Safestrap. Then like you said, do whatever then flash the safestrap flashable kernel that matches your rom and it will reboot back to rom

jrkruse said:
In my rom its called Lollipop Safestrap just click on it and hit Recovery Reboot it will take you right to Safestrap. Then like you said, do whatever then flash the safestrap flashable kernel that matches your rom and it will reboot back to rom
Click to expand...
Click to collapse
Thank you.
One last question (hopefully). I am running ARMv7. What version of Xposed should we be running? According to this: http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118 Arter97's sdk21 version. Is that accurate? Basically this? http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
When upgrading your roms, is a cache / dalvik cache wipe all that is needed? When I went from BA08 to BOG5 I went ahead and wiped data, system, and the caches.

It's my Birthday and this is a wonderful present to start out with.:silly:

@jrkruse You are a damn beast with these ROM's Thanks so much for everything you do here with the community. Are you planning on doing a "dark it up" theme for this? I was really hoping for an all black and white theme. Black settings / white text type of thing. Also, how hard would it be to get a nexus system UI running on this ROM that can use layers? Kind of like the Freedom ROM?

Sharpie603 said:
@jrkruse You are a damn beast with these ROM's Thanks so much for everything you do here with the community. Are you planning on doing a "dark it up" theme for this? I was really hoping for an all black and white theme. Black settings / white text type of thing. Also, how hard would it be to get a nexus system UI running on this ROM that can use layers? Kind of like the Freedom ROM?
Click to expand...
Click to collapse
Themes from bog5 roms should still work. I will not be doing as much with S5 as I have moved on to nexus 6P

jrkruse said:
Themes from bog5 roms should still work. I will not be doing as much with S5 as I have moved on to nexus 6P
Click to expand...
Click to collapse
[emoji22] [emoji22] Looks like it's time for me to upgrade. ..
Sent from my SM-G900V using Tapatalk

man im on like my 15th attempt to flash a Lollipop rom where HD calling works. I keep going back to KK enabling it, making sure it works and then as soon as I try to flash any LP rom it goes back to saying to "upgrade to HD calling". I dont know what else i could do differently! Any suggestions?
Edit- im posting this here because i just flashed this rom, just making that clear
---------- Post added at 10:40 PM ---------- Previous post was at 09:47 PM ----------
jrkruse said:
Odin Flashable Full Retail Tar Image With BOD5 Bootloaders
If your comming from KitKat or cannot get HD Calling working you may have to flash this VZW_BOK3_RETAIL_TAR_IMAGE_WITH_BOD5_BOOTLOADERS.tar.zip then activated HD calling then Flash NCG_Rescue_Tar_And_NCG_For_Root.tar and start over with rooting procedure
Click to expand...
Click to collapse
i tried doing this but again its "ugrade your service to HD calling!"

bryank29 said:
Thank you.
One last question (hopefully). I am running ARMv7. What version of Xposed should we be running? According to this: http://forum.xda-developers.com/xposed/official-xposed-lollipop-t3030118 Arter97's sdk21 version. Is that accurate? Basically this? http://forum.xda-developers.com/xposed/unofficial-xposed-samsung-lollipop-t3113463
When upgrading your roms, is a cache / dalvik cache wipe all that is needed? When I went from BA08 to BOG5 I went ahead and wiped data, system, and the caches.
Click to expand...
Click to collapse
This is the one I installed:
xposed-v75-sdk21-arm-arter97-snapdragon.zip
Been working.
Sent from my SM-G900V using Tapatalk

damagi123 said:
man im on like my 15th attempt to flash a Lollipop rom where HD calling works. I keep going back to KK enabling it, making sure it works and then as soon as I try to flash any LP rom it goes back to saying to "upgrade to HD calling". I dont know what else i could do differently! Any suggestions?
Edit- im posting this here because i just flashed this rom, just making that clear
---------- Post added at 10:40 PM ---------- Previous post was at 09:47 PM ----------
i tried doing this but again its "ugrade your service to HD calling!"
Click to expand...
Click to collapse
After flashing the bok3 full factory image from the op when the phone boots to the red Verizon screen pull the battery reboot back to stock recovery wipe data. The reboot and set up phone HD calling will then work. After you make a test call just to make sure you can begin the root process

jrkruse said:
After flashing the bok3 full factory image from the op when the phone boots to the red Verizon screen pull the battery reboot back to stock recovery wipe data. The reboot and set up phone HD calling will then work. After you make a test call just to make sure you can begin the root process
Click to expand...
Click to collapse
did exactly as you described. did not work. still just goes right back to UPGRADE TO HD CALLING! Thanks so much but man this is friggin insane.

damagi123 said:
did exactly as you described. did not work. still just goes right back to UPGRADE TO HD CALLING! Thanks so much but man this is friggin insane.
Click to expand...
Click to collapse
After you Odin bok3 and get HD calling working. Then start over are you restoring anything and what are you using to flash rom safestrap or FF

jrkruse said:
After you Odin bok3 and get HD calling working. Then start over are you restoring anything and what are you using to flash rom safestrap or FF
Click to expand...
Click to collapse
I wasn't restoring anything. I was starting absolutely fresh. I finally got it. here's what I did I pulled my sim while I was powering on and then pulled the battery again. then restarted and it finally worked.

damagi123 said:
I wasn't restoring anything. I was starting absolutely fresh. I finally got it. here's what I did I pulled my sim while I was powering on and then pulled the battery again. then restarted and it finally worked.
Click to expand...
Click to collapse
Im glad it works. The hd calling is a pain some people have a hard time getting it to work. I personally have never had an issue with my phone but I have had problems getting it to work on another persons phone so I can relate to the problem.

If anyone downloaded the odin recovery image VZW_BOK3_RETAIL_TAR_IMAGE_WITH_BOD5_BOOTLOADERS.ta r.zip. It was brought to my attention that recovery.img was missing from tar file. This will not affect anything as the recovery.img did not change .I reuploaded it and it now contains the recovery.img so if you want you can redownload.

[H910][Oreo][Stock][Rooted] AT&T LG V20 Stock Oreo rooted flashable zip

Good Morning
New: Well AT&T updated us to Sept Security patch
here's the new Stock rooted rom > H910_20h_Oreo_full_rooted.zip > https://www.androidfilehost.com/?fid=1322778262904015326
Tested by @darkknight200
i dirty flashed over the 20g rooted setup. It booted up fine and works like normal.
Now have to debloat att apps and restore twrp. This time i used twrp app to restore twrp right in system and it worked properly. Saves the hassle to go into fastboot to push twrp.
All in all those are minor inconveniences, The zip is fine.
Thanks allot man.
Click to expand...
Click to collapse
After @NotYetADev posted his VS995 rooted Oreo We decided to give it a try on the H910.
It's not perfect but it does work. You'll need to Format Data and flash the H910_20g_Oreo_full_rooted.zip + the Newest - H910_mk2000 kernel from recovery-twrp-h910-2018-10-18.img
Your phone will be wiped and updated to Stock rooted Oreo so backup your phone first!
If you have never rooted your H910 you'll need to use the guide here first > https://forum.xda-developers.com/v20/how-to/root-h910-v10m-t3664500
Note: when you get where you would flash 10r just use my rom instead. Don't forget to flash the kernel after the rom
Note2: Flash TWRP again before you reboot (Install / Install Image / recovery-twrp-h910-2018-10-18.img to Recovery
It's also recommended to use the new TWRP for Oreo found here > https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239
Note: you'll have to flash TWRP back to the phone after flashing the rom and kernel because it installs stock recovery.
If you have any problems getting DATA on any sim other than AT&T check this post to fix your APN > https://forum.xda-developers.com/showpost.php?p=79619740&postcount=244
Thanks @StrikerTheHedgefox
After your phone is setup be sure and install the Magisk apk
Hide unlocked Bootloader warning boot screen by 4shared < This removes the ugly pink and black screen on reboot. I tested it and it works great
Huge thanks go to @darkknight200 and @askermk2000 for the Idea and the kernel.

thank u. but does the fingerprint work and what are the bugs if any

Yes fingerprint scanner works
Side note you'll have to flash twrp again
Use this version > https://forum.xda-developers.com/v20/development/recovery-twrp-3-2-1-0-t3720239 and you should have no problems
aminjomaa13 said:
thank u. but does the fingerprint work and what are the bugs if any
Click to expand...
Click to collapse
Sent from my PH-1 using Tapatalk

if i have root then cant i just use flashr or another flashing app for twrp

aminjomaa13 said:
if i have root then cant i just use flashr or another flashing app for twrp
Click to expand...
Click to collapse
I installing twrp img from twrp just after flashing the ROM would do the trick.

if i dont have an at&t sim card ，will this rooted rom restrict some function such as wifispot 。。。。。。

Test flashed this on my h915 device. I have working full data and root and everything works.
Just gotta debloat it myself
running very smooth

zkm15 said:
if i dont have an at&t sim card ，will this rooted rom restrict some function such as wifispot 。。。。。。
Click to expand...
Click to collapse
Its the Stock Oreo rom dump .. only thing changed is a patched_boot.img and the Eng_aboot.img
in fact the original files are in the rom too they just don't get flashed
everything should work as expected

battery life took a hit what are the optimal CPU GPU values to optimize battery without totally crushing performance

anyone else pass both safetynet test on magisk 17.2 on h910 oreo?
It seems to be failing most of the time for me.

aminjomaa13 said:
battery life took a hit what are the optimal CPU GPU values to optimize battery without totally crushing performance
Click to expand...
Click to collapse
this question is better left in the Kernel thread > https://forum.xda-developers.com/v20/development/h918-h910-us996-ucl-mk2000-kernel-t3708330
I never mess with kernel setting aside from the Screen settings

darkknight200 said:
anyone else pass both safetynet test on magisk 17.2 on h910 oreo?
It seems to be failing most of the time for me.
Click to expand...
Click to collapse
safetynet test for non at&t sim card ？ it is a problem on android N .

Awesome! Glad this works on other devices! Good job, XDA!

NotYetADev said:
Awesome! Glad this works on other devices! Good job, XDA!
Click to expand...
Click to collapse
ya the zip method you did with modifying only 2 files in the whole firmware should work on all other dirtysanta devices.
Edit:
i re-flashed the h910 oreo and setup and debloated everything again. Now I am passing safetynet with no problems and certified device. very weird.
One thing to note, this is on the early build of Oreo TWRP that I was able to flash properly vs using nouget twrp the first 2 flashes that gave me bugs each time.

darkknight200 said:
ya the zip method you did with modifying only 2 files in the whole firmware should work on all other dirtysanta devices.
Edit:
i re-flashed the h910 oreo and setup and debloated everything again. Now I am passing safetynet with no problems and certified device. very weird.
One thing to note, this is on the early build of Oreo TWRP that I was able to flash properly vs using nouget twrp the first 2 flashes that gave me bugs each time.
Click to expand...
Click to collapse
using Oreo TWRP flash this zip will pass the saftynet test ? it is quite a problem on
android N ，it will disable the wifispot function.

OP, I love you.
If we already have the engineering aboot and TWRP flashed, can we just flash this right over (with a data/system wipe)?
I love SuperROM but I need Wi-Fi Calling to work.
EDIT: I'm an idiot, I misread your instructions. Am I correct in understanding that this is just the stock AT&T Oreo image with aboot and boot swapped out?

sheik124 said:
OP, I love you.
If we already have the engineering aboot and TWRP flashed, can we just flash this right over (with a data/system wipe)?
I love SuperROM but I need Wi-Fi Calling to work
Click to expand...
Click to collapse
yes if you are coming from rooted h910 nougat rom with twrp, you can flash this h910 oreo zip with no problem.
All the bloat from att should be there when u boot up so wifi calling should work.

sheik124 said:
OP, I love you.
If we already have the engineering aboot and TWRP flashed, can we just flash this right over (with a data/system wipe)?
I love SuperROM but I need Wi-Fi Calling to work.
EDIT: I'm an idiot, I misread your instructions. Am I correct in understanding that this is just the stock AT&T Oreo image with aboot and boot swapped out?
Click to expand...
Click to collapse
darkknight200 said:
yes if you are coming from rooted h910 nougat rom with twrp, you can flash this h910 oreo zip with no problem.
All the bloat from att should be there when u boot up so wifi calling should work.
Click to expand...
Click to collapse
Yes just 2 files changed flash right over Nougat > I recommend you use this version of TWRP > https://s3.amazonaws.com/phoenix591/us996/recovery-twrp-us996-2018-09-23.img
it's tested by @darkknight200

clsA said:
Yes just 2 files changed flash right over Nougat > I recommend you use this version of TWRP > https://s3.amazonaws.com/phoenix591/us996/recovery-twrp-us996-2018-09-23.img
it's tested by @darkknight200
Click to expand...
Click to collapse
Awesome, downloading it now. Can you confirm a cpl things?
mk2000 kernel means that we can continue using exFAT on micro SD.
Right now I have unencrypted internal and external storage, this keeps it all the same.
Updates baseband/modem to the radio that came out with Oreo.
Will post results once I'm all set back up. I was literally about to selectively flash back to stock v10v, keep TWRP and root, let it download the OTA, and then try to get updated. This is easier.

sheik124 said:
Awesome, downloading it now. Can you confirm a cpl things?
mk2000 kernel means that we can continue using exFAT on micro SD.
Right now I have unencrypted internal and external storage, this keeps it all the same.
Updates baseband/modem to the radio that came out with Oreo.
Will post results once I'm all set back up. I was literally about to selectively flash back to stock v10v, keep TWRP and root, let it download the OTA, and then try to get updated. This is easier.
Click to expand...
Click to collapse
Yes mk2k Oreo still let's u use exfat.
The zip will update all partition besides the 2 described above. So you will be on Oreo baseband modem.