[Q] Phone randomly died , won't start again - Galaxy Note II Q&A, Help & Troubleshooting

So I put my phone on charge and went to sleep, the next morning the phone's battery lamp shined green as usual when the phone was fully charged. Only it had turned itself off and it wouldn't start it again.
I haven't contacted my provider yet because i am unsure whether the warranty will cover it since I rooted it the day before, have not installed anything yet though.
I have tried removing the battery for a couple of hours without any result, I have also tried different combinations of holding down buttons without any result either.
Can it be as simple as the battery broke? How can i check if that is the case without any other battery or voltmeter etc?
Has anyone else had this problem?
I am running 4.1.2 on my 7105, flashed from ODIN about a month ago.

Please provide some details to answer you better
Do you able to put device in download mode? What you can read in download mode rt upper corner?
Which method you have used to root? Have you flashed any cwm? If yes link here which one.
Have you tried flashing? If yes what was outcome?
Sent from my GT-N7100 using xda premium

dr.ketan said:
Please provide some details to answer you better
Do you able to put device in download mode? What you can read in download mode rt upper corner?
Which method you have used to root? Have you flashed any cwm? If yes link here which one.
Have you tried flashing? If yes what was outcome?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
No i am not able to get into download mode since absolutely nothing happens when i press any button, just like as if there was no battery in the phone.
I used CF-Auto-Root-t0lte-gtn7105 to root but I don't think that this is the source of the problem since the phone died two days after i rooted.
As I said I am using the 4.1.2 official version which i flashed using odin, that was over like 2-3 months ago so I dont remember exactly which one I used but I believe it was this one: http://forum.xda-developers.com/showthread.php?t=2027586
Here is the thread i used to root: http://forum.xda-developers.com/showthread.php?t=1933542

Firmware you have linked which you believe to flashed is doubtfully patched for sds.
On N7100 same released in dec 12 and within few days it was withheld, may be it was not properly patched. Later release in 2013 are sds patched.
Do you remember it was somewhat leggy/freezing before this happened?
Though symptoms mimics sds, have you tried to reboot to recovery?
Sent from my GT-N7100 using xda premium

dr.ketan said:
Firmware you have linked which you believe to flashed is doubtfully patched for sds.
On N7100 same released in dec 12 and within few days it was withheld, may be it was not properly patched. Later release in 2013 are sds patched.
Do you remember it was somewhat leggy/freezing before this happened?
Though symptoms mimics sds, have you tried to reboot to recovery?
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
No freezes or anything but the day before i rooted i remember it restarted itself whilst in my pocket, was sitting still so don't think i accidentally pressed the off button, but can't know for sure.
Cant enter recovery or anything since absolutely nothing happens when i hold down up/home/power, neither if I hold down/home/power or any other combination. Absolutely no response from the phone, just as there was no battery in the phone but i can assure you that there is. Nothing happens when I connect the charger either. No lights no nothing!

If possible try to manage for different battery to just confirm it is not battery issue, and remove battery from device for a day meanwhile and try to boot after that, if no result then it's likely sds and should consult service station.
Sent from my GT-N7100 using xda premium

I didn't think sds affected n7105 that's why I swapped both of my s3's for mine I'm pooping it now. S4 here I come
Sent from my GT-N7105 using xda app-developers app

Hi,
Is the N7105 got the same eMMC chip 0xf1 and 0xf7 as the N7100?

thedadio said:
I didn't think sds affected n7105 that's why I swapped both of my s3's for mine I'm pooping it now. S4 here I come
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
ppn7 said:
Hi,
Is the N7105 got the same eMMC chip 0xf1 and 0xf7 as the N7100?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=net.vinagre.android.emmc_check&hl=en
Download it and check. If it says "No, Sane chip" you're fine.

happened to me too!
exactly the same **** happened to me too i don't know what happened, i didn't root it or did anything to it. it just randomly turned itself off and didn't start up again. then suddenly it happened to load the battery again and i was able to boot it, but here the ****ed up part came... it showed me the samsung startup logo and everything but then weird green vertical stripes(like the matrix) appeared and nothing more happened. few reboots after, same problem as in the beginning, it's not starting up again. help me please

Related

Why did my Galaxy Nexus brick itself?

I have been using my fine since release from Verizon. Most of the time on 4.0.4 deodexed stock w/ FrancoKernel Milestone 4 and Radio I515.09 V.FA02 / I515.FA02.
Phone is in great condition. It was not overheating at the time of shut down.
Randomly the screen went dark with a bunch of lines (acting like it was dying).
It stayed on that frozen line screen until I pulled the battery.
It restarted with the Google logo and just sat there.
Pulled again. Now phone does not charge or turn on trying 3 different batteries.
Took battery and sim out for 10 minutes and still nothing.
I didn't mess with voltage or overclock or anything like that.
---
Should I send it in for warranty claim? I'm afraid they will get it working and see my rooted phone with private information and a ROM that allows tethering.
Did you attempt to restore to stock and see if it persists?
Sent from my Galaxy Nexus using Tapatalk 2
happymouse said:
Did you attempt to restore to stock and see if it persists?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
How do I return a phone to stock that I can't turn on?
jamor414 said:
How do I return a phone to stock that I can't turn on?
Click to expand...
Click to collapse
Can't boot into fast boot mode? Holding the power button and the both volume keys. Until the big android pops up?
Sent from my sprint galaxy nexus
ÜBER™ said:
Can't boot into fast boot mode? Holding the power button and the both volume keys. Until the big android pops up?
Sent from my sprint galaxy nexus
Click to expand...
Click to collapse
That doesn't work either. It has no signs of life whatsoever.
Android suicide :'(
Sent from my M886
jamor414 said:
That doesn't work either. It has no signs of life whatsoever.
Click to expand...
Click to collapse
Yeah gunna have to call for a replacement.
Sent from my sprint galaxy nexus
happymouse said:
Did you attempt to restore to stock and see if it persists?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Derrrrrrrrp
jamor414 said:
That doesn't work either. It has no signs of life whatsoever.
Click to expand...
Click to collapse
Yeah if it doesn't turn on no matter what you've tried, it's most likely an unrecoverable brick. I've had it happen to me on an HTC phone randomly and it sucked. Aside from what you've already tried, I'd say maybe leave the battery in, plug the phone into the charger and wait for a bit and see if anything happens. Other than that you're SOL.
I also highly doubt that Verizon will be able to coax the phone back to life if it's a hardware fault.
damn. thanks.
I had a Bionic do that, it seemed like it just shorted out one night. I went to a Verizon store and tried different batteries and such in it with no luck. Probably just a hardware defect of some sort.
Mine did the same just the other day. Same exact way you described it for me. I tried to revive it using ODIN and OMAP Flash but it gets stuck at writing to the NAND then fails. I actually searched the forum and it seems to have happened quite a lot. I'm guessing its a hardware defect that some of the Nexus have just like how it was on the first batch of Galaxy S i9000M phones. (I know because mine corrupted twice and Samsung refused to fix it the second time.) Some threads and even Chainfire's Nexus killed itself it seems:
https://twitter.com/ChainfireXDA/status/221919265408823297
http://forum.xda-developers.com/showthread.php?t=1671044
http://forum.xda-developers.com/showthread.php?t=1701347
http://forum.xda-developers.com/showthread.php?t=1696246
http://forum.xda-developers.com/showthread.php?t=1621430
http://forum.xda-developers.com/showthread.php?t=1592931
With that said, there might be one last thing you can do which is the OMAP flash JTAG via USB if you haven't tried it yet:
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
This will try to flash a bootloader for you where in you can access fastboot, etc. If you can access Download Mode, you can try to use ODIN to bring it back as well.
If ODIN or OMAP Flash fails to write to the NAND then its hardware issue and needs to be replaced. Hope you have warranty still.
Thanks Dawg. Nothing worked.
VZW tech support didn't even ask one question and sent me a new phone which arrives today. It must be common.
Loved my phone setup too.
I have to start backing everything up to my PC. I had a feeling not having an SD card would burn me.

[Q] Galaxy S III Fried

Would appreciate if anyone could help
Bought a brand new Galaxy S III from T-Mobile, a week ago. On the same day I rooted it, using these instructions galaxys3root dot com/galaxy-s3-root/how-to-root-t-mobile-galaxy-s3-sgh-t999/. . . Worked out great.
Then I used this ROM called Deodexed_Debloated_T999UVALEM, and that worked out fine.
Today I decided to use this rom: Criskelo_6.0.1_Stock_XXBLG9_ota
And while it was installing, it asked for an update file, which I did not have.. So I chose the option to reboot the phone. Since then the phone has been practically dead, and here are the symptoms:
1. The phone does not power up, in any mode
2. When connected to the pc, pc cannot recognize it
3. Installed Kies, and drivers, nothing changed
4. Plugged to the charger, and nothing changed
5. Removed the batter for over an hour and repeated the above and nothing changed
Does anyone know what I can to salvage this phone?
Thank you
Rekhter said:
Would appreciate if anyone could help
Bought a brand new Galaxy S III from T-Mobile, a week ago. On the same day I rooted it, using these instructions galaxys3root dot com/galaxy-s3-root/how-to-root-t-mobile-galaxy-s3-sgh-t999/. . . Worked out great.
Then I used this ROM called Deodexed_Debloated_T999UVALEM, and that worked out fine.
Today I decided to use this rom: Criskelo_6.0.1_Stock_XXBLG9_ota
And while it was installing, it asked for an update file, which I did not have.. So I chose the option to reboot the phone. Since then the phone has been practically dead, and here are the symptoms:
1. The phone does not power up, in any mode
2. When connected to the pc, pc cannot recognize it
3. Installed Kies, and drivers, nothing changed
4. Plugged to the charger, and nothing changed
5. Removed the batter for over an hour and repeated the above and nothing changed
Does anyone know what I can to salvage this phone?
Thank you
Click to expand...
Click to collapse
Looks like you flashed a ROM for I9300.
Can you get into download mode?
Hold down and home key while restarting phone.
Rekhter said:
Would appreciate if anyone could help
Bought a brand new Galaxy S III from T-Mobile, a week ago. On the same day I rooted it, using these instructions galaxys3root dot com/galaxy-s3-root/how-to-root-t-mobile-galaxy-s3-sgh-t999/. . . Worked out great.
Then I used this ROM called Deodexed_Debloated_T999UVALEM, and that worked out fine.
Today I decided to use this rom: Criskelo_6.0.1_Stock_XXBLG9_ota
And while it was installing, it asked for an update file, which I did not have.. So I chose the option to reboot the phone. Since then the phone has been practically dead, and here are the symptoms:
1. The phone does not power up, in any mode
2. When connected to the pc, pc cannot recognize it
3. Installed Kies, and drivers, nothing changed
4. Plugged to the charger, and nothing changed
5. Removed the batter for over an hour and repeated the above and nothing changed
Does anyone know what I can to salvage this phone?
Thank you
Click to expand...
Click to collapse
The problem here is that you flashed an International rom onto a T-Mobile Galaxy S3. The only solution I could think of would be to flash back to stock using Kies but that isn't really possible unless the phone is able to go into download mode.
zer0trip said:
Can you get into download mode?
Hold down and home key while restarting phone.
Click to expand...
Click to collapse
This
But you will hold the Volume down + Home + Power button Don't let go until your in download mode
Jigga0o7 said:
The problem here is that you flashed an International rom onto a T-Mobile Galaxy S3. The only solution I could think of would be to flash back to stock using Kies but that isn't really possible unless the phone is able to go into download mode.
Click to expand...
Click to collapse
Thank you for your response, unfortunatley it is not doing anything, it is not restarting in any modes.
Got any suggestions?
You just hard bricked your phone!!! :/ damn that sucked!!!!
Sent from my SGH-T999 using xda premium
cybrnook said:
This
But you will hold the Volume down + Home + Power button Don't let go until your in download mode
Click to expand...
Click to collapse
I held all three buttons down for over 3 minutes, nothing happened. Should I try it for longer?
Rekhter said:
I held all three buttons down for over 3 minutes, nothing happened. Should I try it for longer?
Click to expand...
Click to collapse
No , shouldn't take more than 10 seconds.
Sorry to hear that man, but in the future PLEASE RESEARCH before you get flash happy. International version of the GSIII has completely different hardware inside.
You need to stick to T-Mobile GSIII roms, or don't flash them at all. Might be a good candidate for stock rooted, or no root at all.
Pull battery. Put battery back in and hold Vol down, home and power, until it vibrates, then let power go but hold the other two until download mode comes up.
Flashing different carrier ROMs and kernels will result in hard bricking your phone!!! Only flash ROMs and kernals that is for your phone model!!!
Sent from my SGH-T999 using xda premium
The downfall of getting Flash Happy and just throwing anything at it you think you can...
stevessvt said:
Pull battery. Put battery back in and hold Vol down, home and power, until it vibrates, then let power go but hold the other two until download mode comes up.
Click to expand...
Click to collapse
Tried that again. Removed the battery, held all three down for 2 minutes straight, no vibration. screen black, nothing happening :-/
dannydv said:
Flashing different carrier ROMs and kernels will result in hard bricking your phone!!! Only flash ROMs and kernals that is for your phone model!!!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Dude you are more drama than gurls. Relax @op worst case scenario u will have to buy a jtag $3 on ebay and problem solved but first do some search and try possible solutions that worked for other users.
Alarmmy said:
It is time to call Tmobile or Samsung for warranty exchange.
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Quite sure this is not covered under warranty.
---------- Post added at 10:26 PM ---------- Previous post was at 10:26 PM ----------
lazarat said:
Dude you are more drama than gurls. Relax @op worst case scenario u will have to buy a jtag $3 on ebay and problem solved but first do some search and try possible solutions that worked for other users.
Click to expand...
Click to collapse
JTAG ftw
dannydv said:
Flashing different carrier ROMs and kernels will result in hard bricking your phone!!! Only flash ROMs and kernals that is for your phone model!!!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
not entirely true. At&t roms an kernels work with the T-Mobile s3. Don't remember if any others do.
Sent from my SGH-T999 using Tapatalk 2
I haven't seen one for 3 bucks but you definitely need the JTAG.
mustk1ll20 said:
not entirely true. At&t roms an kernels work with the T-Mobile s3. Don't remember if any others do.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Yup... we CAN in fact flash kernels and att roms... its modems/radios from other carriers that shouldn't be flashed. We can also flash some sprint and verizon roms, but as they are CDMA it'll take some more advance modding, to get them to run full and proper... probably a little over the OP's head, but just saying.
Still alls not lost, look into Jtag as others have suggested...
If u hard brickd your phone the $5 usb dongle JTAG will not unbrick it! You need to send it in for a jtage reflash!
Sent from my SGH-T999 using xda premium
dannydv said:
If u hard brickd your phone the $5 usb dongle JTAG will not unbrick it! You need to send it for jtage reflash!
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Any suggestions on where I can get this done?

[Q] note 2 n7100 crashing

hey
my phone has been acting weird for a while now.
the phone crashes a lot, some times it freezes while scrolling, some times it shuts down, some times it restarts on its own....
i tried to root the phone and flashed it with wanam, but it didn't stop crashing, then i flashed with omega v12, but the problem still continued...
shall i rule out that this might be a software issue?
what hardware part might be causing such behavior
ashrafezz said:
hey
my phone has been acting weird for a while now.
the phone crashes a lot, some times it freezes while scrolling, some times it shuts down, some times it restarts on its own....
i tried to root the phone and flashed it with wanam, but it didn't stop crashing, then i flashed with omega v12, but the problem still continued...
shall i rule out that this might be a software issue?
what hardware part might be causing such behavior
Click to expand...
Click to collapse
That doesn't sound good...
IMO it's most likely a hardware issue.
It's hard to say which part is causing this. Maybe the storage?
I hope this aren't SDS symptoms.
That would mean that SDS would be still possible with 4.1.2
muena90 said:
That doesn't sound good...
IMO it's most likely a hardware issue.
It's hard to say which part is causing this. Maybe the storage?
I hope this aren't SDS symptoms.
That would mean that SDS would be still possible with 4.1.2
Click to expand...
Click to collapse
i have no clue what that would be
i have the insane chip, but i do not know if this is sds or not
the phone hadent been stable since the 4.1.2 upgrade....
ashrafezz said:
i have no clue what that would be
i have the insane chip, but i do not know if this is sds or not
the phone hadent been stable since the 4.1.2 upgrade....
Click to expand...
Click to collapse
AFAIK if you had the SDS symptoms before the update, it is possible that you experience SDS after the 4.1.2 update.
I would backup all data, restore stock kernel/rom, unroot and return the phone for warranty.
ashrafezz said:
i have no clue what that would be
i have the insane chip, but i do not know if this is sds or not
the phone hadent been stable since the 4.1.2 upgrade....
Click to expand...
Click to collapse
use eMMC Brickbug to check using the memory test. In theory if it fails it is affected by SDS and your phone will die someday. If not it could be another problem. But as I said it is just "in theory", nothing 100% sure.
Sent from my GT-N7100 using xda app-developers app
aka_sirok said:
use eMMC Brickbug to check using the memory test. In theory if it fails it is affected by SDS and your phone will die someday. If not it could be another problem. But as I said it is just "in theory", nothing 100% sure.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
done that.
it passed the memory test although it has the insane chip.
i have no clue what this is, i bought it from the grey market so i just have a shop warranty.
am sending it in tomorrow for them to check it.
if nothing happens, i will have to send it to the official Samsung service.
appreciate your kind reply
ashrafezz said:
done that.
it passed the memory test although it has the insane chip.
i have no clue what this is, i bought it from the grey market so i just have a shop warranty.
am sending it in tomorrow for them to check it.
if nothing happens, i will have to send it to the official Samsung service.
appreciate your kind reply
Click to expand...
Click to collapse
Don't jump to conclusion so fast, do you use any custom kernel? I suspected it's due to wrong configuration
Try to recall what the last stable status of your phone would be help a lots...
Sent from my GT-N7100 using Tapatalk 2
sklchan said:
Don't jump to conclusion so fast, do you use any custom kernel? I suspected it's due to wrong configuration
Try to recall what the last stable status of your phone would be help a lots...
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
As he wrote in his first post, he rooted the phone because of the issues.
So it happened with stock system too.
Well new start from full wipe did it for me except I restored all apps with titanium Backup.
Sent from my GT-N7100 using xda premium
UtkarshGupta said:
Well new start from full wipe did it for me except I restored all apps with titanium Backup.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Same here
had some reboots(1/day), but after factory reset and update to DMC 3 no reboots since ~12 days.
First l left ereything untouched and added step by step every 4 days root, frameworkmod, my core Apps (via titanium backup)
As I've said, lots of these crashing are due toto conflicting setting...
Sent from my GT-N7100 using Tapatalk 2
UtkarshGupta said:
Well new start from full wipe did it for me except I restored all apps with titanium Backup.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
tried to restart, and factory reset, and wiped the cash and made a full restore....
nothing worked
even the custom roms didn't do much
i sent it out to service to c what they have to say
ashrafezz said:
tried to restart, and factory reset, and wiped the cash and made a full restore....
nothing worked
even the custom roms didn't do much
i sent it out to service to c what they have to say
Click to expand...
Click to collapse
Please don't forget to tell us what the problem was, when you get your phone back.
muena90 said:
Please don't forget to tell us what the problem was, when you get your phone back.
Click to expand...
Click to collapse
Yup same here, would like to know the culprit of the error as well...
Sent from my GT-N7100 using Tapatalk 2
Run stress test.
Sent from my GT-N7100 using xda premium
so, i got my phone back from the shop.( it is not the official Samsung retailer, just the shop that sold me the phone).
the guys said that they re-installed software and tried several kernels.
after a week of trials of reinstalling with no success, the guy called and said the phone is ready and working fine.
i got the phone and it worked fine for 5 min, then started acting crazy again.
i decided to root to see if i could get it going,
after several trials of rooting and un-rooting, and finally out of frustration, i knocked on the phone's back where the Mother board is located and re-rooted the phone.
suddenly the phone worked without freezing for the 5 days so far....
i am still monitoring the phone, but it seems that banging on the mother board had an effect on it (as weird and silly as it might seem)
i know that my phone fell a lot and that my son dropped it like a zillion times before it went acting crazy.....
i thought maybe something moved inside, and well, it seems i was correct (so far at least)...
ashrafezz said:
so, i got my phone back from the shop.( it is not the official Samsung retailer, just the shop that sold me the phone).
the guys said that they re-installed software and tried several kernels.
after a week of trials of reinstalling with no success, the guy called and said the phone is ready and working fine.
i got the phone and it worked fine for 5 min, then started acting crazy again.
i decided to root to see if i could get it going,
after several trials of rooting and un-rooting, and finally out of frustration, i knocked on the phone's back where the Mother board is located and re-rooted the phone.
suddenly the phone worked without freezing for the 5 days so far....
i am still monitoring the phone, but it seems that banging on the mother board had an effect on it (as weird and silly as it might seem)
i know that my phone fell a lot and that my son dropped it like a zillion times before it went acting crazy.....
i thought maybe something moved inside, and well, it seems i was correct (so far at least)...
Click to expand...
Click to collapse
Do you fancy hitting mine too?
Ive had this issue the past month, I have the insane chip aswell. Sent it off to Samsung as one day, it literally just made the screen go funny (multi colours, as if you pulled a cartridge out of the n64 or a Gameboy).
Samsung then took my warranty off, as they deemed it down to a small crack in my top right glass bit, which doesn't affect the phones use at all, as it was there for 3 months. They attempted to charge me £290 for a replacement logic board, and a new glass panel for the front, whish I think isn't fair as it wasn't the screen crack that caused the SDS on my phone.
Got mine back today, and the first thing I did was download all of the tools necessary to flash the ROM, only to find that I get a FAIL message in Odin, due to a missing PIT partition or something.
I now own a fancy paperweight, as I can only put this all down to a properly franked memory chip.

I need help

Owner of international Note 2.
This morning I found my phone dead. I cannot start it either through power button or other combination of buttons. I took out the battery and back in. Through ADB no luck it doesn't even register that I plugged in the phone.
From time to time the first led on the right of the camera blinks (I think it's one of the sensors).
Can anyone through an idea what I can do to recover my phone?
Sent from my Nexus 7 using XDA Premium HD app
daniel_cassian said:
Owner of international Note 2.
This morning I found my phone dead. I cannot start it either through power button or other combination of buttons. I took out the battery and back in. Through ADB no luck it doesn't even register that I plugged in the phone.
From time to time the first led on the right of the camera blinks (I think it's one of the sensors).
Can anyone through an idea what I can do to recover my phone?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
have you rooted your phone ? .. can you go to recovery ? download mode ?
My phone was rooted. I had MIUI on it. I was on the same ROM for 2 weeks, so it can't be the ROM. I cannot access the phone in any way possible
Unfortunately looks like its SDS ( sudden death syndrome ) . Was your phone on 4.1.1 or 4.1.2 firmware? Its supposed that 4.1.2 has sds fix. Anyway if its sds so only option is to replace motherboard.
Sent from my GT-N7100 using xda premium
T511 said:
Unfortunately looks like its SDS ( sudden death syndrome ) . Was your phone on 4.1.1 or 4.1.2 firmware? Its supposed that 4.1.2 has sds fix. Anyway if its sds so only option is to replace motherboard.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Agree with T511.. One of my frns S3 also had SDS n like he mentioned, motherboard had to be changed... if you have warranty n bill they will do it free.. doesnt matter if its rooted.. they cant check either..
It seems so. I've read for the last hour about it. What i don't know is: if i go to service, will they detect i was rooted and on custom rom? If so... can they refuse my service completely (After all SDS is not ROM related) or at least they can service me but with charges (which i presume it will be allot, but after all less then a new phone)?
daniel_cassian said:
It seems so. I've read for the last hour about it. What i don't know is: if i go to service, will they detect i was rooted and on custom rom? If so... can they refuse my service completely (After all SDS is not ROM related) or at least they can service me but with charges (which i presume it will be allot, but after all less then a new phone)?
Click to expand...
Click to collapse
Even they cant access it pal.. so they wont come to know.. just take it to service.. they will surely do it free if its under warranty..
but your data cant be revived.. hope you had a backup of contacts and msgs.. (5 mins'm waiting to post this .. as i've just started postin after a decent learning)
I had everything on my card. Titanium Backup few days ago....so i won't lose anything important. I just hope that the service will do it without arguing. I am under contract to Vodafone since november 2012. But in my country service or service period are words which are still foreign to distributors or sellers in general

[Q] Odd brick situation Tmobile SGH-T999 (Cant find exact answer)

Hey everybody,
I rooted my phone a couple weeks ago and one day it just pooped out. I researched a bunch on google etc and found some things to try but so far no solutions.
Model: SGH-T999 T-mobile s3 (Used CF-Auto-Root and Odin for rooting)
Problem: After the phone pooped out, I was unable to enter recovery mode. I could enter dl mode however it crashes at variable intervals. So I bought a jig figuring maybe that would help but it still crashes in dl about 5 seconds later. Any suggestions?
Everything that I have found on the internet has been were people can usually get it into dl mode and keep it there or they cant get there at all even with a jig. Any help would be appreciated. Thanks!
If you were running stock it's probably a hardware problem. If not what Rom are you on? What/when/how was your most recent flashes?
Have you tried kAsp3rd's brick fix in dev section?
Sent from my SCH-I535 using Tapatalk 4
DocHoliday77 said:
If you were running stock it's probably a hardware problem. If not what Rom are you on? What/when/how was your most recent flashes?
Have you tried kAsp3rd's brick fix in dev section?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I just tried the kasperd brick fix and it didnt work. It still crashes at variable times and I cannot get it into download mode long enough to do anything. I tried a jig and it also still crashes. Any help would be great. Thanks!
Does it turn off? Reboot? Freeze?
Sent from my SGH-T999L using Tapatalk 4
DocHoliday77 said:
Does it turn off? Reboot? Freeze?
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
It starts and then crashes. After awhile it might make it to the animation with the blue wave forming around the words samsung, but usually it crashes on the Samsung Galaxy SIII logo in the beginning. Also when I put it into download mode it crashes anywhere from 1-5 seconds after. When I try to get into recovery mode it crashes almost right away when the blue words are at the top left of the screen.
Also when I put the battery in it tries to boot on its own without me pressing power button, and sometimes it tries to reboot after it crashes and turns off without me pressing anything. Also after it crashes I usually cannot just press the power button to try and power it up again so I have to take the battery out and put it back in.
When I was doing the Kasperd brick fix I used the T999 debrick image. How do I know if I have a different variant of the T999. I saw that some people had T999v and T999N. What are those?
Look under the battery for your model. Sounds like a power button issue. All I can say is try fiddling with it a bit. May have to open to see if it is physically always in contact, or it could be a deeper issue on the board. Hard to say.
Sent from my SGH-T999L using Tapatalk 4
DocHoliday77 said:
Look under the battery for your model. Sounds like a power button issue. All I can say is try fiddling with it a bit. May have to open to see if it is physically always in contact, or it could be a deeper issue on the board. Hard to say.
Sent from my SGH-T999L using Tapatalk 4
Click to expand...
Click to collapse
Ok I just see T999 on the label.
How can it be a hardware issue when I never dropped the phone or anything. I was just thinking it was because I rooted the phone because it happened about a week after I rooted it. It was working one minute and then a couple hours later when I took it out of my pocket it was off and I tried turning it on and all that stuff started happening. I will definitely check the power button though. Thanks for the help.
Also another piece of info to add. When I plug it in to charge both the battery charging symbol and red light will sometimes turn on and then it crashes/goes black similar to what happens when trying to power up the phone. Not sure if that helps at all. Thanks!
If my phone was hard bricked I wouldnt be able to turn it on at all correct? Im trying to figure out if I will need to get this thing jtagged or something in order to get it working again.
phillycheese917 said:
How can it be a hardware issue when I never dropped the phone or anything.
Click to expand...
Click to collapse
Physical damage is not a prerequisite of hardware failure. Ever have a hard drive go bad? Did you drop it first?
Aerowinder said:
Physical damage is not a prerequisite of hardware failure. Ever have a hard drive go bad? Did you drop it first?
Click to expand...
Click to collapse
True, however I just find it odd that I rooted the phone and a week later it happened. That is why I am leading towards an issue involving that and not hardware damage.
If it was a problem with rooting, it would have gone south right away. Many people are having these button issues recently. And you don't have to drop it, like aerowinder said, but you do use the button right? Moving parts wear out. Hardware fails. That's really all there is to it. While I could be wrong in my diagnosis, I don't think that will prove to be the case here.
Sent from my SGH-T999L using Tapatalk 4
It does most certainly sound like a hardware issue in the power button. I read another thread very similar to this same thing on the T999.
KAsp3rd said:
It does most certainly sound like a hardware issue in the power button. I read another thread very similar to this same thing on the T999.
Click to expand...
Click to collapse
Any suggestions on what to do from here? I dont think the phone is under warranty anymore.
I took the back casing off to see if the button is getting stuck or anything, but all the mechanics look normal.
phillycheese917 said:
Any suggestions on what to do from here? I dont think the phone is under warranty anymore.
Click to expand...
Click to collapse
I would recommend searching around for others who have had the same issue and seeing what their resolutions were. I've not seen many on here but google turned up quite a few.
KAsp3rd said:
I would recommend searching around for others who have had the same issue and seeing what their resolutions were. I've not seen many on here but google turned up quite a few.
Click to expand...
Click to collapse
Thanks guys! I found a good thread on here about the S3 sudden death thread. Im going to read up on that and see what I can do. It was just tough to find since I was thinking it was bricked but the descriptions for this power button sudden death thing sound spot on. Hopefully I will be able to get everything back in working order.

Categories

Resources