Develop Bugs

Problems with my SGS 2

Can someone please help me out here. I just got my SGS 2 for T-Mobile a few days ago, as I'm coming from a Sensation. The phone is rooted and I installed Juggernaut and after a few days my phone started to reboot constantly and say that network is unavailable. I would reboot into recovery and wipe and it restarted and same thing happened. I then began to reinstall ROM and it would work for a bit, then same thing would happen. I then formatted system, data, and reinstalled ROM, same problem. I then installed Beast ROM thinking it might be ROM, but same thing happened with this one. I have wiped over and over again and same problem. I got a new sim card and same thing. I re-rooted and same problems. I installed stock ROM, downloaded new stock ROM, upgraded modem, and same problems. I remove sd card, same problem. I am out of ideas and options so someone please assist me with this matter as I've never had this problem before.

Sounds like a faulty device. I'd take it back!
Sent from my SGH-T989 using xda premium

This was happening to my first SGS2 as well. It was within the 14 day buyers remorse thing from Tmobile and I was able to exchange it for a brand new one. Haven't had any issues since.
Sent from my SGH-T989 using xda premium

Well the problem with that is that I bought it off of someone. Everything had been working fine until I applied a custom ROM. I will continue to mess around with it to find a solution.
Sent from my iCrap killer

Try the new stock and see if it continues.

cbrvnm said:
Well the problem with that is that I bought it off of someone. Everything had been working fine until I applied a custom ROM. I will continue to mess around with it to find a solution.
Sent from my iCrap killer
Click to expand...
Click to collapse
Just call T-Mobile and get a warranty exchange.
Powered by the SGSII....

or try a different rom , i had those issues with juggernaut also

tigerz0202 said:
or try a different rom , i had those issues with juggernaut also
Click to expand...
Click to collapse
I did try different ROMs. I tried beast's, stock, and new stock one also, and it still continued.
Sent from my iCrap killer

cbrvnm said:
I did try different ROMs. I tried beast's, stock, and new stock one also, and it still continued.
Sent from my iCrap killer
Click to expand...
Click to collapse
well do a warranty exchange then i had the same thing happen on my first phone also ,all i ran on my first phone was stock rom and juggernaut and it kept doing it so i had to return it

tigerz0202 said:
well do a warranty exchange then i had the same thing happen on my first phone also ,all i ran on my first phone was stock rom and juggernaut and it kept doing it so i had to return it
Click to expand...
Click to collapse
I'll try out a few more things and if that doesn't work I'll exchange it. Thanks.
Sent from my iCrap killer

For the rest of u that had the same problem, were u rooted and running a custom ROM?
Sent from my iCrap killer

Nop its the phones that come faulty I had to get mines replaced because of the same problem and even the new upgrade didn't help it. Now the new one I got two days ago it's working like a champ and on beastmod
Sent from my SGH-T989 using XDA App

dtddemon said:
Nop its the phones that come faulty I had to get mines replaced because of the same problem and even the new upgrade didn't help it. Now the new one I got two days ago it's working like a champ and on beastmod
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Ok. Thanks.
Sent from my iCrap killer

Well I think I got it working as it hasn't rebooted or lost signal today. I redid root, upgraded modem to new one, and reformatted sdcard. I rebooted the phone several times without problem, but I haven't tried wiping cache/dalvich as I'm kinda scared that this might cause some problems again but when I decide to I hope nothing happens.
Sent from my iCrap killer

cbrvnm said:
Well I think I got it working as it hasn't rebooted or lost signal today. I redid root, upgraded modem to new one, and reformatted sdcard. I rebooted the phone several times without problem, but I haven't tried wiping cache/dalvich as I'm kinda scared that this might cause some problems again but when I decide to I hope nothing happens.
Sent from my iCrap killer
Click to expand...
Click to collapse
Nevermind. Today the phone began to reboot once again and I called customer service and basically I have to go through some steps before they can replace it. So I'll see how that goes.

Did u fix.permission
Sent from my SGH-T989 using XDA App

Hey dude, let me offer you a bit of advice. Even if you bought the phone off some guy, you can still get Tmobile to send you a new one through the warranty.... just don't mention where you bought it from. What you have to do is log on to your Tmobile account and verify that under "My Device" it shows you using a GS2. This means their system shows you using that phone. Then contact their customer service through the chat, and just say that you are having a problem with the phone, blah blah blah. They shouldn't ask you where you bought it, and they should send you a new one with a return label to send this one back. Just make sure that it's stock and unrooted. Hope this helps.

Well I will be getting a replacement phone through warranty exchange afterall. Hopefully this new one works out well. Thanks everyone for ur input.
Sent from my iCrap killer

Ok, so I got a replacement phone and bought another one. I can root the phone and install roms, but no matter what rom I use, I always get no network available and constant reboots after a reboot. I have wiped completely, formated sd card and same problems. I have never had this happen on any previous phone. Does anyone have any ideas or suggestions cuz I'm completely lost on what to do. :banghead:
Sent from my iCrap killer

Very similar experience yesterday for me. Zero data, it wont read any sim card. Getting my 3rd replacement within a week.

[Q] How to unbrick? (Blue LED of death)

I pretty much already know the answer - JTAG. I'm just hoping for a little bit of HOPE. Are there any other possible ways of me unbricking it with a blue LED of death?
No USB recognition, no Download mode, no recovery.
I was already on AOKP Build 30, I was getting forcecloses because I went from Build 29 to 30 without wiping data, so I used Mobile Odin for EL26 kernel, did a full wipe on data/cache, flashed AOKP Build 30, flashed Gapps, then I did a reboot. It rebooted onto the Galaxy SII screen with the yellow triangle, then it went away and rebooted again to come to the Blue LED of death and doesn't go away until a battery pull.
Apparently a USB jig won't work.
I can take it into Sprint (I have a warranty), but what should I tell them? Would they charge me for a new phone, and would I get it right away?

hrffd said:
I pretty much already know the answer - JTAG. I'm just hoping for a little bit of HOPE. Are there any other possible ways of me unbricking it with a blue LED of death?
No USB recognition, no Download mode, no recovery.
I was already on AOKP Build 30, I was getting forcecloses because I went from Build 29 to 30 without wiping data, so I used Mobile Odin for EL26 kernel, did a full wipe on data/cache, flashed AOKP Build 30, flashed Gapps, then I did a reboot. It rebooted onto the Galaxy SII screen with the yellow triangle, then it went away and rebooted again to come to the Blue LED of death and doesn't go away until a battery pull.
Apparently a USB jig won't work.
I can take it into Sprint (I have a warranty), but what should I tell them? Would they charge me for a new phone, and would I get it right away?
Click to expand...
Click to collapse
I think you may be hosed but if you have the jig I'd definitely give it a shot (just in case). If that doesn't work you can take it into Sprint. If I remember right with the warranty if they can repair it there's no charge, if they need to send you a new device it's a $100 deductible. Most people just say it quit working on them without offering an explanation, seems to work most of the time.
Good luck!

Apparently JTAG is not going to work either. Something seems to be actually destroying the MMC chip when you mess with ICS and custom recoveries.

sputnik767 said:
Apparently JTAG is not going to work either. Something seems to be actually destroying the MMC chip when you mess with ICS and custom recoveries.
Click to expand...
Click to collapse
JTAG has been able to recover some hard bricks. I think it depends on the extent of the damage.
Sent from my SPH-D710 using Tapatalk

Dchibro said:
JTAG has been able to recover some hard bricks. I think it depends on the extent of the damage.
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
Have not heard of Jtag bringing anyone back from these bricks though.. Also there is a guy in the thread above yours... right before I posted that had a similar issue with AOKP Build30... Hope there is no problem with that rom..

playya said:
Also there is a guy in the thread above yours... right before I posted that had a similar issue with AOKP Build30... Hope there is no problem with that rom..
Click to expand...
Click to collapse
Ya, Me too.

hrffd said:
I pretty much already know the answer - JTAG. I'm just hoping for a little bit of HOPE. Are there any other possible ways of me unbricking it with a blue LED of death?
No USB recognition, no Download mode, no recovery.
I was already on AOKP Build 30, I was getting forcecloses because I went from Build 29 to 30 without wiping data, so I used Mobile Odin for EL26 kernel, did a full wipe on data/cache, flashed AOKP Build 30, flashed Gapps, then I did a reboot. It rebooted onto the Galaxy SII screen with the yellow triangle, then it went away and rebooted again to come to the Blue LED of death and doesn't go away until a battery pull.
Apparently a USB jig won't work.
I can take it into Sprint (I have a warranty), but what should I tell them? Would they charge me for a new phone, and would I get it right away?
Click to expand...
Click to collapse
I am not sure if you listed every step you did or were just summarizing.
Did you have the Yellow Triangle before any of this? I ask because nothing you did should have triggered the yellow triangle unless you had it before (or traditional ODIN'd CWM outside of the steps you listed)
Also, nothing you did should have prevented you from getting into ODIN DL mode. Even in the case of /data EMMC corruption, you can still get into ODIN DL mode.
Are you sure you can't get into ODIN DL mode? Pull the battery, then as you insert the battery press-and-hold Power+VolDown. If it is difficult to do the finger combination, then you are doing it right.
If you can get into ODIN DL mode, use the EL29 OneClick to get back to a known base. Use the Full version. If it hangs on data.img, then you have the /data emmc corruption and your only option is to get the unit replaced. JTAG will not work.

I have a quick question since we seem to be on the topic of bricks today. Has anybody bricked from making a nandroid in ICS recovery then using format all zip and then restoring from it. I am not referring to AOKP, CM9, etc rather stock or themed stock ROMs. I would NEVER recommend anyone to do this but I have made a few and restored them only wiping with format all zip. Am I tempting fate here or what? I thought this was narrowed down to wiping individual partitions or working from AOKP, CM9 recovery. Any thoughts here?
Sent from my Nexus S 4G using xda premium

JohnCorleone said:
I have a quick question since we seem to be on the topic of bricks today. Has anybody bricked from making a nandroid in ICS recovery then using format all zip and then restoring from it. I am not referring to AOKP, CM9, etc rather stock or themed stock ROMs. I would NEVER recommend anyone to do this but I have made a few and restored them only wiping with format all zip. Am I tempting fate here or what? I thought this was narrowed down to wiping individual partitions or working from AOKP, CM9 recovery. Any thoughts here?
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
the question is why are you wiping when restoring a nandroid back up?
You should be fine but the wiping step is pointless. The restore process should do it automatically.
Also yes, I have done a backup while in FC22 based CWM and recovered it from another FC22 based CWM install and it worked fine. No need to wipe at all.
Sent from my SPH-D710 using Tapatalk 2 Beta-5

@JohnCorleone,
There are other posters that agree with you that not all ICS ROMs have that problem. Epix4G has reminded me of this on occasion, but that was in regards to using Calk's ROMs and solutions. But I would also caution that this probably isn't a good idea for Joe Schmoe with a shiny new E4GT... maybe those that have been around longer or are willing to take that risk.
In my personal case I don't have the option for insurance and had to pay full price for this phone. I can't afford to brick it so I stick with the ODIN TARs for now. Maybe a few months down the road, once ICS is out and hopefully there's a better handle on this, I'll try some of the other options out there. Besides, coming from an Optimus S stock will do everything I need and more right now.

garwynn said:
@JohnCorleone,
In my personal case I don't have the option for insurance and had to pay full price for this phone. I can't afford to brick it so I stick with the ODIN TARs for now. Maybe a few months down the road, once ICS is out and hopefully there's a better handle on this, I'll try some of the other options out there. Besides, coming from an Optimus S stock will do everything I need and more right now.
Click to expand...
Click to collapse
Ya, I was using my phone on a different carrier, and bricked it. Talk about a ****ty realization. And coming from an Optimus, life is goooood eh? lol.

take the phone to sprint as long as they cant see anything your good to go. tell them you plugged it in to charge came back and smelt something funny and phone was real hot.

Same brick here, only blue led of death and no activity.
The phone is outside US so can't even get warranty / replacement. Can't get get mmc chip from Samsung which in this case is KLMAG4FEJA-A003

Jtag
sent from MY BAD A$$ ET4G

JTAG has failed over RISC

Disillusioned said:
Same brick here, only blue led of death and no activity.
The phone is outside US so can't even get warranty / replacement. Can't get get mmc chip from Samsung which in this case is KLMAG4FEJA-A003
Click to expand...
Click to collapse
Are you able to get ahold of a USB jig and see if this will somehow get it to come to life? If not, have you considered asking someone in the US to try and work with Samsung on your behalf?

Its pretty much dead at this point, time to replace the device. Even if a jig will trigger dl mode it will more than likely fail/hang at /data in odin.
Sent from my SPH-L710

-EViL-KoNCEPTz- said:
Its pretty much dead at this point, time to replace the device. Even if a jig will trigger dl mode it will more than likely fail/hang at /data in odin.
Sent from my SPH-L710
Click to expand...
Click to collapse
Yes, but if there is not a replace option getting that far would mean a modified pit will restore most functionality.
Sent from my SPH-D710 using Tapatalk 2

garwynn said:
Yes, but if there is not a replace option getting that far would mean a modified pit will restore most functionality.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
True, that's a 50/50 shot and worth the try if there's not a warranty or ins option, but if warranty is an option I'd personally grab a replacement instead of patching up a borked one just so I wouldn't run into a major issue from patching it back together and then be out of warranty and stuck with a total brick. I've also seen a few ppl be able to get to dl mode and it fail at data but the pit not work, probably user error but never know could just be totally fubar from the emmc bug
Sent from my SPH-L710

-EViL-KoNCEPTz- said:
True, that's a 50/50 shot and worth the try if there's not a warranty or ins option, but if warranty is an option I'd personally grab a replacement instead of patching up a borked one just so I wouldn't run into a major issue from patching it back together and then be out of warranty and stuck with a total brick. I've also seen a few ppl be able to get to dl mode and it fail at data but the pit not work, probably user error but never know could just be totally fubar from the emmc bug
Sent from my SPH-L710
Click to expand...
Click to collapse
It was def user error. In another post he said he loaded aokp from rujelus recovery:crying:

[Q] Phone randomly began to Reboot

Recently had a Galaxy S2 do something strange and I wanted to see if you guys can decipher what really happened because I have no idea what caused this to happen.
Let's start off with some other info....I was running:
CWM Touch Recovery 6.0.1.8
Cyanogenmod10 Nightly 111212
I simply turned it off once the battery was getting low and charged it, once it was done I turned it on and it made it to the lock screen and then restarted. It would continue do that indefinitely until I removed the battery. So I thought maybe something went wacky and got corrupted so I went back to stock....When Odin restarted it I made it to the Android Welcome screen and it restarted again just like before. So then I got really desperate and did a factory reset and erased all my personal data along with a different stock rom...ICS stock. Nope, it STILL restarts.
Additionally, T-Mobile is replacing said device for a new SGS2, but now I'm afraid to root it. Which is why I want to figure out what happened to it. I'm starting to have suspicions about my extended battery I bought because when this restarting issue began, I've been using them for a little over a week and I haven't done any cyanogenmod updates or flashes recently.

on another note, if I do decide to root again, which Recovery should I use? Preferably one that doesn't require me to use Darkside Superwipe or cache scripts. I'd prefer a Recovery that can do it without scripts. And if you could provide the link, that would be great. I don't care if it's touch or not.

I have been using TWRP for awhile now. Supposedly the built in Wipes are very effective. I like the look and aesthetics of it. I don't think the issue you experienced had anything to do with rooting and romming. I think you may have had a legitimate phone issue. Don't be afraid, just be prepared with backups and knowledge and such.

jcnbama said:
I have been using TWRP for awhile now. Supposedly the built in Wipes are very effective. I like the look and aesthetics of it. I don't think the issue you experienced had anything to do with rooting and romming. I think you may have had a legitimate phone issue. Don't be afraid, just be prepared with backups and knowledge and such.
Click to expand...
Click to collapse
Thanks for your input, As a precaution, do you think I should stop using the unofficial extended batteries? Because this started about 2 weeks after using them.

goku1910 said:
Thanks for your input, As a precaution, do you think I should stop using the unofficial extended batteries? Because this started about 2 weeks after using them.
Click to expand...
Click to collapse
I would go a while without using it and see if the issue persist. If it does then you'll have your answer. Either way.
Sent from my SGH-T989 using xda app-developers app

Sounds like your phone's power button is messed. You can try using a small flathead screwdriver and put it into the sides of the power button and rock it around a little bit. If that doesnt work i guess youre going to have to take it to a repair shop or if you have warranty just bring it back.
Sent from my SGH-T989D using xda app-developers app

Bricked?

So yesterday I was going to switch from PA to BeanStalk and ran into some problems, i restored back to PA.
Last night I went and downloaded LiquidSmooth I believe it is, went into recovery *cwm 6.0.2.7.* wiped data, cache, dalvik and formated system.. Installing the zip I ran into a status 7 error. I went to restore my nandroid from earlier in the day, my stable PA setup. No restore files could be found, internal, or external.
At this point I powered my phone off so take my micro sdcard out so I could download a rom through my laptop. While the rom was downloading I decided to go back to recovery to see if there was anything I was doing wrong there..I couldnt get to recovery. I couldnt get into download mode.. Plugging it in to the wall charger I wasnt even getting a charging light. I let it sit overnight on the charger and decided to start on it this morning..
Any button combo I do yields no result.. So I'm fearing this may be a toasted device.. If anyone has insight please let me know.. Much thanks..

plugging my phone into usb cable to laptop, driver goes to install: 'qhsusb_dload no driver found
looking this up in google just re-enforces my suspicions..

yeah dude your phone is now a doorstop. this happened to me once as a noob android "modder" as i was trying to install an rom made for the international version of the gs3 (i9300) onto my north american at&t gs3
(SGH-I747). luckily i was on warranty and got a new one for free. hopefully you are on warranty as well.
Sent from my SAMSUNG-SGH-I747 using xda premium

20twins10 said:
So yesterday I was going to switch from PA to BeanStalk and ran into some problems, i restored back to PA.
Last night I went and downloaded LiquidSmooth I believe it is, went into recovery *cwm 6.0.2.7.* wiped data, cache, dalvik and formated system.. Installing the zip I ran into a status 7 error. I went to restore my nandroid from earlier in the day, my stable PA setup. No restore files could be found, internal, or external.
At this point I powered my phone off so take my micro sdcard out so I could download a rom through my laptop. While the rom was downloading I decided to go back to recovery to see if there was anything I was doing wrong there..I couldnt get to recovery. I couldnt get into download mode.. Plugging it in to the wall charger I wasnt even getting a charging light. I let it sit overnight on the charger and decided to start on it this morning..
Any button combo I do yields no result.. So I'm fearing this may be a toasted device.. If anyone has insight please let me know.. Much thanks..
Click to expand...
Click to collapse
Beanstalk 4.3??? Cause team chopsticks are saying there's a bug that can brick a phone maybe. So they suggest everyone wait before building or flashing cm based 4.3 roms.
****edit**** sorry ignore. Misread the first bit. You were on Beanstalk, nandroided back to pa, then tried liquid smooth. I got it now. Hope you figure it out!
Sent from my SAMSUNG-SGH-T989 using xda app-developers app

kj2112 said:
Beanstalk 4.3??? Cause team chopsticks are saying there's a bug that can brick a phone maybe. So they suggest everyone wait before building or flashing cm based 4.3 roms.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
BeanStalk 4.3 was yesterday morning. I had a hard time getting it to boot back up after wiping cache n dalvik. It was really unresponsive, holding buttons and releasing took forever to yield a result. So there was alot of battery pulling and buttons. I got pissed and just said **** it and left it alone and it booted up, I booted to recovery and switch back the Paranoid Android. There was a small handful of people in the thread all kinda saying the same thing, long delays and unresponsive..
My PA setup was stable, I've had it on for months.. I was in a flash kinda mood so I decided to try a different rom, something not 4.3 based.. So I downloaded the LiquidSmooth rom but it error'd during installing.. I wasnt able to restore, And when I shut it down it just seems I couldnt get it back up to do anything..
It could be a combination of events.. Just a minor bump in the road.. Not the first phone I had brick..
Eh.. Guess I get a new phone..

20twins10 said:
BeanStalk 4.3 was yesterday morning. I had a hard time getting it to boot back up after wiping cache n dalvik. It was really unresponsive, holding buttons and releasing took forever to yield a result. So there was alot of battery pulling and buttons. I got pissed and just said **** it and left it alone and it booted up, I booted to recovery and switch back the Paranoid Android. There was a small handful of people in the thread all kinda saying the same thing, long delays and unresponsive..
My PA setup was stable, I've had it on for months.. I was in a flash kinda mood so I decided to try a different rom, something not 4.3 based.. So I downloaded the LiquidSmooth rom but it error'd during installing.. I wasnt able to restore, And when I shut it down it just seems I couldnt get it back up to do anything..
It could be a combination of events.. Just a minor bump in the road.. Not the first phone I had brick..
Eh.. Guess I get a new phone..
Click to expand...
Click to collapse
Insurance wont cover it, TMobile is shipping one out under warranty protection.. Do they go back into the phones that are sent back and look at them or what??

Nah your good all they do is connect it to there program and restore it they have capabilities we dont lol
sent from my t mobile S4

20twins10 said:
So yesterday I was going to switch from PA to BeanStalk and ran into some problems, i restored back to PA.
Last night I went and downloaded LiquidSmooth I believe it is, went into recovery *cwm 6.0.2.7.* wiped data, cache, dalvik and formated system.. Installing the zip I ran into a status 7 error. I went to restore my nandroid from earlier in the day, my stable PA setup. No restore files could be found, internal, or external.
At this point I powered my phone off so take my micro sdcard out so I could download a rom through my laptop. While the rom was downloading I decided to go back to recovery to see if there was anything I was doing wrong there..I couldnt get to recovery. I couldnt get into download mode.. Plugging it in to the wall charger I wasnt even getting a charging light. I let it sit overnight on the charger and decided to start on it this morning..
Any button combo I do yields no result.. So I'm fearing this may be a toasted device.. If anyone has insight please let me know.. Much thanks..
Click to expand...
Click to collapse
Yeah dude that's a brick...sucks but no T-Mobile doesn't look into the device just basically do a higher form of JTAG an completely wipe the hardware to start over, or if it's real bad they just junk for parts and build somebody else a "refurbished" phone, there system makes the best dev look like a noob lol
Sent from my SAMSUNG-SGH-T989 using xda premium

soupysoup said:
Yeah dude that's a brick...sucks but no T-Mobile doesn't look into the device just basically do a higher form of JTAG an completely wipe the hardware to start over, or if it's real bad they just junk for parts and build somebody else a "refurbished" phone, there system makes the best dev look like a noob lol
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I got a laugh out of that, but I'm sure its true. With the amount of phones on the market, I'd love to know the percentage they take back in and replace.. It's gotta be astounding.. It's a small thorn in my side for a day and a half, but my phone should be here before noon. I just gotta go and find my rootkit folder and get it all ready
This is the 2nd phone I've wound up bricking. I didnt get my first true smart phone till October 3yrs ago. HTC droid incredible.. that phone was seriously tuffer then nails.. It was dropped so many times, i just stopped caring if it fell cause i knew it would be ok.. Went down a flight of wood steps into my basement during a call and didnt blink.. I wound up melting the back cover to the battery once, my daughters * i have twins* were destroying something and I had torch on looking for something. I wound up putting the phone down on a towel w/ torch on facedown.. I got busy cleaning what they messed up and by the time I remembered my phone I went to get it and it shut down as I picked it up.. It was extremely hot and around the LED you could see a ripple from where it melted. I pulled everything apart, let it cool off for like 10minutes and it booted right back up.. It bricked way later on, I was way more flash happy back then, then I am now. I'm pickier now, back then I was just trying anything..
This sII was bought in October of last year. But it's seen its number or battery pulls and restores.. Tomorrow we will follow up the same..

20twins10 said:
I got a laugh out of that, but I'm sure its true. With the amount of phones on the market, I'd love to know the percentage they take back in and replace.. It's gotta be astounding.. It's a small thorn in my side for a day and a half, but my phone should be here before noon. I just gotta go and find my rootkit folder and get it all ready
This is the 2nd phone I've wound up bricking. I didnt get my first true smart phone till October 3yrs ago. HTC droid incredible.. that phone was seriously tuffer then nails.. It was dropped so many times, i just stopped caring if it fell cause i knew it would be ok.. Went down a flight of wood steps into my basement during a call and didnt blink.. I wound up melting the back cover to the battery once, my daughters * i have twins* were destroying something and I had torch on looking for something. I wound up putting the phone down on a towel w/ torch on facedown.. I got busy cleaning what they messed up and by the time I remembered my phone I went to get it and it shut down as I picked it up.. It was extremely hot and around the LED you could see a ripple from where it melted. I pulled everything apart, let it cool off for like 10minutes and it booted right back up.. It bricked way later on, I was way more flash happy back then, then I am now. I'm pickier now, back then I was just trying anything..
This sII was bought in October of last year. But it's seen its number or battery pulls and restores.. Tomorrow we will follow up the same..
Click to expand...
Click to collapse
Yeah we've all bricked a device lol, I had a Samsung galaxy precedent that I beat to sh*t, threw, dropped, whatever n it always booted, still to this day actually lol its sitting in a draw somewhere, my daughter plays games on it lol, but yes honestly the amount of s2s that have been refurbished is astounding my buddy is a tech for T-Mobile which is how I know all this but they hardly ever even send u back the same device when u send for repair, just junk it for a new refurb, wipe and restore the broken one and someone else gets it lol, there tough and almost unbrickable but almost is the key word, how u bricked urs though is strange, I've never had it happen like that before, good luck with the new one and switch to twrp, much better recovery for all the new roms out there
Sent from my SAMSUNG-SGH-T989 using xda premium

I got this phone under the "free" section of craigslist.(lucky me)
this phone was perfect, no cracked screen, no scratches, just a bump in the side. The only major problem was that this phone was hard bricked.
What I did was that I went to ebay, and found a random seller with decent reviews for JTAG service. The whole thing cost about 40 dollars. (since I got the phone free, I would only lose $40 if this was a scam)
This dude was really nice! I got my GS2 back within a week completely fixed. with stock touchwiz loaded and prerooted alerady

new phone arrived a few hours ago. been running some errands and such.. now to root this one.. tmobile picked the tab up on this one..

so i threw cwm recovery on via odin, flashed my superuser zip. it failed a couple times, 3rd time it took.. booted up and titanium couldnt get access.. in the su update fixer its also failing at "gaining root access"..
any idea's?

Reboot issue

So I just got a refurbished Nexus 7 from NewEgg and for a day it was working fine. Even ran a stress test against it.... but then the second day I ran Words with Friends and it froze for a second and rebooted. This happened twice. My guess is hardware but wanted to get some opinions on this before I sent it back.

Sievers said:
So I just got a refurbished Nexus 7 from NewEgg and for a day it was working fine. Even ran a stress test against it.... but then the second day I ran Words with Friends and it froze for a second and rebooted. This happened twice. My guess is hardware but wanted to get some opinions on this before I sent it back.
Click to expand...
Click to collapse
Did you try factory reset and see if random reboots still occur?

Wipe all the things then flash from scratch?

nhizzat said:
Wipe all the things then flash from scratch?
Click to expand...
Click to collapse
I've used it for maybe 24hrs.. and was Factory Reset before getting to me. Is there any issues with 4.4.4 at all doing this?

I've had no issues with my Nexus 7. A factory restart really doesn't mean much. Eliminate as many variables as possible then go from there.