Develop Bugs

[ROM][UNOFFICIAL][4.4.3][D2TMO/D2LTE] Omni Rom for all D2s [Multi-window][OpenDelta]

This is an unofficial build of Omni Rom based on KitKit 4.4.2. There is no official support for the d2 variants. Props to androidsftw for picking apart what was needed for our d2s.
I am not the dev of this rom, all I did was add in necessary device/vendor/d2 files for d2. This is not a port, everything has been built from source.
As with all things root, I am not responsible for anything that happens while flashing this rom. You take responsibility for your actions. Nandroid is your friend.
----------------------------------
Downloads:
Omni Rom for the D2LTE - Droidhype Roms
GAPPS 4.4.2 - PA 0-Day
SuperSU - Chainfire
Kernel (optional) - BMS
----------------------------------
Installing for the first time? Grab the newest full zip from the D2LTE directory. For future updates, just go to Settings -> System Updates and let the magic happen.
HOW TO INSTALL
1. Factory Data reset
2. Wipe System/Data/Dalvik/Cache
3. Install ROM zip from Sdcard
4. Install GAPPS zip from Sdcard
5. Install SuperSU from Sdcard
6. Reboot to home screen to confirm good flash
7. (Optional) Reboot to recovery and flash kernel
TO USE DELTAS, YOU HAVE TO USE TWRP OR PHILZ RECOVERY. CWM WILL NOT WORK BECAUSE IT DISABLES SCRIPTING CAPABILITIES BY DEFAULT. If there's anything that you want the updater to flash automatically after it flashes your update, put the file(s) in the FlashAfterUpdate directory inside your Opendelta folder in your internal storage.
Join the BMS G+ community which will have quicker release info in the future for all things BMS and roms.
Enjoy!
Cherry-picks:
- Multi-window
This build is unofficial, so I don't exactly carry around a changelog. However, you can always check cmxlog for omni and see what's been changed with each version of one of their nightlies. It won't be exact as some have specific device merges, but it will give you a good idea. The dates on my builds will correspond with the officials listed on cmxlog.
You can also check their gerrit or git to see what's been merged.
This question gets posted pretty frequently so if some users could please bookmark this post, we can just repost it when needed. Here are all the links you can peruse for your changelog/update enjoyment.
cmxlog - http://omni.cmxlog.com/4.4/
gerrit - https://gerrit.omnirom.org/#/q/status:merged,n,z
github - https://github.com/omnirom/
G+ - https://plus.google.com/u/0/communities/102450203113748251717
XDA - http://forum.xda-developers.com/omni
XDA:DevDB Information
Omni Rom for the d2tmo, a ROM for the T-Mobile Samsung Galaxy S III
Contributors
GideonX
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: Omni
Version Information
Status: Beta
Created 2014-02-18
Last Updated 2014-02-18

Reserved

FIRST!
Thanks, Will try!

2nd haha anyways will give this a try when i get home c:
Sent from my SGH-T999 using xda app-developers app

Hell yes finally, thanks for this for sure
Sent from my SGH-T999 using Tapatalk

So what I'm getting is that a d2lte build will work on all d2 variants, no updater-script editing required?

Screenies??

As GideonX has said, these builds support all the d2 variants. Everything is automatically done during flashing. You don't need to do anything but flash like normal

downloaded and working
Except for su recconising apps. have tried manual install also just can't seem to make it work. appreciate this rom otherwise. will keep trying. thanks:good:

Is anyone having problems with swipe typing?

trofmoc said:
Except for su recconising apps. have tried manual install also just can't seem to make it work. appreciate this rom otherwise. will keep trying. thanks:good:
Click to expand...
Click to collapse
4.4 needs special twrp jyst in case you restored back on to tw or never updated.
Anyways seems like the rom had little to offer in my personal opinion. I decided to just go an restore previous rom instead
Sent from my SGH-T999 using xda app-developers app

I just installed the Rom! Working great! Thank you.
Wp4Wp4:good:

twrex82 said:
Is anyone having problems with swipe typing?
Click to expand...
Click to collapse
Try PA's gapps. If you're talking about how no letters actually get inputted on the screen even though it is showing the swipe, then that's what you need.
http://forum.xda-developers.com/showthread.php?t=2397942

New D2LTE 2014-02-21 Build - http://goo.gl/zJwFzA
- Had some opendelta issues. Please flash this entire zip this time around, thanks.
- Screen rotation is in settings now.

where are the screen shots for this rom?

Thank you for this rom and one quick question, can't Sync facebook contacts info anymore on the last build?
"Envoyé depuis mon SGH-T999 avec Tapatalk"

Can someone on tmobile verify uploading pictures and video works with this rom in instagram? it may be a kitkat issue with instagram but previously I have gotten a lot of freezes, FC, and reboots while trying to upload video. anybody willing to test this on the latest release?

Dude sorry but are u spamming the threads with the same question?
Sent from my SGH-T999 using xda app-developers app

Anyone have OpenDelta mess up their phone? Every time I booted into recovery it would install the update. Then lost root and my gapps. It was hell trying to get it all back.

Purplezigar said:
Anyone have OpenDelta mess up their phone? Every time I booted into recovery it would install the update. Then lost root and my gapps. It was hell trying to get it all back.
Click to expand...
Click to collapse
I'm using Philz recovery, opendelta updates work as expected. What's your setup?

[ROM][5.1][Flounder] Pure AOSP 3/18/15 [LMY47D]

Hello! I'll be posting pure AOSP builds whenever there are new versions of android released (providing I have the time).
If you choose to use these builds, please ensure you have unlocked your bootloader and have custom recovery installed. I have also noticed that TWRP seems a little wonky at this point, so in order for me to flash it correctly, I had to wipe, then restart recovery, then flash. Hope that's not the case for everyone else.
3/18/15
Added ability to change DPI.
3/15/15
No longer messes with recovery at all. Bluetooth working, data does not force encrypt.
3/13/15
Android 5.1.0_r1 (LMY47D)
This release will wipe your recovery. If anyone needs this changed let me know and I will build another.
1/3/2015
Android 5.0.2_r1 (LRX22G)
Data is now encryptable, meaning your unencrypted data should stick going forward.
Included my own build of stock kernel with Linaro 4.9.3 toolchain.
Fixed bluetooth (thanks Lollipopalooza/Craig)
No longer need to re-flash recovery.
12/6/2014
Android 5.0.1_r1 (LRX22C)
You will need to install separate gapps
You will need to re-flash your custom recovery after you install (you all let me know if I should change this or not, I think I will on future builds)
I am not responsible for anything that happens to your device or to you, yourself while flashing this.
Latest DL Links will be in post #2.
XDA:DevDB Information
Pure AOSP Flounder, ROM for the Nexus 9
Contributors
gchild320
ROM OS Version: 5.0.x Lollipop
Based On: AOSP
Version Information
Status: Stable
Created 2014-12-06
Last Updated 2015-01-03

Downloads
3/18/15
https://www.androidfilehost.com/?fid=95916177934543409
3/15/15
https://www.androidfilehost.com/?fid=95916177934541983
3/13/15
5.1 - https://www.androidfilehost.com/?fid=95916177934540786
1/3/14
Flounder Android 5.0.2_r1 build LRX22G https://www.androidfilehost.com/?fid=95864024717074545

Future FAQ if necessary (let's hope not).

Thank you!!!!
Will test it tomorow
I hope cm12 will build on arm64 soon

Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.

mpmilestogo said:
Just a few questions. What gapps do you recommend? What twrp ? There is the mainline version and the one @USBhost did. Thanks for the ROM!! Really appreciate seeing this show up.
Click to expand...
Click to collapse
I didn't realize that there were two versions of twrp...I used the one from twrp website.

gchild320 said:
I didn't realize that there were two versions of twrp...I used the one from twrp website.
Click to expand...
Click to collapse
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery

USBhost said:
Yep
https://s.basketbuild.com/devs/USBhost/Nexus 9/recovery
I fixed some things
in it
Factory reset will not encrypt data
fixed the device name
look bit better
custom built FIRE-ICE kernel for recovery
Click to expand...
Click to collapse
Hell yes checking this out tomorrow.

build
Awesome !!!! Been waiting for this. How did u build? Last week since their are little options for roms decided to build one on my own and i did a repo sync to Google source but when i did lunch flounder wasn't listed in the build options ?

Flounder still isn't listed just lunch it anyway

Made a video running the ROM. Works very well!!
https://www.youtube.com/watch?v=kVQW-PMepn0

Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware

http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Hiro Nakamura said:
Hello,
can anyone provide a minimal gapps pack? I would like to avoid too much bloatware
Click to expand...
Click to collapse

belair56 said:
http://fitsnugly.euroskank.com/?rom=banks&device=gapps
This maybe what you are looking for.
Click to expand...
Click to collapse
Well i don't think it's 64bit version or is it ?

Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
From what I understand the apps themselves need to be optimized for 64 internally. These are all Google apps so they are if Google did so. As you update from the play store you don't choose if you're running 64bit or not.
As always I can be wrong.

Hiro Nakamura said:
Well i don't think it's 64bit version or is it ?
Click to expand...
Click to collapse
This is actually a great question.

Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.

omvir said:
Adaptive brightness doesn't work. Other than that everything seems to be working.
Edit: Okay so I used an app to look at which sensors were working and which ones weren't... The proximity sensor is not working at all.
Click to expand...
Click to collapse
Adaptive brightness is working flawlessly. Maybe you had a bad download or flash.

gchild320 said:
Flounder still isn't listed just lunch it anyway
Click to expand...
Click to collapse
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?

jlokos said:
I use USBhost's version of TWRP. I tried to flash the rom following directions in OP. It wouldn't flash. First it said for flounder and this device is flounder. Also said something about updater binary. I got this with the other rom also. I tried un-mounting and mounting system, but I still got the error messages. Any ideas?
Click to expand...
Click to collapse
I manually changed it to work with official twrp... Not sure why twrp is calling it volantis instead of flounder but that's why. Also, to get anything to flash in twrp at the moment, I have to reboot recovery after wiping. Hope this helps.

[Answer] Experimental Build Installation Guide (For Those Who Have Missed It).

I Have Seen Some People That Has Missed The Guide About The Lineage OS (LOS) Experimental Installation So I Made This Thread.
Lineage OS Experimental Is For Those Who Doesn't Want To Wipe Their Data (Ect: Installed Apps, Media And More) As You Need To Do With To The LOS Nightly Build. (It Is NOT Recommended To Dirty Flash The Nightly).
DO NOT TRY TO INSTALL LOS 13.0 ON TOP OF CM 14.1!!!
Guide For CM 13/14.1 Official Build To LOS 13/14.1 Official Build:
Install On Recovery Mode:
1. Download LOS 14.1 Experimental And Nightly For Your Device.
(If You Downloaded Them On PC Then Just Transfare The ZIP Files To Your Phone).
2. Go To Recovery.
3. Do A Full Back Up.
4. Install LOS 14.1 Experimental (Do Not Wipe).
5. Reboot To System.
6. Reboot To Recovery.
7. Install LOS 14.1 Nightly (Do Not Wipe).
8. Reboot To System (DONE!!).
Or Just To Be Safe (If The ROM Where Working Correctly).
9. Reboot To Recovery.
10. Do Another Back Up.
(Number 3, 9 And 10 Is Just To Be On The Safe Side).
P.S. Experimental Options Will Be Removed In Approx 2 Months!
If You Want Root On Your Device Then Just Download The Super SU From Lineage OS Extras And Install It In Recovery.
Guide If Needed:
1. Download The Correct Super SU For Your Device.
2. Reboot To Recovery.
3. Go To Install.
4. Select The Super SU ZIP File.
5. Install.
6. DONE!!
(You Can Do A Back Up After The Installation If You Want To).
Official Guide For Experimental Builds And More! (Source)
Official Homepage!
Official Downloads!
Official Lineage OS Extras (Super SU)!
Official Lineage OS Wiki!
Official Server Status Page!

Thanks for that Glompa541, worked perfectly. Will future updates work OTA?

tmarsh12345 said:
Thanks for that Glompa541, worked perfectly. Will future updates work OTA?
Click to expand...
Click to collapse
Yes it should be OTAs. But I cannot promise because I am not working with Lineage OS.
When I installed the Lineage OS 14.1 Experimental on my OP2 then when I rebooted to system after the flash then I got a notification about an update and that update was Lineage OS 14.1 Nightly so I think that it should be OTA updates in the future.

Hello,
Worked on my N4.
Thanks

somanaika said:
Hello,
Worked on my N4.
Thanks
Click to expand...
Click to collapse
No Problem!
I am glad that it helped you.

Glompa541 said:
I Have Seen Some People That Has Missed The Guide About The Lineage OS (LOS) Experimental Installation So I Made This Thread.
Where can I find the experimental LineageOS build?
Click to expand...
Click to collapse

sergiemiyagi said:
Glompa541 said:
I Have Seen Some People That Has Missed The Guide About The Lineage OS (LOS) Experimental Installation So I Made This Thread.
Where can I find the experimental LineageOS build?
Click to expand...
Click to collapse
It is no longer offered/available, you will need to clean flash.
Click to expand...
Click to collapse

sergiemiyagi said:
Glompa541 said:
I Have Seen Some People That Has Missed The Guide About The Lineage OS (LOS) Experimental Installation So I Made This Thread.
Where can I find the experimental LineageOS build?
Click to expand...
Click to collapse
jhedfors said:
sergiemiyagi said:
It is no longer offered/available, you will need to clean flash.
Click to expand...
Click to collapse
Yeah as jhedfors said..
The experimental builds has ended.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

Building Experimental Version

Hi,
since I like to stay at Marshmallow for now (especially because of the lack of Xposed for Nougat) but also like to already make the switch to Lineage, I see no other way then building Lineage based on CM 13.0 for my both devices (Oneplus 3 and kenzo) by myself.
While I'm familiar with building CM, it's not clear to me if it's possible to make a "Experimental" build (for dirty flash migration) and if so, how? Are there any build flags to be set? Any additional steps after building? How are the offical "EXPERIMEMTAL" builds done at download.lineageos.org?
Thank you very much in advance, it's very good to see Lineage OS getting traction after the Cyanogenmod shutdown.

Same problem

I would also be interested in this. Thank you for all your help.

No solution found?

schlowmo said:
Hi,
since I like to stay at Marshmallow for now (especially because of the lack of Xposed for Nougat) but also like to already make the switch to Lineage, I see no other way then building Lineage based on CM 13.0 for my both devices (Oneplus 3 and kenzo) by myself.
While I'm familiar with building CM, it's not clear to me if it's possible to make a "Experimental" build (for dirty flash migration) and if so, how? Are there any build flags to be set? Any additional steps after building? How are the offical "EXPERIMEMTAL" builds done at download.lineageos.org?
Thank you very much in advance, it's very good to see Lineage OS getting traction after the Cyanogenmod shutdown.
Click to expand...
Click to collapse
timkoop said:
Same problem
Click to expand...
Click to collapse
jmozmoz said:
I would also be interested in this. Thank you for all your help.
Click to expand...
Click to collapse
timkoop said:
No solution found?
Click to expand...
Click to collapse
I'm not sure if you all know this exactly but, the LineageOS Experimental builds is actually CyanogenMod Migration Builds.
It's intent is for those who use CyanogenMod installed and don't want to just wipe the whole device clean so the Experimental build is to install over the current CyanogenMod without wiping anything to Migrate from the CyanogenMod to the LineageOS. Then when it's done, you install the LineageOS Nightly build (or Snapshot if it's available) over the Experimental without wiping anything to complete the Migration.
With that stated, it would be a real challenging endeavor to create an Experimental build with that type of Migration feature.
I would applaud anyone, outside of the LineageOS Devs, who can accomplish this.
But, I'm not one to gossip... So you ain't heard that from me... LMAO!!!
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...

If you take a look at the Console Output of Jenkins, then there are build-scripts... I think they can build migration builds/they "know" how toll build these...
Fetching changes from the remote Git repository > git config remote.origin.url ssh://[email protected]/lineageos/build_scripts # timeout=10
Do you now how to get these script(s)?

To observations:
- In https://forum.xda-developers.com/showpost.php?p=70944088&postcount=26 and https://forum.xda-developers.com/showpost.php?p=70959718&postcount=27 it is described how to compile the current version of the cm-13.0 branch of lineageos for the Moto G (osprey). This build can be flashed on top of a Cyanogenmod 13.0 build without any problems. After reflashing Xposed it is also working.
- These are the changes between a "normal" and and "experimental" build of cm-13.0 on Jenkins for a certain phone (manta) on Jenkins:
builds: https://jenkins.lineageos.org/job/android/617/parameters/ and https://jenkins.lineageos.org/job/android/618/parameters/
changes on gerrit: https://review.lineageos.org/#/c/160268/ https://review.lineageos.org/#/c/160269/ https://review.lineageos.org/#/c/160272/
I totally unsure, what these patches really do, but I would guess its about checking signatures during the process of an OTA update.

160269 only adds the watermark... I think 160272 does the "real" migration, but I don't know, what the other change does...
I'll try to flash a normal nightly, but if it works, why do they make data migration builds?
But if I would build a migration build I only had to apply the changes to my repo and that's it?
EDIT: I just installed LineageOS over my CynaogenMod installation (14.1) on my HTC One A9 and it worked

timkoop said:
160269 only adds the watermark... I think 160272 does the "real" migration, but I don't know, what the other change does...
I'll try to flash a normal nightly, but if it works, why do they make data migration builds?
But if I would build a migration build I only had to apply the changes to my repo and that's it?
EDIT: I just installed LineageOS over my CynaogenMod installation (14.1) on my HTC One A9 and it worked
Click to expand...
Click to collapse
The watermarks are there for a reason.
Once the migration has completed, and your on the main screen with the watermarks, it is an indication that you have migrated successfully and ready for you to flash the latest Nightly build (or Snapshot build if one has been released).
Reboot back to recovery, and without wiping a thing, you'll then flash the Nightly and GApps. Wipe Dalvik and then reboot.
Peace and Love!
Peace and Love!
~Ringo Starr~
Sent on my Communicator [SCH-I535] from the Bridge of the U.S.S. Enterprise...
*PLEASE SELECT/CLICK THE THANKS BUTTON/OPTION*

[CLOSED][SHARE] Lineage 18, Android 11 for Pixel 4a Sunfish

This is not my build. Credit ny-hardcore for all the hard work on this. I'm just posting it.
Screen call is broken.
This is Lineage 18, Android 11 custom rom for the Pixel 4a Sunfish
If you do not want root, you can stop after step 6
1. Reboot to bootloader
2. fastboot flash --slot all boot recovery.img https://drive.google.com/file/d/1Hh7D_UbnnoTRr1XbC9i0-dvtFgbuFqrP/view?usp=sharing
3. Reboot to recovery
4. factory reset
5. adb sideload lineage-18.0-20201209-UNOFFICIAL-sunfish.zip
https://mega.nz/file/cUlVXApI#NbzUJ6UlyQvyPTitKnW7uJG_tHrsfYor9O0dH4yIiWc
6. Reboot to system
7. Install Magisk Manager https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk
8. Reboot to bootloader
9. fastboot flash boot magisk_patched.img https://drive.google.com/file/d/1cONN9Ev0jdAHaRSeOeYyeRTONJ-yO_8-/view?usp=sharing
10. Reboot to system

Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.

liamwhite said:
Could you please provide a kernel and device source tree for this? I have an in-progress diff which I am working to get 18 running fully on the device. It doesn't boot yet, and I would like to know what I messed up.
Click to expand...
Click to collapse
Based on the fact that this is NOT my work as stated above, I'm NOT at liberty to tell you. No offense. I would contact xda member edmontonchef and ask him. He's the one who sent it to me. I would like to think this wouldn't be a issue because if it was mine, I wouldn't care, but it's not.

This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.

ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
I'm using it right now. Great Rom. Thank you!!! Hope you don't mind I shared it.

Does this support signature spoofing?

Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
Would doubt it, if it's just vanilla LOS

ny-hardcore said:
This is my build.
Device tree is based of DU trees (r11x branch) and vendor (also r11x)
Kernel is flar2 kernel with wifi merged in.
Click to expand...
Click to collapse
Are Gapps included. Looking for a non gapps rom

EggZenBeanz said:
Are Gapps included. Looking for a non gapps rom
Click to expand...
Click to collapse
No gapps. Minimal Google play service function are included in build.

Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
No

TheSayaMan said:
No gapps. Minimal Google play service function are included in build.
Click to expand...
Click to collapse
Actually it contains gapps/Google play.

ny-hardcore said:
Actually it contains gapps/Google play.
Click to expand...
Click to collapse
I guess I assumed wrong. I thought he was referring to having to flash a seperate gapps zip.

Espio419 said:
Does this support signature spoofing?
Click to expand...
Click to collapse
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G

ny-hardcore said:
i'm working on a microg edition using the notes from the guy who made the microG build for 4a 5G
Click to expand...
Click to collapse
Oh yeah! Would love to see that. I'm ready to hop from my pixel 3xl once there's a non gapps ROM available

New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.

TheSayaMan said:
New build updated in OP. Thank Senior Member ny-hardcore for this.
Changes: Lineage sources and kernel updated with latest google update. The boot.img was updated in the payload to eliminate a second boot flash after sideloading rom for working WiFi. Please report any bugs that I may have missed. Also, I never dirty flash over anything. They more than likely cause problems. I did a clean install of this. If you are on the previous build of this, I DO NOT recommend dirty flashing it.
Click to expand...
Click to collapse
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?

Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
I haven't been able to check everything out. One thing I just noticed is that I am unable to pass safetynet with it but not a big deal for me.

Edmontonchef said:
Flashed and running well. WiFi worked right away. I noticed the boot.IMG in the op has stock recovery so I used the derpfest boot.IMG for flashing instead.
Also it's still November ASB?
Click to expand...
Click to collapse
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.

TheSayaMan said:
The boot in OP will work as well so take your pick and yes I did notice its still November. He's working on another build though.
Click to expand...
Click to collapse
december hasnt been merged in lineage sources

Is the boot.img a twrp recovery or? I am coming from stock, so would i need to touch twrp at all for this?