Develop Bugs

[Q] tmobile OTA and rooted phone

i have a T989, rooted, Clockwork Mod, and installed some stock Android (sans bloatware) MOD.
i had updates set to automatic and am now being bugged to install the new TMobile update, which doesn't seem to be able to install with Clockwork, and i can't turn off the persistent Update prompts.
i've already bricked one GS2, and obviously fear doing it again. I wouldn't get another chance, i don't think. (i do have insurance on the phone, not sure if it would cover a rooted phone?)
what can someone tell me about the TMobile update and Clockwork, or whatever i need to do, go with the update or stop it somehow...?
thanks for your help.

Ota update requires stock recovery.
Grab one of the updated stock roms and flash via cwm. Then Odin the new baseband.
Sent from my SGH-T989

i think i have one of those stock roms - i chose one that was just 'the same thing but without some of the standard apps'. how can i check to see what rom i have...?
and what do you mean by baseband? the new update? is it already dl'd to my phone? i've searched through the phone's dirs (rooted File Explorere, i guess) and could not find anything...

sorry to be a pain - i can't brick another one, of course... (
is this what you mean by a 'stock updated rom':
http://forum.xda-developers.com/showthread.php?t=1312736 ?

glennnall said:
sorry to be a pain - i can't brick another one, of course... (
is this what you mean by a 'stock updated rom':
http://forum.xda-developers.com/showthread.php?t=1312736 ?
Click to expand...
Click to collapse
No, look for the KL1 release.
Baseband is your radio btw. Don't worry about the radio for now, just work on getting the rom flash.
Sent from my SGH-T989

ok, found Deodexed_KL1_T989 (T989UVKL1 by Whitehawkx) is that what i'm looking for? -
couple of questions:
he says on the post:
"DONT FLASH - add files to the zip in the app folder, then flash. Or usb connect drag to sd the use some rooted file explorer to place in system/app then reboot."
Flash or don't Flash? I'm transferring the zip to sd now, then i need to move it to system/app...?
once i've 'flashed' what do you mean "Odin the baseband"? i have Odin, used it last time...
thanks

GideonX said:
No, look for the KL1 release.
Baseband is your radio btw. Don't worry about the radio for now, just work on getting the rom flash.
Sent from my SGH-T989
Click to expand...
Click to collapse
I flashed the ROM, now i have 2.3.6, and now i'm stuck with 2 OTA notifications, one states postponed, and choosing START for the update does nothing.
help?

I had the base load on mine with a bunch of stuff frozen and Clockwork on it (plus root)
I first unfroze all the stuff I had frozen, then ODIN'd back the stock recovery. Didn't touch anything else, then told the OTA to go ahead.
It updated just fine -- removed root of course. I then ODIN'd back the clockwork recovery and re-installed SU, then re-froze all the boatware.
Done in about 15 minutes -- no muss, no fuss, didn't lose anything.

Genesis3 said:
I had the base load on mine with a bunch of stuff frozen and Clockwork on it (plus root)
I first unfroze all the stuff I had frozen, then ODIN'd back the stock recovery. Didn't touch anything else, then told the OTA to go ahead.
It updated just fine -- removed root of course. I then ODIN'd back the clockwork recovery and re-installed SU, then re-froze all the boatware.
Done in about 15 minutes -- no muss, no fuss, didn't lose anything.
Click to expand...
Click to collapse
ok, thanks - this is what i didn't understand - i can Odin back to Stock recovery?

for some reason Odin doesn't recognize my phone in download mode, but it does when i'm connected and the phone is on... any reason for this? i don't use odin in any means but download mode, right?

glennnall said:
I flashed the ROM, now i have 2.3.6, and now i'm stuck with 2 OTA notifications, one states postponed, and choosing START for the update does nothing.
help?
Click to expand...
Click to collapse
You can probably clear this up by formatting /system in CWM. Then wiping cache and dalvik. Then flash the FL1 update. Hit advance, fix permissions and then reboot.

GideonX said:
You can probably clear this up by formatting /system in CWM. Then wiping cache and dalvik. Then flash the FL1 update. Hit advance, fix permissions and then reboot.
Click to expand...
Click to collapse
did all this, nothing's changed. i'm unable to get Odin to see my phone in DL mode. when i boot into DL mode, the device manager shows an alert on my phone. in normal, the drivers work fine and Odin sees the phone.
damn.

[Solved] $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)

Basically this is what happened, I rooted my phone using TeamEpic-Root-from-Recovery-v5.zip and CWM-Recovery-LTE-SGS3-v5.tar.zip with Odin without any problems. Then I tried tampering with the framework-res.apk and I thought I did it correctly, I replaced it with the current res in the /system/framework folder of the internal sd. Then I rebooted my phone and bam stuck at the Samsung Galaxy S III screen. I've now tried finding a way to get into the internal sd card to replace the framework-res.apk back to original but my computer wont recognize it when in recovery or downloading mode. I have trying reflashing Clockworkmod several times and I've tried wiping the cache and factory reset. When I factory reset it says error mounting sd card, aborting. I am now out of ideas as to how to fix it and I'm not sure what to do with PIT files, which could be a possible solution. I am running Tmobile's Galaxy S3 T-999 16gb. All that being said, anyone who can help me get my phone back up and running I will reward you with $10 through paypal, because that's how desperate I am to fix my phone before someone finds out I bricked it!

Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
Something similar happened to me. What I did was use a different lower version of Odin and reinstalled the drivers, and everything worked fine. It may not work for you but it's just a, thought, and try reflashing with the T-Mobile Stock ICS rom.
Sent from my SGH-T999 using xda app-developers app

camacho.kyle said:
Something similar happened to me. What I did was use a different lower version of Odin and reinstalled the drivers, and everything worked fine. It may not work for you but it's just a, thought, and try reflashing with the T-Mobile Stock ICS rom.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, what do you mean by reinstall drivers, like kies? I can't flash any rom's because I can't transfer the zip files over to the sd card since my phone won't recognize it since it won't go past the samsung screen. All I can do is flash clockwork mod from odin like .md5 and .tar. If I install a lower version of Odin what version did you use, and do you think flashing clockwork mod will be able to replace the framework-res.apk through odin?

Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
iAmYoungSpiffy said:
Thanks for the reply, what do you mean by reinstall drivers, like kies?
Click to expand...
Click to collapse
Reinstall the drivers for Odin, and you can even try reinstalling Kies too. Make sure you restart your pc after you reinstall kies and the drivers.
Sent from my SGH-T999 using xda app-developers app

Are the files you flashed for a I9300? They do not look familiar to me.

Re: $10 Reward to whoever can help me get my phone working again! (SOFT BRICK)
Aerowinder said:
Are you using a SGH-T999 or an I9300? If the former, use the links in my signature. Should fix it if it's not hosed.
Uninstall Kies (and the drivers if the Kies uninstall doesn't do it).
You may want to Odin a stock rom. If you do, it it before flashing a recovery.
Click to expand...
Click to collapse
He's using a T999
Sent from my SGH-T999 using xda app-developers app

camacho.kyle said:
He's using a T999
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Do you think changing the clockworkmod .tar.md5 file and flashing something different will have any affect? If so, what do you suggest?

Check out my signature, it has everything you should need (save the OS you want).

Aerowinder said:
Check out my signature, it has everything you should need (save the OS you want).
Click to expand...
Click to collapse
Wow thanks for that clockworck mod! It has much more features than v5 I'm gonna play around with it and see what I can come up with.

Aerowinder said:
Check out my signature, it has everything you should need (save the OS you want).
Click to expand...
Click to collapse
Thank you for the files, I'm now able to flash roms from my sd. I"ve flashed your clockwork and superuser. However, when I load up the phone I'm still getting stuck at the samsung logo

no external sdcard?

Did you try to flash another rom? What were you using, and what did you flash?

Why are you trying to fix a bricked ROM with CWM?
Just Odin a stock rom, and work from there. I don't know why you would keep trying to reflash recovery, that isn't going to do squat for you.

Go to the section/post in the general section on ODIN and pick a STANDARD ODIN image...Odin isn't that hard to manage.
Or use the S3 toolbox posting in the general section.
Most likely, this is because the rom has something funny in the cache...WIPE it to factory if you can get into a recovery...
Scott

mt3g said:
no external sdcard?
Click to expand...
Click to collapse
I do, 64gb

Aerowinder said:
Did you try to flash another rom? What were you using, and what did you flash?
Click to expand...
Click to collapse
I used Odin v307 to flash TeamEpic-Root-from-Recovery-v5.zip, i used clockwork mod to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 (I got both of these from a post on these forums. I also tried superuser. Nothing is working do you have a download link to a ROM I could try?

You can't flash a rom from your external sdcard? or your internal? or either?

sbaeder said:
Go to the section/post in the general section on ODIN and pick a STANDARD ODIN image...Odin isn't that hard to manage.
Or use the S3 toolbox posting in the general section.
Most likely, this is because the rom has something funny in the cache...WIPE it to factory if you can get into a recovery...
Scott
Click to expand...
Click to collapse
I've now tried flashing Team Epic's ROM and I've wiped all cache restored to factory settings wiped dalvik cache, no progress.

mt3g said:
You can't flash a rom from your external sdcard? or your internal? or either?
Click to expand...
Click to collapse
Now that I updated my clockwork mod I'm able to flash from my sd card. Trouble for me is finding the right ROM that is compatible and appealing. I've tried a few now and whenever I flash them I go to boot up the phone and I get stopped on the samsung galaxy s iii logo. There has to be a way to wipe everything and flash a fresh clean rom. I've stayed up till 2 in the morning only to get up at 6 in the morning two nights in a row now totaling almost 10 hours of trying to fix my phone

iAmYoungSpiffy said:
I used Odin v307 to flash TeamEpic-Root-from-Recovery-v5.zip, i used clockwork mod to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 (I got both of these from a post on these forums. I also tried superuser. Nothing is working do you have a download link to a ROM I could try?
Click to expand...
Click to collapse
From this quote it seems that you are flashing TWRP recovery and the flashing CWR right after it. That makes no sense. I don't use CWR on this phone but have used it before. So I'm not sure that LTE should be in the description as T999 isn't an LTE device. I could be wrong though. You can get an Odin-able version of either TWRP or CWR from this page.
Go here and download the stock image TMO T999UVDLJA. Follow the directions in the OP (make sure you unzip it first. Read and then read it again) . Fire up Odin and put the Root66 tar in the PDA slot (nothing in PIT). Flash the Root66. It will take about 5 minutes or so. Once it says Pass it should reboot. It WILL bootloop. If you have already flashed EITHER TWRP or CWR, then boot into recovery and Factory Reset. If you haven't flashed EITHER TWRP or CWR, then pull your battery and boot back into Download Mode. From there you put EITHER TWRP or CWR into the PDA slot and flash it. Pass. The reboot into recovery and Factory Reset.
First boot will take the longest bc it has to rebuild the /cache and /dalvik-cache. Let's get you up and running before you move on to flashing a custom ROM, OK?

[Q] Can't get LiquidSmooth v2.5 OFFICIAL to load on my Sprint phone

I am trying to get this ROM installed on my Sprint S3: http://forum.xda-developers.com/showthread.php?t=2148306. My phone is rooted and I have TWRP 2.5.0.0 installed. When I download the file on my pc and transfer it to my phone, I boot into recovery, wipe the data as recommended (already did a backup), and when I try to install, it says "Failed". I can get some other ROMS to work (Goodness, etc.) but this one I can't. The file name is Liquid-JB-v2.5-OFFICIAL-d2spr.zip. Any ideas as to where to start? I can't post in that ROM thread because I don't have more than 10 posts.
Any help is greatly appreciated!

robertfah said:
I am trying to get this ROM installed on my Sprint S3: http://forum.xda-developers.com/showthread.php?t=2148306. My phone is rooted and I have TWRP 2.5.0.0 installed. When I download the file on my pc and transfer it to my phone, I boot into recovery, wipe the data as recommended (already did a backup), and when I try to install, it says "Failed". I can get some other ROMS to work (Goodness, etc.) but this one I can't. The file name is Liquid-JB-v2.5-OFFICIAL-d2spr.zip. Any ideas as to where to start? I can't post in that ROM thread because I don't have more than 10 posts.
Any help is greatly appreciated!
Click to expand...
Click to collapse
Down load it again, sounds like you got a bad one

robertfah said:
I am trying to get this ROM installed on my Sprint S3: http://forum.xda-developers.com/showthread.php?t=2148306. My phone is rooted and I have TWRP 2.5.0.0 installed. When I download the file on my pc and transfer it to my phone, I boot into recovery, wipe the data as recommended (already did a backup), and when I try to install, it says "Failed". I can get some other ROMS to work (Goodness, etc.) but this one I can't. The file name is Liquid-JB-v2.5-OFFICIAL-d2spr.zip. Any ideas as to where to start? I can't post in that ROM thread because I don't have more than 10 posts.
Any help is greatly appreciated!
Click to expand...
Click to collapse
It's either a bad download like evoer said, but more likely it's the firmware you're on. Starting with v2.5, you need to be on MD4 before you can flash the Rom. It'll fail otherwise.
The best way to get on MD4 is to go over the Freeza's Stock Rooted Rom thread and grab the MD4 Firmware update zip:
MD4 Firmware:
MD4 Firmware/modem/baseband update
MD5: EEEAFDBE59CF9C5B492B1A591EC92D02
Click to expand...
Click to collapse
The filename should be: Galaxy-S-fre3-MD4FirmwareModemAIO.zip
Just boot into recovery and flash this zip. Restart your phone and verify in Settings - about phone that the baseband ends with "MD4." Then reboot into recovery and flash LiquidSmooth like normal.
Let me know if you have any more problems.

evoer said:
Down load it again, sounds like you got a bad one
Click to expand...
Click to collapse
Yeah, I did that....I even tried to download the latest from GooManager and still got the same results. I'm surprised no one else has said anything, either that or something's jacked on my phone

topherk said:
It's either a bad download like evoer said, but more likely it's the firmware you're on. Starting with v2.5, you need to be on MD4 before you can flash the Rom. It'll fail otherwise.
Click to expand...
Click to collapse
I'm thinking this is it....I am dling it now and will let you know. Should I run it right from TWRP (I currently don't have any ROM installed but I can mount my sdcard and access the file that way) or do a restore and then run it?

robertfah said:
I'm thinking this is it....I am dling it now and will let you know. Should I run it right from TWRP (I currently don't have any ROM installed but I can mount my sdcard and access the file that way) or do a restore and then run it?
Click to expand...
Click to collapse
Restore any working rom, flash md4, go to settings and verify. Flash liquid...should be golden

atesamc days
topherk and evoer, thanks a BUNCH for helping me with this. That was the problem. As soon as I did a restore, flashed the new MD4, verified it, then flashed liquid, it worked like a charm!
Thanks again! :good:

[Q] Can't install new ROMs

So I'm currently running Cyanogenmod version 10.2.0 .. Android 4.3.1.
I've updated to the newest version of TWRP.
I factory wipe, then try to install a different ROM.. for example I've tried PA & AOKP.
Every time I try this it fails within 1 second and I have to restore a backup and go back to Cyanogenmod.
EDIT: I have a T-Mobile Galaxy S3
I have attached an image of when I get an error when I try to flash.
UPDATE:
Alright so I was able to get past that error by going into advanced wipe and selecting "System". Now when I flash I get a new error. I am attaching a new picture.

You need to give more info on the error
Sent from my SGH-M919 using Tapatalk

serio22 said:
You need to give more info on the error
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I'm at work now. I'll post and update with the error later.

Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app

spartan268 said:
Do you have a t-mobile s3? If you are from a different carrier such as wind mobile I could know the problem. I also had a problem flashing 4.3 Roms with my t999v wind s3.
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Mine is T-Mobile. I'm still at work til 2AM EST. I'll probably post my error tomorrow.

Alright guys, I attached a screenshot (picture lol) of my phone and the error I am getting when I try to flash different ROMs. Any help?

Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.

Shallwhat said:
Alright guys.. I was able to get past that other error but now I have a new one when trying to install a new ROM.
Here is a screenshot of the error.
Click to expand...
Click to collapse
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.

Noobiologist said:
Update your recovery. You're using TWRP 2.5.5.0 when the latest one is 2.6.3.1. If you can't boot into Android, Odin the TWRP recovery. Also, make sure you completely wipe your internal storage before flashing a custom ROM. If that custom ROM isn't working for you, try another one to see if that flashes since that would indicate that the custom ROM you're trying to flash could potentially be a bad download.
You also need to post more information about your phone.
Which custom ROM are you using?
Which kernel are you using or trying to use?
etc etc.
Click to expand...
Click to collapse
I've tried flashing multiple ROMS.. Slimbeam.. AOKP.. ParanoidAndroid.. I've downloaded from GOOManager and I've also downloaded from external links and put on my external SD card. Nothing works. Like I said in the OP I am running Cyanogenmod 10.2.. Android 4.3.1. I'm using the Ktweaker kernel.
I updated my TWRP from Goomanager and it only updated to 2.5.5.0. How do I get it to update to 2.6.3.1?

So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.

Same problem happened to me last night, I tried to install the modem again but the same error keep coming up.

To everyone with issues updating recovery. Goo has a openrecovery script issue. Your best bet is to flash latest Recovery using Odin. You may choose to use Mobile Odin if you feel like it.

Can't restore anything except Kitkat
I keep getting the same error, except I can't flash or restore any rom that isn't kitkat (all the kitkat roms are buggy so i want 4.3 back). I reflashed twrp 2.6.3.1 with odin but its still not letting me flash anything.
Also if it helps I can't copy anything from the internal SD to the external SD using twrp file manager.

Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3

I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?

Nothing will flash except Kitkat
Perseus71 said:
Older Rom's backups can't be restored due to file system changes. You will have to wipe everything and flash fresh if you want 4.3
Click to expand...
Click to collapse
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something

Shallwhat said:
So I just went to update TWRP from goomanager again and when it went to download it failed because "invaid MD5 sum".
Edit: So I tried updating again and it said it was successful. I rebooted into recovery and it still says 2.5.0.0
I'm lost.
Click to expand...
Click to collapse
Did odin flash of the most current recovery take care of your issue?
Hastily spouted for your befuddlement

GodLik3 said:
I tried the latest version of TWRP, and I'm on StockROM by TeamInferno. I got V7 and I saw an update on it last night (V8) so I downloaded it and tried to install it fom Clockworkmod recovery and it didn't work so I tried TWRP and the same thing happened. Do I have to wipe everything to update my ROM?
Click to expand...
Click to collapse
What was the specific error message when flashing ?
QuatroQuatro said:
Ive tried that multiple times. once the Odin flashable tw 4.3 downloads, I'm going to try that but I can't flash any fresh roms using twrp except 4.4 (Jellybam to be specific).
I tried Stockorama 4.3 tw, but it would just reboot after getting past the "samsung galaxy sIII" screen (tried insecure kernal too). I'm wondering if I'm in a weird soft brick or something
Click to expand...
Click to collapse
What is your TWRP Version ? Also what is your Bootloader version ? (No its not the baseband)

My bootloader is T999UVUEMJC
My baseband is uvuemjc
TWRP is version 2.6.3.1 (I've also tried 2.6.3.0)
I think it got updated bootloader/baseband when I odin flashed stock tw 4.3 (the only jellybean ROM that works)
I also made a backup of my 4.4, but it wouldn't let me restore even that.

You have been talking about 2 different things.
1. Flash a New Rom - Either Touchwiz or AOSP. $.3 or newer.
2. Restore a Rom - I think you are talking about a Nandroid Restore.
If you are referring to Point 1 as "Restore Rom" then you need to change terminology in order to help us understand your problem correctly. Re-Flashing a rom that you used to have is still Flashing not "Restore".
With that UVUEMJC Bootloader, you can completely forget about flashing previous Touchwiz Firmwares such as UVDMD5 or UVDLJC. If you tried them, you WILL brick your phone. If you tried Custom Touchwiz Roms based on those 2 firmwares, it may or may not work.
Now if you are trying to flash a AOSP Rom, either 4.3 or Kitkat 4.4, and you do have latest TWRP, (2.6.3.1), please specify the error message in detail.
You must do Factory Reset and Wipe Dalvik + Cache in the Recovery before flashing the AOSP Roms.

[RESOLVED] Help! My phone is stuck on the AT&T Logo!

I am returning my phone to my dad because i'm getting an upgrade and he wants to sell it, so i tried to revert to stock from CM12.1 unofficial nightlies. I flashed the FNJ1 system and boot.img. my phone was on FNJ1. now it's stuck on the at&t logo and i cant do anyhting, any help?
AT&T SGH-I747 UCUFNJ1 CM12.1 unofficial nightly.
Edit: In the mean time i've reverted to cm12 but i still need to revert to stock so any help is greatly appreciated.

You have to factory reset after flashing back to stock. If you are going to sell it, I suggest doing so from stock recovery.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
You have to factory reset after flashing back to stock. If you are going to sell it, I suggest doing so from stock recovery.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I reflashed the FNJ1 rom and then factory reset afterwards and it still hangs at the AT&T boot logo, any other suggestions?

Where did the rom come from exactly? There are a few that I've seen. Did you check the md5 to make sure the download wasn't corrupted?
Can you verify your bootloader / baseband?
Using terminal emulator (twrp has one built in) enter this.
getprop ro.bootloader
getprop ro.baseband
Let us know what it says.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Where did the rom come from exactly? There are a few that I've seen. Did you check the md5 to make sure the download wasn't corrupted?
Can you verify your bootloader / baseband?
Using terminal emulator (twrp has one built in) enter this.
getprop ro.bootloader
getprop ro.baseband
Let us know what it says.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
i used Enewman's fnj1 system and boot.img from the general forum here. and i cant boot into recovery only download mode, but i know for sure it was ucufnj1
also the other post is me:
We will need more detailed info if you don't mind.
What were you on before? cm 12.1
What "stock rom" and what recovery exactly did you flash. enewman's fnj1
How did you flash? cwm
You said it "still doesn't boot" but we're able to flash it, do you mean it just won't boot android? yes
Can you boot download mode? yes
What was wrong that made you need to flash the rom and recovery to make it boot, and how did it get to that point to begin with? need to get to stock to sell, wouldnt boot, and the soft brick help said to try flashing stock recovery.

I managed to boot into recovery by flashing an older version of CWM via Odin. i flashed CM12.1 back again and it boots! thank god i have a phone again. any ideas as to what is causing the softbrick?

Hard to say. I do know that enewman17 recommends flashing with twrp, and that's what most people have used AFAIK. So there may be something about the newer cwm that executes the script a little differently. That's purely a guess though. Could've just been a bad flash for whatever reason.
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
Hard to say. I do know that enewman17 recommends flashing with twrp, and that's what most people have used AFAIK. So there may be something about the newer cwm that executes the script a little differently. That's purely a guess though. Could've just been a bad flash for whatever reason.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Should I try flashing twrp and then flashing the stock rom?

if i'm not mistaken CWM has pretty much been abondoned and no longer updated.
twrp and philz are preferred.
then again , "couldve just been a bad flash for whatever reason".
"all i can really do is stay out of my own way and let the will of heaven be done"

l3gionaires said:
Should I try flashing twrp and then flashing the stock rom?
Click to expand...
Click to collapse
You can try it if you like. Keep cm available just in case though. You might try some of the other stock builds too. Check the general and development section. I think there's about 3 NJ2 roms, each done a little differently.
Sent from my SGH-T999 using Tapatalk

mrrocketdog said:
if i'm not mistaken CWM has pretty much been abondoned and no longer updated.
twrp and philz are preferred.
then again , "couldve just been a bad flash for whatever reason".
"all i can really do is stay out of my own way and let the will of heaven be done"
Click to expand...
Click to collapse
TWRP is a million times better! works great thanks for the suggestion!
DocHoliday77 said:
You can try it if you like. Keep cm available just in case though. You might try some of the other stock builds too. Check the general and development section. I think there's about 3 NJ2 roms, each done a little differently.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
i updated my bootloader and modem to nj2 then flashed the stock rom for nj2 (this time using TWRP) and had the same outcome, it just hangs on the AT&T logo. I think this phone is doomed to be a CM12.1 phone.

That's strange. Did you try a different one if the NJ2 stock roms as well?
Oh and did you check the md5 to make sure the download wasn't corrupted?
Sent from my SGH-T999 using Tapatalk

DocHoliday77 said:
That's strange. Did you try a different one if the NJ2 stock roms as well?
Oh and did you check the md5 to make sure the download wasn't corrupted?
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
all md5s match and i tried enewman's deodexed fnj2 roms as well and it still hangs at AT&T Logo. maybe it's an issue of returning from Lollipop to KK?

Check the cm rom threads. Maybe someone else there has run into a similar problem. I don't use it myself, so I'm not familiar enough with it to say.
I'll try to do a little digging when I get home. There's got to be some sort of explanation!
(Have you ever tried reformatting /system to anything other than ext4? )
Sent from my SGH-T999 using Tapatalk
---------- Post added at 12:26 AM ---------- Previous post was at 12:25 AM ----------
Maybe try another TW custom rom. Just to see if it does the same thing.
Sent from my SGH-T999 using Tapatalk

It is probably a matter of coming back from an AOSP/CyanogenMod Lollipop rom back to a stock KitKat rom. I have seen a number of reports of people having the same issue of getting stuck at the logo during boot.
I have seen two fixes being reported as working, both are going to make you work to set the phone up for use.
1) After flashing enewman17's NJ1/NJ2 rom, stay in recovery and flash the stock recovery. Reboot into recovery then do a factory reset from the stock recovery.
2) If the above didn't work, use Odin to reflash TWRP or Philz recovery. From the recovery format the internal sdcard. Have the NJ1/NJ2 rom stored on an external sdcard so that you can reflash it from recovery.

dawgdoc said:
It is probably a matter of coming back from an AOSP/CyanogenMod Lollipop rom back to a stock KitKat rom. I have seen a number of reports of people having the same issue of getting stuck at the logo during boot.
I have seen two fixes being reported as working, both are going to make you work to set the phone up for use.
1) After flashing enewman17's NJ1/NJ2 rom, stay in recovery and flash the stock recovery. Reboot into recovery then do a factory reset from the stock recovery.
2) If the above didn't work, use Odin to reflash TWRP or Philz recovery. From the recovery format the internal sdcard. Have the NJ1/NJ2 rom stored on an external sdcard so that you can reflash it from recovery.
Click to expand...
Click to collapse
i'll try these when I get home and update asap
also @ DocHoliday I don't Know how to do that

dawgdoc said:
It is probably a matter of coming back from an AOSP/CyanogenMod Lollipop rom back to a stock KitKat rom. I have seen a number of reports of people having the same issue of getting stuck at the logo during boot.
I have seen two fixes being reported as working, both are going to make you work to set the phone up for use.
1) After flashing enewman17's NJ1/NJ2 rom, stay in recovery and flash the stock recovery. Reboot into recovery then do a factory reset from the stock recovery.
2) If the above didn't work, use Odin to reflash TWRP or Philz recovery. From the recovery format the internal sdcard. Have the NJ1/NJ2 rom stored on an external sdcard so that you can reflash it from recovery.
Click to expand...
Click to collapse
l3gionaires said:
i'll try these when I get home and update asap
also @ DocHoliday I don't Know how to do that
Click to expand...
Click to collapse
#1 worked for me! for some reason when i was on NJ1, the recovery didn't work, so i guess updating to NJ2 fixed it? anyways who cares! I'm back to fully bloated TW! Thank you guys for all your help!

l3gionaires said:
#1 worked for me! for some reason when i was on NJ1, the recovery didn't work, so i guess updating to NJ2 fixed it? anyways who cares! I'm back to fully bloated TW! Thank you guys for all your help!
Click to expand...
Click to collapse
Glad to hear it worked. :victory: Now to find a buyer.