Database Info

Unlocked bootloader

So if i unlock my bootloader will i be able to take the JB OTA when it arrives? If not how do i restore the locked bootloader? Also what if my phone has issues.. Would vzw notice i have this?
Sorry if these r dumb questions. I am not 100% on unlocking it.
Sent from my SCH-I535 using Tapatalk 2

Adam outler specifically stated to not do any ota's after unlocking the bootloader...besides the devs will bring us updates faster than ota anyways. Im not 100% but Adam has a stock bootloader.tar posted in the op of his thread. I believe you would flash that in the bootloader function of odin and that will relock your bootloader...now I am not 100% on this, hopefully others will confirm!

The stock bootloader and firmware flash should do the trick to take updates according to Adam himself in the unlock bootloader post. No guarantee you will ever be able to get it unlocked again though.
Also, CyanogenMod team have already switched to working on the CM10 (jellybean) non-kexec version for Verizon now according to the project status page. I wouldn't take Verizon OTA anyway, don't really want the dumbed down no local search that Apple is forcing on us with their patents.

So I should be able to flash any rom i want now? Also what recovery should I use? Stock/CWM/or TWRP? At least for the CM10s
manaox2 said:
The stock bootloader and firmware flash should do the trick to take updates according to Adam himself in the unlock bootloader post. No guarantee you will ever be able to get it unlocked again though.
Also, CyanogenMod team have already switched to working on the CM10 (jellybean) non-kexec version for Verizon now according to the project status page. I wouldn't take Verizon OTA anyway, don't really want the dumbed down no local search that Apple is forcing on us with their patents.
Click to expand...
Click to collapse

llama555 said:
So I should be able to flash any rom i want now? Also what recovery should I use? Stock/CWM/or TWRP? At least for the CM10s
Click to expand...
Click to collapse
First you should wait until Devs start releasing Roms and kernels that take advantage of the unlocked bootloader. If you are this unfamiliar with things, just relax and wait for some new/updated Roms to come out that have clear instructions for you. Don't rush into things and brick your phone because you don't fully understand what you are doing.
Sent from my SGS3 on Synergy Nightlies

Schaweet said:
First you should wait until Devs start releasing Roms and kernels that take advantage of the unlocked bootloader. If you are this unfamiliar with things, just relax and wait for some new/updated Roms to come out that have clear instructions for you. Don't rush into things and brick your phone because you don't fully understand what you are doing.
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
I love you
Sent from my SCH-I535 using xda app-developers app

Schaweet said:
First you should wait until Devs start releasing Roms and kernels that take advantage of the unlocked bootloader. If you are this unfamiliar with things, just relax and wait for some new/updated Roms to come out that have clear instructions for you. Don't rush into things and brick your phone because you don't fully understand what you are doing.
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
I mean I knew exactly how to do things on my DX I just am not as sure with my S3. What recovery would you recommend?

llama555 said:
I mean I knew exactly how to do things on my DX I just am not as sure with my S3. What recovery would you recommend?
Click to expand...
Click to collapse
At this point it's not the recovery but the lack of unlocked bootloader roms (non kexec) for vzws3. I've used rom manager and ez recovery with the s3 with great success.
Sent from my SCH-I535 using Tapatalk 2

voodoomanx said:
At this point it's not the recovery but the lack of unlocked bootloader roms (non kexec) for vzws3. I've used rom manager and ez recovery with the s3 with great success.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The only big difference between cwm 6 and previous versions is its support for kexec, but otherwise does the same thing and can be used for any of the Roms we already have (from what I understand. I tried finding the original thread i read that on but came up short so if I'm wrong someone please correct me as I don't want to spread false information).
And honestly I'm sure almost every rom will be updated within 24 hours to reflect this if not sooner and development will be full steam ahead! Just beware of an OTA cause you know Verizon is not gonna be happy we broke out of their sphere of influence. You can prolly guarantee this "issue" will be towards the top of their to-do list.
Sent from my SCH-I535 using xda app-developers app

Otas cannot be forced though right?
We always have to accept it on our end correct?

asmallchild said:
Otas cannot be forced though right?
We always have to accept it on our end correct?
Click to expand...
Click to collapse
That's not always the case anymore. I've noticed Rezound users have been forced OTA's (update installs without your explicit approval) which means we very well could see the same as well.
Sent from my SCH-I535 using xda app-developers app

asmallchild said:
Otas cannot be forced though right?
We always have to accept it on our end correct?
Click to expand...
Click to collapse
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.

Sccrluk9 said:
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Click to expand...
Click to collapse
Phew good, I'm on Synergy, I think they've blocked OTAs

Sccrluk9 said:
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Click to expand...
Click to collapse
even if you unlock the bootloader and are worried about OTA's just install clockwork mod or team win. the custom recovery will stop the installation of the files. last line of defense as some phones will download and OTA and install it regardless of what you do (rezound, thunderbolt, etc)

droidstyle said:
besides the devs will bring us updates faster than ota anyways.
Click to expand...
Click to collapse
Always, +1. I've never understood the desire to get OTAs afteryou start modding your phone.
llama555 said:
Also what recovery should I use? Stock/CWM/or TWRP? At least for the CM10s
Click to expand...
Click to collapse
As long as there are still kexec roms out there, you'll still need a kexec recovery to flash them. If you know for sure you won't be using kexec, use whatever you want except for stock. Don't ever flash the stock recovery unless you're mailing it off to Verizon.
drbobmd said:
The only big difference between cwm 6 and previous versions is its support for kexec, but otherwise does the same thing and can be used for any of the Roms we already have (from what I understand.
Click to expand...
Click to collapse
That isn't strictly true. CWM 6.x has a couple of nice features that CWM 5.8.x doesn't, like the deduplication technique to save you space when you have multiple backups. You're right though, in that if you're happy with CWM, there's no reason to switch after unlocking.

SFniner415 said:
I love you
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Off topic, sorry, but GO NINERS!!!
Sent from my SCH-I535 using Tapatalk 2

lazarus2405 said:
Always, +1. I've never understood the desire to get OTAs afteryou start modding your phone.
As long as there are still kexec roms out there, you'll still need a kexec recovery to flash them. If you know for sure you won't be using kexec, use whatever you want except for stock. Don't ever flash the stock recovery unless you're mailing it off to Verizon.
That isn't strictly true. CWM 6.x has a couple of nice features that CWM 5.8.x doesn't, like the deduplication technique to save you space when you have multiple backups. You're right though, in that if you're happy with CWM, there's no reason to switch after unlocking.
Click to expand...
Click to collapse
Good to know thank you
Sent from my SCH-I535 using xda app-developers app

so what if your rooted and don't wanna
Flash a Rom is there anything, esle to do to stop an ota?
Sent from my SCH-I535 using xda premium

Hulk0069 said:
so what if your rooted and don't wanna
Flash a Rom is there anything, esle to do to stop an ota?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
My best guess would be to find out what files are responsible for it and see if they are safe to remove via root explorer or something.
Sent from my SCH-I535 using xda premium

Sccrluk9 said:
If you are on a custom ROM most devs will have the OTAs killed off anyways. If you are not on a custom ROM there is really no point in unlocking it.
Click to expand...
Click to collapse
The OTA's also fail once they boot into recovery if the stock recovery isn't there. So it's not likely you'll get a forced OTA that works.

[Q] Looking for the latest (rooted) stock rom

I always hate asking questions like this, because someone inevitably points me to a link that was super-easy to find and I scratch my head wondering how I missed it! But, I am looking for a rooted stock ROM (latest) download link.
I recently upgraded my phone and made the mistake of selling it to someone with the latest CM ROM on it. Although I informed them that it wasn't 100% functional and of course once they had problems with it they returned it to me.
Hence the request for the latest rooted stock rom. I want it rooted since people do look for that and it's on them if they decide to try out new ROMs.
As always, thanks for the assistance.

Does the person you're selling the phone to want it rooted? Cuz they can't flash roms if the bootloader is not unlocked which means you would need to do both.
Sent from my SCH-I535 using Tapatalk 4

It is unlocked and rooted at the moment. I only want to put a stock rom on there to ensure that there are no technical issues that a potential buyer might have running a custom rom (and that they can take it into a verizon store for support).
If necessary, I guess I could unroot it by putting the stock rom back on it and then go through the motions of re-rooting and unlocking. I just assumed that there was a rooted stock rom availble I could flash.
SlimSnoopOS said:
Does the person you're selling the phone to want it rooted? Cuz they can't flash roms if the bootloader is not unlocked which means you would need to do both.
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse

Sisren said:
It is unlocked and rooted at the moment. I only want to put a stock rom on there to ensure that there are no technical issues that a potential buyer might have running a custom rom (and that they can take it into a verizon store for support).
If necessary, I guess I could unroot it by putting the stock rom back on it and then go through the motions of re-rooting and unlocking. I just assumed that there was a rooted stock rom availble I could flash.
Click to expand...
Click to collapse
I would not give someone a rooted and unlocked phone unless they request it. If they request it then fine. Bit otherwise it's a very bad idea. They could be someone who had no idea what root means and screw their phone up. They would take it to Verizon to have it fixed and then Verizon would say "Sorry we don't help people who has modified their software" (root and unlocked).
Sent from my SCH-I535 using Tapatalk 4

Sisren said:
It is unlocked and rooted at the moment. I only want to put a stock rom on there to ensure that there are no technical issues that a potential buyer might have running a custom rom (and that they can take it into a verizon store for support).
If necessary, I guess I could unroot it by putting the stock rom back on it and then go through the motions of re-rooting and unlocking. I just assumed that there was a rooted stock rom availble I could flash.
Click to expand...
Click to collapse
Aight, here it is then. Credit goes to Scrosler for the work. I do agree with @Sandman-007 though, I'd set it back to stock, unrooted and be done with it all. Leaves no stone unturned. Just make sure it is openly stated that the device is rooted and unlocked but with the stock rom installed. Anything less would be negligent.
Sandman-007 said:
I would not give someone a rooted and unlocked phone unless they request it. If they request it then fine. Bit otherwise it's a very bad idea. They could be someone who had no idea what root means and screw their phone up. They would take it to Verizon to have it fixed and then Verizon would say "Sorry we don't help people who has modified their software" (root and unlocked).
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse

ROM after 4.3 OTA Update

I have upgraded to the Verizon 4.3 release for the GS3 and have also rooted the phone using the safe root method. Now I am wondering if I will be able to flash a ROM since upgrading and will the ROM have the same move 2 sd card feature that the 4.3 OTA has... Thanks In advanceee:good:

importiconep3 said:
I have upgraded to the Verizon 4.3 release for the GS3 and have also rooted the phone using the safe root method. Now I am wondering if I will be able to flash a ROM since upgrading and will the ROM have the same move 2 sd card feature that the 4.3 OTA has... Thanks In advanceee:good:
Click to expand...
Click to collapse
4.3 OTA is LOCKED down! If you attempt to flash a ROM or recovery, you WILL HARD BRICK your phone

Doubtful because it hasn't happened to the s4 people. I would say hope for safestrap.
Sent from my SCH-I535 using xda app-developers app

I took the ota. I'm only looking to flash update zips(apks), does this mean I can't even install a custom recovery?
Sent from my SCH-I535 using xda app-developers app

jjosph said:
I took the ota. I'm only looking to flash update zips(apks), does this mean I can't even install a custom recovery?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That is correct, you cannot install a custom recovery on the 4.3 OTA.

landshark68 said:
That is correct, you cannot install a custom recovery on the 4.3 OTA.
Click to expand...
Click to collapse
If you flash an older stock ROM, will this also brick the phone?

omniball3000 said:
If you flash an older stock ROM, will this also brick the phone?
Click to expand...
Click to collapse
Yes, if you took the 4.3 OTA and try to flash an older stock build, you will brick your phone. As it stands right now, if you took the OTA you can root it, but you are still stuck on that stock ROM.

What would happen if we managed to flash a stock ROM like 4.4.x? I've seen so much talk about going backwards, they've locked us out of going backwards so let's go forward...maybe.
Sent from my SCH-I535 using xda app-developers app

ATGkompressor said:
What would happen if we managed to flash a stock ROM like 4.4.x? I've seen so much talk about going backwards, they've locked us out of going backwards so let's go forward...maybe.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
As of right now if you took the OTA update to Android 4.3 your hopes of doing anything custom other than rooting your phone are hopeless.
In order to flash a ROM such as Android 4.4.X aka KitKat you need a custom recovery manager. To be able to flash anything the first thing you need is an unlocked bootloader. The OTA update has locked the bootloader down so that you if you were to try and install CWM or TWRP recovery as soon as you boot into recovery mode you are going to get a Yellow Triangle that says "Verizon has detected unauthorized software on this phone, please turn off your phone and take it in to your nearest Verizon Store.
If you turn off your phone and power it back on you will keep getting that message...
The only way around it is to boot into Download Mode -> Vol Down + HOME for 2 Seconds then hit Power (if i remember correctly). After you boot into download mode you can then boot your phone back up regularly.
If you have made the mistake of trying to put a custom recovery on your phone you can put the stock recovery back on your SGS3 (stock recovery is better than no recovery) by downloading the recovery image and overwriting your custom recovery with the command "dd" in Android Terminal Emulator. For this to work you must be rooted.
Here is a link to the tutorial which shows you how to write the stock bootloader and stock recovery back to your Verizon (d2vzw) SGS3 in case you have made this mistake...
http://forum.xda-developers.com/showthread.php?t=2581166
In that thread pay close attention to the 2nd post as it shows you the commands to use to write your stock recovery or stock bootloader back to your phone.
I know it sucks that we can't put custom ROM's or a custom recovery (this hurts the most!) on our Verizon phone for now at least...
COME ON VERIZON EMPLOYEES! LEAK THE UNLOCKED BOOTLOADER! WE WONT TELL!
Maybe we will get lucky and some international version will come out and we can use that...
I remember awhile back that ASUS locked their bootloader on their Transformer tablet and you could request it from ASUS and they made you fill out this form saying that you understood by unlocking your bootloader you could not make a claim for a warranty. Why can't Verizon do that!?
I pray someone works this out eventually...
"Hope for the best prepare for the worst" - ?
-droidshadow

ATGkompressor said:
What would happen if we managed to flash a stock ROM like 4.4.x? I've seen so much talk about going backwards, they've locked us out of going backwards so let's go forward...maybe.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That would still require you to have a custom recovery. Also that would still most likely brick your phone cause the only 4.4 ROMS are AOSP based, meaning it installs a different kernel than the stock one. Thus when when the phone would boot up it would check the the kernels signature and would brick upon not finding one.

So I guess all hopes of finding a way around this are hopeless...for now. If u remember, a few months ago, President Obama signed a bill for Verizon Wireless to monitor all cell phone activity without the consent of the user, in conjunction with the NSA. I suspect that this is the reason why only Verizon has opted to completely lock down the bootloader because it contains code embedded in the bootloader (or partitions pertaining to bootloaders, aboot, and such) that allow National Security Agencies to implement spyware and tracking or listening programs. This is a testament to the sub-communist movement that is slowly taking hold in this so-called "free" society that was brought forth by our forefathers.
But back on subject - I just upgraded from a HTC Thunderbolt to SGS3 because most development for the Thunderbolt was few and far between. Upon purchasing my shiny new device, this Abomination of Android that is 4.3 was already being OTA'd. Had I known then....man, had I known then. It's a sad time for superusers all-over Verizon's crummy wireless empire.
Sent from my SCH-I535 using xda app-developers app

Is there anyway you could post the link for the safe strap recovery option? I am rooted on 4.3 but I want a recovery that may work so that if this thing gets cracked be that much closer to freedom.
Verizon is doing us like Andy Dufrane...locks us down forcing us to tunnel a hole in the wall and crawl through 3 football fields sh!t to free!
Sent from my SCH-I535 using xda app-developers app

ATGkompressor said:
Is there anyway you could post the link for the safe strap recovery option? I am rooted on 4.3 but I want a recovery that may work so that if this thing gets cracked be that much closer to freedom.
Verizon is doing us like Andy Dufrane...locks us down forcing us to tunnel a hole in the wall and crawl through 3 football fields sh!t to free!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Safestrap is not available for the s3. It would have to be ported.
Sent from my SCH-I535 using Tapatalk 2

You might still be in your window to return the device. Don't they give you like 30 days to try it out and if you don't like you can return for free and try another?
---------- Post added at 12:45 PM ---------- Previous post was at 12:38 PM ----------
ATGkompressor said:
So I guess all hopes of finding a way around this are hopeless...for now. If u remember, a few months ago, President Obama signed a bill for Verizon Wireless to monitor all cell phone activity without the consent of the user, in conjunction with the NSA. I suspect that this is the reason why only Verizon has opted to completely lock down the bootloader because it contains code embedded in the bootloader (or partitions pertaining to bootloaders, aboot, and such) that allow National Security Agencies to implement spyware and tracking or listening programs. This is a testament to the sub-communist movement that is slowly taking hold in this so-called "free" society that was brought forth by our forefathers.
But back on subject - I just upgraded from a HTC Thunderbolt to SGS3 because most development for the Thunderbolt was few and far between. Upon purchasing my shiny new device, this Abomination of Android that is 4.3 was already being OTA'd. Had I known then....man, had I known then. It's a sad time for superusers all-over Verizon's crummy wireless empire.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You might still be in your window to return the device. Don't they give you like 30 days to try it out and if you don't like you can return for free and try another?

wenzer said:
You might still be in your window to return the device. Don't they give you like 30 days to try it out and if you don't like you can return for free and try another?
Click to expand...
Click to collapse
Probably not, it's a 14 day return window now.
Sent from my SCH-I535 using Tapatalk 4

They do have safestrap for i535 for people who have the 4.3 OTA update. I have been looking for a TouchWiz based 4.3 rom to flash in safestrap but have not been successfull. I would love to find one.

I've looking for one and I bricked my phone twice. It looks likes it's going to be a min before we see one.
Sent from my SAMSUNG-SGH-I537 using xda app-developers app

danielevon said:
They do have safestrap for i535 for people who have the 4.3 OTA update. I have been looking for a TouchWiz based 4.3 rom to flash in safestrap but have not been successfull. I would love to find one.
Click to expand...
Click to collapse
There are 3 or 4 - 4.3, Touchwiz ROMS. Old&Slow's stock, rooted ,deodexed; Wicked Sensations; Slapnuts; M.O.A.R (Mother of All Roms). If I missed any I'm sure someone can correct me.
Via Solitary Confined SGS3

ATGkompressor said:
There are 3 or 4 - 4.3, Touchwiz ROMS. Old&Slow's stock, rooted ,deodexed; Wicked Sensations; Slapnuts; M.O.A.R (Mother of All Roms). If I missed any I'm sure someone can correct me.
Via Solitary Confined SGS3
Click to expand...
Click to collapse
Cleanrom 8 and samstock.
Sent from my SCH-I535 using Tapatalk 2

And most of them say specifically that they are for unlocked bootloaders or not compatible with safestrap. Is there some trick I need to know to flash these roms in safestrap on 4.3 with a locked bootloader?

Custom Recovery for Kitkat

I was just wondering if there is any active development or effort going towards getting a custom Recovery for D800s that are rooted with kitkat. I know that you can go back to stock jellybean and then re root and put back the old recovery and then flash away, but I've been holding off on attempting this assuming some talented developer would create a new custom Recovery sooner or later. If nobody is working on it then that's fine and I can use the former method, I would just like to know if me waiting is pointless or not.
Thank you
Sent from my LG-D800

sropedia said:
I was just wondering if there is any active development or effort going towards getting a custom Recovery for D800s that are rooted with kitkat. I know that you can go back to stock jellybean and then re root and put back the old recovery and then flash away, but I've been holding off on attempting this assuming some talented developer would create a new custom Recovery sooner or later. If nobody is working on it then that's fine and I can use the former method, I would just like to know if me waiting is pointless or not.
Thank you
Sent from my LG-D800
Click to expand...
Click to collapse
AutoRec the only ting to keep in mind is that if you are going to flash an aosp/4.2 rom you also got to flash a kk baseband ported for aosp or the jb baseband

Thank you! How would I go about finding one of those basbands?
Edit: when looking at the Mahdi ROM thread I noticed there is a device specific "patch" file that I'm supposed to flash a long with the ROM, is that what you were referring to?
Sent from my LG-D800

sropedia said:
Thank you! How would I go about finding one of those basbands?
Edit: when looking at the Mahdi ROM thread I noticed there is a device specific "patch" file that I'm supposed to flash a long with the ROM, is that what you were referring to?
Sent from my LG-D800
Click to expand...
Click to collapse
No the patches for some roms are because they support multiple devices and the patches are usually modified kernels to boot the different devices the baseband is for touch/gps/radio/rotation/etc there is a the w ad which has most of the jellybean basebands and cloudy has the stock kk basebands in most of his roms thread
Sent from my LG-D800 running stock kk, rooted with philz using XDA app

Is the S5 slipping away?

Is it just me or has development waned for the S5 due to the locked bootloader? There's just so much you can do with safestrap and modifying Touchwiz. In reality, the odds of a bootloader unlock being discovered is rather slim. Look at the S4, the newest firmware releases are still not unlocked and you're forced to use safestrap. I realize we rely on a talented hacker out there to find an exploit that lets us replace the bootloader with a custom one OR the carrier allowing the bootloader to be unlocked. I've read somewhere that the S5 is approved for use by the U.S. Government so the likelihood of Verizon making the phone insecure by allowing people to unlock the bootloader is close to nil. I just really really want to see this phone not slip into XDA obscurity.

terrigan said:
Is it just me or has development waned for the S5 due to the locked bootloader? There's just so much you can do with safestrap and modifying Touchwiz. In reality, the odds of a bootloader unlock being discovered is rather slim. Look at the S4, the newest firmware releases are still not unlocked and you're forced to use safestrap. I realize we rely on a talented hacker out there to find an exploit that lets us replace the bootloader with a custom one OR the carrier allowing the bootloader to be unlocked. I've read somewhere that the S5 is approved for use by the U.S. Government so the likelihood of Verizon making the phone insecure by allowing people to unlock the bootloader is close to nil. I just really really want to see this phone not slip into XDA obscurity.
Click to expand...
Click to collapse
it is slipping away, but not because of the bootloader being locked. Not as many people (devs included) bought the phone as early adopters, so i'm guessing there's just not enough interest or intent in the phone.

terrigan said:
There's just so much you can do with safestrap and modifying Touchwiz.
Click to expand...
Click to collapse
That right there is why development is slow. There's only so much one can do with a stock system to work with. Expect to see development have a boost after each OTA until all mods are worked in, then the same downward slope until the next OTA. Repeat. :good:

MrHyde03 said:
That right there is why development is slow. There's only so much one can do with a stock system to work with. Expect to see development have a boost after each OTA until all mods are worked in, then the same downward slope until the next OTA. Repeat. :good:
Click to expand...
Click to collapse
There may be hope for that. Over in the Verizon S4 forums, they got kexec working. No aosp yet, and its very unstable, but they found it. It should work on the S5 with a little more work. Hopefully this happens this month.
Sent from my SM-G900V using XDA Premium 4 mobile app

eragon5779 said:
There may be hope for that. Over in the Verizon S4 forums, they got kexec working. No aosp yet, and its very unstable, but they found it. It should work on the S5 with a little more work. Hopefully this happens this month.
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This would be good. kexec was the savior of my previous phone.

eragon5779 said:
There may be hope for that. Over in the Verizon S4 forums, they got kexec working. No aosp yet, and its very unstable, but they found it. It should work on the S5 with a little more work. Hopefully this happens this month.
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm not sure if kexec is possible without having a SELinux permissive kernel. I believe the Galaxy s5 is enforcing unfortunately (not vulnerable).

jal3223 said:
I'm not sure if kexec is possible without having a SELinux permissive kernel. I believe the Galaxy s5 is enforcing unfortunately (not vulnerable).
Click to expand...
Click to collapse
That is being worked on already. There is a thread about it.
Sent from my SM-G900V using XDA Premium 4 mobile app

I really hope they are successful.

eragon5779 said:
There may be hope for that. Over in the Verizon S4 forums, they got kexec working. No aosp yet, and its very unstable, but they found it. It should work on the S5 with a little more work. Hopefully this happens this month.
Sent from my SM-G900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Actually I'm running a GPE ROM on my Verizon S4 right now. It's SafeStrap compatible. I love AOSP vs TouchWiz.

Being pessimistic it does seem like the beginning of the end for s5. By this I mean to say that safestrap just doesn't cut it as I do not like stock kernel. But everyone's done an amazing job thus far so haven't completely given up but I think nexus devices are the route I will take.

jal3223 said:
I'm not sure if kexec is possible without having a SELinux permissive kernel. I believe the Galaxy s5 is enforcing unfortunately (not vulnerable).
Click to expand...
Click to collapse
to my knowledge it is in the kernel. on vzw s4 mdk devicds were unlocked allowing you to flash custom kernals that were modded by devs like ktoons to make it permissive..
The later firmware builds (cant go back to mdk if took ota to a newer firmware) are in the same boat as the s5 so if they have it on later kernal builds for the s4 then it might b possible.. then again, they have it on the note 3 but doesnt work on the s5 so that concept isnt always possible

Not slipping away. Just at a road block. Everyone has done all the modding they can do on the device. I think everyone is waiting on 5.0.

elliwigy said:
to my knowledge it is in the kernel. on vzw s4 mdk devicds were unlocked allowing you to flash custom kernals that were modded by devs like ktoons to make it permissive..
The later firmware builds (cant go back to mdk if took ota to a newer firmware) are in the same boat as the s5 so if they have it on later kernal builds for the s4 then it might b possible.. then again, they have it on the note 3 but doesnt work on the s5 so that concept isnt always possible
Click to expand...
Click to collapse
I'm working on it. It's rather difficult. It appears the kernel was compiled with no /dev/mem(kmem) character devices in the config. After going through the kernel source, it looks like SELinux was set to always enforce. This is where ro.build.selinux.enforce=1 comes from. The bootloader checks the boot.img hash and for a special cookie
Code:
SEANDROIDENFORCE
which appears before the hash. If this cookie/magic isn't present, the warranty bit will blow. Since I can't access memory directly, and the methods I could use are significantly limited because of the Enforcing status, some sort of vulnerability in the kernel will need to be present. As soon as we can get Permissive, I can get us kernel modules, and hopefully kexec with the help of a few other great devs @Surge1223 @CalcProgrammer1

Your efforts are truly appreciated!
Sent from my SM-G900V using Tapatalk

The OP is originally from September something. I just seen this post and was interested in it, it is now November and if you ask me, yes it has slipped away, technology moves on quickly, i6+ is out and now we will start seeing things about a s6 in the works and it is what it is.
I blame the locked bootloader on a ton of stuff not being created. You have to grab ahold of technology in the moment and use it fast or else its gone before you know it.

It is certainly nothing like the S3 forums. That place is still kicking.

From what I understand they're close to kexec on it and the S4, since they only need KK-compatible kernels and they previously had unlocked bootloaders. That isn't the case here.
Samsung really screwed up with this one. If the N6 wasn't assured to be a failure on Verizon and it didn't have a massive footprint I'd be all over it.

Everybody panic.

Wish we can get some good news soon.

Dead is all I'm seeing, except for the few amazing devs we have now. Those still building, thank you
Galaxy 6s Os 6.2.8▪Ss° Pen