Hey guys I didn't think it would happen but for those of you that are still running the sm-n900v we now have official support for lineage OS 7.1.2 merged into hltetmo. The only thing that's required is the hlte recovery not the hltevzw recovery. You have to make sure you're on the latest baseband and just wait till today's official build and it will be in there. Also follow the thread link below and you'll see what I'm talking about. I just tested a test build and my data is working great.
https://forum.xda-developers.com/ga...-0-cm14-trader418-unofficial-t3459973/page427
And this is a screenshot of the test build I'm running just to show proof.
alexp1289 said:
Hey guys I didn't think it would happen but for those of you that are still running the sm-n900v we now have official support for lineage OS 7.1.2 merged into hltetmo. The only thing that's required is the hlte recovery not the hltevzw recovery. You have to make sure you're on the latest baseband and just wait till today's official build and it will be in there. Also follow the thread link below and you'll see what I'm talking about. I just tested a test build and my data is working great.
https://forum.xda-developers.com/ga...-0-cm14-trader418-unofficial-t3459973/page427
And this is a screenshot of the test build I'm running just to show proof.
Click to expand...
Click to collapse
Thanks Alexp1289! What is the latest baseband? And have you by chance tested bluetooth on this? Will it connect to a headset or car stereo?
Droidify said:
Thanks Alexp1289! What is the latest baseband? And have you by chance tested bluetooth on this? Will it connect to a headset or car stereo?
Click to expand...
Click to collapse
Latest baseband is 0F1 and Bluetooth works great I haven't had any issues so far. You'd have to flash the latest Samsung firmware package with Odin if you're not on the 0F1 baseband then flash the latest hlte twrp recovery.
Sent from my SM-N900V using Tapatalk
alexp1289 said:
Latest baseband is 0F1 and Bluetooth works great I haven't had any issues so far. You'd have to flash the latest Samsung firmware package with Odin if you're not on the 0F1 baseband then flash the latest hlte twrp recovery. Then flash the hltetmo test build zip or wait for official hltetmo build today. Verizon support is being baked into hltetmo so that's what we have to flash.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Sent from my SM-N900V using Tapatalk
alexp1289 said:
Latest baseband is 0F1 and Bluetooth works great I haven't had any issues so far. You'd have to flash the latest Samsung firmware package with Odin if you're not on the 0F1 baseband then flash the latest hlte twrp recovery.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Ok that is what I am on. Will give this a go at some point soon! Thanks
Droidify said:
Ok that is what I am on. Will give this a go at some point soon! Thanks
Click to expand...
Click to collapse
I've only gotten a couple random reboots so far but other than that it's going great.
Sent from my SM-N900V using Tapatalk
great news bobby
I've flashed it and no signal what's so ever tried 7 different ones I'm on of1 as well as unlocked
happydad4130 said:
I've flashed it and no signal what's so ever tried 7 different ones I'm on of1 as well as unlocked
Click to expand...
Click to collapse
Go to that thread I posted and ask for help. You must be doing something wrong because I'm on Verizon and everything works great on this rom.
What room did u download and what did u do when the room does boot it only boots to safemode and still no signal I'm not.a noob but damn
..
happydad4130 said:
What room did u download and what did u do when the room does boot it only boots to safemode and still no signal I'm not.a noob but damn
..
Click to expand...
Click to collapse
Download 20170719:
https://download.lineageos.org/hltetmo
You also need to have TWRP for hlte installed:
https://dl.twrp.me/hlte/twrp-3.1.1-0-hlte.img.html
And flash that recovery image with flashify:
https://play.google.com/store/apps/details?id=com.cgollner.flashify
Don't forget to download a gapps package (arm 7.1):
http://opengapps.org
You need to make sure your Verizon note 3 is on the lastest baseband which is SEPL1 if it's not you needed to flash this using Odin 3.09 here's the baseband file to flash in Odin:
https://www.androidfilehost.com/?w=files&flid=199473
Here's where you get Odin:
http://androidhost.org/PVAIv
Follow the thread link in the OP for support and submitting bugs after flashing lineage.
This ROM is working flawlessly! I am using a different kernel to add fast charge and new CPU governors. Heavy use for the past 4 days and no problems at all!
https://forum.xda-developers.com/ga...lte-synergy-kernel-la14-1-based-roms-t3612028
alexp1289 said:
You need to make sure your Verizon note 3 is on the lastest baseband which is SEPL1 if it's not you needed to flash this using Odin 3.09 here's the baseband file to flash in Odin:
Click to expand...
Click to collapse
Can you clarify the requirement for the SEPL1 baseband? Your screenshot in the OP shows OF1 as your baseband.
Thanks!
nicky666s said:
Can you clarify the requirement for the SEPL1 baseband? Your screenshot in the OP shows OF1 as your baseband.
Thanks!
Click to expand...
Click to collapse
I was wrong earlier I had to update mine. OF1 works but SEPL1 is preferred since it's the lastest.
cssr said:
This ROM is working flawlessly! I am using a different kernel to add fast charge and new CPU governors. Heavy use for the past 4 days and no problems at all!
https://forum.xda-developers.com/ga...lte-synergy-kernel-la14-1-based-roms-t3612028
Click to expand...
Click to collapse
FYI: After flashing Synergy Kernel I lost root and Reflashing SuperSU did not work. I had to flash Magisk-v13.3 after flashing the kernel and it fixed the root problem.
http://www.stechguide.com/download-magisk-v13-3/
Also, note that if you install Magisk, it will have to be uninstalled before you do an update. If you don't, it will update and you will get an error. You can still uninstall Magisk and install the update again and then reinstall Magisk. If you change the kernel again.
@ golfslicer
I had the same problem after updating the kernel and also use the same solution. Was going to post about it but, you beat me to it.
Lineage also has root (SU) solution.
https://download.lineageos.org/extras
CIFS/SMB & NFS network share
Does anyone know how to mount a cifs/smb (or nfs) share with LineageOS?
bash script that I used with Aryamod 6.5 & 6.6 & SManager no longer works with LOS. Manually trying to mount from the LOS builtin terminal or Term. Emulator (installed from Play Store), also doesn't work.
Thanks in advance.
P.S. Also can I make this permanent by editing fstab, so that the network share is mounted on boot?
I personally don't use file sharing. But a quick search for Samba(smb) will probably give you all the help you need.
Still getting a really bad echo on this mod, same as i did on the unofficial port of CM13. Any recommendations? Thanks for any help offered.
Flashed this ROM a few days ago and had no problems with it yet. Installation was a breeze. Wiped system, data, and cache, then flashed the ROM and open gapps with twrp and it booted right up. I'm using it as a daily driver at this point because it is so stable! Love stock android! Was very pleased to hear the note 3 now has official support!
Related
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
BDogg718 said:
I was just curious if anyone was planning on building TRWP 2.4 for the fassy since its not yet supported by their team.? Or does it still not play nice with the fassy?
Click to expand...
Click to collapse
I'd love to see it on the fascinate! I'm rolling with it on my a500 and its freaking awesome
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
Click to expand...
Click to collapse
You don't have to unlock the fascinate its all open just put cwm on it and flash cm10.1 twrp won't work on cm10 and above so you have to use cwm use this guide here http://forum.xda-developers.com/showthread.php?t=1238070
Sent from my SCH-I500 using Tapatalk 2
Xceptiona1noob said:
I am going to be receiving a fascinate tomorrow and have plans to install cm10.1 via odin. From my understanding I can then install twrp and goo to install updates from that point on. I presume I have to still use odin to unlock the phone and get CM10.1 working, but goo/twrp should work for updating it from the nightlys after that point, correct?
http://teamw.in/project/twrp2/40
Click to expand...
Click to collapse
cm10 includes it's own "cmupdater" app. Checks for new builds on your schedule (or manually), notifies of new builds, displays change logs, and installs the updates. Works well. It's visible on the "about phone" settings menu. Also available in the app drawer...
Sent from my SCH-I500 using xda premium
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
jt1134 said:
I've fixed twrp to work with cm10.1. Works pretty well. Too bad injection doesn't work any more.
Click to expand...
Click to collapse
Nice I've never used twrp so I may have to try it
Sent from my SCH-I500 using Tapatalk 2
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Updated source code is here:
https://github.com/jt1134/Team-Win-Recovery-Project/commits/twrp2.4
https://github.com/jt1134/android_device_samsung_fascinatemtd/commits/myjb-next
http://www.mediafire.com/?ul4n2gc1ba044sb
Click to expand...
Click to collapse
Thanx JT! Back-up and restore work just fine! Great work as always!
BDogg718 said:
Thanx JT! Back-up and restore work just fine! Great work as always!
Click to expand...
Click to collapse
Good to know. Thanks for testing it
jt1134 said:
Linked below is a kernel bundled with the latest version of TWRP modified to work with the fascinate. I've only tested it with my personal cm10.1 build, it should work with other 4.2.2 ROMs, may work with 4.2.1 ROMs. Due to the way the bootloader handles the kernel/recovery partitions, it (currently) has to be bundled with the kernel. If I come up with a way to make it stick across different builds I'll submit the changes to the appropriate upstream repositories, etc.
I haven't tested much other than flashing zip files, backup/restore may break your device into a million pieces. That might be kinda funny.
Click to expand...
Click to collapse
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
hhp_211 said:
And it does work on the latest hellybean as long as you 1st flash your cm kernel to it :thumbup:
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
I'd love to see this incorporated into the devil kernel
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Thanks jt. It`s a step forward. You da man that's all I can say. :thumbup::beer:
Sent from my SCH-I500 using Xparent Green Tapatalk 2
if you are on fassy, notta posted a pa twp recovery flashable test as of now
LasVegasRomeo said:
if you are on fassy, notta posted a pa twp recovery flashable test as of now
Click to expand...
Click to collapse
does that kernel notta posted kill your WiFi?
kill type ?my wifi is workin I havent had any issues as far as i know. ran wifi a lil bit earlier and no issues. My wifi has is always crappy for me though here at home. Seems spotty a lil but like i said thats normal for me.
jt1134 said:
Seems my changes have been merged in the main TWRP repository
I still can't seem to come up with a decent way to replace the recovery permanently from kernel to kernel, but I've fixed fakeflash to work with the current version of TWRP. Fakeflash allows you to temporarily flash a different recovery by flashing a zip file in your current recovery. This allows it to work regardless of what kernel/recovery you are currently using.
A test version is linked below. Flash it in your current recovery and it will reboot into TWRP. Subsequent reboots will run your previous recovery, the zip needs to be flashed each time to use TWRP. Anyone who has had the fascinate for more than a year and a half should know all about fakeflash it's the original way we used recovery (**** you samsung).
http://www.mediafire.com/?tq0uq2uo24lofcl
Click to expand...
Click to collapse
is there a way to modify the source to use the prebuilt bootimage.Also when compiling it fails to create the utilities folder.
Edited: problem solved. See my last post to the solution I found.
I don't know if it works in Odin cause I haven't tried it, but there is a link somewhere in the Skynote port ROM thread that has the modem as a zip flashable in recovery. It DOES work as I am on MJ9 on Paranoid Android 4.4.2.
Numzi said:
I don't know if it works in Odin cause I haven't tried it, but there is a link somewhere in the Skynote port ROM thread that has the modem as a zip flashable in recovery. It DOES work as I am on MJ9 on Paranoid Android 4.4.2.
Click to expand...
Click to collapse
Well from "Krowley3's" Sophisticated ROM thread, you can flash it via ODIN with this file: http://www.androidfilehost.com/?fid=23269279319198557
Thanks for letting me know its working for you on PA.
bigw34 said:
Well from "Krowley3's" Sophisticated ROM thread, you can flash it via ODIN with this file: http://www.androidfilehost.com/?fid=23269279319198557
Thanks for letting me know its working for you on PA.
Click to expand...
Click to collapse
No problem. Try flashing it then. I'm sure it should work.
Well I ended up flashing the file...the first time was through TWRP and it didnt change anything. The next time I tried through ODIN and it gave me an "unknown baseband" that a lot of people are reporting. I ended up with no data, had to flash back to stock and start all over again using vramc3.
Numzi, how did you get it working on your phone?
I'm running the new firmware with CM11. I flashed it in cwm and it works fine
tgyberg said:
I'm running the new firmware with CM11. I flashed it in cwm and it works fine
Click to expand...
Click to collapse
Maybe ill try switching over to CWM and try it. Did you notice better wifi/LTE coverage with the new firmware?
bigw34 said:
Maybe ill try switching over to CWM and try it. Did you notice better wifi/LTE coverage with the new firmware?
Click to expand...
Click to collapse
It's about the same
For anyone reading this thread and had trouble like me with the modem, try flashing this: https://dl.dropboxusercontent.com/u/48640/android/VRUEMJ9_zif.zip
I flashed it using latest twrp on slim rom/slimkat 4.4.2, and it worked perfectly.
Thanks to "zif" at this thread: http://forum.xda-developers.com/showthread.php?t=2577809&page=6
I am having a really hard time with my evo lte!
Problem:
I had CM nighties running prior to downloading and using the official HTC RUU for sense 5 and android 4.3.
I ran the RUU and everything was fine, my antennas, bootloader, etc updated.
I decided to go back to CM so I rooted (attempted to later you will find out what went wrong) and installed CWM (latest one 6.0.4.6). I downloaded a cm rom and flashed it with the latest Gapps but every time I flash CM's nightly, it fails. I factory reset and rebooted and it asked me if I wanted to root? <--- think the problem is there... But anyway, I can flash Gapps fine but not CM's roms. I tried stable nightlies and different ones.
Any ideas?
i.imgur.com/2TACLZ0.jpg
imgur.com/rIOGrn4
I am a noob here, I apologize in advance.
Thanks in advance to ones that can help!
Which cm version did u flash?
Sent from my Nexus 5 using Tapatalk
My CM version
klin1344 said:
Which cm version did u flash?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
cm-11-20140407-NIGHTLY-jewel.zip
rohanpatelt7 said:
I am having a really hard time with my evo lte!
Problem:
I had CM nighties running prior to downloading and using the official HTC RUU for sense 5 and android 4.3.
I ran the RUU and everything was fine, my antennas, bootloader, etc updated.
I decided to go back to CM so I rooted (attempted to later you will find out what went wrong) and installed CWM (latest one 6.0.4.6). I downloaded a cm rom and flashed it with the latest Gapps but every time I flash CM's nightly, it fails. I factory reset and rebooted and it asked me if I wanted to root? <--- think the problem is there... But anyway, I can flash Gapps fine but not CM's roms. I tried stable nightlies and different ones.
Any ideas?
i.imgur.com/2TACLZ0.jpg
imgur.com/rIOGrn4
I am a noob here, I apologize in advance.
Thanks in advance to ones that can help!
Click to expand...
Click to collapse
You must flash a version with updated partition support as the 4.3 update changed everything. CM nightlies do not support this, they only work with those who have no updated to the new format that came with 4.3. You'll need to get a build with the support commit included. Fairly easy to do yourself if you have the time and storage on your hard drive.
Sent from my Nexus 5 using Tapatalk
Reply
numel007 said:
You must flash a version with updated partition support as the 4.3 update changed everything. CM nightlies do not support this, they only work with those who have no updated to the new format that came with 4.3. You'll need to get a build with the support commit included. Fairly easy to do yourself if you have the time and storage on your hard drive.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks for the speedy reply! Quick question, does this mean I need to find an older RUU and use it on my phone before I reroot and try again? Also if you do not mind, can you post quick steps to doing this maybe with links?
The help is greatly appreciated! This is my daily driver phone.
rohanpatelt7 said:
Thanks for the speedy reply! Quick question, does this mean I need to find an older RUU and use it on my phone before I reroot and try again? Also if you do not mind, can you post quick steps to doing this maybe with links?
The help is greatly appreciated! This is my daily driver phone.
Click to expand...
Click to collapse
If you want to flash nightlies, you will have to RUU back to an older version. You'll have to run the RUU and go through all the steps again, yes. An alternative is to use ROMs that have been updated to support the new partitions. I believe CaptainThrowback has a list in Android Development that lists all the builds that support. Not included in the list is Pac-Rom which can be found in Original Android Development.
Sent from my Nexus 5 using Tapatalk
Thanks
numel007 said:
If you want to flash nightlies, you will have to RUU back to an older version. You'll have to run the RUU and go through all the steps again, yes. An alternative is to use ROMs that have been updated to support the new partitions. I believe CaptainThrowback has a list in Android Development that lists all the builds that support. Not included in the list is Pac-Rom which can be found in Original Android Development.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thank you sir, I will give this a try! Will report back results if any other person is going through the same situation.
rohanpatelt7 said:
Thank you sir, I will give this a try! Will report back results if any other person is going through the same situation.
Click to expand...
Click to collapse
Or you could flash this version of CM with new partition layout
http://d-h.st/BOy
Reply
GoblinZ said:
Or you could flash this version of CM with new partition layout
http://d-h.st/BOy
Click to expand...
Click to collapse
Thanks! I am going to flash this after my root tonight but just a question, are you going to be following the updates with the nighties? CM's updater won't work will it with your build of it? Thanks!
Here is a deodexed fully stock rooted rom with busybox and with knox removed. This is For MDK Bootloader I dont know If it will work on SS or Not.
Rom
VZW_NC5_AROMA_4_29_30.zip Aroma Installer Choose what to Install
I545_VRUFNC2_AROMA_4_18_14.zip Aroma Installer Choose what to Install
I545VRUFNC2_4_17_14.zip Full Stock Installs Everything
Thanks to these guys!
Link to leaked Verizon 4.4.2 TW Rom
Link to Jeboo Kernel go give him a thanks!
Link to update modem radios Thanks Surge1223!
Oh man!!! Great job as always! Can't wait to try this out
Sent from my SCH-I545 using XDA Premium 4 mobile app
jrkruse said:
Here is a deodexed fully stock rooted rom with busybox and with knox removed. This is from the leaked Verizon 4.4.2 TW Kitkat Rom. It Includes stock kernel by Jeboo. Can Only be flashed with custom recovery on MDK bootloader!
Rom
I545VRUFNC2_4_17_14.zip
Thanks to these guys!
Link to leaked Verizon 4.4.2 TW Rom
Link to Jeboo Kernel go give him a thanks!
Link to update modem radios Thanks Surge1223!
Click to expand...
Click to collapse
Thank you ! Let the Roms begin ???
Sent from an Echoenian
Thanks once again
Nice. Been waiting a long time for this!
Anyone able to download, keep getting an error from androidfilehost?
vicn77 said:
Anyone able to download, keep getting an error from androidfilehost?
Click to expand...
Click to collapse
Mine is DL'ing fine....so far, so good
dl works fine md5 matches . Now to recovery, thanks JrKruse!
Sent from my SCH-I545 using Tapatalk
Word Up. Thank Jrkruse!
The flash failed for me: "format () expects 5 args, got 4"
Status 7
I'm using Philz recovery
3colby3 said:
Mine is DL'ing fine....so far, so good
Click to expand...
Click to collapse
heath2805 said:
dl works fine md5 matches . Now to recovery, thanks JrKruse!
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
My fault, didn't have enough room to download. Downloading fine now.
So it seems to have flashed fine, but I'm getting random vibrate patterns every 10 seconds or so? Very weird...
HoosierDaddy2442 said:
So it seems to have flashed fine, but I'm getting random vibrate patterns every 10 seconds or so? Very weird...
Click to expand...
Click to collapse
Which recovery are you using? It wouldn't flash for me using Philz.
TWRP
HoosierDaddy2442 said:
So it seems to have flashed fine, but I'm getting random vibrate patterns every 10 seconds or so? Very weird...
Click to expand...
Click to collapse
I heard surge mentioning that too. Mines running great with no problems. I used TWRP 2.5.0.2 with verified MD5 .
Sent from my SCH-I545 using Tapatalk
Yep, all that checked out fine for me. Will wait and see what can be done.
HoosierDaddy2442 said:
Yep, all that checked out fine for me. Will wait and see what can be done.
Click to expand...
Click to collapse
Hmm....Strange you on wifi? Haven't been able to test that yet.
Sent from my SCH-I545 using Tapatalk
jrkruse said:
Here is a deodexed fully stock rooted rom with busybox and with knox removed. This is from the leaked Verizon 4.4.2 TW Kitkat Rom. It Includes stock kernel by Jeboo. Can Only be flashed with custom recovery on MDK bootloader!
Rom
I545VRUFNC2_4_17_14.zip
Thanks to these guys!
Link to leaked Verizon 4.4.2 TW Rom
Link to Jeboo Kernel go give him a thanks!
Link to update modem radios Thanks Surge1223!
Click to expand...
Click to collapse
How will this differ from your Aroma'd version besides the lack of customizations of the install? Will you be Aroma-ing this ROM too with your own twist? Is this more or less stable than the International version we've been dealing with? Sorry for all the questions. Just trying to figure out which KitKat TW ROM is best and most stable for this phone. Seems like this Verizon ROM would be in the long run.
Holy ****, it's finally here after all these months!
Is it rooted, with everything functional? I had to go back to 4.3 because other 4.4 roms were buggy.
fafaffy said:
Holy ****, it's finally here after all these months!
Is it rooted, with everything functional? I had to go back to 4.3 because other 4.4 roms were buggy.
Click to expand...
Click to collapse
Yes its rooted and no issues here.
Sent from my SCH-I545 using Tapatalk
I recommend if your having trouble flashing using Philz Custom recovery uncheck signature verification and uncheck not to allow old recovery scripts
philz_touch_6.26.4-jflte.zip
If you want to keep using TWRPI suggest updating to the lattest
TWRP_2-7-0-1zip.zip
so I got this galaxy s5 (free) to replace the S4 I had.. I'm on AT&T and the S5 is a T-Mobile device.. I unlocked and am currently using on AT&T without any issues.. I tried Cyanogenmod 12 on it.. had way too many Bluetooth music issues.. so I switched back to a rooted t-mobile stock.. which is terrible.. bluetooth music works great but everything is is painfully slow.. so I want to find a good fast custom rom (that also has proper bluetooth music support).. With so many device versions and so many custom roms I'm just a bit perplexed.. I found some that are debloated stock roms which seem like that would be good. but I'm just a bit confused on what parts I need to have as "t-mobile g900t" and which parts I don't have to have that way? so yeah this is a bit of a newbie question (even though I have run 4 or 5 custom roms in the past (original galaxy s and my s4 both had custom roms). .but those were always at&t devices on at&t network.. so was an easier choice..
at any rate.. looking for some tips on how to best find the right rom.. Would love to do this today/tomorrow.. avoid messing with the phone during the work week..
Thanks in advance!!
Gary
Try the latest stock ROM for the phone. Many of us were having issues with lag with prior 5.1.1 ROMS. The latest ROM has fixed all these issues. Very snappy.
i feel like i remember seeing bluetooth/audio fixes & updates in the CM13 nightly changelogs, you also didnt specify which CM 12 you installed... the last 12.1 snapshot from october or the last nightly from december?
You can run whatever rom you want. If it works with KLTE it works on your phone. Check the S5 unified development. Cyanogen has always been crap on this phone, probably always will be. Try an AOSP based one like Tesla or TipsyOS (probably won't find them on this site, they post all of their roms on their Google+ page)
Unfortunately the only Marshmallow available for this phone so far is CM-13 based so it's also crap and full of bugs...
To be honest, no ROM you find will be perfect. The most stable thing I've found is to just use a rooted stock ROM and debloat the hell out of it then run Google Now launcher or Nova and forget that you have a Samsung device for a while, until the next OTA comes out and you have to do the process over again.
Sean89us said:
You can run whatever rom you want. If it works with KLTE it works on your phone. Check the S5 unified development. Cyanogen has always been crap on this phone, probably always will be. Try an AOSP based one like Tesla or TipsyOS (probably won't find them on this site, they post all of their roms on their Google+ page)
Unfortunately the only Marshmallow available for this phone so far is CM-13 based so it's also crap and full of bugs...
To be honest, no ROM you find will be perfect. The most stable thing I've found is to just use a rooted stock ROM and debloat the hell out of it then run Google Now launcher or Nova and forget that you have a Samsung device for a while, until the next OTA comes out and you have to do the process over again.
Click to expand...
Click to collapse
much improved deep sleep battery means crap & full of bugs? i'm over a week behind on nightlies & there arent that many bugs... http://www.cmxlog.com/13/klte/ things are improving all the time, only CM 12.1 is stuck... but the last december nightly isnt buggy either
Sort of forgot about this thread. first Thanks for the replies.. So I have been using CM13 since I posted this.. and this has great for speed.. but BlueTooth continues to suck.. no matter what bluetooth device I use with this Rom it skips and stutters. I've finally had enough.. it's been quite a long time with this issue so time for me to switch.. I will try one of the rooted stock roms and debloat it with one of those tools.. thanks again everyone!
gpinkham said:
Sort of forgot about this thread. first Thanks for the replies.. So I have been using CM13 since I posted this.. and this has great for speed.. but BlueTooth continues to suck.. no matter what bluetooth device I use with this Rom it skips and stutters. I've finally had enough.. it's been quite a long time with this issue so time for me to switch.. I will try one of the rooted stock roms and debloat it with one of those tools.. thanks again everyone!
Click to expand...
Click to collapse
Go to the international s5 site look at Tamirda's phoenix rom . It's 6.0.1 mm very snappy very few bugs. Very moddable. Just load a stock mm rom from here first than so you have the proper bootloader and modem. After installing you feel like you got a mini s7. Good good.
Sean89us said:
You can run whatever rom you want. If it works with KLTE it works on your phone. Check the S5 unified development. Cyanogen has always been crap on this phone, probably always will be. Try an AOSP based one like Tesla or TipsyOS (probably won't find them on this site, they post all of their roms on their Google+ page)
Unfortunately the only Marshmallow available for this phone so far is CM-13 based so it's also crap and full of bugs...
To be honest, no ROM you find will be perfect. The most stable thing I've found is to just use a rooted stock ROM and debloat the hell out of it then run Google Now launcher or Nova and forget that you have a Samsung device for a while, until the next OTA comes out and you have to do the process over again.
Click to expand...
Click to collapse
Sent from my SM-G935F using XDA-Developers mobile app
inspired55 said:
Go to the international s5 site look at Tamirda's phoenix rom . It's 6.0.1 mm very snappy very few bugs. Very moddable. Just load a stock mm rom from here first than so you have the proper bootloader and modem. After installing you feel like you got a mini s7. Good good.
Click to expand...
Click to collapse
Question.. I currently have CM13 loaded in this phone.. so do I still need to do the "Just load a stock mm rom" first? I assumed I already had the proper bootloader and modem..
thanks!
gpinkham said:
Question.. I currently have CM13 loaded in this phone.. so do I still need to do the "Just load a stock mm rom" first? I assumed I already had the proper bootloader and modem..
thanks!
Click to expand...
Click to collapse
If you have the mm bootloader and modem installed just wipe and flash. But I believe cm 13 could be ran on the lp bootloader. I odined the stock tar first that way you know all the partitions are proper. Than Odin Twrp 3 0.0 . Make sure you back up your data from internal storage because when you Odin factory package it wipes phone storage. I learned this the hard way lost a bunch of pictures lol anyway I found this to be the best way. Hoping this helps....
Sent from my SM-G935F using XDA-Developers mobile app
inspired55 said:
If you have the mm bootloader and modem installed just wipe and flash. But I believe cm 13 could be ran on the lp bootloader. I odined the stock tar first that way you know all the partitions are proper. Than Odin Twrp 3 0.0 . Make sure you back up your data from internal storage because when you Odin factory package it wipes phone storage. I learned this the hard way lost a bunch of pictures lol anyway I found this to be the best way. Hoping this helps....]
Click to expand...
Click to collapse
1. is there a way to tell which bootloader I have?
2. I'm running teamwin.. I assume that's fine for flashing Phoenix but does one really need Odin?
3. I had a rooted stock image before I installed CM13.. (the stock image was so dang slow.. forget which.)
thanks again!
Gary
gpinkham said:
1. is there a way to tell which bootloader I have?
2. I'm running teamwin.. I assume that's fine for flashing Phoenix but does one really need Odin?
3. I had a rooted stock image before I installed CM13.. (the stock image was so dang slow.. forget which.)
thanks again!
Gary
Click to expand...
Click to collapse
Get any phone info app and check and see if your bootloader ends in pe1 if it don't you don't have mm bootloader. Teamwin is twrp just make sure it's version 3.0.0 that version seems to do best with the phoenix rom.
Sent from my SM-G935F using XDA-Developers mobile app
inspired55 said:
Get any phone info app and check and see if your bootloader ends in pe3 if it don't you don't have mm bootloader. Teamwin is twrp just make sure it's version 3.0.0 that version seems to do best with the phoenix rom.
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
Sorry for eavesdropping but I dont think that PE3 came yet, either via OTA or on sammobile.
Correct me if I am wrong
Sent from my SM-G900T using XDA-Developers mobile app
S.N [user=2501176 said:
@.k.[/user]3;67525688]Sorry for eavesdropping but I dont think that PE3 came yet, either via OTA or on sammobile.
Correct me if I am wrong
Sent from my SM-G900T using
I'm sorry you are correct I meant pe1 pe3 is for the Note 4. I've been working with a friends note 4 past few days. Thanks for catching my error . Hate giving wrong advice... original post edited...
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
inspired55 said:
Get any phone info app and check and see if your bootloader ends in pe3 if it don't you don't have mm bootloader. Teamwin is twrp just make sure it's version 3.0.0 that version seems to do best with the phoenix rom.[/URL]
Click to expand...
Click to collapse
thanks for sticking with me on the all the newbie questions.. bootloader version reported as G900TUV1FOG6.. later in the list it shows Latest Firmware: G900TUVUGPE1/G900TTMBGPE1/G900TUVU1GPE1.. so at first I was thinking I was ok.. but that second entry had me wondering.. (dang.. just noticed this was never submitted (from 6/28).. oh well)..
ok.. So I assumed I'm good to go.. installed the latest TWRP (3.0.2).. wiped the data area and tried to flash Phoenix.. It starts installing Aroma.. and within a couple of seconds the phone reboots back into TWRP.. did this a few times.. rebooting into the OS gets me a new Cyanagenomod not Phoenix.. figure I must be missing a step somewhere (or have something that is preventing Phoenix from installing).. thoughts?
thanks again!!
gpinkham said:
ok.. So I assumed I'm good to go.. installed the latest TWRP (3.0.2).. wiped the data area and tried to flash Phoenix.. It starts installing Aroma.. and within a couple of seconds the phone reboots back into TWRP.. did this a few times.. rebooting into the OS gets me a new Cyanagenomod not Phoenix.. figure I must be missing a step somewhere (or have something that is preventing Phoenix from installing).. thoughts?
thanks again!!
Click to expand...
Click to collapse
I think you still don't have the correct bootloader . The firmware is mm because your using CM13. The easiest way to get it done for sure is to odin the official MM firmware. Than install Twrp 3.0.0 flash superuser to have root . Reboot in recovery and flash phoenix rom v12.0 than the 12.6 update. This may take extra time this way but all the partitions will be correct. Or odin bootloader in BL slot and modem in cp slot . Don't set for auto reboot pull battery back into download mode Odin Twrp pull battery. Reboot into recovery than flash superuser. Than flash phoenix. Good luck
Sent from my SM-G935F using XDA-Developers mobile app
inspired55 said:
I think you still don't have the correct bootloader . The firmware is mm because your using CM13. The easiest way to get it done for sure is to odin the official MM firmware. Than install Twrp 3.0.0 flash superuser to have root . Reboot in recovery and flash phoenix rom v12.0 than the 12.6 update. This may take extra time this way but all the partitions will be correct. Or odin bootloader in BL slot and modem in cp slot . Don't set for auto reboot pull battery back into download mode Odin Twrp pull battery. Reboot into recovery than flash superuser. Than flash phoenix. Good luck
Click to expand...
Click to collapse
OK.. you may be right.. I downgraded TWRP to 3.0.0 and the install started working fine.. but now the reboot into Phoenix has been going for about 35 mins.. I know it can take some time but that seems extreme.. will wait a bit longer and if it doesn't work I'll try the steps you listed above..
thanks again
Gary
inspired55 said:
I think you still don't have the correct bootloader . The firmware is mm because your using CM13. The easiest way to get it done for sure is to odin the official MM firmware.
Click to expand...
Click to collapse
Well I used Heimdall.. flashed a bootloader image MM.. now the phone seems to be completely bricked.. get the samsung galaxy s5 screen keys light up.. and just sits there.. time to toss it I guess. .(was a freebie anyway)..
gpinkham said:
Well I used Heimdall.. flashed a bootloader image MM.. now the phone seems to be completely bricked.. get the samsung galaxy s5 screen keys light up.. and just sits there.. time to toss it I guess. .(was a freebie anyway)..
Click to expand...
Click to collapse
Got the phone back to CM13. so back to crappy bluetooth music streaming.. ha.. oh well I will give this try again some other day..
thanks again for the help!
Gary
gpinkham said:
Got the phone back to CM13. so back to crappy bluetooth music streaming.. ha.. oh well I will give this try again some other day..
thanks again for the help!
Gary
Click to expand...
Click to collapse
Gary look in this general section for the post that instructs you how to install factory mm. Follow the guide. Google to see how to install factory tar files using Lunix . I'm guessing my instructional writing skills leave something to be desired lol . Once you have the factory mm up and running install Twrp flash superuser reboot. Than reboot into recovery flash phoenix rom. Good good
Sent from my SM-G935F using XDA-Developers mobile app