Develop Bugs

[ODIN] Stock DJ20

This should help a few people out. Thanks to dfgged, we now have stock Odin files. There has been minimal testing of these, but they do in fact work to help recover. It won't fix everything, but if you had to go back to stock for warranty reasons, this would be better than having a really messed up ROM. Currently, I only have the System and Kernel. Both are untouched, minus the System dump being rooted, which was required to get the dump. Flash in Odin via the PDA button. I will also work on getting the rest of the usable images posted, and will post a CWM flashable package for stock, stock deodexed, and debloated then as well for DJ20.
System
Kernel

So I flashed dl09 followed by both above and I'm still stuck at the Samsung screen...wtf?

If you have a Fascinate, why did you flash these files? If you have a Continuum, why did you flash DL09?

imnuts said:
If you have a Fascinate, why did you flash these files? If you have a Continuum, why did you flash DL09?
Click to expand...
Click to collapse
I have both. I needed to try something on the continuum with prl and modem modification to try and overwrite vzw pop settings. But now nothing on the continuum. And it doesn't appear to be any Odin backs...

jenisiz said:
I have both. I needed to try something on the continuum with prl and modem modification to try and overwrite vzw pop settings. But now nothing on the continuum. And it doesn't appear to be any Odin backs...
Click to expand...
Click to collapse
so you flashed verizon odin files on your continuum? that wasnt going to end well

nitsuj17 said:
so you flashed verizon odin files on your continuum? that wasnt going to end well
Click to expand...
Click to collapse
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.

jenisiz said:
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
Click to expand...
Click to collapse
By confirmed do you mean "not at all confirmed"?

jenisiz said:
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
Click to expand...
Click to collapse
where was it confirmed? i dont recall ever seeing that

jenisiz said:
No kidding...but it has been confirmed that dl09 works on the continuum...however for somereason, not so well on mine.
Click to expand...
Click to collapse
The only thing that is confirmed to work as far as going from the Fascinate to the Continuum are the radios. If you get a botched up baseband, you can flash a Fascinate radio to a Continuum (and probably the other way if we had Continuum radios, but we don't), but that is the only thing that is cross-compatible that I've seen. Maybe you could get most of a ROM to work as well, but you'd loose your softkeys as well as the ticker functionality if you didn't have the proper framework files.

nitsuj17 said:
where was it confirmed? i dont recall ever seeing that
Click to expand...
Click to collapse
Search...dl09 has been confirmed. I'd post links but its to much trouble on my phone. But I attempted and no go...still searching for ideas. Confused why I would be held up by the radio?

jenisiz said:
Search...dl09 has been confirmed. I'd post links but its to much trouble on my phone. But I attempted and no go...still searching for ideas. Confused why I would be held up by the radio?
Click to expand...
Click to collapse
I just searched the entire Continuum sub-forum, and there is no mention anywhere that DL09 from the Fascinate works on the Continuum. The only thing I found close was mention that the DL09 baseband works, but there is no mention of anyone using DL09 on their Continuum. I even searched at Android Central and Android Forums, and no one anywhere has flashed a full DL09 that is recorded at XDA/AC/AF.

imnuts said:
I just searched the entire Continuum sub-forum, and there is no mention anywhere that DL09 from the Fascinate works on the Continuum. The only thing I found close was mention that the DL09 baseband works, but there is no mention of anyone using DL09 on their Continuum. I even searched at Android Central and Android Forums, and no one anywhere has flashed a full DL09 that is recorded at XDA/AC/AF.
Click to expand...
Click to collapse
That's what I attempted? I flashed the band and no boot...not complete dl09
Edit: You and I actually talked about it through pm.

Flashing the modem doesn't cause the phone to stop booting, so something else is likely the problem.

jenisiz said:
That's what I attempted? I flashed the band and no boot...not complete dl09
Edit: You and I actually talked about it through pm.
Click to expand...
Click to collapse
you made it sound like you flashed the dl09 rom, thats where i was coming from on my comments

Nope...not the rom lol. I was going off of a convo in pm with nuts. I wish it was that obvious though...

hi everyone..
having an issue with this recovery...i have used this file twice before to recover the wife's continuum.. however last night it wouldn't work.. meaning, it flashes in ODIN just fine, gives me "success" however when the phone reboots, nothing has flashed and it is exactly the same as before flashing..
i have red cwm on the phone, and have tried clearing everything (cache, dalvik, data/factory reset, mounted all partitions and wiped those) i also tried flashing the kernel which seemed to work.. however it still will not reset to factory.. i used the same file i have on my computer that worked 2x before, and even re-downloaded the one posted here and tried that as well.. nothing..
it appears for some reason the phone accepts the connection and/or files, but won't "run" them if that makes any sense...
i also have 2 nandroid backups that i tried to restore, which is the factory setup..and it hangs at the samsung logo (i gave up after 20 mins and pulled battery) .. and the second nandroid takes me to the deodexed/basic rom that was built here.. which works but has issues..
im trying to get back to complete stock.. i have also tried using superoneclick to unroot, but the program gives me an "error 22" when pushing rage, and locks up..
i have tested adb, and it will connect to phone, but NOTHING can be pushed or pulled using the commands..
im lost here.. anyone have any ideas?

Did you convert the partition with voodoo?
Sent from my SCH-I400 using XDA Premium App

trailblazer101 said:
Did you convert the partition with voodoo?
Sent from my SCH-I400 using XDA Premium App
Click to expand...
Click to collapse
thanks for the reply sir..
i did not convert to voodoo...however i will check that in the voodoo section just to be certain its not toggled..im very familiar with voodoo, as i ran it on my fascinate for a long time .. i am using factory cable as well.. i will edit the post if it comes to fruition that it did..i never flashed a kernel - unless the one with the ROM here was voodoo..but i dont remember hearing sexy lady telling me anything when i flashed it
this is SO frustrating..it worked 2x before.. im assuming something is borked with r/w somewhere..but i havent a clue where to look to change it..
it boots to blue recovery, run update.zip to red..
under mounts and storage (that i cleared all on before) it currently reads all mounted except /dbdata which is unmounted..

Lmao, sexy lady...
When I get home, log into the Continuum irc channel, and lets see if we can't straighten you out
Sent from my SCH-I400 using XDA Premium App

any chance we can have the OP links updated, please, i tried downloading the files but links are broken

Where's all the ROMS!

We need more development!
Sent from my LG-P930 using XDA App

I mean WHERE ARE ALL THE ROMS! terrible grammar
Sent from my LG-P930 using XDA App

Instead of asking. Why don't you learn to develop one? Then, there would be more.

Was that a question? Cause last time I checked a question supposed to end with a question mark: "?"
Anyhow, first thing first, we need figure out what's the deal with boot loops, when that solved then we could move on forward with the roms.
Right now I'm on stock rom, and I know if I reboot or shutdown the phone, I'll need go through CWM to restore last backup, because it will boot loop. Fortunately unbricking process still works on my phone, my understanding that few people already hard bricked their phones after installing a custom rom...

[email protected] said:
Was that a question? Cause last time I checked a question supposed to end with a question mark: "?"
Anyhow, first thing first, we need figure out what's the deal with boot loops, when that solved then we could move on forward with the roms.
Right now I'm on stock rom, and I know if I reboot or shutdown the phone, I'll need go through CWM to restore last backup, because it will boot loop. Fortunately unbricking process still works on my phone, my understanding that few people already hard bricked their phones after installing a custom rom...
Click to expand...
Click to collapse
I'm in the same boat too. I've customized my stock rom, but can't really reboot. The best thing I can do is quick boot to CWM then reboot from CWM.

[email protected] said:
Was that a question? Cause last time I checked a question supposed to end with a question mark: "?"
Anyhow, first thing first, we need figure out what's the deal with boot loops, when that solved then we could move on forward with the roms.
Right now I'm on stock rom, and I know if I reboot or shutdown the phone, I'll need go through CWM to restore last backup, because it will boot loop. Fortunately unbricking process still works on my phone, my understanding that few people already hard bricked their phones after installing a custom rom...
Click to expand...
Click to collapse
I was having a bunch of problems with bootloops after a reboot. Since I formatted /data through ADW and reflashed a rom, i havent had any more
Sent from my LG-P930 using XDA App

red_solo_cup said:
I was having a bunch of problems with bootloops after a reboot. Since I formatted /data through ADW and reflashed a rom, i havent had any more
Sent from my LG-P930 using XDA App
Click to expand...
Click to collapse
But you didn't restore your data after that, correct? You just started fresh?
The factory rest and formating /data is the same thing as far as I could tell...

@[email protected]
That is correct. Right after flashing I restored backups through titanium backup. It solved the problems I was having, but I can't say for sure it will work for everyone.
Sent from my LG-P930 using XDA App

I'm gonna hijack this thread and derail it, for now. Red_solo_cup, was your username inspired a certain song sang by a certain quirky country singer by the name of Toby Keith? hehe

aquariuz23 said:
I'm gonna hijack this thread and derail it, for now. Red_solo_cup, was your username inspired a certain song sang by a certain quirky country singer by the name of Toby Keith? hehe
Click to expand...
Click to collapse
Haha, no way. I may have to retire this handle...
I don't listen to country.

I gave up on looking for anyone to support this phone, much less the Bell version. I'll wait for ICS to be released, and revert back to a manufacturer that has developer support within the next year or so.

red_solo_cup said:
Haha, no way. I may have to retire this handle...
I don't listen to country.
Click to expand...
Click to collapse
LOL! Dang! Well, it's a funny song nonetheless.
---------- Post added at 09:25 AM ---------- Previous post was at 09:10 AM ----------
LiViD said:
I gave up on looking for anyone to support this phone, much less the Bell version. I'll wait for ICS to be released, and revert back to a manufacturer that has developer support within the next year or so.
Click to expand...
Click to collapse
I haven't really given up just yet, but the slow down we are currently experiencing after the excitement of achieving CWM backup and Custom ROMs is eating me up inside. We have lost momentum on the development of new ROMs or Kernels or Mods for this phone, and in all honesty, is quite disheartening. I am grateful for the things we have obtained for this phone and to the Devs and Users who have come over to help us achieve them, but we need more, and I know we can get more. There must be something we can do, people we can speak with. I know it is hard for Devs to create something without physically having the phone in their hands so I understand why things are progressing so slow, and hopefully soon some of them will pick up this phone as well.
Let's try to reach out again to Devs that we know from other threads to help us out with new things to use. We seem to especially need custom Kernels for this phone, so let's find those who can do kernels. Let's not give up hope yet, let's keep trying and jump start this forum back to life.

Help! Phone not bricked, but won't boot.

Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?

Try flashing the stock tar in odin if nothing else works.

DroidGnome said:
Ok wasn't sure if I should post this in Q&A or Dev... but since it's a question:
"Can anyone help with this?" ..
Here's the situation.
Sprint Galaxy S3.. using Blazer ROM 1.6
Team Epic Recovery (non-touch), don't recall exact version
Everything has been fine the last week or so.
I changed 2 things earlier today:
1) Using NFC Task Manager, I enabled "NFC during AirPlane mode" after which it asked me to reboot. I did not at that moment...
2) I modified build.prop to change the default alarm ringtone.
I also did not reboot as I was about to make some other changes...
Since I'm at work, I got sidetracked, but noticed something since the phone was on my desk face up. It suddenly rebooted on it's own.
No big deal, I had thought... except it never came back on.
And now.. It won't boot up at all. I cannot go into recovery either!!
I CAN go into download mode... so I did so and tried to reflash recovery.
Still unable to boot up or go into recovery..(Phone flashes the samsung logo , then disappears forever).
I'm attempting to download the stock ROM via the toolkit and see if that will fix things, but without recovery I'm pretty sure nothing is going to work.
Has anyone seen something like this before? Where it will go into download mode but NOT recovery?
Click to expand...
Click to collapse
Just flash the stock tar ur downloading in Odin. Ur fine even if you managed to Bork recovery as long as u can still get into dl mode ur ok

I've haven't seen this problem on the Sprint variant yet but it definitly sounds like it's fixable
Like others have pointed out, since you can get into Download mode fine flash the Stock Odin tar file found here
When you boot up I would consider doing a data wipe (Factory Reset option in Settings>Back up and reset) but that's up to you

Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium

DroidGnome said:
Yep.. that stock ROM fixed it... now to 're-root' and reapply my ROM... fun fun fun.
I'm thinking that the build.prop change must have caused it.. will be testing that over the weekend to be sure
Click to expand...
Click to collapse
Ya Ive seen some build.prop changes mess things up. Luckily you could get back up.
Fun feeling huh! lol

fergie716 said:
That is weird tho.. I edit my build.prop all the time and haven't seen this before.
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store

DroidGnome said:
So far all is working and I didn't even have to wipe the data (actually couldn't at first because I couldn't get into recovery hehe) , and I'm guessing the build prop must have been because I did it on the device, and 'maybe' I hit a stray key or something.. usually I edit at home and push it to the phone but I was in sort of a hurry.
WILL NEVER DO THAT AGAIN!
As I watched it attempt to boot up each time, I kept coming up with different excuses to try to tell the Sprint store
Click to expand...
Click to collapse
Glad to hear you're up and running again!!
Best excuse ever to Sprint is when I woke up it was like that haha

Flashing ROM

I have downloaded the ROM Classic v0.1.0 Supermagic, placed it on my SD card. I have also unlocked my bootloader and have CWM recovery. I have returned to the bootloader screen, went to recovery mode, and went to select which zip I wanted to flash. I found the classic v0.1.0 file and slected it, which I thought would begin the flash/download. It simply opened and gave me 3 more options for files. data/, system/, and META-INF/
I should probably mention that after getting the classic v0.1.0, i extracted it and put that file on my sd card.
I have an EVO 4G, unlocked but still with the S-ON, although I can still flash files. I really appreciate any help.

Don't extract a rom..and use smelkus recovery its better than that one
Sent from my PC36100 using xda premium

but other than that mistake, it looks like I'm on track? and speed really isn't an issue right now. As new as I am, I simply want it to work.

WeAreGuns said:
but other than that mistake, it looks like I'm on track? and speed really isn't an issue right now. As new as I am, I simply want it to work.
Click to expand...
Click to collapse
+1 on what Ireyes said and also wipe all except sd card 3 times, then flash.

Read the Evo guide in my signature

MIKESTONY said:
+1 on what Ireyes said and also wipe all except sd card 3 times, then flash.
Click to expand...
Click to collapse
this will help I hope. i'm stuck in a boot loop atm. I eventually cose a different ROM, papasmurfs CM9, but i kept the same procedures, all went well until this boot loop. hope this wipe helps.

HipKat said:
Read the Evo guide in my signature
Click to expand...
Click to collapse
Wow. That helps. I followed the rules and read everything I could before attempting anything and searched and read some more. Somehow I missed that thread. Would have saved me a boatload of time and frustration.

WeAreGuns said:
Wow. That helps. I followed the rules and read everything I could before attempting anything and searched and read some more. Somehow I missed that thread. Would have saved me a boatload of time and frustration.
Click to expand...
Click to collapse
Try fully Rooting your evo I had the same problems when I unlocked the boot loader on the og evo for the second time.don't worry you can RUU it and get back to fully stock if you have any problems.
this right here is my pretty boy swag!

For all the flashers here for the T989

The whole process is pretty simple on what I have done. I will explain my situation here and my question that has got be baffled.
So it all started about two weeks ago, where I was flashing LiquidSmooth on my phone. I had a Touch-type CWM. It isn't mega old but it's pretty old for CWM, I haven't updated in a while (as i've seen there are updates to recent ones).
Anywho, I did a complete wipe, used the darkside wipe, alongside with the darkside cache wipe.
I think this was my fault, so please correct me anyone if I am wrong here. I accidentally hit "reboot phone" instead of "reboot bootloader"
I got a permabrick from this whole ordeal. It was a permabrick because It said QHSUSB_DLOAD in the device manager, looking this up further confirmed my reasoning. I didn't want to jtag because that invovles removing the phone to pieces and soldering on wires etc. etc.
So I resorted to send it out to Samsung.
All is well when it came back. I made sure this time the whole phone was setup properly.
So I use Odin install for CWM and SU was installed via CWM. I install an older version of CWM (non-touch, i believe 1st revision as i've posted in one of the threads).
I kept stock ROM, everything was working okay and suddenly, KERPLUNK, it went back into permanent brick after I deleted cache partition, dalvik cache, and battery cache wipe. I didn't do fix permissions or anything, just hit reboot afterwards.
This is a super head scratcher here..... Anyone know where I went wrong?
Any insight here is greatly appreciated! :good:
P.S. I am now sending in my phone TWICE to Samsung for repairs.

If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it

LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium

All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium

rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well

LoopDoGG79 said:
If you are on the most up to date CWM, do not use the scripts. They are no longer needed, and will cause problems( hard brick though, never heard of) The second time, im stumped. I suggest go to TWRP and ditch the scripts. Latest TWRP does not need it
Click to expand...
Click to collapse
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
suaverc118 said:
I finally jumped in the water and flashed twrp! Yay!
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Nice! What is TWRP and how is it like?
rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
playya said:
great call on that I had to educate a few users that the d2tmo is not for our phone but indeed the S3. Good catch on your part and it sounds like user error as well
Click to expand...
Click to collapse
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.

You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium

XxGoKoUxX said:
Could you please educate me with a link referring to what TWRP is? Sorry, i'm still fairly new to the scene and all i've ever been educated upon is CWM.
Nice! What is TWRP and how is it like?
I've flashed the hercules ROM. I know this for sure because Liquidsmooth was working, it was extremely glitchy (playing games gave me pixelated actions sometimes, and using something like gameCIH/Game Guardian was unworkable). So i decided to ditch it and was getting ready to flash Jedi Mind Trick.
After the whole hard bricking ordeal, I decided to stick to stock rom, and even on that, I just flashed CWM and SU ONLY. Rebooted, and deleted the cache's (like i've posted to you) with absolutely no success. It baffled me that I bricked the phone AGAIN too!
Yes..... there is something wrong, i feel it is a user error also, but i'm very unsure where to even start
Once again, all of your insight is well appreciated! I just do not want to hardbrick my phone AGAIN and have to send it to Samsung. I am not allowed to even think of a replacement because this was a b-day present a year or two ago from my fiance.
Click to expand...
Click to collapse
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1

DM_Sledge said:
You say that it is bricked again. Do you mean by that, that you cannot get into recovery?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yes, it is perma-bricked, meaning the only method of fixing the brick is jtagg'ing
Upon plugging it into device manager, I get the prompt "QHSUSB_DLOAD" and phone doesn't even boot on no matter what combinations I make.
LoopDoGG79 said:
Flash this in recovery, reboot recovery, and you will have TWRP!!
TWRP 2.3.1.1
Click to expand...
Click to collapse
Thank you LoopDo, I will do this after I get my phone home again.

I have this phone, and none of the steps you listed would brick the device. Even with no ROM on the phone, you should still be able to get into recovery.
Is there something you aren't telling us?
Sent from my Galaxy Nexus using xda premium

Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since

XxGoKoUxX said:
Nope, wouldn't be a reason why I would lie because then the problem will never be resolved.... I'm kind of nervous on reflashing ONE more time after the phone comes home again....
The phone has been fixed once AGAIN, and it is in the process of being shipped back to me.
Phone will be home Wednesday and I will give it ONE more try
Wish me luck!
P.S. my PC has been glitchy lately, so that MAY or MAY NOT contribute to the permabrick, then again the brick doesn't happen until I flash stuff via CWM.
P.S.S. I've since re-installed Win 7 again, it hasn't been glitchy since
Click to expand...
Click to collapse
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.

I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.

I'd like to say thank you for everyone's patience. All of your insight is more than helpful!
DroidDonX said:
You most likely flashed the Wrong Liquidsmooth ROM (incompatible Kernel), and it hard bricked the phone. It happened to me the same way, and I had to send it in for JTAG.
Click to expand...
Click to collapse
I might have, but the one i downloaded (which is still on the phone's memory card) is a hercules ROM. Either way on my second try there was a hard brick also, in return of which I had to resend it in. The second try was just simply: Odin---->CWM---->Root---->SU---->wipe cache partition+fix permissions+wipe dalvik cache via CWM (not the super scripts).
cipsaz said:
I have bricked my phone installing the Liquidsmooth ROM too. I downloaded the wrong ROM, though. The thread should have a big ****in warning to double check the ROM you are about to download, otherwise your phone is a toast. There were more people who bricked their phones by installing the Liquidsmooth.
Well, I got it back from the warranty and the phone looks good. Installed that Liquidsmooth again and played for a day. Tried other JB ROMs. Most of them are OK in terms of battery life and smoothness, but there is something wrong with the signal. People always say my voice isn't clear. I got tired of all this BS and testing new ROMs and went to back to ICS and won't look back, not anytime.
Don't use darkside scripts, btw. You don't need that anymore.
Click to expand...
Click to collapse
Thanks again for your insight I think i'm done with flashing for a little bit for now.... I kind of want as factory of a JB Rom as possible. :good:
If anyone has any idea where I can get that, please let me know as my Stock ICS is a bit laggy at times, with the facial recognition system, it lags even worse!

rymanh said:
All the steps you say you did don't point to a brick. But one thing caught my eye! You said you were flashing liquidsmooth? What File did you flash? Did it have Hercules in the name? Because if it didn't then it's not for our phone.. I only ask because a lot of other people made that mistake
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
that just happened to me today with liquid smooth. i had to unroot, flash stock, and start over. im pretty sure i got it from goo.im under hercules. unfortunate mislabeling? oh yeah, and if your phone shows anything other than nothing, youre not hard bricked. thats why its called Hercules, i think. ive been soft bricked so many times from dumb **** like. ****ing with the governors and all that **** cm gives you the option to do when there aint even a 1080p camera that works fully = / lol <3 Cm I Love Yew!! But yeah, odin will set you free!!!