yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini General] SWisaiahAG:
yes , but an easier way to go about root is to install CWM Recovery , than flash Supersu root file.

Sorry , forgot to mention when at androidforums.com :D

link for most functional recovery

http://xdaforums.com/showthread.php?p=46977196

just flash with Odin it's fast . and just look up supersu on xda . than download flashable
[Galaxy S III Mini General] iRootAll:
I picked up a t599n on a trade. The person tried rooting it themselves and now it will boot to the setup wizard and then force close, not allowing the system to boot. I have tried flashing the prerooted tar with odin but it fails every time. I have even tried to flash cwm to no avail. I am not a novice when it comes to odin but this is perplexing. This is what odin reads

<ID:0/007> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> T599N-Pre-rooted.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/007> Odin v.3 engine (ID:7)..

<ID:0/007> File analysis..

<ID:0/007> SetupConnection..

<ID:0/007> Complete(Write) operation failed.

<ID:0/007> Added!!

<OSM> All threads completed. (succeed 0 / failed 1)

I get the same when I flash cwm as well. Has anyone dealt with this? Any help would be great. Thanks
[Galaxy S III Mini General] 16BitRun:
Try removing the .md5 and leave .tar on the file name. It should be rename as T599N-Pre-rooted.tar and reflash on Odin. That's what I did and it worked for me. Also, try to flash this tar on Odin for CWM on T599N... https://www.dropbox.com/s/j7372celhi9il1j/recovery.tar
[Galaxy S III Mini General] tys0n:
Looks like a problem with connection. Take a look on your computer's taskmanager that nothing with KIES is running. Try another cable/USB port.

Sent through time and space from my s3mini/CM10.2
[Galaxy S III Mini General] iRootAll:
Thanks, that did the trick
[Galaxy S III Mini General] iamubiquitous:
At a loss

After lurking for far too long and mining this site for a solution, I have decided to just ask. I have t599n, it will not restore. ' E:failed to mount' etc. have tried to recover stock from cwm and android recovery 3e. reboots to Tmobile brand and hangs. Apparently the partition table is boned. I have no idea what to do at this point, having searched the site for days and tried every method I could find. XDAdev is the last word in these devices as far as I can tell...any suggestions? I have tried every firmware package aimed at this (Metro pcs) phone, and every method of installation has failed..
[Galaxy S III Mini General] morepr:
Did u try flashing the Pre ROOTED T599N firmware through ODIN ?? Cus that work's for me
[Galaxy S III Mini General] tys0n:
Can you boot to recovery?

Did you try to format system, cache and dalvik, and then flash package in Odin?
[Galaxy S III Mini General] :
If the partiton table is messed, you may need to re-pit. I'm not entirely sure, double check with someone else. But you basically would have to go on odin, tick the "repartition" checkmark and in pda use a tar'd pit file. After that, try the t599n firmware from this thread, but do try tyson's suggestions first.
[Galaxy S III Mini General] iamubiquitous:
Yes, tried to rename .md5 to tar and flash with odin but the problem is that when I try to wipe the dalvik, it can't...I I have used cwm and 3e to recover to stockt599n with no luck. I suspect it is a partition problem

but I cannot seem to find a pit file for this increasingly annoying phone. I'm sure when I do get it fixed, my opinion will change. I'm currently using my sgh-1777 unlocked, rooted and shostock3 and it's working fine. This one was to be a gift to someone needing to be dragged, kicking and screaming, into the 21st century.
[Galaxy S III Mini General] iamubiquitous:
No Va

Tried it all I think...Basically, I get the E: failed to mount* and E: failed to find* and when I try to format or mount E: fails to find it's...but I digress.

From the research I've done on this god-tier site, I believe that it has to be a partition error, if I try to wipe dalvik, it doesn't go to the are you sure table with the wipe selection down near the bottom to verify "yes" wipe the darn thing...it just returns to the top of the same page. Anyway, if I can get the custom binary count to zero at this point Samsung will give me a new phone...they already sent me an R.A. and shipping label. So maybe that is my question: Can I get the custom binary count to zero from cwm or 3e? then I can brick a new phone at least. lol
[Galaxy S III Mini General] 16BitRun:
The only way I know is to install Triangle Away from the Google Store to reset the counter to zero. https://play.google.com/store/apps/details?id=eu.chainfire.triangleaway I unrooted my phone after using this app to reset the counter back to zero and sent my phone for repair under warranty and it worked. I don't know of a way with CWM.
[Galaxy S III Mini General] iamubiquitous:
'I was afraid of that

yes I f figured as much but since I can't get the phone to load the operating system that's out of the question I understand there's a jig does the operating system need to be loaded to use that?
[Galaxy S III Mini General] 16BitRun:
Are you able to get to download mode using the three button combo? If so try to flash the [MENTION=3245411]tys0n[/MENTION] pre-rooted ROM with Odin while on Download Mode. If you can't get into Download Mode you can create a jig by following these instructions... http://xdaforums.com/showthread.php?t=819551 You can also purchase one since they are as cheap as $2.00 on eBay. Here is a better article with a FAQ on the subject... http://xdaforums.com/showthread.php?t=1402286
[Galaxy S III Mini General] iamubiquitous:
Yes, I can get recovery mode AND flash with odin I have tried the Pre-rooted rom previously mentioned as well as the stock metroPCS rom in both 3e and cwm recovery. Nothing seems to fix the partition mapping. What I need is the stock pit tar'd so I can try flashing THAT with odin. Barring that, I will try the methods you have directed me to and see what they yield. I can't possibly brick it any worse than it is now and if I can reset the binary count, sammy will send me a new phone. Thank you all for your suggestions. I must mention that before I joined this thread, I performed my due diligence and thoroughly researched and tried ALL the posted fixes (except the jig), before I asked for help.I am new to dev, but have the utmost respect for those of you who take the time to learn and then teach. Thank you all so much! I should also mention that while flashing recovery and roms succeed using odin, when I reboot and try to wipe dalvik and factory reset the partition is still boned. CWM reports error at blk23 and 25 (cache and user data, I believe.) Anyway seeya!
[Galaxy S III Mini General] tys0n:
I can make a pit file for t599n if someone make a backup of pit partition and post it here.

Sent through time and space from my s3mini/CM10.2
[Galaxy S III Mini General] iamubiquitous:
Great...

Thanks tys0n, that's most appreciated. You can't imagine how many times and ways I have tried to fix this and not been able to locate a PIT so they all failed.:good:
[Galaxy S III Mini General] tys0n:
No problem. Let's hope someone with a T-599N can help :)

In terminal:

dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/mmcblk0p3

Please zip it and post it here. Then I can update OP with pit-files for all three T-599's.
[Galaxy S III Mini General] :
This is a pit file I pulled from a t599v,

http://d-h.st/Om6

I'm not sure if it would work with the other variants, but technically it should since there's no hardware differences between them, and the fact that Unjust created one rom that works on them all.
[Galaxy S III Mini General] tys0n:
Thanks, but in this case I need pit from T-599N.

I already got pit for T-599 (codinatmo.pit) and T-599V (codinavid.pit)

Don't know the original pit name for T-599N which have to be correct.

That name can be found inside pit partition.
[Galaxy S III Mini General] 16BitRun:
[MENTION=4734364]iamubiquitous[/MENTION] I can make a pit for you from my T599N. Give me a few minutes.
[Galaxy S III Mini General] 16BitRun:
SGH-T599N Pit

[MENTION=4734364]iamubiquitous[/MENTION] [MENTION=3245411]tys0n[/MENTION] Here is my Pit I extracted and zip from my T599N. Hope it helps. Let me know if it's good or if there is anything else I can do to help.
[Galaxy S III Mini General] tys0n:
Thanks a lot [MENTION=4567700]DJVargas[/MENTION]. Have you flashed any pit from T-599, tmo?

[MENTION=4734364]iamubiquitous[/MENTION] It could be it also use codinatmo.pit, same as T-599. My thought was something like codinamtr.pit

I ran it in pitmagic, so here's a zipped "clean" codinatmo.pit (not whole partition) to put in odins pit-box if you intend to flash fw with repartition.

View attachment codinatmo.pit.zip
[Galaxy S III Mini General] iamubiquitous:
fail

I think I remember a thread in the sgh-599x forum identifying them and mtr looks like the suffix...tmo didn't work...yes, in desperation, I tried it. any how see attached img
[Galaxy S III Mini General] tys0n:
That zip from DJVargas is not a flashable zip if that was what you tried.

You should try flashing firmware with pit in Odin.
[Galaxy S III Mini General] iamubiquitous:
Wat?

Do I rename it? Add an extension?Extract and add ext? I have yet to get to that walk through...Clueless.
[Galaxy S III Mini General] iamubiquitous:
currently in a reading frenzy...thanks again, all y'all!
[Galaxy S III Mini General] 16BitRun:
Hi. I never flashed any pit from T599, TMO. I'll try to run my pit through pitmagic and repost it.
[Galaxy S III Mini General] ClaireVoyant94:
I have the SGH-T599 and used the file in the T599-Pre-rooted.zip file in the original post + Odin 3.07. It can boot properly, but it only goes as far as the "T-Mobile 4G" screen (after the Samsung splash screen). Anyone know why this is happening? Did I use the right file?

Edit: Okay, so I figured out that by waiting long enough, it goes to setup. However, it does this every time I start up the phone. What should I do? Also, I noticed that there's no free space at all, why is this?
[Galaxy S III Mini General] tys0n:
Unzip the cotinatmo.pit.zip I posted, put it in PIT in odin and make sure repartition is ticked, put firmware package in PDA and start.

Ok, thanks. Then I guess they both share the same PIT-file. Just wanted to make sure :)

How long does it take to boot? Have you tried factory reset from recovery?
[Galaxy S III Mini General] ClaireVoyant94:
It takes ~2 minutes to go from the "T-Mobile 4G" screen to the setup wizard (or whatever it should be called). I have not yet tried factory reset from recovery, do you think this should solve the problem of having no free space? :confused:

Edit: Using factory reset from recovery solved neither problem.
[Galaxy S III Mini General] tys0n:
No idea why and I haven't heard any issues from any one else about this.

Was everything ok before flash?
[Galaxy S III Mini General] iamubiquitous:
Results
[Galaxy S III Mini General] ClaireVoyant94:
Depends on what you mean by okay, it was soft-bricked with only CWM recovery installed
[Galaxy S III Mini General] tys0n:
Ok. You know how it got soft-bricked?

Sent through time and space from my s3mini/CM10.2
[Galaxy S III Mini General] ClaireVoyant94:
I stupidly tried installing CWM recovery for the S3 Mini (they're nearly the same so I thought it would work - and it somewhat did) to install CyanogenMod, but when I tried to back it up with the ROM Manager app, it rebooted and got stuck in a boot loop. I flashed it with CWM recovery a second time thinking it would fix it somehow, and that just messed it up even more. I found a version of CWM recovery for the T599 and flashed it with that, and it worked (I was able to go into recovery mode) but I realized I needed a stock ROM for it, and that's how I got to this thread. I flashed it with the .tar.md5 file in T599-Pre-rooted.zip in OP, and that's how I got to where I am now.
[Galaxy S III Mini General] tys0n:
I see. I know there was a few others who also tried cwm for i8190 and got stuck in bootloop and other issues. Some reported that they flashed param for i8190 in an attempt to fix it, and I believe some succeded. It's an "image-cache" for bootloader, and if it is messed up it will fail to boot properly.

I got param.lfs for SGH-T599N so it might be worth trying..View attachment SGH-T599N-param.zip

Unzip and flash tar as PDA in odin.
[Galaxy S III Mini General] :
Actually I'm facing this issue too.
[Galaxy S III Mini General] ClaireVoyant94:
Just tried this and it has the same problem... :confused:
[Galaxy S III Mini General] Unjustified Dev:
Flash stock system.IMG , boot.IMG , and recovery.IMG for you model. I use heimdall command line to flash it. There are stock zips specific for models somewhere in between my cwm thread use xda search . If you bootloop flash stock recovery then flash my philz repacked if you want a custom recovery. I no longer have this phone .
[Galaxy S III Mini General] ClaireVoyant94:
Will the files in OP not work? When were they last updated?
[Galaxy S III Mini General] flip3601:
Good 2 see u back unjust! Its unfortunate u no longer have this phone. I guess that means ur going 2 stop working on it then. Well I hope everything turns out good 4 u. Thanx 4 ur work that u have done while u had this phone.

Sent from my CM10.1 SGH-T599
[Galaxy S III Mini General] tys0n:
If you wonder about the odin packages there's not much to update. It's same system/recovery/boot that the phone came with. I just repacked it to odin images and pre-rooted it.

Anyway..I will update post 2 with flashable zip's for each model as well.

I just did new deodexed ones, with init.d support and busybox installed. Maybe it can help someone.

I'm just gonna try flash it before I upload. Can't say anything about performance or boot since it won't get past bootscreen on my i8190. Same partition layout but a bit different hardware :P Just want to see if script is ok.
[Galaxy S III Mini General] ClaireVoyant94:
I flashed it with the files in this post from Unjustified Dev's thread, and it looks like everything's back to normal! :victory: It's not pre-rooted, but at least my phone is working like normal again.

Thanks to everyone who replied!

Edit: Forgot the link :P
[Galaxy S III Mini General] :
I had an issue in which the internal memory card was full, even after a complete factory reset (formatted everything) and went back to stock. I ended up repartioning the device using a pit file (for me it was codinavid.pit). I resolved this issue by flashing Philz recovery, formatting /system, /data, /cache, /preloader dalvic cache, and format to install a new rom option, and flashed the 09/20 build of CM, which I happened to have downloaded before goo's servers were down. I'm just posting this just in case someone else runs into this issue as well.

Link to Philz recovery: http://d-h.st/Spb
[Galaxy S III Mini General] ClaireVoyant94:
"09/20 build of CM" is CyanogenMod 10.1 I'm guessing? And are you using an SGH-T599?
[Galaxy S III Mini General] :
T599v but the CM and ROM builds are interchangable for the t599, t599n, t599mtr and t599v. Back when Unjust was developing he pushed nightlies, and typically nightly builds are named after the date, and I just happened to have the 09/20 build on my computer. I'll upload that and the PAC rom once I get home.

take a look here for all the roms and recovery available:

http://xdaforums.com/showthread.php?p=48138635
[Galaxy S III Mini General] ClaireVoyant94:
Cool! To flash CM, do I need to use CWM or Philz Recovery, or can I use the stock recovery?
[Galaxy S III Mini General] :
CWM or Philz Recovery, though the latter is better.
[Galaxy S III Mini General] Congarus:
totally confused...

okay I guess I'm just not seeing what I need to be able to root my phone because I have tried the one step root, downloaded and tried superuser supersu so many other running programs that I'm totally confused I had to reset my phone several times because nothing seems to work even the stuff is the post it on here just doesn't seem to work for my T559N...I guess I'm just one of those people that doesn't understand programming in one I ever anything like it happens my head goes berserk.
[Galaxy S III Mini General] :
try cydia impactor, just make sure your phone is in usb debugging mode thoigj/
[Galaxy S III Mini General] 16BitRun:
Cydia Impactor didnt work for me. I dont think it supports our phone. Why don't you just flash the Pre-rooted Firmware for you phone with Odin found on the original post of this thread. That's what I did and didn't have to worry about rooting since Odin took care of it with Tys0n's Pre-rooted Stock ROM and you start fresh.
[Galaxy S III Mini General] morepr:
Try VROOT from the op in the first page
[Galaxy S III Mini General] TheMenoHD:
I can't get ODIN to recognize my phone can someone help:confused:
[Galaxy S III Mini General] DevilDogg:
Try using a different USB cable? I've never heard of Odin not recognizing a phone before.
[Galaxy S III Mini General] kylegrant:
does anyone have another copy of the t599n zip or can someone upload just the t55n.tar.md5 for me? i tried downloading twice and when i unzip, it says the .md5 is broken :( and i really want to switch back from the buggy cm10.1

edit tried win7 extraction, 7zip, and winrar.. all say file is corrupt. and me being dumb didnt make a backup!! :\

edit2: third times the charm! it finally extracted and im back to stock thanks guys!
[Galaxy S III Mini General] DevilDogg:
There's a thread floating around here with a stock+root Odin flashable ROM. I think it's in the t599 general discussion thread.
[Galaxy S III Mini General] kylegrant:
yeah thats where i got my file from... i finaly got it working myself but thanks for the reply!:victory:
[Galaxy S III Mini General] DillonHerring:
Well, do you know Where to get the pit file...I broke my Internal SD Using Re-Partition.:confused:
[Galaxy S III Mini General] kylegrant:
I would try booting into recovery (CWM or Philz) and formatting the internal SD. If that doesnt work for you, the only other thing I can think of trying is to flash to stock using odin and the stock+root zip. Sorry!

I never tried messing with anything PIT-related or my internal SD, but I have a feeling one of these will work for you.
[Galaxy S III Mini General] Unjustified Dev:
I have a pit I can upload I made it with heimdall. Cm11 releasing tomorrow just a port of maclaw build
[Galaxy S III Mini General] kylegrant:
No ****ing way???!!!! Does this cm11 have any bugs like the cm10 had? Also, is there any reason I cant get my samsung to work properly in ubuntu? It shows up as android in file manager and lists the folders in the sdcard but if I click into the folders they appear to be empty (when I know they are not)
[Galaxy S III Mini General] Unjustified Dev:
Same thing i said when I added support into a blank kernel from google source based on samsung

https://github.com/Novathor/android_kernel_samsung_common/commits/android-samsung-3.0-jb-mr0

This will be the kernel I will use.

building 4.3 too had to hold back on maclaw 4.4 port since I seen someone said I never fixed all bugs
[Galaxy S III Mini General] 16BitRun:
Hey [MENTION=4911249]Unjustified Dev[/MENTION] Good to hear from you. I'm happy to hear you are working on 4.3 and 4.4. Don't worry about what anyone says. You are already recognized as someone bringing life to our phones. I'm sure there will always be bugs but they can be iron out little by little as you have done before. We all are excited for these ports specially KitKat and can't wait to try them out. As always let us know of anything we can do to help. Thanks again for all contributions.
[Galaxy S III Mini General] Unjustified Dev:
I didn't port any roms yet all built from source unless you mean that way? I will build it when I get home
[Galaxy S III Mini General] Unjustified Dev:
[MENTION=2213426]morepr[/MENTION] [MENTION=4567700]DJVargas[/MENTION] [MENTION=4455474]kylegrant[/MENTION] [MENTION=5354456]Exothermic[/MENTION]

4.3.1 works very well I had trouble fixing cwm loop thing but now we have cwm , twrp , cwm swipe , and philz cwm which I will update to fix loop you will get :)

No bugs that I have found so far that will be too big too handle.

1.) brightness is wrong so no auto brightness but I will add it things it's due to light module missing fixing that now

Softkeys vibrate but you can't control vibration yet I will add the ability to do so :)

Sound works

Cam/video

Oh yeah reboot to recovery works too no recovery loops period

Stable 3.0.101 kernel opens source based so no patches to get here all merged and fixed.

Low call volume was fixed already.

Offline charging works and home button wakes device so you can see your percentage

Cwm repeatable keys no longer need to just press it down each time you can hold down and get a scroll effect or just swipe down

No BLN yet but it will come

Idk you will have to see for yourself it's amazing :)

Other than mentioned it appears to be stable

Build coming later on
[Galaxy S III Mini General] kylegrant:
You are the man, cant wait to take that ***** for a spin! :D

Edit: whats BLN?

Edit, again: Google search of BLN android tells me it stands for backlight notifications which means the softkey lights stay on during sleep to let you know you have unread notifications.
[Galaxy S III Mini General] Unjustified Dev:
:) rom won't be device specific your model will be t599 and name just codinaxxx
[Galaxy S III Mini General] kylegrant:
I dont get what this means. Just under the settings> about device thats what its gonna say?
[Galaxy S III Mini General] Unjustified Dev:
Yes previous times made me only build t599n because I tested them. I don't have server to build with now. Internet and mms should still work even though it's not defaulting to metropcs or wind model.
[Galaxy S III Mini General] kylegrant:
Uhhh I agree? Not really sure what that means but if it works, it works. Lol, I appreciate your hard work.
[Galaxy S III Mini General] Unjustified Dev:
Lol

simple

You have metro pcs version it wants metro pcs network and I made it so it only could use their network. I changed it now so any network should work with this so called universal build to save me time.
[Galaxy S III Mini General] kylegrant:
Cool. Not that I have any problems with these things but I should get better battery life and more room for apps with your rom, correct?

Edit: my thoughts because without all these touchwiz-whatevers and apps and services that come preloaded.
[Galaxy S III Mini General] :
Great to hear your back! Can't wait to test out the new build! Just for my own knowledge, how did you fix the camera? And regarding McLaw's CM11, I thought his sources weren't posted hence why Oliver abandoned (?) / didn't release omni 4.4?
[Galaxy S III Mini General] Unjustified Dev:
I don't need his source. I preferred to build 4.4 myself . Camera I didn't do anything but use golden device tree and our blobs to make it work.
[Galaxy S III Mini General] :
Weird, I tried using golden's device tree and our blobs but it didn't work out. By McLaw's sources I was refering to the fixes needed to get camera working according to Oliver, but I suppose since Oliver was building omni 4.4, he was referring to different fixes. But it's great to know that you could get kitkat to our devices!
[Galaxy S III Mini General] morepr:
Thank you so much you dont know what this means to us and having a nice rom to mess with lol the big question is when u gonna realease it lmao! Very excited again thank you.
[Galaxy S III Mini General] Unjustified Dev:
On 4.4 no idea about camera that's why I am not building 4.4 since we don't know what maclaw source looks like it's hard to do some things. I could ask him to build a 4.4 for us if he's up to it. [MENTION=5011036]New Macław[/MENTION] when I push my source I have do you mind building 4.4 for us? I would really appreciate it.
[Galaxy S III Mini General] Unjustified Dev:
In a few more hours :) you will have a highly functional build. I couldn't get audio to stay smooth you know it get's high then low when your not clicking on anything. I couldn't get vibrator control implementation working or auto brightness yet. So far everything else works though. Audio does not disappear .