yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] RuggedHunter:
I wish that I could do more than offer encouragement here for you, [MENTION=2471504]jeboo[/MENTION] and all of you who have committed so much time and energy on this project. I can't imagine the frustration you all must feel, at times...

"This is our world now... the world of the electron and the switch, the beauty of the baud. We make use of a service already existing without paying for what could be dirt-cheap if it wasn't run by profiteering gluttons, and you call us criminals. We explore... and you call us criminals. We seek after knowledge... and you call us criminals. We exist without skin color, without nationality, without religious bias... and you call us criminals. You build atomic bombs, you wage wars, you murder, cheat, and lie to us and try to make us believe it's for our own good, yet we're the criminals. Yes, I am a criminal. My crime is that of curiosity. My crime is that of judging people by what they say and think, not what they look like. My crime is that of outsmarting you, something that you will never forgive me for."

The Mentor

i337 MDL > MF3 > MK2 > SafeRoot > SafeStrap 3.71 > HyperDrive 12
[Verizon Samsung Galaxy S 4] Maribou:
Nice hacker manifesto quote. :)

Sent from my Dark Carnage powered device.
[Verizon Samsung Galaxy S 4] Surge1223:
http://www.anyclub.org/2012/05/emmc-partition-tools-usage-for.html?m=1

Remember that gs4 usb repair tool? Well if you dig around in it you can find a patch0.xml, rawprogram0.xml partition.xml etc already made for our device. Using the internet you can find msp.py PartitionTool.py etc. I successfully created a singleimage.bin using those tools. I wonder if I can make it boot off an sdcard with mdk bootloaders....
[Verizon Samsung Galaxy S 4] gnubian:
Let us know how it goes !
[Verizon Samsung Galaxy S 4] Surge1223:
Im going to research some more before I do anything though....but check this out if I put a micro sdcard into my pc it would be detected as /dev/sdb, and I would be able to write images/partitions to it using Qualcomm's own native interface.

msp.py is running from CWD: /home/surge/Desktop/Qa/galaxy_S4_9505

Usage: Mass Storage Programmer - destructively writes data to disks!!

Display this info python msp.py
Wipe partition info (-w) sudo python msp.py -r wipe_rawprogram_PHY0.xml -d /dev/sdb

Write a device (-r) sudo python msp.py -r rawprogram0.xml -d /dev/sdb
Create a singleimage.bin (-r) sudo python msp.py -r rawprogram0.xml -d 0
singleimage.bin stored to c:\temp (-r) sudo python msp.py -r rawprogram0.xml -d 0 -t c:\temp
Create an 8GB singleimage.bin (-r) sudo python msp.py -r rawprogram0.xml -d 16777216

no prompts (-n) i.e. automation sudo python msp.py -n -r rawprogram.xml -d /dev/sdb
Interactively choose files (-i) sudo python msp.py -i -r rawprogram.xml -d /dev/sdb
Specify files from rawprogram.xml (-f) sudo python msp.py -f sbl1.mbn,sbl2.mbn -r rawprogram.xml -d /dev/sdb
Search this path for files (-s) sudo python msp.py -s c:\windows,d:\ -r rawprogram.xml -d /dev/sdb

Patch a device (-p) sudo python msp.py -p patch0.xml -d /dev/sdb
Patch files to singleimage (-p) sudo python msp.py -p patch0.xml -d singleimage.bin
PRE-PATCH images for an 8GB disk (-p) sudo python msp.py -p patch0.xml -d 16777216

ALL IN ONE STEP sudo python msp.py -r rawprogram0.xml -p patch0.xml -d /dev/sdb

******************************************************************************
Usage: Mass Storage Programmer - destructively writes data to disks!!
******************************************************************************

------------------------------------------------------------------------------
Remember - DON'T FORGET SUDO
Remember - DON'T FORGET SUDO
Remember - DON'T FORGET SUDO
------------------------------------------------------------------------------

--------------------------------Partitions Detected--------------------------------------
/dev/sda 465.76 GB sectors:976773168 <--- Not likely an SD card, careful!
[Verizon Samsung Galaxy S 4] jgrubbs:
Grateful for all you do!
[Verizon Samsung Galaxy S 4] Surge1223:
From sec_log=0x100000@0xffe00008 (shortened log below)

This is prior to aboot (lk)

After pissing it off

Edit: Someone with a dev edition device should also send me the output of the below command.

P.S. Someone who hasnt tripped their knox flag should send me the output of this:

./viewmem 0xffe00008 0x100000 >/sdcard/sec_log

pretty sure one of the .config values is for the warranty void (I remember seeing the same specific value in my idb), this isn't a priority though.
[Verizon Samsung Galaxy S 4] retrogrymlyn:
I should be able to do this soon. Knowing Asurion, they will put me back on MK2, (even after my specific requests to not update the phone, which they have in the past said they would be fine now updating it for me.)

Still hoping I wont be on MK2, but if I end up on it anyway, I will work on this with you.
[Verizon Samsung Galaxy S 4] numbR7:
You are an officer and a gentleman sir! I give you my utmost respect! And thank you SIR for your honesty. You can not imagine how proud I am of a man like you! God speed! And farewell.

---------- Post added at 02:19 PM ---------- Previous post was at 01:56 PM ----------

Thank you for your response. I appreciate men like you who voice their opinion like a free man. God speed and farewell sir!

Edit: or fair lady--I don't know you so, sorry for the presumption if I was mistaken.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Baity being a noob here, but how do I use viewmem? Do I flash the zip then run the above command in terminal? Or, connect the phone and run the command in *nux?
[Verizon Samsung Galaxy S 4] Surge1223:
Haha no flashing required ? extract viewmem from the zip and either adb push it to /data/local/tmp or copy and paste it there.

Next you have to be open terminal or adb shell and type

su
chmod 755 /data/local/tmp/viewmem
cd /data/local/tmp

Then the command I posted above

Also I have my paths and permissions set up differently than everyone else so the command to run viewmem may be just "viewmem" instead of "./viewmem"

P.S. theres no rhyme or reason behind the santa, I just wanted to see if itd work like these do ????⛄
[Verizon Samsung Galaxy S 4] Bait-Fish:
LOL

It worked after I ran the command from the tmp directory. ./ worked. However, I got a "segmentation fault" response after about 5-10 seconds.

u0_a224@android:/ $ su

root@android:/ # chmod 755 /data/local/tmp/viewmem

100000 >/sdcard/sec_log <

sh: viewmem: not found

8 0x100000 >/sdcard/sec_log <

sh: ./viewmem: not found

127|root@android:/ # cd data

root@android:/data # cd local

root@android:/data/local # cd tmp

root@android:/data/local/tmp # ls

init.rc

viewmem

0008 0x100000 >/sdcard/sec_log <

sh: viewmem: not found

ffe00008 0x100000 >/sdcard/sec_log <

[INFO] Reading 1048576 bytes at 0xffe00008...

Segmentation fault

139|root@android:/data/local/tmp #

This on a MDK Dev Edition. I don't believe I've ever tripped a warranty counter. . .
[Verizon Samsung Galaxy S 4] Surge1223:
Well ?. Lol its entirely possible that this might not work on mdk (the address may have been different on mdk) Thanks anyways bait ?.
[Verizon Samsung Galaxy S 4] Hashbang173:
Any possibility we can do this: http://xdaforums.com/showthread.php?t=2539904
[Verizon Samsung Galaxy S 4] jamesd1085:
I asked surge that when that thread started...apparently our chipsets are worlds different...he said what works for them most likely won't work for us
[Verizon Samsung Galaxy S 4] Surge1223:
Actually our chipsets are similar if not the same, our aboot functions differently though
[Verizon Samsung Galaxy S 4] jamesd1085:
Ah...I see...didn't mean to misquote...I just remembered you said something was different from ours that wouldn't allow us to follow the same trail...it really doesn't seem to be working out for them either so yeah
[Verizon Samsung Galaxy S 4] ky5ever:
PM'd you my sec_log from my MK2 retail S4, that has not tripped the knox flag.

Let me know if you need anything else! Im sorry for suddenly leaving (not like i was helping much anyways) but Im back! Ill do whatever I can, and if I cant help, Ill learn how.
[Verizon Samsung Galaxy S 4] NighthawkXL:
Sadly the answer is no, we've already ruled out changing the cert files. If only it was that easy we'd would have been unlocked a long time ago... besides the idea is silly. If you edit a certificate it becomes invalid for whatever you where using it for in the first place since the hashes would no longer match the expected one.
[Verizon Samsung Galaxy S 4] scryan:
Surge, do you know if Kexec is still coming along?

As much as I get the desire to blow the thing wide open, I feel like if we can flash a new Kernel, Rom and Radio... Well I am happy :) We could at least keep up to date with out taking further updates.

I haven't been able to find much about kexec (beyond the general concept, especially wrt android), but was really hoping that it wasn't too far in the distance with jeboo's bypass LKM exploit... Though I have found postings from other phones that were never able to get it running stable enough to be of use, I was hoping that Hash had experience with it that would help it just be a matter of putting in the time? Obviously nothing against him, but it seems Hash is stretched very thin with all the devices he works on. Is there anyone still working on Kexec? Is it a matter of man hours, or has development hit a snag?

I try not to pester too much, but I have been hoping to see info on it for a while... The combo of not being able to touch the kernel, and increased security with each update worries me for the future.

*sigh* and here I thought switching from an obscure t-bolt to an S4 was going to give me more options. Stupid me taking exploits for granted and accepting the ME7 update :(
[Verizon Samsung Galaxy S 4] ky5ever:
I myself do know that Hashcode is working on kexec, or at least, has it on the table. He is/was working on hooking lkm_bypass into SafeStrap so that SS itself could load modules. He actually has a modified version of SS that does just that, but with the very basic version of lkm_bypass that theyve been working on, i.e. not for human consumption.

Kexec AFAIK is not being worked on, as further research and work is needed. However, just because you dont hear anything about it does NOT mean its not being worked on.

Some stuff needs to be kept on the down low, if you know what Im saiyan.
[Verizon Samsung Galaxy S 4] Surge1223:
From talking to Hash about it recently, I know he really wants to get it to work, but theres an issue with flushing the cache. If you google kexec chances are you'll end up in one of Hash's threads lol so its not for a lack of experience on his part. I myself have been trying to learn more about kexec from studying how Hash has implemented it in the past (while also trying not to bother Hash with my dumb questions..) but if and when I learn more ill post an update on the status of kexec for the S4.
[Verizon Samsung Galaxy S 4] ericerk:
Would you address the state of second init?
[Verizon Samsung Galaxy S 4] Surge1223:
Safestrap is an implementation of 2nd-init.
[Verizon Samsung Galaxy S 4] LiLPurP:
What about the possibility of using a program to connect multiple computers together to run a brute force on the private key? The hacker group "Anonymous" had something similar with there 0rbit program (i think thats the name) which allowed them to use the running pc as a "slave" for a lack of better words, would that be possible here?
[Verizon Samsung Galaxy S 4] Royalaid:
Highly doubt it

http://stackoverflow.com/questions/...ute-force-a-salted-sha-512-hash-salt-provided

this isn't the exact case but you get the point.
[Verizon Samsung Galaxy S 4] jhasty01:
Too bad we can't force change or spoof the expecting side in order to match up (or force/spoof the status of matched up) .. I would expect this hard to even attempt since you would probably brick each time you fail.
[Verizon Samsung Galaxy S 4] Surge1223:
From the MG7 build we found a user had...the flag in aboot it set to 3. How many people do we have left on ME7?
[Verizon Samsung Galaxy S 4] almonteb:
ME7 here
[Verizon Samsung Galaxy S 4] jgrubbs:
Still on me7 here as well!
[Verizon Samsung Galaxy S 4] scap99:
Most definitely.
[Verizon Samsung Galaxy S 4] Surge1223:
K if you guys could maybe remain there for a little bit, at least until I do more analysis on these new bootloaders. Interestingly enough, Im unable to flash the modem and nonhlos from this build as well..theres def something strange about this build. Its definitely meant for our device though. Im not going to suggest flashing it to anyone unless im sure it will prove to be advantageous, it appears this is the first build with SEAndroid set to enforcing.
[Verizon Samsung Galaxy S 4] BrennanU:
I'm still on ME7.
[Verizon Samsung Galaxy S 4] scap99:
Roger that!
[Verizon Samsung Galaxy S 4] sokrboot:
ME7 here as well.
[Verizon Samsung Galaxy S 4] Surge1223:
Got the modem to flash, strangely it needed to be signed correctly (that is had to be depadded of trailing zeroes) normally this is not the case for flashing a modem via recovery, usually it only needs to be signed properly for Odin to flash it. Samsung made depadding the modem quite tricky for some reason, more tricky than usual. It took me two tries to get it depadded successfully (usually it only takes one) also, it appears AWS is enabled on this modem.
[Verizon Samsung Galaxy S 4] gunz.jones:
I thought AWS was updated with me7/mk2 anyway.
[Verizon Samsung Galaxy S 4] scryan:
I think your mixing them up?

MDK > ME7 > MI2 > MJ7 > MK2 (MI2 might be wrong, but the overall order should be right)

I believe AWS was MJ7/MK2. ME7 is the 2nd update that fixed loki.
[Verizon Samsung Galaxy S 4] Hashbang173:
So is there any hope of flashing the mg7 bootloader for us on mk2?
[Verizon Samsung Galaxy S 4] Mistertac:
Also the guy who has the MG7 ( 4.2 ) phone said it has Knox on it. Now unless I'm just forgetting since it's been a while... Wasn't Knox first brought to us on MJ7 4.3 ?

Sorry I'll let you guys have it from here.. Just this has really interested me.. A build no one has ever seen or heard of. I know I'm not the only one constantly checking in for updates lol
[Verizon Samsung Galaxy S 4] Hashbang173:
Yeah I'm checking daily now just hoping we can Odin mg7 over mk2 to get an unlocked bootloader
[Verizon Samsung Galaxy S 4] Bad Bimr:
Both my wife's and my phone are on me7. Mine with Safestrap and hers just rooted and debloated.

I figured if an exploit comes out bring on me7 may be a benefit.

I ask before and will ask again. Is there any reason to upgrade from me7?
[Verizon Samsung Galaxy S 4] RuggedHunter:
I understand why you might not want to upgrade yet....still, mk2 has a lot of development to offer...

i337 MDL > MF3 > MK2 > SafeRoot > SafeStrap 3.71 > HyperDrive 12

☆☆☆☆☆☆☆☆☆☆☆☆☆☆

Interesting ----> The Five Basic Laws Of Human Stupidity

Hmmm....
[Verizon Samsung Galaxy S 4] Surge1223:
You are correct this is a 4.2.2 build with 4.3 security. Actually I had forgotten that user said he had knox on his S4, I only saw SEAndroid was set to enforcing via inspection of aboot.

To all;

So to sum up so far

:

-MG7 has SEAndroid enforcing and includes knox

-MG7 has a SW_ID flag with a value of 3 placing it before MI1 chronologically

-MG7 has an AWS enabled modem

P.S. Remember none of the above was in MI1.
[Verizon Samsung Galaxy S 4] jamesd1085:
Got to be something they saw in this that kept it from large-scale release...I trust if there is something there you will find it
[Verizon Samsung Galaxy S 4] ciabatoni:
h311sdr0id

I've dealt with h311sdr0id in matters before, and if im not mistaken, He is home now, and Ive seen him posting in other threads... Keep in mind that I havent checked every page in this thread to see if he has dropped in at all, I read up to page 7 and skimmed thru the last 5 to see if he did. But, I didnt see him...However, I am certain he is home, and gracing forums with his presence. If someone wants to check with him, or invite him to take a glimpse. If I come across him Ill be sure to let him kno what going on here...
[Verizon Samsung Galaxy S 4] ryanbg:
I messaged him not too long ago and received no response.
[Verizon Samsung Galaxy S 4] LiLPurP:
He may already be working on it or may not be interested in assisting on the bootloader, give him time we shall see but at the moment [MENTION=4939386]Surge1223[/MENTION] is working hard to find some kind of exploit anywhere, maybe Surge has contacted him already

Using: AT&T Samsung GS4 4.3 MK2 Rooted with SafeStrap Recovery

PETITION: http://www.change.org/petitions/samsung-usa-at-t-unlock-the-bootloader-of-the-galaxy-s4-sgh-i337-2
[Verizon Samsung Galaxy S 4] Surge1223:
[MENTION=766721]ryanbg[/MENTION] is also working hard to find an exploit, but as far as contacting hellsdroid, we were put in contact with each other through a common source. We have yet to actually talk to each other though.
[Verizon Samsung Galaxy S 4] LiLPurP:
I saw a guy say samsung has offically stated that a efuse was used in the s4 not sure if its true but here is the link he posted, also kind of curious what an efuse would mean as far as the bootloader?

Using: AT&T Samsung GS4 4.3 MK2 Rooted with SafeStrap Recovery

“Unless someone like you cares a whole awful lot, nothing is going to get better. It’s not.” - Dr. Seuss
[Verizon Samsung Galaxy S 4] pwned3:
As I have no experience with this other than quietly rooting from the sidelines... has anyone reached out to Adam outler to see if he would be willing to help? Wasn't he responsible for finding an exploit for the s3?

Sent from my SCH-I545 using Xparent Skyblue Tapatalk 2
[Verizon Samsung Galaxy S 4] Surge1223:
No he wasn't, Ralekdev was. Also he doesn't want to work on Samsung devices anymore.

Edit: errr wait actually Ralekdev was more responsible for the note 2 unlock, on the s3 there was a leak by an African-Canadian Sock Monkey
[Verizon Samsung Galaxy S 4] jeboo:
That thread/theory was discredited long ago, let's not dredge it up again..
[Verizon Samsung Galaxy S 4] ky5ever:
Damn sock monkeys, modding Samsung phones and telling people how it's done.... :p
[Verizon Samsung Galaxy S 4] Surge1223:
Heres the stock depadded VRUDMG7 partitions I have incase anyone else wants to examine them

Download I545VRUDMG7_Stock.tar.md5
[Verizon Samsung Galaxy S 4] ciabatoni:
Off Topic

I dont wanna get off topic here, but really want want to do a external 2 internal swap, on my VZW S4. Im just curious bc Ive been reading a cple different methods here on xda. Just not sure which one is for my bootstrapped S4, Here are 2 links incase someone wants to offer me an opinion, Bc im getting no answers in the thread... I dont wanna cross post, so if you could follow and maybe check it out, I would really appreciate it,

http://xdaforums.com/galaxy-s3/development/mod-extsd2internalsd-v8increase-data-t1772234

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

Ive also considered a few apps that do something similar on the market, Like, Roorexternal2internal, Foldermount etc...Thanx, and If this is wrong and offends anyone, plz delete it ASAP, and I apologize...
[Verizon Samsung Galaxy S 4] decaturbob:
This is way off topic...you should know better than to thread hijack.
[Verizon Samsung Galaxy S 4] Hashbang173:
So any chance we can flash this over mk2. Sorry if this is completely impossible to do.
[Verizon Samsung Galaxy S 4] Channning.Brown:
No way to go backwards at this time :(
[Verizon Samsung Galaxy S 4] Hashbang173:
What about over me7
[Verizon Samsung Galaxy S 4] Addiso:
Like the above user said no way to go backwards.
[Verizon Samsung Galaxy S 4] ciabatoni:
I apologize and didn't mean, nor wanna hijack. Please remove my comment on the off topic question, I was onlg looking for a little advice in either of those 2 threads. Getting the bl unlocked means a great deal to me as well. I appreciate all the hard work going into finding a solution. Thank you,

Sent from my SCH-I545 using Xparent Cyan Tapatalk 2
[Verizon Samsung Galaxy S 4] Hashbang173:
I mean flash mg7 over me7. Some users are still on me7. Not me :(
[Verizon Samsung Galaxy S 4] muniz_ri:
Hey Surge, I noticed you were able to depad aboot. If that is the case wouldn't 4.4 users be able to uptick the qfuse counter in 4.3's aboot to match 4.4 and then downgrade to factory stock 4.3 via Odin? Thanks,
[Verizon Samsung Galaxy S 4] :
Try it out out and let us know how it goes
[Verizon Samsung Galaxy S 4] Surge1223:
Unfortunately no, because if you change the counter, even just by one character it invalidates the secure hash aboot is verified with by sbl3. And you would end up in emergency dload mode (qhsusb_dload mode).
[Verizon Samsung Galaxy S 4] Surge1223:
Please no one try doing this. More than likely Odin will give you a "secure check fail: aboot" error message but in case it does go through or you use other means you will hard brick your device. Lets be more responsible with what we post.
[Verizon Samsung Galaxy S 4] Mistertac:
Hey Surge.. Any insight on what the deal is with this build? Like... Do you think it was just some test build? I see your other summary about how it's basically 4.2.2 with 4.3 security and AWS enabled. Just curious what your thoughts as of right now are on it?

Just an oddball build that up until now no one has seen?
[Verizon Samsung Galaxy S 4] RuggedHunter:
I don't want to dredge it up, but where can I read more about it? I think his early findings gave a lot of hope and partially formed a basis for the research in this thread... my understanding is that his discovery and his detainment are/were a bit mysterious...? I've seen a few of his recent posts, some offering encouragement and confirming that it's possible, and others that seem to distance himself from the effort...

☆☆☆☆☆☆☆☆☆☆☆☆☆☆

i337 MDL > MF3 > MK2 > SafeRoot > SafeStrap 3.71 > HyperDrive 12

Interesting read.... HERE !
[Verizon Samsung Galaxy S 4] Surge1223:
Might as well ask right now. Hey [MENTION=4181229]h311sdr0id[/MENTION] I don't suppose you feel like providing proof anytime soon do you? I mean dont get me wrong itd be great if you could help and it was true but being that you wont post or reply with any proof, im sure you can understand why we've gone from skeptics to doubters.
[Verizon Samsung Galaxy S 4] Surge1223:
Okay everyone, we need to find the address that this "Kernel Panic Upload Mode" is loaded at. I can trigger this manually, but we need to know where/how its loaded. [MENTION=2471504]jeboo[/MENTION] do you know?
[Verizon Samsung Galaxy S 4] dpeddi:
Isn't it the tz kernel?

Inviato dal mio GT-I9505 utilizzando Tapatalk
[Verizon Samsung Galaxy S 4] Surge1223:
I dont think so, the TZ is loaded by SBL2 and it basically just sets up the security environment and makes SMC calls. Plus its loaded from eMMC and operates in IMEM. The TZ is also pretty small (0x2A000000 - 0x2A03F000 in phys mem)
[Verizon Samsung Galaxy S 4] RuggedHunter:
[MENTION=4939386]Surge1223[/MENTION], how can we help you identify the address that it is called from? You mentioned that you can enter Kernel Panic manually...I assume that a kernel log afterwards does you no good? I'm trying to find a way that even my noobness can help...

☆☆☆☆☆☆☆☆☆☆☆☆☆☆

i337 MDL > MF3 > MK2 > SafeRoot > SafeStrap 3.71 > HyperDrive 12

Interesting read.... HERE !
[Verizon Samsung Galaxy S 4] RuggedHunter:
I came across this LINK that (I think) is a 4.4 kernel source code, but I'm not sure. OP says it was tested on mk2...? About 3/4 to the bottom is a reference to "4d07daf ARM: prevent kernel panic when ALIGNMENT_TRAP is set"

I will clean this post up if it's not useful, so as not to clog your thread... Please let me know.

☆☆☆☆☆☆☆☆☆☆☆☆☆☆

i337 MDL > MF3 > MK2 > SafeRoot > SafeStrap 3.71 > HyperDrive 12

Interesting read.... HERE !
[Verizon Samsung Galaxy S 4] Surge1223:
Well kernel panics arent uncommon its just the specific address in memory though. Also I did grab a log after thanks for reminding me. Its posted here in case anyone is interested http://pastebin.com/xQpfumMQ

[MENTION=766721]ryanbg[/MENTION] and I know of atleast 3 differnt kernel panic/different panic upload screens we can boot to and they can all be invoked manually.