Database Info

Samsung "Custom Lock" icon on boot

Not sure if this has been answered already (maybe I'm bad at searching) or if it has to do with the Flash Counter, but anyone know how to get rid of the Custom Lock icon that appears on the boot up screen?

Young War said:
Not sure if this has been answered already (maybe I'm bad at searching) or if it has to do with the Flash Counter, but anyone know how to get rid of the Custom Lock icon that appears on the boot up screen?
Click to expand...
Click to collapse
Yep been answered before.
You get it when you flash a non 100% original Odin package. So like route 66.
To make it go away you have to flash the completely stock Samsung image and do the non Odin root in the dev section.
Sent from my SCH-I535 using xda app-developers app

nosympathy said:
Yep been answered before.
You get it when you flash a non 100% original Odin package. So like route 66.
To make it go away you have to flash the completely stock Samsung image and do the non Odin root in the dev section.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thank you. Is there currently any known reasons if this should cause concern? I should be good with leaving it as is atm, right?
Hoping eventually there's a flashable zip to clear that...

It also happens if you do the non ODIN root and then you freeze or remove systems apps

Will the USB Jig from the SGS2 do anything for this Device?
Sent from my SPH-D710 using Tapatalk 2

pyrostic said:
Will the USB Jig from the SGS2 do anything for this Device?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Not sure but from what I have read it doesn't appear to be compatible. Pins are in different places.
Sent from my SCH-I535 using xda premium

pyrostic said:
Will the USB Jig from the SGS2 do anything for this Device?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Yes. The jig from the s2 works and will reset the counter and eliminate the lock image.
Sent from my SCH-I535 using xda premium

wpbear said:
It also happens if you do the non ODIN root and then you freeze or remove systems apps
Click to expand...
Click to collapse
It does not ... if you disable the SysScope.apk immediately after rooting.

I like the unlock custom display. Shows that I am enjoying my custom phone!

AdamHLG said:
I like the unlock custom display. Shows that I am enjoying my custom phone!
Click to expand...
Click to collapse
+1 I love your comment. Unless bringing in for warranty, who cares.
Sent from my SCH-I535 using xda premium

AdamHLG said:
I like the unlock custom display. Shows that I am enjoying my custom phone!
Click to expand...
Click to collapse
^ this!
Sent from my SCH-I535

lowg said:
It does not ... if you disable the SysScope.apk immediately after rooting.
Click to expand...
Click to collapse
Can you go into more detail? Wouldn't you have to boot after root, so can disable SysScope be done anytime? What other uses did SysScope have?

wpbear said:
Can you go into more detail? Wouldn't you have to boot after root, so can disable SysScope be done anytime? What other uses did SysScope have?
Click to expand...
Click to collapse
If you use the "debugfs" exploit, once you obtain root, the first thing you should do is rename /system/app/SysScope.apk and you should be good.
My method was based off analysis done by Ralekdev, which according to him there is a process scanner as part of SysScope.apk that will look for apps running as root outside a list of 'whitelisted' apps.
To your question, yes it is a bit of what came first the chicken or the egg -- but I'm assuming this process scanner is not constantly running so if you just do it right away before running other apps as super user regularly there is little chance it will be tripped.

I used the odin way to root my device and the GPS does not work so I received my CLN device and need to get rid of the custom boot. Is there any other way to get rid of it?

Custom recoveries are what triggers the unlock icon. If you flash the stock recovery, the unlock icon should disappear.

There are actually other ways to get the padlock notification than custom recoveries. I've got it from modifying my framework-res.apk file, and you can get it from deleting and modifying system apps, changing ROMS through Odin and so on. It's really not a big deal unless you need to clear it for warranty related purposes. If you do, follow the guide on development, or get a jig for 3 bucks on ebay.

I just followed the guide in the development sections. Everything is A-OK and I'm ready to send back in the old one. The CLN device seems to be in pretty good shape.

ilkevinli said:
Custom recoveries are what triggers the unlock icon. If you flash the stock recovery, the unlock icon should disappear.
Click to expand...
Click to collapse
For what it's worth I flashed TWRP using dd and did not trip the counter after disabling the apk (and shared lib it uses to be sure).
Sent from my Galaxy S3

I had the unlocked lock image when I rooted with Odin and flashed bean rom, the flashed cm10 and it disappeared. I kind of like it too. It shows I'm not a square... or am I
Sent from my SCH-I535 using xda premium

Young War said:
Thank you. Is there currently any known reasons if this should cause concern? I should be good with leaving it as is atm, right?
Hoping eventually there's a flashable zip to clear that...
Click to expand...
Click to collapse
Leave it and display it like a badge of honor. A big fu to vzw if you will.

Little clarification and help please

Hi guys! I am switching from a GSIII to this on Tuesday and I know a bit about rooting but I wanted to know what is the main differences between being rooted and having a unlocked bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium

Optimizer said:
Hi guys! I am switching from a GSIII to this on Tuesday and I know a bit about rooting but I wanted to know what is the main differences between being rooted and having a unlocked bootloader?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Being rooted allows you to unlock the bootloader which allows all the magic that happens here. If you are getting a hox now make sure it does not come with 4.0.4 installed as there is no root for that yet.

I don't think you have to be rooted to flash a recovery. You just have to unlock your bootloader and flash a recovery via adb command.
Sent from my HTC One X using xda app-developers app

Nabeel Kiani said:
I don't think you have to be rooted to flash a recovery. You just have to unlock your bootloader and flash a recovery via adb command.
Click to expand...
Click to collapse
On AT&T you need to be rooted to unlock the bootloader, as the bootloader unlock is not officially available. But on Rogers, you can unlock the bootloader and install a custom recovery, AFAIK.
In short, root just gives superuser privileges. So you have access to system files, can apply mods and apps that require root (but not flashed in recovery) etc.
Bootloader unlock is required if you want to flash custom ROMs, radios, kernels, custom recovery, etc.

So I am on ATT and I got the one x shipped to me and it will be here tomorrow so there will be no rooting for me until someone finds an exploit I am thinking
Sent from my SAMSUNG-SGH-I747 using xda premium

Optimizer said:
So I am on ATT and I got the one x shipped to me and it will be here tomorrow so there will be no rooting for me until someone finds an exploit I am thinking
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I'm afraid so.

gunnyman said:
I'm afraid so.
Click to expand...
Click to collapse
Is there a root method or a way of at least removing bloat to where maybe I can't have a unlocked bootloader but I would at least like it debloated... has anyone found a way for that yet? lol

Optimizer said:
Is there a root method or a way of at least removing bloat to where maybe I can't have a unlocked bootloader but I would at least like it debloated... has anyone found a way for that yet? lol
Click to expand...
Click to collapse
That's a negative grasshopper.

gunnyman said:
That's a negative grasshopper.
Click to expand...
Click to collapse
Well, I am willing to donate to whoever finds one!

Optimizer said:
Well, I am willing to donate to whoever finds one!
Click to expand...
Click to collapse
You should politely ask Gunny to make a bounty thread. He absolutely loves them.

Smh

Optimizer said:
Is there a root method or a way of at least removing bloat to where maybe I can't have a unlocked bootloader but I would at least like it debloated... has anyone found a way for that yet? lol
Click to expand...
Click to collapse
You can reduce the majority of the bloat in an unrooted stock phone running an ICS firmware by "disabling" the unneeded bloatware system apps by going into the stock app manager, then selecting to view all apps, then pressing on each system bloat app you don't need, and hitting "disable" in the app info dialog that opens up. Disabling the system apps makes them invisible to the system and the app drawer. Thus, they can't be run by you or the system until you enable them again. Thus, they don't bog down your phone and trash up your app drawer.
This works for the majority of the bloat that comes with AT&T. I did this while I was waiting for the famous 1.85 root method. It made my wait considerably more bearable!
Sent from my One X using xda app-developers app

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.

[Troubleshooting] Loki [possible 4.3 bootloader Exploit] (op updated 01/23/14)

What is Loki?
In a nutshell this exploit will if it works edit cwm and twrp to work with the 4.3 bootloader and to flash patched kernels to work with the new bootloader. This would mean 4.3 OTA people could flash any rom 4.1.2 people can with a custom recovery flashed from loki and a minor tweak to the kernel. The bootloader is not touched instead tricked into thinking any kernel that has the loki code is the stock kernel. Loki exploit was found by djrbliss
Click to expand...
Click to collapse
I just need a second person to verify (Preferably trial run) if this is patched for sure or not.
revasm said:
Hey everyone,
I'm sorry to bring bad news, but ML1 is hardened against the Loki exploit. boot_linux_from_mmc checks boot headers now, and aborts if they attempt to overwrite aboot. check_sig is different as well, but I didn't examine it more.
IDA results: https://gist.github.com/revasm/8572927
Click to expand...
Click to collapse
I have had no luck figuring out how to work
Code:
loki_find-linux-x86_64
This is needed to get the offsets from the aboot.img to put into the
Code:
loki_patch.c
Then compile into a binary so it can flash the custom recovery into a .lok
I will not be asking djrbliss for help and I urge you to not bug him. Chances are this exploit has been patched and will not work for our bootloader. But if anyone gets bored and wants to try to figure it out who knows maybe our bootloader still has the exploit?
First order of business we need to figure out how to get the loki_find binary to read the offsets from the aboot.img or find a diffrent way to figure the offsets out.
Who ever figures that one out will need no help setting up the patch file and test it out.
Pull your aboot.img with adb (windows or Linux)
make sure you pull the aboot.img from the code below and not from /dev/block/mmcblk0p5
Code:
adb shell
su
dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/data/local/tmp/aboot.img
chmod 644 /data/local/tmp/aboot.img
exit
exit
adb pull /data/local/tmp/aboot.img
The next step is the one I am stuck on hopefully someone can figure it out.
source Links:
djrbliss GitHub
technical blog post
[LOKI] Bootloader hack official FAQ thread
Downloads:
loki-master.zip <--- from djrbliss GitHub
loki-master.7z <-- (mirrored my myself 1/22/14)
aboot.7z <-- Must extract (My aboot.img)
ADB Only (Windows)
ADB Only (Linux) <-- Plus instructions
bootimg_tools.7z -- Might help us (Not my work but I did create both of the read me files with original links)

<never know>

Disregard
Sent from my SCH-I535 using Tapatalk

Bump.

Disregard

Yes. It is. I'll try flashing to stock tomorrow if it doesn't help
Sent from my SCH-I535 using Tapatalk

This should be interesting.

I must of been to tired to read how to do this correctly last night. Will hopefully have a Loki zip for using non stock kernels when i get home. The aboot we were pulling was the wrong aboot. If so this will turn into a summary of what I did/ step by step on how you can do it if you want to get your superuser funk on.

ThePagel said:
I must of been to tired to read how to do this correctly last night. Will hopefully have a Loki zip for using non stock kernels when i get home. The aboot we were pulling was the wrong aboot. If so this will turn into a summary of what I did/ step by step on how you can do it if you want to get your superuser funk on.
Click to expand...
Click to collapse
Great news.
Sent from my SCH-I535 using Tapatalk

Keep us updated.
Sent from my SCH-I535 using Tapatalk

I feel dumb but what's all this mean? Lol
Sent from my SCH-I535 using xda app-developers app

cplking said:
I feel dumb but what's all this mean? Lol
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
It means if this all works, anyone who grabbed the 4.3 ota can use safe strap with non touchwiz based roms. At least, that's my understanding.
Sent from my SCH-I535 using Tapatalk

cplking said:
I feel dumb but what's all this mean? Lol
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
That'd be great cuz I'm going through aosp withdrawals lol
Sent from my SCH-I535 using xda app-developers app

Dadud said:
It means if this all works, anyone who grabbed the 4.3 ota can use safe strap with non touchwiz based roms. At least, that's my understanding.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Or for the more technical info, read:
http://forum.xda-developers.com/showthread.php?t=2292157
Sent from my SCH-I535 using Tapatalk 4

You shouldn't feel dumb I took down the link that explained everything. In a nutshell this exploit will if it works edit cwm and twrp to work on the 4.3 bootloader and to flash edited roms to work with the new bootloader. Note that safestrap at least for the the being will not work with Loki. you will need to pick what you want more any ROMyou want but stuck to one ROM slot or a few ROM slots that only boot 4.3 tw ROMs. Just don't get your hopes up the only way this will work is if Samsung forgot to patch the exploit. The newer s4 bootloaders are patched. http://blog.azimuthsecurity.com/2013/05/exploiting-samsung-galaxy-s4-secure-boot.html?m=1
The ROMs themselves will also need to be loki patch (that's the easy part)

If I were to be the lab rat for testing this, this won't set off a qfuse and brick my phone will it, or is that to be found out as we go along? I have all the odin files to flash back to unrooted stock.
Sent from my SCH-I535 using Tapatalk

Dadud said:
If I were to be the lab rat for testing this, this won't set off a qfuse and brick my phone will it, or is that to be found out as we go along? I have all the odin files to flash back to unrooted stock.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
No it doesn't touch the boot loader. It tricks the boot loader to think any kernel you load is the stock kernel.

ThePagel said:
No it doesn't touch the boot loader. It tricks the boot loader to think any kernel you load is the stock kernel.
Click to expand...
Click to collapse
Sounds good. i'll be defiantly helping you test this out.

OK so what do I need to make a Loki patch? You mentioned that you were pulling the wrong aboot?
Sent from my SCH-I535 using Tapatalk

Besides the only fuse that can be triped on this phone is the warranty bit. I think that was proven by people fully over weighting there boot loader and making a revival from the hard brick.

[FIRMWARE 4.4.2] VRUDNE1 full wipe tar + NE1 Update Zip

For d2vzw SCH-I535 ONLY
This is the official tar ball for VRUDNE1. DO NOT DOWNLOAD THIS FILE UNLESS YOU ARE 100% SURE YOU KNOW WHAT YOU ARE DOING. Any locked bootloaders are not my fault.
THIS WILL LOCK YOUR BOOTLOADER FOREVER
4.4.2 VRUDNE1 full wipe tar download HERE
No Wipe HERE​
4.4.2 Update Zip
For reasons that should be obvious I recommend not to update yet unless you really cant wait. This zip was ripped out of the ota download folder I have not applied it myself so use at your own risk.
There has been successful upgrades using this update zip.
I am assuming you must be on a untouched version of nc1 for this to work (no root) apply update zip in stock recovery.
Download the 4.4 update zip from HERE

techfreak243 said:
i played the stupid card and softbricked my S3. i was in a curious mood and wanted to go back to a fresh 4.3 to get to a fresh 4.4.2. is there anyway for me to unbrick it with or without losing my data (preferrably losing because i want a fresh start). Does anybody know when a tar will be ready or when the file will be available through the Verizon Repair Assistant?
Click to expand...
Click to collapse
flash this via odin if you bricked your bootloader!
contain: tz.mbn sbl3.mbn sbl2.mbn rbm.mbn aboot.mbn
flash on VRUDNE1 kitkat tw only

Thanks @ThePagel! Can't wait for the Tar file

I'm on the newest clean Rom but badly want tw kit Kat. I don't care about losing the ability to flash aosp or flash kernels. So when the tar comes out I will be able to just load that into Odin and put on my phone?
Sent from my SCH-I535 using XDA Premium 4 mobile app

yonith said:
I'm on the newest clean Rom but badly want tw kit Kat. I don't care about losing the ability to flash aosp or flash kernels. So when the tar comes out I will be able to just load that into Odin and put on my phone?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes sir

yonith said:
I'm on the newest clean Rom but badly want tw kit Kat. I don't care about losing the ability to flash aosp or flash kernels. So when the tar comes out I will be able to just load that into Odin and put on my phone?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You really can't wait a few more days for a new CleanROM?
Are you really that desperate to permanently lock down your phone in such a way that only a hard-wired JTAG procedure can undo?
If you lock your bootloader, you are stuck with SafeStrap and needlessly wasting space on your phone to accommodate ROM slots.

LLStarks said:
You really can't wait a few more days for a new CleanROM?
Are you really that desperate to permanently lock down your phone in such a way that only a hard-wired JTAG procedure can undo?
If you lock your bootloader, you are stuck with SafeStrap and needlessly wasting space on your phone to accommodate ROM slots.
Click to expand...
Click to collapse
Agreed.

It worked for me. Thank you
Sent from my SCH-I535 using Tapatalk

I messed something up, now I can't odin back to 4.3 and all I get is the firmware upgrade encoundered an issue... when I try to odin back to 4.3 it fails.. oops.

reno218 said:
I messed something up, now I can't odin back to 4.3 and all I get is the firmware upgrade encoundered an issue... when I try to odin back to 4.3 it fails.. oops.
Click to expand...
Click to collapse
Were you on KitKat? Cuz that's not possible to do.

LLStarks said:
You really can't wait a few more days for a new CleanROM?
Are you really that desperate to permanently lock down your phone in such a way that only a hard-wired JTAG procedure can undo?
If you lock your bootloader, you are stuck with SafeStrap and needlessly wasting space on your phone to accommodate ROM slots.
Click to expand...
Click to collapse
My understanding is that this is going to be similar to the gs4 where there are frankenkernels and frankenroms hacked together to keep our bootloader unlocked. This isn't as reliable as the straight kernel. Correct me if I'm wrong that was just the impression I got.
Sent from my SCH-I535 using XDA Premium 4 mobile app

I have a locked boot loader, I took t the 4.3 ota. If I take this new ota is there a way to root once it updates?
Sent from my SCH-I535 using Tapatalk

greatdaneduke said:
I have a locked boot loader, I took t the 4.3 ota. If I take this new ota is there a way to root once it updates?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Yes - search for Towelroot in this forum, works great - and super easy.

yonith said:
My understanding is that this is going to be similar to the gs4 where there are frankenkernels and frankenroms hacked together to keep our bootloader unlocked. This isn't as reliable as the straight kernel. Correct me if I'm wrong that was just the impression I got.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
This is FUD. You've been misled. Custom roms do not touch unlocked bootloaders or require exotic engineering to keep things that way.
If you've unlocked your bootloader anytime within the past 2 years, you're set. You don't need to do anything. Just don't take the damn OTA. You should be on a custom rom or have already disabled such OTA functionality manually. If you take the OTA, you are screwed no matter what.
There's no frankenkernels or frankenroms. If you want to make a rom based on the update for normal folks who were smart enough to keep their bootloader unlocked, you simply remove the bootloader files altogether from the OTA tar/zip and begin customizing. You can use the stock kernel or compile your own using the source Samsung provided. For the poor souls who are locked down, they are stuck with the stock kernel and SafeStrap. Only thing they can modify is the system partitions they create.
There's nothing "franken" about either approach.
The only people with weird bootloader configurations are those who dipped in and out of OTA sequencing. Maybe their SBL or RPM/TZ partitions are stuck at LF2 or something just as ancient.
Ideally, every binary partition should be at firmware MF1 except for the aboot at LE6. My modem is at ML1 for the hell of it since flashing modems (even from the locked down 4.3 OTA) is safe.
tl;dr The unlocked rom scene is not impacted by Knox or anything OTAs lock down. It exists outside of the walled garden Verizon and Samsung are trying to create.

Well thanks for enlightening me! I will hold out until one of or beloved devs cook up a rom.

If I were everyone in this thread...
I would just chill out for a while...

scrosler said:
If I were everyone in this thread...
I would just chill out for a while...
Click to expand...
Click to collapse
This man right here...listen to this man.

Woot woooooooo.
Chillin like it's my job.
Sent from my SCH-I535 using XDA Free mobile app

open1your1eyes0 said:
This man right here...listen to this man.
Click to expand...
Click to collapse
Good to see your still floating around the s3 threads which device are you using as of late
Sent from my SCH-I535 using XDA Free mobile app

MIKEYSAKZ said:
Good to see your still floating around the s3 threads which device are you using as of late
Sent from my SCH-I535 using XDA Free mobile app
Click to expand...
Click to collapse
I'm currently on the S5 as my daily driver but I bought an S3 again a few months ago as a backup phone/desk clock if something happens to my daily. It's really nice to see how far this device progressed over this time (it beat a Nexus as far as OS updates...namely Galaxy Nexus) so I just had to get it again after hearing it would get KitKat. From 4.0.4 all the way to 4.4.2 now. That is a beautiful thing to experience. :good: