OK so I have no clue really want safestrap is really. I've only had phones that I could unlock my bootloader.
I guess my questions are is how much different is safestrap vs unlocked bootloader and did Verizon/Samsung lock this thing down to the point we can't unlock this thing.?
I just bought this phone on Verizon edge and had no knowledge about this thing being locked down.
Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.
I've had safe strap on my bionic and flashed asop ...but why would anyone on this device want asop??? ...that would not make a lot of..."touchwiz" lol.
Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app
jprovan1 said:
Thanks for the reply. Yes your correct but no need to be an douche. Yes search answers questions but people who have used safestrap can sometimes provide better answers. This is the q&a section so that means you can ask questions. Anyways thanks for part of your reply.
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I hope that was for the jerk and not the joke.....
Was for the jerk. I liked the joke
Sent from my SM-N900V using xda app-developers app
xdadevnube said:
Simple search will help.
Safe strap allows you to Flash stock ROMs and stock kernels. It is not a bootloader bypass. You cannot have recovery at this time. The chance of an actual bootloader unlock and/or recovery is slim.
We currently do have root.
If you want to do anything other than flash stock based ROMs and kernels (when SS is available, which is likely soon), then you should use a different device or get the Dev edition when it comes out.
You should do more research before putting that much money on a device down. I want the Note3 very much, but I much prefer a device with more flexibility, even if it isn't as badass.
Click to expand...
Click to collapse
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.
Banggugyangu said:
This is wrong. Safestrap is a bootstrap recovery. It IS a "bootloader bypass" of sorts. Once everything is squared away, safestrap WILL allow flashing of non-stock ROMs and the execution of Kexec kernels. We will have access to almost everything available with an unlocked bootloader, except it will require room on our internal storage for the ROM files.
Click to expand...
Click to collapse
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.
xdadevnube said:
AFAIK, it will not allow kexec, as that is a different exploit. Also, it cannot modify aboot. So you will not be able to install AOSP ROMs or anything but a modified stock kernel. Believe me, I would love to be wrong.
Click to expand...
Click to collapse
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.
Do we loose safestrap if we take OTA upgrade to Kitkat (when it's available)?
Banggugyangu said:
Hashcode has implemented kexec into nearly every device's safestrap. Also, AOSP is still possible with the stock kernel. You simply have to incorporate certain parts of the stock ROM. I did all of this on the Droid Bionic. I had an AOSP ROM before safestrap was even created. It had a couple Blur elements that were very minor, but required.
Click to expand...
Click to collapse
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.
xdadevnube said:
I was thinking of the S4 that doesn't have kexec and cannot flash AOSP. It is reasonable to assume that the N3 could get kexec even although the S4 doesn't have it.
SS is not bootloader bypass. Many benefits of an unlocked bootloader will not be realized with SS. However, it should be a decent option for at least getting some ROMs. With kexec, then most people will be happy.
Click to expand...
Click to collapse
There is a huge difference when Hashcode has the phone in question. It's my understanding that this is the first Samsung phone he has had.
So he's stated that he plans to add kexec? That would be [email protected]$$.
Sent from my SM-N900V using Tapatalk
Related
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....
Okay! So I present you all with a question. I've read multiple threads on safestrap ROMs and id you have the MDL loader on how you can in-fact load custom ROMs.
But here's my biggest question, (I'm not sure if this should go in a dev sub-forum or here, but this seemed to make the most sense) but here it is, Is there any reason or advantage to stay on the MF3 bootloader firmware (4.2.2) which is locked to safestrap.
As in is there any progress whatsoever on the ability to install custom ROMs on this version, or any estimations or just plain and simple to not be rude, but is there remotely any way to install custom non-TW, non 4.2.2 ROMs, via safestrap on the firmware?
Or would I be better off upgrading via OTA to 4.3.3 so that I can utilize my Galaxy Gear, with retaining my root from SuperSU Pro "Survival Mode"? To be totally honest from the looks of the forums and Q+A recently most ATT users have done this exact thing.
That being said is there any sort of progress or planned progress/development towards the ability to create custom ROMs for these new MK2 bootloaders? I'm sure any ROM developer that wishes to continue to create ROMs that can be used by more than a slim picking would be on this development already but that's my questions!
Xeon.Jamal said:
Okay! So I present you all with a question. I've read multiple threads on safestrap ROMs and id you have the MDL loader on how you can in-fact load custom ROMs.
But here's my biggest question, (I'm not sure if this should go in a dev sub-forum or here, but this seemed to make the most sense) but here it is, Is there any reason or advantage to stay on the MF3 bootloader firmware (4.2.2) which is locked to safestrap.
As in is there any progress whatsoever on the ability to install custom ROMs on this version, or any estimations or just plain and simple to not be rude, but is there remotely any way to install custom non-TW, non 4.2.2 ROMs, via safestrap on the firmware?
Or would I be better off upgrading via OTA to 4.3.3 so that I can utilize my Galaxy Gear, with retaining my root from SuperSU Pro "Survival Mode"? To be totally honest from the looks of the forums and Q+A recently most ATT users have done this exact thing.
That being said is there any sort of progress or planned progress/development towards the ability to create custom ROMs for these new MK2 bootloaders? I'm sure any ROM developer that wishes to continue to create ROMs that can be used by more than a slim picking would be on this development already but that's my questions!
Click to expand...
Click to collapse
Hashcode the man behind safestrap Is working on bri ging safestrap to 4.3....other than that, other people may be working on it or they may not. 99% of rom devs dont have the skill to unlock a bootloader, not saying they are bad devs but it takes a completely differnt set of dev skills to unlock a bootloader...alot more coding
Sent from my SAMSUNG-SGH-I337 using Tapatalk
mg2195 said:
Hashcode the man behind safestrap Is working on bri ging safestrap to 4.3....other than that, other people may be working on it or they may not. 99% of rom devs dont have the skill to unlock a bootloader, not saying they are bad devs but it takes a completely differnt set of dev skills to unlock a bootloader...alot more coding
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Awesome, but there would still be no way to truly get ROMs like Dandroid or anything that has kitkat or non TW right? I know what you are saying about the devs. Its a totally different skillset. I hadn't thought of that. D'Oh! Thanks for the reply! I might upgrade to 4.3.3 so I can utilize my hear now!
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.
Hey,
I got my Galaxy S4 AT&T SGH-I337 as I337UCUAMDB, and ever since then was running cyanogenmod 11.
Recently after a stupid mistake (updating to a nightly, then to M10) I had to return to stock ROM, and on a CM dev's lead installed a NB1 ROM.
Since then, I wasn't able to install TWRP (installing it would make the phone boot only into download mode), and installing CM would produce constant "com.android.phone/acore/media" errors.
Right now I'm running Google Edition for SafeStrap (v1.1 - 4.4.4), which, TBH, isn't nearly as good as CM11 and still very buggy...
I read as much as I could about the whole AT&T GS4 bootloader situation, but still haven't understood it fully:
Could my bootloader have been locked by the update?
If not, why can't I install a custom recovery and CM again?
If so, is there anyway I can downgrade back to MDB (maybe from here?) Or to anything that can allow me to install CM again?
Thanks in advance,
Yuval.
Edit: If I can still use safestrap to install any custom ROM, why can't I install CM? (I did a clean install [full wipe] a couple of times, w/ and w/o gapps, to no avail) Or did I not understand well the safestrap custom ROM options?
Your bootloader was always locked, loki just exploited it.
You have to use SafeStrap as MF3 (I think) and above closed the loki patch. That means no custom kernels and no custom recovery.
No, you can't downgrade back. Sorry.
I would highly recommend reading before you make any major changes to your phone in the future.
RAID Xero said:
Your bootloader was always locked, loki just exploited it.
You have to use SafeStrap as MF3 (I think) and above closed the loki patch. That means no custom kernels and no custom recovery.
No, you can't downgrade back. Sorry.
I would highly recommend reading before you make any major changes to your phone in the future.
Click to expand...
Click to collapse
Thanks for your comment! I understand the loki patch, but wasn't sure if it was automatic up until then (I haven't applied it manually).
No custom kernel or recovery is more than fine by me as long as SafeStrap serves as a practical replacement for one (custom recovery), but it still does not solve my problem:
I'm unable to install CM11 M10, even after multiple clean flashes with SafeStrap.
I realise this might not be a bootloader problem as I previously thought, but would still appreciate any intake as to how to solve this.
I read extensively about the SGH-I337 situation, but albeit technologically-oriented, didn't grasp it fully. Thanks for helping to clarify this up!
novikyuval said:
Thanks for your comment! I understand the loki patch, but wasn't sure if it was automatic up until then (I haven't applied it manually).
No custom kernel or recovery is more than fine by me as long as SafeStrap serves as a practical replacement for one (custom recovery), but it still does not solve my problem:
I'm unable to install CM11 M10, even after multiple clean flashes with SafeStrap.
I realise this might not be a bootloader problem as I previously thought, but would still appreciate any intake as to how to solve this.
I read extensively about the SGH-I337 situation, but albeit technologically-oriented, didn't grasp it fully. Thanks for helping to clarify this up!
Click to expand...
Click to collapse
Very simply, you can not run cm anymore. You're stuck with touch wiz based roms after you updated the firmware.
Sent from my Nexus 5 using XDA Free mobile app
You can run a Google Play Edition ROM, that's about as close to CM as you're going to get using SafeStrap.
jd1639 said:
Very simply, you can not run cm anymore. You're stuck with touch wiz based roms after you updated the firmware.
Click to expand...
Click to collapse
RAID Xero said:
You can run a Google Play Edition ROM, that's about as close to CM as you're going to get using SafeStrap.
Click to expand...
Click to collapse
Okay, I think I now fully understand this. Thank you RAID Xero and jd1639 for the help!
I guess I learnt my lesson to look into evil AT&T ROMs before updating to and from them
Also, too bad I never noticed any warning regarding this on Cyanogenmod's website (or maybe I just missed it)...
Thanks again, and unless there's a new magical way to bypass the locking, this thread may be marked as locked.
You're welcome, and happy flashing!
I am looking to get rid of my htc one m8 and go back to Samsung. I know the s5 does not have an unlocked boot loader but it looks like custom roms can happen via safestrap. My question is, when buying the phone used, is there a specific software version i DO NOT want? The goal is to root, safestrap and then put some sort of custom rom on the phone.
Thanks
dougmod said:
I am looking to get rid of my htc one m8 and go back to Samsung. I know the s5 does not have an unlocked boot loader but it looks like custom roms can happen via safestrap. My question is, when buying the phone used, is there a specific software version i DO NOT want? The goal is to root, safestrap and then put some sort of custom rom on the phone.
Thanks
Click to expand...
Click to collapse
Currently you are good to go even on the latest NI2 update. You only need to downgrade the kernel to NCG via odin, run towel root, then reflash the newest NI2 kernel. There is a good write-up on it. Just look a few posts down.
BladeRunner said:
Currently you are good to go even on the latest NI2 update. You only need to downgrade the kernel to NCG via odin, run towel root, then reflash the newest NI2 kernel. There is a good write-up on it. Just look a few posts down.
Click to expand...
Click to collapse
Thanks for the reply. I'm so excited to get off of the m8. The reception is terrible.
I also see that the dev scene looks pretty limited in the Verizon section. Is that because everything has been unified like the s4 so I can pretty much use any rom? AOsp, cm, etc
dougmod said:
Thanks for the reply. I'm so excited to get off of the m8. The reception is terrible.
I also see that the dev scene looks pretty limited in the Verizon section. Is that because everything has been unified like the s4 so I can pretty much use any rom? AOsp, cm, etc
Click to expand...
Click to collapse
No, unfortunately, things are somewhat limited as the bootloader remains unlocked for the consumer edition so no custom kernels.
I think he meant to say the bootloader remains locked on the retail version.
Sent from my SM-G900V using XDA Free mobile app
kclive said:
I think he meant to say the bootloader remains locked on the retail version.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
thanks, you are correct :silly: