Database Info

[Q] 2.15 HBoot for AOSP ROM?

Just flashed and so far running almost perfectly! Loving it. Only bug I have noticed so far is that the quick settings toggle for GPS is broken. It is stuck greyed out on "Location Off", even when GPS is toggled on, and whether it is being actively used or not. Touching the toggle doesn't seem to change anything. Also along with that I just noticed that the GPS icon never appears in the status bar when being used like it would in Jelly Bean.
What launcher is everyone using? I wanted to stay KitKat based but also want a lot of the extra functionality like gestures and such. So far it seems Holo Launcher HD best fits that. Tons of customization and KitKat based. I'm missing a couple of things, mainly the swipe left for Google Now (just has Jelly Bean home page system), and the launcher font is the old Holo, so looks just a bit different than system font. But that's just nitpicking, I really like it so far. Just curious to see what other people are using.
Thanks JoshX!

This might be a dumb question, but would it be better or even necessary at all to update to the 2.15 firmware and/ord HBoot when using an AOSP ROM? The unofficial CM11 that JoshX built specifically, if that makes a difference. I ask because for CM10.2 I believe it was necessary to run the 3.18 RUU prior in order to be on the 2.14 firmware (maybe I'm mistaken about why?). I haven't flashed or done much anything with my phone until recently, so I just noticed that there is now a 2.15 HBoot. I'm running CM11 at the moment and my bootloader shows 2.14 HBoot.
Just a bit confused and was curious, thanks in advance.

icu64 said:
That's normally the radio that handles that but keys double check. Did you do the 2.15 hboot/firmware update?
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
I'm running Torched KK B2.1 with CM11 at the moment but I am on 2.14 firmware. Should I update or is it not necessary?

Chrysis said:
I'm running Torched KK B2.1 with CM11 at the moment but I am on 2.14 firmware. Should I update or is it not necessary?
Click to expand...
Click to collapse
Not necessary, it's only necessary for Sense 5 ROMs.
Sent from my Evita

@Chrysis
Please note, there is no need to repost a question that has already been answered. Please keep your questions on this subject in this thread.
Thank you

timmaaa said:
Not necessary, it's only necessary for Sense 5 ROMs.
Sent from my Evita
Click to expand...
Click to collapse
Got it, thanks! If I wanted to update to a newer radio from that firmware though, would it still be unecessary? Just read a few times that firmwares and radios are typically bundled, so wanted to double check.
TonyStark said:
@Chrysis
Please note, there is no need to repost a question that has already been answered. Please keep your questions on this subject in this thread.
Thank you
Click to expand...
Click to collapse
My bad, I didn't see the post in the kernel thread until after I started this thread. Will keep it to one place in the future!
The first post that's here now I did mean for the ROM thread though, it was separate from my question about the new hboot. Would it be alright if I posted it back to that thread? Thanks. Apologies again for repeating my question elsewhere.

It's basically suggested to use the radio (1.31) that's bundled with the 2.15 firmware for proper use with a Sense 5 ROM. In any other situation you can use whatever radio you want really. Anecdotally I have tested the 1.31 radio while on the 2.14 firmware and it performed terribly. That may have been confined to my experience though, you can always test it yourself. If a radio doesn't work well it's super easy to just flash another one.
Sent from my Evita

[ROM][OFFICIAL][NIGHTLIES]Vanir-AOSP | Optimization Level Legendary| HBOOT 2.15

Welcome to VanirAOSP. Our mission is to deliver a clean optimized version of Android to as many devices as possible. This is not a kang rom. You will find versions of the features you love that we've rewritten and improved on plus a few we wrote ourselves. we've tried to acheive a more organized and cohesive setup to improve the user experience while correcting any performance regressions and improving functionality.
If you're the kind of person that needs options to change the font and color on every letter and expect the ROM to end up looking like kid's cereal box then GTFO. You will not find customizations that are done just because someone figured out how to do them. Everything in here has a purpose and is held to a high standard of coding.
General features:
stock mode - ability revert to stock AOSP code with the exception of a few custom features we chose to keep active
enhanced performance.. longer uptime with less slowdown
custom written CRON and init.d.
minor UI and graphics improvements
custom navbar, navring, and hardware key features
active notifications (improved active display + lockscreen notifications)
usability improvements like power reboot menu and sound
animation control
Improved Vanir keyboard
CM's profiles & quicksettings
additional quicksetting tiles
immersive desktop <- fully configurable immersive mode
low profile mode
statusbar mods
clock & battery mods
lockscreen blur and other mods
soon to come -> quick cam and flash notifications
busybox, embedded root, init.d, cron etc
many improvements and new features unique to vanir
more to come when i feel like updating the op
issues:
- stop flashing the moto X binaries. they do not improve anything for you and aren't even for your device.
- open source camera and launcher3 do not have the same featuers as the google versions. use the latest
banks standard gapps if you'd like these. His gapps are super legit and always up to date.
Join our Google+ community for news/updates
Nightly downloads are available on our google+ page or directly from our server
if you're interested in becoming a maintainer.. or just need help please send an email to [email protected]
Download:
http://www.emccann.net/nuclearmistake/VanirAOSPNightlies
Check Vanir Updater for updates daily
Gapps: http://goo.im/devs/BaNkS/GApps i recomend Banks Gapps
Experimental (These are downloads built by me that are not official and may or may not be stable but your welcomed to test them and give feedback)
http://downloads.codefi.re/ethanj99/vanir_ville
Please Consider Rating this thread 5 Star and press the like button
Credits:
Vanir
Slim ROMS
AOKP
AOSP
PAC-Man
codefireXperiment
Code Aurora Forum
DHOMD
nuclearmistake
Jason Downing
PrimeDirective
LorDClockan
tbalden
pingpong
Rc420head
Flashalot
Source:
ROM Source: https://github.com/VanirAOSP
KernelSource: https://github.com/CyanogenMod/android_kernel_htc_msm8960
HBOOT 2.15 ONLY!!!
Q&A thread for questions about the rom: http://forum.xda-developers.com/showthread.php?t=2713079
if you want a clean aosp rom than go into development settings on this rom and enable stock mode and reboot!

....and Try :good:

Fixed op. Added link that I missed earler
Sent from my iPad using Tapatalk

Finely there's a op lol Good Job[emoji844]
Sent from my D2lte CandyKat

Works for 2.16 hboot (please tell me yes ) ?

if you are on hboot 2.16 flash cm11 2.16 version boot.img

benJX said:
Works for 2.16 hboot (please tell me yes ) ?
Click to expand...
Click to collapse
+2!!! Love to see more for 2.16 hboot!!!
---------- Post added at 07:18 PM ---------- Previous post was at 07:15 PM ----------

rmbq said:
if you are on hboot 2.16 flash cm11 2.16 version boot.img
Click to expand...
Click to collapse
Where do you get this file?
Sent from my HTC One S using Tapatalk

leald said:
Where do you get this file?
Sent from my HTC One S using Tapatalk
Click to expand...
Click to collapse
download cm11 for hboot 2.16, in the zip there's a file named boot.img

First thanks for the rom. I m giving it a go and seems neat so far. I only got a doubt. I m trying to keep as close to aosp as possible. Main problem for me is the things like halo or active notifications. is there a way to completely remove them from the rom? I mean really remove them with all their related files, not just disabling 'em.

maluus said:
First thanks for the rom. I m giving it a go and seems neat so far. I only got a doubt. I m trying to keep as close to aosp as possible. Main problem for me is the things like halo or active notifications. is there a way to completely remove them from the rom? I mean really remove them with all their related files, not just disabling 'em.
Click to expand...
Click to collapse
Well to keep things short no
Sent From Ville Candykat

Flashalot said:
Well to keep things short no
Sent From Ville Candykat
Click to expand...
Click to collapse
Yes go to developer settings and enable stock mode. Than all that stuff is gone. It disables all that extra stuff. It is put in there for people with your wants. A fast rom with stock look and feel
maluus said:
First thanks for the rom. I m giving it a go and seems neat so far. I only got a doubt. I m trying to keep as close to aosp as possible. Main problem for me is the things like halo or active notifications. is there a way to completely remove them from the rom? I mean really remove them with all their related files, not just disabling 'em.
Click to expand...
Click to collapse
Sent from my One S using Tapatalk

rmbq said:
if you are on hboot 2.16 flash cm11 2.16 version boot.img
Click to expand...
Click to collapse
Rom didn't even flash on 2.16 hboot, it says it is for 2.13 & 2.15. As expected, flashing cm11 kernel doesn't change anything to it.
Btw thx for your reply
Sent from my ElementalXed One S

benJX said:
Rom didn't even flash on 2.16 hboot, it says it is for 2.13 & 2.15. As expected, flashing cm11 kernel doesn't change anything to it.
Btw thx for your reply
Sent from my ElementalXed One S
Click to expand...
Click to collapse
You can use my guide HERE to get rid of the check for proper hboot and you can flash the ROM on any hboot. Then follow rmbq's advice to flash the boot.img for 2.16 from a CM11 ZIP
@rmbq: I didn't know it is so easy to flash a 2.15 ROM on a 2.16 phone...is this the only difference? Just flash another kernel? I thought there are other modules or libs that are different if ROM is built for 2.16. Why is everybody asking for a 2.16 build then if things would be so easy? As I know, 2.16 hboot uses a different partition map and the flash of kernel in fastboot won't change this. Also there was a different recovery to be used for 2.16 hboots. He should flash the 2.15 ROM using his usual 2.16 recovery then just flash a working 2.16 kernel (from another similar ROM) in fastboot? Looks too simple and I'm wondering why not everyone having a 2.16 hboot do the same

benJX said:
Rom didn't even flash on 2.16 hboot, it says it is for 2.13 & 2.15. As expected, flashing cm11 kernel doesn't change anything to it.
Btw thx for your reply
Sent from my ElementalXed One S
Click to expand...
Click to collapse
you have to change a line in META-INF/com/google/android/updater-script.
you'll see there's getprop("ro.bootloader") == "2.15.0000", replace 2.15.0000 with 2.16.0000
Rapier said:
You can use my guide HERE to get rid of the check for proper hboot and you can flash the ROM on any hboot. Then follow rmbq's advice to flash the boot.img for 2.16 from a CM11 ZIP
@rmbq: I didn't know it is so easy to flash a 2.15 ROM on a 2.16 phone...is this the only difference? Just flash another kernel? I thought there are other modules or libs that are different if ROM is built for 2.16. Why is everybody asking for a 2.16 build then if things would be so easy? As I know, 2.16 hboot uses a different partition map and the flash of kernel in fastboot won't change this. Also there was a different recovery to be used for 2.16 hboots. He should flash the 2.15 ROM using his usual 2.16 recovery then just flash a working 2.16 kernel (from another similar ROM) in fastboot? Looks too simple and I'm wondering why not everyone having a 2.16 hboot do the same
Click to expand...
Click to collapse
only partition table is different from 2.15 and 2.16, and it's in ramdisk! I think it's worth it to try

A minor OT - it would be good to have a tutorial regarding previous posts. It will be helpfull for lot of us .
Востани Сербие, востани царице

Loreane Van Daal said:
A minor OT - it would be good to have a tutorial regarding previous posts. It will be helpfull for lot of us .
Востани Сербие, востани царице
Click to expand...
Click to collapse
nobody confirmed it's working!

Well then, if i catch some time during weekend will try.
Востани Сербие, востани царице

i try it now for three days..with new Radio.. just like now i dont see anything who doesnt work... good batterylife. all i can say.. nice bootanimation very usefull settings..
i use the phone only for testing and playing with custom roms because i have the htc one M8 now

ulmcity said:
i try it now for three days..with new Radio.. just like now i dont see anything who doesnt work... good batterylife. all i can say.. nice bootanimation very usefull settings..
i use the phone only for testing and playing with custom roms because i have the htc one M8 now
Click to expand...
Click to collapse
Thanks. And others remember feedback on rom is welcomed in the thread
Sent from my iPad using Tapatalk

[Q] Franco Kernel 21

Hi guys,
I tried to flash the Franco kernel with the CM11 snapshot M9, for some reason i get pixel distortion top right. Where the cell bars show, sometimes over the complete right side of the screen.
Thereafter i re-flashed the rom directly following with the franco kernel, same result though.
Any ideas?
Thanks!

Its known issue. Graphics overlay on screen touch.
Workaround: Goto 'Developer Options' and disable Hardware Overlays.
U have to do this every time u reboot the phone.

Update your ROM, you're using a outdated ROM thats lacking the commits. Easier to update your ROM than to do a workaround on every reboot.

zephiK said:
Update your ROM, you're using a outdated ROM thats lacking the commits. Easier to update your ROM than to do a workaround on every reboot.
Click to expand...
Click to collapse
You're saying there is an update for stable version?
Or do you mean flashing the latest nightly?
Thanks for the answers guys!

Waanzin said:
You're saying there is an update for stable version?
Or do you mean flashing the latest nightly?
Thanks for the answers guys!
Click to expand...
Click to collapse
Latest nightly.

What samflorin said, M10 is out for some phones. OnePlus One is still being worked on so they didn't push M10 yet. When it does, it should be very close to the OTA.
M9 was a very old build that lacked the commits causing conflict on the kernel side of things. Once you update, all should be good

[Q&A] [ROM][OFFICIAL][KitKat 4.4.4][Ville] PAC-ROM 4.4.4.RC-2

Q&A for [ROM][OFFICIAL][KitKat 4.4.4][Ville] PAC-ROM 4.4.4.RC-2
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:

atrus5 said:
New build is up. Just some minor changes and fixes to the build. Here is the link. https://s.basketbuild.com/dl/devs?dl=pacman/ville/dev/pac_ville_4.4.4.RC-2_20141019-003708.zip
Click to expand...
Click to collapse
Bluetooth is really broken for me.

Pilipin said:
Bluetooth is really broken for me.
Click to expand...
Click to collapse
Can you send a logcat of what happens when you use Bluetooth

@atrus5 Have you added a custom kernel yet? If not, i'm working on one with @javelinanddart and possibly @AKToronto, but I'd need help compiling it. It always fails for me.

josepha19223 said:
@atrus5 Have you added a custom kernel yet? If not, i'm working on one with @javelinanddart and possibly @AKToronto, but I'd need help compiling it. It always fails for me.
Click to expand...
Click to collapse
I don't add custom kernels to the build. I guess I could but I feel the user can add whatever they want afterwards instead of having one built in. I am not the best person to ask for building a kernel as I don't do that kind of thing. I just like building the roms and testing them.

atrus5 said:
I don't add custom kernels to the build. I guess I could but I feel the user can add whatever they want afterwards instead of having one built in. I am not the best person to ask for building a kernel as I don't do that kind of thing. I just like building the roms and testing them.
Click to expand...
Click to collapse
Well let me know if you want to. you did add a poll so i was just wondering

josepha19223 said:
Well let me know if you want to. you did add a poll so i was just wondering
Click to expand...
Click to collapse
Yeah sorry that poll was from the very beginning of the thread and I can't get rid of it

hello got error flashing Lates PacMan build 4.4.4 pac_ville_KK.RC-3.dev_20141129-123111
E:Error executing updater binary in zip
Click to expand...
Click to collapse
Hboot 2.15, S-off, radio 1.11, TTWRP 2.5.0.0
pls help
upd. Flashing TTWRP 2.8 - fixed problem. Sry for diturbing

BorHblK said:
hello got error flashing Lates PacMan build 4.4.4 pac_ville_KK.RC-3.dev_20141129-123111
Hboot 2.15, S-off, radio 1.11, TTWRP 2.5.0.0
pls help
upd. Flashing TTWRP 2.8 - fixed problem. Sry for diturbing
Click to expand...
Click to collapse
yeah i was gonna say just update your recovery but you got it

Calling out gives blank screen
Hey - new to the forum here, and I know this rom is discontinued for the ville, but perhaps someone can point me in the right direction;
When I want to place a call, the screen goes blank. The call itself is being made, but I cannot get the screen to work again. Even after the call disconnects. Only way, is to lock screen with power button (still blank) and press power button again to go to unlock screen.
This problem is also for incoming calls only after picking up the phone.
This is what I did to the phone so far:
- Unlock bootloader via HTC site
- Root phone
- Install TWRP
- Flash PACROM , PA GApps, Update-SuperSU, flash boot.img in fastboot
My setup:
HTC One S S4
HBOOT 2.15
Radio: 1.11.50.05.28_10.27.50.08L
Kernel: 3.4.82
ROM: pac_ville 4.4.4 20141231
S-ON
TWRP: 2.8.6.4
SuperSU 2.46
I have looked around in the threads here but seems no-one else is having this problem.

Can you try to use a different gapps. Pa adds info to there gapps. Use the gapps from the op.

Actally it was the proximity sensor that was giving issues, I used a calibration app to set it manually and since have been using Pacman happily. God it would be great to see a LP PACMAN for the Ville

krillin2112 said:
Actally it was the proximity sensor that was giving issues, I used a calibration app to set it manually and since have been using Pacman happily. God it would be great to see a LP PACMAN for the Ville
Click to expand...
Click to collapse
Glad you found the problem and fixed it.
It won't be me making the build. If anyone else wants to that would be great.
Sent from my Nexus 5 using XDA Forums

Yeah I read you no longer have a working Ville. I really do like the ROM and maybe one day someone can make a LP build. There is one for the HTC One (m7 & m8). Don't know how much work it would entail to adapt that to Ville.

Temasek unofficial cm-12.1 builds

This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26

Thanks for keeping support for the Note 3 alive.

Great, good to see 12.1 back alive. Anything I can do to help, just say so.

Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.

Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that

Straw poll whether to include root in the build here http://strawpoll.me/7191529

trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)

Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything

hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!

redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have

trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!

redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help

trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!

redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical

trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results

swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.

redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.

eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?

redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)

redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure