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!!!
Related
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.
Hello all! I've been trying to fix my phone for a few days, and can't seem to do it, so I thought I'd make a post regarding it.
I believe the beginning of this originated after trying to go back to gingerbread from fc15 ICS. To learn from my mistakes, this is NOT good, right? lol. probably because fc15 wasn't made for gingerbread?
I was able to get into CWM, but I couldn't perform a recovery or install a new ROM. At this time (after trying a whole bunch of things to fix my device), I may or may not be rooted, but I'm almost certain I am not because I can't get into CWM. If I have to lose all of my data, I guess I will (I didn't have an SD card at the time - just got one), but if there's any way I would like to keep my data. Also, at this point, I'm at the "formware upgrade encountered an issue. please select revoery mode in kies and try again". I have been able to get rid of this screen in the past, but I'd like to know the best rout to go from here.
I have read about bricked devices for awhile now, but to attempt to link the hazy definition I have with experience, is my device bricked?
Please help me!
Thank you.
tf201
I'm sorry, just now seeing the sticky regarding bricked device prevention. But I'd like to know how to identify a bricked device (besides not being able to do anything at all - which isn't my case), and if I have any option at this point.
tf201
andddlay said:
I'm sorry, just now seeing the sticky regarding bricked device prevention. But I'd like to know how to identify a bricked device (besides not being able to do anything at all - which isn't my case), and if I have any option at this point.
tf201
Click to expand...
Click to collapse
If you can get into download mode then Odin back to el26 like most instructions say to. Once you have a working GB then you can make a decision on where to go from there. Others might have better advice as that's gonna kill all you're data.
Swyped from my E4GT running Blazer 4.1 using xda premium
CyberpodS2 said:
If you can get into download mode then Odin back to el26 like most instructions say to. Once you have a working GB then you can make a decision on where to go from there. Others might have better advice as that's gonna kill all you're data.
Swyped from my E4GT running Blazer 4.1 using xda premium
Click to expand...
Click to collapse
thanks for the reply! after flashing stockcwm-el26, i was able to get back into cwm. however, from there i'm still having trouble. it will not boo. i'm still going to try a whole bunch of stuff lol
tf201
Hopefully someone will comment on my suggestion... If you can get into cwm then I would use calc's format all zip then flash a ROM that has a great record of smooth install.I personally have never had a problem with Blazer so that's what I would flash. Like I said, hopefully someone will either agree or have a better solution before you go with my idea. Good luck and make sure if you get it going you share your leanings!
Swyped from my E4GT running Blazer 4.1 using xda premium
Best bet is to download one of sfhub's one click root methods since your phone can still get into download mode. Doesn't matter what u already have on ur phone as his method will wipe all and replace all as long as you can get into download mode with your computer recognizing ur phone.
Sent from my SPH-D710 using XDA
dante32278 said:
Best bet is to download one of sfhub's one click root methods since your phone can still get into download mode. Doesn't matter what u already have on ur phone as his method will wipe all and replace all as long as you can get into download mode with your computer recognizing ur phone.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Yea what he said... Much easier than screwing around with flashing stuff like I suggested.
Swyped from my E4GT running Blazer 4.1 using xda premium
sorry for responding so late!
thank you both very much. i tried the program, and was still unable to recover the device - it always hung right at the end, unfortunately. a replacement device is in the mail, and i should get it very soon (thankfully for free).
another question i suppose i would like to ask...on cwm, it says i can mount internal storage as a mass-storage-device. when i try to do this, nothing pops up. is there a way to do this and, potentially, recovering my data?
tf201
I just got my gnex today. I had a epic 4g previously and flashed roms constantly so Im not a total noob as far as that goes. I used gnex toolbox to unlock bootloader,root and flash cwm, and then I tried first rom which I like which is miui. It would not boo, it just stuck on the splash screen. no biggie so I flashed factory image back and redid cwm and then flashed aokp and right now I have been staring at a unicorn head and animation for about 5 minutes with no end in sight. Am I doing something wrong? I also flashed franco kernel right after flashing aokp. Do I need to boot into rom first then do kernel?
funny that happened to me too, the first time I rooted and flashed, I fixed permissions and it booted,
Try pulling your battery then rebooting. Sometimes when flashing it will hang in boot the first time. If that doesnt work try flashing the rom only. Im no expert on the nexus but my friend's did that and it worked. Sometimes my i777 does it also but rebooting always has solved it for me. I juat happened to see your post on the main page hope it works for you.
Sent from my SGH-I777 using XDA
Ok fixing permissions didnt work, or reflashing. So I decided to reflash factory rom and it has dissappeared from both my downloads folder and gnex toolkit folder so I have to redownload.
Make sure you are doing a proper full wipe. See my signature.
And above all, make sure you are flashing the correct version or rom for your gn. So many versions out now that who knows.
HumanXv2 said:
Ok fixing permissions didnt work, or reflashing. So I decided to reflash factory rom and it has dissappeared from both my downloads folder and gnex toolkit folder so I have to redownload.
Click to expand...
Click to collapse
You said that your nandroid disappeared? Sounds like your bootloader may have locked again, this causes a full wipe, explaining how your nandroid disappeared.
Sent using a cell phone....
Am I the only person that finds it amusing that someone says "I'm not a total noob" and "I used a toolkit to unlock, root, and flash..." right after one another?
For the problem at hand, have you tried to just wipe data after flashing the ROM/Kernel combo?
obsanity said:
Make sure you are doing a proper full wipe. See my signature.
And above all, make sure you are flashing the correct version or rom for your gn. So many versions out now that who knows.
Click to expand...
Click to collapse
Awesome, worked like a charm. I didnt think about wiping at all. Thanks a lot man
imnuts said:
Am I the only person that finds it amusing that someone says "I'm not a total noob" and "I used a toolkit to unlock, root, and flash..." right after one another?
Click to expand...
Click to collapse
My personal favorite is:
"I'm not a noob, I've flashed countless ROMs on my XXX phone before"
"Have you tried using ADB?"
"What's ADB?"
ZeroBarrier said:
My personal favorite is:
"I'm not a noob, I've flashed countless ROMs on my XXX phone before"
"Have you tried using ADB?"
"What's ADB?"
Click to expand...
Click to collapse
Ahh masters of the command line scoffing at lesser people.
Move along
HumanXv2 said:
Ahh masters of the command line scoffing at lesser people.
Move along
Click to expand...
Click to collapse
actually its more like people dont understand the basics of how to root/unlock phones and then create threads going "HALP i borked my phone!!?!?!"
if you had taken the time to use and learn fastboot, or even how to properly flash a rom, this thread wouldnt have been created.
So i tried to update my AOKP with just using my phone. And after the reboot.. nothing happened. So i did a battery pull and now when I turn on my baby the led goes blue and stays there.. frozen. No access to recovery or download.
Black screen and blue led.. so yeah.
What I'm asking is.. there's no way of coming back?
Sent from my Old Evo using xda premium
Also.. I semi-bricked before and was able to fix via download mode.. so I know my way around.
Sent from my PC36100 using xda premium
When you updated AOKP you flashed the EL26 CWM kernel as per the instructions in all AOSP roms up until now? Both the recovery in AOKP 37 and the Zip for AOKP 39 (as far as I am aware) are not safe to flash in ICS Recovery.
BLoD is a sign that the bootloader is borked. Normally this is something fixable via JTAG. But it is also caused at Random by the Super Brick bug which can not be fixed. Sounds like you flashed not only an unsafe Zip but in an unsafe recovery and if you tell me you factory reset that would be even worse.
Our phone has a bug in its eMMC firmware which needs to be patched. All of the former ICS leaks have had kernels that can trigger it and last i checked only the Nighlies for CM9 have a safe updater binary used in conjunction with a made safe recovery are generally safe to flash from ICS. Which is exactly why the threads tell you to use the EL26 CWM kernel which if mobile can be flashed via mobile odin. Failure to do so will eventually at random trigger the bug.
Blue LED and not able to get phone into Odin mode = Hard Brick
another one bites the dust......i just don't know how the directions could be any more clear on flashing ICS ROM's. Maybe we need a sticky in every forum in bold letters that says:
"READ ME BEFORE FLASHING!"
I read the warnings and all that jazz. It was just a bad download thanks to the 4G. Mistakes happen. Relax @ above poster.
Yeah I went about it the right way. I have insurance with Sprint, hopefully I'll get lucky and get a new phone.
Thanks to the rest that answered.
Sent from my PC36100 using xda premium
I agree with Rican Bomba... Not everyone is a Android hacking Guru. We are all trying to learn here. I bricked my phone and i did follow QBking77's instructions (Who i believe to be the best at explaining things thoroughly in his videos) yet, there are so many post that aren't clear. I had force closes like crazy on AOKP and before i found the one poster that said don't wipe in ICS... I had done it and lights out R.I.P. First E4GT. I have flashed way too many times to count without incident. Some posters put more info on how not to brick than others. I followed QBking's method to a tee and something was still wrong... I don't blame him (He makes things crystal clear and is great at what he does), things happened and that was that. I learned something from a poster who was very clear and i won't make the mistake again (not to mention I'm leaving AOKP alone lol). Take it easy on these guys, they will learn soon with a little friendly direction
Rican Bx Bomba said:
I read the warnings and all that jazz. It was just a bad download thanks to the 4G. Mistakes happen. Relax @ above poster.
Yeah I went about it the right way. I have insurance with Sprint, hopefully I'll get lucky and get a new phone.
Thanks to the rest that answered.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Never never never never download a ROM through Mobile Network... and if you do, make sure you check the md5. I think almost all of my 4G ROM downloads have been corrupt
iniz94 said:
Never never never never download a ROM through Mobile Network... and if you do, make sure you check the md5. I think almost all of my 4G ROM downloads have been corrupt
Click to expand...
Click to collapse
Flashaholic lol no computer access at my job and at home at the moment.
Sent from my PC36100 using xda premium
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
alexanderd said:
Hi everyone. I'm new to the forum and I'm looking for a little help today.
I rooted my new Sprint Galaxy S III using Odin3-v3.04, and CWM_SuperUser_v3.0.7. Afterwards I rebooted and all was good.
I then downloaded I9300_Omega_v6.0_XXALF6 ROM and loaded on my phone and rebooted into recovery to install the ROM. I went through the install process, selected remove bloatware and installed. When finished I checked the reboot phone and clicked finish. The phone turned off and didn't ever turn back on.
I have pulled the battery and tried to power on using recovery, download mode and just power but nothing works.
Anyone have any idea what I can do?
Thank you for your time and help.
Click to expand...
Click to collapse
development area has a thread for that:
http://forum.xda-developers.com/showthread.php?t=1727171
ONLY use ROMs that you'll find here in these threads not the I9300; that s a different phone from ours.
Thanks I'll check there.
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Epix4G said:
But seriously I hope you learned your lesson and will read and hope you get your phone fixed or replaced
Sent from my Sprint Galaxy Nexus CDMA using Xparent ICS Blue Tapatalk 2
Click to expand...
Click to collapse
Hopefully this fail helps us all back from a potential brick. We live, flash and learn.
Sent from my SPH-D700 using xda premium
New phone on the way!
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
alexanderd said:
I was able to get a replacement sent from Sprint. Had to go to a corporate store and have a tech look at the phone and they agreed it was toast...
Luckily they didn't know it was due to my failed attempt to load an unsupported ROM.
Lesson learned... new phone should be in by the end of the week.
I'll be waiting for a supported ROM this time.
Click to expand...
Click to collapse
No wonder our insurance deductibles keep going up...
bizdady said:
No wonder our insurance deductibles keep going up...
Click to expand...
Click to collapse
+1
Still sucks for op
Sent from my SPH-L710 using Tapatalk 2
matrixzone5 said:
Honestly I was waiting for this to happen gid luck restoring it phone
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
Oh man tell me about it, I almost stupidly went on to the CM9 nightlies and downloaded the I9300 version before I thought to myself, "well wait a minute, that's not my model number!"
Duh, shoulda had a V8.
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
pizzlewizzle said:
I didnt install a GSM rom but still managed to brick somehow. Didnt touch any system files or do anything to where i should be bricked either. Any idea when a full stock Odin package will be made? My phone has been bricked for almost 2 days now
Edit: i started a tread here a few days ago -> http://forum.xda-developers.com/showthread.php?t=1731416 if anyone cares to look or has any advice for me
Thanks
Click to expand...
Click to collapse
What have you tried so far? Have you tried reflashing cwm recovery in Odin?
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
taygutta said:
I did the same thing that the OP said, flashed that omega rom and now my phone wont turn on either.
I was going to try the jig method
Click to expand...
Click to collapse
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
bizdady said:
Have you tried mskip's fix??
http://forum.xda-developers.com/showthread.php?t=1727171
Click to expand...
Click to collapse
I want to do this but I somehow need to get the phone on. The buttons dont work.
Any luck?
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
brickeds3 said:
My phone got stuck booting, so I tried to install the omega rom. The install worked well, and I clicked "reboot." Now the phone won't turn on. I can't get to ODIN or recovery anymore.
Did you guys find any fixes?
Click to expand...
Click to collapse
What happened is that you flashed a rom that was meant for the international version of the S3 and your on the US version. The only fix I have found is to send it to mobiletechvideos.com. I did and they say they can fix it and maybe save my data I have on it ( I just sent it in)
My fingers are crossed for the data recovery but as far as the phone I am going to send it for a exchange anyway.
Welp, I'm sad to say I just did the same thing too. Should have read. I'm a stinkin noob at this. I installed the I9300 version on a US version phone. Has there been any more development on this? Is the hardware fried, or is there a fix through that mobiletechvideos.com that was mentioned? What was the outcome of that, Taygutta, if you don't mind me re-bringing back up a potentially painful topic?? This thread made me a little sick, since it's my brother's new phone (someone else that knew what they were doing rooted it for him but he didn't like the rom, so I thought I would help him find a few other options to try flashing.)
Anyway, any confirmation that I'm buying my brother a new phone (so I can emotionally prepare for the purchase) or are there some other options?
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
6uPMAH said:
There's one more thing you can try. There's a little device called a USB Jig. It was made for SGS-2 to clear the yellow triangle and reset flash counts in ODIN mode. It also puts your phone in ODIN mode by simply plugging it into the USB port of a powered down phone. Once in ODIN mode, you can reflash a stock ROM, recovery, etc. You can buy these for around $20 or less on the web.
If this does not work, I'm afraid nothing will.
Good luck.
Click to expand...
Click to collapse
Somewhere in the thread an answer exists. You are not the first to do this.
I think the jig is the best way.
Sent from my SPH-L710 using Tapatalk 2