Database Users

[Q] Please Help!

So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.

khampton_03 said:
So I just rooted my Verizon Samsung Galaxy Note 3 with Kingo. All I have installed so far is SuperSu Pro and Titanium backup. Im on android 4.3 and I have the MJE version. (which seems to be the most uncommon because I cant find any help anywhere, so im posting this thread). All I want to know is how or if I even can get the CyanogenMod rom on my phone. This is my first android device ever and I've had it for 5 months and Im definitely never going back to Apple devices. Anyway, I just rooted, I dont care about tripping Knox because I dont have a warranty anyways. I just need someone to explain to me how to get all the things I need including CM. From what ive read I need CWM and GAPPS.
Click to expand...
Click to collapse
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?

Adam Browning said:
Slow down there. Lol. Do you have a developer edition Note 3 or just a regular retail Note 3 you purchased from Verizon?
Click to expand...
Click to collapse
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.

khampton_03 said:
Lol sorry Im very new to android. I got it from Verizon but i enabled Developer mode if thats what youre asking haha.
Click to expand...
Click to collapse
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Here is a link for the Eclipse thread: http://forum.xda-developers.com/showthread.php?t=2620723

Adam Browning said:
It's all good lol. No, developer mode just gives you some extra features if you want to debug your device. A developer edition Note 3 is a phone that was available directly from Samsung in a small quantity. It had the bootloader unlocked, which is a must for a AOSP ROM such as Cyanogenmod. Cyanogenmod requires a custom kernal, which a retail Note 3 (that you purchase through Verizon or another retail store) can not flash due to the locked bootloader. I would suggest peeking over in the Android Development section to check out the ROMs you are able to flash. Just steer clear of the ones saying for the developer edition or DE (for short). If you're wanting a ROM that has an AOSP feel to it though, check out Eclipse.
Click to expand...
Click to collapse
So could I somehow unlock the bootloader??

khampton_03 said:
So could I somehow unlock the bootloader??
Click to expand...
Click to collapse
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876

Adam Browning said:
Many people have looked into that, and no luck so far. It is still locked for devices such as ours. Kind of sucks, I know. Almost every Android phone I've owned, I have ran Cyanogenmod on it. With Verizon being difficult about locking the bootloaders, and Samsung introducing Knox, I don't think we will see a bootloader unlock anytime soon, if ever. With the new 4.4.2 leak that BeansTown106 has made available for us here:
http://forum.xda-developers.com/showthread.php?t=2726558
Kernal modules are enabled, so we may have a workaround in the near future for the locked bootloader. I would suggest not taking the OTA for 4.4.2, but instead flashing the leaked 4.4.2 that is available via that thread. Once you take the OTA, it isn't known if you'll ever be able to flash this leak, which may allow for a modified kernal and therefore AOSP ROMs. I may be mistaken in some of the details, and someone can correct me if I have said something wrong in this, but this thread will explain it a little better:
http://forum.xda-developers.com/showthread.php?t=2727876
Click to expand...
Click to collapse
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha

khampton_03 said:
So back to the beginning haha how do I flash a rom or what should I do since I just rooted and only have supersu haha
Click to expand...
Click to collapse
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?

Adam Browning said:
It all depends on what you want to do. How knowledgeable are you with rooting, Odin, and flashing in general?
Click to expand...
Click to collapse
Ive never flashed anything and I dont know how to use odin. Lol

khampton_03 said:
Ive never flashed anything and I dont know how to use odin. Lol
Click to expand...
Click to collapse
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558

Adam Browning said:
Lol. Oh goody. Well you're in for a lot of reading then. If you're already rooted and have supersu installed, then at least you have that part out of the way. The way that we install custom ROMs onto our phones (since the bootloader is locked) is by using Safestrap, developed by Hashcode. You can find any and all information you will need on it here:
http://forum.xda-developers.com/showthread.php?t=2517610
Safestrap gives you the ability to have multiple custom ROMs on your phone, without having to flash directly over your stock ROM (if you don't want). It is an application that you download onto your phone, you then open it up and install custom recovery. Once that is completed, you will then see a Safestrap screen everytime you turn on or restart your phone. I would suggest reading through or at least skimming the thread via the link provided above.
Once you have created a ROM slot and have it selected as the active slot, you can then proceed to install a custom ROM into that slot. Once you have everything set up, you can then switch between the custom ROM in "Slot x" to the stock ROM slot, giving you a cushion in case you completely screw up.
You're going to have to decide whether or not you want to stay on the 4.3 base, or update to the 4.4.2 base leak. The only advantages of either one are strictly your personal preference. There are a few that prefer the 4.4.2 base over the 4.3 base due to one reason or another. If you want to update the the newest 4.4.2 base leak though, follow the instructions provided via this link:
http://forum.xda-developers.com/showthread.php?t=2726558
Click to expand...
Click to collapse
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?

khampton_03 said:
So I am going to install Kitkat by watching the video on the thread. He said something about making sure the "MD5's match". What does that mean?
Click to expand...
Click to collapse
That, you don't really have to worry about honestly. I never check, though it may be good practice to. Just follow along with the video in the thread and you will be good to go. Just remember that after you install 4.4.2, you cannot flash 4.3 based ROMs. Also, there is a bug in Safestrap right now that renders the ROM slots somewhat useless, though you can attempt to use them at your own risk. If you want to flash one of the 4.4.2 based ROMs afterwards, it is suggested to back up the stock ROM, and flash the custom ROM in the stock ROM slot. All I can say is, goodluck. Lol. It is a fun process, though somewhat difficult at times. If you have anymore questions after the fact, just reply here. I'll help out as much as I can. It always puts a smile on my face to help convert an Apple fanboy/girl over to Android.

[Q] Verizon galaxy note 3 om Toubles!

Hi guys, I have a question regarding some roming stuff with the verizon version of the galaxy note 3. I am not new to roms by any means and I have been searching frantically to find one place with the complete answer im looking for. I made the early mistake of taking the OTA upgrade for KK, therefore I am currently running 4.4.2 with the NC4 build and NC4 baseband. Now while i have easily rooted my phone at this point with the towelroot. I also have had no problem getting the new 3.72 safestrap installed and running on my phone. My question now at this point is trying to figure out my next step with a new ROM I am trying install....I have been looking at all of my info to get the Hyperdrive ROM installed and I cant seem to find all the info I need in one location. Can I or can I not flash a new ROM to the NC4 baseband? I have seen some information where some people say I might be able to flash the NC2 kernal using ODIN and others say just trying to flash any ROM in general creates a black screen in which a battery pull needs to be done...yada yada.....? So in short, am I able to flash a ROM to the note 3 at this point or am I S.O.L?

sickorsane1 said:
Hi guys, I have a question regarding some roming stuff with the verizon version of the galaxy note 3. I am not new to roms by any means and I have been searching frantically to find one place with the complete answer im looking for. I made the early mistake of taking the OTA upgrade for KK, therefore I am currently running 4.4.2 with the NC4 build and NC4 baseband. Now while i have easily rooted my phone at this point with the towelroot. I also have had no problem getting the new 3.72 safestrap installed and running on my phone. My question now at this point is trying to figure out my next step with a new ROM I am trying install....I have been looking at all of my info to get the Hyperdrive ROM installed and I cant seem to find all the info I need in one location. Can I or can I not flash a new ROM to the NC4 baseband? I have seen some information where some people say I might be able to flash the NC2 kernal using ODIN and others say just trying to flash any ROM in general creates a black screen in which a battery pull needs to be done...yada yada.....? So in short, am I able to flash a ROM to the note 3 at this point or am I S.O.L?
Click to expand...
Click to collapse
Yes you can!! As long as the rom says that they support it you can. It says right here in red on the hyperdrive op-" This Rom is able to be installed on the Verizon Galaxy Note 3 On KitKat Bootloader with KK Safestrap" so make a backup with safestrap and try it out! And since it doesn't say anything about what specific one to use (I see what you are talking about) you won't have any harm with a backup. By the way the reason why a lot of roms were/are based on NC2 was because it was way more leniant than NC4 but now most if not all roms will support it. Just read the op.
Sent from my GalaxyAwesome

K03WL3R said:
Yes you can!! As long as the rom says that they support it you can. It says right here in red on the hyperdrive op-" This Rom is able to be installed on the Verizon Galaxy Note 3 On KitKat Bootloader with KK Safestrap" so make a backup with safestrap and try it out! And since it doesn't say anything about what specific one to use (I see what you are talking about) you won't have any harm with a backup. By the way the reason why a lot of roms were/are based on NC2 was because it was way more leniant than NC4 but now most if not all roms will support it. Just read the op.
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
Hmmm....well I tried to do the jasmine rom and I seem to have had the same problem that quite a few people are having. I put it in slot 1, created the rom slot and such, reboots into the recovery mode on ss just fine but then it goes to a black screen as if it's off. Have to battery pull. Maybe gonna try a different rom and see where I end up.

I'm running JasmineRom on the stock slot, but I also have the NC2 kernel..
Sent from my GalaxyAwesome

K03WL3R said:
I'm running JasmineRom on the stock slot, but I also have the NC2 kernel..
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
Should I try stock slot then? I used slot 1 with 3.75

You could try that (I would), or just flash the Nc2 stuff, then boot up (on stock), boot back to recovery and flash JasmineRom on stock. Those steps are just what I did and it worked for me. I'm really sorry but for the life of me that's the best I can remember about what I did. If none of that works, I'll try to install Jasmine onto a rom slot when I can.
Sent from my GalaxyAwesome

K03WL3R said:
You could try that (I would), or just flash the Nc2 stuff, then boot up (on stock), boot back to recovery and flash JasmineRom on stock. Those steps are just what I did and it worked for me. I'm really sorry but for the life of me that's the best I can remember about what I did. If none of that works, I'll try to install Jasmine onto a rom slot when I can.
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
I flashed Nc2 from a post on here and still didn't work....I'm about to give up

Have you tried just making a backup and starting over from fresh stock?
Sent from my GalaxyAwesome
---------- Post added at 11:35 PM ---------- Previous post was at 11:27 PM ----------
Also ask here- http://forum.xda-developers.com/showthread.php?t=2780031
Sent from my GalaxyAwesome

You need to flash the rom after you've wiped everything, then reboot to download mode and install the unified firmware via odin. That should work.
Sent from my GalaxyAwesome

K03WL3R said:
You need to flash the rom after you've wiped everything, then reboot to download mode and install the unified firmware via odin. That should work.
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
That did not work as that was the original plan of action. Only to come to a nice black screen

Okay, the dev just posted instructions in his last post on the JasmineRom thread. Check it out, it took me a while for it to work on my phone, it seems like a couple people are like us too.. Just a mix of trial and error
Sent from my GalaxyAwesome
Edit: and sorry I couldn't help so far, I don't really want to go back to stock considering this is my daily and I need a bigger sd card to make a full backup. [emoji53]

K03WL3R said:
Okay, the dev just posted instructions in his last post on the JasmineRom thread. Check it out, it took me a while for it to work on my phone, it seems like a couple people are like us too.. Just a mix of trial and error
Sent from my GalaxyAwesome
Edit: and sorry I couldn't help so far, I don't really want to go back to stock considering this is my daily and I need a bigger sd card to make a full backup. [emoji53]
Click to expand...
Click to collapse
All good! I finally got it working thanks to you saying the dev mentioned something! Jasmine up and running with no issues!

Jasmine V2
I never sign up for web sites but the Jasmine Rom is just so good I had to say thanks. Also concerning the excess power usage, I noticed that when plugged into AC charger the Android OS goes from 40% down to the 20's. Hope it helps. Again thanks to hsbadr for being a great DEV.
PS: K03WL3R I see you helping on hsbadr's forum, please convey my thanks and suggestion to him, for as I am a new member I can not post on his forum.
Thanks

Sorry it took me so long, there's an open discussion in the general/help section for jasminerom! I'm pretty sure new users can post there?

[Q] Developer Edition Tar 4.4.4 NE9

I may have messed up, but I am not 100%, not use to Samsung Devices.
I have a developers edition S5.
I tried to run updates but it would not take any update OTA even though there were two, NCG was the current room.
I flashed the ni2 via odin.
Now on the screen, instead of Mode: Developer, it says Qualcomm Secureboot.
I am not sure if I relocked the bootloader, if it can be unlocked,
Or this just the need to go into a recovery and flash a different rom.
Did I relock the bootloader?

hill180 said:
I may have messed up, but I am not 100%, not use to Samsung Devices.
I have a developers edition S5.
I tried to run updates but it would not take any update OTA even though there were two, NCG was the current room.
I flashed the ni2 via odin.
Now on the screen, instead of Mode: Developer, it says Qualcomm Secureboot.
I am not sure if I relocked the bootloader, if it can be unlocked,
Or this just the need to go into a recovery and flash a different rom.
Did I relock the bootloader?
Click to expand...
Click to collapse
I believe you have. But first I need to ask you 1) were you rooted and 2) did you have a custom recovery (TWRP) on your phone before you ODIN'd NI2? If you had TWRP on your phone before ODIN can you get into TWRP recovery now? Just an FYI, Samsung does not send out, in any form (OTA or otherwise) updates to the Developer Edition phones. The explanation for why they don't is long and no one except for Samsung knows for sure and they are not commenting on the issue. Dev owners keep their phones up to date by flashing custom ROMs released by our Dev community for retail and dev edition phones.

hill180 said:
Did I relock the bootloader?
Click to expand...
Click to collapse
When you flashed the stock tar you locked the bootloader and unfortunately you will need to contact Samsung and explain what you did. Most likely you will need to send the phone in so they can unlock it again. Contact them first.

Misterxtc said:
When you flashed the stock tar you locked the bootloader and unfortunately you will need to contact Samsung and explain what you did. Most likely you will need to send the phone in so they can unlock it again. Contact them first.
Click to expand...
Click to collapse
I think you're right Misterxtc, unfortunately all Samsung is going to do is return him a retail version of the S5. According to 3 other Dev owners that locked their bootloaders all Samsung would do is return their phones to working order, but no unlocked bootloader.

jpcalhoun said:
I think you're right Misterxtc, unfortunately all Samsung is going to do is return him a retail version of the S5. According to 3 other Dev owners that locked their bootloaders all Samsung would do is return their phones to working order, but no unlocked bootloader.
Click to expand...
Click to collapse
That doesn't sound too promising. They really need to change their policy on that.

im not sure why you would have flashed a ne9 tar when instructions clearly say NOT to flash odin tars on a dev edition s5 because it will lock the bootloader
Sent from my SM-G900V using XDA Free mobile app

Thank you all.
Yes the phone has been locked. Obviously I blame myself for not researching and just assuming.
If there is a silver lining, it appears my phone has a bad microphone, when I called, Samsung wanted to do an warranty exchange. I told them it was a new item less than 5 days, so I am just going to return.
Still debating if I should wait a few month and get the S5 locked from VZW as I am not seeing a lot of dev (although it makes it easier to root), or if I should get another model of phone all together, or reorder the S5 Dev Edition.

hill180 said:
Thank you all.
Yes the phone has been locked. Obviously I blame myself for not researching and just assuming.
If there is a silver lining, it appears my phone has a bad microphone, when I called, Samsung wanted to do an warranty exchange. I told them it was a new item less than 5 days, so I am just going to return.
Still debating if I should wait a few month and get the S5 locked from VZW as I am not seeing a lot of dev (although it makes it easier to root), or if I should get another model of phone all together, or reorder the S5 Dev Edition.
Click to expand...
Click to collapse
I hope Samsung does right by you. Just my opinion, but I think the Developer Edition S5 is the best phone on the market right now. The only other phone, that I know of, that allows the user the flexibility and performance of a unlocked bootloader phone is the HTC M8. The M8 is a good phone no doubt, but I like the S5 better. True, there aren't that many ROMs rilght now, but more and more get added as time goes by. The ROMs that are available are good, staple ROMs and range anywhere from super customization available to the user to lean, debloated super fast with great battery life...and a couple in between. Your choice, but if Samsung will replace your Dev Edition with a new Dev Edition...I think that is your best bet right now. But that is just my opinion. Good luck.

jpcalhoun said:
I hope Samsung does right by you. Just my opinion, but I think the Developer Edition S5 is the best phone on the market right now. The only other phone, that I know of, that allows the user the flexibility and performance of a unlocked bootloader phone is the HTC M8. The M8 is a good phone no doubt, but I like the S5 better. True, there aren't that many ROMs rilght now, but more and more get added as time goes by. The ROMs that are available are good, staple ROMs and range anywhere from super customization available to the user to lean, debloated super fast with great battery life...and a couple in between. Your choice, but if Samsung will replace your Dev Edition with a new Dev Edition...I think that is your best bet right now. But that is just my opinion. Good luck.
Click to expand...
Click to collapse
Thanks, Samsung is def returning the Dev phone without a 15% restock (have rma). Not because of the locking, but because of the mic. I think you are correct.
I had to go to my standby which is the dev Moto X. Love this phone, but the photos are bad, and it is slow. When I confirm the credit has been giving for the Dev phone, I will reorder the Dev edition. This time I will have to figure out a way to make a backup for resell, and flash only using TWRP.

hill180 said:
Thanks, Samsung is def returning the Dev phone without a 15% restock (have rma). Not because of the locking, but because of the mic. I think you are correct.
I had to go to my standby which is the dev Moto X. Love this phone, but the photos are bad, and it is slow. When I confirm the credit has been giving for the Dev phone, I will reorder the Dev edition. This time I will have to figure out a way to make a backup for resell, and flash only using TWRP.
Click to expand...
Click to collapse
I've always been a Moto fan myself, but although they still make good phones, they're not great phones (camera, display etc). I just post a "Do's and Don'ts" for Dev owners. Give it a read and let me know if I should add something to the thread. I've seen six users brick their Dev S5s in the past couple of weeks, hopefully the thread will help the next guy from making a mistake: http://forum.xda-developers.com/verizon-galaxy-s5/general/developer-edition-s5-dos-donts-t2895563

jpcalhoun said:
I've always been a Moto fan myself, but although they still make good phones, they're not great phones (camera, display etc). I just post a "Do's and Don'ts" for Dev owners. Give it a read and let me know if I should add something to the thread. I've seen six users brick their Dev S5s in the past couple of weeks, hopefully the thread will help the next guy from making a mistake: http://forum.xda-developers.com/verizon-galaxy-s5/general/developer-edition-s5-dos-donts-t2895563
Click to expand...
Click to collapse
great read. (I my case I would have still been returning my phone, but the next S5 will be safe )
The only add, if even possible. It is possible to backup the stock recovery before installing TWRP. So when it is time to sell, you can return the TWRP original backup and flash the original stock recovery?

hill180 said:
great read. (I my case I would have still been returning my phone, but the next S5 will be safe )
The only add, if even possible. It is possible to backup the stock recovery before installing TWRP. So when it is time to sell, you can return the TWRP original backup and flash the original stock recovery?
Click to expand...
Click to collapse
That's a great question and one that I have been trying to figure how to do. I am not sure about this, but in order to backup a stock recovery you would have to use ADB and do a total backup of the phone that way. I have never tried that and I don't know for sure if it will even work using ADB. Here is how I look at it...who would want to pay $550 (or less) for a Developer Edition phone and never replace the stock recovery with a custom recovery? It doesn't make sense. In fact, the only way you can tell that a Developer Edition phone has not been inadvertently "locked" (not trying to stick a finger in your eye here) is to ask/see if a custom recovery is installed. If not, then there is no guarantee to the buyer that the bootloader is truly unlocked. SafeStrap does not count!

CM11 Rom/Verizon S5/Not Booting

Hello everyone, I tried searching the forum for a solution but have not found any. I'm in a little predicament and I need some help!
Summary: I recently rooted my Verizon S5 using Towelroot and have safestrap installed. I am trying to install CM11 Rom and so far it hasn't been working for me. Everyone I boot up the rom for the first time I get the Samsung S5 boot screen and it is just black. Vibrates twice, and then loops back to the samsung boot screen.
Phone: Verizon Samsung S5 (G900V)
Android Version: 4.4.4
Baseband: ANI2, Kernel 3.4.0
Rooted with Towelroot, with safestrap 3.75 installed for verizon.
So far this is the procedure I have tried to install CM11:
1. Boot into recovery via safestrap.
2. Activate my ROM SLOT that I have created for custom ROM's.
3. Do a wipe (Cache, Data, Dalvik) and I have also tried wiping System also prior to installing CM11.
4. Flashing CM11 (downloaded from this thread: http://forum.xda-developers.com/gal...t/rom-cyanogenmod-11-0-android-4-4-4-t2864288) via buildbot mirror. I downloaded the latest release named: cm-11-20141104-UNOFFICIAL-kltevzw
5. After, flashing GAPPS also downloaded from the thread above for CM11.
6. They both successfully flash and I reboot the phone. (And yes I have tried wiping after flashing these two and rebooting but it still doesn't work)
7. The phone reboots, I see the Samsung S5 boot screen, then the splash screen for Safestrap, and then the screen goes black. The phone vibrates twice and then loops back to the Samsung S5 boot screen.
Does anyone know how to fix this? Thank you so much!

If your phone isn't a Dev Edition it will not work. CM Roms use AOSP and you can't run those or custom kernels on a retail edition phone.
Sent from my SM-G900V using XDA Free mobile app

Xaede said:
Hello everyone, I tried searching the forum for a solution but have not found any. I'm in a little predicament and I need some help!
Summary: I recently rooted my Verizon S5 using Towelroot and have safestrap installed. I am trying to install CM11 Rom and so far it hasn't been working for me. Everyone I boot up the rom for the first time I get the Samsung S5 boot screen and it is just black. Vibrates twice, and then loops back to the samsung boot screen.
Phone: Verizon Samsung S5 (G900V)
Android Version: 4.4.4
Baseband: ANI2, Kernel 3.4.0
Rooted with Towelroot, with safestrap 3.75 installed for verizon.
So far this is the procedure I have tried to install CM11:
1. Boot into recovery via safestrap.
2. Activate my ROM SLOT that I have created for custom ROM's.
3. Do a wipe (Cache, Data, Dalvik) and I have also tried wiping System also prior to installing CM11.
4. Flashing CM11 (downloaded from this thread: http://forum.xda-developers.com/gal...t/rom-cyanogenmod-11-0-android-4-4-4-t2864288) via buildbot mirror. I downloaded the latest release named: cm-11-20141104-UNOFFICIAL-kltevzw
5. After, flashing GAPPS also downloaded from the thread above for CM11.
6. They both successfully flash and I reboot the phone. (And yes I have tried wiping after flashing these two and rebooting but it still doesn't work)
7. The phone reboots, I see the Samsung S5 boot screen, then the splash screen for Safestrap, and then the screen goes black. The phone vibrates twice and then loops back to the Samsung S5 boot screen.
Does anyone know how to fix this? Thank you so much!
Click to expand...
Click to collapse
Since you're using SafeStrap, I'm assuming you have a retail edition Verizon S5 (non-developer edition).
1. Retail cannot use CM ROMs. Ever.
2. Safestrap does not flash any partitions other than cache, data, and system. Meaning even if you had a DevEd with safestrap, it would never flash a kernel.

BigBot96 said:
Since you're using SafeStrap, I'm assuming you have a retail edition Verizon S5 (non-developer edition).
1. Retail cannot use CM ROMs. Ever.
2. Safestrap does not flash any partitions other than cache, data, and system. Meaning even if you had a DevEd with safestrap, it would never flash a kernel.
Click to expand...
Click to collapse
Thank you for the quick replies, and also for clarifying. So would it be possible to run a custom ROM on a retail edition phone? What possibilities are possible (in terms of customization, root options, etc) for a retail edition phone?
Do XPOSED Framework Modules on retail verizon versions?

Xaede said:
Thank you for the quick replies, and also for clarifying. So would it be possible to run a custom ROM on a retail edition phone? What possibilities are possible (in terms of customization, root options, etc) for a retail edition phone?
Do XPOSED Framework Modules on retail verizon versions?
Click to expand...
Click to collapse
Any of the ROMs located in the Verizon Galaxy S 5 Android Development subforum as long as it states compatible with retail edition.

BigBot96 said:
Any of the ROMs located in the Verizon Galaxy S 5 Android Development subforum as long as it states compatible with retail edition.
Click to expand...
Click to collapse
And in terms of customization?

Xaede said:
And in terms of customization?
Click to expand...
Click to collapse
That's up to you depending on what you're looking for. The most customizable, tough, is Alliance. Each ROM offers the devs own take on "custom rom". Just gotta find one you want to use.

BigBot96 said:
That's up to you depending on what you're looking for. The most customizable, tough, is Alliance. Each ROM offers the devs own take on "custom rom". Just gotta find one you want to use.
Click to expand...
Click to collapse
Thank you alot BigBot!

Xaede said:
Thank you alot BigBot!
Click to expand...
Click to collapse
Yo, only problem is that they just dropped support for the S5 in favor of the N6 I really thought there was hope for the work on the bootloader or even the N12 build update Really gonna miss that Rom

kemerystudios said:
Yo, only problem is that they just dropped support for the S5 in favor of the N6 I really thought there was hope for the work on the bootloader or even the N12 build update Really gonna miss that Rom
Click to expand...
Click to collapse
you can thank vzw/samsung for locking the BL down so good for that lol

elliwigy said:
you can thank vzw/samsung for locking the BL down so good for that lol
Click to expand...
Click to collapse
Yep, locked bootloaders SUCK!!! Samsung and Big Red can lick my...
Ummm... Popsicle! Almost forgot this is a family friendly environment.

elliwigy said:
you can thank vzw/samsung for locking the BL down so good for that lol
Click to expand...
Click to collapse
Good News though! Beans may pass permission down to Goldie and others so that progress can continue! Im all in for that, and my friend and I have been "experimenting" with a couple theories that may help future phones, boot loaders and other stuff.. So yeah, happy Modding!
---------- Post added at 03:08 AM ---------- Previous post was at 03:03 AM ----------
ludeawakening said:
Yep, locked bootloaders SUCK!!! Samsung and Big Red can lick my...
Ummm... Popsicle! Almost forgot this is a family friendly environment.
Click to expand...
Click to collapse
Hey, I blame Samsung for Knox amd other bloat/crap, but in honesty they are a company that makes these phones for crowds that buy them for the crap they put on them. BIG RED the world fattest *****iest carrier (excuse the language) makes me extremely... Angry... For lack of other words... They are CDMA, bootlock their phones, slow updates down, and charge a ****ton for it! They are bad. Just bad. Fix that crap Verizon, just fix it. No more begging for you to stop torturing me, I swear another slip up and I quit! TMobile here I come, also Ludeawaking, I hope you get the rights from beans and good luck, and Elliwigily (sorry i forgot how to spell you name :| ) great debloat, still is a great daily driver! Happy Modding!

soft bricked my phone

I have a verizon note 3 I ordered from insurance when my last note 3 finally bit the dust. My previous phone was running jasmine and stock using safestrap. I strove to do the samewith this phone. Instead, when attempting to use towelroot, it said my phone was no longer supported. I tried to find a viable nc2 and couldn't for the last week. Most links on this website are dead because note 3 is hardly supported anymore. I finally found one, one developed by hrsbad or one someone claimed was, the custom note 3 nc2. When I flashed it using odin, i get an error that pops up with Samsung splash screen, "kernel is not seaandroid enforcing" It then takes me to a yellow exlaimation point with "system software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest verizon wireless store for help. Is there anything i can do? Im sure there's a wiz out there who knows an easier solution.
I would appreciate your help very greatly, and if you could explain to me why i couldnt; use safestrap and even suggest how i could root an alternate way that would be super amazing. Thanks for any help you might be able to lend.

I have attemtped to flash all the nc2 and nc4 finally succeeding with one that had previously failed. The kernel error no longer appears and my phone is behaving normally. I have 4.4.4 and would like to root it, are there any options anyone knows of? Towelroot does not support my version, Im open to any suggestions. Thanks in advance.

try one of these imgs http://forum.xda-developers.com/showthread.php?t=2524572

vzwnexus said:
try one of these imgs http://forum.xda-developers.com/showthread.php?t=2524572
Click to expand...
Click to collapse
EDIT: Thanks for your reply again, but I was wrong. I didn't try any of these because all the links I'd be interested in are no longer being served. Is there anywhere else I can get this at, or anything else I can do. Thank you again I really appreciate it.
thanks for your reply. did try the nc2 in AP spot of odin and it bricked my phone temporarily. Did I use the wrong one? or should I have used multiples of those to do it properly?

do you remember what firmware you were running before going full root? you'll want to get that img to flash. maybe nc4?

vzwnexus said:
do you remember what firmware you were running before going full root? you'll want to get that img to flash. maybe nc4?
Click to expand...
Click to collapse
I have put nc4 back on. This is how the phone was shipped. But I was unable to root with towelroot, I am still without root. And that is the crux ofmy questions now, is where can I get nc2 so I can use towelroot, or is there a better method than that?

what I have tried
nc2kernel.tar.md5
VZW-N900VVRUCNC4-20140512165349
n900v_kk_firmware.tar.md5
It has been very difficult finding these files online, sammobile is where I got one of them, the other two were from a hsrbad post, a comment from "Dutchboy" who still hosted these files lead me to them.

it's hard to say if those work, what I'm trying to determine is the original firmware your phone was running before all of this. I'm not super good at this just fyi.. haha. i usually look for the modem and firmware for the "original" firmware from before rooting.

vzwnexus said:
it's hard to say if those work, what I'm trying to determine is the original firmware your phone was running before all of this. I'm not super good at this just fyi.. haha. i usually look for the modem and firmware for the "original" firmware from before rooting.
Click to expand...
Click to collapse
Sorry for the late response. School and work are kicking my butt. The original is hard to say, I attempted like five different roms after noticing that mine could not be towelrooted. all of these romsfailed, and one finally raised an exception with the security that temporarily soft bricked my phone, I found a nc4 on sammbile that was able to remedy that, but I'd like most of all to get this rooted and safestrapped again so i can dualboot as i had previously. I'm also pretty novice but i enjoy the attempting to do this stuff, even when it ends in me bricking my phone for the day :good:

so have you been able to get your phone running?

deindichter said:
Sorry for the late response. School and work are kicking my butt. The original is hard to say, I attempted like five different roms after noticing that mine could not be towelrooted. all of these romsfailed, and one finally raised an exception with the security that temporarily soft bricked my phone, I found a nc4 on sammbile that was able to remedy that, but I'd like most of all to get this rooted and safestrapped again so i can dualboot as i had previously. I'm also pretty novice but i enjoy the attempting to do this stuff, even when it ends in me bricking my phone for the day :good:
Click to expand...
Click to collapse
Towelroot was supposed to work on NC4.
You can not flash any ROM lower than NC4 due to bootloader. There is also supposedly a rooted NC4 here that you can flash...but towelroot should work.
Sent from my Note 3 via Tapatalk

donc113 said:
Towelroot was supposed to work on NC4.
You can not flash any ROM lower than NC4 due to bootloader. There is also supposedly a rooted NC4 here that you can flash...but towelroot should work.
Sent from my Note 3 via Tapatalk
Click to expand...
Click to collapse
Thank you both for your replies.
Towelroot had previously worked , this is an insurance replacement as mine bit the dust. I went to towelroot and to my great sadness does not work. I am using:
4.4.4
sm-n900v
n900vvrudnj6
kernel 3.4.0
Truly I'm novice so Im not positive if any of this can help or not, but do you know of a way I can towelroot?

deindichter said:
Thank you both for your replies.
Towelroot had previously worked , this is an insurance replacement as mine bit the dust. I went to towelroot and to my great sadness does not work. I am using:
4.4.4
sm-n900v
n900vvrudnj6
kernel 3.4.0
Truly I'm novice so Im not positive if any of this can help or not, but do you know of a way I can towelroot?
Click to expand...
Click to collapse
Nothing works on 4.4.4 or higher....sorry
Sent from my Note 3 via Tapatalk

thank you.

My phone is rebricked, does anyone know where you can get files to revert back to stock?

They're all here...... well most of then back to 4.3
sammobile.com/firmwares/database/SM-N900V/