yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Well, guys, I have some bad news on my end... My S3 is hard bricked, and despite all my efforts, I have not been able to bring it back to life. I am not yet sure where this will lead, but at least for the moment, there is going to be little I can do in the way of further support and development. I will of course try to help out as best as I can, but not being able to flash the rom, test, or even just generally make use of it can become a pretty big handicap. Don't get me wrong though, I am not saying this rom is dead. If nothing else, it can be a great base for others to build from, and I am not calling it abandoned just yet. (just temporarily unsupported). Its a big IF, but IF I can get a replacement S3, then i will just pick up where I left off.

I should know pretty quickly what I will be able to do, and Ill update you when I do. Hopefully things will turn out good and be resolved quickly!

I shudder at the thought, but I just hope Im not forced to dig up one of my old flip phones for a while! Lol!

For now though, I want to thank everyone for your help and support! It certainly has been fun! Now lets just hope I can return with good news!

Doc
[T-Mobile, Samsung Galaxy SIII] nataku199:
You might be alright getting a replacement. I've sent back bricked phones without any problems. Twice actually, My 1st GS and a GS3.
[T-Mobile, Samsung Galaxy SIII] revwillie:
I came from wicked as well. But all I did was backup, wipe cache and data, flash deodexed, flash modem, reboot.
[T-Mobile, Samsung Galaxy SIII] allendj81:
sidekick is leaving and now you are slowly going away... at this pace, our device is gonna be left out somewhere in a shelf collecting dust :( I hope you come back
[T-Mobile, Samsung Galaxy SIII] anil2653:
It is very bad news for T-999 users :crying:

We hope and pray for you to get a replacement of your device

otherwise we all will be missing your big contributions.....
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
Sob! 10chars:crying:
[T-Mobile, Samsung Galaxy SIII] calexchelse:
This is indeed sad news. Will be hoping for a quick return
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
I have an HTC touch pro 2 I can send to you Doc. ...it beats the crap out of a flip phone. .

:beer:

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] 4Orr:
Oh no! I hope you find a way to get your GS3 replaced, Doc. It would be a huge loss to everyone in this forum if we lose you.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thanks Guys! I do appreciate the compliments and kind words! And the device offer Tower! I have an old MyTouch 3G Slide, so I wont have to resort to the old flip phone! Still, after the S3, it doesn't seem like much of an improvement over the flippers! I do very much appreciate your offering your old device for me though! Especially when its not even something I could use to really benefit the forum here! For now, I prefer you hang on to your own device though, but Thank You!!! (now, if someone wants to give away an S3....! J/K!!!)

I was asked in another thread how I bricked it, and it happens to be directly related to the leak, so I figured I would post it here and just link to it. Basically, as many of you may know, we are using the AT&T kernel for these Roms. This is because with the kernels that were included with the T-Mobile builds result in broken WiFi. After a LOT of investigating and questioning people who know more than I, I have come to suspect that the two modules which are needed for WiFi (cfg80211.ko and wlan.ko) are actually built into another part of the firmware and symlinked to the modules folder, most likely from the bootloader. (this is new to 4.3 btw, if I am right).

As it turns out, I have everything included in the firmware releases, except aboot (bootloader). So I figured I would at least check the other parts, just in case. So one at a time I planned to flash each part of the firmware, testing along the way. Started with sbl2, which did not help, but everything still functioned as expected. So I rebooted again and next flashed sbl3. Again, I rebooted into the system but it did not seem to help nor harm anything. Onto flashing RPM. I reboot recovery......nothing. Dead...Bricked....Hard!

I figured that it being the sbl3 flash that caused the brick, KAsp3rd's debrick method would work without a doubt! (one of the reasons I took the risk!) The debrick image includes the sbl2 and sbl3, and both would be flashed back to MD5 when I got into download mode. Boy was I wrong! There is simply no change at all. I spent several hours on it, trying to create the debrick SD with different block sizes, 2 sd cards, and different ways of formatting the sd. None worked... I am quite confused as to why it didnt, but in the end, it just didn't and I am still bricked.

So now I get to decide, pay the $150 deductible and get a replacement, upgrade to the S4 for $99 + payments, or upgrade the the Note3 + payments. What I would love to do and what was my original plan was to keep the S3 and upgrade to the Note3. I'd still like to avoid giving up the S3, but I dont even think Ill be able to afford any of the above options on their own anyway right now. So once I can come up with the money, I may have little choice but to just go with the upgrade. I haven't decided just yet though. But I will let everyone know what is happening once I know myself!

So thats where I am at now. I know its more of an explanation than what was asked, but I figured I just put it all out there for those who might want to know the little details!

Thanks again guys!

:cowboy:
[T-Mobile, Samsung Galaxy SIII] 4Orr:
Can you rescue your SG3 by using one of the many JTAG services? It might be a cheaper alternative.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
probably could, but considering the screen has been horribly cracked for a while now (pieces started falling out at the corners!), the glass over the camera is cracked, and id likely need a new battery soon, im not sure the cost in repairs would be worthwhile.

plus, not having been able to wipe my personal data from tge internal sd, makes me reluctant to send it anywhere. some of the data IS sensitve, and i cant trust anyone to fix it and not browse around, or worse, copy the whole thing to look at later.

ive busted others in the past doing that to someones data, and cant believe that some stranger in another state could resist the temptation. im sure itd probably be ok, but is just not a risk i can take with it.
[T-Mobile, Samsung Galaxy SIII] nataku199:
I had almost no problems flashing this but I lost all my titanium backups. Is there a way to pull the app data from the nandroid backup? I remember soft bricking my phone the last time I tried that. If not, would a nandroid restore set it right back to the way it was before the flash?
[T-Mobile, Samsung Galaxy SIII] tp2215:
Here is a just a suggestion, if you still under a plan from T-mobile, just call them up and play it stupid. Act as if you have no idea what happened to the phone and chances are they will just send you a new one and ask to send them back the old one no questions ask. They usually walk you through some basic (stupid) simple tasks like restarting etc. and then send a replacement overnight. I have done that a couple of times now even through my phone was rooted, heavily modified and running custom roms and never heard a single thing back from them nor ever seen anything on my bill. In my oppinion I dont even thing they look at them when they receive them. Just a suggestion.
[T-Mobile, Samsung Galaxy SIII] scifan:
Oh, ouch... do you know what happened?

---------- Post added at 08:24 AM ---------- Previous post was at 08:20 AM ----------

You should be able to restore your nandroid and then use TiB to backup your data again... make sure it's going to your external SD card instead of to internal storage...
[T-Mobile, Samsung Galaxy SIII] chrisokaly:
Problems rebooting

Since flashing this update I have problems with the reboot function... when I choose 'reboot' all it does is hang at the GS3 splash screen...

I have tried:

1. Format data (internal)

2. Odin to stock, reroot via Kies, flash recovery, reinstall

3. Set up phone again, reboot, and same thing.

I've noticed a few things... it doesnt only happen on this update. Also happens if I do the same above process and flash a AOSP 4.3 update. Very annoying. The only thing I can think of is I am also using TWRP 2.6.3.0 (I think I had been on 2.6.1.0 previously. Has anyone had this happen to them?
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Put up a PayPal doc and I'll help. Pay the 150 and get the t999L as I did. The only drawback is it'll probably be a stupid white one like I have.

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] revwillie:
I think nandroid manager can do that. It's in the play store.

Sorry to hear about your s3, doc. But thanks for doing as much as you did with your aging phone. I still find it funny how powerful these phones are once the software catches up to the hardware.
[T-Mobile, Samsung Galaxy SIII] nataku199:
Yeah, that's where I screwed up. I'm just worried that restoring back to a 4.1.1 rom is going too brick it.
[T-Mobile, Samsung Galaxy SIII] scifan:
Try booting into recovery and wipe the dalvik cache.
[T-Mobile, Samsung Galaxy SIII] anil2653:
I have taken backup of leak2 and Dan's 4.3.1 through Rom Manager and restored also and everything is working perfectly no issues

So I am sure it is not issue with 4.3 but may be twrp or something else
[T-Mobile, Samsung Galaxy SIII] Coug76:
That might work if his screen wasn't smashed. Warranty won't cover devices with damage.

Hastily spouted for your befuddlement
[T-Mobile, Samsung Galaxy SIII] tp2215:
Yea, i didn't read that the screen was smashed. It should work if there is no physical damage such as the screen smashed or if the white moisture sticker on the back panel and the battery isn't pink (That indicates to them that the phone was dropped in water). But if it is hard bricked then it would probably work.
[T-Mobile, Samsung Galaxy SIII] roly17:
So Doc, are we ok running this? As long as we are not flashing firmware as you were doing there should be no problems, right?

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
It is probably still there. Just is hard to find and not being read due to the /0 profile folders issue. Using a root capable browser, go to either /data/media, or /storage/sdcard0 and you will find everything there. You basically need to move everything to /data/media/0.

If you want to verify, just go into TiB preferences and where you choose your backup folder, click detect, and it will find the correct folder.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Unfortunately, mine is well out of warranty. Besides, as stated, it has pretty bad physical damage as well.

Yup, bricked while trying to get the MJC kernel working so I could use it with this build as intended. (I posted a few back with all the details).

Im a little confused. Once you have Odin flashed the latest firmware, you dont need to do that again each time. And why are you rerooting with Kies? Since you have already Odin flashed the firmware, just follow these steps and you should be fine.

Factory Reset

Flash MJC (or MJ4) Modem (only if you havent already, no need to do it again if your baseband is already one of these)

Flash MJC deodexed Rom

Reboot System
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yes, you can flash the Roms in the op and whatever else here that has been posted. I have never released the rest of the firmware because I did not want to ask anyone else to test without knowing more about it. And now that I know more about it, I won't be releasing it! Lol!

Anytime you go backwards to an older version, you will most likely have to factory reset or it will hang at boot. Should be little to no danger in flashing back to an older version though.

Already got one on my profile, but I will never ask for anything. Its just not the reason I do what I do around here. I do appreciate the gesture man! Thank You and everyone else who has posted in response! Never quite expected so much!
[T-Mobile, Samsung Galaxy SIII] nsxalwayz:
i've been going back and forth between 4.3 TW, 4.3 AOSP, and 4.1.2 TW without any problems. (knocks on wood)
[T-Mobile, Samsung Galaxy SIII] John_Minfuse:
Will this work on the Sprint S3?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Highly doubt it. Even if the rom works, you wont be able to get any data connection because you can't flash our modems.
[T-Mobile, Samsung Galaxy SIII] allendj81:
I would like to inform you guys that tonight I bought the Gear and had successfully pair it with my GS3. Fyi, I'm running full deodexed knox free with no bloat removed. It connected with no problems and its working flawlessly. Tested it to make calls and to sent text using S voice, its all smooth :good::good::victory:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
i dont want this thread to continue to be about my new paperweight, but i do want to try one last thing to revive it.

please check my post linked below and consider helping me out with it.

thanks!

http://xdaforums.com/showthread.php?p=47531023
[T-Mobile, Samsung Galaxy SIII] 4Orr:
I have a debrick.zip file from the LJC bootloader for you, Doc. Would you like me to upload it to my G Drive and share it with you?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
OP2 & OP5 updated

Added some info on some reported issues.

Added the rom I was personally using in case anyone is interested.
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
Thanks on that note, I wasn't entirely sure what was going on between carrier and international versions of the the 4.3 update.
[T-Mobile, Samsung Galaxy SIII] ThC23:
Emt/shell/emulated/titanium

Copy or move and paste to the external SD or SD.

Powered by the SGSIII

Powered by the SGSIII
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
just tried and still no good....will try again slightly differently, but if anyone is on ANY different firmware and is willing to create the debrick img fike for me to try, i would be most thankful!

Thanks [MENTION=4461541]4Orr[/MENTION] for taking the time to help!

theres got to be a reason it wont work for me....hate it when i cant figure something like this out!
[T-Mobile, Samsung Galaxy SIII] razielpr:
I'm having extremely bad battery
[T-Mobile, Samsung Galaxy SIII] scifan:
Whoa... use bbs and see what's keeping it awake... and is consuming battery.

Yesterday I ran a good 12 hours and didn't really start killing my battery until I started playing games later in the day...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
also, screen on time and the larger graph can help too. but it looks like you probably had tge screen on the whole tine, (brightness?), plus games like strike team are not gonna be gentle on battery.

i had run candy crush, literally for about 10 min at one point and it caused about a 20-30% drop!

heres the thing ive boticed on mine, if there is no heavy draw going on, itd last quite a while, but the rate of drain increased significantly as power required increased. as the battery gets older and closer to eol, this gets worse. so a small increase in the draw from the battery may net a much larger decrease in the available charge than you normally would expect. this is why even though at idle and gentle use i got good results, but i still made mention that i would need to replace my battery soon. as soon as i play a game, or use a battery or cpu/gpu hungry app, my available charge would drop, fast!

looking at your graph it appears to be a steady drain, so im curious as to your screen on time/brightness level, game time, etc. im guessing you were playing the majority of the time it was on? mid to high bright?

basically this is guesswork, because theres not enough info. but it does look similar to some things i saw on mine.
[T-Mobile, Samsung Galaxy SIII] scifan:
I know I'm using a fair amount of screen time this morning... but my battery isn't discharging at that rate...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
OP5 Updated!

Added a couple of mods to Post 5. One adds all languages, the other contains a number of tweaks to the CSC feature.xml file. Please note these have not been fully tested since I wound up bricking my phone. But since they are all rather safe to try, i figured I would go ahead and post them.

These CSC tweaks/mods can be found all over XDA. Some I discovered on my own. For these reasons, I did not give credit to any one in particular. There is just no way I can go back and discover who made the original finds. In case you want to use some of the included tweaks, but not all, click below for a list of what I have changed. I did give evil1art credit for finding a new one I had not yet seen, adding quick panel toggles.

Edit: To apply, just find the existing line and change the value, or add the line and reboot.

Show Time text was sent, not received.

server

Allow send mms to email address

true

Change colors of days of the week in calendar. Sunday R=Red

XXXXXXR

Add Call button to logs list

false

Show Total Call Time

true

Disable Software Update under About Phone

false

Add/Change Quick Panel Toggles

Wifi;MobileData;Location;AutoRotate;SilentMode;SmartStay;AirplaneMode;WiFiHotspot;PowerSaving;SmartPause;AirGesture;DrivingMode;DormantMode;BlockMode;AllShareCast;MultiWindow;Bluetooth;SBeam;Nfc;AirView;Sync;SmartScroll;AssistiveLight

NOTE: These are copied from the S4 forums by evil1art. Not all will probably be available for our phone. Also, I added the AssistiveLight, hoping to get the flashlight toggle. Not sure if it will work or not.

Set Browser Homepage

http://www.google.com

Allow delete all bookmarks

true

Edit and delete bookmarks

true

UA in settings

true

Enable UA Profile menu

true

Enable "Exit Browser" option in menu

true

Enable Exit Prompt on browser

true

Change number of allowed Tabs in Broswer (Change 12 to preferred number) set to 24

12

black background on email

false

Show GPS Menu in Camera

true

Allow to continue playing music while using camera

true

Enable NFC during call

false

Change number of pages on Launcher (set to 3)

3

Disable Caller IQ Broadcast

false

Deleted

pcweb.tmobile.com
[T-Mobile, Samsung Galaxy SIII] Knumb:
My battery is pretty decent. It's only been 1 day...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you have updated your SuperSU, either with the flashable zip, or via the Play Store, and are having problems where you lose root access for some/all apps, try this:

Open /system/etc/init.d/99SuperSUDaemon in a text editor.

Delete the "auto" so the line should look like this:

/system/xbin/daemonsu --daemon &

Save and reboot.

I can't remember for sure, but I believe it was loserskater who discovered this, so props to him! (might have been someone else in his thread)
[T-Mobile, Samsung Galaxy SIII] shinkien:
First off, this is awesome. Running the deodexed stock and this thing is smooth so far. Gps is snappy and so is data. The only thing I'm having a problem with is receiving mms from emails or third party apps like textnow. I was able to get them in 4.12, but not even a blip here. Anyone know if its a setting that needs to be enabled or if its an apn issue? I've some of the apn's that I found online but not getting any results yet.
[T-Mobile, Samsung Galaxy SIII] scifan:
So, while this isn't 20 hours of run time, I have just over 4 hours of screen time with fairly heavy use...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
notice the csc tweaks i posted a few back. there is another in the feature.xml file that allows receiving of emails im pretty sure. look for it and change the value, save, reboot and test.

if you cant find it let me know.
[T-Mobile, Samsung Galaxy SIII] nayoung802:
Do none of the exposed framework stuff work on this ROM? And can I replace the stock messaging with an aosp messaging app?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
some xposed modules have been reported working, some have caused issues for others. no idea about msg app. you could always just try it out and let us know.
[T-Mobile, Samsung Galaxy SIII] jonk26.2:
I have 2 spare motherboards...one i just posted on ebay that has a bad imei but everything else works...the other has a good imei but the microphone and accelerometer don't work...let me know if you would like me to loan you one....or both.
[T-Mobile, Samsung Galaxy SIII] :
The csc mod didn't work for me
[T-Mobile, Samsung Galaxy SIII] shinkien:
I tried changing the values in these lines:

<CscFeature_Contact_SupportMMS>true</CscFeature_Contact_SupportMMS>

<CscFeature_Contact_SendEmailViaMMS>true</CscFeature_Contact_SendEmailViaMMS>

and tried adding this line at the end of the "contact" set:

<CscFeature_Contact_RecieveEmailViaMMS>true</CscFeature_Contact_RecieveEmailViaMMS>

No luck tho. Is there another one that I'm missing? Thanks for any help Doc.
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
Got my fingers crossed for this guy, lol! Not knowing if Wallet 'Tap and Pay' will work is the only thing holding me back.
[T-Mobile, Samsung Galaxy SIII] Rev10eight:
Thanks Doc, gonna give the deodexed a spin.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thanks man! I answered in the debrick thread though, so dont figure I need to repost here.

None of the included mods worked?? Are you certain it flashed? Try unzipping the file and just manually copy the feature.xml to /system/csc/ and reset the permissions to what they are for the other files in that folder. Then reboot. There are quite a few mods included, and while I don't expect them all to work, some absolutely should. Such as the increased number of allowed tabs in the browser.

If quick panel extensions are not working, I probably know why and can tell you how to fix if you are up for it.

I may have been mistaken. This looks like the one I was thinking of:

<CscFeature_Contact_EnableOptionToSelectEmailMMS4EmailAddress>true</CscFeature_Contact_EnableOptionToSelectEmailMMS4EmailAddress>

Sorry about that. When I think about it though, it does seem like it might not be a good idea to enable receiving email via sms/mms! Doubt itd be able to handle 95% of what you actually receive, such as html encoded messages, lots of links, and would likely take dozens of "texts" to encompass all of the characters!
[T-Mobile, Samsung Galaxy SIII] allendj81:
Have any of you guys try to use the allshare cast dongle?? Mine connects by I get no image on my tv. It stays on the black screen that says "connecting..." but it never does show an images or sound. The hub its on LJ02 version.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I do know for sure is someone else was able to use the MHL adapter to connect to their TV.

But when we got 4.1.2, we found that AllShare Cast did not work if you were rooted due to drm restrictions. Also if your system status showed as "modified", it would not work. I'd imagine its the same in this build, and is likely even more restrictive than before.