yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Jack Test:
can I reload an official firmware to the phone

My phone got bricked, the phone is in official state and never been rooted. But now it is stuck in Samsung S3 logo, btw, it is T999. I believed it is still in version 4.1.2

So I got the official firmware downloaded and the phone can boot to Download mod by holding volume Down/Home/Power keys.

1) Use Windows 7, it said that the phone is not in USB debug mode.

2) Linux Casual, JOdin3, it is asking for PIT file. But I don't have the PIT file.

So here I need help!!!

a. ) Does anyone have a PIT file to share for T999 version 4.1.2, and would that work?

b.) Any way to reflash the firmware using Odin or JOdin?

Thanks a lot.
[T-Mobile, Samsung Galaxy SIII] Teracotta:
So hey, I just got a T999N, and I'm new to the S3 business (have an S4 Mini) so I've got some questions, reading this thread.

1. I'm looking for a STOCK rom that is DEODEXED. I look here and I don't even see root for T999N. Nobody ever got around to this?

2. The phone I have is using Android 4.1. JellyBean, so presumably it does not have Knox. Where can I get the stock, deodexed ROM for this phone that isn't 4.3, because I don't want to have to deal with Knox, thanks.

3. Why is the flash counter an issue? On the S4 Mini, if I want to reset the counter, I just flash the original firmware version and the counter is reset. Why can't you do that with the S3?
[T-Mobile, Samsung Galaxy SIII] kvends:
can this work

can this work with a stuck up logo on samsung? im using samsung sgh-t999 stuck on logo can this steps work? need rply thankyou.
[T-Mobile, Samsung Galaxy SIII] namelnw:
New
[T-Mobile, Samsung Galaxy SIII] NancyJ:
Just wanted to say...

Hate to de-necro this thread but I created an account just to say, "Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you." FINALLY got my friggin' phone rooted.
[T-Mobile, Samsung Galaxy SIII] DavidWCS:
I'm curious how you approached your phone modding. Traditionally it seems to use ODIN to install a recovery, such as TWRP. Then using TWRP to flash a custom ROM.

Maybe there are others who still tinker around with this old (circa 2012) Samsung Galaxy S3 i747 While I am a newbie, I have enjoyed flashing Custom ROM's , from CyanogenMod, thru various versions of Lineage, and now CRdroid.

Totally free of Google; no Google Play Store, no Google Pay, no Google Framework, no Gapps, no Google spyware, no Google bloatware, no Google tracking etc.

I download all my apps as APK's which are readily available on the Net ( Google them . . . just kidding! ).

My older Samsung S3 i747 was a 'd2att' originally locked to Rogers, in Ottawa, Ontario, Canada. Then switched over to MTS (Manitoba Telephone System). Now running on Bell Canada. My replacement is also a Samsung S3 i747, originally running T-Mobile in Arizona, now running on Bell Canada.

Damn fine phones.
[T-Mobile, Samsung Galaxy SIII] TLX317:
And I thought I was cool for using a 2 year old OnePlus 5T haha. Hope you guys enjoy messing around with the S3! It was one of my favorite phones to own.
[T-Mobile, Samsung Galaxy SIII] javaman83:
Used the Odin method described here to go from the UVDLI8 leak to UVDLJA. Worked flawlessly. Thanks for the easy guide.
[T-Mobile, Samsung Galaxy SIII] akapaul26:
Maybe I should of been more specific. I am running blackjelly official jb rom. I used the mobile odin pro to flash the ota firmware. I am not sure it worked as I got some errors...can u shoot me some advice on this please?

Sent from my SGH-T999 using Xparent Blue Tapatalk 2
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Can you be a little more specific on the errors you got? If you flash the OTA in Mobile Odin, it should work just fine, were you running a modified system prior to flashing the OTA?
[T-Mobile, Samsung Galaxy SIII] akapaul26:
I was just running the rom out the box. Do i need to flash a stock rom? It ssid 348 of the some 1024 system files didnt match and something else..

Sent from my SGH-T999 using Xparent Blue Tapatalk 2
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Oh, ok. You were probably not on the correct build for the OTA to work. The OTA was made to patch only UVALJ4, the last ICS release. If you were not updated to that build already then it would have failed. It does sound like Mobile Odin let it patch what it could though, which seems a little odd. I havent seen it do that before.

I would not count on being up to date. It sounds kind of like you will be running a mixed build of sorts.

Your best bet is to flash the root66 firmware via Odin. I am thinking that Mobile Odin would be ok to use, as your other partitions were likely updated correctly when you did the OTA. Unfortunately there is no way I know of to tell for sure, unless you have a log of the install. Which is why I suggest using desktop Odin, just to be certain.
[T-Mobile, Samsung Galaxy SIII] akapaul26:
Ok will try that.. the root66 is a not zip format whuch threw me off.

Sent from my SGH-T999 using Xparent Blue Tapatalk 2
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
right, When you download it it will be in a .7z format (7zip). Extract the .tar.md5 file and put that into the PDA section of Odin.
[T-Mobile, Samsung Galaxy SIII] drocha86:
Hey doc got a question I'm on frostyjb v7 with i7 firmware and want to update to v8 with the new firmware LJA do I just use the rt66 in Odin or do I have to go to my stock ROM and firmware. And after I do the rt66 do I need to also flash the LJA firmware.

Sorry for the noob question but I want to make sure thank you.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
All you gotta do is flash root66 via Odin. Thats it!

If you want to flash roms afterwards, install recovery from rom or goo manager, then flash away!
[T-Mobile, Samsung Galaxy SIII] Androiduser96:
HELP! I keep getting the no PIT partition error. I'm flashing the official JB fw with root. I extracted the .tar file from the .7z. what do i do?
[T-Mobile, Samsung Galaxy SIII] Kelevro:
I've also got a question (sorry for the noobyness):

I'm on XquiziT's ROM (Jellybean based) right now, if I flash the .tar file (the one that doesn't have preroot and will get rid of root) from sammobile (or your mirror) using ODIN, will it work alright? Or will I have to devolve to an ICS ROM first?

Thanks!
[T-Mobile, Samsung Galaxy SIII] CousinMikeyP:
Doc.

Check Ur PM.
[T-Mobile, Samsung Galaxy SIII] :
So I'm on basehand T999UVLH2 ICS Wicked Rom V7. When I first got my phone it only came with ICS so now I want to put FrostyJBV9 on my phone. So all I do is download root66, flash that using Odin on my windows computer & then wipe, install the JB Rom? Is it that simple? & which root66 do I download ICS or JB one?
[T-Mobile, Samsung Galaxy SIII] akapaul26:
Hey thanks m8. Everything is good. I installed through odin, reflashed twrp and reinstalled my backup....running all fresh now!

Thanks again!

Sent from my SGH-T999 using Xparent Blue Tapatalk 2
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Can you post exsctly what the error says and when it happens?

Im in snd out the next few hours, but ill try to help as best I can

yup, itll work just fine. No need to preflash anything.

It is that simple! Use the latest jb firmware.
[T-Mobile, Samsung Galaxy SIII] Androiduser96:
While trying to flash the latest JB official fw. I keep getting the "PIT partition" error on Odin. What do I do? I tried googling. Nothing helps.
[T-Mobile, Samsung Galaxy SIII] :
So clockworkmod recovery gets erased after flashing root 66 right? How do I get it back? I see you said

use your root capable file explorer, browse to and delete or rename the following two files:

/system/recovery-from-boot.p

/system/etc/install-recovery.sh

Now, reinstall TWRP or CWM (I suggest using Goo or Rom Manager to do this)

Reboot recovery to verify the correct one is installed and working!

^ I don't get that. So do i boot up & run the rom manager app then get CWM back basically> do clean full wipe & install the JB rom of my choice?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ive never run into a PIT partition error.

PIT (Partition Information Table I believe) files contain the partition layout, or mapping, of your device. Block number, locations, sizes, etc. As I understand it, they are generally used to repartition the device.

Ill try to look up some info, but as I said, im in and out for the next few hours.

Thats why I asked the exact error and when it occurs. Does it just say PIT Error and thats it?

Does it happen when you click Start, or does it seem to go for a bit then happen. What is it flashing when it happens? In the left box it should tell you what its currently flashing, system, modem, boot, sbl, etc.

This info would make it much easier to diagnose and troubleshoot.

That should only be the case if you flash the OTAs. It shouldn't be in the root66 version. If it is, let me know please.

If so did you delete/rename those two files? After that, you get Rom Mgr for CWM or Goo Mgr for TWRP. In the goo app, press menu and choose install openRecovery Script. In Rom mgr, I think its an obvious option.
[T-Mobile, Samsung Galaxy SIII] :
wait wait wait im confused lol, I haven't done anything yet which is why im asking these questions. So Once I flash Root66 does CWM get removed?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yes. But you shouldn't need to worry bout those 2 files you mentioned.

After flashing just go straight to reinstalling recovery. Thats it.
[T-Mobile, Samsung Galaxy SIII] :
Thanks for your help, I figured it out. I flashed using odin then used rom toolbox to get CMW back & did full wipe to install the FrostV9 rom
[T-Mobile, Samsung Galaxy SIII] nviz22:
Have they leaked the 4.1.2 version of Touchwiz for the T999 yet?
[T-Mobile, Samsung Galaxy SIII] kipster3001:
Don't know if this is the right place to ask this question but, has anybody heard about having a multy window feature like the note 2? I was reading a thread about it leaking for the s3 i9300, do you guys think we will be seeing this soon for us???

Never mind I found what I was looking for thanx...
[T-Mobile, Samsung Galaxy SIII] mahatasin:
Rooting using rooted kernel?

Hi,

My phone is completely stock. I don't want to flash the entire firmware. Is it possible to root by simply flashing a kernel? If i root, is there by any chance may I loose wifi calling? The last question is kinda stupid, but just confirming.

Baseband version: T999UVDLJA

-Thanks in advance.
[T-Mobile, Samsung Galaxy SIII] Kelevro:
Thanks, Doc! I've downloaded it and will try it if the new OTA-based Stock ROMS are funky. The whole reason I wanted to stop all this was because of the faulty leaked ROMs that would make my phone crap-out.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No the kernel isnt the root of root! There are a number of ways to do it, but I like using root66 because its the easiest and safest.

Theres CF-Root by Chainfire in Original Development, S3 Toolkit stickied next to this thread, zedomax's method in development....

You can use any one of those.

Just fyi though, it is not possible to root without Odin.

(well, there's heimdal on mac) Not really sure why youd be against flashing the FW. Not trying to convince you, just curious.

To each his own.

So far none of the problems we had with the leaks. A small number if folks have reported issues like the leaks, but its not the rom causing them.

Mine is running beautifully!
[T-Mobile, Samsung Galaxy SIII] Jose0726:
Hi i was wondering if anyone else havong this issue...im getting this red border around my screen when i open apps or lockscreen...anyways to trigger that off?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
First ive ever heard of that issue. Did you just update? Root?

Did you try a reboot? What was the last thing you did to the phone before it started?

Try also, if rooted, boot to recovery and wipe cache and dalvik.

If that doesnt help, go in recovery again and factory reset. (Note: if you have stock recovery this will wipe your internal sdcard along with everything else!)
[T-Mobile, Samsung Galaxy SIII] Jose0726:
Thanks for the response. Well i was on the latest ics root66 version. I tried doing the ota update via software update on phone 2 times but got an update failed loading default configuration t mobile screen...so i downloaded the jb root66 version and flash it via odin. Im on stock recovery and hadnt done no wiping because i didnt want to get nothing erase.. heres a pic of what im getting. Pd: i did it wt. Oaint but its exactly what im getting on every unlock screen etc
[T-Mobile, Samsung Galaxy SIII] dmarco:
That will be released in the 4.1.2 version of JB which should be Dec sometime, for T- mobile anyway, not sure about other carriers :D
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sorry, not sure what you were trying to say there.

Anyhow, I understand not wanting to wipe anything, but oftentimes its the only solution.

Install twrp using goo manager from store.

Make a nandroid backup so you can restore back to exactly how you are now if it goes wrong.

Then start with the cache and dalvik wipes. These do not delete any important user data. Dalvik will rebuild at boot (can take a few min, be patient).

If still not fixed do a factory reset. With twrp installed it wont touch your internal sdcard. It will wipe all apps and settings, but you can always restore the nandroid if its not fixed.

Sorry man, but with such a rare issue thats the best way I have to try and fix it. You could always post in Q&A where more people will see your question too.
[T-Mobile, Samsung Galaxy SIII] titaneds73:
just wanted to say thank you doc for the awesome fw and as for unlocking my phone i was able to unlock it with aokp installed just wanted something different been on aokp too long, did wait 15 min but never booted, went into stock recovery did data factory reset and cleared cache and booted fine ,thanks again DOC
[T-Mobile, Samsung Galaxy SIII] Bitcloud30:
Could you make a video on how to root with the latest pre-rooted firmware? XD
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You flash it in Odin as you would any official firmware. There should already be lots of vids out there for this.
[T-Mobile, Samsung Galaxy SIII] Jose0726:
sorry lol i mix letters sometimes haha i meant i use odin..ne ways thanx..i did a cache wipe and it solved the red flashing borders. left it stock recovery since im kinda a flashing adict guy and im not ready to start flashing roms daily like i used to wt. sgs3 staying stock for a while jajan
[T-Mobile, Samsung Galaxy SIII] titaneds73:
check out ZEDOMAX on youtube and he also has a site called galaxys3root.com very useful how to videos on there .
[T-Mobile, Samsung Galaxy SIII] drocha86:
How can I install the touch recovery. Do I just flash it in recovery.
[T-Mobile, Samsung Galaxy SIII] kponti:
Do the updates wipe your phone?

Also ODIN does not recognize the rooted version of the OTA, I cannot even select it, I think it has something to to with the .7z file extension, it is not being picked up as an option on ODIN
[T-Mobile, Samsung Galaxy SIII] buzzltyr1818:
so i tried to odin the root66 and now i cant go into cwm...after i odined the root66 file should my settings still be there or should it have been like i just pulled it out of the box fresh like i have to set the google acoount? cause my settings were still there. i was coming from jb v7. im trying to upgrade to v9.1 but ran into this problem. i see in one of the post he wrote...

[Q] After updating via OTA, I can no longer boot into CWM or TWRP recovery! Stock recovery always boots up! What do I do??

[A]

This is actually a very simple fix!

Using your root capable file explorer, browse to and delete or rename the following two files:

/system/recovery-from-boot.p

/system/etc/install-recovery.sh

how do i get to these two files on my phone to edit them? hopefully this will fix my issue.
[T-Mobile, Samsung Galaxy SIII] buzzltyr1818:
^^^ nevermind got it working
[T-Mobile, Samsung Galaxy SIII] kponti:
So CWM aborted due to an error, ODIN will not see the file needed...I guess no JellyBean for me
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If its one of the ones with a .zip extension, yes. If it has a .tar extension, then you have to use odin.

And for the zip files, you have to already have a custom recovery installed.

you have to extract the file from the 7zip archive. You will be flashing a .tar.md5

good job man! Sorry, haven't been on much at all the last couple of days.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
I have one question. I updated my stock unrooted GS3 (T-Mobile) to the latest version (Jelly Bean) via the software update on the phone. Everything was working fine before and after the update. I wanted to root it so I downloaded the Root66 file corresponding to the latest update that I have, and flashed it using odin. After the phone restarted nothing was deleted on the phone, superuser and root was added to the phone. But wifi calling started to give problems, it disconnect from time to time. Any idea how to fix it? if not I will have to flash stock without root and keep using it that way. Thanks in advance
[T-Mobile, Samsung Galaxy SIII] cccheel:
Soft Brick?

Longtime flasher here. So, I attempted to use Odin to flash route66, per instructions. Everything went fine in Odin (got the PASS), but now the phone is stuck at the SAMSUNG logo. Please help.

PS I came from CM10.
[T-Mobile, Samsung Galaxy SIII] scrued:
I think you have to do a full factory reset first before you odin your phone.
[T-Mobile, Samsung Galaxy SIII] cccheel:
Yea, I'm not sure how I missed that. I was able to manually get into recovery. Should I go through the whole Odin process again? I'm at the point where I have root and am on the latest stock. Can I just go ahead and flash FrostyJB 9.1?
[T-Mobile, Samsung Galaxy SIII] scrued:
After you do a full factory reset and odin the official JB with root, then you can flash any JB roms you want.
[T-Mobile, Samsung Galaxy SIII] cccheel:
I tried flashing FrostyJB in recovery, and it said it did it, but whgen the phone restarted, it was on stock. I did get a weird message about Android upgrading and a counter that went up to 204.

I just did another factory reset and ODINed route66 again. Hopefully, it'll work this time, and then I can flash FrostyJB like normal.
[T-Mobile, Samsung Galaxy SIII] kponti:
DocHoliday77 I know I clicked thanks but seriously thank you again, I didn't realize what a simple problem I had (file not unzipped). Thanks again
[T-Mobile, Samsung Galaxy SIII] buzzltyr1818:
i didn't factory reset before i odined, thats probably why all my info was still there like my background and all my apps but it was successful. only issue i had was getting cwm back on. i odined it but wouldn't stick, the way i fixed it was odined the file again but didn't check auto reboot, after file was loaded pulled battery to restart phone and bam! it stuck. prob something i did wrong and was a simple mistake but if anyone runs into this try that and itll work. dont know since i didn't do factory reset before odining the root66 file if thats considered a dirty flash but after i installed the new 9.1 everything is all great. and yes i did do usual steps factory, cache, dalvik before i flashed rom. thanks doc, dj, and darron i think for all your hard work, the rom is amazing battery like is fantastic. 10rs and still have 87% left!!! themes are awesome, got so many compliments from your royal blue color, now everybody asking me to do this to there phones!! without people like you our phones would be so boring. :laugh:
[T-Mobile, Samsung Galaxy SIII] darkphantom:
worked like a charm :) I didn't reset and all my apps are still here and functioning!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Frosty is a stock based rom, so itll look just like stock tw in a lot of ways. Check about device in settings to verify youre on frosty

The counter is it building dalvik cache, itll happen when you flash a deodexed rom.

hmm. I need to look into it, but usually the only way stock recovery sticks is if youve updated by OTA. See post 3 for details on it.

Glad your up and running!

Many times factory resetting isnt necessary. I do recommend it when changing to a different android version (required if going backwards) just to ensure everything is compatible. But if youre running good than thats a bonus!

Also a lot of times itll hang during boot, forcing a reset. Used to not hapoen so much but lately it seems it does.
[T-Mobile, Samsung Galaxy SIII] potentdro:
Is it normal to not have these two files?

/system/recovery-from-boot.p

/system/etc/install-recovery.sh

So can I proceed to flashing the recovery using goo?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Its fine. They should only show up if you ever flash an ota update. Its the method sammy uses to patch recovery for an update.
[T-Mobile, Samsung Galaxy SIII] Nabeel10:
So I followed the instructions to the T, and got root66 JB stock up and running. I then installed goo manager to get TWRP 2.3.1.

Then I reboot to recovery and install Wicked v1 JB, but for some reason it is hanging on the boot screen.

anyone know whats up?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Need a factory reset. Nandroid first though.
[T-Mobile, Samsung Galaxy SIII] cccheel:
Thanks for all your help, Doc. I got it figured out.
[T-Mobile, Samsung Galaxy SIII] Ryan79:
Anyone else having issues installing apps from the market? I installed the Root66 update via Oden, did a factory reset and wiped the cache.. and I'm able to get about 2 apps installed then the market app bugs out, and every install comes up with the following error:

Error "any app name" could not be downloaded due to an error (error retrieving information from server. [RPC:S-5:AEC-0])

any idea how to fix? I can go into the stock recovery and do a factory reset... and that gets me back to where I can install 2 apps again... then the error returns

Thanks!
[T-Mobile, Samsung Galaxy SIII] titaneds73:
off the top of my head clear data in google services framework,clear data in playstore and reboot,install goo.im app and install twrp recovery,go into recovery and wipe cache, dalvik cache and fix perms. and if that still doesnt work then re download .did you check the md5? hope this helps
[T-Mobile, Samsung Galaxy SIII] Ryan79:
I did check the MD5 but for S&Gs I'm downloading the Root66 again and running through the flash...

if that doesn't work, I'll see if I can flash recovery from oden to try and fix permissions/clear dalvik.... attempting to install anything from the market fails... since the playstore attempts to update applications before I can get to it and then the error occurs.
[T-Mobile, Samsung Galaxy SIII] Ryan79:
so, it looks like the re-flash did it... thanks for your advice though titaneds!
[T-Mobile, Samsung Galaxy SIII] titaneds73:
yeah no problem,in my experience sometimes even though the md5 is matching a re download works dont know why,and if you go on google you can down load the apk for goomanager and install twrp recovery,you dont have to use odin.i have always liked twrp recovery never failed me
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
That was an odd problem. Glad you got it fixed man! :thumbup:

Thanks for helping out man!

Agreed on TWRP.
[T-Mobile, Samsung Galaxy SIII] titaneds73:
yeah no problem DOC,thanks for the great rom.let me pick your brain for a min if you some time.i installed the root66 rom it was perfect call me crazy but i like touchwiz,im on my 3rd day i think and today all of a sudden it just started getting really laggy,i tried a reboot ,i tried wiping cached fixing perms and it was still laggy,i checked the taskmanager and to me it had an unusually high ram,or maybe im not use to my phone taking up that much ram but it was near aroung 1 gig of ram,is that normal and have you received any lag at all?thanks for your time.