So I am on my fourth ICS rom and haven't had any problems with a brick. I jumped on xda a today ans daw this http://www.xda-developers.com/android/determine-your-devices-hard-brick-risk-with-got-brickbug/
Now I download the app and it told me this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now is this due to a brick bug or just people doing something stupid?
As long as you follow OP directions and flash from el26 cwm kernel, you will be OK.
Sent from my SPH-D710 using Tapatalk
I'm staying away until ics is an official release, but that's just me being safe than sorry.
I see you flashed Venums latest rom. I tried it out last night but just wasn't feeling it. Any time you flash anything there is a chance of a brick. Keep that in mind and you will be fine. Do your homework check the md5 then flash. If you are not sure then don't flash and remember qbking77 probably has a youtube video already so watch it.
someguyatx said:
I see you flashed Venums latest rom. I tried it out last night but just wasn't feeling it. Any time you flash anything there is a chance of a brick. Keep that in mind and you will be fine. Do your homework check the md5 then flash. If you are not sure then don't flash and remember qbking77 probably has a youtube video already so watch it.
Click to expand...
Click to collapse
Yeah man I been flashing roms for over two years on 4 devices. Never bricked one yet.flashed four different ics roms without going back to the el26. I think ppl just bri k there for being stupid. Lol thanks to all of you
Sent from my SPH-D710 using Tapatalk 2
oscarthegrouch said:
I'm staying away until ics is an official release, but that's just me being safe than sorry.
Click to expand...
Click to collapse
I will tell you something about Samsung and there official releases. When I had my cappy they keep saying there will be an update for froyo and before you know it I was flashing GB and still no release. Lol
Sent from my SPH-D710 using Tapatalk 2
dfuse06 said:
Yeah man I been flashing roms for over two years on 4 devices. Never bricked one yet.flashed four different ics roms without going back to the el26. I think ppl just bri k there for being stupid. Lol thanks to all of you
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
I am glad your laughing. I guess when Google engineers ran into the bug they were doing something stupid? I guess when they had Samsung write new firmware for eMMC chips going into the GNex it was because they were doing something stupid. I guess when all the Kernel and recovery developers bricked their phones and they couldn't even be jtag'd they were doing something stupid. Actually technically when you develop you know their are risks, but this risk is not something anyone expected. It is a permenant bug that will always be with your phone, things will be done to avoid it. But the danger isn't going away. Even after the OTA, as we are finding out there is still the danger of the calls being made from CWM zips, etc.
Just keep hitting factory reset in ICS, quickest way to do it and it still may take a few tries. If you think its perfectly okay that the Galaxy Note was push an update that causes random bricks when people factory reset thats fine. But you can't tell them they were doing something stupid when Samsung never emailed them to say "Don't factory reset".
Its a hard cold fact that sooner or later one of the times mmc_erase() is called with the flag MMC_CAP_ERASE corruption will occur at the wearlevelfs level which can only be fixed by vendor specific commands not available to even repair centers.
4 roms? I did a few the wrong way. But 4 roms altogether? Many of us are around 30 and thats unique not reflashes. Probably around 200 total flashes myself just for ICS on this device. I am home on CM9 now which means only a couple a week from now on i think.
RainMotorsports said:
I am glad your laughing. I guess when Google engineers ran into the bug they were doing something stupid? I guess when they had Samsung write new firmware for eMMC chips going into the GNex it was because they were doing something stupid. I guess when all the Kernel and recovery developers bricked their phones and they couldn't even be jtag'd they were doing something stupid. Actually technically when you develop you know their are risks, but this risk is not something anyone expected. It is a permenant bug that will always be with your phone, things will be done to avoid it. But the danger isn't going away. Even after the OTA, as we are finding out there is still the danger of the calls being made from CWM zips, etc.
Just keep hitting factory reset in ICS, quickest way to do it and it still may take a few tries. If you think its perfectly okay that the Galaxy Note was push an update that causes random bricks when people factory reset thats fine. But you can't tell them they were doing something stupid when Samsung never emailed them to say "Don't factory reset".
Its a hard cold fact that sooner or later one of the times mmc_erase() is called with the flag MMC_CAP_ERASE corruption will occur at the wearlevelfs level which can only be fixed by vendor specific commands not available to even repair centers.
4 roms? I did a few the wrong way. But 4 roms altogether? Many of us are around 30 and thats unique not reflashes. Probably around 200 total flashes myself just for ICS on this device. I am home on CM9 now which means only a couple a week from now on i think.
Click to expand...
Click to collapse
I hear you dude.I am just saying if this is a known bug and ppl are still flashing ROMs with high risk of bricking. That is stupid. Not everyone has the money to get another phone if they brick. But it is the way the game goes. Thanks for the info I didnt know it was really all that bad. Looks like I will be going back ti el26 everytime I flash.
Edit and that still sucks,and this only ics? is GB safe?
Sent from my SPH-D710 using Tapatalk 2
Even though the app reports bricking probabilities, you shouldn't assume any firmware rev is safe. Per the EMMC lockup discussion thread, fwrev 0x25 (which brickbug reports as "probably safe") has a separate data corruption issue. Until there's a definite solution, if you're flashing ICS ROMs, you should follow the forum instructions and flash back down to EL26 w/ CWM and then back up or you're risking a brick.
EDIT: Flashing to an ICS ROM from EL26 w/ CWM is as safe as any regular flashing operation though, and speaking as someone that dragged their feet to flash up to ICS - it's worth taking the leap now if you're okay with a couple of hiccups (Blu Kuban here). Incredible experience and fairly easy to go back and forth if you take nandroid and titanium backups.
One again thanks to all for all the info. I had some phones that I tought were just unbrick able. I use to try everything on my cappy and the jig what the bomb. lol
Sent from my SPH-D710 using Tapatalk 2
dfuse06 said:
I hear you dude.I am just saying if this is a known bug and ppl are still flashing ROMs with high risk of bricking. That is stupid. Not everyone has the money to get another phone if they brick. But it is the way the game goes. Thanks for the info I didnt know it was really all that bad. Looks like I will be going back ti el26 everytime I flash.
Edit and that still sucks,and this only ics? is GB safe?
Click to expand...
Click to collapse
Was talking to Chris41G last night he detailed some of the paths that were likely to brick still. SFHUB has been working on ways for developers to make their Recoveries and CWM Zips safe. Even with recoveries that are safe to wipe with some zips can still trigger the bug.
As far as GB goes, Calk's format all has a known safe updater binary. The cap erase flasg was not enabled on our GB kernel but as was also found out is still apparently safe if enabled. I cant remember what command it is but on ICS something like makeext4fs() is now called and is part of the problem. But only code compiled against the library that uses that even calls it.
We were all messing with leaks and its all our fault if something happens. We all have instructions and if someone doesn't read or follow them then yeah that is stupid. However the Galaxy Note was pushed ICS OTA without a workaround (which the GS2 i9100 has) and people were able to brick by just factory resetting which seems to be one of the easiest ways.
Googles engineer Ken Sumrall said the area for the /Data partition being the one to go was because it was written to more often, more chances. This thread - http://forum.xda-developers.com/showthread.php?t=1644364 has more information than I can even explain but may also be a hard read. They found the problem with the eMMC firmware while developing the Gnex, the prototypes had the same eMMC firmware as our phone. This can be update at the factory but not by the end user. The corruption occurs at a lower level than is presented as writable storage and can not be fixed by JTAGing firmware. It is possible for some super bricks to be partitioned around, others not.
ODIN is safe too by the way so if your ODINing your leaks no real worries there, there was some question as to calls made by Mobile ODIN which i flashed the EL26 kernel probably 25+ times with.
RainMotorsports said:
Was talking to Chris41G last night he detailed some of the paths that were likely to brick still. SFHUB has been working on ways for developers to make their Recoveries and CWM Zips safe. Even with recoveries that are safe to wipe with some zips can still trigger the bug.
As far as GB goes, Calk's format all has a known safe updater binary. The cap erase flasg was not enabled on our GB kernel but as was also found out is still apparently safe if enabled. I cant remember what command it is but on ICS something like makeext4fs() is now called and is part of the problem. But only code compiled against the library that uses that even calls it.
We were all messing with leaks and its all our fault if something happens. We all have instructions and if someone doesn't read or follow them then yeah that is stupid. However the Galaxy Note was pushed ICS OTA without a workaround (which the GS2 i9100 has) and people were able to brick by just factory resetting which seems to be one of the easiest ways.
Googles engineer Ken Sumrall said the area for the /Data partition being the one to go was because it was written to more often, more chances. This thread - http://forum.xda-developers.com/showthread.php?t=1644364 has more information than I can even explain but may also be a hard read. They found the problem with the eMMC firmware while developing the Gnex, the prototypes had the same eMMC firmware as our phone. This can be update at the factory but not by the end user. The corruption occurs at a lower level than is presented as writable storage and can not be fixed by JTAGing firmware. It is possible for some super bricks to be partitioned around, others not.
ODIN is safe too by the way so if your ODINing your leaks no real worries there, there was some question as to calls made by Mobile ODIN which i flashed the EL26 kernel probably 25+ times with.
Click to expand...
Click to collapse
Yeah i just bought moble odin pro
Sent from my SPH-D710 using Tapatalk 2
dfuse06 said:
Yeah man I been flashing roms for over two years on 4 devices. Never bricked one yet.flashed four different ics roms without going back to the el26. I think ppl just bri k there for being stupid. Lol thanks to all of you
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Ive bricked 4x times and im glad i did because now i can go step by step with someone that might be going through the same thing and help restore their phone..what if youre a tester for a dev? Testing non stable roms? I dont appreciate this comment and im sure the majority of the community doesnt either
manufan721 said:
Ive bricked 4x times and im glad i did because now i can go step by step with someone that might be going through the same thing and help restore their phone..what if youre a tester for a dev? Testing non stable roms? I dont appreciate this comment and im sure the majority of the community doesnt either
Click to expand...
Click to collapse
[/url][/IMG]
manufan721 said:
Ive bricked 4x times and im glad i did because now i can go step by step with someone that might be going through the same thing and help restore their phone..what if youre a tester for a dev? Testing non stable roms? I dont appreciate this comment and im sure the majority of the community doesnt either
Click to expand...
Click to collapse
well dude this comment was not at you and when I said something stupid I mean stupid I had a cappy has my 1st android phone and I flashed rom from other phone and just doing stupid stuff,but we had home made jigs that unbrick anything. It didn't matter, plus a dev should test a non stable rom them self. Any mod, theme, I mean anything I post I test myself to ensure nothing well happen to anyone's phone.Sorry if I got you panties in a bunch'but come on dude read every post you took this the wrong way'but yeah no hard feeling man. Good luck to you, and not bricking your phone again.
rwright64 said:
[/url][/IMG]
Click to expand...
Click to collapse
Lmfao
Sent from my SPH-D710 using Tapatalk 2
dfuse06 said:
well dude this comment was not at you and when I said something stupid I mean stupid I had a cappy has my 1st android phone and I flashed rom from other phone and just doing stupid stuff,but we had home made jigs that unbrick anything. It didn't matter, plus a dev should test a non stable rom them self. Any mod, theme, I mean anything I post I test myself to ensure nothing well happen to anyone's phone.Sorry if I got you panties in a bunch'but come on dude read every post you took this the wrong way'but yeah no hard feeling man. Good luck to you, and not bricking your phone again.
Click to expand...
Click to collapse
Good answer bro..no hard feelings on my end either.. if i did take this the wrong way then i apologize for it..
Related
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
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
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!!!
Couldnt find threads related to my specific device so i made it.
After installing a custom rom on my tmobile gn2 (hyperdroid pegasus) i realized that my SIM card wasnt being detected. Having run into this problem before i decided to use the gn2 toolkit to re-flash a stock rom and start from scratch, which worked and allowed my sim card to be detected use my mobile network (TMOBILE USA)
Only after installing hyperdroid and trying to reflash the stock rom, the custom hyperdroid rom would stay on the device after multiple attempts! Being clever, i decided to download and reflash the rom using ODIN only in download mode which worked and now the device is running the Samsung Official build branded with tmobile but will not boot past the samsung logo (one of two that i see appear upon boot)
Looking at a thread for the original Note 1, do i assume correctly that my phone is now bricked? If so, anyone else know of an absolute md5/tar image i can use that can get me back to factory out of the box, i bought this phone unsubsidized over the iphone5 because i wanted something that woulc pack a wallop. Now im just walloping myself for wasting not just 100 dollars more but 750 dollars on a device, running an os, being supported by everyone who wants their hands on it, in a community that will chew you out if you ask incorrectly.
So im whining yes but i could use some advice. Sure im a noob but so were you once, all i reall ask for is some compassion. thanks...
Did you try factory reset?
Sent from my SGH-T889 using xda premium
Try to use odin root66 for prerooted or stock
After odin do factory reset
Sent from my SGH-T889 using xda premium
Thanks for replies, really appreciated
I cannot begin to explain this ordeal i had with my note 2. Thanks for the replies as of this point however, actually directions that i took in figuring it all out and getting my phone back to factory defaults...
So to elaborate, my N2 has been rooted for a few days and i decided to install a custom ROM, which disabled or didn't support my SIM. Trying to undo the flash and go back to a ROM i was using via ROM manager, i realized it could not be undone. Every time i tired to reflash a(ny) zip from my device using rom manager i was still booting with the custom malfunctioning rom (Hyperdroid Pegasus)
After realizing that i couldn't undo the flash of the custom rom via ROM manager, the galaxy note 2 toolkit or via ODIN straight up, i somehow ended up bricking my phone using an image i got off of samsung-updates (which i downloaded using the galaxy n2 toolkit). In bricking i mean it would power on and boot into the samsung whirlpool, then the tmobile 4g accelerated android, and then to a glowing samsung logo and didn't progress from there.
Doing some research i noticed that there was a more recent image version for my specific device (jan 5 2013) downloaded it and gave that a try, flashed it via ODIN (because by the time it was bricked Download mode / Odin mode and ODIN 3.07 for windows was my only available option!) and launched up my gn2... ONLY to find it booting to the animations and then looping them! WTF?!
So more research and i got to a recovery mode, wiped my data and finally voila. (Even samsung support couldn't support this...)
No discredit to the Hyperdroid Rom, I'm sure it works for a lot of people out there but i guess it doesn't like my tmobile note 2 sgh-t889.
I just hoped if anyone else ran into the same problem, download the image from samsung-updates.com, the latest of course! Then, (if you can boot into download mode that is) use ODIN (i used version 3.07) to load the image you got off samsung-updates (OSM will take more or less 5 minutes to check the md5 package so don't panic)
If your lucky you shouldn't have to do anything else, but if you get into a weird situation when you can't get past the boot animation screens, boot into recovery mode (which i THINK is hold down UP, POWER, AND THE HOME KEY as it powers up) and select to CLEAR WIPE DATA or FACTORY RESET.
Hopefully after wiping you should have successfully re-flashed a "bricked" galaxy note 2 that won't boot past the animation screens.
Thanks for reading! Im here to answer any questions or help, maybe i won't play with custom rome anymore but id sure like to start building my own!
Rhiannon224 said:
Did you try factory reset?
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
jay661972 said:
Try to use odin root66 for prerooted or stock
After odin do factory reset
Sent from my SGH-T889 using xda premium
Click to expand...
Click to collapse
To both you guys, i just want to say i elaborated on your answers for the benefit of helping someone like me who craves detail. No offense to you guys, but i was racketing with Samsung about this and driving their people nuts! the solution had came to me before i saw your replies so I'm just glad i took the right path in it all and i guess i admit i lost faith in XDA for a second there. anyways :good:
So wait, in all that flashing and reflashing and messing with Odin, you hadn't done a factory reset yet? Isn't that the first step almost any ROM dev(or even any normal flashoholic on these forums) will tell you to take?
shinkinrui said:
So wait, in all that flashing and reflashing and messing with Odin, you hadn't done a factory reset yet? Isn't that the first step almost any ROM dev(or even any normal flashoholic on these forums) will tell you to take?
Click to expand...
Click to collapse
I give you permission to call me a newb, Okay? Feel better and call me in the morning.
Lol no need to get offended man It's a learning experience.
I only said something because you seemed so bitter about your perceived lack of support around here and even went so far as to say you almost lost faith in xda, yet it seems like you didn't do step 1.
At any rate, glad your note 2 is revived
Sent from my SGH-T989 using xda app-developers app
2ruen0 said:
I give you permission to call me a newb, Okay? Feel better and call me in the morning.
Click to expand...
Click to collapse
This seemed fitting...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Still, good on you for learning a few things and getting your phone back in action.
shinkinrui said:
Lol no need to get offended man It's a learning experience.
I only said something because you seemed so bitter about your perceived lack of support around here and even went so far as to say you almost lost faith in xda, yet it seems like you didn't do step 1.
At any rate, glad your note 2 is revived
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Darkshado said:
This seemed fitting...
Still, good on you for learning a few things and getting your phone back in action.
Click to expand...
Click to collapse
Lol, funny picture. Yes i almost lost faith but obviously you guys came through. I am one of 4 million people who did or didnt follow the rules but thats a good thing, i think the tmobile jellybean community needs as much help as it can get right now and if it takes making a tiny mistake good for us.
actually shinkinrui, i wasnt sure if you were trying to troll me or trying to remind me that this forum is for the leet and the leet only. I understand the work devs go through, but its still a community that needs to thrive, not be put off or put down.
Neither, actually. I was annoyed at the implication that it was this community's fault you went through your ordeal. Like someone blaming their cable company for their cable not working when they just didn't change the input on their TV.
And my post didn't insult you, it pointed out your mistake. Big difference
Thanks !!!
2ruen0 said:
I cannot begin to explain this ordeal i had with my note 2. Thanks for the replies as of this point however, actually directions that i took in figuring it all out and getting my phone back to factory defaults...
So to elaborate, my N2 has been rooted for a few days and i decided to install a custom ROM, which disabled or didn't support my SIM. Trying to undo the flash and go back to a ROM i was using via ROM manager, i realized it could not be undone. Every time i tired to reflash a(ny) zip from my device using rom manager i was still booting with the custom malfunctioning rom (Hyperdroid Pegasus)
After realizing that i couldn't undo the flash of the custom rom via ROM manager, the galaxy note 2 toolkit or via ODIN straight up, i somehow ended up bricking my phone using an image i got off of samsung-updates (which i downloaded using the galaxy n2 toolkit). In bricking i mean it would power on and boot into the samsung whirlpool, then the tmobile 4g accelerated android, and then to a glowing samsung logo and didn't progress from there.
Doing some research i noticed that there was a more recent image version for my specific device (jan 5 2013) downloaded it and gave that a try, flashed it via ODIN (because by the time it was bricked Download mode / Odin mode and ODIN 3.07 for windows was my only available option!) and launched up my gn2... ONLY to find it booting to the animations and then looping them! WTF?!
So more research and i got to a recovery mode, wiped my data and finally voila. (Even samsung support couldn't support this...)
No discredit to the Hyperdroid Rom, I'm sure it works for a lot of people out there but i guess it doesn't like my tmobile note 2 sgh-t889.
I just hoped if anyone else ran into the same problem, download the image from samsung-updates.com, the latest of course! Then, (if you can boot into download mode that is) use ODIN (i used version 3.07) to load the image you got off samsung-updates (OSM will take more or less 5 minutes to check the md5 package so don't panic)
If your lucky you shouldn't have to do anything else, but if you get into a weird situation when you can't get past the boot animation screens, boot into recovery mode (which i THINK is hold down UP, POWER, AND THE HOME KEY as it powers up) and select to CLEAR WIPE DATA or FACTORY RESET.
Hopefully after wiping you should have successfully re-flashed a "bricked" galaxy note 2 that won't boot past the animation screens.
Thanks for reading! Im here to answer any questions or help, maybe i won't play with custom rome anymore but id sure like to start building my own!
Click to expand...
Click to collapse
Thamks !!!! alot man this post help me:highfive:
"wiping data / factory install" selection worked for me
Thanks for this tip!
I was stuck on the Samsung animation logo after flashing to 4.1.1 so that I could unlock my phone. :crying:
I went to the recovery mode and hit the "wipe data / factory install" selection and it rebooted into the 4.1.1 ROM successfully.
Awesome! :laugh:
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
PLEASE HELPME THIS IS MY CASE: i tryied to root my sprint 4g epic GS2 , i did it throught ODIN i attached the PDA file my KERNEL is FL24 and when i finished the process throught ODIN The phone reebot with a yellow triangle an it can not access to the operation system , I just can open de downloading mode and the recovery mode
iim not even know if the rooted was succesful completed , so i need som help if there is any file that u can put in the memory and try to install throught the recover mode cuz i downloaded the original firmware and ODIN doesnt recognize my phone now really scare about this phone its not even my phone is a friend's phone :crying:
What file did you flash?
Ok, calm down. If you can boot into recovery you are ok. Here's what you do. Download chris41g's el26 stock cwm(tar). Google it. Boot into download mode. Flash the kernel through Odin. When it says pass and reboots, pull the battery. Reinsert and boot into recovery. You will be in cwm now. Do the cache, dalvik wipe, then flash the ROM(E4GT only, since in assuming that's the phone you have) you have saved in your phone's ext or internal drive, and when it's done, reboot, and you should be good. If you didn't save the rom, you'll have to mount the usb storage and load it through cwm. Search the threads for that too. Good luck
Sent from my SPH-D710 using xda premium
---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------
BluesRulez said:
What file did you flash?
Click to expand...
Click to collapse
Hey Blues, good to see ya! :beer: let me know if I missed something
Sent from my SPH-D710 using xda premium
I would have just suggested to flash a one click restore to get the phone back into an operational state. Minimal steps since the op seems to be in panic mode.
Hard to tell what's happened in the few hours since the original post.. would be interested in what transpired from the "oh ****, I screwed up" moment..
MoHoGalore said:
I would have just suggested to flash a one click restore to get the phone back into an operational state. Minimal steps since the op seems to be in panic mode.
Hard to tell what's happened in the few hours since the original post.. would be interested in what transpired from the "oh ****, I screwed up" moment..
Click to expand...
Click to collapse
Usually goes something like this "oh ****, I screwed up" anicface: :messes around with everything possible without researching first: "**** me, I killed it now"
☆SoA: Son's of Android™☆
I like to break stuff!
-EViL-KoNCEPTz- said:
Usually goes something like this "oh ****, I screwed up" anicface: :messes around with everything possible without researching first: "**** me, I killed it now"
☆SoA: Son's of Android™☆
I like to break stuff!
Click to expand...
Click to collapse
Exactly like that too I bet. Obviously didn't read enough BEFORE messing around with it! But I guess I'm a nice guy and wanted to calm the op down. They did seem in serious panic mode. Lol:beer: anyone?
Sent from my SPH-D710 using xda premium
How about calming down. Not shouting and tell us exactly what Odin file you say you flashed and how. Sounds like you tried to flash just a kernel -FL24 via PC odin. Yes you'll get that yellow triangle.
Also sounds like you flashed a kenel that was not compatible with the Android version you were on (you ROM version) hence the not booting to ROM
Simple fix.
Download a Full Restore Odin One-click ROM. They can be found in RWilco's repository http://forum.xda-developers.com/showthread.php?t=1903252
Read carefully how to use it to flash the entire ROM. It's dead simple.
Then go back and do a whole LOT of reading about how to update and modify this phone or you're going to paperweight a device! Your posts sounds like someone who saw an operation on a tv show once then tried to do an appendectomy on someone and freaked out that it didn't work how you thought it would.
Patience, read, learn. Search read some more and patience will get you far.
leaderbuilder said:
How about calming down. Not shouting and tell us exactly what Odin file you say you flashed and how. Sounds like you tried to flash just a kernel -FL24 via PC odin. Yes you'll get that yellow triangle.
Also sounds like you flashed a kenel that was not compatible with the Android version you were on (you ROM version) hence the not booting to ROM
Simple fix.
Download a Full Restore Odin One-click ROM. They can be found in RWilco's repository http://forum.xda-developers.com/showthread.php?t=1903252
Read carefully how to use it to flash the entire ROM. It's dead simple.
Then go back and do a whole LOT of reading about how to update and modify this phone or you're going to paperweight a device! Your posts sounds like someone who saw an operation on a tv show once then tried to do an appendectomy on someone and freaked out that it didn't work how you thought it would.
Patience, read, learn. Search read some more and patience will get you far.
Click to expand...
Click to collapse
Ha, I already tried to calm him/her down, lol. The op was hours ago, so they either calmed down and actually read what we wrote or some of the INCREDIBLY simple threads the guys here at XDA put together, or they have a nice expensive paperweight. Appendectomy comment was classic though. :beer: for that one. Maybe they stayed at a Holiday Inn Express last night.hmmmm
Sent from my SPH-D710 using xda premium
jdsingle76 said:
Ha, I already tried to calm him/her down, lol. The op was hours ago, so they either calmed down and actually read what we wrote or some of the INCREDIBLY simple threads the guys here at XDA put together, or they have a nice expensive paperweight. Appendectomy comment was classic though. :beer: for that one. Maybe they stayed at a Holiday Inn Express last night.hmmmm
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
If you ever stay at a seedy motel and wake up in a bathtub full of ice, the missing kidney is the least of your worries. I hear hepatitis is a real *****.
☆SoA: Son's of Android™☆
I like to break stuff!
Op said his phone is no longer recognized by Odin which makes me think he flashed something he shouldn't have.
===================
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
-EViL-KoNCEPTz- said:
If you ever stay at a seedy motel and wake up in a bathtub full of ice, the missing kidney is the least of your worries. I hear hepatitis is a real *****.
☆SoA: Son's of Android™☆
I like to break stuff!
Click to expand...
Click to collapse
Ha, you must have read my Tijuana comment in the pub. Yes, I would have to agree with you, hep would suck!
Sent from my SPH-D710 using xda premium
jdsingle76 said:
Ha, you must have read my Tijuana comment in the pub. Yes, I would have to agree with you, hep would suck!
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Lol the appendectomy comment reminded me of a friend of mine who had a kidney stolen while he was in Mexico and when he got to the hospital they got him stable but he was in icu for about a month. Well he found out the scalpel hadn't been sterilized and he ended up with tetanus, hep c, and some other weird disease.
☆SoA: Son's of Android™☆
I like to break stuff!
jdsingle76 said:
ha, i already tried to calm him/her down, lol. The op was hours ago, so they either calmed down and actually read what we wrote or some of the incredibly simple threads the guys here at xda put together, or they have a nice expensive paperweight. Appendectomy comment was classic though. :beer: For that one. Maybe they stayed at a holiday inn express last night.hmmmm
sent from my sph-d710 using xda premium
Click to expand...
Click to collapse
thank you for ur help but there is a problem odin doesn't recognize my phone , and i tryied with othe phone (skyrocket sgs2 ) and it does recognize that , that why i cant flash it with odin, or if may i do it throught recovery mode ?
leaderbuilder said:
How about calming down. Not shouting and tell us exactly what Odin file you say you flashed and how. Sounds like you tried to flash just a kernel -FL24 via PC odin. Yes you'll get that yellow triangle.
Also sounds like you flashed a kenel that was not compatible with the Android version you were on (you ROM version) hence the not booting to ROM
Simple fix.
Download a Full Restore Odin One-click ROM. They can be found in RWilco's repository http://forum.xda-developers.com/showthread.php?t=1903252
Read carefully how to use it to flash the entire ROM. It's dead simple.
Then go back and do a whole LOT of reading about how to update and modify this phone or you're going to paperweight a device! Your posts sounds like someone who saw an operation on a tv show once then tried to do an appendectomy on someone and freaked out that it didn't work how you thought it would.
Patience, read, learn. Search read some more and patience will get you far.
Click to expand...
Click to collapse
thank you for ur help but there is a problem odin doesn't recognize my phone , and i tryied with othe phone (skyrocket sgs2 ) and it does recognize that , that why i cant flash it with odin, or if may i do it throught recovery mode ?
leaderbuilder said:
How about calming down. Not shouting and tell us exactly what Odin file you say you flashed and how. Sounds like you tried to flash just a kernel -FL24 via PC odin. Yes you'll get that yellow triangle.
Also sounds like you flashed a kenel that was not compatible with the Android version you were on (you ROM version) hence the not booting to ROM
Simple fix.
Download a Full Restore Odin One-click ROM. They can be found in RWilco's repository http://forum.xda-developers.com/showthread.php?t=1903252
Read carefully how to use it to flash the entire ROM. It's dead simple.
Then go back and do a whole LOT of reading about how to update and modify this phone or you're going to paperweight a device! Your posts sounds like someone who saw an operation on a tv show once then tried to do an appendectomy on someone and freaked out that it didn't work how you thought it would.
Patience, read, learn. Search read some more and patience will get you far.
Click to expand...
Click to collapse
thank you for ur help but there is a problem odin doesn't recognize my phone , and i tryied with othe phone (skyrocket sgs2 ) and it does recognize that , that why i cant flash it with odin, or if may i do it throught recovery mode ?
THETWINS1990 said:
thank you for ur help but there is a problem odin doesn't recognize my phone , and i tryied with othe phone (skyrocket sgs2 ) and it does recognize that , that why i cant flash it with odin, or if may i do it throught recovery mode ?
Click to expand...
Click to collapse
Do you get any response from a pc when you plug it in? The only options I see is MAYBE trying abd but it seems like you're in need of a jtag service by mobiletech or someone like that.
HI
jdsingle76 said:
Ok, calm down. If you can boot into recovery you are ok. Here's what you do. Download chris41g's el26 stock cwm(tar). Google it. Boot into download mode. Flash the kernel through Odin. When it says pass and reboots, pull the battery. Reinsert and boot into recovery. You will be in cwm now. Do the cache, dalvik wipe, then flash the ROM(E4GT only, since in assuming that's the phone you have) you have saved in your phone's ext or internal drive, and when it's done, reboot, and you should be good. If you didn't save the rom, you'll have to mount the usb storage and load it through cwm. Search the threads for that too. Good luck
Sent from my SPH-D710 using xda premium
---------- Post added at 09:03 PM ---------- Previous post was at 09:02 PM ----------
Hey Blues, good to see ya! :beer: let me know if I missed something
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
thank you for ur help but there is a problem odin doesn't recognize my phone , and i tryied with othe phone (skyrocket sgs2 ) and it does recognize that , that why i cant flash it with odin, or if may i do it throught recovery mode ?
there is not response when i plug it in
MoHoGalore said:
Do you get any response from a pc when you plug it in? The only options I see is MAYBE trying abd but it seems like you're in need of a jtag service by mobiletech or someone like that.
Click to expand...
Click to collapse
there is not response when i plug it in!! can u send me a email or a private message so u can explain me better
THETWINS1990 said:
there is not response when i plug it in!! can u send me a email or a private message so u can explain me better
Click to expand...
Click to collapse
There is really nothing I can suggest at this point other than you need to look up mobiletech jtag service if you're willing to invest in fixing the phone. Even then it's not a guaranteed fix.
BluesRulez said:
What file did you flash?
Click to expand...
Click to collapse
i flash a file named : SPH-D710_Zedomax_Kernel.tar throught ODIN after completed it showed the yellow triangle and thats all happended then ,,
if u know spanish this is the web site where i got the information to root it
http://yosoyandroid.com/2011/09/tutorial-root-samsung-epic-touch-4g-galaxy-s2-sprint/