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.
Related
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.
If I'm not big on flashing roms at the moment, is there any good reason to unlock the bootloader? The only benefit I've read so far is that booting up is a bit faster.
Also, seeing as how rooting and unrooting is pretty easy without the use of odin/flashing, is there a way to re-lock the bootloader without odin (in case an OTA update comes along the way)?
Any OTAs that come along are likely to break the insecure bootloader.
If you ever intend to use custom ROMs I would suggest not accepting any OTAs regardless.
Download ez unlock from the market to lock and re-lock.
dunderball said:
If I'm not big on flashing roms at the moment, is there any good reason to unlock the bootloader? The only benefit I've read so far is that booting up is a bit faster.
Also, seeing as how rooting and unrooting is pretty easy without the use of odin/flashing, is there a way to re-lock the bootloader without odin (in case an OTA update comes along the way)?
Click to expand...
Click to collapse
To answer your question, there is no reason unless you want to flash a ROM with a custom kernel (eg CM or AOKP).
You can backup your bootloader and restore using terminal / dd, and I think some of 'one click' tools also are doing this now sounds like.
Sent from my Galaxy S3
So bootloader needs to be unlock more for kernel, right?
Sent from my SCH-I535 using Tapatalk 2
From here on out, i would think that 90% of kernel and rom development will be aimed towards unlocked bootloaders.
download app from market to unlock. One click. Easy!
Sent from my SCH-I535 using Tapatalk 2
djisia87 said:
download app from market to unlock. One click. Easy!
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
It even says "that was easy" lol
that was easy
If for no other reason but to tell Verizon FU Icehole's.
Power to the People.:highfive:
ImgBurn said:
If for no other reason but to tell Verizon FU Icehole's.
Power to the People.:highfive:
Click to expand...
Click to collapse
This.
Sent from my SCH-I535 using xda premium
ExodusC said:
Any OTAs that come along are likely to break the insecure bootloader.
If you ever intend to use custom ROMs I would suggest not accepting any OTAs regardless.
Click to expand...
Click to collapse
Wouldn't a person be able to Odin the stock .tar that we have now to overwrite any **** Verizon tries to push on us?
Sent from my SCH-I535 using Tapatalk 2
pyrostic said:
Wouldn't a person be able to Odin the stock .tar that we have now to overwrite any **** Verizon tries to push on us?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Where is this .tar located?
You have to unlock the bootloader to change boot images... right?
So my last s3 stopped working and I got a new one sent via my extended warranty. Previously I had an unlocked bootloader and root running gummy 4.4 which was awesome! My new phone came stock with 4.3 touchwiz which I am reading might be bad news. So here are my questions:
1) Is there really no way to unlock the bootloader on 4.3?
2) What are my alternatives to installing custom roms?
3) Is safestrap a stable/safe option even though its in beta?
4) Can safestrap be reversed if a method for unlocking the bootloader is revealed?
5) Where can I find a rooting tutorial for 4.3? Can I lose root easily/ corrupt my phone if a Samsung update is applied?
6) Should I wait for a downgrade option? Slash is it supposedly possible (twitter update)?
jl2222 said:
So my last s3 stopped working and I got a new one sent via my extended warranty. Previously I had an unlocked bootloader and root running gummy 4.4 which was awesome! My new phone came stock with 4.3 touchwiz which I am reading might be bad news. So here are my questions:
1) Is there really no way to unlock the bootloader on 4.3?
Click to expand...
Click to collapse
Nope.
2) What are my alternatives to installing custom roms?
Click to expand...
Click to collapse
As of this minute, one option: Saferoot then Safestrap.
3) Is safestrap a stable/safe option even though its in beta?
Click to expand...
Click to collapse
Yup. Read the replies in Safestrap if you need reassurance.
4) Can safestrap be reversed if a method for unlocking the bootloader is revealed?
Click to expand...
Click to collapse
Yup, you could even Odin flash VRUCML1 4.3 tar and be back to "normal" again. However, don't count on the 4.3 bootloader being unlocked. There's no guarantee anyone is even utilizing their time to find an exploit and its entirely possible no one is.
5) Where can I find a rooting tutorial for 4.3? Can I lose root easily/ corrupt my phone if a Samsung update is applied?
Click to expand...
Click to collapse
Read me. Use Saferoot, then SafeStrap. Yes, much worse could happen in a future update as well.
6) Should I wait for a downgrade option? Slash is it supposedly possible (twitter update)?
Click to expand...
Click to collapse
That's your call. It's possible, but whether it comes to fruition is entirely different.
Will xposed module work using safestrap safe ROM? Gotta get my greenify experimental features back! And keep chat!
Sent from my SCH-I535 using xda app-developers app
jl2222 said:
Will xposed module work using safestrap safe ROM? Gotta get my greenify experimental features back! And keep chat!
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
They should
Sent from my SCH-I535 using Tapatalk 4
SlimSnoopOS said:
They should
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
Im in the same situation as OP.. Xposed works. I'm on alliance 23.
I was wondering can we flash custom kernels then flash the dependencies or are we stuck with the safestrap kernel?
Sent from my SCH-I535 using Tapatalk
omair2005 said:
Im in the same situation as OP.. Xposed works. I'm on alliance 23.
I was wondering can we flash custom kernels then flash the dependencies or are we stuck with the safestrap kernel?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I think flashing a custom kernel isn't suggested with SafeStrap. I don't know the specifics, maybe @BadUsername or someone else can expand on that? I thought I read that you are still running the stock kernel even if you flash a custom kernel when using SafeStrap. Someone was discussing this before but it was not explicitly proven they were in fact running the custom kernel.
omair2005 said:
Im in the same situation as OP.. Xposed works. I'm on alliance 23.
I was wondering can we flash custom kernels then flash the dependencies or are we stuck with the safestrap kernel?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Good deal! Glad xposed works. How you liking alliance by the way? I'm torn between that and clean rom. I'm actually not the most familiar with TW roms currently. Before this replacement phone I was all ASOP.
Sent from my SCH-I535 using xda app-developers app
jl2222 said:
Good deal! Glad xposed works. How you liking alliance by the way? I'm torn between that and clean rom. I'm actually not the most familiar with TW roms currently. Before this replacement phone I was all ASOP.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I've come to the conclusion I want to use my partitions to the full capacity so I'm sticking with stock rom + xposed for any modifications I need..
Yeah same here, I was AOSP for awhile soon as I discovered Quantum Kernels..
omair2005 said:
I've come to the conclusion I want to use my partitions to the full capacity so I'm sticking with stock rom + xposed for any modifications I need..
Yeah same here, I was AOSP for awhile soon as I discovered Quantum Kernels..
Click to expand...
Click to collapse
Quantum Kernels huh. Not familiar with those kernels. Ill have to check them out. I would use the stock rom as well Im just worried about a random automatic update that would kill root and make my replacement phone even more useless than it already is without an unlocked bootloader. Do you know if there a way to disable the Samsung update center on the stock rom using root?
jl2222 said:
Quantum Kernels huh. Not familiar with those kernels. Ill have to check them out. I would use the stock rom as well Im just worried about a random automatic update that would kill root and make my replacement phone even more useless than it already is without an unlocked bootloader. Do you know if there a way to disable the Samsung update center on the stock rom using root?
Click to expand...
Click to collapse
Use TiBu and freeze SDM, FWupgrade
Disclaimer: rooting your phone entails risk. You may brick it, cause it to catch fire, cause it to form the first node in the Skynet network, or otherwise render it inoperable.
Step 1: flash ML1_KERNEL.tar via ODIN.
Step 2: get saferoot from here.
direct download
Step 3: Unzip the saferoot.zip
You should have the following when done:
- a file called "install.bat"
- a file called "install.sh"
- a folder called "files"
Step 4 - Root your phone
Double click on the "install.bat" to run the root. It will root and reboot your phone. Once that's done, you're rooted!
Step 5: flash back NC1_KERNEL.tar via ODIN.
Now after you got root what to do! Check this usefull thread http://forum.xda-developers.com/showthread.php?t=2653902
Thanks to:
K1mu for saferoot.
me.
Thank you for this guide. It worked great. However, Wifi will not turn on now. Data works fine but no wifi. Usually I can find any information I need to fix a problem, but in this case I have been unsuccessful. So I am posting my very first reply. Any ideas of what happened? Or a way to fix?
JimmySiegel said:
Thank you for this guide. It worked great. However, Wifi will not turn on now. Data works fine but no wifi. Usually I can find any information I need to fix a problem, but in this case I have been unsuccessful. So I am posting my very first reply. Any ideas of what happened? Or a way to fix?
Click to expand...
Click to collapse
What you did to get wifi not turn on?
try flash full rom again may help you.
If you can install safestrap and flash wifi modules may this work.
I forgot to mention that I stupidly tried to use EZ-Unlock knowing full well that the bootloader wouldn't unlock. Which resulted in a hard brick. I got out of that using a debrick SD card boot luckily. I planned on flashing with Odin again but thought I would ask first. Should I flash everything or just the WiFi modules?
Sent from my Nexus 7 using XDA Premium HD app
JimmySiegel said:
I forgot to mention that I stupidly tried to use EZ-Unlock knowing full well that the bootloader wouldn't unlock. Which resulted in a hard brick. I got out of that using a debrick SD card boot luckily. I planned on flashing with Odin again but thought I would ask first. Should I flash everything or just the WiFi modules?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Flash full stock rom, that happend to me once.
mohammad.afaneh said:
Flash full stock rom, that happend to me once.
Click to expand...
Click to collapse
I flashed the full ML1 rom and then re-rooted with saferoot again. Everything is working perfectly now. Thank you for your help
question..
I got this, Thank yoU! The instructions are very good!
Now the question I have is once I'm rooted can I install TWRP and roms?
Thanks for helping out a novice...
cowboysdude said:
I got this, Thank yoU! The instructions are very good!
Now the question I have is once I'm rooted can I install TWRP and roms?
Thanks for helping out a novice...
Click to expand...
Click to collapse
No dont try you will brick your device.
you can install safestrap and install stock 4.3 only as second and third rom.
Ckeck the thread linked in OP.
mohammad.afaneh said:
No dont try you will brick your device.
you can install safestrap and install stock 4.3 only as second and third rom.
Ckeck the thread linked in OP.
Click to expand...
Click to collapse
Gotcha!! Huge Thanks!! Will do that!!!
I'm reading ... what version of safestrap would I use?
Thanks
cowboysdude said:
Gotcha!! Huge Thanks!! Will do that!!!
I'm reading ... what version of safestrap would I use?
Thanks
Click to expand...
Click to collapse
There is one version, 3.71.
mohammad.afaneh said:
There is one version, 3.71.
Click to expand...
Click to collapse
Thank you, very
This works great! But can we custom recovery like twrp or clockwork?
Sent from my SCH-I535 using Tapatalk
theviper90210 said:
This works great! But can we custom recovery like twrp or clockwork?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Read the previous page
Sent from the Shark Tank using XDA Premium 4 mobile app
Read right over that lol, thanks safestrap it is
Sent from my SCH-I535 using Tapatalk
theviper90210 said:
Read right over that lol, thanks safestrap it is
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
No problem. Be sure to read the safestrap thread carefully. Especially the part about having to flash the kernel module each and every time you flash a ROM in order to have working Wi-Fi. Here is a thread that has a list of safestrap compatible ROMs:
http://forum.xda-developers.com/showthread.php?t=2653902
[INDEX] TW 4.3 Download List (5-24-14)
Sent from the Shark Tank using XDA Premium 4 mobile app
I assume u would use the nc1 kernel if were on the nc1
Sent from my SCH-I535 using Tapatalk
landshark68 said:
No problem. Be sure to read the safestrap thread carefully. Especially the part about having to flash the kernel module each and every time you flash a ROM in order to have working Wi-Fi. Here is a thread that has a list of safestrap compatible ROMs:
Click to expand...
Click to collapse
Does anyone know of NC1 modules? I can only find ML1, and they don't work. I've tried flashing them twice on CleanROM 8.2, and still have no WiFi. Battery life on stock is KILLING ME, so I would really like to get this working.
elempoimen said:
Does anyone know of NC1 modules? I can only find ML1, and they don't work. I've tried flashing them twice on CleanROM 8.2, and still have no WiFi. Battery life on stock is KILLING ME, so I would really like to get this working.
Click to expand...
Click to collapse
I don't think there is an NC1 kernel module yet. If there were one, I would assume it would be in the OP of the safestrap thread.
Sent from the Shark Tank using XDA Premium 4 mobile app
elempoimen said:
Does anyone know of NC1 modules? I can only find ML1, and they don't work. I've tried flashing them twice on CleanROM 8.2, and still have no WiFi. Battery life on stock is KILLING ME, so I would really like to get this working.
Click to expand...
Click to collapse
I can compile the nc1 kernel but I cant test it as bootloader locked.
If I have the time will try to compile and take the modules, will download clean rom first hope my net connection still alive
could you not just flash the NC1 Kernel from the OP FIX, the one we flash back to the phone after rooting?
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: