yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S 4 Android Development] Surge1223:
This depends on whether or not you are able to root using saferoot or not (since its dependent on the get/put_user exploit) and whether your stock kernel was compiled with support for loading modules. You can check your kernel source config file to see.

After checking your kernel source you can create or compile modules from the source direcctory. You should probably know how to compile kernels before continuing but here are a couple things you should do anyways. In terminal emulator or with adb shell type:

Next, compile your kernel from source with its defconfig. After you have successfully compiled the kernel change the .config file to allow module loading and compile a module.

Or if compiling is not for you then just to test compile a module using memory data from the kallsyms file you made earlier if the source for the module requires it. And adb push-it to /data/local/tmp. Next:

Then youd have to follow the directions jeboo gives in the OP and patch compile bypasslkm making sure to change all address and settings to comply with the s3.
[AT&T Samsung Galaxy S 4 Android Development] the_mentor:
If you have the Verizon s3 with Android 4.3 it has a locked bootloader that won't allow you to flash any custom rom and I was hoping this can be useful.
[AT&T Samsung Galaxy S 4 Android Development] WordsworthESP:
This isn't ready, so no... it won't help. As stated, this thread is for devs to post. If they ever get it working, we'll know about it.

Sent from my Hyperdriven S4
[AT&T Samsung Galaxy S 4 Android Development] martinasa:
I have question where i have to put this commands ?

ON CMD or some program, cuz now i have i337 Rooted 4.3 with baseband 4.4.2 and the Wifi doesnet work.

Thanks !!!
[AT&T Samsung Galaxy S 4 Android Development] Bleedin_Sarge:
I am trying to play around with kexec, and dont mind having to odin stock ML2 if something blows chunks all over the system.

Can this be used against either MF3 or ML2. If it could be used against MF3, Its possible to boot 4.3 with the MF3 kernel, I think thats how I used saferoot to root 4.3.

So one could downgrade their kernel to MF3 and run this against the kernel to load kexec_load.ko in, and then work on kexec itself.

For those reading this: do not try this, I am only asking for information.

(: Sent from my sgh-i537 that thinks it is an i337 :)
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
This only works on MK2 kernel, not MF3. If kexec were developed it wouldn't matter what kernel it's loaded on since we'd load another over it.
[AT&T Samsung Galaxy S 4 Android Development] Bleedin_Sarge:
How hard would it be to build BypassLKM against MF3? Or is it out of the question? I am willing to do a little learning and some trial and error, now that I have another phone on the way.

(: Sent from my sgh-i537 that thinks it is an i337 :)
[AT&T Samsung Galaxy S 4 Android Development] DeadlySin9:
You'll have to look at the process stated in the OP to get the exploit and see if you can recreate those steps on MF3 I believe. Also, I believe you might need to find a method to write to the kernel memory to execute it.
[AT&T Samsung Galaxy S 4 Android Development] Bleedin_Sarge:
I was able to run the bypasslkm binary on MF3, and it said it was patched. But loading a module built for another 3.4.0 phone fails with LKMauth error.
[AT&T Samsung Galaxy S 4 Android Development] jeboo:
The MF3 kernel is vulnerable, but the patch address would have to be changed in bypasslkm.c and recompiled. I figured most people on MF3 have since upgraded to MK2. They're both vulnerable, rootable, etc..
[AT&T Samsung Galaxy S 4 Android Development] Bleedin_Sarge:
My method is downgrading from ML2 to MF3 for the exploit. Could you provide me with a version for MF3?
[AT&T Samsung Galaxy S 4 Android Development] Surge1223:
You should be able to follow the directions outlined in the OP and find the address to patch then simply change the address in bypasslkm.c before recompiling.
[AT&T Samsung Galaxy S 4 Android Development] 1nstak1ll:
Dead thread

Hate to revive an old thread, but this interests me. I know this is for Jellybean, but is there an updates for it? I'd be willing to help unlock the bootloader of my i537, and whoever wants to do this can get the 1k bounty..
[AT&T Samsung Galaxy S 4 Android Development] hubh98:
Can any senior help me compile a bypasslkm for sprint sph-l720T MK5? I have attached the boot.img.

It is only for ATT and vzw now.

Thank you a lot.
[AT&T Samsung Galaxy S 4 Android Development] hubh98:
An easy solution is to install a stock rom with SELinux permissive. I have installed the Tmobile rom from here with gsm unlocked on my sph-l720T.

http://xdaforums.com/galaxy-s4-sprint/general/l720-l720t-gsm-unlock-att-tm-t3189063

2.stock m919 rom (this is important for 4g/lte)

https://www.androidfilehost.com/?fid=23252070760975187

Everything works fine, wifi, gsm celluar.
[Moto X Q&A] ap3604:
I was about to order my moto x and I don't have one to compare against (all the stores I can get to only have woven black).

Which one has better fingerprint / smudge resistance?

- Woven Black

or

- Black
[Moto X Q&A] _MetalHead_:
I have woven black, it doesn't really get any smudges at all. The back always looks clean and fingerprint free. My Nexus 5 on the other hand is a damn smudge magnet.
[Moto X Q&A] Bradart:
I have a white one that I then converted to a black one which was later converted to a green one. No fingerprints or stains on any of them.
[Moto X Q&A] RyanTX:
I'd say woven would be better.

Moto X using Tapatalk
[Moto X Q&A] Russell Sprouts:
What difference does it make? Are you a professional cellphone photographer?

Only parts of the phone that fingerprints irritate me is on the camera lens cover and sometimes the screen. The Moto X's screen is pretty slick and smudge resistant. But I do find myself occasionally touching the rear lens cover when pulling the phone out of my pocket.

Wash your hands more often and your phone will stay cleaner and as a side benefit you won't get sick as often. :)

As far as a materials, I'm not impressed with the scratch resistance of the "soft matte" colors. The back of my navy AT&T model picked up some little nicks in short order. I just got a woven black T-Mobile version and I'm hoping it will be more durable. It has a similar soft feel, though, so I'm not so sure. Maybe the smooth finish colors are better.

Or perhaps this phone just wasn't meant to be set down on anything hard without a cover installed...
[Nexus 7 Q&A, Help & Troubleshooting] ichigo_kurosaki:
I purchased a 32GB 1st Generation Nexus 7 2 days ago. Upon purchase, i tested it on the store and it was already running Jellybean 4.3 and had a KitKat 4.4.2 ready to install. but i didn't flash it yet because i haven't paid for the item yet. i just tested itfor basic functions like if wifi works, charging works and stuff like that (i am quite experienced in android stuff, owning and having rooted an HTC Sensation XE, now running Team Venom's Vipers 5.0.0.:D but this ismy first tablet).:victory:

So upon getting home, i had the KitKat update installed. everything works fine, thankfully. no issues. Butone thing i noticed was, even when i had updated to kitkat, on my wallpapers, there is no KitKat wallpapers. Only those of Jellybean still. that's not a big problem though, but i just thought i might as well ask. because i was expecting wallpapers from settings will also be changed. is that normal?:confused:
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, ichigo_kurosaki...

Normal I think.

I've just checked my own 16Mb 'grouper' Nexus 7, having recently flashed the KK4.4.2 OTA update... and it also only has the old Jellybean wallpapers.

I have my own substantial collection of wallpapers, so it's not something I'd normally check for... preferring instead to use my own.

The KitKat wallpapers are readily available online... not that I much care for any of them. Too bright and white for my decidedly dark and stygian tastes:).

If you want them, just search for them in Google Images.

Rgrds,

Ged.
[Verizon Samsung Galaxy S 4] k1mu:
I posted this hoping it would become a sticky.

Moderators: any chance? Or is this unacceptable since it's not a question?
[Verizon Samsung Galaxy S 4] decaturbob:
this really needs to be a sticky as we all know how many aren't taking the time to more than a cursory check in these threads

---------- Post added at 06:16 AM ---------- Previous post was at 06:09 AM ----------

k1mu, I also created a step by step guide (with links) that walks you thru the entire process of going from ME7/MI1 to MJ7 by flashing the wipe tar image of MJ7, installing your saferoot, safestrap and HD11

http://xdaforums.com/showthread.php?t=2579278

I was feeling pretty bad for all the people that were messing up their phone becasue od not understanding the entire process.
[Verizon Samsung Galaxy S 4] tkacer:
Props to you both ! The only thing I would emphasize for MDK users is to get yourself educated (plenty of threads) on the Loki process. The proper use of it when flashing unfamiliar recoveries or kernels can save alot of headaches (trust me I know !!)
[Verizon Samsung Galaxy S 4] decaturbob:
Bumping
[Verizon Samsung Galaxy S 4] sixtythreechevy:
MJ7

Excuse my ignorance but I am running what I believe to be MDK but I updated my modem to MJ7 and now my baseband says MJ7. I have the latest TWRP installed. I am not running SafeStrap. Should this situation be noted in the thread?
[Verizon Samsung Galaxy S 4] joshm.1219:
nope updating modem changes what your baseband version says.
[Verizon Samsung Galaxy S 4] FernBch:
For those who are unsure if you can install the custom recovery:

The BUILD must be MDK not the MODEM. If you are running different build you can flash different modems. Just because you have the MDK modem does not mean you can flash a custom recovery.
[Verizon Samsung Galaxy S 4] thesoldier:
Yeah you can flash any baseband at any time you like...that's your radio/modem. You can also flash a new build as long as your bootloader remains on MDK. For example, I'm running a stock MJ7 ROM but I'm still Loki'd on the MDK bootloader.
[Verizon Samsung Galaxy S 4] FordNate:
ok heres my issue

Delete
[Verizon Samsung Galaxy S 4] k1mu:
What really matters here is what Bootloader you're running. Since updating the modem changes the Baseband string, that can't be used to tell if a phone is locked. I've updated the OP to say Bootloader version and to explain how to get to the Bootloader version.
[Verizon Samsung Galaxy S 4] tkacer:
Have you tried this: http://xdaforums.com/showthread.php?t=2301720
[Verizon Samsung Galaxy S 4] FordNate:
yes and got it running again with root:D
[Verizon Samsung Galaxy S 4] tkacer:
Happy 4 ya - nothing worse than a borked phone !!!!
[Verizon Samsung Galaxy S 4] dbinnc:
This I think has happened to me. I used Goo also. Now whenever I reboot it goes to the download screen. PITA. I am running build MK2. I am still unsure as to what I need to do to get back to a "before" state so I can do it properly?

ANy help appreciated.

THanks,

Derek

:crying:
[Verizon Samsung Galaxy S 4] k1mu:
Install the MK2 no-wipe from here.
[Verizon Samsung Galaxy S 4] decaturbob:
I want to bump this thread so we can use the OP as a starting point for a stickie guide concerning verizon S4 and what you need to know for modding your phone.

Naddict will be assisting in getting the sticky set up. This will be a WIP and will NOT be a thread to post questions. Lets get all our smart people contributing with info and links as needed to help all those who wish to mod their phone from not repeating all the same errors and bricking.
[Verizon Samsung Galaxy S 4] rolltide78:
Excellent! Thank you!
[Verizon Samsung Galaxy S 4] kerryh420:
Developers edition bootlader

Want to apologize up front if this is too off topic but it's kind of related to rooting. I have the Verizon Dev Ed and it arrived two weeks ago w MJ7 installed. within an hour of turing it on the phone starts OTA update to MK2. (yeah, i know. say it ain't so)

Now, both versions are BL locked on the NON-DE devices, but how does that work for DE? MY boot screen has a symbol of and "unlocked" padlock. I assume this indicates BL unlocked. My question/comment is this: If the BLis in fact, unlocked, then why can I not flash recovery? after scouring the websites I tried ADB. i figured this would be worth a shot as it does't use apps to "function". Reading here says Goo manager and other programs are a no go. THe only thing I have used any program w is Rom manager and that was to chose and install the recovery. Did not work. Tried flashing in odin- no dice.I have come across a DL copy of MK2 and that is flash-able and then root-able with safe root, but wth is up w the BL? Why can't I install and boot into recovery? Both CWM and TWRP recognize the device and install recoveries but they can't succeed getting into their respective recovery.

Can anyone shed some light on this or point me in the right direction? IF anyone want to know anything else about the Dev Ed I ll be happy to share whatever I can. Also, Anyone need a guinea pig try some of their stuff out (in exchange for helping educate me in the ways of the rom, of course). (I NEVER had this much trouble with DE Motorola devices)
[Verizon Samsung Galaxy S 4] Mightycaptain:
I'm pretty sure you'll need to root first. Also I'm not sure standard twrp is what you need for the Dev edition. They are lokied and I don't believe you have a need for that. That being sailing not exactly sure what your process for rooting will be or which recovery you need.

Maybe this thread will give you some insight.

http://xdaforums.com/showthread.php?t=2339849

Then research about flashing roms on the Dev. Edition. It will be different for you.
[Verizon Samsung Galaxy S 4] capo_kyle:
MK2 to MDK?

Hope this is appropriate post for this thread, in the theme of what's possible and what's not, is there a way to go from the MK2 bootloader to the MDK so that custom rom's can be installed "normally" like all other androids I've had? Haven't been able to find any threads that have this answer.
[Verizon Samsung Galaxy S 4] decaturbob:
Read the first post....

safestrap enabled, Hyperdrive driven
[Verizon Samsung Galaxy S 4] Mistertac:
Jeez huh
[Verizon Samsung Galaxy S 4] capo_kyle:
The thing is, I read the first post before I posted, and I also just re-read it several times; I don't see where it answers the question of whether you can safely flash the MDK if you're on the MK2 version. I see where it provides links for those who need to re-flash stock MDK but it doesn't clarify whether this could be flashed to replace MK2 and following the links are no bueno either. Thanks for any help that can be offered.
[Verizon Samsung Galaxy S 4] decaturbob:
You can not go back. ...your bootloader is locked.

safestrap enabled, Hyperdrive driven
[Verizon Samsung Galaxy S 4] k1mu:
fair enough.

I didn't think it necessary to repeat yet again that you can't downgrade. OK, I'll edit the OP.
[Verizon Samsung Galaxy S 4] lokerman:
I never knew one question could be repeated so many times. It reminds me of the car ride to California when I was 5 years old. Are we there yet?
[Verizon Samsung Galaxy S 4] Mistertac:
It is said way too much. Even worse is people still try to do it without searching around for the info first.
[Verizon Samsung Galaxy S 4] decaturbob:
5 minutes of looking at threads and some reading would prevent 95% of the issues....
[Verizon Samsung Galaxy S 4] stewdaddy123:
This is great info! Thanks. I have looked around quite a bit, and can't seem to find an answer to this question: What custom ROMs can be flashed on Samsung Galaxy S4 i545, Baseband=VRUEMK2, Kernel=3.4.0, Build=VRUEMK2?

I was able to do the recovery through SS and get Foxhound, but some features were not working and couldn't get Xposed to work properly. I tried Hyperdrive and it would not flash through SS. I'm just trying to find out what's possible regarding customs ROMs for this specific phone/model/build?
[Verizon Samsung Galaxy S 4] decaturbob:
no one ever has reported the inability to install hyperdrive thru ss, obviousl;y doing something wrong or have a bad download.

there are only a handful of roms out that work thru SS..HD is by far the most common one used. The Dev threads shows what other roms are ss compatible....
[Verizon Samsung Galaxy S 4] stewdaddy123:
You're right, it was me. I figured it out. Thanks
[Verizon Samsung Galaxy S 4] k1mu:
You should browse the Android Development forums for Safestrap compatible ROMs.

As far as Hyperdrive goes: you need to make sure that you use the current version of SS for MK2, and flash the *safestrap* copy of Hyperdrive.

The links are a bit confusing (my first download was of the non-Safestrap version, which didn't work, of course.)
[Verizon Samsung Galaxy S 4] stewdaddy123:
Yes, that was the issue, after doing a little more research, I noticed there are 2 different downloads within the thread. I had to go back and download the Hyperdrive RLS12 "SafeStrap" version and everything worked fine.
[Verizon Samsung Galaxy S 4] towelboy:
wheww, this thread saved me from frying my phone. thanks k1mu! :victory:
[Verizon Samsung Galaxy S 4] decaturbob:
many guides and threads that everyone needs to read to understand the process of what they are getting into before they brick their phone and it costs themselves some money.
[Verizon Samsung Galaxy S 4] Mistertac:
The Bieeeeb has been getting into a lot of trouble lately, not easy I'm sure to keep up on this android stuff while racing Lambos high and drunk.
[Verizon Samsung Galaxy S 4] NoSauce:
Some clarification on OP for those with Dev Edition and more What’s possible Q's

Thank you, to k1mu and other contributors. It was an excellent idea especially for those starting out. I’ve found a couple of threads dedicated to the dev. edition but it

I have the Galaxy S4 (SCH-I545) - Verizon, Developer Edition.

Build number:

JDQ39.I545OYUAMDK

Baseband version: I545OYUAMDK

Android Version 4.2.2

The OP stresses the importance of being mindful of your firmware version when following threads/guides so as not to brick one’s phone. I understand that shorthands like “MDK” are commonly used, but I’m not sure if these shorthands necessarily have wider implications of “any build number ending in MDK”. I’m not sure if all firmwares ending in “MDK” may be treated the same or if it refers specifically to the seemingly more popular VRUAMDK version. I couldn’t help but notice that mine says “OY” instead of “VR” (maybe it’s a dev. edition thing).

[ANSWERED] 1. Is this something I need to be concerned about? That is, is it okay to follow threads/guides for “MDK” just the same as if I have VRUAMDK? When people say MDK does it encompass all firmware that ends in MDK?

"The DevS4 came originally with I545OYUAMDK. The retail S4 came with I545VRUAMDK. The only difference is that the DevS4 has a different ABOOT partition which allows for the unlocking." "The DevS4's are now sold with I545OYUEMJ7"

- So apparently the OY means that the bootloaders are unlockable (Dev. edition). This will be irreversibly be changed with firmware update (can no longer be unlocked).

2. Should I also be wary of the first part of the Build number/firmware? JDQ39. ? Is it safe to follow directions with different numbers (first part)? While I’m at it, how about the Android Version is that important when it comes to do’s and don’t’s and not bricking my phone?

[answered] 3. Is there a way to turn off over-the-air (OTA) updates? I felt like this question was relevant to this thread as it can change firmware versions which has implications for what’s possible and what is not.

- "If you get a file explorer like Root Explorer, you can rename the sdm.apk to sdm.apk.bak and it should stop it."

4. I haven’t activated my phone yet. Does it matter if I unlock/root my phone before or after activating service?

I just want some confirmation/verification on these things so I don’t brick my phone. Also, I’m more familiar with using custom recovery/TWRP from my other android device whereas I’ve never heard of SS. The OP is pretty clear that firmware updates are irreversible. As such, it would be nice to know how to retain my ghetto, less up-to-date firmware.

I would much appreciate it if the more knowledgeable folks on this forum would chime in. In the meantime I’ll do more searching and sifting through threads. I’ll post/update if and when I find answers. Hopefully, it would be of use to others out there with dev. edition.

eternally grateful,

ns
[Verizon Samsung Galaxy S 4] k1mu:
The developer edition is a different animal. You can't take OTA updates, but if you're not careful, you can end up with a locked bootloader due to trying to flash non-developer stock software. You're sort of stuck on MDK if you want stock software, but you can flash a whole lot more ROMs than anyone else.
[Verizon Samsung Galaxy S 4] goast:
Hi guys OK I'm rooting my friends phone Verizon s4 with mk2 .. So I know that I can only use safe root to gain root access .. Since its not my phone I didn't want to go the safe strap method..my question is will closed frame work run correctly still? And what can be removed bloatware wise that won't harm the phone? Thank u in advance
[Verizon Samsung Galaxy S 4] k1mu:
Updated the OP with pointers to tools to tell the bootloader version and to mention the developer edition.
[Verizon Samsung Galaxy S 4] seadooman:
Backing up with TWRP or CWM

Once rooted can the stock MK2 ROM be backed up like normal and reinstalled because its not a custom ROM or am I completely locked into doing the ODIN Recovery. I looked and cannot seem to find an answer for this.
[Verizon Samsung Galaxy S 4] decaturbob:
what are u going to back it up with?
[Verizon Samsung Galaxy S 4] seadooman:
On my Samsung tablet I have used cwm but since this phone has a locked boot loader I am assuming I can't back it up before I start to modify anything.
[Verizon Samsung Galaxy S 4] decaturbob:
Safestrap allows back ups
[Verizon Samsung Galaxy S 4] k1mu:
As decaturbob said, you can install Safestrap recovery and back it up using that. Then, if you need to, you can re-flash to stock using ODIN, re-root, install Safestrap, then restore the backup. It may be easier, however, to restore apps using something like Titanium Backup.
[Verizon Samsung Galaxy S 4] seadooman:
If I use safe strap is there any chance that I could trigger knox?
[Verizon Samsung Galaxy S 4] k1mu:
Using Safestrap won't set the Knox Warranty Void flag. However, you need to understand what DOES set the flag: attempting to flash either an unsigned kernel or recovery, or flashing an older recovery.

So, if you root with Saferoot, then install Rom Manager and try to flash CWM on a Knox-enabled device, that will probably trip the Knox Warranty Void flag. That's not Saferoot's fault.

If you install Safestrap on MK2 and try to use it to restore a MDK nandroid backup, it'll also probably trip the flag. That's not Safestrap's fault.

I say "probably" above because I think in both of these cases, the flash will fail but not set the flag. It appears that only using ODIN to try to flash unapproved firmware actually trips the flag. However, I'm not going to experiment with my phone. :)

You have to be aware of what can and can't be done. There's a lot of misinformation and incomplete information out there, particularly you tube videos explaining how to install CWM on a "Galaxy S4" that NEVER mention that it's an unlocked Sprint phone. Or that it only works on MDK bootloaders. There's rooting techniques here on XDA for MDK that say "Not for ME7" when they should say "Not for anything past MDK". So, it's kind of a minefield. Read, learn, and be careful what you do. At the very least, you're risking a soft brick by messing about too much.
[Verizon Samsung Galaxy S 4] seadooman:
[B I really don't need to install a different ROM at this time but I am wanting to remove some of the Bloat, Seems safe to say If I "screw up" I can use ODIN and reinstall the OEM MK2 and be safe?

Thanks for all your help.
[Verizon Samsung Galaxy S 4] k1mu:
Yup, there's always the stock ROM to recover from if you mistakenly remove too much.