yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] jtl_777:
Oh my bad. I didn't flash it yet obviously cause I didn't want to lose wifi-calling ahahah. Now I feel like an idiot. So do i need to worry about another kernel or not? just flash the rom and the modem in the OP?

---------- Post added at 11:48 PM ---------- Previous post was at 11:45 PM ----------

Also which modem do you recommend b/t JC and J4? and whats the difference b/t the two? sorry about all the Q's lol.
[T-Mobile, Samsung Galaxy SIII] TheArtiszan:
No idea what the difference is.

I just flashed the newer one because it's newer >.>
[T-Mobile, Samsung Galaxy SIII] Talon25:
I wrote what I did for my installation in my signature there is a link. It worked for me and 3 other people, maybe it will work for you? Try it out, let me know. Good luck.

---------- Post added at 09:58 PM ---------- Previous post was at 09:56 PM ----------

Flash the JC modem for T-Mo

---------- Post added at 09:59 PM ---------- Previous post was at 09:58 PM ----------

And, the AT&T kernel will enable wifi to work. WiFi calling does work with that kernel :)

---------- Post added at 10:03 PM ---------- Previous post was at 09:59 PM ----------

I think, if you are trying to go back to 4.1.2 you would need to go back to the MD5 firmware. As Doc mentioned, use Root66's MD5 T-Mo T999 firmware. I would try that if I were in your position, I have not tested it though. You could also retry the 4.3 install using the steps I used in a link in my signature it worked for a few people maybe it will for you too. Good luck!
[T-Mobile, Samsung Galaxy SIII] nfssys:
Saw that too, esp in recovery

I also noticed this behavior, and thought that I had lost root or something funky.

I upgraded CWM(latest) and still same issue, it kept displaying the /mtn/shell/emulated/ folder which only had 3 folders (0, legacy, obb).

/0/ made reference to /sdcard/ contents however the behavior was very annoying.

I flashed TWRP through ODIN and then it was displaying the /sdcard/ folder as before.

All is well now, not sure if it is a behavior with CWM with 4.3 but TWRP was able to see it just fine.

Just thought I would share my findings.
[T-Mobile, Samsung Galaxy SIII] jtl_777:
Is it necessary to use CWM to install this or will TWRP work just fine? What do you do if you lose root during install?
[T-Mobile, Samsung Galaxy SIII] _-..zKiLLA..-_:
So i followed your instructions to a t and now my wifi is broken and i dont know how to fix it and my backup md5 mismatched >.<
[T-Mobile, Samsung Galaxy SIII] beto0216:
Flash the atnt kernel in the original post I had the same issue!
[T-Mobile, Samsung Galaxy SIII] googlephone:
Any one has problem that the mobile data limit can not be changed in data usage setting?
[T-Mobile, Samsung Galaxy SIII] _-..zKiLLA..-_:
well that didnt help that just killed my data. im gonna odin back to stock lol
[T-Mobile, Samsung Galaxy SIII] zul8er:
To get data back you have to be on the MJC Baseband. If your on MD5 it won't get data. Your phone number will also be unknown.

---------- Post added at 04:01 AM ---------- Previous post was at 03:58 AM ----------

BTW. This ROM works fine. I have flashed it 3 times now because I just can't leave well enough alone. Tried to do some 4.1.2 framework modding... Nope. Tried to get wallet working.... Nope. Then really messed things up with Wanam. I'm sick of starting over. ;)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sorry you're having such problems getting this to work. Anytime you go backwards in builds, e.g. 4.3 to 4.1.2, you will have to factory reset or it'll stick at boot up.

As for why 4.3 isn't working, I'm not sure. Did you verify the md5sum on the downloads (rom, kernel and modem)? Are you certain its a T999, not a T999L? What recovery are you flashing it with?
[T-Mobile, Samsung Galaxy SIII] revwillie:
I'm still using twrp 2.5.0.0 and it flashed everything fine. I haven't upgraded because there seemed to be problems with newer recoveries.
[T-Mobile, Samsung Galaxy SIII] chrisram88:
I'm having the same problem. If I reboot, it will hang on the s3 splash screen. I'm on dmd5 bootloader. Factory reset in twrp then flashed rom followed by kernel since wifi was broken. I didnt wipe internal tho. Glad I'm not the only one lol.
[T-Mobile, Samsung Galaxy SIII] kingston73:
You should read this thread:

http://xdaforums.com/showthread.php?p=47892939#post47892939

Answers lots of questions. For anybody who is considering making the jump from 4.1.2 to 4.3 I'd say read that entire FAQ thread first before you do anything at all.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Did you try both modems? Any mods? Strange that this is happening to you guys. To be sure check for that recovery-resource.dat file. Also, open install-recovery.sh and make sure it looks to be calling daemonsu.

Just as a test, try flashing the rom w/o the kernel. Boot up fully, then go back and flash the kernel

Yes, I am oulling this outta thin airand have little to base it on, but there has to be something different for you guys since it works fine for others....
[T-Mobile, Samsung Galaxy SIII] chrisram88:
I tried both modems. No mods at all just straight leak 2 debloated. I will flash with your instructions and will report back. Might be later in the evening since Im working 3rd shift and need some sleep soon :)
[T-Mobile, Samsung Galaxy SIII] kramer987:
ok so i got it to work and here is how.

first i will list what problem i was having: i would flash either the STOCK leaked ROM posted by docholiday along with the kernel and the appropriate modem and things would be fine. i'd boot into the ROM and set my phone up. it would work 100% fine. calls, data, wifi, etc. then, if my phone rebooted for any reason, it would hang at the samsung splash screen.

first attempted solution: i performed a FULL WIPE (cache, dalvik, factory reset, data, system), everything. then i'd reflash, boot, reboot 100% and then upon first reboot it would hang again.

next solution: full wipe. tried flashing an old ROM like Wicked10. 100% flash. 100% boot. reboot and hang.

next solution: full wipe. tried flashing the stockmod rom lite. 100% flash. 100% boot. reboot and hang.

next solution: ODIN flash 4.1.2 route66 rom. 9min25sec to complete. get PASS. reboot into ROM and it hangs. i do some google searching and i have to perform a factory reset after i flash the ROM. i do so and it boots to the ROM. i reboot, and it reboots no problem.

next step: i flash the stockmod lite 4.3 rom. first i do a full wipe. everything. flash the rom. boot into the ROM. reboot and .... success. it reboots just fine.

so what did i learn? i think after you flash the 4.3 leak or stockmod ROM you have to do ANOTHER factory reset. unless you do a factory reset, you will not be able to reboot without it hanging at the glowing samsung boot logo.
[T-Mobile, Samsung Galaxy SIII] Talon25:
You don't have to upgrade CWM to install this and should be the same for TWRP. As for root, when you're done flashing and press reboot via CWM it might give a warning saying that the ROM might have lost Root and do you want to gain root back (something to that effect). Choose yes and you will be good to go.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sorry if I wasn't clear about that. Its what I was intending for you guys to do previously. Glad you got it working and I hope the rest goes smoothly for you!

I don't think this was an option selectable by the user. If I remember right, when you reboot it will check for root and at that time will offer to fix it if needed.

------------------------------------

[MENTION=535343]all[/MENTION]

I was rereading posts and thought I should mention that I never recommend wiping /system. Any rom you flash will do this for you. But I have seen on several occasions where someone did this, then something went wrong and they couldn't get anything to flash correctly. Since they wiped system, they now had no OS to boot into! A few times I saw it take a few days to finally get their phone working again! So just a word of caution.

Except in very rare cases, I don't think it should ever be done.
[T-Mobile, Samsung Galaxy SIII] chrisram88:
i tried to factory reset again after i flashed the rom. it still hung after I reboot. i guess i have to odin flash 4.1.2 route66 since that is the only difference in installation method that i see from what im doing.
[T-Mobile, Samsung Galaxy SIII] Talon25:
Thanks Doc, I'll go back and edit what I said - misworded. You are correct, it should ask when you press reboot via CWM that the ROM may not have root and do you want to root.
[T-Mobile, Samsung Galaxy SIII] anil2653:
Thanks Doc for this information at least for me as I was always formating system of course I keep nandroid backup too but precautions is better than cure

Now I will avoid formating system except specifically asked

:thumbup:
[T-Mobile, Samsung Galaxy SIII] droctii:
I'm experiencing random reboots.

Did a full wipe. Odin rooted66 stock rom, then flashed this rom with the recommended modem and kernel from the original post. I've wiped then cache and fixed permissions

Is anyone having these problems?
[T-Mobile, Samsung Galaxy SIII] googlephone:
I have freezes when using some root apps and have to take battery to reboot my phone. I did factory reset before flash this Knox free rom. It only happens with some root apps, weird.
[T-Mobile, Samsung Galaxy SIII] Last Hegemon:
Phone freezes if I use rooted apps

Hi guys / Doc,

I've installed the T999_Official_UVUEMJC_Deodexed_KnoxFree with TWRP (had doc's root66 UMD5before 4.1.2), installed att kernel and modem but if I try to run a superuser app, phone freezes (have to reboot it each time). I did not do a system wipe or factory reset, just dalvik and cache (thought that's what was recommended...unless I misunderstood). It asked if it should inject root at one point and I selected yes. I did not do an OTA or Kies update; always did root66 and never had root problems. Upgrading ROM did not wipe my previous apps/files; they're all in there.

I'm getting mixed messages. I ran Root Checker and it initially told me I have root but when I ran it again it said that I don't. I tried to reinstall Super SU and it said: There is no SU binary installed and SuperSU cannot install it. :(

Please help. Phone runs fine and is fast as long as I don't use apps which require root access. If I use Secure Settings, Network Log, SuperSU it starts freezing. They randomly work but not consistently. Should I do a factory reset or should I reinstall the ROM? What did I do wrong, missed something? Appreciate your advice! (sorry for posting in two places but want to help others too)
[T-Mobile, Samsung Galaxy SIII] ega2oo2:
Anyone tried to odex this ROM after flashing?
[T-Mobile, Samsung Galaxy SIII] Talon25:
Hey man, you should have done a full system wipe/factory reset coming from 4.1.2. This is because there is a new base/firmware for 4.3 that you need to get into your system. Check my signature for install directions that worked for people. You were correct for injecting root through recovery when prompted to do so. Good luck, let me know how it turns out.

---------- Post added at 12:10 PM ---------- Previous post was at 12:08 PM ----------

I haven't heard of anyone trying to odex this rom yet after installation. Just curious, why do you want to odex :)
[T-Mobile, Samsung Galaxy SIII] Coug76:
Performance. Odexing can do good things for efficiency. Deodexed roms can be themed and customized much more easily.

Hastily spouted for your befuddlement
[T-Mobile, Samsung Galaxy SIII] moonfire711:
Okay, so I have one issue on 4.3 that is bugging me. When I make phone calls, the person on the other end says I sound garbled. Not to the point that they can't understand me, but it's not good quality. I wasn't sure about this, so I factory reset, did everything again in the way of setting up 4.3, and still the same. I took my wife's GS3 which is still on 4.1.2 during a phone call and I could immediately here the difference. Bad enough for me to go back to 4.1.2 for now.

Has anyone else noticed this? (I think I read a while back that someone said something similar to this)

Could this possibly be from using the AT&T kernel?

Note: I was using the knox free version without any other issues at all.
[T-Mobile, Samsung Galaxy SIII] yakabud:
Fresh Installed the official release from the op, coming from the leaked version but I couldn't enable the wifi. Tried to installed the MJC modem still no luck. Glad I have nandroid backup.

But I never had a problem with booting and root (installed the supersu from op) did a full wipe, data and factory reset and cache.
[T-Mobile, Samsung Galaxy SIII] mryounghc:
I also get this. People say it sounds bad. Through headset and bluetooth is fine though.

A reboot fixes It. Also when answering a call they dont here me the first time. I have to wait about 2 seconds before i say "hello".

This happens every call.
[T-Mobile, Samsung Galaxy SIII] moonfire711:
I appreciate someone confirming that it's not just me. I have restored back to 4.1.2 for now. Wife says I sound normal again, at least relative to how I used to sound. Maybe not so normal compared to other people. ;)
[T-Mobile, Samsung Galaxy SIII] gavilan2010:
Can anybody confirm if flash work on this Rom I installed but I don't have sound on live videos...
[T-Mobile, Samsung Galaxy SIII] Talon25:
I don't think it would be the AT&T kernel, but could be an issue with the modem. Try reflashing the modem and see if that helps. If not, maybe trying the MJ4 modem and see if that makes a difference?

---------- Post added at 08:09 PM ---------- Previous post was at 08:08 PM ----------

Did you also flash the AT&T kernel? WiFi does not work with the ROM itself (issue with the T-Mo kernel at the moment).
[T-Mobile, Samsung Galaxy SIII] moonfire711:
After restoring to 4.1.2, I still had the latest modem, and my wife said I sounded good again. So, therefore, I don't think it's the modem. Something in the rom, or kernel. My bet is placed on the Kernel.
[T-Mobile, Samsung Galaxy SIII] yakabud:
Thanks for the reply. Yes I did install it, but I had no data and IMEI after that.

---------- Post added at 10:39 PM ---------- Previous post was at 10:37 PM ----------
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
For those having priblems with root, did you update? If so this will cause what most of you were reporting. For now, do not update SuperSU unless you care to re edit several scripts each time. I will look into an easier solution, but the included files work just fine for now.

For those having issues with voice calls. This is probably caused by a few things, starting with the towers in your area. If they have not been upgraded, or are having problems, the latest modems may not be able to function correctly. I seriously doubt it is the rom, modem or kernel on its own. I belueve only 2 have reported it, out of several thousand downloads of it. You can try the other kernel, but may not have working WiFi. I recommend redownloading (check md5) and try again, clean, no mods, no updates. Also be sure to try both modems. There are always devices that simply do not function exactly like the rest do, so don't rule this out either. The only other thing I could think to tell you would be to flash the full update. But that is entirely up to you.

For anyone who has no working wifi, or you have no data signal and/or imei, please re-read the op and follow instructions there. No wifi means you need to flash the kernel, no data/imei means you need to flash the modem.

A large number of people have stated the rom/build has been performing extremely well. To me this just means that most of the issues some are experiencing are indeed fixable. (Or they are being caused by mods, dirty flashes, restored backups, etc).

So if you do encounter bugs or issues, be sure you haven't flashed mods or restored system data from an older build. Also consider factory resetting and reflashing.

Hope that helps some of you out!
[T-Mobile, Samsung Galaxy SIII] moonfire711:
Thanks Doc.

I will say that I have only tried the latest modem, not the previous one link in the OP. However, when I updated to 4.3, I did get poor sound quality during phone calls for those who were listening to me on the other end of the call. When I flashed back to my nandroid backup, everything was restored except the modem. I am still on the latest modem. The sound quality is back to normal and sounding good. So, based on this, I would conclude that the modem is not the problem. I'm not sure what is, but the evidence seems to clearly show that I've had both good and bad results with the same new modem, but the good results were on an older rom/kernel and the bad results were on the newer rom/kernel.

Perhaps I'll get bored and flash 4.3 again with the previous modem just to be sure.

Thanks again for your work on bringing this to everyone, and for offering your continued support and advice.

Oh, and I've flashed my fair share of roms. I have certainly read every post in this thread and I have followed all instructions precisely. I have done a full factory reset and wipe when flashing this rom, and like stated before, I have had no other problem except this one.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
It is odd to say the least. I never like troubleshooting qos type issues related to the cell network. There are literally dozens or more possible things you can look at that can affect the connection from phone to tower, and there's no guarantees there isn't just some anomaly in either the tower or phone. Could be anything from the build.prop to how a particular fw build works with a particular modem/kernel/whatever. Add to that the fact only two of you have reported it, and the potential for finding the cause diminishes, a lot.

If you do give it another shot let me know. I can always give you at keast a few things to try. Sorry you had trouble with it though.
[T-Mobile, Samsung Galaxy SIII] Last Hegemon:
Doc, would appreciate it if you could look into this! It's an amazing ROM but SuperSU acts up once in a while (either shuts phone off or freezes it...not often but it does happen).
[T-Mobile, Samsung Galaxy SIII] ega2oo2:
Coug76, that's exactly what I mean. Actually, I always prefered to flash odexed ROMs because of their better promptness. Customization is not my primary goal, only root. Although this new ROM is very good and stable for me (thanx, Doc!), I see a noticable delay when starting apps, I guess that may be due to its being deodexed.

I've found several apps which may help, one is Odex Me. I'm a bit worried about breaking something, so I kindly ask an advice, is it worth trying with this ROM?
[T-Mobile, Samsung Galaxy SIII] 4Orr:
You could perform a nandroid prior to odexing the ROM. Rom Toolbox can be used to Odex the Rom also.

Edit. Sorry, I meant Titanium backup.
[T-Mobile, Samsung Galaxy SIII] Sincitybronze:
I'm confused about whether it's possible to flash (backward) to 4.1.2. Will this result in bricking my phone or is that only a possibility if I updated OTA?
[T-Mobile, Samsung Galaxy SIII] droctii:
Enjoying the ROM. However, in addition to the infrequent random reboots, I'm noticing that sometimes the phone will simply not dial out. It just momentarily "dials" the number but immediately cuts off -- repeatedly. The only suloutions I've found are rebooting or toggling between airplane mode on/off.

Also, separately -- sometimes I notice that turning data off really doesn't turn it off.

I'm running the JC modem and AT&T kernel.

Thanks.
[T-Mobile, Samsung Galaxy SIII] Talon25:
It's possible you need to use Odin to flash the older firmware use Root66s, then you can flash 4.1.2
[T-Mobile, Samsung Galaxy SIII] Sincitybronze:
Thank you. And just so I'm clear on this, what should I absolutely avoid doing to prevent a brick like the one doc had?
[T-Mobile, Samsung Galaxy SIII] calexchelse:
I was running doc official deodexed ROM. Had the last everyone is talking about. Since taking the plunge and flashing Mr.Robinson's root66 test, making sure root is active, then reflashing docs deodexed official ROM, lag is gone. I'm really beginning to believe that the new update does change a few things. And those changes are the only things that will keep the lag from occurring.

Just a thought. Not a Dev but after several tests that is what I think. When I odin'd the root 66, it did a weird upgrade that it hadn't done before.
[T-Mobile, Samsung Galaxy SIII] 0RBon:
??

It's there a way to prevent the /0/0 folders structure ?

:crying:
[T-Mobile, Samsung Galaxy SIII] googlephone:
SuperSU freezed my phone dozens time in one single day. Some root apps gained root once but lost root after some time and freezed my phone when I tried to load root apps. Loading supersu would also freeze my phone 9 out of 10 when opening it. Yesterday I deceided to fromat /system and only wipe cache and dalvik cache, then reflash the rom again in cwm recovery. Now I have no more problem with supersu freezing problems when using some root apps and my phone feels much smoother.

---------- Post added at 12:10 AM ---------- Previous post was at 12:00 AM ----------

You can not flash older firmware if you already upgraded the 4.3 firmware. It will brick your phone. If you didn't upgraded to the 4.3 firmware (if you only flashed the 4.3 rom and modem, without flashing 4.3 firmware), your firmware is still the old one so you don't need to flash older firmware . You can flash old rom and modem.

---------- Post added at 12:14 AM ---------- Previous post was at 12:10 AM ----------
[T-Mobile, Samsung Galaxy SIII] Talon25:
This should be incorrect, as far as my understanding goes if you installed Doc's 4.3 (and did NOT receive the OTA update my T-Mo) you should be able to go back to previous firmware (MD5 I believe it is). I believe Doc also said this a few pages ago.

EDIT: I believe this is to kramer987's problems when he flashed 4.3. A few pages back from that, he also says it is possible from flashing via this ROM, but NOT if you got the OTA update. Heres the link to look into it a little more before Doc (or someone else that already did this) can give a cut and try solution.

[MENTION=2861685]Sincitybronze[/MENTION] If it was me trying to get back to 4.1.2, I would download MD5 from Root66, load my SD with 4.1.2 rom (probably the modem too) and then I would ODIN the MD5 firmware, boot recovery factory reset wipe flash rom then reboot and see what happens. Again, this is what I would do but have NOT tested
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Definately will. Just been too busy with family and the holidays!

I may be wrong, but doesn't TiB only odex the /system/app folder?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
if you updated to 4 3 via OTA or Odin, you should still be able to flash older roms, kernels (and maybe modems?). But you can not, MUST NOT try to force flash the older full firmware such as what you'd find in my firmware thread.

If you did NOT take the OTA, or odin the 4.3 firmware, you should be fine to keep doing things as you always have.

where are you seeing that data doesn't turn off? How are you switching it off?

Some things to try when either of those happen:

Grab a logcat

Try some of the developer options such as Choose app to debug, show cpu usage, etc, etc.

Simple! Do NOT be curious!!! Lol!

I bricked in a rather unique way, so I really doubt anyone would end up doing what I did unless it were deliberate!

I do believe that this rom is a good solid driver for most, but I do also believe that you won't get maximum stability and performance unless you flash the full firmware.

It something each person will have to decide on their own, since it us a trade-off

To my knowledge, no. I thought google was going to fix it a while back, but I guess it was just a rumor.

Well...actually there could be a way. Ill have to look into it later on though, and it'll probably either be really easy, or waaay beyond my ability to do anything!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If I were to edit chainfires SuperSU update to work for us, and post it in the op, would that be satisfactory for you guys for now?

You couldn't update via play store, and would have to wait for me to redo each release. Untill a better solution is found anyway. Thoughts?