WORKING ROMS FOR UNLOCKED N900V w/VZW (and MVNO) SIMS

[bftb0]

FWIW, here is the build I am running already modded to remove the assert and have basic VZW functionality in build.prop

Use at your own risk

https://drive.google.com/file/d/0ByZWXbOZqmVqYkRod2Y5SXNNVGs/view?usp=docslist_api

@mightysween

Thank you for this ^^^^^.

I flashed it and configured it last night, & had to drive 38 miles each way (to & from) work today. So I ran a track logger app on both drivesw.

As you said, GPS is solid as a rock in this older (v6.1) Temasek CM13 ROM - no missing segments, no giant offsets. I had just assumed that GPS was always flaky in CM13, but this is good news (sorta) - it means we have a reference version of cm13 to compare to that actually works!

Maybe that will make it a bit easier to figure what went wrong in the newer releases.

 

[mightysween]

Thanks.

Do you have the original (trader418) file cm-13.0-20160407-UNOFFICIAL-temasek-hltespr-V6.1.zip ? I looked on @trader418's basketbuild and google drive, the "OLD" stuff there only runs back to about 04/29-30 or so.

I'd like to compute the deltas (hltespr -> hltevzw). Or is literally the only two changes in build.prop and the assert in the installer?

I'd like to get off of rooted stock; the only thing that holds me back is GPS. (I don't care at all about NFC and very little about BT).


.

I don't think Trader was building VZW yet on 04-07. The link is to a kanged version of the Sprint CM13 that I repackaged.

And yes... those are the only two differences.

 

[bftb0]

I don't think Trader was building VZW yet on 04-07. The link is to a kanged version of the Sprint CM13 that I repackaged.

And yes... those are the only two differences.

OK. Gotcha. Thank You.

I found the original 0407 sprint build .zip archive [ see @joshndroid XDA thread, post #2 and here ]

$ diff joshndroid/META-INF/com/google/android/updater-script mightysween/META-INF/com/google/android/updater-script 
1c1
< assert(getprop("ro.product.device") == "SM-N900P" || getprop("ro.build.product") == "SM-N900P" || getprop("ro.product.device") == "hltespr" || getprop("ro.build.product") == "hltespr" || abort("This package is for device: SM-N900P,hltespr; this device is " + getprop("ro.product.device") + "."););
---
> 
$ diff joshndroid/system/build.prop mightysween/system/build.prop 
46,47c46,47
< ro.cdma.home.operator.numeric=310120
< ro.cdma.home.operator.alpha=Sprint
---
> ro.cdma.home.operator.numeric=311480
> ro.cdma.home.operator.alpha=Verizon Wireless
49c49
< ro.telephony.default_network=10
---
> ro.telephony.default_network=8

 

[marblesmike]

Will it do Bluetooth stereo correctly? I ask because that's one reason I'm sticking to a TW based rom.

 

[bftb0]

Will it do Bluetooth stereo correctly? I ask because that's one reason I'm sticking to a TW based rom.

Not sure if you were asking me or someone else. I've used it with two BT devices, both of which worked (a laptop & an OBD II engine reader), and it worked without hiccup but I haven't tried it with any audio devices.

 

[landwaster]

It works! Thank you!

FWIW, here is the build I am running already modded to remove the assert and have basic VZW functionality in build.prop

Use at your own risk

(Link to file would be here, but I'm not allowed to post links)

Thank you so much! I flashed this version of the ROM you provided, and it's working perfectly for me. The GPS is totally solid, and the system functions flawlessly. I can attest that it also works with Xposed perfectly. This was the only version of CM13 I installed where the GPS worked. As for the Bluetooth, I do know that it sync'd with my car and fitness tracker with no problems. I don't have any BT stereo headphones to test, sorry. Thanks again!

 

[bftb0]

Thank you so much! I flashed this version of the ROM you provided, and it's working perfectly for me. The GPS is totally solid, and the system functions flawlessly. I can attest that it also works with Xposed perfectly. This was the only version of CM13 I installed where the GPS worked. As for the Bluetooth, I do know that it sync'd with my car and fitness tracker with no problems. I don't have any BT stereo headphones to test, sorry. Thanks again!

The only thing I have noticed so far is that the current YouTube app seems to get "stuck" quite frequently. It is responsive to touchscreen input, but after it plays a few clips it won't play any streams any longer, and I have to kill it off in the task manager and restart it. (There is no "play" button visible, almost as if it thinks that it is playing.) I have a different Android device on the same WiFi network that seems fine in this regard. Not sure what to make of it at this time.

Very happy to have working GPS on a CM13 ROM though.

 

[marblesmike]

Installed this last night and no major issues so far. Good battery life, BT stereo streaming works (I have a BT stereo in my car and it paired and streamed flawlessly), good GPS, etc. Much more stable than the Darklord MM rom in which I would randomly not get text messages.

 

[marblesmike]

Update: only issue I'm having is with BT calling. I can stream audio over my car stereo via bluetooth but when I try to make or take a call I get no sound or garbled sound.

Any ideas? I'm checking out the Temasek thread and he's up to version 10.3 for Verizon phones/sims so I'm going to back mine up and give that one a shot.

 

[mrfollis]

Installed this last night and no major issues so far. Good battery life, BT stereo streaming works (I have a BT stereo in my car and it paired and streamed flawlessly), good GPS, etc. Much more stable than the Darklord MM rom in which I would randomly not get text messages.

Same here, Darklord MM rom worked great at first, then over time text message problems then mms not work at all then no text or mms., Now I'm back looking for a more stable version or fixes or another Rom.

Any help or direction to another great rom like darkloard mm but working would be great. (I did try installing the zip for mms fix at no avail, even after re install and following the step by step proceedures on the videos..

Thank you all.

 

[marblesmike]

Update: only issue I'm having is with BT calling. I can stream audio over my car stereo via bluetooth but when I try to make or take a call I get no sound or garbled sound.

Any ideas? I'm checking out the Temasek thread and he's up to version 10.3 for Verizon phones/sims so I'm going to back mine up and give that one a shot.

Update:

I installed Temasek 10.3 for Verizon and had the bluetooth calling issue as well. So I downgraded it to 10.1 (someone said BT was working for them there) and still no bluetooth calling. I found a "Purify Bluetooth fix" zip and flashed that and voila no more BT calling issues.

 

[RaaidR]

@mightysween

Thank you for this ^^^^^.

I flashed it and configured it last night, & had to drive 38 miles each way (to & from) work today. So I ran a track logger app on both drivesw.

As you said, GPS is solid as a rock in this older (v6.1) Temasek CM13 ROM - no missing segments, no giant offsets. I had just assumed that GPS was always flaky in CM13, but this is good news (sorta) - it means we have a reference version of cm13 to compare to that actually works!

Maybe that will make it a bit easier to figure what went wrong in the newer releases.

I flashed this today, but I cannot get Skype to work. As soon as I open it, even before I enter my information, it stops working. Has anybody else had any issues with this?

 

[bftb0]

I flashed this today, but I cannot get Skype to work. As soon as I open it, even before I enter my information, it stops working. Has anybody else had any issues with this?

I don't use Skype so I can't say.

I will say that I've had crash-on-open app troubles on a few apps that work well on stock (on several different Android device types) but aren't happy on various versions of CM. Not a ton of apps, but it happens.

If you are curious as to the mechanism, usually the "logcat" will have a java stack trace in it that will give the approximate location of the crash mechanism. Some app devs will be responsive if you provide them that kind of diagnostic details. I wouldn't hold my breath expecting Microsoft to do that, but you never know. Just don't mention CyanongenMod

As far as using logcat goes, I've tried using a few logcat-recording apps. They work, but the typical output of logcat is so prodigious that it is tedious to look through logs on the device using the app, so I just capture the files manually (either using ADB on the PC or a terminal emulator on the device) and move the log files to a PC to look at them.

su
# clear the current log
logcat -c
# start logcat ; proggy will run until ^C
logcat -v threadtime >> /sdcard/logcatcrashcapture.txt
# put terminal emulator app in background and start up the problem app, then Ctrl-C after the crash
^C

good luck

 

[RaaidR]

I don't use Skype so I can't say.

I will say that I've had crash-on-open app troubles on a few apps that work well on stock (on several different Android device types) but aren't happy on various versions of CM. Not a ton of apps, but it happens.

If you are curious as to the mechanism, usually the "logcat" will have a java stack trace in it that will give the approximate location of the crash mechanism. Some app devs will be responsive if you provide them that kind of diagnostic details. I wouldn't hold my breath expecting Microsoft to do that, but you never know. Just don't mention CyanongenMod

As far as using logcat goes, I've tried using a few logcat-recording apps. They work, but the typical output of logcat is so prodigious that it is tedious to look through logs on the device using the app, so I just capture the files manually (either using ADB on the PC or a terminal emulator on the device) and move the log files to a PC to look at them.

su
# clear the current log
logcat -c
# start logcat ; proggy will run until ^C
logcat -v threadtime >> /sdcard/logcatcrashcapture.txt
# put terminal emulator app in background and start up the problem app, then Ctrl-C after the crash
^C

good luck

I went back and downloaded a Skype APK from April 5, and now Skype works. Seems like it has an issue with that maybe?

 

[homyg411]

When i noticed the bootloader unlock I was extatic, but I knew there probably wouldn't be many reliable roms out there. I ran into most of the problems I've read through in these forums, mostly no radio or sms even though I followed instructions to a T. It came down to Flashing a radio zip SPECIFICALLY for the 900v. See, when I would get CM13 installed, my phone suddenly shows up as a 9005. Now, I don't pretend to know anything about android development, but I DO know firmware, "drivers"... they tell software how to use the hardware they're operating on. If My phone thinks it's a 9005, it probably also thinks it has a 9005 modem. There were other little quirks like governors, but i won't get into that . In the Jasmine Rom 6.1 announcement page/instructions, there's a little section at the end for "Developer mode" phones. It had 2 additional files to flash after the rom. A standalone kernel, and STANDALONE BASEBAND. I had seen several people say their 900v was now "developer" or something, so i had an idea. Here was the process:

Into twrp 3.0.2, running Jasmine 6.1...
Factory wipe, Flash latest CM13 9.9, wipe dalvik, flash google apps, wipe dalvik, flash CM13 9.9 AGAIN (not even sure this step is necessary), wipe dalvik, flash SU, wipe dalvik, REBOOT INTO DOWNLOAD MODE, Flash N900VVRUE00F1_Modem.tar.md5, reboot into recovery, factory restore.......

Finally, booted to system and I'll be a sumbitch, the radio's working.
I'm willing to wager all those other roms i tried out, where the radio refused to work, would all work if i had just flashed this baseband. THAT'S EXCITING.
I'm shocked I never read about anyone else doing this, or why i didn't think of it before: that there was a way to flash individual parts of the whole "ROM".
I later flashed the kernel from the Developer files as well via Odin. "lk_hltevzw-v6.4"
What I Wish I knew how to do is take a factory rom or flashable zip and make flashable versions of the kernel, baseband, bootloader perhaps, etc.

Anyway, I genuinely hope my trials help you guys get some cool roms up and running on our 900V's.

Xerx

So I tried this to a tT Question is do you have a developer verizon phone? I know I do not have a developer phone because any htlevzw rom or zip does not work. I tried flashing the kernel and it would not work. My phone is SM-900V retail version NOT developer on Verizon and does have TWRP installed and bootloader unlocked. I need help getting Tema to work on mine w/ cellular towers. Only lollipop seems to work which means Jasmine Rom

No matter what my phone thinks its still SM-9005. And my Sim voice says out of service. My Data is in service and i can use 4g to download though

I tried both Tema version CM13 v6.4 and CM13v11

 

[njdan30]

So I tried this to a tT Question is do you have a developer verizon phone? I know I do not have a developer phone because any htlevzw rom or zip does not work. I tried flashing the kernel and it would not work. My phone is SM-900V retail version NOT developer on Verizon and does have TWRP installed and bootloader unlocked. I need help getting Tema to work on mine w/ cellular towers. Only lollipop seems to work which means Jasmine Rom

No matter what my phone thinks its still SM-9005. And my Sim voice says out of service. My Data is in service and i can use 4g to download though

I tried both Tema version CM13 v6.4 and CM13v11

Actually if you look at your baseband which is the modern it never changed. And the name can be changed very very easily in build prop

sent from my Verizon note 3 running 6.0.1 TouchWiz

 

[homyg411]

finured it out
was using the wrong bootloader


for future reference if using verizon to have htlevzw bootloader
it will be orange not blue

 

[Asylum_Designs]

mightysween
FWIW, here is the build I am running already modded to remove the assert and have basic VZW functionality in build.prop

Use at your own risk




I can confirm this is the only rom i have seen radios work on. gonna try to stay on it for the next few days. I do have a question. Every rom I have tried out is now getting "the kernal is not seandroid enforcing" on boot, including this one. It's installed with twrp 3.0.2.1. It boots fine, I'm just wondering if this will effect anything or can i ignore it?

 

[njdan30]

Ignore

sent from my Verizon note 3 running 6.0.1 TouchWiz

 

[droid5404]

actually found a fully functional s7 port for the verizon note 3 minus mms. Will post rom later can't remember which it was.