yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S 4] krnnme:
Hmm that's what I thought too

But you see it came with sw build number ending in MDM_LLK

And the sku was schi545kdu

It's so weird

And also to root it I didn't have to go through steps 1,2,4 to root it on the mdk guide

I just did step 3

And I thought goomanager didn't host lokid recoveries

I installed twrp 2.6.3.0 directly from goomanager
[Verizon Samsung Galaxy S 4] Bait-Fish:
I'm not sure if what I got Surge1223 was what he needed, but I have been attempting to get a real PIT file using anything, really. Heimdall seems to be the best, but it fails on my WinXP machine repeatedly. "heimdall.exe is not a valid win32 application." it does the same for heimdall-frontend.exe.

Maybe someone else here can get Heimdall to work and issue these commands to get the PIT file (instructions from this thread).

I'm guessing the last command isn't necessary. Then, upload "SGR.pit" for the rest of us. TIA
[Verizon Samsung Galaxy S 4] Roland_D:
Lol... You lost me there... I don't know what to tell you... Maybe somebody else had any clue on what that baseband is...

---------- Post added at 12:16 PM ---------- Previous post was at 12:10 PM ----------

So apparently is a stolen store device... (LOL!)

At least according to what they say here... http://forums.androidcentral.com/verizon-samsung-galaxy-s4/295346-software-update-4.html#post2914085
[Verizon Samsung Galaxy S 4] krnnme:
you know I actually considered that too with the little info i found about it online

but it has a clean esn

it lets me activate it normally

the funny thing is

it's fully functional and not stuck in demo mode

which makes me wonder why verizon would put these kind of phones out there at the store

cause it has an unlocked bootloader... and I highly doubt they would put out dev editions of the phone
[Verizon Samsung Galaxy S 4] Skeetch79:
So being a noob with Heimdall, what does this tell you? Is it the Partition mapping? Does it actually extract each partition and output it to your PC?

Sorry, please clarify.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Surge1223 wrote,

I don't know much about it myself.
[Verizon Samsung Galaxy S 4] Bait-Fish:
[MENTION=2786463]Toddricks[/MENTION], I re-made the system.tar.md5 and zipped it up using a different command to generate it. Hope that will work. It's located in the orginal post here.
[Verizon Samsung Galaxy S 4] Skeetch79:
So this is a stock rooted system image?

In creating the image, was there a custom recovery installed at the same time?
[Verizon Samsung Galaxy S 4] Bait-Fish:
Yes, and no. But recovery is not included, only system. The phone still had stock recovery when the original system.img was dd'd.
[Verizon Samsung Galaxy S 4] Toddricks:
Sku on my developer device is schi545zkd

Sku on my consumer edition is schi545zkv

---------- Post added at 03:12 PM ---------- Previous post was at 03:02 PM ----------

Downloading as I type this reply. Will try to flash as soon as I get it downloaded and extracted. Hope this one goes good.
[Verizon Samsung Galaxy S 4] Skeetch79:
Weird, my developer device has a SKU of SCHI545ZKV. Maybe some ZKD's were converted at the factory to ZKV?

The webpage for Samsungs Developer Phone does have a URL of "http://www.samsung.com/us/mobile/cell-phones/SCH-I545ZKDVZW" - ZKD

But mine is clearly a developer but has the SKU ending in ZKV
[Verizon Samsung Galaxy S 4] Toddricks:
Failed in odin.

md5 checksum is good but failed in nand
[Verizon Samsung Galaxy S 4] Bait-Fish:
Well, crap. . .

I'm not sure why it's failing.
[Verizon Samsung Galaxy S 4] Toddricks:
Wish I knew too.
[Verizon Samsung Galaxy S 4] Bait-Fish:
I've been trying it on mine and it fails too. I am at a loss.
[Verizon Samsung Galaxy S 4] Toddricks:
Same message I get in odin
[Verizon Samsung Galaxy S 4] oakley470:
You guys getting nand write errors all had:

A)antivirus/kies/ anything possible diasbled before running and usb debugging enabled

B) if using windows right click run as admin

correct? also did anyone attempt with different versions of Odin/drivers installed? or even different cables or usb ports? these shouldnt affect it but they have been known to in the past
[Verizon Samsung Galaxy S 4] Skeetch79:
Not sure if it makes any difference but I was able to convert the boot and recovery images you had posted earlier in this thread into odin flashable tar.md5 files issuing the same commands but through cygwin

I installed cygwin and then loaded the cygwin terminal from the shortcut created on my desktop - called, in my case, "cygwin64 terminal"

doing so creates a folder within your, in my case, c:\cygwin64\home\ directory - it is named after the username you are logged into windows as. so for me i see c:\cygwin64\home\Brett. before issuing any commands, I moved the recovery.img and boot,img files I downloaded from your posts into this folder - my username folder.

I then issued the three command lines through cygwin terminal for the recovery.img file:

tar -H ustar -c recovery.img > recovery.tar

md5sum -t recovery.tar >> recovery.tar

mv recovery.tar recovery.tar.md5

i repeated the steps for the boot.img file obviously renaming the commands where needed.

The files generated (both recovery.tar.md5 and boot.tar.md5) were flashable without error using ODIN 3.07 in the PDA spot of the program. I left only "reset time" checked - I unchecked auto reboot. You will have to wait a little in this case until you see "pass" with a green background - it tends to hang on "reset" with a blue background for a while. but i had no issue.

maybe try cygwin and follow what i did - substituting "system.img" where needed instead of "recovery.img" and so forth.

see how it goes.

---------- Post added at 09:01 PM ---------- Previous post was at 09:00 PM ----------

In my case where I successfully flashed a recovery.tar.md5 and boot.tar.md5 created from cygwin with the commands I had BitDefender running and also was using the latest samsung usb drivers.
[Verizon Samsung Galaxy S 4] Bait-Fish:
Thanks for the input. I've searched and searched for answers. The same rig/setup worked a couple times flashing a GS4 Retail back to stock.

I think it may be something wrong with the tar.md5 process. I'll have to set up Cygwin. It took forever to not even get close to completing on the XP machine so I really have not been looking forward to revisiting it again.
[Verizon Samsung Galaxy S 4] Surge1223:
I was about to write the package, but I went over the pit file and i noticed it was exactly the same as the consumer edition one. I thought the developer edition had more partitions than the consumer one. That and the partitions all line up exactly like the consumer edition, i remember previously the partitions were different...
[Verizon Samsung Galaxy S 4] Skeetch79:
This is my partition block output in terminal emulator:

u0_a235@android:/ $ su

form/msm_sdcc.1/by-name/ <

lrwxrwxrwx root root 1970-01-26 21:57 aboot -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 1970-01-26 21:57 apnhlos -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 1970-01-26 21:57 backup -> /dev/block/mmcblk0p23

lrwxrwxrwx root root 1970-01-26 21:57 boot -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 1970-01-26 21:57 cache -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 1970-01-26 21:57 carrier -> /dev/block/mmcblk0p28

lrwxrwxrwx root root 1970-01-26 21:57 efs -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 1970-01-26 21:57 fota -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 1970-01-26 21:57 fsg -> /dev/block/mmcblk0p24

lrwxrwxrwx root root 1970-01-26 21:57 hidden -> /dev/block/mmcblk0p27

lrwxrwxrwx root root 1970-01-26 21:57 m9kefs1 -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 1970-01-26 21:57 m9kefs2 -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 1970-01-26 21:57 m9kefs3 -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 1970-01-26 21:57 mdm -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 1970-01-26 21:57 modemst1 -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 1970-01-26 21:57 modemst2 -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 1970-01-26 21:57 pad -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 1970-01-26 21:57 param -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 1970-01-26 21:57 persdata -> /dev/block/mmcblk0p26

lrwxrwxrwx root root 1970-01-26 21:57 persist -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 1970-01-26 21:57 recovery -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 1970-01-26 21:57 rpm -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 1970-01-26 21:57 sbl1 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 1970-01-26 21:57 sbl2 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 1970-01-26 21:57 sbl3 -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 1970-01-26 21:57 ssd -> /dev/block/mmcblk0p25

lrwxrwxrwx root root 1970-01-26 21:57 system -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 1970-01-26 21:57 tz -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 1970-01-26 21:57 userdata -> /dev/block/mmcblk0p29

root@android:/ #

---------- Post added at 06:31 AM ---------- Previous post was at 06:29 AM ----------

Sorry about formatting but I do see system as block 16 - which agrees with your PIT
[Verizon Samsung Galaxy S 4] jpcalhoun:
Dev Edition Stock Kernel

Hey guys does anyone have a link to the

stock kernel

for the Verizon Dev Edition i545, MDK? I've read all 46 pages in this thread, maybe I missed it, if so I apologize.
[Verizon Samsung Galaxy S 4] Roland_D:
I don't think I've seen it around...
[Verizon Samsung Galaxy S 4] Bait-Fish:
It's here a couple places. The first one was taken from a nandroid by locofocos.

The second was asharad, taken by dd if/of.

The third, I extracted individually with Philz CWM using the custom function for just the kernel.

Edit: Added links.
[Verizon Samsung Galaxy S 4] Surge1223:
Seriously the pit files are exactly the same. I made an odin flashable dev modem, just to test that odin will read it ok. Anyone want to try flashing it? Also wheres the link for the system partition?

---------- Post added at 10:08 AM ---------- Previous post was at 09:51 AM ----------

Those boot.img's, those are from stock dev edition that was rooted, but no custom recovery right?

---------- Post added at 10:16 AM ---------- Previous post was at 10:08 AM ----------

Also you cant flash a system.tar.md5, it has to be a system.img.ext4
[Verizon Samsung Galaxy S 4] Bait-Fish:
This post quotes one I uploaded and links to my failed (so far) tar.md5 attempt.

Edit: I believe all boot.img files in this thread are stock Dev, likely from phones with root and recovery. We can directly just flash recovery via ODIN, never having to touch the kernel like the old MDK, MD2, Motochopper, back to MDK method did.

Edit 2:

Ohhh. Thank you VERY MUCH for helping straighten this out!

I'm guessing the .ext4 is more than just a difference in name.
[Verizon Samsung Galaxy S 4] equake:
Seriously, someone needs to consolidate all the Good flashable images into one thread so folks can try them out.

I'm wondering if it be easier to to take a known good flashable tar file and just replacing the requisite files with the Dev version files for example take the Consumer Ed ODIN image and replace with Dev Ed files.

My 2 cents
[Verizon Samsung Galaxy S 4] Surge1223:
That link doesn't work, it says:

Do I have to have a 4shared account or something?
[Verizon Samsung Galaxy S 4] Roland_D:
I made one...
[Verizon Samsung Galaxy S 4] jpcalhoun:
Thank you for your help, much appreciated.
[Verizon Samsung Galaxy S 4] Bait-Fish:
That was my 4shared :confused: First I've heard about the error.

I got a link for the same file... system.img (zipped). The MD5s posted previously still apply.

http://www.4shared.com/zip/v_9BmI7O/system.html

Did that still fail?
[Verizon Samsung Galaxy S 4] Surge1223:
I need, sbl1, sbl2, sbl3, rpm, tz, hidden, cache, aboot, and persdata partitions lol. Actually what I really need is the firmware, that is sbl1, sbl2, sbl3, aboot, rpm, and tz. What happens when you guys open Kies on a pc? Is there anyway you can extract the stock image from there?

Currently I have the following in ready to be made into a odin package:

boot.img

modem.bin

NON-HLOS.bin

recovery.img

system.img.ext4
[Verizon Samsung Galaxy S 4] Skeetch79:
Awesome work!

Personally both KIES and Verizon Upgrade Assistant do not recognize the firmware on the phone. So for me that is not an option. Anyone else have this issue as well?

---------- Post added at 01:47 PM ---------- Previous post was at 01:41 PM ----------

FYI - http://www.sammobile.com/2013/10/01...oid-4-3-test-firmware-for-galaxy-s4-gt-i9505/

Would be nice to have official firmware. Probably will get the firmware for 4.2.2 after the OTA for 4.3 is out.

But what gets me is that SXTPDevelopers sent a tweet this morning in regards to the firmware for the Galaxy Note III - they a link to the ODIN-TAR (http://www.sxtpdevelopers.com/showthread.php?t=324).

They also have firmware for the VZW S4 - MDK stock TAR, no root (http://www.sxtpdevelopers.com/showthread.php?t=237).

They may have a few others as well on their site throughout the various threads.

I just don't understand what makes our Firmware any different. They will not release it - due to, what they claim, C&D letters from Samsung. They release other device's firmware but not ours. What is the deal with that?
[Verizon Samsung Galaxy S 4] Surge1223:
The scariest part of making this odin package is the firmware, because your firmware is different and doesnt have a locked bootloader, theres no way im making this odin package unless im absolutely a hundred percent sure that who ever uploads the files is still on stock dev image, ideally the only modification they would have made to their phone would be to root. I don't think theyd release the firmware for the dev edition because they are probably afraid of someone being able to figure out a method or workaround to allow non dev edition edition gs4's use a modified version of the dev edition firmware.
[Verizon Samsung Galaxy S 4] Skeetch79:
Fine, but then couldn't the same be thought when releasing firmware for the Developer Edition of the HTC One - which is on HTCdev.com? Motorola hosted firmware for the WiFi only Xoom, it could have been used for the locked down LTE/Wifi VZW version, but never was.
[Verizon Samsung Galaxy S 4] Roland_D:
Yeah it blows my mind too...

I don't think so... First of all there is already a Dev ed stock flashable out there... And secondly the lock is hardware not only software... So the only thing to figure out is how to raise 700 bucks to buy a device with unlocked boot loader...
[Verizon Samsung Galaxy S 4] Skeetch79:
The Dev Ed stock flashable which you reference is over at the other site? (just to clarify!) LOL
[Verizon Samsung Galaxy S 4] Roland_D:
No there is a post in development...

edit: http://xdaforums.com/showthread.php?t=2352396
[Verizon Samsung Galaxy S 4] Surge1223:
Thats just the system and boot partitions, it doesn't contain any firmware, also the kernel is modified. Also, I didnt say the lock was hardware or software exclusive, I was just saying it might provide more insight and or help find another vulnerability, like a modified aboot, etc. It also has the benefit of being signed by Samsung.
[Verizon Samsung Galaxy S 4] Skeetch79:
Right. Yeah, I have seen this one. Would be nice if Scrosler could also come up with an Odexed Rom as well.
[Verizon Samsung Galaxy S 4] equake:
That file is not a ODIN flashable image but a ROM which is rooted and deodexed and not truly stock.
[Verizon Samsung Galaxy S 4] Roland_D:
I see...
[Verizon Samsung Galaxy S 4] Bait-Fish:
I have all of those too. To reassure you, I did as little to the phone as possible. [MENTION=4139454]asharad[/MENTION] and I were trying to assist someone who claimed to have found a bootloader unlock, which proved not to be. In the process, we used different methods to root and get the files. He ODIN'ed a recovery and root, leaving his boot.img untouched. I used the old pre-release MD2 kernel, Motochopper, root method. When all was said and done, I flashed his (developer) boot.img back to get the Dev MDK kernel back. My method preserved recovery.img. Totally stock Dev phone other than root and connecting to my home WiFi. I didn't connect it to a Gmail account either, bypassing that during initial boot.

Give me some time and I'll get those files up and PM'd to you, Surge1223. Any personal data worries otherwise? Especially, that these will be in a public image for all?

Maybe I'll post the MD5s for each publicly. Hopefully [MENTION=4139454]asharad[/MENTION] could verify his MD5s against mine.

EDIT: Those MD5s are:

29136d25aed899d6ee74159f6f8daaaa *aboot.img

e850e23f9c2bd97527b132aaecb0474d *apnhlos.img

da6a0d097e307ac52ed9b4ad551801fc *backup.img

d7d0693384050fb4b6bbdafefbeafd18 *boot.img

8f4e33f3dc3e414ff94e5fb6905cba8c *carrier.img

C53A3622F4F75D6C14E66CC0901B4357 *.cache.img

4523f8608e43a57a37961d1b35f7c1fd *efs.img

f1c9645dbc14efddc7d8a322685f26eb *fota.img

d1dd210d6b1312cb342b56d02bd5e651 *fsg.img

9e9890fe6ad84d4484d63720aeb93708 *hidden.img

254d25ab12fcf9dfb0dd42a19f0fc995 *m9kefs1.img

a998fe885e65157605b78199129409ab *m9kefs2.img

e8c1f9fe2e1c12165ba601a425b93d7a *m9kefs3.img

7f9f7eca2aba8a2f8521f7cff3942668 *mdm.img

d1dd210d6b1312cb342b56d02bd5e651 *modemst1.img

d1dd210d6b1312cb342b56d02bd5e651 *modemst2.img

8970d9ead803297edb9635f14e47a586 *pad.img

f556f1e3de0f3d2e78ca425e4b862152 *param.img

551bcf9abbe3f53fde2e48564463915d *persdata.img

96995b58d4cbf6aaa9041b4f00c7f6ae *persist.img

b07a0fdf9997c6b0ea8fde3dce38382e *recovery.img

0e613bd21d07fc021fe0eee40ef76c39 *rpm.img

e3321bac74b10dd10a45e51aa8e38d93 *sbl1.img

6afe0db027c8baacea3a9d69e98f43fb *sbl2.img

ab06c7ee1d43632309fcd378dba50b65 *sbl3.img

0829f71740aab1ab98b33eae21dee122 *ssd.img

0ac0955670840d830879fc2aaff52588 *system.img

de08866ae400aca0f3cc19f7be19644f *tz.img

(created with RapidCRC)

Edit: PM sent, done and done! :thumbup:
[Verizon Samsung Galaxy S 4] Bait-Fish:
A question that's come to mind these last couple days, is it possible to dd if/of system back to the phone while the phone is in a normal ON state? It seems to me that parts of that partition would be in use and may cause some issue/conflict doing that live. Thoughts?
[Verizon Samsung Galaxy S 4] Skeetch79:
So I dd'd my own partitions from my phone and compared them against what you had posted. I noticed a few of the MD5's did not match up, while the others were spot on.

These did not match:

aboot.img

cache.img

efs.img

hidden.img

m9kefs1.img

m9kefs2.img

m9kefs3.img

param.img

persdata.img

system.img

Now, I would expect cache, efs, m9kefs1, m9kefs2, m9kefs3, persdata and system not to match because those partitions would differ from user to user and phone to phone. The EFS data is unique for each phone. Obviously, the persdata is different from phone to phone due to different users. Cache would vary as well depending on its contents at the time of dd'ing.

But what is held in param.img? hidden.img? aboot.img?

Now I have stock boot.img but Philz Touch Recovery for my recovery, yet our MD5's for recovery match...do you also have Philz Touch Recovery installed? The one which I posted a few days ago (philz_touch_5.08.5-jfltevzw.tar.md5)? If so, that would make sense as to our matching MD5's.

Would system.img MD5's differ as well due to what is installed in the system partition at the time - meaning yours would be different than mine versus someone else's?
[Verizon Samsung Galaxy S 4] Surge1223:
Ill pause my progress. Aboot, hidden, recovery are crucial. Also while I was looking through the pit files, i noticed recovery, sbl1, aboot, and I think everything actually are exactly the same. I didn't compare everything though, here Im posting both incase anyone wants to compare
[Verizon Samsung Galaxy S 4] Skeetch79:
What are the functions of aboot and hidden?

Can either of these change if you flash a custom recovery?
[Verizon Samsung Galaxy S 4] Skeetch79:
So I polled another user of the Dev phone in another forum and the MD5's he gave me for his device's aboot and hidden partitions are different from mine and also from what Bait-Fish posted. So far three different MD5's for both aboot and hidden.

Could they vary from device to device? Surge1223, you seem to feel as though they should be identical from device to device.
[Verizon Samsung Galaxy S 4] Bait-Fish:
I am using Philz but it's about 1.5 months ago, the version not the latest. Not sure what to say about differing MD5s. Would bs=4096 in the dd command line cause that. That could be my case.
[Verizon Samsung Galaxy S 4] Surge1223:
Aboot is the one that needs to be the same. Maybe its the way they are posted (i.e aboot vs aboot.mbn vs aboot.img). Can we post all of them we have? Ill take a deeper look at the three with some software. Are the file sizes at least the same? On mdk its 1.2 mb

Heres the md5 from stock MDK odin tar's aboot.mbn

MD5: 684caa6e13f29f9cc78c6265f691e314

In all honesty im more worried about the pit file
[Verizon Samsung Galaxy S 4] Skeetch79:
I am dd'ing all the partitions as .img files so I have aboot.img, hidden.img, system.img, etc...how would I pull aboot as a mbn file?

Which files need to be in mbn format and which in img format?

My aboot.img has an MD5 of 0363BEFB2BCD79996AEB99570549E05E and a size of 2,048Kb
[Verizon Samsung Galaxy S 4] Surge1223:
They're posted in the pit .txt files I attached a few posts back
[Verizon Samsung Galaxy S 4] Skeetch79:
I looke dover your PIT files and they make sense. The question I have though is in the case of a file like aboot.mbn, can I still dd if/of it to aboot.img, create an ODIN flashable tar.md5 from it and upon flashing it back expect it to go to the right spot or do I have to extract it from the partition a different way?
[Verizon Samsung Galaxy S 4] Surge1223:
You dont need it to be a .img just rename it to aboot.mbn. and no, I think you'd have issues because aboot is needed to get to download mode, and the dd'd img is not the same as the original in the firmware. Im not including the aboot or sbl1 in the odin image im making. Only If someone accidently flashed a stock me7 tar with odin on a dev device id include it just to test. Ive got this thing ready to go, just doing some checks before I post anything. This is going to happen in phases.

Phase test 1: Flash dev modem, apnhalos, kernel and recovery from a odin tar package. --this will confirm the dd'ed img files converted to bin and mbn successfully and that the recovery and kernel are stock. Also anything that goes wrong here is fixable.
[Verizon Samsung Galaxy S 4] Chris123NT:
Sounds very encouraging so far, if this all leads to an odin flashable package for all of us with dev phones I think this will make a lot of people rest a little easier knowing they have that safety net to odin back to "stock".
[Verizon Samsung Galaxy S 4] Surge1223:
Ok heres the first odin package, let me know if there are any issues. Report back with what your kernel and modem are after you flash this and if you can boot into stock recovery
[Verizon Samsung Galaxy S 4] Toddricks:
Downloaded file and ready to flash.

Everytime I go to flash with odin 3.07 it crashes saying odin has encountered a problem.

Flashing in pda with f. reset time checked and auto reboot checked....................

What am I doing wrong here?
[Verizon Samsung Galaxy S 4] Toddricks:
Ok it is not odin because I was able to flash the stock mdk tar.

Must be an issue with the modem, recovery, kernel package.
[Verizon Samsung Galaxy S 4] Surge1223:
My bad small folder error, all the files are fine I just messed up the .gz part. Here's the fixed Odin image in tar.md5. This time I made sure odin loaded it correctly. Let me know if there's any issues.
[Verizon Samsung Galaxy S 4] Toddricks:
Re downloaded the file. At a charity event right now. Will give it a shot when I get home. Fingers crossed.
[Verizon Samsung Galaxy S 4] Toddricks:
Fails in nand. Odin fail