yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] ryanbg:
The USB D+/D- (Data in/Data out) pins turn into UART/Serial lines when there's a certain level of resistance between the GND (Ground) ID (Identification). There's also a Vcc line that provides 5v of voltage. So in a USB plug, there's D+,D-,GND,ID, and VCC (Not in correct order, but those five.) Pick up a regular-sized USB cable and look inside the plug, you'll see those 4/5 pads on it (sometimes ID is omitted, not sure if that's entirely accurate.) The serial line will allow you to see the kernel/system messages. So instead of having to look at the log on your device via ADB or on the device itself, you can see live messages when the kernel crashes, and see why. This is helpful for debugging things like kexec, so you can see what happens when something goes wrong, without losing a connection until the device actually powers off. I hope that made sense.

I don't think this will do what you might think it will, it won't help you run any ROMs or custom kernels, but it'll help get kexec working. I think kexec is really the best option, and can provide a great opportunity to learn for those of you at that level. From this point on from a research perspective, you would really need C and Linux Kernel experience and general embedded device knowledge to contribute. I'm very busy and I only do this as a hobby so the more help the better, but only if capable.
[Verizon Samsung Galaxy S 4] Surge1223:
^this
[Verizon Samsung Galaxy S 4] vt0r:
^that
[Verizon Samsung Galaxy S 4] hisham2630:
not a joke.

i get another boot mode called (bootloader panic mode!)...in the middle of screen.

there was details on top left of screen...details like when you reboot into download mode.

i can't remember how is that happen but it stays at this mode for about 10 seconds then reboot.
[Verizon Samsung Galaxy S 4] dmt010:
Yes I've posted images of this mode already. And you likely attempted to load a camera firmware driver which caused the kernel to panic because you wrote random data to the device which wasn't an actual driver. Essentially long story short, your phone bsod'd
[Verizon Samsung Galaxy S 4] vt0r:
https://en.m.wikipedia.org/wiki/Kernel_panic

The BSOD analogy is a pretty good one here. The first time, you either wrote a value to that sysctl that was out of range or simply invalid where there's no validation or error checking, hence the panic.

It's not some secret mode or something useful - just a fatal error state. I'd stop trying to write insane values to random hardware if I were you, because you'd probably be pretty sad if it worked and damaged some hardware component(s) instead of just causing a kernel panic.
[Verizon Samsung Galaxy S 4] dmt010:
Yeah I read up on this a bit @ work today. It's related to the flash on the rear facing camera. I'd strongly suggest not tinkering with any block devices / character devices/ etc if you don't know what you're doing. Chances are it crashed from exactly what previous nerd said.

If you end up finding the hidden kernel Sanders mode please let us know. Lunch time.
[Verizon Samsung Galaxy S 4] traco1:
Knox

I decided to uninstall a bunch of bloatware on my phone & the app actually led me to the knox apps listed in the system Curious as to , If I uninstall the Knox apps/files will it ;

#1 trip Knox

#2 ruin my phone

#3 allow me to unlock my boot-loader

#4 make phone totally useless

What u think?
[Verizon Samsung Galaxy S 4] ryanbg:
No to all of those. It seems like that would be way too simple to uninstall an APK and have the bootloader unlocked. This post is also extremely off-topic.

EDIT: It would be appreciated if posts were limited to people only contributing something they know as fact (and actually relevant to what we're working on.) Speculation and guessing are not conducive to this thread. Basically, if you don't know what you're talking about, have evidence to prove a relevant fact, or are just going to suggest something that is obviously too simple or won't work we ask that you withhold from posting. It's discouraging to come back here and have to sort through posts of "Can't we just resign the bootloader?" or "We should use this TZ exploit" or "Can't we just do blah to blah." We ask that only those who can contribute with knowledge post here. No ETAs, no obviously incorrect suggestions, nada. Otherwise we won't be able to stick around any more. Heed my warning.

I also respectfully ask that if a moderator were to see this post, that they do a quick cleaning and provide swift justice for those who continue to post off-topic or redundant posts. Thank you.
[Verizon Samsung Galaxy S 4] kcarden:
Only risk youd run is tripping Knox. I'd disable instead of uninstalling. Possibly soft brick or bootloop but that's obvious when messing with /system
[Verizon Samsung Galaxy S 4] doubleaykay:
Any updates, folks? Looks like we've hit a lull in the thread and it would be great if someone could update us!
[Verizon Samsung Galaxy S 4] eikoo:
The phone is dead. Best you can hope for is cm13 on an mdk
[Verizon Samsung Galaxy S 4] KaHOnas:
I assume you mean that there is no more development being done and any S4s that have been waiting for a bootloader unlock should just hang up the proverbial hat.

Sent from my rooted but bootloader locked MK2 Galaxy S4
[Verizon Samsung Galaxy S 4] doubleaykay:
I think there is more development being done... this is XDA, I would expect no less. Even if it's just kexec, it's progress. [MENTION=5638731]KaHOnas[/MENTION]
[Verizon Samsung Galaxy S 4] staTrill:
I sure hope so. This is my first post; I have been lurking this thread for nearly a month now and just want it to be made public that there are plenty of us anxiously watching from the sidelines for a solution.

Seriously, don't give up on us guys! There are too many of us stuck with this phone for whatever reason.

-Stat (vzw S4 #DMI1)
[Verizon Samsung Galaxy S 4] Navydoc201:
I've been watching for a while also. My problem is that I'm on the OF1 build...
[Verizon Samsung Galaxy S 4] tshelby73:
When I was on the droid x2 once the devs left it's over. That device is still locked. I foresee the same for this device. Should have learned my lesson back then but didn't do my research correctly on the different variants of s4.

Sent from S4 using the better than it was then they jacked it again Tapatalk
[Verizon Samsung Galaxy S 4] mbabich17:
You probably should keep stuff like this to yourself. It's not development related at all, and I think it's very disrespectful to devs who are or were working on this. On a separate note I was reading up on how Samsung unbricks a phone with the knox fuse blown by changing the result of the hash to account for the blown fuse rather than generating a new one. Does this still require the private key? And if not is it possible to modify the process to change what value is read from the qfuses?
[Verizon Samsung Galaxy S 4] tshelby73:
No more Devs left for the Verizon s4 anymore ....:'( sad sad day.

Quote from a dev in actual dev forum.

Sent from S4 using the better than it was then they jacked it again Tapatalk
[Verizon Samsung Galaxy S 4] gadget!:
There are still devs working on the S4, don't believe everything you read.

sent from a Galaxy far far away.
[Verizon Samsung Galaxy S 4] EdrickMG:
Wow reading this gave me hope!! http://www.xda-developers.com/veriz...gn=Feed:+xda-developers/ShsH+(xda-developers)
[Verizon Samsung Galaxy S 4] doubleaykay:
Gues, the Verizon S5 bootloader has been unlocked, seen in this link that [MENTION=5969908]EdrickMG[/MENTION] kindly provided: http://www.xda-developers.com/veriz...gn=Feed:+xda-developers/ShsH+(xda-developers)

Can this be applied to the S4 -- even if we need to modify it? If not, can we use the same method used to achieve this to make an unlock for our S4?
[Verizon Samsung Galaxy S 4] TheLoonyRebel:
I've been wondering this same thing myself since the news hit XDA over this. I am hoping this can lead us to some kind of method to getting our S4's off of purgatory island same with Verizon Note 2's on 4.4.2 ND7 as well.
[Verizon Samsung Galaxy S 4] stang5litre:
[MENTION=4390046]tshelby73[/MENTION] not all devs are labeled as devs[emoji6] [emoji39] [emoji48]

I build s4 Roms
[Verizon Samsung Galaxy S 4] blackops11252:
In the words of my granddaughters favorite movie Frozen "Let it go, just let go!"
[Verizon Samsung Galaxy S 4] jose_mdzg:
Guys, the verizon s4 lollipop of1 root is almost ready, two days ago in kingroot's app there was a "root strategy available" for the s4 of1...it said it had a success rate of a half star of three...but the root didn't worked for me, so today i got an root exeption from the kingroot app (the root didn't work either)...so maybe in a few days we will finally have s4 lollipop of1 root....the're devs working on the root so dont lose hope ;)
[Verizon Samsung Galaxy S 4] XxD34THxX:
This is not the thread for root.

As for the exploit. If it really uses the former methods.... And someone adapts it for the s4... 90% chance I'm going to a nexus device tomorrow....

I digress

What I mean to say is, if the s5 has been unlocked, and it seems like a full unlock rather than loki, then WOW
[Verizon Samsung Galaxy S 4] PalmCentro:
Developer has no intention to release the method as of now

http://xdaforums.com/showpost.php?p=63830020&postcount=15
[Verizon Samsung Galaxy S 4] XxD34THxX:
well crap...
[Verizon Samsung Galaxy S 4] EdrickMG:
Beatup it's too smart, I bet he will eventually but for now is doing a checkmate move... Imagine the hundred of people asking for ETA and screw it up... I have seen it in mods... If not... Well at least we know for sure it can be done
[Verizon Samsung Galaxy S 4] XxD34THxX:
Either that or some Legal Issue we do not know about..
[Verizon Samsung Galaxy S 4] npjohnson:
^this.

As I mentioned. If it is a leaked aboot he is using, or a zeroday TZ Flaw, this won't see release for a long time/ever.
[Verizon Samsung Galaxy S 4] scottsdca:
Post it anonymously...
[Verizon Samsung Galaxy S 4] npjohnson:
That isn't how these things work. A leaked firmware that affects one device? Sure. You'll be scolded, and potentially sued.

But releasing an Internal Bootloader, or one that you signed with a Leaked RSA key? Yeah. Good luck on court. No matter that anonymity, they'll track you down.
[Verizon Samsung Galaxy S 4] skepticmisfit:
http://xdaforums.com/showpost.php?p=63911154&postcount=85
[Verizon Samsung Galaxy S 4] XxD34THxX:
So basically.... the s5 HAS a way out... somehow... Just not through that method that beaups found..

I digress
[Verizon Samsung Galaxy S 4] RuggedHunter:
So... This guy in a note 3 thread posted a video of himself downgrading from 5.0 to 4.2.2 in THIS THREAD and a few posts afterwards uploaded the files.

Not sure if it's relevant or not, but worthy to bump the thread.
[Verizon Samsung Galaxy S 4] XxD34THxX:
Unless we/he/someone can modify his method for us... He seems to be having trouble with the modem.. I assume the s4 does not have to worry about that problem as flashing modems does not brick/affect the device in any unintended way. That said, it is centered around knox and an efuse on that device. The problem is with the s4, we have to worry about a physical qfuse...

I'm gonna stop here since I'm dead tired... and I have nothing else more to say...
[Verizon Samsung Galaxy S 4] npjohnson:
Well. Sort of. Our rollback counter isn't a QFUSE, its called RPMB, and its a protected eMMC drive, not writable. The Note 3 however, uses a QFUSE. This isn't complicated to do. We can downgrade from a "version" of 5.0.1 to 4.3.

To do this you need to be on a KitKat or JB Bootloader, and just have upgraded your system, modem, boot, etc. Then you could Odin to whatever your bootloader version is.
[Verizon Samsung Galaxy S 4] XxD34THxX:
So I've been living through a lie...

jk

That helps clear my perception, thanks.
[Verizon Samsung Galaxy S 4] G.moe:
Looks like he posts a similar file for the i9505 later in that thread.
[Verizon Samsung Galaxy S 4] doubleaykay:
Is there a separate thread for the kexec development, or are there any updates on it? And any updates on this?
[Verizon Samsung Galaxy S 4] RuggedHunter:
If you search for "surge1223 kexec" you'll find a handful of relevant threads.

Sent from my g928c
[Verizon Samsung Galaxy S 4] ryanbg:
S4 does not utilize RPMB partition even though it's provisioned for it.
[Verizon Samsung Galaxy S 4] npjohnson:
Really? Huh. My mistake.
[Verizon Samsung Galaxy S 4] ryanbg:
No worries! If you take a look at aboot in a disassembler, you'll see the references to the RPMB stuff are not referenced by any functions. Just left over junk unfortunately.
[Verizon Samsung Galaxy S 4] Surge1223:
Yep, can confirm
[Verizon Samsung Galaxy S 4] linuxxnut:
Fused value

How exactly do the fused values work. When a rom is flashed to the device does it write the value to the counter. If so would it be possible to modify the value being written for example modifying an me7 image to set the counter back to 1 then flash the mdk image. I have some coding experience but this stuff is all pretty foreign to me sorry if this is a stupid suggestion.
[Verizon Samsung Galaxy S 4] Legitsu:
fuses are just that physical fuses.... there is no way to unset them ...
[Verizon Samsung Galaxy S 4] Cobaltikus:
I think of the fuses as set-only bits, that start out as 0's, and you can set them individually to 1's, but once they are set to 1 they can never go back to 0. At least that is the idea. I find it difficult to believe any statement that contains the word "never". Each upgrade has a maximum value it will allow for these fuses. So if version 2 sets a new bit fuse that wasn't previously set, version 1 will no longer be allowed. However, even if these fuses cannot be physically unset in the hardware, it's still software that controls the logic about not allowing older versions to run, and it's the software we are trying to exploit, so that the software will simply ignore the fuses and allow anything, or so that we can trick the software into thinking a fuse isn't set when it really is.

This is how I think of it. Feel free to correct me if I'm wrong.
[Verizon Samsung Galaxy S 4] vt0r:
You're better off thinking of qfuses as... well... fuses. A fuse (electrical) is essentially just a conductive link that breaks when a surge of power over its rated max capacity is sent to it. The common Qualcomm implementation involves actual hardware fuses in the CPU itself that get blown during upgrades, etc. Since these are actual physical connections that are severed, there is no going back once they get blown, outside of some magical, microscopic CPU surgery.

As far as the software issue, that brings us back to square one, as we now need to circumvent the integrity checks to make your custom software boot, assuming you would just replace a BL chain component.

This is the part everyone has been working on all this time.
[Verizon Samsung Galaxy S 4] ryanbg:
This. It's a permanent chemical reaction at a microscopic level.
[Verizon Samsung Galaxy S 4] XxD34THxX:
Why even go to these lengths... Argh

/rant before it gets to large.
[Verizon Samsung Galaxy S 4] LupineDream:
I was working on the Straight Talk S4 SM-S975L ATT variant and blew my qfuse (Warranty void) after hex editing :( But not before I gained root on the device, breaking Wi-Fi. Time to trash this device and find one without a blown qfuse. These hardware fuses are innately frustrating. I practically threw the thing across the room when I saw warranty void, because at that point flashing another aboot was impossible.

Strange thing....on my device I was able to downgrade the kernel from OF4 to NB1 via a simple hex edit to the build number. But I broke the qfuse...from not correctly signing it. I did not see this thread. I've failed. :'(
[Verizon Samsung Galaxy S 4] Legitsu:
kernel downgrading you can always do its the aboot partition checks are what matters
[Verizon Samsung Galaxy S 4] LupineDream:
Yes well, as I posted in the other thread...wait...holy hell...someone got jailed for hacking the bootloader? Or was that just a hoax?

Aside, I myself am boycotting SAMSUNG products. I can choose where to put my money, and its definitely not going to be in SAMSUNG's mouth. These Verizon variants ticked me off to a point that when all of my SAMSUNG devices finally kick the bucket, I'm switching. Developers improve upon softwares, not degrade or deface them. We add more efficient kernels and bring more life to a stock bloated phone than thought possible, add new software that increases performance and keeps the phone (and the visible brand name) in the hands of the user for all to see. I feel that these new security measures for consumer devices are beyond wrong. All I wanted to do personally was theme my phone to make it look boos, but seriously if someone did indeed get jailed over this, that'll be it. For wanting to theme out and improve buggy software?

Bye SAMSUNG, you lost my business.
[Verizon Samsung Galaxy S 4] npjohnson:
Uh. Did it boot after hex edit? It shouldn't.

Blowing the Warranty Bit has nothing to do with not being able to Flash partitions, I have one whose warranty bit is blown, it affects literally nothing.

No, no its not. We can downgrade out boot partition to something within rollback... with an OFx BL, going to NCx/NKx should be impossible.

He wasn't jailed for that. He was jailed for sharing internal things he shouldn't have. Work freely, as long as you don't rely on leaks, RSA, etc. your in the clear.
[Verizon Samsung Galaxy S 4] Legitsu:
you can `flash` the kernel but it won't boot was what I meant
[Verizon Samsung Galaxy S 4] npjohnson:
Well. Not via ODIN. Via dd, yes. But you clan flash any partition (excluding PBL) via dd as long as you have root, aboot included.
[Verizon Samsung Galaxy S 4] Legitsu:
you can flash via odin by patching the checksum(at least on the st version) as the op did but that doesn't do anything for you

I bailed on my s4 traded it for a g2 ...

I still have a NC5 S4 as a backup but at this stage its looking like its not gonna be worth the effort originally I had planed to make my own cROM from the samsung base with as much as the upstream ASOP as I could patch in ...
[Verizon Samsung Galaxy S 4] Legitsu:
I wonder if there is any webkit exploits that may be of use
[Verizon Samsung Galaxy S 4] npjohnson:
For what? Root? Not that are known currently, WebKit exploits can usually mean something jailbreakme-esque if they're in the right context, and can bring up root.

As for the BL, it has no bearings.
[Verizon Samsung Galaxy S 4] Legitsu:
but it might get you kexec depending on the context ;)

just like on the ps4 where they break out of the trust zone if nothing else It might lead to some interesting breakpoints
[Verizon Samsung Galaxy S 4] npjohnson:
Well. It would just get us root. WebKit has no kernel permissions that could allow changes for kexec.

And we already have OF1 root and module loading, so kexec playground is set up, but I haven't been working on it.
[Verizon Samsung Galaxy S 4] Legitsu:
talking about using webkit exploits to gleen information

if nothing else might be-able to use it to create some interesting crashdumps
[Verizon Samsung Galaxy S 4] klabit87:
Was modload updated to support oc1 and of1? I thought the addresses are different so the current version you posted some time ago wouldn't work.

But I could be wrong.

That would be nice if it was.
[Verizon Samsung Galaxy S 4] npjohnson:
Oh shoot. I don't think we ever distributed that version. I'll ask around and maybe post an update for it.
[Verizon Samsung Galaxy S 4] klabit87:
Awesome! I've started to get the hang of some kernel dev but not nearly as advanced as I need to be.

Just want to get as many modules as I can to test them out.

Just testing things though.

Thanks!
[Verizon Samsung Galaxy S 4] wolfen1086:
Ok i saw the header on this thread about unlocked king the bootloader and it got my attention, but when I started reading it gave me a headache LOL do I only have one question.. Is thd boot loader on the Verizon S4 locked or unlocked, , keep in mind yall, I am only capable of hacking G a paper again with a knife, tall are thd experts
[Verizon Samsung Galaxy S 4] gadget!:
Yes, the bootloader on the Verizon S4 is locked.

If you are lucky enough to have a Verizon S4 on the original MDK bootloader it can be unlocked.

It is actually not unlocked but exploited using Loki, so you can install custom recoveries, roms, kernels, etc.

sent from a Galaxy far far away.
[Verizon Samsung Galaxy S 4] wolfen1086:
How can I tell if I'm on the original or not,?
[Verizon Samsung Galaxy S 4] gadget!:
If you have ever taken an update from Verizon you aren't but if you want to check, go to the Play Store and download "Samsung Phone Info".

That will show you what your boatloader is.

sent from a Galaxy far far away.
[Verizon Samsung Galaxy S 4] wolfen1086:
My Bootloader is I545VRUGOF1 So i guess it cant get unlocked yet :(

I liek the app you told me to get it tells me everything except what country the phone was made in, and I really dont care where it was made because it works
[Verizon Samsung Galaxy S 4] zeb carter:
Even though I have just moved from the VZW GS4, I never took any updates from Verizon and am still on MDK. I am running DANVDH's GPE rom.

Now I have followed this thread from inception and I don't recall anything about being able to unlock the MDK bootloader. Can someone point me to an actual method that works or is it still theoretical?
[Verizon Samsung Galaxy S 4] DeadlySin9:
I'm pretty sure they meant to say it can be exploited. A lot of people say it's unlocked when really it's just loki exploit.
[Verizon Samsung Galaxy S 4] zeb carter:
That's what I thought but I'm sure there are quite a few folks who don't know the difference. The LOKI exploit is what gives us those wonderful ROMS that the other folks can only dream about. Sure, they can use Safestrap to load TW based roms but they cannnot use any AOSP based roms with Safestrap.
[Verizon Samsung Galaxy S 4] gadget!:
I edited my post.

Thank you. Yes, my bad, it is not truly unlockable but exploited using Loki.

sent from a Galaxy far far away.
[Verizon Samsung Galaxy S 4] kcarden:
[MENTION=5848265]npjohnson[/MENTION] has an AOSP rom out for safestrap?
[Verizon Samsung Galaxy S 4] wolfen1086:
Somebody please do me a favor, in case I lose this thread, in the OF1 bootloader ever foes have a way to unlock it email me. Pm me. Call me. Just PLEASE tell me, I'd love to have this phone exactly like my old S4, it was a unlocked the mobile phone with TWRP recovery and CM11 on it I'd love to do that to this thing
[Verizon Samsung Galaxy S 4] EdrickMG:
You can't have it buddy, Verizon lock bootloaders and your equipment is lock, if you enter to Verizon equipments, LG G4, note 4 (mine), etc, etc there is a bounty of 8,000 dollars or more... Whoever who do that... Unlock bootloader if you have read history in Xda requieres almost hours and hours and hours to achieve this is not that simple... In the history of Xda I belive and correct me if I am wrong someone in s5 did it and reclaim 18,000 dollars for doing it, it is possible but requieres time and most of developers are here as a Hobbie is not their job, they have family and other important things to do, my equipment is not even rootable, in s4 at least..... You have the option to achieve that so go figure, short answer not possible to have twrp and roms like cyanogenmod etc, etc, with your bootloader
[Verizon Samsung Galaxy S 4] wolfen1086:
I know it's probally locked forever, I remember once with sprint I updated and had nadir problems. So I mistakenly wiped the entire phone and when I turned it on it said "Operateing system not found" I'd try that with this phone because I have thd Verizon Kit Kat firmware on mh computer. But I'm scared I'll turn this phone into a paperweight
[Verizon Samsung Galaxy S 4] npjohnson:
Yup. KitPop 4.4.4