yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini General] DroidJP:
Oh, if you want the original sgh-t599n stock param here it is in this thread

http://xdaforums.com/showthread.php?t=2407389&page=20

i've downloaded but the zip is not cwm/twrp its just the file by itself. If only i can flash it. if you even go to page one this guy extracted the entire images of this phone to download too. How do you make this file cwm/twrp flashable?

Update: Disregard. Thanks Man! this zip fixed it!.
[Galaxy S III Mini General] danielryanhernandez:
t599-?

Does this work on all sgh-t559-'s? I have sgh-t599n?
[Galaxy S III Mini General] KageBeast:
That's why it's t599- meaning yes it does.
[Galaxy S III Mini General] JairoAV25:
Error Flashing SGH-T599N

Hi all,

I'm trying to flash my stock Exhibit and only gets Failed message from Odin 3.10.

Any help would be appreciated.

Thanks in advance.
[Galaxy S III Mini General] chargeee:
Hi i downloaded this recovery and flashed it ino my 599n and now iam in complete bootloop, trie everything, if i install ROM that acutally not complaining that i have wrong recovery, still gettin back to cwm, so, great, probably nothing to do right
[Galaxy S III Mini General] lowvoice:
Philz touch I know works on sgh-t599n
[Galaxy S III Mini General] whodisname:
Hey guys. I have a request. My sister has this phone and she wanted me to fix it for the longest and I kept putting it off. She passed last week. I'd like to get a zip file for philz touch or twrp to duty on it. It has cwm and it all error 7 problems. (I absolutely have the right ROM) its just a thing I want to do if anyone cod help me I'd appreciate it. Thank you. here are some specifics of whats wrong here. Im familiar with how to mess with these devices quite a bit. anyhow..

it has cwm. it wont flash anything. I get error 7 for everything either imidiatly or after around 20 seconds of trying to fool with it.

instead of download mode, I get

POWER RESET or UNKNOWN UPLOAD MODE. odin appears to connect but stops at initializing connection". im looking for a zip file recovery that I know is good so I can try that. didn't mean to make the post so gloomy, its just an thing. I really wanna fix this phone now.
[Galaxy S III Mini General] whodisname:
If someone can help me wilh a link to some of these old files I'd appreciate it. You would be helping me out a lot too just for what it is. Thanks. Any questions or anything you can pm me or I'm subscribed to his thread.
[Galaxy S III Mini General] :
Just graduated here, heading off to university this September. The files are finally uploaded onto the drop-box. Let me know if you need any other files.

Indeed it is, I was actually thinking of buying another phone that has other roms, but now I don't have to.
[Galaxy S III Mini General] Unjustified Dev:
My mom pawned my laptop no other PC can build they are too slow and weak I still can try to tar it up. I have Ubuntu on a desktop dual booting

Why is cache.IMG so large lol I think you may need a clean one as well.
[Galaxy S III Mini General] :
On it, anything else seems unusually large?

Edit: It's still coming up as 720 mb.
[Galaxy S III Mini General] Unjustified Dev:
I can't do it the desktop is so slow and its freezing downloading I guess you guys have to wait till this weekend when I get my laptop back :(
[Galaxy S III Mini General] tys0n:
It's because of dd. The whole block gets extracted.

It would be same size even if it's empty. It can probably be edited with hexeditor, removing all 00 to reduce size if you know how to do it.

I think the *tar.md5 should be normal size anyway, as all zero bytes gets compressed to nothing.
[Galaxy S III Mini General] :
Are you just adding them all to one tar or is there a specific process to it? With some guidance, I can attempt it once I get ubuntu reinstalled.
[Galaxy S III Mini General] tys0n:
I use these in cygwin.

tar -H ustar -c image_1 [image_2 ...] > ******.tar
md5sum -t ******.tar >> ******.tar
mv ******.tar ******.tar.md5

Could you please also dd mmcblk0p3 and save it as codinatmo.pit ?

Let's see if i'm right about this..
[Galaxy S III Mini General] :
I've had difficulty setting up cygwin, but I'll revisit that.

Done, it's in the dropbox folder.

https://www.dropbox.com/sh/2cb96xyih7heg5i/oeIGkqM1Vs
[Galaxy S III Mini General] tys0n:
Yup, it was the pit file but I noticed when I opened it that it's name should be "codinavid.pit". It's the partition information table to use with odin if partitions get's *****d up bad. Should only be flashed with full firmware and NEVER if it's not neened.

Then I believe we can find STE_boot1.img at mmcblk0p5

and STE_boot2.img at mmcblk0p6.

Looking good :D
[Galaxy S III Mini General] :
Uploaded into the drop box. Are they supposed to be that small?
[Galaxy S III Mini General] tys0n:
Yes it's small. Block is 0.5mb, but accual filesize in firmware is only 384 kB.

---------- Post added at 02:13 AM ---------- Previous post was at 02:01 AM ----------

boot.img

STE_boot1.img

STE_boot2.img

recovery.img

modem.bin

cache.img

system.img

.........What's missing for a stock odin fw is "hidden.img"..in mmcblk0p24 i think.

Should be around 100mb.
[Galaxy S III Mini General] :
Uploaded to dropbox as well: https://www.dropbox.com/sh/2cb96xyih7heg5i/oeIGkqM1Vs
[Galaxy S III Mini General] tys0n:
Looks like I was totally wrong about compressed zeros. The tar came out at 2gb. :silly:
[Galaxy S III Mini General] :
That might make sense since the phone comes with 1.34 gb of usable space, and the phone is said to have 4gb memory.
[Galaxy S III Mini General] tys0n:
Looks good though :good:
[Galaxy S III Mini General] :
So is that everything that's required for the stock firmware?
[Galaxy S III Mini General] tys0n:
That is everything that's in stock firmware for i8190 which is basicly the same device, so yeah I think so.

Anyone with a bricked T599 who want's to try it? :p
[Galaxy S III Mini General] :
I recall that a user named pedrin92, in the system dump thread mentioned he had bricked his phone. Perhaps he'd like to try?
[Galaxy S III Mini General] tys0n:
The *.pit amd param and everything else is good to keep, but those partitions shouldn't be messed up by flashing a zip, unless you brick it by flashing some sh*t for a device with different partition layout.
[Galaxy S III Mini General] :
He's currently online in the other thread: http://xdaforums.com/showthread.php?t=2407389&page=9
[Galaxy S III Mini General] tys0n:
Yeah, may be. I'm uploading it now and post a link when it's done.

The pit file in your phone knows which file goes where so just load it in odin as PDA. F reset and auto reboot should be ticked. Make sure battery is loaded over 60%.Put the phone in download mode (vol-/home/power), and connect usb to phone. Hit start in Odin and wait for it to finish.
[Galaxy S III Mini General] :
Alright, I'll try it out.

Edit: Flashed okay.
[Galaxy S III Mini General] tys0n:
Aah, you made your own *.tar?

It worked fine?
[Galaxy S III Mini General] :
Yes sir, everything seems fine and seems to be working.
[Galaxy S III Mini General] tys0n:
[rom][cwm]t599_uvamb5[stock]

GREAT! :)

Then I can put this out in the air...SGH-T599_UVAMB5.zip

Stock rom. Deodexed and zipaligned. Added SuperSu and Su binary, busybox.

Flash in your CWM recovery.
[Galaxy S III Mini General] :
Awesome, I'll try flashing that as well.

Edit: Download randomly stopped, have to redownload, so this may take a bit.
[Galaxy S III Mini General] Unjustified Dev:
After seeing this progress I am going to work on dual boot this weekend when and if I get this phone plus my laptop
[Galaxy S III Mini General] :
Edit: It was in a boot-loop. Ended up flashing stock firmware.

Awesome!
[Galaxy S III Mini General] tys0n:
Hmm ok :/ I'm not at home now. Can't remember if I made automatic wipe of cache and dalvik.

You could try that if you haven't done that prior to flash.

Sent through time and space from my s3mini/CM10.1
[Galaxy S III Mini General] :
Still in a boot loop.
[Galaxy S III Mini General] tys0n:
Ok. I'll take it down for now and have a look at it when I get home. Sorry..

Sent through time and space from my s3mini/CM10.1
[Galaxy S III Mini General] Unjustified Dev:
Try to get a logcat if possible
[Galaxy S III Mini General] tys0n:
It looks like there's two different models.

ROM Name : JZO54K.T599VVLAME3

CSC version : T599VYVLAME3

ro.product.model=SGH-T599V

ro.product.device=codinavid

ROM Name : JZO54K.T599UVAMB5

CSC Version : T599TMBAMB5

ro.product.model=SGH-T599

ro.product.device=codinatmo
[Galaxy S III Mini General] Unjustified Dev:
[MENTION=3245411]tys0n[/MENTION] that's true I may pull it from Samsung source and look I pulled mb5 because I knew it was the T-Mobile version

Some users also had t599v on their responses so I actually don't know what carrier that is

Tamil.soljahz has the t599v
[Galaxy S III Mini General] tys0n:
Ok. Maybe that's why my deodexed rom went to bootloop.

It was made from the MB5 but I think [MENTION=5354456]tamil.soljahz[/MENTION] got the T599V.
[Galaxy S III Mini General] Unjustified Dev:
Yep it says t599v from one post but here's the defconfig https://github.com/TeamRegular/andr.../cm-10.1/arch/arm/configs/codinavid_defconfig shouldn't be much difference though I built cwm with the provided boot and it works. Maybe its another issue why it didn't work

I'll compare them at school and see the differences
[Galaxy S III Mini General] tys0n:
Samsung US presents SGH-T599 as Samsung Galaxy Exhibit™ (T-Mobile)

Samsung CA presents SGH-T599V as GALAXY Ace II e

What's that about? :eek:

Untill this gets sorted out I'm taking the Odin firmware offline. If this is correct the odin-file would then be done for T599V.
[Galaxy S III Mini General] Unjustified Dev:
The Odin worked for the T-Mobile its linked in my cwm thread the guy that looped pm'ed it worked wait I haven't downloaded it myself :D

I thought it was your zip that looped him ? You have to be on stock recovery first seen it in a s3 mini thread I will have an insecure boot.IMG made today
[Galaxy S III Mini General] tys0n:
build.prop from the odin-rom I made.

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.T599VVLAME3
ro.build.version.incremental=T599VVLAME3
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Thu May 9 21:53:47 KST 2013
ro.build.date.utc=1368104027
ro.build.type=user
ro.build.user=se.infra
ro.build.host=QBAGENT175
ro.build.tags=release-keys
ro.build.changelist=1195349
ro.product.model=SGH-T599V
ro.product.brand=samsung
ro.product.name=codinavid
ro.product.device=codinavid
ro.product.board=DB8520H
ro.product.cpu.abi=armeabi-v7a
# Samsung Specific Properties
ro.build.PDA=T599VVLAME3
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=montblanc
# ro.build.product is obsolete; use ro.product.device
ro.build.product=codinavid
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=codinavid-user 4.1.2 JZO54K T599VVLAME3 release-keys
ro.build.fingerprint=samsung/codinavid/codinavid:4.1.2/JZO54K/T599VVLAME3:user/release-keys
ro.build.characteristics=vid
# end build properties

Rebranded phone,YAY :)

I'll give you a link in PM.
[Galaxy S III Mini General] Unjustified Dev:
Well it worked so its most likely similar to the s4 their ROMs work on each other with minimal issues. The ace 2 is not it . The t599v is a different country I believe . There are more exhibits according to the kernel like 3 more and codina is a galaxy ace I think or just a base defconfig for a line of exhibit phones I will compare them all at school
[Galaxy S III Mini General] tys0n:
Ok so it's confirmed to work even on the T599 then?

- the T-mobile addons, as apps and so.
[Galaxy S III Mini General] Unjustified Dev:
Idk about all of that I will ask if necessary :D .

t599v says galaxy ace 2e weird enough I doubt Tamil missed a box saying that so there is no t599v on open source just t599 and t599n . I thought it was your zip that bricked and not the Odin stock
[Galaxy S III Mini General] tys0n:
Well, I can make another one for T599 also if someone give me the .img's from it.

They got different apps and csc. OTA updates and kies will recognise it wrong.
[Galaxy S III Mini General] Unjustified Dev:
Hopefully I can get one but could you send me a list of partitions with all the images?
[Galaxy S III Mini General] tys0n:
Will do when I get back home later today.

Sent through time and space from my s3mini/CM10.1
[Galaxy S III Mini General] Unjustified Dev:
I want my signature like yours soon though leaving with my dad this weekend

Sent through time and space from my galaxy exhibit/CM10.1
[Galaxy S III Mini General] :
Yes, you're right I have the SGH-T599v.

Edit: I didn't have the box, and I searched it up which lead me to this forum, but you're right in canada it's branded as the Galaxy Ace 2 e. Is it really that much of a difference between the phones?
[Galaxy S III Mini General] Unjustified Dev:
I dont think so but I will see the defconigs
[Galaxy S III Mini General] tys0n:
It can't be much difference. Soon we'll know.

Here's what I got regarding partitions.

From tamil.soljahz outcome of "cat /proc/partitions", compared from my outcome on i8190, and from looking at your pit-file:

SGH-T599:
/proc/partitions

major minor #blocks name

7 0 5229 loop0
179 0 3866624 mmcblk0
179 1 128 mmcblk0p1 - MBR,GPT
179 2 384 mmcblk0p2 - MasterTOC - STE_boot.bin
179 3 1024 mmcblk0p3 - codinavid.pit / codinatmo.pit (device dependent)
179 4 1024 mmcblk0p4 - md5.img
179 5 512 mmcblk0p5 - STE_boot1.img
179 6 512 mmcblk0p6 - STE_boot2.img
179 7 512 mmcblk0p7 - dnt.ssw
179 8 512 mmcblk0p8 - reserved
179 9 1024 mmcblk0p9 - cspsa.img
179 10 1024 mmcblk0p10 - cspsa2.img
179 11 16384 mmcblk0p11 - EFS.img
179 12 16384 mmcblk0p12 - modemfs.img
179 13 16384 mmcblk0p13 - modemfs2.img
179 14 51200 mmcblk0p14 - ssgtest.img
179 15 64 mmcblk0p15 - ipl.bin
179 16 14336 mmcblk0p16 - modem.bin
179 17 2048 mmcblk0p17 - normal.bin
179 18 2048 mmcblk0p18 - normal2.bin
179 19 16384 mmcblk0p19 - param.lfs
179 20 16384 mmcblk0p20 - boot.img
179 21 16384 mmcblk0p21 - recovery.img
179 22 1228800 mmcblk0p22 - system.img
179 23 737280 mmcblk0p23 - cache.img
179 24 102400 mmcblk0p24 - hidden.img
179 25 1535983 mmcblk0p25 - userdata.img
179 64 2048 mmcblk0boot1
179 32 2048 mmcblk0boot0
179 96 15637504 mmcblk1
179 97 15633408 mmcblk1p1
254 0 5229 dm-0

After I made your pit more readable:View attachment 2223578

The odin service firmvare for i8190 looks like this:

STE_boot.bin...I don't know where it fits. Could it be something combined for block 01/02?

STE_boot.bin goes to MasterToc. Just looked it up with hex.
[Galaxy S III Mini General] Unjustified Dev:
Thanks will save this would be nice to get t599 and t599v user to pull these files from stock so we can make an stock tar that has all the correct files
[Galaxy S III Mini General] Unjustified Dev:
Did you get it booted if not odin the tar from cwm thread a user confirmed it working I doubt canada version makes a difference just like the galaxy s4 versions I installed a sprint rom on the cspire version with no issues except service . So it seems we need to make a codina-common folder and separate trees for codinatmo and codinavid

the other phones are

codinanewcotmo_defconfig - MetroPCS Exhibit .NewCo or Newco is a generic name for proposed corporate spin-off, startup, or subsidiary companies before they are assigned a final name, or to proposed merged companies to distinguish the to-be-formed combined entity with an existing company involved in the merger which may have the same (or a similar) name. In a handful of cases the new company may retain the name "Newco". Tmo is saying it is the tmobile version as well since they just merged coverage with them , metro PCs that is

codinatmo_defconfig -Tmobile Exhibit

codinavid_defconfig - Canada Videotron Galaxy Ace IIe same board as t599 with t599v companies can change their device names

codina_defconfig- I think its what they use to base the other defconfigs like if another company wanted this phone
[Galaxy S III Mini General] tys0n:
The odin tar is made with the files for T599V that tamil.soljahz shared from his dropbox.

The other systemdump from goldfingerfif is from T599, but it's not in .img format and was missing a few partitions.

It got labeled wrong as I thought it was only one model and same firmware.
[Galaxy S III Mini General] camaro322hp:
I have a rooted T599 (T-Mo USA version, not the V). I can try to help if you guys need some files from it, however, I'm pretty new to all this so would need detailed instructions of how to get the files.
[Galaxy S III Mini General] Unjustified Dev:
Tyson will be here in a while he is the expert on pulling imaged as well as Tamil. I have not got this phone yet . If you want you can install cwm and have fun I will add init.d to the kernel today if possible should help and if possible send a kernel with some governors added
[Galaxy S III Mini General] :
Are you just trying to build a stock odin for the T599? With the help of tys0n i made it for the t599v, so I could assist him with that.
[Galaxy S III Mini General] Unjustified Dev:
Yeah is your phone working?
[Galaxy S III Mini General] :
Yeah, I flashed the stock odin I made (well recreated tys0ns since I didn't want to wait for him to upload it and download it again).
[Galaxy S III Mini General] Unjustified Dev:
LOL :) I downloaded it too. About to upload a stock kernel with init.d so you all can have some tweaks

btw try to make a stock based of ty0ns new info for the stock odin he has all the partitions and such . No need for sdcard img unless your sharing info :)
[Galaxy S III Mini General] :
On it, oh I was meaning to ask is your version of CM compatible with my phone or just the tmobile variant? If so, seeing how I have a stock odin, I dont mind testing it out.
[Galaxy S III Mini General] Unjustified Dev:
No pc remember.... My mom pawned my laptop with all my code , roms ,and personal info and linux is unlocked by default so they have access to it I really hope they respect me by keeping out of my pc
[Galaxy S III Mini General] tys0n:
For anyone that has a rooted SGH-T599(tmo) and adb going, please backup:

cd "whatever/ dir/ you/ got/ adb"

adb shell

su

dd if=/dev/block/mmcblk0p2 of=/extSdCard/STE_boot.bin

dd if=/dev/block/mmcblk0p3 of=/extSdCard/codinatmo.pit

dd if=/dev/block/mmcblk0p5 of=/extSdCard/STE_boot1.img

dd if=/dev/block/mmcblk0p6 of=/extSdCard/STE_boot2.img

dd if=/dev/block/mmcblk0p16 of=/extSdCard/modem.bin Can take it from goldfingerfif thread

dd if=/dev/block/mmcblk0p19 of=/extSdCard/param.lfs Can take it from goldfingerfif thread

dd if=/dev/block/mmcblk0p20 of=/extSdCard/boot.img (I need a secure, non modified boot.img)

dd if=/dev/block/mmcblk0p21 of=/extSdCard/recovery.img Can take it from goldfingerfif thread

dd if=/dev/block/mmcblk0p22 of=/extSdCard/system.img

dd if=/dev/block/mmcblk0p24 of=/extSdCard/hidden.img Can take it from goldfingerfif thread

exit

exit

adb pull /extSdCard/STE_boot.bin

adb pull /extSdCard/codinatmo.pit

adb pull /extSdCard/STE_boot1.img

adb pull /extSdCard/STE_boot2.img

adb pull /extSdCard/boot.img

adb pull /extSdCard/system.img

exit

Now you can delete it from your external sd. zip them and upload it somewhere.

I can take cache.img that i have. It's empty anyway.

If no one got a secure boot.img I can unpack it, change ro.secure and repack.

STE_boot files is most likely the same, but i prefer to safe.

This is enough to tar an odinfile, to start with.

The rest can be backed up later.
[Galaxy S III Mini General] Unjustified Dev:
Could you link me to what you use to unpack all my tools won't repack and the kitchen I used is jacked up

?
[Galaxy S III Mini General] Unjustified Dev:
[MENTION=5354456]tamil.soljahz[/MENTION]

TEST:Insecure boot.img with init.d support and busybox now you can toy with xposed modules

DOWNLOAD: http://d-h.st/3oG

It has the modified init.rc to import.cm.rc
[Galaxy S III Mini General] tys0n:
I just use kitchen in cygwin and hexeditor so it's nothing fancy :D

There's also this universal init.d .
[Galaxy S III Mini General] Unjustified Dev:
That's cool still they needed it I didn't upload sysinit I forgot but now it may be better that way since its insecure with adb on boot
[Galaxy S III Mini General] tys0n:
Yeah I need adb to work, but if you're not an "advanced" user then the universal init.d should be enough to add scripts and use link2sd etc.
[Galaxy S III Mini General] Unjustified Dev:
Yeah that's nice btw do you have Linux?
[Galaxy S III Mini General] tedparkes:
Hello,

Sorry to distract you, but I was curious if any of you know if this phone is currently rootable. I have the MetroPCS version of the t599n. This is the only thread on I could find on google with people actively working on the phone, so I am asking here for that reason. I do not mean to derail your rather advanced discussion.

Thank you,

Ted.
[Galaxy S III Mini General] tys0n:
No linux, yet..

Haha, No worries. You should be able to root it with cydia impactor, or flash cwm in odin and then flash SuperSu.zip

Maybe cydia is to prefer, but I think cwm shold work on T599N as well.
[Galaxy S III Mini General] camaro322hp:
I'm trying to get these files, but when I run dd if=/dev/block/mmcblk0p2 of=/extSdCard/STE_boot.bin, I get the following message:

cannot open for write: No such file or directory

Not sure why, because I do have an extSdCard directory. What am I doing wrong?

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

I'm not sure 100% on the t599n, but I used Cydia Impactor to root my T-Mo t599. I suspect it should work on yours.
[Galaxy S III Mini General] tys0n:
Oh my fault. It should probably be :

dd if=/dev/block/mmcblk0p2 of=/storage/extSdCard/STE_boot.bin

I'm not used to stock rom :P
[Galaxy S III Mini General] george2019:
as you made a backup of these files
[Galaxy S III Mini General] tys0n:
No i haven't. I don't own this phone but I would like to get a hold of them so I can make an Odin firmware for it. T599(tmobile).

Sent through time and space from my s3mini/CM10.1
[Galaxy S III Mini General] drevil00:
currently pulling all these files will upload them and link them in a little bit

having issues with the system.img updated a system app accidently through link2sd and now phone keeps getting hung up on boot up
[Galaxy S III Mini General] tys0n:
Oh..system apps on external sd doesn't sound so good. You know which app?

You got a nandroid backup to restore in cwm?

Edit: If you know which apk you should be able to delete the link2sd mountscript in /etc/init.d through adb and push the apk & odex file to /system
[Galaxy S III Mini General] drevil00:
Unfortunately I dont know which one it was, good thing is that the wife has the same phone so I will get those files tomorrow from her phone

The problem is that in link2sd you have the option to replace the old system app with an updated version, i accidently did this with one of the apps not realizing i was in the system directory. I wish that i had moved the app instead...would be easier to fix than this
[Galaxy S III Mini General] camaro322hp:
I'm still getting the same error message with the /storage in front of the path. I've attached a screenshot of my command prompt window.
[Galaxy S III Mini General] :
I think that there may already be a file on your sd card called STE_boot.bin delete that, and try again.
[Galaxy S III Mini General] camaro322hp:
No, that file is not already there. My phone is connected in stock recovery mode, is that correct?
[Galaxy S III Mini General] tys0n:
I think you need cwm to use adb shell conmands. Terminal emulator on phone works too, but I think adb is easier.

Sent through time and space from my s3mini/CM10.1
[Galaxy S III Mini General] camaro322hp:
OK, I used Terminal Emulator, and it worked. I have all the files you requested. Suggestions on where to upload them? Or I could share my google drive with you and you could get them there?

One other rookie question - these files don't contain any of my sensitive information, do they? Like email passwords and such? Just want to make sure I'm not publishing any of my personal info.