Database Users

Safestrap roms

Now that the OTA has locked everyone up or those of us that got a device that didn't have the chance to unlock the bootloader, do most/some/all/etc roms that we have for the Razr M work with Safestrap?
Sorry if this is posted elsewhere but I didn't see it and only saw mention of roms having to be compatible with it

collins521 said:
Now that the OTA has locked everyone up or those of us that got a device that didn't have the chance to unlock the bootloader, do most/some/all/etc roms that we have for the Razr M work with Safestrap?
Sorry if this is posted elsewhere but I didn't see it and only saw mention of roms having to be compatible with it
Click to expand...
Click to collapse
I don't know the exact roms, but I know there are a few. Since the bootloader was unlocked though, the development for safestrap roms has slowed or stopped. Check in the Android Development section and scroll through for the safestrap roms. I believe they were 4.1.2 roms only, but don't quote me on that.
Sent from my Droid Razr M using xda app-developers app

Jersey846 said:
I don't know the exact roms, but I know there are a few. Since the bootloader was unlocked though, the development for safestrap roms has slowed or stopped. Check in the Android Development section and scroll through for the safestrap roms. I believe they were 4.1.2 roms only, but don't quote me on that.
Sent from my Droid Razr M using xda app-developers app
Click to expand...
Click to collapse
ROMs developed for SS stopped at 4.1.1, meaning that there not any 4.1.2 custom ROMs available. bootloader was unlocked prior to 4.1.2 rolling out.
there might be a way to convert them to SS though - I know that a dev was able to convert a SS ROM to TWRP flashable recovery, so perhaps he might be able to do the reverse.

jco23 said:
ROMs developed for SS stopped at 4.1.1, meaning that there not any 4.1.2 custom ROMs available. bootloader was unlocked prior to 4.1.2 rolling out.
there might be a way to convert them to SS though - I know that a dev was able to convert a SS ROM to TWRP flashable recovery, so perhaps he might be able to do the reverse.
Click to expand...
Click to collapse
I believe DeadCalm was updated to 4.1.2. Also, Eclipse v1.2 is still SS compatible but it leans more heavily on AOSP styling.
SS compatible ROMs:
-Early builds of CM10 (way early, like at the beginning of thread early)
-DeadCalm was SS enabled, not sure if it was modified for an unlocked bootloader only
-Energy is SS enabled and never altered for unlocked bootloader
-Flying Jelly was SS enabled and I don't think it was modified to work only on an unlock bootloader
-Eclipse v1.2 was SS enabled, I don't think it was modified for unlocked bootloader

RikRong said:
I believe DeadCalm was updated to 4.1.2. Also, Eclipse v1.2 is still SS compatible but it leans more heavily on AOSP styling.
SS compatible ROMs:
-Early builds of CM10 (way early, like at the beginning of thread early)
-DeadCalm was SS enabled, not sure if it was modified for an unlocked bootloader only
-Energy is SS enabled and never altered for unlocked bootloader
-Flying Jelly was SS enabled and I don't think it was modified to work only on an unlock bootloader
-Eclipse v1.2 was SS enabled, I don't think it was modified for unlocked bootloader
Click to expand...
Click to collapse
yeah, but those are all 4.1.1 ROMs - and I'm fairly certain deadcalm is unlocked bootloader only, as it was created for just 4.1.2.
but I really don't think it matters much anymore - Motorola has been quite diligent on providing updates, so I would not be surprised to see an official 4.2.2 release by the end of this year, with a 4.3 release by next summer.

jco23 said:
yeah, but those are all 4.1.1 ROMs - and I'm fairly certain deadcalm is unlocked bootloader only, as it was created for just 4.1.2.
but I really don't think it matters much anymore - Motorola has been quite diligent on providing updates, so I would not be surprised to see an official 4.2.2 release by the end of this year, with a 4.3 release by next summer.
Click to expand...
Click to collapse
Yeah, you're right on all those being 4.1.1, but I was just throwing out some options. Personally, I think very few of the devs, if any, will develop for SS. Sure, the people that are getting new phones or maintenance replacements are hosed. However, people that owned the phone and decided to install the update and not unlock their bootloader? Well, it's their own fault. They've been warned for 4 months that the patch could be locked. Look what happened, it was locked. The one thing the devs could do, that would be fairly easy, is just update the older SS ROMs to the newer OTA. That would help out a lot of people.

RikRong said:
Yeah, you're right on all those being 4.1.1, but I was just throwing out some options. Personally, I think very few of the devs, if any, will develop for SS. Sure, the people that are getting new phones or maintenance replacements are hosed. However, people that owned the phone and decided to install the update and not unlock their bootloader? Well, it's their own fault. They've been warned for 4 months that the patch could be locked. Look what happened, it was locked. The one thing the devs could do, that would be fairly easy, is just update the older SS ROMs to the newer OTA. That would help out a lot of people.
Click to expand...
Click to collapse
100% agreed on the warnings - but I also understand why folks may have been skittish beforehand (took me 3 months of reading before I rooted my first device). given that this phone is now offered for free, I can see many new folks to this community, but they'll be SOL unless we are blessed with the help from a dev to unlock their bootloader.
that being said, the devs are not required to create a hack or make their ROMs SS-compatible, but I would not be surprised if locked bootloader phones soon begin to outnumber the locked one. i'm just thankful that they are here.

To be fair, the droid razr m that I'm working on has its bootloader locked because my girlfriend is skittish about me touching her phone. Women

I could barely even get any to work when they were still developing SS Roms, so goodluck... Never accept OTA's...

AK47sForAll said:
I could barely even get any to work when they were still developing SS Roms, so goodluck... Never accept OTA's...
Click to expand...
Click to collapse
Unfortunately the one I have had the OTA already downloaded so I didn't even get a chance to unlock the bootloader...been trying to find a white one at a reasonable price and haven't' had much luck

collins521 said:
Unfortunately the one I have had the OTA already downloaded so I didn't even get a chance to unlock the bootloader...been trying to find a white one at a reasonable price and haven't' had much luck
Click to expand...
Click to collapse
What do you consider reasonable? And have you tried eBay?

AK47sForAll said:
What do you consider reasonable? And have you tried eBay?
Click to expand...
Click to collapse
Ya I've been watching eBay and other sites for a good deal on a white one. Under $200 and in great shape is where I'm looking to get one. I'm in no real rush so I can wait for a deal to pop up

http://www.droidrzr.com/index.php/t...calm-v14-7172013-412-base/page-30#entry333531
That being said.
An activated DC is a path to this & you take your data with you.
http://forum.xda-developers.com/showthread.php?t=2246081
Edit Yet this is a backup made by the full twrp. Yet again they are supposed to be compatible....

Jcase's "SlapMyMoto" "Now what" Q and A thread. By dtrud0h.

This post is to try to sort out the questions, concerns and troubles that users come up against when using.the "SlapMyMoto" rooting method to gain "Root" on the Moto X.
[Question]What happened to my "Recovery"--
[ANSWER]- It's gone. There's no "Recovery". Now you have read/write access to /system instead of a recovery. Your system will boot normally, except /system will be read-write accessible.
[Question ] - Can I flash Xxx-xxx.zip through recovery like it says here - xxxxxx.com/yada/yada/instructions (with link to. Zip file) .com
[Answer] No.
[Question ] Why not?
[Answer] Because you have a "Custom" Recovery that does nothing more than provide read-write access. to the /system partition , ..period.
[Question] -- Can I use some other"Recovery"?
[Answer ] -- ? DUNNO? Maybe jcase will chime in and clarify that. As it stands, maybe the 4.4 recovery, don't know for sure what it will do to your root. Whether it is the 4.4, or 4.2 recovery, without unlocking your Boot loader it will have to be a signed. zip file for system security.
Where else can I turn for answers?
Hopefully, here: http://forum.xda-developers.com/showthread.php?t=2538896
SlapMyMoto 0.5c Beta (4.4 root, RW to system)
As it stands, jcase is attending to family/personal matters. I'm sure he will be back sometime. Until then, just have to wait it out.
Sent from my XT1055 using Xparent Cyan Tapatalk 2

Question- Why with a locked bootloader do I need recovery?
Answer- You don't!
Comment- Good, because you don't have one now that you used SlapMyMoto to root. Your recovery has been replaced by write protection off.

lowvolt1 said:
Question- Why with a locked bootloader do I need recovery?
Answer- You don't!
Comment- Good, because you don't have one now that you used SlapMyMoto to root. Your recovery has been replaced by write protection off.
Click to expand...
Click to collapse
Unless you want to clear cache, flash a signed update.zip you really don't need it. Until you do.
Sent from my XT1055 using Xparent Cyan Tapatalk 2

dtrud0h said:
Unless you want to clear cache, flash a signed update.zip you really don't need it. Until you do.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Or I could just use adb
via my slapped KIT KAT moto X rockin on Verizon

Yup, you sure could. What I'm trying to get across to the masses is, its not all about you lowvolt1, there are many new, or people that don't known their way around all this that read the "How-to" from xyz.com and expect it to work.
If you can read, apply your good judgement, and move on then great.
There are other people that can't yet wrap their heads around the bootloader/recovery thing that just got a phone, have no clue, and want help or answers. This is the thread for them.
Maybe you should start a thread for stuff that's all about you if that's what you want.
Sent from my XT1055 using Xparent Cyan Tapatalk 2

dtrud0h said:
Yup, you sure could. What I'm trying to get across to the masses is, its not all about you lowvolt1, there are many new, or people that don't known their way around all this that read the "How-to" from xyz.com and expect it to work.
If you can read, apply your good judgement, and move on then great.
There are other people that can't yet wrap their heads around the bootloader/recovery thing that just got a phone, have no clue, and want help or answers. This is the thread for them.
Maybe you should start a thread for stuff that's all about you if that's what you want.
Sent from my XT1055 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
My narcissistic nature is not in question here. What is in question is why you are trying to help new people or people with questions, yet you continue to blurt out false truths.
Maybe you should listen to the people that have alot more knowledge than you and I put together and do a little more research before you continue to confuse people.
via my slapped KIT KAT moto X rockin on Verizon

lowvolt1 said:
My narcissistic nature is not in question here. What is in question is why you are trying to help new people or people with questions, yet you continue to blurt out false truths.
Maybe you should listen to the people that have alot more knowledge than you and I put together and do a little more research before you continue to confuse people.
via my slapped KIT KAT moto X rockin on Verizon
Click to expand...
Click to collapse
OK I for one found your (original) explanation quite helpful as I didn't pick up on the recovery/bootloader thing. I'm still not rooted...
The recovery I can live without - I think you've explained it well.
What happens to the bootloader? it looks like (in step "5") it is downgraded to the 4.2.2 bootloader? So we're running 4.4 with a 4.2.2. bootloader when all said and done?

tdiman said:
OK I for one found your (original) explanation quite helpful as I didn't pick up on the recovery/bootloader thing. I'm still not rooted...
The recovery I can live without - I think you've explained it well.
What happens to the bootloader? it looks like (in step "5") it is downgraded to the 4.2.2 bootloader? So we're running 4.4 with a 4.2.2. bootloader when all said and done?
Click to expand...
Click to collapse
Yes. As I understand it your statement is correct.
via my slapped KIT KAT moto X rockin on Verizon

Guys-
I don't feel like going through all 80+ pages on the slapmymoto thread, so I will ask it here.
I have the at&t version with 4.4 on it. Can I root at the moment with the 0.5 slapmymoto, if not, is 1.0 going to be solving this issue?
Thanks in advance-

Dodolom said:
Guys-
I don't feel like going through all 80+ pages on the slapmymoto thread, so I will ask it here.
I have the at&t version with 4.4 on it. Can I root at the moment with the 0.5 slapmymoto, if not, is 1.0 going to be solving this issue?
Thanks in advance-
Click to expand...
Click to collapse
I am assuming your on the non Dev edition. I am not familiar with at&t, so I will ask this. Can you unlock the boot loader on that version? If not then yes I believe you can root using slap. But you have to downgrade to 4.2.2 first.
via my slapped KIT KAT moto X rockin on Verizon

lowvolt1 said:
I am assuming your on the non Dev edition. I am not familiar with at&t, so I will ask this. Can you unlock the boot loader on that version? If not then yes I believe you can root using slap. But you have to downgrade to 4.2.2 first.
via my slapped KIT KAT moto X rockin on Verizon
Click to expand...
Click to collapse
Yeah, this is jus the retail at&t version on the Cyber Monday sale. I had the GSM DE from day 1 but sent it to a friend in england to play with and then Cyber Monday deal popped up, so I ordered one but this time I went with the custom design which only comes with the carriers.
Anyways, how can I know if I can unlock the bootloader or not?

Dodolom said:
Yeah, this is jus the retail at&t version on the Cyber Monday sale. I had the GSM DE from day 1 but sent it to a friend in england to play with and then Cyber Monday deal popped up, so I ordered one but this time I went with the custom design which only comes with the carriers.
Anyways, how can I know if I can unlock the bootloader or not?
Click to expand...
Click to collapse
Try Google searching it. I don't think you can. Verizon can't and since you made mention of a Dev edition I am guessing you can't unlock.
via my slapped KIT KAT moto X rockin on Verizon

lowvolt1 said:
Try Google searching it. I don't think you can. Verizon can't and since you made mention of a Dev edition I am guessing you can't unlock.
via my slapped KIT KAT moto X rockin on Verizon
Click to expand...
Click to collapse
I think I will wait for the 1.0 and see what happens or if I get some time this week, I will give it a shot with the downgrading and all that.
Thanks

Dodolom said:
I think I will wait for the 1.0 and see what happens or if I get some time this week, I will give it a shot with the downgrading and all that.
Thanks
Click to expand...
Click to collapse
You may be waiting awhile for 1.0. If it comes at all.
via my slapped KIT KAT moto X rockin on Verizon

I just recieved a Moto X on Verizon in the mail and I really would like to root it to debloat and run a custom rom but I have always had Samsung and worked with odin. How do we go about rooting this? What do you think is the easiest way? For some reason ADB isnt working on my computer. Thanks in advance! I REALLY NEED SOME HELP!!

ehusidic said:
I just recieved a Moto X on Verizon in the mail and I really would like to root it to debloat and run a custom rom but I have always had Samsung and worked with odin. How do we go about rooting this? What do you think is the easiest way? For some reason ADB isnt working on my computer. Thanks in advance! I REALLY NEED SOME HELP!!
Click to expand...
Click to collapse
1. There are no custom roms at the moment. Unless you have the Verizon Dev edition.
2. You will only gain root access and RW permissions
3. The easiest way is slap my motto is the only way if you want to be rooted on kit Kat 4.4
4. You will definitely need adb
Sent from my GT-P3110 using Tapatalk 4

[Q] Say if you boot into "recovery," otherwise write protection-off mode, then you reboot. Do you boot back into normal mode? Or does it default into write protection-off mode until you explicitly tell it to boot normally?

erikikaz said:
[Q] Say if you boot into "recovery," otherwise write protection-off mode, then you reboot. Do you boot back into normal mode? Or does it default into write protection-off mode until you explicitly tell it to boot normally?
Click to expand...
Click to collapse
That depends, are you rebooting in to recovery again, or rebooting in to Android? Android = WP on. Recovery = WP off.

A couple of non-SlapMyMoto questions have been asked here so... (dtrud0h, feel free to add these to your OP)
[Q] What is the best way to root my Moto X?
[A] Depends what Rom is on your X. Generally there are 3 "stock" motorola rom versions for the X. The ROM it shipped with (android 4.2.2), the "camera fix" update (4.2.2), and Kit Kit (4.4). And it depends on if you have a locked bootloader or not.
Locked Bootloader with KitKat (4.4) see SlapMyMoto -> SlapMyMoto 0.5c Beta (4.4 root, RW to system)
Locked Bootloader with "Camera Update" see -> [Root] RockMyMoto (Yes, even the first OTA)
Locked Bootloader with initial shipping rom see -> [Root/Write Protection Bypass] MotoX (no unlock needed)
UNLOCKED bootloader see -> https://plus.google.com/110773150384694258853/posts/VhtJtg92sTP
NOTE: these should work across all carrier variants of the Moto X. that means ATT, VZW, TMO, TIM, Rogers, etc.. should be able to use these. You just need to pick the right process based on your ROM or locked vs unlocked bootloader.
[Q] Once I root, can I accept an OTA update on my phone?
[A] If you have rooted with SlapMyMoto, RockMyMoto, PwnMyMoto, or have otherwise replaced stock recovery, then please do not let your phone try to install any OTA updates!!!
As stated in another Question/Answer, using JCASE's SlapMyMoto, RockMyMoto and PwnMyMoto to root will replace your recovery to allow for the ability to boot with R/W permitted. When the OTA update downloads to your phone, and it tries to reboot to install it, the phone/update is trying to use the stock recovery to install the update. Since it is not there, the update will fail and the phone will reboot and it will likely try to reboot and try to install again. This can often result in the phone being stuck in a boot loop of continually retrying to reboot and install the update. There are ways to fix this posted in other threads. NOTE: there may be ways to get around this and install the OTA zip but that is a topic for another thread.
If you have an unlocked bootloader and have installed a custom recovery, it might be possible to install the OTA ZIP manually, but again that is a topic for another thread.
[Q] Can I unlock the Bootloader on my Moto X? or How do I know if I can unlock my bootloader or not?
[A] If you have a Developer Edition Moto X, yes you can unlock the bootloader and it doesn't void your device warranty. If you have a MotoMaker or Carrier Branded model, it depends on IF your carrier allows Motorola to do it, and it will void your warranty. For example, Verizon and ATT does now allow Motorola to unlock your boot loader. T-Mobile users can unlock their bootloader but it will void their warranty.
To see if your Moto X bootloader can be unlocked visit -> https://motorola-global-portal.cust...e/bootloader/unlock-your-device-a/action/auth You can step through the process until you get to the final submit WITHOUT voiding your warranty. Based on the site's wording, once you hit the final submit to request the code, your warranty is voided (unless your phone is a developer edition)
[Q] How do I run a custom rom on my X?
[A] SlapMyMoto and the like is/are not a process to allow you to run custom roms.
Unless you have an unlocked bootloader, you can't remove the Stock Motorola ROM and run a completely custom rom. And because most X owners generally agree the stock X ROM is very good, there are not many custom roms available for the X, even for those with unlocked bootloaders. Any available custom roms are posted in -> http://forum.xda-developers.com/moto-x/development so please use those threads for info/discussions.
If you have locked bootloader, there are a few options for using Safestrap to allow for some customization or "alternate roms", but that is a topic which doesn't apply to this thread.

So what can we really do after we gain root. The obvious is run apps that require root but what else? I am a user and follow directions from devs on how to do things. So without the knowledge or experience of the deep pits of android what can I do with root? This root process looks a little tough but I could figure it out once I piece all the threads together to understand it better.
Sent from my vzw moto X
---------- Post added at 10:00 AM ---------- Previous post was at 09:54 AM ----------
Will this work on a non developer vzw phone?
http://forum.xda-developers.com/showthread.php?t=2521509
Sent from my vzw moto X

Flash ROM & some crazy nintendo graphics

Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!

Same issues apon using The Samsung Galaxy S4 for Verizon (jfltevzw) Build MK2 rooted using vRoot (English) and using safestrap. if needed I can upload the safestrap apk or version. If I install any type of AOSP ROM the boot logo is either missng or baby blue with wierd static lines. AOKP is the only AOSP ROM that eventually boots (with static boot logo) but no wireless works, and this is the same wether MK2 and/or MJ7 modules are installed or not. the only rom I can successfuly install and use daily that has no bootloader based issues is Hyperdrive ROM For jfltevzw & jflteatt. Any info would be much apreciated!
Sent from my SCH-I545 using xda app-developers app

^ Interesting. I didn't expect anyone else to have this issue. I never read about it before. I really feel like it has something to do with SafeStrap.

Heath Cliff said:
Hi guys, I'm wondering if anyone can shed some light on a few things for me.
I have an ATT SGH i-337 MK2 with SafeStrap 3.71
Today I tried to flash PAC ROM and Dirty Unicorn into ROM Slot-1, and upon reboot when the ROM's logo should appear the whole screen just looked like when a nintendo cartridge isn't working. It was just a few crazy colors with some blocks and lines here and there.
Then I tried AOKP with it's Loki'd Kernel being part of the ROM. The nintendo screen came back again, but then the AOKP logo popped up clear as day for a second. Then went back to the lines and colors.
So could this be a problem with Safestrap compatibility? If so, how can I uninstall it? (I did read the dev's thread, and it just says use .APK and IDK what that means)
Or could it be that I also need to use Loki Doki with the other two? (Didn't see anything about that in PAC or DU threads)
Thanks!
Click to expand...
Click to collapse
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.

REEEEEEAAAAADDDD!!!!
It's been very well documented that AOSP does not work with safestrap. Neither does loki. There currently is no way/fix to flash AOSP.
So
1. No AOSP or GPE
2. No loki
3. No flashing custom kernels
Sent from my GT-I9505 using Tapatalk

John The Rhino said:
If you would have read 1st, then you would know that you can NOT flash any non TW rom on MK2. This is stated over & over on XDA. Safestrap is NOT the problem it is a Godsend from Hashcode for us to be able to flash custom roms onto our locked boot loader devices. Please read before flashing, bricking & then bashing the developers. Follow the directions posted on how to restore your phone, or better yet make a trip to Best Buy & they'll do it for you. Good Luck.
Click to expand...
Click to collapse
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA

Heath Cliff said:
I did read first. I've been reading this forum for quite a while actually. But there is so much information it's hard to keep it all straight. This ATT stuff is a lot different then my VZW Razr was. That phone was just flash and forget. There are so many different ROM's for this phone now that are 4.3 or KitKat I guess I just didn't realize that, that Android version came with the ROM and was originally something more mod-able stock.
Any way I wasn't bashing SS or Hashcode. I clearly said "compatibility issue" i.e. some programs just don't play well together hence the existence of compatibility mode, virtual machines, and x86 processors. So maybe you should read before bashing novice community members and making yourself look like a big asshole.
And I don't need best buy to fix anything I have a NANDroid, backup on Kies3, and Google+. Besides, I did all of this flashing I on a separate partition so the stock ROM was never altered. Thanks for absolutely nothing at all.
For anyone else that feels like they can move on with me, I would really like to try to install TWRP in place of SS. I'd appreciate any help with how to go about doing that. TIA
Click to expand...
Click to collapse
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.

John The Rhino said:
Well stating Safestrap may have a compatibility issue is offensive to the developer, especially since you did not read the instructions or posts from other members who did as you. If you would follow the directions it's perfect. I have 4 different roms on my phone + stock to choose from! How cool is that? I understand the overwhelming urge to flash a rom, as I too have been flashing on my Skyrocket since the factory warranty expired last year, and flashing roms is a breeze on that device. However, this S4 is more complicated since the introduction of the KNOX & the LOCKED boot loader. These phones are expensive so unless you really want a $700.00 brick, read, read some more, then read it all again. Safestrap uses TWRP to flash the roms, but TWRP alone is not compatible with MK2 nor is CWM. If you want to flash roms on your ATT MK2 S4 Safestrap is the only way to do that at this writing.
Click to expand...
Click to collapse
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again

Heath Cliff said:
Okay, well thank you for that. I just see so many ATT S4's in here with other ROMs and Recoverys I thought I could get something to happen. Anyway, sorry for the poor thread and response. I appreciate the plain blunt fact that SS and the ROMs that work with it are my choices for now. And don't worry about me. The worst that I'd probably get is a soft brick and I've recovered from that before Thanks again
Click to expand...
Click to collapse
Hey man I totally understand. It's hard to watch all these other roms pop up for the original S4 & we can't flash them. But we no longer have to suffer with only the stock rom option since Hashcode's brilliant Safestrap was released. Once you get use to it, the ability of being able to multi-boot roms really kind of makes up for the locked boot loader. Soon though, we will have 4.4 Kit Kat & then we can start this process of getting off the stock rom all over again. Right? It could be worse, we could have I-phones. We do have a ever growing number of great custom TW based roms available to us here for our device. So try them, you'll be surprised how much better your phone performs. Glad I made sense & forgive my bluntness that's just how us Rhinos roll.

[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.

Double check before I root

I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!

burgertime78 said:
I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
Click to expand...
Click to collapse
You can't flash anything other than Touch Wiz Roms. That guide and ones like The Ultimate All in one Guide will be a starting place. No custom recoveries either.
Sent from my GT-I9505G using Tapatalk

rugmankc said:
You can't flash anything other than Touch Wiz Roms. That guide and ones like The Ultimate All in one Guide will be a starting place. No custom recoveries either.
Sent from my GT-I9505G using Tapatalk
Click to expand...
Click to collapse
So what's the problem? ATT? too new a hardware version? I have the worst luck with this stuff - if I buy a router to flash a custom firmware like Tomato, it's the ONLY version that isn't supported. crazy.
I'm not sure what a custom recovery is unfortunately. That said, can I root this phone at all? I guess if I can't flash the rom I want to use, can I at least install titanium and freeze all the crapware that I don't want running?
btw - thanks for the response.

burgertime78 said:
So what's the problem? ATT? too new a hardware version? I have the worst luck with this stuff - if I buy a router to flash a custom firmware like Tomato, it's the ONLY version that isn't supported. crazy.
I'm not sure what a custom recovery is unfortunately. That said, can I root this phone at all? I guess if I can't flash the rom I want to use, can I at least install titanium and freeze all the crapware that I don't want running?
btw - thanks for the response.
Click to expand...
Click to collapse
Any build after mdl has the bootloader locked down. If you read thru those two threads OP pages you get an idea. You will also need to get familiar with SafeStrap. I am on the old build and can use an exploit called loki-doki to bypass Sammy's security check and allow kernel to flash.
There may be some new stuff on rooting NC1, but I don't keep up. Basically you had to go back to mk2 to root then go back NC1 and use SafeStrap to flash only TW roms. The SafeStrap thread will explain that. But, it creates slots on the System partition again fooling Sammy. More or less--
Like I said not an expert as I don't have the issue you have with bootloader. But that is the gist of it. Just need to read up so you don't brick--good luck.

rugmankc said:
Any build after mdl has the bootloader locked down. If you read thru those two threads OP pages you get an idea. You will also need to get familiar with SafeStrap. I am on the old build and can use an exploit called loki-doki to bypass Sammy's security check and allow kernel to flash.
There may be some new stuff on rooting NC1, but I don't keep up. Basically you had to go back to mk2 to root then go back NC1 and use SafeStrap to flash only TW roms. The SafeStrap thread will explain that. But, it creates slots on the System partition again fooling Sammy. More or less--
Like I said not an expert as I don't have the issue you have with bootloader. But that is the gist of it. Just need to read up so you don't brick--good luck.
Click to expand...
Click to collapse
DAMN! Thanks!

burgertime78 said:
DAMN! Thanks!
Click to expand...
Click to collapse
Good Luck
There are plenty of folks here to help with specifics like jd and tedusa--:good:

burgertime78 said:
I just acquired a GS4 from ATT today. it is:
Android 4.4.2 (which I upgraded myself)
Baseband V: I337UCUFNC1
I found this thread http://forum.xda-developers.com/showthread.php?t=2663545 But I wanted to make sure there is not anything newer or different since then. I wasn't able to find anything else by searching. I'm trying to root this phone to use CyanogenMod. Unfortunately, my phone is not supported in their list of easy installs.
Can someone verify the steps for me to root and flash Cyan to this model phone before I pull the trigger? Thanks!
Click to expand...
Click to collapse
New way to root is call towelroot. Google it or search for it around here the link is everywhere. It's an apk file made by geohot (same guy that jail broke the iphone and ps3). Once you root you can install safestrap. If you've ever owned an droid device they have something identical called boot strap. Think of it as a dual boot of sorts. Definitely keep your eyes on these threads as well as the sgs5 thread. If an exploit is discovered it'll probably be for the s5 and will be compatible with our s4 (towel root was made for the s5 but works for a whole bunch of devices)
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

burgertime78 said:
DAMN! Thanks!
Click to expand...
Click to collapse
Link: http://forum.xda-developers.com/showpost.php?p=52167774&postcount=3&nocache=1&z=8413408249616623
I was in the same boat as you 2 weeks ago, bought a NC1 and wanted CM, and used this to root. I currently use the Google Edition ROM that has been modified to work on locked bootloader phones, though it does have it's fallbacks. For someone new I'd recommend GoldenEye, just click the link on my signature to download it.
Good luck!

Oh, btw--check out GEOHOT's Towelroot thread in General for NC1. I knew I forgot one. That was the recent method I was thinking of. Not sure which of threads are best for you--depends what you want to do.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
HaHa posted at same time.

You all are AWESOME! Thank you so much! I'll look into this and keep you posted.

rugmankc said:
Oh, btw--check out GEOHOT's Towelroot thread in General for NC1. I knew I forgot one. That was the recent method I was thinking of. Not sure which of threads are best for you--depends what you want to do.
---------- Post added at 10:38 PM ---------- Previous post was at 10:37 PM ----------
HaHa posted at same time.
Click to expand...
Click to collapse
I just towelrooted. It worked! I was watching this video http://gs5.wonderhowto.com/how-to/r...nt-even-at-t-verizon-20-seconds-flat-0155617/ and I did it while I Was watching the video. On my device, it did not even reboot - i just said "should be rooted" so I loaded a root checker and sure enough, it is rooted! took all of about 8 seconds.
Now, on to a rom.
I'm confused now. Why can I not use CM? I read about SafeStrap and I understand it's sort of a dual boot setup - I get that. So, in a sense, I'm not really installing FRESH, a new rom - at least not in the sense that you format your hard disk and install a new OS. However, what ARE my choices in roms? I know the whiz touch, and now the golden eye, plus the google modified - but what else? I want something cut down, simple and battery friendly. I'm not a super power user and I don't require much. Actually, battery life is the most important thing to me.
This is my business phone - I use Gmail, SMS, maybe take a few pictures - and I listen to podcasts. very basic user. Advice?

burgertime78 said:
I just towelrooted. It worked! I was watching this video http://gs5.wonderhowto.com/how-to/r...nt-even-at-t-verizon-20-seconds-flat-0155617/ and I did it while I Was watching the video. On my device, it did not even reboot - i just said "should be rooted" so I loaded a root checker and sure enough, it is rooted! took all of about 8 seconds.
Now, on to a rom.
I'm confused now. Why can I not use CM? I read about SafeStrap and I understand it's sort of a dual boot setup - I get that. So, in a sense, I'm not really installing FRESH, a new rom - at least not in the sense that you format your hard disk and install a new OS. However, what ARE my choices in roms? I know the whiz touch, and now the golden eye, plus the google modified - but what else? I want something cut down, simple and battery friendly. I'm not a super power user and I don't require much. Actually, battery life is the most important thing to me.
This is my business phone - I use Gmail, SMS, maybe take a few pictures - and I listen to podcasts. very basic user. Advice?
Click to expand...
Click to collapse
MDL builds have an exploit that allows the kernel to flash. That is loki-doki. Bypasses the Sammy security check to allow this. There is no exploit yet for post MDL builds. Hence you can only flash stock Touch Wiz kernels, thus only roms that have them. So, no aosp based roms. In one of the threads in General that talk about MK2/NC1 etc is a list of roms for you. I forget the technical coding side of SafeStrap. But, it puts roms in System bypassing the bootloader. But, no way of doing that with aosp roms yet.
I am old and don't retain things much anymore if they are not very important to me. So, although I have read up on this stuff, and have a "45 year old" Engineering Degree, I don't need SafeStrap having the MDL bootloader. So, don't remember all that I have read. But, what I said is the basics of it.
Your roms need to have SafeStrap option in the rom thread's OP page. If not listed, it won't work. Having said all that things like Towelroot are new and more options may come along. :good: