Related
Every time my phone dies, or I turn it off or I reboot, no matter what 4.3 rom I'm using, it stays on the boot animation until I either pull battery or hold power to turn off. I've flashed, reflashed, dirty flashed clean flashed (I format the system as well) I've tried CM10.2, PacMan, and Beanstalk and all three have this issue. I haven't read anywhere that someone else is having problems like this. Please advise!:fingers-crossed:
Aiekazie said:
Every time my phone dies, or I turn it off or I reboot, no matter what 4.3 rom I'm using, it stays on the boot animation until I either pull battery or hold power to turn off. I've flashed, reflashed, dirty flashed clean flashed (I format the system as well) I've tried CM10.2, PacMan, and Beanstalk and all three have this issue. I haven't read anywhere that someone else is having problems like this. Please advise!:fingers-crossed:
Click to expand...
Click to collapse
I have the same problem. Can't seem to figure it out either. The only way to fix it is to reflash. At first I thought it was an app or setting but after a clean install and boot I reboot without going through the setup but it still would not reboot.
Same
I'm having the exact same issue and as you have, I've tried everything I can think of.
Ive tried flashing CM 10.2 + GAPPS, just CM10.2, 3 different types of Google Edition Roms and in every case the initial boot is fine... It boots and works perfectly, however on first reboot, it wont boot back up.
It just sits on the SGS4 logo, have left it for 25 minutes.
I would really love to know how to fix this. The only way to get it working after it has been restarted once is to delete cache, dalvik AND data...
Cache and Dalvik don't fix it.
figured a little bit...
Well now that I've flashed it using TWRP instead if CWM touch, it does reboot back up. However with TWRP flashing I'm getting reboots while typing.
Aiekazie said:
Well now that I've flashed it using TWRP instead if CWM touch, it does reboot back up. However with TWRP flashing I'm getting reboots while typing.
Click to expand...
Click to collapse
I used Goo manager to install TWRP. Then used that to install the latest nightlies and latest gapps - 0813. So far so good!!
anandlal said:
I used Goo manager to install TWRP. Then used that to install the latest nightlies and latest gapps - 0813. So far so good!!
Click to expand...
Click to collapse
Gonna give this a try I'll post back.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Aiekazie said:
Gonna give this a try I'll post back.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Click to expand...
Click to collapse
If this works can you post a quick overview of what you did...
Because I've tried reinstalling TWRP and it didnt seem to help, but happy to try again if it works for you!
All is good!
Been running it since I installed using the method i mentioned above.
The ROM is running smoothly with no issues or reboots. I did reboot it a couple times to verify that it is booting properly.
Alright...I installed TWRP through Goomanager, when I did this I selected the manual option and booted into CWM and performed a BACK UP first...flashed the TWRP.zip file that goo downloaded for me. Version 2.6.0.1 I think it was? I rebooted into recovery and found it successfully flashed TWRP, I went into the wipe options and chose data cache system and dalvik, backed out and chose install and reinstalled Cm10.2 and GApps. I'm able to reboot and all but I'm still finding reboots here and there....I was able to go 18hrs on battery (awesome for stock settings!) And without a single reboot.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Yup that's the same for me. Random reboots here and there but overall very solid with great battery life.
Can't wait for more nightlies.
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
Ya know. Now that I've let 8.14.2013 nightly settle in I havent had a reboot in quite some time. I might stick here til some major change logs come..
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Try This Rom
[Rom][JellyBean][4.3][BeanStalk Build 4.3.05][updated 8.19]
I have Flashed it with no issues :fingers-crossed:
hope this will help you
Yeah, I posted in the dev thread, that particular one gives me reboots while typing if the vibrate on key press is on. Other than that it was working fine. I'm still digging the cm 14th nightly.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Aiekazie said:
Yeah, I posted in the dev thread, that particular one gives me reboots while typing if the vibrate on key press is on. Other than that it was working fine. I'm still digging the cm 14th nightly.
Sent from my SAMSUNG-SGH-I717 using Tapatalk 4
Click to expand...
Click to collapse
Yup same with me. Kinda surprised that there have been no more Nightlies for this though, The Note II has one updated to 18th.
I'm sticking with this.
After running just about every ROM for this device, I recently flashed my first stock based ROM (cooked 1.8). However since this time I've been unable to flash back to any aosp ROM. I get boot looped on every one. I've tried everything. Yet, I can flash cooked again no problem. I know there's something I'm missing. Any help would be great.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
You have a nandroid backup right? Restore that then flash whatever you want.
Sent from my SGH-I777 using Tapatalk 2
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
adrock74 said:
Backup won't boot either. That was my first plan.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Search for Siyah kernel v4.3.3 in the forums and install, restart recovery and flash away. Should take care of it.
T
Sent from my SGH-I777 using Tapatalk 2
I always have kept that kernel on standby but that didn't work. I've tried every kernel. Can't believe backups won't even boot. I flashed cook's ROM wipe before his ROM the first time, wonder if that did something.
Sent from my SAMSUNG-SGH-I777 using XDA Premium 4 mobile app
Try Odin to stock and start from scratch. A lot of work but hey what do you have to lose. :beer:
Sent from my SGH-I777 using xda app-developers app
First find a compatible Kernel for the AOSP ROM your trying to flash. Flash that Kernel.
Second, after the flashing is done, reformat the device; cache, dalkiv cache and system and system settings.
Third, reboot into recovery mode from the recovery menu itself.
Fourth, flash the kernel one more time.
Fifth, flash the AOSP ROM of your choice.
Sixth, reboot back into recovery menu.
Seventh, reformat once more.
Eigth, reboot the device.
As you should know, the first boot up after flashing a ROM takes the longest. Give it like a minute or two.
If this doesn't work, you have to flash a kernel that was compatible with the "cooked" rom you were using. Then from there do a reformat from the recovery menu. Once reformat is done, flash the AOSP kernel, then flash the AOSP ROM right after. Then reformat once more and reboot as normal.
If that doesn't work, flash compatible kernel with the "cooked" ROM your using now and also relay the cooked ROM, and then use Odin to bring it back to stock un-rooted. From there, do as you wish.
Butchr said:
Have you tried to format system under mounts and storage after your factory reset, and before you flash your rom and gapps? Just a suggestion. Not sure it will fix you problem or not. It seems as if I had a problem similar to what you are describing after running a Samsung based rom in the past. I believe that was the cure to my issue.
Click to expand...
Click to collapse
That is exactly what needed to be done. Mr cook actually has another thread with cwm flashable wipe scripts that would have done that. Quite handy :thumbup:
I've had no luck with KitKat getting provisioned properly. Every time it shows no MIN or Mdn out prl. I can flash back to twrp and restore slimbean and have no connection issues. I've successfully flashed stock mc3 in cwm and gotten service then tried cm11 and no luck.
Anyone have any suggestions?
Use cwm recovery for kitkat
Sent from my SCH-I605 using XDA Premium 4 mobile app
Use CWM
nikhil.kdhand said:
Use cwm recovery for kitkat
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I did. I was in twrp on slimbean. Flashed CWM touch, booted into CWM recovery. From there I factory reset and wiped system. Flashed CM11, PA_GAPPS 4.4 12/12/13 and had no service. Flashed Beans stock mc3 in CWM and had signal. Then tried CM11 again after having service in CWM with stock. At this point I'm back in TWRP with Slimbean.
Thanks in advance!
Hope you are using cm11 which is 2611 built
Sent from my SCH-I605 using XDA Premium 4 mobile app
cm11
nikhil.kdhand said:
Hope you are using cm11 which is 2611 built
Sent from my SCH-I605 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I previously had the same issue with the 2611 build and I'd now happening on the 12-9 build
Same Issue
Currently having the issue, i am always stuck in roaming and after surfing the web about the issue following some other phone guides as well i am still having the issue, after flashing kitkat, still no service. I also went back to stock and reset the phone as well, also tried doing a refresh on the antenna as well still no cigar.
problem solved!
joshsikora said:
Currently having the issue, i am always stuck in roaming and after surfing the web about the issue following some other phone guides as well i am still having the issue, after flashing kitkat, still no service. I also went back to stock and reset the phone as well, also tried doing a refresh on the antenna as well still no cigar.
Click to expand...
Click to collapse
After some thinking, I noticed that the mj9 stock ROM was available. I odin'd back to stock, ran casual, used odin to flash twrp 2.6.3.1, flashed beanstown stock odexed mj9 ROM. After verifying signal, I did factory reset from twrp, and installed sbrissen 12-9 ota 4.4 ROM and gapps 12-13. Success. Going to backup and try slimkat next, but thought I'd update you all.
Hello, I have an i717 and I'm having an extremely annoying issue with LiquidSmooth 3.1. So basically, after the first boot/setup, it runs perfectly fine. Beautifully. But if I turn it off, it won't load the OS when I turn it on again. It'll sit on a black screen for several hours. I've tried reinstalling this ROM about 5 times and had the same issue each time.
Anyone having the same issue, or know a fix?
MoronDroid said:
Hello, I have an i717 and I'm having an extremely annoying issue with LiquidSmooth 3.1. So basically, after the first boot/setup, it runs perfectly fine. Beautifully. But if I turn it off, it won't load the OS when I turn it on again. It'll sit on a black screen for several hours. I've tried reinstalling this ROM about 5 times and had the same issue each time.
Anyone having the same issue, or know a fix?
Click to expand...
Click to collapse
Just restarted the phone, booted after the 12th time.
LS goes through the bootanimation twice so it will look like its boot looping. Plus it does seem to take a while to boot into the os, just gotta be patient with the ROM on initial boot.
sent from my sweetened CandyKat SGH-I717
dzee206 said:
LS goes through the bootanimation twice so it will look like its boot looping. Plus it does seem to take a while to boot into the os, just gotta be patient with the ROM on initial boot.
sent from my sweetened CandyKat SGH-I717
Click to expand...
Click to collapse
This is really weird. I formatted all of the partitions, and did a fresh re-install of LiquidSmooth 3.1. It installed just fine, the Polluti0n V2 patch installed fine as well. But when I tried installing the Gapps (pa gapps stock 4.4.4 20140629), it came up with:
"file_getprop: failed to stat "/system/build.prop": No such file or directory.
E: Error in /sdcard/pa_gapps-stock-4.4.4-20140629-signed.zip
(status 7)
Installation aborted."
MoronDroid said:
This is really weird. I formatted all of the partitions, and did a fresh re-install of LiquidSmooth 3.1. It installed just fine, the Polluti0n V2 patch installed fine as well. But when I tried installing the Gapps (pa gapps stock 4.4.4 20140629), it came up with:
"file_getprop: failed to stat "/system/build.prop": No such file or directory.
E: Error in /sdcard/pa_gapps-stock-4.4.4-20140629-signed.zip
(status 7)
Installation aborted."
Click to expand...
Click to collapse
Status 7 is upgrade your recovery, but I have never seen it hit with gapps or just gapps.
Weird
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Status 7 is upgrade your recovery, but I have never seen it hit with gapps or just gapps.
Weird
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
How do I fix this?
MoronDroid said:
How do I fix this?
Click to expand...
Click to collapse
What recovery are you running?
Have you tried a different gapps package?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
What recovery are you running?
Have you tried a different gapps package?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I have tried 3 different Gapps packages, all had the same result. I don't know what recovery version I am using. But I'm using CWM 5.5.0.4
MoronDroid said:
I have tried 3 different Gapps packages, all had the same result. I don't know what recovery version I am using. But I'm using CWM 5.5.0.4
Click to expand...
Click to collapse
CWM is your recovery and your version#
TWRP is also a recovery used.
Let me ask you how long have you been flashing on this version of recovery and is there an updated version?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
CWM is your recovery and your version#
TWRP is also a recovery used.
Let me ask you how long have you been flashing on this version of recovery and is there an updated version?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I purchased this phone used, and I've had it for 2.5 weeks and have been flashing every couple of days between CM10.1.3 and LS 3.1. I believe there may be an updated version, I'll look around.
MoronDroid said:
I purchased this phone used, and I've had it for 2.5 weeks and have been flashing every couple of days between CM10.1.3 and LS 3.1. I believe there may be an updated version, I'll look around.
Click to expand...
Click to collapse
Oh yeah....if you are flashing CM 10 with it wow. That is quite an older version and LS 3.1 is kit kat. CM 10 is the equivalent of JB so your bouncing back and forth and the up to date recoveries were designed to handle KK.
go to development and find the TWRP thread from "GIMMIEORILLTELL". it is TWRP version 2.8.0.1 ???
TWRP is a touch based recover which is sooooooo simple to use. No more toggle of the volume rocker.
Download and flash like you would any rom.
Once flashed, boot up whatever or pull battery and replace.
Boot back into recovery and it will be there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Oh yeah....if you are flashing CM 10 with it wow. That is quite an older version and LS 3.1 is kit kat. CM 10 is the equivalent of JB so your bouncing back and forth and the up to date recoveries were designed to handle KK.
go to development and find the TWRP thread from "GIMMIEORILLTELL". it is TWRP version 2.8.0.1 ???
TWRP is a touch based recover which is sooooooo simple to use. No more toggle of the volume rocker.
Download and flash like you would any rom.
Once flashed, boot up whatever or pull battery and replace.
Boot back into recovery and it will be there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I'll surely give it a try, but not at this ungodly hour. I'll be without a phone for the day, but oh well.
captemo said:
Oh yeah....if you are flashing CM 10 with it wow. That is quite an older version and LS 3.1 is kit kat. CM 10 is the equivalent of JB so your bouncing back and forth and the up to date recoveries were designed to handle KK.
go to development and find the TWRP thread from "GIMMIEORILLTELL". it is TWRP version 2.8.0.1 ???
TWRP is a touch based recover which is sooooooo simple to use. No more toggle of the volume rocker.
Download and flash like you would any rom.
Once flashed, boot up whatever or pull battery and replace.
Boot back into recovery and it will be there.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
Flashed... and now it continually boot loops with the Samsung logo flashing. I think it's bricked. This is fantastic...
MoronDroid said:
Flashed... and now it continually boot loops with the Samsung logo flashing. I think it's bricked. This is fantastic...
Click to expand...
Click to collapse
No no no.......deep breath. Relax.
Pull battery.
What were you doing?
And what did you do?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
No no no.......deep breath. Relax.
Pull battery.
What were you doing?
And what did you do?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I selected the Zip using CWM, and told it to flash it. It successfully flashed, replacing the recovery.img. Then I reboot, and it bricked. Keeps flashing the samsung logo, pressing the recovery buttons (volume up+ power) does nothing. There's nothing I can do. It's dead.
MoronDroid said:
I selected the Zip using CWM, and told it to flash it. It successfully flashed, replacing the recovery.img. Then I reboot, and it bricked. Keeps flashing the samsung logo, pressing the recovery buttons (volume up+ power) does nothing. There's nothing I can do. It's dead.
Click to expand...
Click to collapse
Continually powers off and reboots. Vibrates and such.
MoronDroid said:
Continually powers off and reboots. Vibrates and such.
Click to expand...
Click to collapse
PRAISE THE ANDROID MODDING COMMUNITY
http://forum.xda-developers.com/showthread.php?t=1784857
MoronDroid said:
PRAISE THE ANDROID MODDING COMMUNITY
http://forum.xda-developers.com/showthread.php?t=1784857
Click to expand...
Click to collapse
Could be a stuck power button my friend. Flick the back of the phone behind the power button with your finger.
Dont be shy, but done break your finger either.
Very common problem.
Pull battery. Can you get download mode?
Unless you flashed files for the wrong device, I don't think you are bricked.
If you can get download mode, you are not bricked.
What file did you flash?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
captemo said:
Could be a stuck power button my friend. Flick the back of the phone behind the power button with your finger.
Dont be shy, but done break your finger either.
Very common problem.
Pull battery. Can you get download mode?
Unless you flashed files for the wrong device, I don't think you are bricked.
If you can get download mode, you are not bricked.
What file did you flash?
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
Click to expand...
Click to collapse
I fixed her. All I did was install Odin, and reinstall the stock ROM (md5 file). Also just rooted it with a new verision of CWM.
I want to thank you for your patience.
MoronDroid said:
I fixed her. All I did was install Odin, and reinstall the stock ROM (md5 file). Also just rooted it with a new verision of CWM.
I want to thank you for your patience.
Click to expand...
Click to collapse
We were getting close to that option. Every once in a while, and I have had to do it recently, we have to return to stock. Basically it takes out all the garbage that has accumulated, even though our process is clean.
I couldn't get anything to flash, not even an alternate recovery. Went back to complete stock, Re root and Bob is your uncle. (that means everything as good as new).
Glad your fixed. Dont let it detour you from flashing. It's a lot of fun. Keeps me off the streets.
Sent from my SAMSUNG-SGH-I527 using XDA Free mobile app
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Odin stock tar file.
Ammar335i said:
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Click to expand...
Click to collapse
What kernel are you using? You should be using the Stock CM12 Kernel with the same build date as your CM12 Install.
If you are running a different kernel on Official CM12 it will cause you to loose voice service. This issue started on April 03 2015 Nightly and hasn't been fixed yet.
What Radio/Baseband are you using? You should be on NH7 or NK4 when running CM12.
I will assume you are doing a clean install each time before flashing CM12 by performing a factory reset in recovery which wipes data, cache, and dalvik.
If you open up your dialer and dial *#*#4636#*#* it opens up a secret testing menu. Go to Phone Information and check if your "Set preferred network type:" is set as "LTE/CDMA". If it is not, do so and see if that changes anything.
Ammar335i said:
So recently I downloaded the cm12 nightly ROM on my Galaxy note 3 (sprint). Everything works fine, but I can't make/receive calls or text. I took it to the Sprint store and they told me to backup the ROM, then restore the backup of the stock ROM and do a profile update, then restore the custom ROM after that... Problem is that when I went back to the stock ROM I still had the problem, even after the profile update... this isn't my first time flashing ROMs, I've successfully flashed C-ROM and CM ROMs in the past and never came across this problem. Has anyone encountered a similar problem? And found a solution?
Click to expand...
Click to collapse
Sounds to me like you have bad download of CM12. I would download it again. Compare properties of both downloads see if you have the same number of bytes. Make sure you are rooted, stock OS, and a custom recovery installed. With the bootloader current binary and system status both having a "custom" status. Then try to flash CM12 through your custom recovery again. For more info just click flashing roms in my signature.
Get your carrier to check if your imei is blacklisted on their eir node connected to imeidb.org
Sent from my D5803 using XDA Free mobile app
rbeavers said:
Odin stock tar file.
Click to expand...
Click to collapse
Sorry I'm fairly new to this, you're gonna have to tell me how to find that
Sent from my SM-N9005 using XDA Free mobile app
Philux-X said:
What kernel are you using? You should be using the Stock CM12 Kernel with the same build date as your CM12 Install.
If you are running a different kernel on Official CM12 it will cause you to loose voice service. This issue started on April 03 2015 Nightly and hasn't been fixed yet.
What Radio/Baseband are you using? You should be on NH7 or NK4 when running CM12.
I will assume you are doing a clean install each time before flashing CM12 by performing a factory reset in recovery which wipes data, cache, and dalvik.
If you open up your dialer and dial *#*#4636#*#* it opens up a secret testing menu. Go to Phone Information and check if your "Set preferred network type:" is set as "LTE/CDMA". If it is not, do so and see if that changes anything.
Click to expand...
Click to collapse
I did the secret testing menu and changed the preferred network to LTE/CDMA and my calls started working and I started receiving sms (thank you). I can't send SMS though. Plus I lost data connectivity.
Also, I did do clean installs.
Sent from my SM-N9005 using XDA Free mobile app
Your on the wrong version of CM12. You need to be using hltespr. Your on hlte.
Download from here
http://download.cyanogenmod.org/?device=hltespr
Philux-X said:
Your on the wrong version of CM12. You need to be using hltespr. Your on hlte.
I tried downloading hltespr using TWRP but it kept saying unsuccessful, so I looked it up and others were having the same problem. So I switched to cwm recovery and it also said unsuccessful, and It gave the message saying that the ROM was hltespr and this device was hlte. Also all the other ROMs I downloaded in the past were all hlte and they worked fine.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
The old versions might have worked, but the new ones will not because of telephony changes done by CM on April03. Its getting hung up on the device name from build.prop. At least that has been my experience in the past.
Do an advanced wipe. Data/System/Cache/Dalvik
Do a Reboot to recovery
Then flash hltespr.
I'm using TWRP 2.8.5 btw.
Other things to try if that does not work:
You can try flasing hltespr ontop of hlte and see if that works.
Try flashing ViSXN3N custom rom and then flash hltespr.
Philux-X said:
The old versions might have worked, but the new ones will not because of telephony changes done by CM on April03. Its getting hung up on the device name from build.prop. At least that has been my experience in the past.
Do an advanced wipe. Data/System/Cache/Dalvik
Do a Reboot to recovery
Then flash hltespr.
I'm using TWRP 2.8.5 btw.
Other things to try if that does not work:
You can try flasing hltespr ontop of hlte and see if that works.
Try flashing ViSXN3N custom rom and then flash hltespr.
Click to expand...
Click to collapse
Okay I'll try that now, what is ViSXN3N custom ROM? I can't find anything on it
Sent from my SM-N9005 using XDA Free mobile app
ViSXN3N is here
http://forum.xda-developers.com/showthread.php?t=2696396
Philux-X said:
ViSXN3N is here
http://forum.xda-developers.com/showthread.php?t=2696396
Click to expand...
Click to collapse
Same problem, it says that this is for sm-n900p hltespr and i have hlte... also i just noticed that the message i have on the bottom of my posts say sent from my Sm-N9005..? is my phone confused? lol
update
So I installed cm11 to see if it would work and it did... I guess that means it was just the ROM? Although I loved the interface of cm12, so im going to try and flash a different version to see if that works.
Turns out when I first rooted my phone I downloaded a hlte recovery. After flashing a hltespr recovery using Odin and then flashing the correct hltespr ROM, everything worked fine. Thanks for the help guys
Sent from my SM-N900P using XDA Free mobile app