Develop Bugs

something went wrong

I updated to the EL30 modem and my data slowed down quite a bit so i used heimdall and went back to eh17 then flashed back cleanGB mtd. now my phone gets stuck at a black screen any time i reboot after flashing a theme. i have tried several roms mtd and bml and i can no longer flash themes. i dont know what could have happened?

Are you on MTD now? If so you have to mount system in CWM just before flashing.
Sent from my SPH-D700 using XDA App

i did. i also tried it on a bml rom.I then tried to integrate the theme into a rom with no luck( i have done this hundreds of times.). i just get stuck on the samsung screen

jpond83 said:
i did. i also tried it on a bml rom.I then tried to integrate the theme into a rom with no luck( i have done this hundreds of times.). i just get stuck on the samsung screen
Click to expand...
Click to collapse
This happened to me at one time andd the only thing that fixed it was odining back to stock and starting over... either your cwm got corrupted or the mtd partition did...
Sent from my SPH-D700 using Tapatalk

i have used heimdall to go back to stock several times and it didnt help. would odin make a difference? I dont like to use odin.

flastnoles11 said:
This happened to me at one time andd the only thing that fixed it was odining back to stock and starting over... either your cwm got corrupted or the mtd partition did...
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I'd say that CWM got corrupted...I've had to go thru that at least 3-5 times. Yep, you gonna have to Odin back to stock EC05 and start over. EL30 has been running pretty good for me...running stock deodexed with EL30 modem. I had tried using just the modem on EI22 Roms with little luck.

i would use el30 but i cant stand the green when the screen turns off.

try this....
boot into recovery, go into mounts and storage, format EVERYTHING besides boot. Format Data, Cache, SD card, System. Then install your rom, and boot up. Once it boots up, turn your device off. boot into recovery, wipe dalvik and cache, mount system (do this ONLY if you are installing a BML theme on your MTD rom), install theme, umount system, reboot.

Help! Phone Not Working Anymore :(

I flashed back to stock first, then I installed CMW, then SU.apk,
then i flashed full wipe by darkside (?) from dev forum.
then when i went to install from the SD card for juggernaut rom, it gives me error ever since.. it says (bad)
my computer can't read my phone anymore,
phone stops at the booting screen,
factory reset isn't helping either...
any suggestions? anyone?

ILLHYHL said:
I flashed back to stock first, then I installed CMW, then SU.apk,
then i flashed full wipe by darkside (?) from dev forum.
then when i went to install from the SD card for juggernaut rom, it gives me error ever since.. it says (bad)
my computer can't read my phone anymore,
phone stops at the booting screen,
factory reset isn't helping either...
any suggestions? anyone?
Click to expand...
Click to collapse
When you are in recovery go to mounts and then mount usb storage. Then connect your phone to your pc. Try downloading another rom and transferring it over. (this would require an external sdcard)

Can you get in to download mode? If so just use the stock Oden and go back to stock. Then flash clockwork mod recovery via Odin, flash whatever rom you want to use. For what it's worth I am very happy with macnut
Sent from my SGH-T989 using xda premium

If you can get into recovery I would suggest reflashing whatever rom it is you want, i usually format everything except /sdcard whenever I flash a new rom to ensure theres nothing leftover (some might argue this but its never served me wrong), then follow the instructions the OP posted in the rom you want to flash. It sounds like a bad flash to me anyway.

ILLHYHL said:
I flashed back to stock first, then I installed CMW, then SU.apk,
then i flashed full wipe by darkside (?) from dev forum.
then when i went to install from the SD card for juggernaut rom, it gives me error ever since.. it says (bad)
my computer can't read my phone anymore,
phone stops at the booting screen,
factory reset isn't helping either...
any suggestions? anyone?
Click to expand...
Click to collapse
As suggested above, try download mode (holding volume up and down while plugging in USB) and flashing through Odin. As to what's giving you the error, it could be a bad download (always check MD5 sums once its on your phone!), or if it was giving an MD5 sum mismatch then that usually is a result of renaming the file on your phone. Anything that you flash cannot have any spaces in it, otherwise it won't read. That goes for nandroid backups as well.

[Q] Can't ODIN or flash, saying Unable to mount items

I tried billard412's Sprint ROM restore to stock and something went haywire.. It rebooted and then it would just boot loop. Ok I thought I'll just Odin back .. but everytime I tried any TAR to Odin it would just stop at cache.img.. I am able to get into TWRP and when I tried a restore, it restored fine, but then it would say
E: Unable to mount /efs
E: Unable to mount /preload
E: Unable to mount /carrier
I've tried various operations, megawipes and such and it would still give me that error on my Sprint Galaxy Note 2 at the end.
Can anyone help me please?

This is scary! I was about to use that so I could do the full ma7 update but now I'm not so sure.
Maybe you should ask billard for ideas since he knows what actions his zip takes and *should* have clues about what parts could go wrong.
Sent from my SPH-L900 using xda premium

KEYofR said:
This is scary! I was about to use that so I could do the full ma7 update but now I'm not so sure.
Maybe you should ask billard for ideas since he knows what actions his zip takes and *should* have clues about what parts could go wrong.
Sent from my SPH-L900 using xda premium
Click to expand...
Click to collapse
I think if I had backed up my EFS folder I might be OK, but alas. I didn't .. This is my first Samsung phone, coming from HTC.... I asked in his thread but it's probably one of those one in a million chance type of things that happened to me

well if that didnt work i just had the same issue
due to upgrading to stock MA7 and flashing an LK8 rom with an MA7 stock kernal
i had to odin twrp recovery and run the restore zip from there since i cant mount preload
also if the zip dont work load a custom rom then go back to recover and try it then you should be able to odin again
*also when i went back to stock LJC i went to manual recovery and cleared cache and dalvik because when i did a factory reset E: failed again*

Tha_Dynasty2049 said:
well if that didnt work i just had the same issue
due to upgrading to stock MA7 and flashing an LK8 rom with an MA7 stock kernal
i had to odin twrp recovery and run the restore zip from there since i cant mount preload
also if the zip dont work load a custom rom then go back to recover and try it then you should be able to odin again
*also when i went back to stock LJC i went to manual recovery and cleared cache and dalvik because when i did a factory reset E: failed again*
Click to expand...
Click to collapse
billard was able to point me into the direction of a PIT that I used to re-partition the phone.. Now I just have the mouning /efs problem, which if I read correctly, I should have backed up.. that's where I am now. I was able to go back to stock but it boot loops and when I go into recovery I have the unable to mount ./efs error

jyan_osu said:
billard was able to point me into the direction of a PIT that I used to re-partition the phone.. Now I just have the mouning /efs problem, which if I read correctly, I should have backed up.. that's where I am now. I was able to go back to stock but it boot loops and when I go into recovery I have the unable to mount ./efs error
Click to expand...
Click to collapse
wow so the repartition didnt work?
i mean like i said you can try after doing stock you
can reboot go in to stock recoevery and clear things they may help
and also when loopinng i used twrp 2.4.0.1 i think thats the newest 1

Tha_Dynasty2049 said:
wow so the repartition didnt work?
i mean like i said you can try after doing stock you
can reboot go in to stock recoevery and clear things they may help
and also when loopinng i used twrp 2.4.0.1 i think thats the newest 1
Click to expand...
Click to collapse
Yea using the newest TWRP.. cleared everything.. tried multiple roms both rooted and stock.. i think it's a lost cause

jyan_osu said:
Yea using the newest TWRP.. cleared everything.. tried multiple roms both rooted and stock.. i think it's a lost cause
Click to expand...
Click to collapse
i dont think so i swear
i got same issue it even told me to connect to kies due to odin not working nor the restore for 1 click
you have to make sure when you went to recoevry and flashed the stock ljc
http://forum.xda-developers.com/showthread.php?t=2086769
it will take you back to stock period when your phone boots
you will have to shut it down and then go to recoveryt which it will be stock and then
wipe factory 2 times and then cache 2 times and that should repartition your phone
reboot it and then use a stock tar and then repartition you should be good to go and you even have 0 reset counts with stock LJC

[Q] Cannot flash anything

T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.

moebawlz said:
T989 without any SD card in it, the one I had died apparently new one on order. Went to flash the latest PA rom but kept getting error 7 using CWM. I updated my recovery to the latest TWRP and still will not flash. I tried updating to the newest radio UVMC6, but that wont flash. I am currently on CM10.1 nightly. My process for flashing is recovery, superwipe, flash, which is when the flash errors out and I re wipe and then I can flash my CM10 back on. So I can flash CM10 all day long but nothing else. I searched on here and found that the ATT version of this phone has this problem and you have to flash an AOKP and then flash whatever you want, other phones with similar problems say use ODIN and flash stock and then go from there. I am just looking for any advice on this situation. I could not find anything specific enough in my search to help me and I am hoping someone here can. Thanks in advance.
Note: I have also tried flashing CM10.1 RC5 and has the same problems.
Click to expand...
Click to collapse
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium

soupysoup said:
For onw those superwipe scripts are not needed with twrp, u might be getting the error from that, are u trying to flash from internal SD card since ur external died? That might cause it but I don't think so, I would suggest trying a manual wipe of all partitions, data, system, cache, dalvik, 2x , then flash, if that doesn't work try using Odin, go back to stock and start over, that should fix it definetly
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.

moebawlz said:
Thank you... I wasnt sure about superwipe on TWRP since I just put it on and came from CWM. I am trying to flash from the internal card and the new external card will be at my doorstep tomorrow so I will drop that in as well. I will drop back in once I get all this done and hopefully all goes well.
Again thanks.
Click to expand...
Click to collapse
Good glad I can help, let me know how it all goes, now I'm interested lol
Sent from my SAMSUNG-SGH-T989 using xda premium

Ok so I got my new SD card. Tossed that in, just figured I would try flashing from the external, no luck there. Same issues.
Odin back to stock using this tutorial http://forum.xda-developers.com/showthread.php?t=1513359&page=3
Used http://forum.xda-developers.com/showthread.php?t=2195283 this to regain root.
Got CWM back on but now I cannot flash SuperUser
When I go to flash Superuser it says
Mounting System
Deleting System:bin/su...
Deleting System:xbin/su
Extracting files to SYSTEM
Setting SYSTEM:bin/su permissions to 06755...
Creating SYSTEM:xbin/su symbolic link...
E: Error in /emmc/Superuser-3.0.7-efghi-signed.zip
(Status 0)
Installation aborted
So on the plus side I didn't brick the phone... downside now I am back to Gingerbread and currently stuck here...
Possibly a bad zip file?
Any ideas on this?

Quick update... I am a moron... Did not realize that root is kept with this restore... Got Superuser from market and am good to go.
Installing TWRP now and will have an update on the flash soon.

OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place

moebawlz said:
OK... the fun seems to have just begun
I cannot install TWRP from GooManager. No clue why, looking on here and I found //techerrata.com/browse/twrp2/hercules (cant link too new of a member)
So as it seems I can download the .img and GooManager should see it and if that doesnt happen I can install it through the terminal with these commands
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
OR flash it with ODIN... Which I would assume I get the .tar file and follow the same process as putting the recovery files in?
Aside from TWRP being an issue, I tried installing the PA rom with CWM and I got this:
Installing update
set_perm:some changes failed
E:Error in /sdcard/pa_hercule...zip
(Status 7)
Installation aborted
The same error I had in the first place
Click to expand...
Click to collapse
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.

meekrawb said:
I'm not sure what your overall problem is, but if you are going to install TWRP do not use Goo Manager or the img file. They have been messing up peoples phones. Odin the tar or try the zip from the TWRP thread.
Click to expand...
Click to collapse
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...

moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Click to expand...
Click to collapse
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.

i went to flash with goo last night and it bricked the phone kind of, i had to ODIN and reflash the CWM again and bam the phone rebooted no problem

meekrawb said:
If you can boot into TWRP, then they must have fixed the Goo problem.
It seems like you have tried most everything. Maybe you should Odin back to stock. If you are comfortable doing it, that is.
Click to expand...
Click to collapse
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?

Lucky for me I kept a backup saved on my PC from before I did anything here. So I am back to the CM 10.1 Nightly I started on for the time being.
Is there any other method of flashing a rom that I might be able to try?

moebawlz said:
I did Odin back to stock before. I am still on stock gingerbread right now with root access and am getting the errors I have been. I followed the tutorials in the sticky thread that I posted before that got me back to stock.
Within TWRP I tried installing the newest Cyanogen Mod and got
E:Error executing updater binary in zip
Error flashing zip
When I try installing the PA rom I get the same error
Any thoughts? Would going back to stock through Odin and doing this again potentially fix it? or is that a shot in the dark?
Click to expand...
Click to collapse
It would be a shot in the dark. I did a Google search for your error and a couple of people said they were able to fix it by using TWRP 2.3. That was for different phones though. Maybe try that before going stock.

I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3? I also found this
http://forum.xda-developers.com/showthread.php?t=1639673
or
http://forum.xda-developers.com/showthread.php?t=1658418

Just a thought here... I keep gettin emmc errors... I was reading about upgrading and downgrading TWRP through the Terminal Emulator and it said use emmc or sdcard depending on what the phone reads it as.
When I first got the phone i recall seeing emmc when i would go into any file browser. Now it just says sdcard0 (internal) & sdcard1 (external)
So how can I get recovery to stop looking for emmc and start looking for sdcard0?
Unless I am way off in left field here with this.

moebawlz said:
I am by no means a pro at this and am still learning as I go. Just to make sure of what I am doing, can I Odin TWRP 2.3?
Click to expand...
Click to collapse
Yes, use Odin and the 2.3.3.0 tar from the techerrata website. I like using the Odin method because I have never had a problem upgrading recovery that way. I don't know about the emmc errors because I have only used the dd method like twice.
Edit: Maybe your internal memory is corrupted? I'm not sure how to test for that though.

moebawlz said:
Well that could be a problem... I just got GooManager to do what I wanted it to do before I saw this message. If I overwrite it with the tar will that be ok or am I better off starting this process over and Odin back to factory stock again?
Along with that after I got TWRP working through Goo Manager again I tried flashing PA again and I had the same error as I did in the first place.
Maybe my phone just hates anything but the nightly I had before...
Click to expand...
Click to collapse
I think u must be getting bad DL then because none of that sounds right lol, if u got twrp to load into your device and all is working fine then the only other option is a bad DL, try checking the DL with a root browser or something to see the size of the file, status 7 errors are from the zip, usually bad install script in the ROM, which could be caused by a bad DL, check the DL size and let me know
Sent from my SGH-T989 using xda premium

went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?

moebawlz said:
went back to 2.3.3 and still having the same error.
Is there a way to correct any possible errors in my internal memory?
Click to expand...
Click to collapse
If the DL is good, I don't know what else to tell u that is very strange indeed, but interesting too, I've never not been able to install at all, I'm curious..
Sent from my SGH-T989 using xda premium

[Q] phone installs PA3.96a fine but gets stuck upon rebooting

I installed paranoidandroid 3.96a today and I had some errors before I was able to install it so I ended up formatting the data and then clearing the caches.
I flashed PA. Then I flashed the latest google apps. Then I flashed PA again and rebooted. My phone loaded fine and I was able to install everything I want.
Then if I reboot my phone it get stuck on the splash screen and cannot load. If I go into TWRP 2.5.0.0 recovery it asks me for a password (I have not yet a password although I recently bought this phone used on swappa so I've contacted the seller to ask if he set a password). If I push cancel at the password screen then I can get into TWRP but if I go to wipe the dalvik cache it say sit "failed." The test printed to the console is:
Updating partition details...
E: Failed to wipe dalvik
Updating partition details...
I also cannot browse the internal memory of my phone. There is no folder named "android" or similar.
Any thoughts would be greatly appreciated. I'm going to try to update TWRP to the latest version. After that I'm out of ideas

Try the latest twrp like you said. Then you can also try cwm. Before you csn browse your file system in recovery, you have to mount system.
Id try another factory reset and reboot though. If thst doesnt help try another kernel. If youre still stuck, idin flash back to full stock with the root66 firmware, then start over clean from there.
Sent from my SGH-T999 using xda premium

how long do you let the phone sit after rebooting? I'm currently on the same rom and noticed it takes longer than usual to reboot the device. it's seems like it takes just as long to reboot the phone as it does to boot up the phone right after flashing the rom.
try letting the phone sit for 5-10 mins and see if it boots up. it's kind of ridiculous it takes that long to reboot a phone, but then again the rom is in alpha. I might try reflashing the rom to see if this still happens.
Just posted in the ROM thread to see if anyone else has the same issue.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Try the latest twrp like you said. Then you can also try cwm. Before you csn browse your file system in recovery, you have to mount system.
Id try another factory reset and reboot though. If thst doesnt help try another kernel. If youre still stuck, idin flash back to full stock with the root66 firmware, then start over clean from there.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I tried installing PA again and then upgrading TWRP to 2.6.0.0 but it still said that it had 2.5.0.0. Then I installed CM10.1 and used that to upgrade to TWRP 2.6.0.0 which worked. I then tried installing PA3.96a again with the same results.
I think that the problem is with TWRP not recognizing android 4.3 installs correctly because I have the same problem with CM10.2 that I had with PA3.96a.
I don't think the problem is that I'm not waiting long enough because after the first restart (i.e. I flash it and restart loading the ROM fine--then when I restart it for the first time it gets stuck). When I go into TWRP after it hangs the first thing it does is ask me for my password. I don't have a password. I think that something is happening to the system partition after install that makes TWRP unable to read it on this phone. Also it says that 0 MB have been used on my phone ram so I think the problem is with TWRP not being able to read the system partition in 4.3 correctly.
Has anyone gotten android 4.3 working on the t-mobile s3 yet?
Edit: And I can't restore from a nandroid backup (unless I put it on my SD card because the phone cannot read from the system partition).

Did you try mounting /system in recovery?
I would seriously consider Odin flashing stock root66 firmware before anything else at this point. Maybe something is corrupted in one of the underlying partitions.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Did you try mounting /system in recovery?
I would seriously consider Odin flashing stock root66 firmware before anything else at this point. Maybe something is corrupted in one of the underlying partitions.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Yes I did. If I mount it I still couldn't see /android or any other folders. I could also not clear the dalvik cache or do a factory reset.
Okay that's the consensus. I'll try restoring to stock sometime this weekend and see how that goes.

I just reverted back to stock using Odin. Reset the counter to be safe and then used odin to load a rooted stock. Then I installed goo manager and had it install TWRP 2.6.0.0.
Success! I can install and 4.3. Something must have been funky with the previous rooting job or something. Who knows. Thanks!

Right on! Good to hear you got it running good!
Sent from my SGH-T999 using xda premium

same thing
so i basically have the same thing but with mine i installed hyperdrive rom and flashing the stock rom like you said doesnt work and doesnt get rid of hyperdrive so it just has the hyperdrive boot screen and i cant get to my internal memory ect. like him please help i cant have ruined my phone by the way im a noob so please be specific and give me links thanks

Did you install stock with Odin?
I installed stock with Odin. I then installed a rooted stock and used that to reroot my phone by installing goo manager to install twrp 2.6.0.0.
Let me know if you want me to get the links for you. I got them on xda from googling
Edit: Found it. I used this http://forum.xda-developers.com/showthread.php?t=1900345.
Downloading the stock took about an hour so I would go ahead and just use odin to install the rooted stock. After you install your phone will reboot and then it will hang on a screen with Samsung on it (or at least it did for me). You then restart your phone and go into recovery and do a factory reset. Then install goo manager and reinstall the recovery by clicking on the options/settings button and selecting "Install OpenRecoveryScript." Then you can download whatever ROM you want to install. Reboot and go into recovery and you can install it.
Sent from my SGH-T999 using xda app-developers app

links please
bmdubs said:
Did you install stock with Odin?
I installed stock with Odin. I then installed a rooted stock and used that to reroot my phone by installing goo manager to install twrp 2.6.0.0.
Let me know if you want me to get the links for you. I got them on xda from googling
Edit: Found it. I used this http://forum.xda-developers.com/showthread.php?t=1900345.
Downloading the stock took about an hour so I would go ahead and just use odin to install the rooted stock. After you install your phone will reboot and then it will hang on a screen with Samsung on it (or at least it did for me). You then restart your phone and go into recovery and do a factory reset. Then install goo manager and reinstall the recovery by clicking on the options/settings button and selecting "Install OpenRecoveryScript." Then you can download whatever ROM you want to install. Reboot and go into recovery and you can install it.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
that would be awesome if you could i want to make sure i do the same downloads as you its so nice knowing im not the only one. im so screwed if i cant fix this

imfukked said:
that would be awesome if you could i want to make sure i do the same downloads as you its so nice knowing im not the only one. im so screwed if i cant fix this
Click to expand...
Click to collapse
Check your flash counter and if it's anything over 0 run Triangle Away to set it back to 0.
Then follow the directions in the stickied thread for directions on how to revert back to stock. I installed the latest t-mobile ROM from this thread http://forum.xda-developers.com/showthread.php?t=1771687
Just make sure you get the T-mobile versions

bmdubs said:
Check your flash counter and if it's anything over 0 run Triangle Away to set it back to 0.
Then follow the directions in the stickied thread for directions on how to revert back to stock. I installed the latest t-mobile ROM from this thread http://forum.xda-developers.com/showthread.php?t=1771687
Just make sure you get the T-mobile versions
Click to expand...
Click to collapse
Triangle Away only after you have stock kernel and stock recovery back on your phone. Otherwise it wont do you any good.
Odin flash the root66 firmware, triangle away, then full unroot from the supersu app.
Sent from my SGH-T999 using xda premium

DocHoliday77 said:
Triangle Away only after you have stock kernel and stock recovery back on your phone. Otherwise it wont do you any good.
Odin flash the root66 firmware, triangle away, then full unroot from the supersu app.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
how do i check my triangle and triangle away it ohh and my odin doesnt have pda it has bl ap cp csc

imfukked said:
how do i check my triangle and triangle away it ohh and my odin doesnt have pda it has bl ap cp csc
Click to expand...
Click to collapse
Reboot your phone and instead of pushing volume up to put it into recovery mode push volume down to bring it into download mode. This is also what you use to revert to stock via odin.

IT WORKED
HOLY **** IT WORKED I HAVENT HAD MY PHONE FOR A WEEK I THOUGHT I WAS SOO SCREWED YOU SAVED MY ASS THANK YOU SOOOOOOO MUCH!!!!!!!:laugh::laugh::laugh::laugh:

My understanding is that it's actually kind for of hard to brick your phone from doing software modifications. It is possible but I think only if you really screw something up. Like powering down while installing a recovery or something.
Sent from my SGH-T999 using xda app-developers app

Unplugging in the midst of a firmware flash, and flashing the wrong models firmware are the easiest ways people hard brick.
If you can get download mode and recovery to boot it can be fixed most of the time.
Sent from my SGH-T999 using xda premium

Yeah what happened with me is I downloaded hyperdrive to my internal and this was my first time and I didn't install cwm or anything like that so I did the factory reset and cleared cashe but then I relized there's no way to clear your dalvik and or launch hyperdrive so I tryed booting my phone and it got stuck on the samsung logo everytime so I used odin to put cwm on my phone and I couldn't access my internal or clear dalvik so I used an external and used my old galaxy s2 to download hyperdrive on to the external and then launched it on my s3 and it installed great it let me choose everything but when I went to launch the phone it got stuck on the hyperdrive boot animation so I tryed like 10 stock roms none of them worked it wouldn't get rid of the hyperdrive boot animation iether so then I was sher the link you gave me wasn't going to work but unlike the other odin ones I did it took time instead of only taking half a second and it worked
Sent from my SGH-T999 using xda app-developers app