yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] jamesd1085:
We can modify and use the already present certs...or at least we could before all these secure boot updates...now to use modified certs we need Samsung's verification signature...this isn't something we can just pull out of a hat...we need someone on the inside to slip us this signature on the low...basically that's not gonna happen...so next move is hoping for a verification bypass to be found...until a way to bypass secure boot is found the best we can hope for is probably a leaked dev bootloader with signature that's just for our device
[Verizon Samsung Galaxy S 4] jjppott:
Like this: http://xdaforums.com/showthread.php?t=2432827 ?
[Verizon Samsung Galaxy S 4] sokrboot:
Ha ha haaaa! I knew it! You love us too much to leave us [MENTION=4939386]Surge1223[/MENTION] !!
[Verizon Samsung Galaxy S 4] 06sharpshot:
Can I just say that you're awesome for sticking around. Great to have you working on this. If there's anything that you'd like help with that us basic users can do just let me know. I'm definitely game for doing mundane tasks to further the cause.
[Verizon Samsung Galaxy S 4] crhylove:
Holy **** bro! Glad you are a free man! That kind of crap is why none of us should give corporations money for anything, ever.

To go after an enthusiast working on a 2 year old device.... Inexcusable.
[Verizon Samsung Galaxy S 4] skepticmisfit:
he was doing the stuff with the s4 while it was the newest thing out, which is why the carrier he was working for got mad. at least from what I understand
[Verizon Samsung Galaxy S 4] lordgodgeneral:
Here's a post from over in the verizon S5 Root/Exploit thread from today that says he has a way to unlock the bootloader for even the S4

http://xdaforums.com/showpost.php?p=57615695&postcount=953
[Verizon Samsung Galaxy S 4] 06sharpshot:
I would seriously cry tears of joy and most definitely try to donate what I can. This is a great Christmas miracle if true.

Edit: After my initial excitement, I feel a lot more skeptical. The user who posted this isn't a developer and appears to be new with that being his only post. Definitely sketchy.
[Verizon Samsung Galaxy S 4] SamuriHL:
You know the old saying about if it seems too good to be true? I'm not saying it's impossible, but, the language used in that post highly suggests it's not necessarily what it seems. "Should work on any device once I activate it on my end".....what exactly does that mean? Yea, so, anyway, keep a vigilant eye on it but keep expectations quite low IMO.
[Verizon Samsung Galaxy S 4] sokrboot:
WARNING! Conspiracy Theory follows:

The guy who posted that (Anthony2131) is really h311sdr0id. Discuss...

LuLz
[Verizon Samsung Galaxy S 4] 06sharpshot:
*X-Files theme starts playing*
[Verizon Samsung Galaxy S 4] Hashbang173:
Hmm http://xdaforums.com/showthread.php?p=57637560
[Verizon Samsung Galaxy S 4] Raymondlikesroot:
agreed with the first part and second part(unfortunately...)
[Verizon Samsung Galaxy S 4] 06sharpshot:
It appears he has started asking for donations as well over in the S5 forum. That thread has quickly descended into anarchy after his initial claim.
[Verizon Samsung Galaxy S 4] thesoldier:
That thread just got closed for 24 hours lol. I'm not too hyped about this guy's claims
[Verizon Samsung Galaxy S 4] npjohnson:
Oh man. Haha. I posted a request to stop bashing people you don't know, and I started getting bashed! That literally made me lol.

Ahh. The pains of software development :p
[Verizon Samsung Galaxy S 4] tshelby73:
I hate false claims of unlocking boot loader. Makes me have to navigate through this crappy new tapatalk app for no reason.

Sent from S4 using the worst jacked up version of Tapatalk to date
[Verizon Samsung Galaxy S 4] majortaylor:
For the time being we don't know if it's a false claim
[Verizon Samsung Galaxy S 4] SamuriHL:
Do we know for sure it's nonsense? No, we don't. But the language used to make the claims fits the bill for a total scam. Things like "works on any phone as soon as I activate it on my end" and seemingly backtracking on claims of what devices it works on. When asked for proof of said claims by posting a video, they provide screen shots of an app my son could create in an hour. So I think the heavy dose of skepticism is warranted here. You can wish for this to turn out positive because you're desperate for an unlock solution, but, at the end of the day known talented Devs have been pouring real effort into this for quite some time without solid end results to date. I would lower the expectation on that thread to nothing more than pure entertainment. If it turns out he has something real, great, the lower expectations will be surpassed. If not, well, it was entertaining, yea? :)
[Verizon Samsung Galaxy S 4] gnubian:
With 18k up for donations and this guy hasn't shown any proof, I'm pretty sure he is full of it. Or stupid.
[Verizon Samsung Galaxy S 4] heath2805:
Seems kinda shady considering the name of the apk was "Permaroot." Google search shows there was already a permaroot back in 2010 to get S-OFF on HTC devices. Also, all of the devices he said it would work on are definitely not the same when it comes to unlocking a bootloader.

Although in the past I've seen files for the S3 that can be flashed in recovery that unroot and relock the device. Now that's amazing!
[Verizon Samsung Galaxy S 4] KaM1KaZ3:
Shhhhhhh. Let's keep this open for real work ?
[Verizon Samsung Galaxy S 4] MorrisC2010:
Dirty Hack: You didn't specify whether you flush the entire cache or ranges at a time. If your not doing ranges try those then load your buffer after if possible.

I haven't look at the source code yet so just throwing this around
[Verizon Samsung Galaxy S 4] sokrboot:
Anyone ever look into whether this is a range flush or full flush?

Although if we can't offline the CPUs properly the flush doesn't matter.
[Verizon Samsung Galaxy S 4] Surge1223:
Well we have to flush cache at multiple points for a number of reasons, the issue is more related to not being able to correctly add identity mapping. If you look in arch/arm/mm/ioremap.c you can see that they restricted mapping to secure mem. I confirmed that this is the main issue as well because i fixed up the identity mapping so it would be right and now when i look at seclog it only shows me two errors, which ill summarize below.

1. I set up prink to debug by throwing an error if the identity mapping i defined was null

2. Seclog complaining about line 251 in arch/arm/mm/ioremap.c, which in a stock kernel shows that identity mapping is disabled for secure mem.

So ive written a new module that might be able to do the remapping using either syscall hijacking or implementing a new ioremap function that is self sustained through the module itself.

So far ive added a lot to the module (its almost a mb in size now) and i added a new remapping method via a new process (kexec_ioremap.c) so we'll see how it goes
[Verizon Samsung Galaxy S 4] biglil1:
Absolutely amazing! !

Don't know what all that means but I believe I understand in a simplified manner.

This is an excellent step forward!

Many thanks to you and the others that continue to work on this!
[Verizon Samsung Galaxy S 4] Surge1223:
Thanks, I'll update source in a bit.

TL; DR

A function I need is blocked in the stock kernel so I'm working on implementing a new function and or hijacking and one to do what I want via a module

P.S. A benefit of building the kernel besides getting the kexec module is getting the fast charge module since I included it in the kernel build process :sly: I'm intentionally not posting modules I made because I want others to build them to get familiar with the process and how to deal with errors etc.
[Verizon Samsung Galaxy S 4] 06sharpshot:
How safe is enabling fast charging? I'm weary after being the victim of a faulty s4 melting while charging at night
[Verizon Samsung Galaxy S 4] Surge1223:
Attached is the reference to identity mapping failing, it's currently set for uart address space as defined by /proc/iomem... But still the problem would persist regardless. I have made a new remap function and built it both inline and as a out of tree kernel module function but have not decided/figured out how to implement it.

Most everything I do and develop hinges on the unsafe side lol.
[Verizon Samsung Galaxy S 4] sokrboot:
For anyone who is like me and is trying to learn this stuff, I found this helpful. http://www.tldp.org/LDP/lkmpg/2.4/html/book1.htm it's older material but is written in a way I can understand...mostly. :D
[Verizon Samsung Galaxy S 4] zombolt:
I know I'm not supposed to do this. Making a non essential post. But the last few on topic posts gave me excited ;) seems as though we are getting close to kexec success?? Should I calm down or are we getting pretty close to retail twrp?
[Verizon Samsung Galaxy S 4] sokrboot:
Yes be excited for progres! BUT every breakthrough that is made is usually paired with new challenges. The devs aren't following a recipe that works once specific ingredients are in place...they are trying to create a meal without knowing exactly which ingredients to use or how exactly to prepare them. A lot of educated guessing, testing, and trial and error. The magic could happen next week, next year or never.
[Verizon Samsung Galaxy S 4] Surge1223:
Well this is tough to answer, the thing is that as far as the kexec process, we've been close for a long time since hash got us most of the way there and I believe his work is based on jonprys Droid 3 kexec, but the last part is crucial and difficult to do because we're working blind.

There's a point in the kexec process where it becomes "the point of no return" what I mean by that is that no debugging messages will show and the process will either fail or succeed and the only way to debug is with a serial or jtag connection. So even if we got this to work (which in the end I think someone will need to serial debug it) Wed still have to make kernels that would boot, and deal with the aftermath of how the system handles the transfer to the new kernel.
[Verizon Samsung Galaxy S 4] 06sharpshot:
The good news is that this phone is still fairly popular and there were a lot of people willing to test via JTAG last time someone suggested using JTAG to try flashing things. I'm fairly certain if we got to where JTAG was needed, there would be people willing to test.
[Verizon Samsung Galaxy S 4] Deliquified:
Has anyone explored the kexec work from the early days of the galaxy s iii?

JT1134 and CVPCS were very skilled at porting it over. Could we reach out to them? Or perhaps employ the original method from cvpcs?

Here's the original G+ post showing kexec on cm9.

https://plus.google.com/app/basic/stream/z12nxjqzjybns3xad04cc5q4knbyjh4hprg0k
[Verizon Samsung Galaxy S 4] Surge1223:
They used hardboot. We can certainly test that too but I mostly test the normal kexec way (normal as in the original way kexec was made) but I tested hardboot past night, same result.
[Verizon Samsung Galaxy S 4] Deliquified:
Bummer that it didn't lead anywhere. Found an interesting comment when researching bootloader info about the galaxy s iii, and frankly it makes a lot of sense. Perhaps we should refocus our efforts elsewhere?

What if the devs were really close to something huge that would of prevented Samsung from locking any future bootloaders on their phones and this leak was intentional to stop devs from exploring anything further? Is this worth looking into their bootloader research to see if anything can be gleaned?

http://www.androidpolice.com/2012/0...nlocked-thanks-to-leaked-unsecure-bootloader/

"..The "African-Canadian Sock Monkey" gang is most likely Qualcomm themselves, as they realized that the people working on unlocking the boot-loader were getting very close in getting a more fundamental hack that would prevent all future boot-loader locks. This way they save both Verizon's face (and their company contract) and put an end to boot-loader hacking efforts, while still maintaining the option to be able at anytime to update the lower level boot-loaders to not accept this recent-hack..."
[Verizon Samsung Galaxy S 4] Surge1223:
I've read that thread many times and have talked to many of those involved, and have even followed up their research further. But one interesting thing is the

African Canadian Sock Monkey leak. It's been a topic of discussion for some of us for quite some time. While I don't think it is qcom, there's something to take away from that, I'll leave that to each individual to try to figure out, plus it's neither here nor there.

Plus they had Ralekdev, who seems to contribute to qcom now, and his account has been inactive for quite some time.
[Verizon Samsung Galaxy S 4] scryan:
Not sure how much you still work on this, and I don't mean to be the guy in the corner offering more work for you to do...

Have you considered compiling kexec for your nexus and trying to take it through the whole process on a little more hospitable device? Not sure how much work goes into making it device specific... But was reading the "thanks for everything" thread and you had me thinking about looking at compiling kernels/available options... and for whatever reason the thought came into my head that if you still wanted to mess with kexec, you may be able to take something away from making it the whole way through the kernel swap/having a stable system on the other side.

I dunno, just a thought.
[Verizon Samsung Galaxy S 4] Surge1223:
I've thought about this as well, will probably attempt it at some point.
[Verizon Samsung Galaxy S 4] Sterben Pistole:
Is it going to be possible to side boot a kernel (which i don't know if it's possible or not) with kexec or is it completely gonna override the stock kernel? Even though I have no knowledge of this type of programing. I do know some Java and HTML, if that would be of any use. I would like to know more on how this will boot up. Will it just boot up the same way the S3 with CM9 (I think that was the device) booted with kexec or will it be a different?
[Verizon Samsung Galaxy S 4] npjohnson:
Same as if you were booting into a ROM Slot, technically speaking (if my understanding is correct) all that would need to be on the stock slot would be the Stock Kernel, Kernel Modules, and SAFESTRAP. Then, when your phone boots, it boots up to SAFESTRAP, then into the ROM slot via Kexec. So, yes, the stock kernel must remain in place, but doesn't need to be the one you will be using after kexec runs.
[Verizon Samsung Galaxy S 4] Legitsu:
I was considering sending my "bricked" s4 out to have the screen replaced

https://www.facebook.com/iRepairzIT

I wonder if he would be willing to solder up a jtag connection and leave it in place before sending it back
[Verizon Samsung Galaxy S 4] scryan:
Then what?
[Verizon Samsung Galaxy S 4] Legitsu:
Surge1223 said he may need serial output assuming somebody can get ahold of a jtag'd I545 s4 just send it to him

if the end result is a higher chance of getting kexec I am all for it

maby we could get enough donations to get him a riffbox if he doesn't have one
[Verizon Samsung Galaxy S 4] Surge1223:
Thanks, luckily I have a riffbox :). Just no idea how to use it. I'm not really a hardware guy (I have soldering tools and my s4 is already disassembled so its just a matter of me sitting down to solder to the pcb). Now that the nexus 6 is my main device, I will either destroy my s4 while in the process of getting kexec to work or get kexec to work.

Either outcome is acceptable to me.

Idk why there's not a semi decent or semi English guide/video on using riffbox...I know YouTube has vids but still...
[Verizon Samsung Galaxy S 4] Legitsu:
ask [MENTION=4902178]Jeeboo[/MENTION]

hes well versed in the ways of the riff

I would love to play with jtag my self but my eyes have long since past the point where I can solder stuff that small
[Verizon Samsung Galaxy S 4] Sterben Pistole:
I would do J-TAG too, but I need this device since it's my daily driver... Is there any way I can help out Surge? I really want to at the very least contribute a tiny portion of help considering I will be using this if it comes out, and if I do use it without helping, I'll feel like a leech.
[Verizon Samsung Galaxy S 4] npjohnson:
I too have switched to an N6 (but on TMO). I am loving it.

You would not believe how many times I too have run into "welp, I'm going to get it working, or brick it, I don't care anymore"
[Verizon Samsung Galaxy S 4] Legitsu:
clarify something for me can we compile the stock nc5 kernel with no changes and boot it ? I am assuming no ...

because I am unsure if the samsung buildt kernel has KGB enabled and I don't think the riff can function as a serial con

you can dump memory addresses but I don't know about a serial con ..

its been ages since I have messed with anything that low level I am assuming you could get debugging output from some kind of aboot hook
[Verizon Samsung Galaxy S 4] waiters:
I replaced my sgs4 as well.. Im done with Samsung entirely since I'll never buy a phone retail price.. Sad because I loved Samsung but they did it not me...
[Verizon Samsung Galaxy S 4] Legitsu:
I am waiting for the lolipop update to drop so we can see what we are working with who know there might be something new we can leverage :fingers crossed:
[Verizon Samsung Galaxy S 4] rayzeur22:
What would be the potential chances of that? If anything the bootchain would be more secure at that point, right?

I'm hopeful for anything that gets us closer, but probably going to switch phones like everyone else is doing...
[Verizon Samsung Galaxy S 4] tshelby73:
Currently on nc5. Tried nk1 but couldn't set se to permissive so went back. In going to assume lollipop is going to be worse as the se policy is even more active on nexus devices.

Sent from S4 using the worst jacked up version of Tapatalk to date
[Verizon Samsung Galaxy S 4] Sterben Pistole:
Hopefully all of the things Google is doing doesn't turn them into the 2nd "Apple". I switched from my i4 to this for many reasons. One was that jailbreaking didn't even give me what I needed. Also, just got an iPod 4 from my cousin and I forgot how to navigate it, lol...
[Verizon Samsung Galaxy S 4] xXsquirr3lsXx:
You're gonna be waiting a LONG TIME then...
[Verizon Samsung Galaxy S 4] Legitsu:
not really should drop via ota within the next month or so
[Verizon Samsung Galaxy S 4] DeadlySin9:
For international, maybe. For carriers? Probably longer.

Either way, it stands that with the Lollipop update comes Google security updates to Android and will make root a bit more difficult. On top of that will be Samsung changes, including security patches, both system side and bootloader side. Maybe the new features will open up a new place to exploit, but that seems an unlikely hope.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] Legitsu:
could't careless about rooting already have it more interested in the possibility of getting a GPE edition rom to actually work correctly

for that we need a signed >5.0 kernel

you can always downgrade to NC5 via odin if somebody manages to get kexec working root too

its unlikely that Samsung would prevent people from downgrading to NC5
[Verizon Samsung Galaxy S 4] DeadlySin9:
Since it's an entirely new version they'll probably up the aboot counter which means no downgrade. They stopped us before when we had an exploit, knowing that we have progress on another is reason enough for them to stop us again.

Sent from my SGH-I337
[Verizon Samsung Galaxy S 4] Sterben Pistole:
Lollipop for the i9500 was leaked. Would that do us any good? I'm positive it won't be of help, but it's better to ask questions than have them unsaid.
[Verizon Samsung Galaxy S 4] Legitsu:
I been trying to figure out if host side rootfs over ADB possible

it would get us custom kernel bit of pain but its better then nothing

so far not much luck having trouble building a image into something usable // then I need to figure out how to boot it

perhaps I can exploite something in the sbin/reboot probly not but its worth a shot ...
[Verizon Samsung Galaxy S 4] doubleaykay:
You should try it out, perhaps just to see what stands in our way.

Also, I have a theory, if we can somehow get the stock kernel patched with kexec-hardboot (a la MultiRom) we could at least get the MultiRom functionality. That's a starting point, no?
[Verizon Samsung Galaxy S 4] Legitsu:
we have safe-strap for multirom support what we need is a way to build and run kernel from source so we can run non TW roms

as for tethered booting that all depends on if the aboot runs a integrity check when booting from a host side adb root fs witch I am assuming it would

not looking to good atm ...
[Verizon Samsung Galaxy S 4] doubleaykay:
But can't we use the kexec patch to spawn in a custom kernel once the TW one has booted and then kill the TW one, right? This seems like the simplest way to do it.
[Verizon Samsung Galaxy S 4] Legitsu:
thats what [MENTION=4939386]Surge1223[/MENTION] is trying to get working
[Verizon Samsung Galaxy S 4] doubleaykay:
Just looked back at that, and it seems you are right, I must have missed that :p
[Verizon Samsung Galaxy S 4] Legitsu:
don't get your hopes up hes switched to the nexus 6 witch also what I am considering because **** samsung ...
[Verizon Samsung Galaxy S 4] doubleaykay:
Urg, no love for us still with the S4 lol. I may start working on something soon with a friend, probably related to getting AOSP on TW kernels...
[Verizon Samsung Galaxy S 4] Legitsu:
good luck with that you will need it
[Verizon Samsung Galaxy S 4] Surge1223:
Lol I haven't done anything on nexus either publicly. I'm still trying to get Kexec working by figuring it out on nexus first. Unfortunately I had to spend a considerable amount of time enabling last kmsg....apparently pstore only logs panics.

Anyways I re-enabled last_kmsg on nexus so now I can see what's up once I make a few ramdisk edits

Hopefully I can even use aroma with chainfires script to see what happens live
[Verizon Samsung Galaxy S 4] dmt010:
Love how originally this thread was a **** vzw thread and now it's evolved over time into a **** Samsung thread. But glad to hear some progress by the surgester
[Verizon Samsung Galaxy S 4] TheLoonyRebel:
I say screw them both.
[Verizon Samsung Galaxy S 4] pendragon11:
F*** em, give the people what they want
[Verizon Samsung Galaxy S 4] tshelby73:
I'd say it's Verizon and att as the other versions are unlockable

Sent from S4 using the worst jacked up version of Tapatalk to date
[Verizon Samsung Galaxy S 4] Sterben Pistole:
We've been over this plenty of times already, lol. Don't think that its VZW and AT&T. Know its them. It's been confirmed its them plenty of times. I'm moving over to the HTC side of things after my time with this phone is done. They've got unlockable bootloaders even on AT&T. I should've atleast gotten an LG G2 instead of an S4 since I didn't know about TouchWiz and all this stuff. Oh well... What's done is done.
[Verizon Samsung Galaxy S 4] dnabors28:
Guys....

So I know this is wreck less and irresposible of me doing what I'm about to do, as I have not read the 180 pages of comments, but I will post blindly anyways. :laugh:

I plugged my Verizon sgs4 (4.4.2, stock rom, rooted via towel root, safe strap installed, NC5) into my tablet to mooch power, and it restarted upon plugging the USB cord into the tablet. But not an ordinary random reboot. This particular reboot cause the device to vibrate twice (about 3 seconds apart), and the first screen to come up had the Samsung logo top center and an icon of a lock (unlocked) with the words "Custom" under it on the bottom center. :confused::confused::confused:

I am going to post pictures and video tomorrow... all my devices are dead and cameras will not work until they are charged:crying::crying::crying:

Edited for spelling.
[Verizon Samsung Galaxy S 4] Dhs92:
That.. That just means you have modified your system files. It happens whenever you install a custom ROM or something that modifies your system's files.
[Verizon Samsung Galaxy S 4] dnabors28:
I'm going to Odin flash it back to stock and try to duplicate...

Just in case. Not calling you a liar, just desperate :crying:
[Verizon Samsung Galaxy S 4] 06sharpshot:
That message comes up when you have a modified system. It does not mean your bootloader is unlocked.