yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini General] Brytnee:
Is the shg-t599 an LTE phone or not? I'm very confused about this and I can't seem to get a straight answer from Samsung or T-Mobile about this. If it is LTE does it need a radio update or what?
[Galaxy S III Mini General] Unjustified Dev:
It's not lte only 4G
[Galaxy S III Mini General] Brytnee:
I've been trying to figure this out. How can I add color to emoji? I'm currently using the nomoreboxes.ws emoji font but it's only black and white.
[Galaxy S III Mini General] supernugget:
Good evening,

I'm having an issue which I hope someone can help me solve.

My wife's phone is the T-Mobile US sgh-t599. If I understand this correctly, this phone is a GS3 Mini, right? So this is the right forum?

Anyway, I am/was trying to de-bloat this thing and as such, I followed the OP's instructions to the letter. Somehow, though, All that I've managed is to get it stuck in a bootloop. The exception is that it will still go into download mode. Odin can still see it and I've downloaded different recovery images to see if one will work. Some succeed in odin, some fail, but none breaks the bootloop.

Not really sure what else is relevant, but I'll do my best to supply whatever info is helpful.

Thanks in advance!

SN
[Galaxy S III Mini General] tys0n:
Flash stock recovery and wipe cache. I think that will take you out of bootloop.

You can also unzip and flash this wipe in odin. Just an empty cache.

View attachment t599_wipe.zip
[Galaxy S III Mini General] supernugget:
Thanks for that.

I've tried them all again, including stock. also flashed the wipe and reflashed each one again to see if there was any change. The stock one stops the bootloop, but now i get the boot screen/then black/ then soft keys light up/ soft keys stay lit and it goes no farther. All of the other ones return me to bootloop, with and without the wipe. I'm using odin 3.04 on windows 7.

Thanks again
[Galaxy S III Mini General] tys0n:
If noting else works, see if you can get to recovery mode and do a factory reset or have a look at the firmware I made.

[INDEX][SGH-T599x][FIRMWARE]
[Galaxy S III Mini General] supernugget:
That did it! Thanks so much!

Really saved my neck.
[Galaxy S III Mini General] mkgarrod:
Helppp!

Hello everyone,

So I'm having some issues with this process, I did everything in the initial instructions, downloaded drivers, odin, recovery, everything and when I try and flash the recovery with Odin, It fails almost immediately on the first step, Kernel, Could anyone help me out on this process? It might have already been asked and answered but I haven't had the time to search 42 pages of notes on this.
[Galaxy S III Mini General] tys0n:
If you happen to have kies installed, make sure that no process with kies is running in the background. Check with your PC's taskmanager.

Otherwise..try another usb port or another cable. Good luck.
[Galaxy S III Mini General] mkgarrod:
Every time i try and flash the recovery.img it fails at the Kernel section. I had a program with Kies running KiesPDLR? or something like that, but I closed it. does all the settings and what not look correct on here so far?
[Galaxy S III Mini General] tys0n:
Yes, all settings is as it should be. Still not working? Have you tried to change usb-port to see if it makes any difference?
[Galaxy S III Mini General] mkgarrod:
yeah, changed it from front to back, should I try on another computer? When I plug it in, this is the windows install that pops up
[Galaxy S III Mini General] tys0n:
Do you connect it in download mode? (vol-/home/power)

I never get any popups like that when I connect in download mode.

Make sure nothing with kies is running.

Open odin and load recovery in PDA.

Put phone in download mode.

Connect to computer and wait for com to be blue.

Press start and wait for PASS.

Phone will reboot itself.

Disconnect cable.
[Galaxy S III Mini General] mkgarrod:
in the top left corner

ID:COM

0:[COM6]

has been blue the entire time... is that correct? and as I'm going to download mode it first asks me to press volume up to continue, or volume down to cancel... is that normal? I never saw anyone else mention that part... Sorry, I'm really not too much of a noob, but I'm used to working on my nexus devices!
[Galaxy S III Mini General] tys0n:
That warning is normal.

Thing is, if it fails you have to reboot to download mode once again. Connection gets closed.

For every retry you have to reboot to download mode, or it will fail every time.
[Galaxy S III Mini General] mkgarrod:
On my screen all it says is

ODIN MODE

PRODUCT NAME: SGH-T599N

CUSTOM BINARY DOWNLOAD: YES (4 counts)

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

>Insert Android symbol

Downloading...

​​

Do not turn off target!!

Is that normal? It's like that EVERY time i have ever turned it to download mode, the 4 times, that it referring to is, i flashed someones pre-rooted firmware with odin, and I did it a few times.

It was actually a link on this thread
[Galaxy S III Mini General] tys0n:
That pre-rooted firmware is probably the one i made with help of the owners here( I don't have this one myself, but a i8190)

Download cound can be set to zero using triangle away, and maybe even official status on rom to gert guarantie back...but that should not make any difference for how odin handles this recovery flash.

Is it stock recovery or cwm you try to flash?
[Galaxy S III Mini General] mkgarrod:
I want cwm, which I believe is the very first link in the OP.
[Galaxy S III Mini General] tys0n:
Yeah I guess OP is updated with best working version :P

Anyway, if you can't get it to work, wait for [MENTION=4911249]Unjustified Dev[/MENTION] to be at help. He will know for sure! Good luck.
[Galaxy S III Mini General] morepr:
I have same problem since they update de recovery when u guys had the first one I had no problem to flash it now it fails to me abd I have the stock Rom
[Galaxy S III Mini General] clipse_101:
So I just re-looked into rooting/getting CWM on the T599n, it looks like people have success with this here, I myself seem to have run into problems and have no clue what exactly it is. I ran Odin and got this:

<ID:0/005> Added!!

<ID:0/005> Odin v.3 engine (ID:5)..

<ID:0/005> File analysis..

<ID:0/005> SetupConnection..

<ID:0/005> Initialzation..

<ID:0/005> Get PIT for mapping..

<ID:0/005> Firmware update start..

<ID:0/005> recovery.img

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

<ID:0/005> Added!!

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

<ID:0/005> Removed!!

Any idea what the problem may be? I wanted to install CWM in order to get this ROM: http://xdaforums.com/showthread.php?t=2493559

It works on the T599n right? I'm really new to this whole scene.
[Galaxy S III Mini General] 16BitRun:
Here try to flash this tar on Odin for CWM on T599N... https://www.dropbox.com/s/j7372celhi9il1j/recovery.tar and yes that ROM is for our phone. Its a great ROM but it has a bug with sound volume plus development has stopped.
[Galaxy S III Mini General] clipse_101:
Yeah, that worked like a charm, thanks man!

I keep trying to download that ROM, but I end up getting a network error, like it times out or something. So for now, I installed CM 10.1, but I do plan on getting PAC-ROM as well :)
[Galaxy S III Mini General] flip3601:
Nice! Personally I think CM10.1 is better. Pac-Rom had quite a few bugs that was hard 2 get past.

Sent from my CM10.1 SGH-T599
[Galaxy S III Mini General] :
That network is due to the hosting site (goo); they still haven't put up all their servers I think and some files are missing, but for the time being CM is the best in terms of features and stablity. PAC is excellent too, but the camera wasn't working (the biggest bug) alongside sound issues which is present in CM as well.
[Galaxy S III Mini General] clipse_101:
For some reason, I can't get Pac-Rom to work, I installed it, but it just stays stuck at the Samsung SGH-T599N screen, not sure what the problem is, going to try CM 10.1 again.

---------- Post added at 04:57 PM ---------- Previous post was at 04:51 PM ----------

Oh okay, thanks for the heads up, I'll see which I like better if i can get PAC working.
[Galaxy S III Mini General] flip3601:
I was able 2 install PAC but after that it wouldn't hold my apps and I kept getting "system UID inconsistencies" notices which I couldn't do anything about. I think it would've been a great ROM but it just wouldn't work 4 me.

Sent from my CM10.1 SGH-T599
[Galaxy S III Mini General] clipse_101:
I can't even get it ha

Not really liking Cm 10.1
[Galaxy S III Mini General] 16BitRun:
I'm glad it worked. I modify the recovery.tar from the OP so it can work with Odin. Use this one instead. https://www.dropbox.com/s/j7372celhi9il1j/recovery.tar That's why many people keep getting error and OP has not been updated.
[Galaxy S III Mini General] alaasd12:
sorry for asking this retarted question

i want to know if the reovery image will work on galaxy ace 2 e (SGH-T599V) i really cant offer to brick this phone at the moment and also i used cydiaimapctor to root would that effected

---------- Post added at 12:19 AM ---------- Previous post was at 12:14 AM ----------

sorry for asking this retarted question

i want to know if the reovery image will work on galaxy ace 2 e (SGH-T599V) i really cant offer to brick this phone at the moment and also i used cydiaimapctor to root would that effected
[Galaxy S III Mini General] :
Just use philz reovery go to t599x general discussion and find it, it'll work I have a t599v, and Cydiaimpactor doesn't have any impact on recovery.
[Galaxy S III Mini General] DS36:
Hello and how are you? Thank you for this posting this recovery. I am trying to port cm11 to the t599n for metropcs. The rom I ported seems to flash fine (stil boot loops at the boot animationthough), but I seem to keep getting a (status 7) error while flashing 4.4 gapps. Doing research I found that I either need to have the latest cwm reovery or the latest twrp. I have been trying for 2 days to complie an updated recovery but seem to fail everywhere I turn. Its just out of my league. Any advice or any tips as to why I am getting a Status 7 error? Thanks for your help.
[Galaxy S III Mini General] 16BitRun:
Cool and your welcome. I read somewhere that sometimes status 7 comes from flashing on a recovery that doesn't support that android version. Also, there was mention about the boot loader as well. Have you try flashing with Philz Recovery for our phone that repacked by Unjustified Dev?... Here... https://www.dropbox.com/s/p4yrrkxx4zxc5u6/repacked_philz_touch_5.15.0-codinamtr.zip Give it a try. If not, maybe you can get together with him to update his recovery for out phone. I'll keep doing some more research.
[Galaxy S III Mini General] DS36:
Oh cool thanks for that. I finally figured out I forgot to edit the build.prop sorry it's been a free years since I did this. :)
[Galaxy S III Mini General] trendal:
T599V not working after

tys0n, I flashed my phone with your T599V-Pre-Rooted.zip and now I have the issue of no memory on my phone!! It starts up fine, although nothing at all is saved. I can't do anything that needs storage space to run. When I go into Settings->Storage the bar is green right across the top and it keeps saying about 100mb for the Applications and then it crashes and the rest of the bars disappear for a moment.

Help please!!!
[Galaxy S III Mini General] tys0n:
I wonder why that happen sometimes. [MENTION=5354456]Exothermic[/MENTION] ran in to something similar.

http://xdaforums.com/showpost.php?p=48113288&postcount=76
[Galaxy S III Mini General] trendal:
I'm having trouble getting a pit file for flashing...every time I've tried codinavid.pit I get the following error in odin:

Set PIT file..

DO NOT TURN OFF TARGET!!

__XmitData_Read ..

Re-Partition operation failed.

The phone still boots fine and everything runs...just can't save anything :confused:
[Galaxy S III Mini General] trendal:
OK, so I've got it working I think...

The file T599V-Pre-rooted.tar.md5 doesn't contain a hidden.img and I think this is where my problem was. The first file I tried to flash was SGH-T599V_VLAME3_YVLAME3.tar.md5 but this file put my phone into a boot loop...but it also has a hidden.img file which I think overwrote the stock one. I then tried flashing with T599V-Pre-rooted.tar.md5 which flashed the system perfectly fine...but probably left the hidden.img file that I had previously flashed. I think this was why my phone would run perfectly fine...but the memory wasn't there.

To fix it, I had to first flash sgh-t599.tar.md5 (found somewhere in this thread) which appears to be the stock T-mobile. It has a hidden.img! Phone started up, although with some errors (a SIM error was one!). I then was able to flash T599V-Pre-rooted.tar.md5 and the phone starts and runs ok so far!!

I still have an issue where when the phone is first turned on, a garbled white screen comes up first sometimes showing a bit of the Android from the Download screen...anyone know why? The phone appears to run fine, otherwise.
[Galaxy S III Mini General] :
I came across the same issue, except I think my issue arose when I tried to flash the golden's recovery (I was the only active user at the time with a t599 variant and I thought the roms for golden and codinavid were interchangeable so I went and flashed it and bricked my phone. [MENTION=3245411]tys0n[/MENTION] did mention that it could be due to an issue with param.lfs but I flashed a new one and it still didn't work.
[Galaxy S III Mini General] trendal:
It may have been param.lfs...that one was missing in T599V-Pre-rooted.tar.md5 but present in the stock t-mobile too.
[Galaxy S III Mini General] trendal:
When these phones do a cold boot, what is the first thing to run? boot.img?
[Galaxy S III Mini General] wilbigdaddy2000:
Trying to get a custom recovery working on t599n. I want cwm but willing to use twrp. Please point me in the right direction. I tried to flash cwm with Odin but I was stuck on Samsung boot screen. So I had to reflash with stock recovery. Don't know what went wrong.
[Galaxy S III Mini General] 16BitRun:
Try flashing this CWM recovery on Odin...I modify the recovery.tar from the OP so it can work with Odin. Use this one instead see if it works... https://www.dropbox.com/s/j7372celhi9il1j/recovery.tar
[Galaxy S III Mini General] wilbigdaddy2000:
Got Odin to work with the recovery u sent. Thanks. Once Odin rebooted my phone what do I do next?

Update: All worked great bro. Thanks a lot. Been trying to get this for weeks now.
[Galaxy S III Mini General] wilbigdaddy2000:
OK bro, oncE I put the phone into cwm recovery, it kept looping back into recovery mode. What am i missing?
[Galaxy S III Mini General] cluck u:
You need to reflash the stock recovery and then cwm again.

See this thread:

http://xdaforums.com/showthread.php?t=2489238
[Galaxy S III Mini General] wilbigdaddy2000:
So I do a wipe and use the pre-rooted stock recovery, then flash the cwm with odin and all should work well, correct?
[Galaxy S III Mini General] wilbigdaddy2000:
Was able to flash cwm successfully. All runs great. Needed to wipe caches first to get rid of the looping. Looking for compatible Roms now. If I can't find, I'll return to question.
[Galaxy S III Mini General] 16BitRun:
Great! You are not going to find to much development for our phone unfortunately but you can refer to this thread for a list of ROMs available... http://xdaforums.com/showthread.php?p=48138635
[Galaxy S III Mini General] GTurn:
I just bought this phone days ago. i successfully rooted the phone with cydia but i cant flash the recovery. i have the sgh t559n. i have read through every page of this thread and have tried every download that has been posted of the recovery and none of them work on my phone. it will flash and as long as i dont reboot to cwm recovery the phone works fine but as soon as i reboot in to recovery it will only boot back in to recovery no matter what i do. I end up reflashing the stock rooted zip and it goes back to stock recovery and the phone is working fine.
[Galaxy S III Mini General] SWisaiahAG:
its a recovery loop . I recommend you flash philz cwm . and don't user apps to reboot to recovery. . it makes you go through a recovery loop .. but [MENTION=4911249]Unjustified Dev[/MENTION] is suppose to be posting links fu for a new rom & recovery so just wait on
[Galaxy S III Mini General] morepr:
Try this recovery

http://d-h.st/Spb

XDA DEVELOPERS PREMIUM SGH T599N ROOTED

---------- Post added at 10:26 AM ---------- Previous post was at 10:23 AM ----------

Try this recovery

http://d-h.st/Spb

The one that works for me without loop is phill repacked recovery if the one in the link doesn't work let me know to send you another one

XDA DEVELOPERS PREMIUM SGH T599N ROOTED
[Galaxy S III Mini General] GTurn:
thanks for the quick response. this recovery did it for me. everything is working fine now.
[Galaxy S III Mini General] tntted:
Help phone might be bricked

Hi I have a sgh - t599v and I was flashing this rom : (http://xdaforums.com/showthread.php?t=2659668), Using after flashing in TWRP I rebooted and got a screen with static showing a bit of the startup logo. Tried to re boot again but same thing. Stuck here but can get to ODIN mode but cannot flash anything getting error no PIT or Can't open the specified file. (Line: 1455). Anything????!
[Galaxy S III Mini General] :
Weird, I have the T599V and it flashed alright for me. Try flashing the t599v stock file in odin: http://www.androidfilehost.com/?fid=23329332407575905 if odin doesn't work try installing heimdall http://xdaforums.com/showthread.php?t=1508703 that's a guide to help you get started, although you'd have to unzip the tar file and flash the files individually in heimdall.
[Galaxy S III Mini General] tntted:
Thanks trying now.
[Galaxy S III Mini General] :
Let me know how it goes.
[Galaxy S III Mini General] tntted:
Nothing keep getting this error : Initialising connection...

Detecting device...

ERROR: Failed to access device. libusb error: -12

Now this Initialising connection...

Detecting device...

Claiming interface...

ERROR: Claiming interface failed!

Forget the above got the right drivers now this:

Initialising connection...

Detecting device...

Claiming interface...

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...

ERROR: Failed to receive PIT file size!

ERROR: Failed to download PIT file!

Ending session...

Releasing device interface...

---------- Post added at 03:05 AM ---------- Previous post was at 02:39 AM ----------

I don't have a kernel... Could that be the problem?
[Galaxy S III Mini General] :
upload the device's pit file: http://xdaforums.com/showpost.php?p=45378447&postcount=143

and it should say detect device somewhere.

Upload the devices' pit file first then press detect device and it should say device found or something to that extend, then unzip the stock file provided above flash and upload the files individually.
[Galaxy S III Mini General] tntted:
Still getting this:

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...

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...

ERROR: Failed to receive PIT file size!

ERROR: Failed to download PIT file!

Ending session...

Rebooting device...

Releasing device interface...

Btw thanks for helping so far.
[Galaxy S III Mini General] :
Try a different usb port, and ensure that you installed heimdall and heimdall front end (and run it as sudo through terminall "sudo heimdall-frontend" if you're running linux) if it's on PC remember to do

"Windows Driver Preparation

1. Install Samsung's Drivers (SAMSUNG_USB_Driver_for_Mobile_Phones.msi either from Kies or SAMSUNG_USB_Driver_for_Mobile_Phones_x86.exe from GB-Stock-Safe-v5.zip)

Note: You should reboot your computer after installing, even if it doesn't tell you to. Drivers wouldn't initialize until I rebooted.

2. Connect your Tab to your computer at least once in Normal, Recovery, and Download mode so that all drivers initialize

3. Reboot your tab to Download mode

4. Run zadig.exe

5. Go to Options > List All Devices

6. Select Samsung USB Composite Device from the dropdown box

7. Click Install Driver (accept any unsigned driver prompts you get)

8. Once Zadig says the drivers are installed successfully, close it"

quoted from http://xdaforums.com/showthread.php?t=1508703
[Galaxy S III Mini General] tntted:
Thanks a lot but I just gonna pay for a repair. Sorry to waste your time.
[Galaxy S III Mini General] :
It's alright, and ask for a quote first so they don't take your phone hostage and make you pay $100+ to get your phone back, if it's too expensive come back and message me I'll try help you further!
[Galaxy S III Mini General] DroidJP:
Since this is my first post i would like to say these forums have been very useful and helpful and i thank these forums for getting me out of serious issues when dealing with android in general. Now i ran into another problem and this one seems to be quite difficult and crossing my fingers that this phone is not permanently bricked. So here it goes.

My phone appears to be stuck in cwm i tried Odin and flashed cwm and restored from nandroid backups within cwm, even using stock unrooted rom. Its still boots up to cwm every time. This all started when i downloaded quick boot app from the play store for convenience and when i tap to reboot into recovery. It boots up to recovery since then i can't get out of recovery. I am stuck and running out of options. I can boot in download mode. Flashing zips in cwm no longer works. Keeps reporting status 7 error but i know it isn't the zips because they used to work when the phone was booting up normally. I even formatted the system partition wipe dalvik cache and data several times. All because of that stupid quick boot app. Is my phone permanently bricked?

Samsung Galxy SGH-t599n metropcs..

Thank you.
[Galaxy S III Mini General] :
http://d-h.st/p94 is the link to to your stock rom, unzip and flash it via odin. Make sure it does flash correctly and isn't resulting in an error. It doesn't make any sense that you flash stock rom and cwm is still present.
[Galaxy S III Mini General] DroidJP:
Thank you! it worked!. I thought this phone was ruined. I can't believe how a power/reboot app could cause this troublesome issue. I thought with cwm you could always "recover" from a bad rom and the boot and recovery partition are left alone and you're good to go with a nandroid backup. Not this time. What if i did not have access to a PC? which has always been bothering me. I mean ROM Manager seems to be the no need for a PC solution but i hear horrid stories how this app can really screw up your phone. I guess i learned something new from this experience. So i guess if one is rooting you better have a computer otherwise shouldn't be rooting at all. Anyways, Thank you. I sure got that panic feeling from this experience so was uncalled and did not expect. I mean a power button app really? lol