yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
Ok, more info. found info on dumping partitions names

used:

ls -l /dev/block/platform/msm_sdcc.1/by-name > /mnt/sdcard/partitions.txt

partitions are as follow:

lrwxrwxrwx root root 2013-01-02 01:11 aboot -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2013-01-02 01:11 backup -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2013-01-02 01:11 boot -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2013-01-02 01:11 cache -> /dev/block/mmcblk0p21

lrwxrwxrwx root root 2013-01-02 01:11 efs -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2013-01-02 01:11 fota -> /dev/block/mmcblk0p15

lrwxrwxrwx root root 2013-01-02 01:11 fsg -> /dev/block/mmcblk0p17

lrwxrwxrwx root root 2013-01-02 01:11 hidden -> /dev/block/mmcblk0p22

lrwxrwxrwx root root 2013-01-02 01:11 modem -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2013-01-02 01:11 modemst1 -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2013-01-02 01:11 modemst2 -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2013-01-02 01:11 pad -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2013-01-02 01:11 param -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2013-01-02 01:11 persist -> /dev/block/mmcblk0p19

lrwxrwxrwx root root 2013-01-02 01:11 recovery -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2013-01-02 01:11 rpm -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2013-01-02 01:11 sbl1 -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2013-01-02 01:11 sbl2 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2013-01-02 01:11 sbl3 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2013-01-02 01:11 ssd -> /dev/block/mmcblk0p18

lrwxrwxrwx root root 2013-01-02 01:11 system -> /dev/block/mmcblk0p20

lrwxrwxrwx root root 2013-01-02 01:11 tz -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2013-01-02 01:11 userdata -> /dev/block/mmcblk0p23

Here is dump of recovery partition... now if someone smarter than me can let me know wher to send this to get a version of cwm or touch built.

Dump created with command:

df if=/dev/block/mmcblk0p14 of=/mt/sdcard/stock-recovery.img

upate: here is the boot image dump.. not sure why both dumps are coming out exactly 10 meg.. is dd limited. or am i doing something wrong:

Also i have a dump with tar of the entire /sytem (too big to store here)

Although, system has been modified with some bloat removed (saved in a save directory) and also additions: superuser, busybox, news and weather widget and lbstestmode to set gps stuff.

anyone know where i can upload it.
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
come on someone.. really need a cwm recovery
[Galaxy S III Mini Q&A, Help & Troubleshooting] dylan07:
I just got this SM-G730A 2 weeks ago. I would like to put CyanogenMod 10 on it. How far are developers from releasing a ROM for it? I have a small amount of knowledge in programming and could practice on my phone.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
CWM build server seems to be down so can't test build one.

Here's the content of recovery ramdisk View attachment 2314991
[Galaxy S III Mini Q&A, Help & Troubleshooting] AssToast:
Like really far, only a few people who own this device
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
oh by the way the batteries are same size as 1500mah ones ..I got a couple and they fit and work in new phone so the 2000mah batteries for the g730a should work in your older phones. Samsung USA has them for sale and in stock. I ordered a couple and the order already shipped.
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
one of the reasons I'm looking for recovery . yesterday my wifi access pts were gone suddenly on my sgs III so I restored them from titanium.. but then

after that later that day noticed Gps was not working the gps icon would not flash.. no satellites were found and even after reboot nothing. even though GPS was enabled. obviously something got hosed in the system..luckily after a cwm 3 month old restore, and a couple of hours of updating and configuring I am working and back to normal.. long story short if something like this happens on new phone with no cwm back up or stock fw to flash it is fubared.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Can you do "cat /proc/partitions" so we can get partition sizes?

Maybe "busybox df -h" as well.
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
will do tonight and post.. it is my wifes phone in her possession today.
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
ok requested files
[Galaxy S III Mini Q&A, Help & Troubleshooting] clickclickpc:
Has this method for root also been tested on the SM-G730A? Considering picking one of these mini's up.
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
ya sorry that is a typo I have the 730a. there is no 740a

Sent from my SAMSUNG-SGH-I747
[Galaxy S III Mini Q&A, Help & Troubleshooting] clickclickpc:
Thanks, Pal. Just wanted to make sure there wasn't yet another SIII mini model out there.
[Galaxy S III Mini Q&A, Help & Troubleshooting] theodoeshutup:
i follow your guide, follow the other guy's guide like you said, and i get a secure fail: recovery error or something like that. i really regret buying this model now.
[Galaxy S III Mini Q&A, Help & Troubleshooting] nico_vas:
Confused

I tied to use the method provided in the link you posted and i believe the recovery file is for international versionsof the s3 mini and i get a fail message every time i try to flash the recovery in odin. Am i missing something here? (i am using model SM-G730A)
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
Ya you are.. there is no recovery for this phone yet..have you even been reading this thread.. why do you think I did research and determined the partition layout is different.. you are lucky you didnt brick your phone and I have no idea what damage you would habe done flashing recovery over the wrong partition.

Sent from my GT-N8013
[Galaxy S III Mini Q&A, Help & Troubleshooting] clickclickpc:
lgkahn,

By the way, do you recall in the thread you referenced below, where the one-click file is located or what post number it was? Or was it from the toolkit instead?

http://xdaforums.com/show...7852&nocache=1

Found the root.zip in the OP but without CWM, I don't think the stock recovery can flash it. I couldn't locate the one-click.
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
strange I don't see it in that thread anylonger.. here is a direct link to the one click root

http://xdaforums.com/showthread.php?t=2459910&highlight=+one+click+
[Galaxy S III Mini Q&A, Help & Troubleshooting] yakmon:
This worked for me. If you get yours rooted and install Titanium backup, can you make a backup of an empty "contact storage" app from your G730A ?

I uninstalled mine by mistake.
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
pm sent
[Galaxy S III Mini Q&A, Help & Troubleshooting] t0ne420:
where you able to root your s3 mini?
[Galaxy S III Mini Q&A, Help & Troubleshooting] ttsstr5:
Need a little help

Ok so I have a Samsung galaxy s III mini

Model: SM-G730A

Andriod version: 4.2.2

I had it rooted and wanted to install recovery-clockwork-touch-6.0.2.7-golden, cm10.1_golden.maclaw.20131019, and gapps-jb-20130812-signed. I can not get it to install the recovery even through Odin. Any help with this would be appreciated. I am sure it is just something I am over looking as this is not my first time rooting and installing custom roms, but it is my first Samsung so not sure if there are different steps but everything I am finding is for a different build.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
There is nothing done for SM-G730A yet.

You're trying to flash files for i8190 which will not work for your device. It may even brick it..

Sent through time and space from my s3mini/CM10.2
[Galaxy S III Mini Q&A, Help & Troubleshooting] ttsstr5:
I thought so

That's what I thought was wrong :( when I googled it those were the only files that said anything about SM-G730A. Luckily none of it installed :)
[Galaxy S III Mini Q&A, Help & Troubleshooting] alexischino:
the worst part is there is no way to unbrick the phone because there is not even a stock firmware to flash with Odin.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Boot and recovery is dumped so hopefully someone build a cwm for you soon.

---------- Post added at 07:36 AM ---------- Previous post was at 07:21 AM ----------

If we knew more about the partitions and what filesystem is used then it would be easier. There's no PIT file or something that can tell us what images it used in odin?
[Galaxy S III Mini Q&A, Help & Troubleshooting] alexischino:
ok i will try to do my part to help in the development for this device, i have (3) SM-G730A devices the one I'm using now and 2 more completely new they are completely sealed I'm going to use this one for testing, I'm waiting for my new laptop to be delivered.
[Galaxy S III Mini Q&A, Help & Troubleshooting] MikeyRay13:
I managed to get SuperSU installed, and Explorer, but I can't delete chinese superuser?
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
root explorer. not sure what explorer is.. you need to make the system writeable first at top of root explorer..
[Galaxy S III Mini Q&A, Help & Troubleshooting] MikeyRay13:
Okay I got Root Explorer, deleted the Chinese SU, but when I try to update binaries on SuperSU, or Superuser, they both fail. Any ideas?
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
is supersu getting root privilage.. did you make sure to wait to update it and make sure it had priviledges b4 you deleted superuser.. I am having no such problems... also try installing this first;

https://play.google.com/store/apps/details?id=stericson.busybox
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
recovery

recovery builder is back up so tried it with stock recovery.. did figure out phone was called something like goldenlteatt

see below

but it failed because it doesnt know anything about it not even the cpu .

Unpacking recovery image.

Android magic found at: 0

BOARD_KERNEL_CMDLINE console=null androidboot.hardware=qcom user_debug=31

BOARD_KERNEL_BASE 80200000

BOARD_PAGE_SIZE 2048

/Volumes/Data/hudson/workspace/android/cm-10.2 /Volumes/Data/hudson/workspace/android/cm-10.2

5662 blocks

/Volumes/Data/hudson/workspace/android/cm-10.2

MANUFACTURER: samsung

DEVICE: goldenlteatt

Arguments: samsung goldenlteatt /tmp/recovery.img

http://http://jenkins.cyanogenmod.com/job/recovery/44952
[Galaxy S III Mini Q&A, Help & Troubleshooting] assassinanex:
ya i tried it yesterday too and it failed
[Galaxy S III Mini Q&A, Help & Troubleshooting] lgkahn:
checked the cpu is a dual core smapdragon 400 so the cpu config should be krait.. but I cannot figure out a way to set it or pass it in to the builder.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Can anyone of you owners post the outcome of:

fdisk -l /dev/block/mmcblk0p20

Thanks in advance
[Galaxy S III Mini Q&A, Help & Troubleshooting] comZ:
lgkahn, thanks for posting the root instructions!! It worked very well. Looking forward to cwm here too..

tys0n, "fdisk -l" produces no output, and "fdisk -l /dev/block/mmcblk0p20" produces:

root@android:/ # fdisk -l /dev/block/mmcblk0p20

Disk /dev/block/mmcblk0p20: 1384 MB, 1384120320 bytes
4 heads, 16 sectors/track, 42240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p20 doesn't contain a valid partition table

Got any more questions?
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
I could need a backup of pit-file which I believe is in mmcblk0p3.

dd if=/dev/block/mmcblk0p3 of=/mt/sdcard/mmcblk0p3
[Galaxy S III Mini Q&A, Help & Troubleshooting] comZ:
I passed the output through "strings" and uploaded it to a pastebin @ sprunge.us/ZWjc Not sure if that's the output you were looking for.

Want to meet up on #xda-devs so I give you these dumps faster and without concern that I'm uploading my account info publicly? I know I should really reset my phone to stock, but this could be an interim solution.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Problem is I can hardly connect to anything on this totally crappy line I'm on right now..I'm glad I can get in to xda haha.

can you zip the file and add it to your post maybe? Need the pit-file to see if Odin is looking for system.img or system.img. ext4

Maybe it's even easier to get the pit from phone with heimdall.

Sent through time and space from my s3mini/CM10.2
[Galaxy S III Mini Q&A, Help & Troubleshooting] comZ:
Not sure how to upload files here, but I uploaded mmcblk0p3 to sprunge.us/fVbc

Is that the right block? From the stringed output I sent before, it didn't seem to have partition information.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Yeah, you're right. That was wrong partition :/

---------- Post added at 06:29 PM ---------- Previous post was at 06:15 PM ----------

I'm pretty sure it should be in mmcblk0p1-mmcblk0p4 since they're not listed in partition list. They should all be small partitions to backup.
[Galaxy S III Mini Q&A, Help & Troubleshooting] comZ:
merchaant endencms

If it helps at all, this is what I tried:

130|root@android:/ # strings /dev/block/mmcblk0 | grep system.img
system.img.ext4

Doesn't help reveal where the PIT is, but at least that may answer your question about system.img or system.img.ext4

---------- Post added at 01:37 PM ---------- Previous post was at 01:30 PM ----------

I did "strings /dev/block/mmcblk0p{1-4} | grep system.img" and they each returned nothing.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Hmm yeah I was wrong. 0p3 is SBL2 :P

Pit must be somewhere and it will tell exactly what format each partition needs to be flashed in odin. (*.bin, *.img, *.img.ext4, *.mbn ) etc..

Found this so I wonder if galaxy mega shares the same pit. MSM8930.pit

http://xdaforums.com/showpost.php?p=47093607&postcount=631
[Galaxy S III Mini Q&A, Help & Troubleshooting] krayzieiyian23:
hey if i can help in any way to keep this thread going im willing to try to get a whole system dump and android kitchen and stuff to help out.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Try this and see if you get a odin flashable system dump. I know it works for i9500 and other devices.

Outcome from

fdisk -l /dev/block/mmcblk0p20
Disk /dev/block/mmcblk0p20: 1384 MB, 1384120320 bytes
4 heads, 16 sectors/track, 42240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Now we know size.

Try this to dump:

su
make_ext4fs -s -l 1384M -a system /sdcard/system.img.ext4 /system
[Galaxy S III Mini Q&A, Help & Troubleshooting] krayzieiyian23:
when i try your first command it says fdisk not found... is that the size for the g730a? can i just do the second line?

i did it and this is what i got out of it

Microsoft Windows [Version 6.1.7601]

Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Program Files\Minimal ADB and Fastboot>adb shell

adb server is out of date. killing...

* daemon started successfully *

shell@android:/ $ fdisk -l /dev/block/mmcblk0p20

fdisk -l /dev/block/mmcblk0p20

/system/bin/sh: fdisk: not found

127|shell@android:/ $ -l /dev/block/mmcblk0p20

-l /dev/block/mmcblk0p20

/system/bin/sh: -l: not found

127|shell@android:/ $ su

su

shell@android:/ # fdisk -l /dev/block/mmcblk0p20

fdisk -l /dev/block/mmcblk0p20

sh: fdisk: not found

127|shell@android:/ # make_ext4fs -s -l 1384M -a system /sdcard/system.img.ext4

/system

ystem /sdcard/system.img.ext4 /system <

Creating filesystem with parameters:

Size: 1451229184

Block size: 4096

Blocks per group: 32768

Inodes per group: 8064

Inode size: 256

Journal blocks: 5536

Label:

FLEX_BG size: 16

Blocks: 354304

Block groups: 11

Reserved block group size: 0

Created filesystem with 2672/88704 inodes and 309791/354304 blocks

---------- Post added at 02:17 PM ---------- Previous post was at 02:05 PM ----------

i have the file on my internal storage. is there anyway i can change the file extension to post it on here without corrupting it?
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
I don't have the device, otherwise I would try to tar it up and see if odin accept it, but please zip it and upload so others can take a look at it if they want or need :good:
[Galaxy S III Mini Q&A, Help & Troubleshooting] bleuninja:
binary

was wondering if there was a way to delete the chinese binary after installing or does busybox delete the old binarys when it installs. I think when installing the chinese root . it creates errors because the files uploaded are chinese and the phone is english . i really want to try this but i ould hate to have some flaws. i depend on this phone allot. i have rooted and installed custom roms on all 4 phones successfully so far. sux there isnt a rom for this yet and a good way to root this. att bloatware is well as yall know sux lol.
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Install SuperSu from play, and I think it will ask if you want to update SU binary.
[Galaxy S III Mini Q&A, Help & Troubleshooting] haffinator:
root@android:/ # fdisk -l /dev/block/mmcblk0p20
fdisk -l /dev/block/mmcblk0p20

Disk /dev/block/mmcblk0p20: 1384 MB, 1384120320 bytes
4 heads, 16 sectors/track, 42240 cylinders
Units = cylinders of 64 * 512 = 32768 bytes

Disk /dev/block/mmcblk0p20 doesn't contain a valid partition table

root@android:/ # make_ext4fs -s -l 1384M -a system /sdcard/system.img.ext4 /system
em /sdcard/system.img.ext4 /system <
Creating filesystem with parameters:
Size: 1451229184
Block size: 4096
Blocks per group: 32768
Inodes per group: 8064
Inode size: 256
Journal blocks: 5536
Label:
FLEX_BG size: 16
Blocks: 354304
Block groups: 11
Reserved block group size: 0
Created filesystem with 2900/88704 inodes and 309956/354304 blocks

I have a link to the output file of the second command in the downloadLink.txt attachment. I hope this is able to help.

I also did the following to get information about each of the block devices.

fdisk -l /dev/block/mmc*

The output is in the fdiskDump.txt file that is uploaded at the URL listed in the attachment.

[MENTION=3245411]tys0n[/MENTION], Thanks for your help thus far! If you are still willing to help out with this custom recovery I will do all I can to help you out. Hopefully we can get a custom recovery soon!
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Downloaded and working fine in ext4_utils. Used simg2img to convert it and mounted fine to temp-folder. Seem to be a valid image so far.

Question is if Odin will take it. Someone still have to try it for errors.

Anyway, if someone can do the same for cache partition I can make a *.tar.md5 with system and cache, for testing.

Wipe cache, then make backup

su
make_ext4fs -s -l 734M -a cache /sdcard/cache.img.ext4 /cache
[Galaxy S III Mini Q&A, Help & Troubleshooting] assassinanex:
here you go -

i'll test anything but im on linux so no odin. heimdall?
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Firmware test!

Heimdall should work as well.

For anyone who want's to try here's packages for both heimdall and odin.

System image was rooted of course, but I also deodexed apps and framework for easier modding. they both contain boot, recovery, system and cache images.

DO THIS ON YOUR OWN RISK.

I WOULD TEST THEM BEFORE POST IF I HAD THE DEVICE

I WILL NOT BE HELD RESPONSIBLE FOR ANY DAMAGE​

Odin package:

SM-G730A_root-deodexed.tar.md5.zip - 771.99 MB

Install drivers

Make sure battery is charged

Unzip and put *.tar.md5 in PDA

Put phone in download mode and connect usb

Wait for phone to be recognized in odin and press START.

Wait for it to finish.

Heimdall package:

SM-G730A-root-deodex.tar.gz - 782.64 MB

Package made in Heimdall frontend 1.4.0 with MSM8930.pit and same images as the other one.

Load package as is with Heimdall-frontend.

Don't use it myself so check guides on how to do if unsure.

Please post results and logs.
[Galaxy S III Mini Q&A, Help & Troubleshooting] kman93:
downloading now. is there any possibility of getting a recovery made first? this phone is my daily driver and without a stock image, a backup would be nice before going balls deep into this. or is that what the logs from this are assisting in doing?
[Galaxy S III Mini Q&A, Help & Troubleshooting] assassinanex:
Here is the error i got... Ill be here to help...

Heimdall v1.4.0

Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna

http://www.glassechidna.com.au/

This software is provided free of charge. Copying and redistribution is

encouraged.

If you appreciate this software and you would like to support future

development please consider donating:

http://www.glassechidna.com.au/donate/

Initialising connection...

Detecting device...

Claiming interface...

Attempt failed. Detaching driver...

Claiming interface again...

Setting up interface...

Initialising protocol...

Protocol initialisation successful.

Beginning session...

Some devices may take up to 2 minutes to respond.

Please be patient!

Session begun.

Downloading device's PIT file...

PIT file download successful.

Uploading BOOT

0%

14%

29%

43%

58%

72%

87%

100%

ERROR: Failed to confirm end of file transfer sequence!

ERROR: (null) upload failed!

Ending session...

Rebooting device...

Releasing device interface...

Re-attaching kernel driver...
[Galaxy S III Mini Q&A, Help & Troubleshooting] kman93:
i am going to try the regular ODIN one, to see if it is an issue with heimdall, maybe. i am working with a really slow connection here, so it could be a while
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
I don't know. Did a quick goole on "ERROR: Failed to confirm end of file transfer sequence!" and it looks like a common error for Heimdall. No idea what's causing it.
[Galaxy S III Mini Q&A, Help & Troubleshooting] kman93:
my connection keeps timing out, so this may be a doozie here
[Galaxy S III Mini Q&A, Help & Troubleshooting] assassinanex:
nevermind
[Galaxy S III Mini Q&A, Help & Troubleshooting] kman93:
yeah, i will have results by tomorrow. where are the logs located (i assume this has something to do with logcat), and what do i need to do when i get it installed, if it boots?
[Galaxy S III Mini Q&A, Help & Troubleshooting] haffinator:
Sorry, I didn't realize there were more new posts since I last looked. This can be mostly ignored.

I also did the above command. I have uploaded the dump in the same manner as my last upload. The output of the command is below.

root@android:/ # make_ext4fs -s -l 734M -a cache /sdcard/cache.img.ext4 /cache
/sdcard/cache.img.ext4 /cache <
Creating filesystem with parameters:
Size: 769654784
Block size: 4096
Blocks per group: 32768
Inodes per group: 7840
Inode size: 256
Journal blocks: 2936
Label:
FLEX_BG size: 0
Blocks: 187904
Block groups: 6
Reserved block group size: 0
Created filesystem with 19/47040 inodes and 5936/187904 blocks
[Galaxy S III Mini Q&A, Help & Troubleshooting] haffinator:
I tired using the odin file but got the following error.

<ID:1/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> SM-G730A_root-deodexed.tar.md5 is invalid.
<OSM> End...

--EDIT--

I don't really know what I am talking about, but don't we need a custom recovery or something that accepts unsigned images first. But again I am just learning about all this android dev stuff so I might be completely wrong.
[Galaxy S III Mini Q&A, Help & Troubleshooting] kman93:
yeah, i would like to wait for a recovery as well. they said something about the cwm build site being bonkers, i don't know too much about that stuff
[Galaxy S III Mini Q&A, Help & Troubleshooting] tys0n:
Thanks. Making a new *.md5 file with different commands. Will check if valid before upload.

No need for custom recovery to flash with odin, but what I try to figure out is if it accepts custom images or if they need to be signed like some of the other at&t devices.

The chance of getting softbricked is very small with these files since they are taken from device itself. It's more likely that odin will give errors.