I just wanted to let you all know that even on 4.1.2 (stock and stock recovery), your note can just all of a sudden die. For no reason. I had stock malaysia ROM 4.1.2 that was released in April I believe. It was rooted, but all I used that for was Titanium Backup.
My usage of the phone was bare minimum, all I really use the phone is for Google Talk. That's actually all I was doing when all of a sudden the screen froze and the phone would not respond to any buttons or touches. Once I removed the battery it never started again. I can't get it to boot normally, or download mode or anything.
I'm in the US and i bought this off eBay back in November or something of last year, so I have no idea what to do now except get another phone.
Yes its the chipset in the phone that has a bug which can kill the phone. Alot of the note2 phones have it including mine. There is an app on market that can tell you if you got the chip in your phone but by now you already know that. Try a phone repair shop or if you want surf around the net and see if you can find a motherboard for a decent price then you could change it your self.
Sent from my GT-N7100 using XDA Premium 4 mobile app
---------- Post added at 06:50 PM ---------- Previous post was at 06:47 PM ----------
The newer roms have a software fix for the hardware bug. Dont remember if that fix is in the rom it self or in the kernel but if you had the latest custom rom on your phone then it might not have died.
Sent from my GT-N7100 using XDA Premium 4 mobile app
I was on 4.1.2 with stock rom and kernel combination. As far as everyone seems to say on this site, that is what you need to do to try to avoid SDS. In either case, my suggestion to everyone here is to just get another phone before yours dies as well.
ksc6000 said:
I was on 4.1.2 with stock rom and kernel combination. As far as everyone seems to say on this site, that is what you need to do to try to avoid SDS. In either case, my suggestion to everyone here is to just get another phone before yours dies as well.
Click to expand...
Click to collapse
My N7105 died also, simply would not boot, not even into download/recovery mode at all, no red led. Tried switching batteries, charging, pressing buttons for 30secs, etc; no response.
It was running 4.1.2 and on Perseus kernel alpha33, which was what everyone said it needed to avoid the SDS issue. My phone was even tested safe/sane via the eMMC test app.
Not 100% certain if it was SDS, but either way it was unresponsive/dead.
ksc6000 said:
I just wanted to let you all know that even on 4.1.2 (stock and stock recovery), your note can just all of a sudden die. For no reason. I had stock malaysia ROM 4.1.2 that was released in April I believe. It was rooted, but all I used that for was Titanium Backup.
My usage of the phone was bare minimum, all I really use the phone is for Google Talk. That's actually all I was doing when all of a sudden the screen froze and the phone would not respond to any buttons or touches. Once I removed the battery it never started again. I can't get it to boot normally, or download mode or anything.
I'm in the US and i bought this off eBay back in November or something of last year, so I have no idea what to do now except get another phone.
Click to expand...
Click to collapse
Ohh,Sorry for that & Thanks share this IMP Info,Have u ever Test eMMC Bug app? U have Sane Chip?U bought new phone?
No I didn't buy a new phone yet, don't have the money. I probably won't, I'll probably just use my old Nexus One. Yes I did use that app and it was insane chip. I just thought that with 4.1.2 it was safe, guess not.
Anybody know if it's safe for me to sell this phone on eBay? Obviously I'm going to sell it as is and write that it doesn't work, but I'm wondering if I do that, if someone can get it repaired, will they have access to my data that was on it?
ksc6000 said:
No I didn't buy a new phone yet, don't have the money. I probably won't, I'll probably just use my old Nexus One. Yes I did use that app and it was insane chip. I just thought that with 4.1.2 it was safe, guess not.
Anybody know if it's safe for me to sell this phone on eBay? Obviously I'm going to sell it as is and write that it doesn't work, but I'm wondering if I do that, if someone can get it repaired, will they have access to my data that was on it?
Click to expand...
Click to collapse
Oh OK,but who ever face SDS they have one common symptoms like when press power button red led blinks,is it same happening in your mobile? also they are able to go in download mod but product id will be missing but in your case u r not able to go in download mod,its confusing.
jdomadia said:
Oh OK,but who ever face SDS they have one common symptoms like when press power button red led blinks,is it same happening in your mobile? also they are able to go in download mod but product id will be missing but in your case u r not able to go in download mod,its confusing.
Click to expand...
Click to collapse
No red light. I can't get into download mode at all.
a piece of my knowledge acquired by reading the whole thread. First of all it doesn't matter if you were at 4.1.2 it should be dlk7 or higher (firsts 4.1.2 didn't have it). so do you know the number? if it was higher it could be a big problem for the affected chips :S
and secondly, there are 2 ways of SDS the first is known as "soft" which allow to enter download. the second is the hard one and the one that OP may have.
hope it helped somehow
Sent from my GT-N7100 using xda premium
aka_sirok said:
First of all it doesn't matter if you were at 4.1.2 it should be dlk7 or higher (firsts 4.1.2 didn't have it). so do you know the number? if it was higher it could be a big problem for the affected chips :S
Click to expand...
Click to collapse
Hmm ok, just curious, my dead phone was running 'HashCheck Hybrid v2.2 ZHDMB1.t0lte' with Perseus kernel. Should it have been safe or no?
aka_sirok said:
and secondly, there are 2 ways of SDS the first is known as "soft" which allow to enter download. the second is the hard one and the one that OP may have.
hope it helped somehow
Click to expand...
Click to collapse
I see, so Hard SDS it was then.
Perseus kernel has the patch for sds added.
GT N7105 with XDA Premium......that is all......
sure but i readed somewhere that to be 100% safe it has to be kernel and recovery sds patched. if you had those patched both the ones that have the insane chip must be worried :S
Sent from my GT-N7100 using xda premium
I wonder if using cyanogenmod also end up the same? I mean this problem only caused by original firmware? if both is the same is there a reasonable solution for stock users? My wife has the phone for 2 months and I want to make sure she doesn't suffer the problem from the beginning. What are the measures I can take to avoid this problem?
maluus said:
I wonder if using cyanogenmod also end up the same? I mean this problem only caused by original firmware? if both is the same is there a reasonable solution for stock users? My wife has the phone for 2 months and I want to make sure she doesn't suffer the problem from the beginning. What are the measures I can take to avoid this problem?
Click to expand...
Click to collapse
it is a hardware problem. check the version of the chip with EMMC checker, 2 months old it's quite a good notice because it means newer chip probably.
Sent from my GT-N7100 using xda premium
Well hopefully. But while investigating the issue in internet I read 1-2 guys who have so called "sane" chips but still having freezes. I don't know if they really had the same issue or they had their phones bricked in the end but that caused me to doubt the safety of sane chips. I don't know.
Enviado desde mi One S usando Tapatalk 4
aka_sirok said:
sure but i readed somewhere that to be 100% safe it has to be kernel and recovery sds patched. if you had those patched both the ones that have the insane chip must be worried :S
Click to expand...
Click to collapse
That was my understanding too, I had Philz CWM Touch (cant remember which version, but I d/led and installed it last month) installed as well.
This was the version I was running:
N7100XXDMC3 N7100OLBDMD1 - Malaysia
maluus said:
Well hopefully. But while investigating the issue in internet I read 1-2 guys who have so called "sane" chips but still having freezes. I don't know if they really had the same issue or they had their phones bricked in the end but that caused me to doubt the safety of sane chips. I don't know.
Enviado desde mi One S usando Tapatalk 4
Click to expand...
Click to collapse
Checked it and my wife's is a "sane" chip.
Related
After installing FoxHound ROM on Galaxy S3 i747, and it is absolutely dead now. Not even powers up. Please help. Cannot get to recovery or download either. Just black screen, no signs of life whatsoever.
thanks
michaelkagan said:
After installing FoxHound ROM on Galaxy S3 i747, and it is absolutely dead now. Not even powers up. Please help. Cannot get to recovery or download either. Just black screen, no signs of life whatsoever.
thanks
Click to expand...
Click to collapse
Can you provide a link to the ROM?
That's an i9300 ROM.
scorpion667 said:
That's an i9300 ROM.
Click to expand...
Click to collapse
That's what I thought. Sounds like a hard brick if you can't get to recovery or download mode. Search out mobiletechvideos they offer j-tag services and I have seen them recommended on here often.
The OP made a mistake and now needs help to fix it.
We are all here to help each other not make someone feel worse about themselves!
Let's respect and help each other
Thread cleaned
Thank you for your cooperation
Friendly Neighborhood Moderator
or you can send to samsung for warranty repair, thats what i had to do.
Just go to att service center and get a replacement. That's it. That's what I.did with my skyrocket
Sent from my SGH-I747 using Tapatalk 2
I heard you can pull battery and then attempt to get into download mode from there from a thread long ago.
Sent from my SAMSUNG-SGH-I747 using xda premium
Few days ago I just started installing ROMs for the first time on my rooted AT&T S3. Starting with CM10, then JellyBam, and so forth testing/trying out one at a time. I was clearing dalvik and wiping cache before and after installing each ROM. Each ROM worked fine until I finally reached the fourth or fifth ROM called Foxhound and that's when my phone when to crap. I went through the install and after it rebooted my screen went blank and never came back on. Unable to get into CWM or Download Mode, I did battery pull and also plugged via USB into my PC it still won't boot. I read that the USB jig works on the Galaxy S3, already ordered and waiting for it to come in. If that doesn't work then I'm gonna have to send it in for JTAG repair. I already read off another site that someone encountered the same issue and the USB jig didn't work (this is after I already ordered it) so I'm crossing my fingers.
And this is all because of Samsung Allshare Play isn't compatible with CM10 because it works off touchwiz. So I was looking for a touchwiz based ROM and heard about Foxhound. Once I get my phone back up I'm going to try Jedi Invasion ROM as I heard some good reviews.
KryptonKal-El said:
Few days ago I just started installing ROMs for the first time on my rooted AT&T S3. Starting with CM10, then JellyBam, and so forth testing/trying out one at a time. I was clearing dalvik and wiping cache before and after installing each ROM. Each ROM worked fine until I finally reached the fourth or fifth ROM called Foxhound and that's when my phone when to crap. I went through the install and after it rebooted my screen went blank and never came back on. Unable to get into CWM or Download Mode, I did battery pull and also plugged via USB into my PC it still won't boot. I read that the USB jig works on the Galaxy S3, already ordered and waiting for it to come in. If that doesn't work then I'm gonna have to send it in for JTAG repair. I already read off another site that someone encountered the same issue and the USB jig didn't work (this is after I already ordered it) so I'm crossing my fingers.
And this is all because of Samsung Allshare Play isn't compatible with CM10 because it works off touchwiz. So I was looking for a touchwiz based ROM and heard about Foxhound. Once I get my phone back up I'm going to try Jedi Invasion ROM as I heard some good reviews.
Click to expand...
Click to collapse
Foxhound is for the i9300 as stated above so JTAG is probably your only option! In the future double check to make sure the ROM you are flashing is for your device!
Sent from my SGH-I747 using xda app-developers app
Someone's your I download mode but phone looks off and screen black. Keep it hooked to Odin to check once it's connected.taken me two days before to fix a bricked phone two hundred trys with screen black but it worked once.
Sent from my SGH-I747 using xda premium
xxsicknessxx said:
Someone's your I download mode but phone looks off and screen black. Keep it hooked to Odin to check once it's connected.taken me two days before to fix a bricked phone two hundred trys with screen black but it worked once.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
sometimes, xxsicknessxx, i dont know wtf you're saying. its all good, though. cheers
xxsicknessxx said:
Someone's your I download mode but phone looks off and screen black. Keep it hooked to Odin to check once it's connected.taken me two days before to fix a bricked phone two hundred trys with screen black but it worked once.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Lmao I think I might understand. Sometimes even though the screen is black you can still do the button combo for download mode and it'll actually go into it even though you can't see that it went into download mode. Then plug in usb and hopefully Odin will recognize that you're in download mode and you'll be able to flash stock rom lol
Sent from my SGH-I747 using xda premium
xBeerdroiDx said:
sometimes, xxsicknessxx, i dont know wtf you're saying. its all good, though. cheers
Click to expand...
Click to collapse
I second that, can you repeat that please? Something about hundred tries...? Lol (seriously though)
---------- Post added at 01:22 PM ---------- Previous post was at 01:13 PM ----------
drock212 said:
Lmao I think I might understand. Sometimes even though the screen is black you can still do the button combo for download mode and it'll actually go into it even though you can't see that it went into download mode. Then plug in usb and hopefully Odin will recognize that you're in download mode and you'll be able to flash stock rom lol
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Correct me if I'm wrong, after the combo press to get into download mode, don't you have to press either Vol Up or Vol Dn to continue into download mode? If so which one?
KryptonKal-El said:
I second that, can you repeat that please? Something about hundred tries...? Lol (seriously though)
---------- Post added at 01:22 PM ---------- Previous post was at 01:13 PM ----------
Correct me if I'm wrong, after the combo press to get into download mode, don't you have to press either Vol Up or Vol Dn to continue into download mode? If so which one?
Click to expand...
Click to collapse
Up
Wilcox12 said:
Foxhound is for the i9300 as stated above so JTAG is probably your only option! In the future double check to make sure the ROM you are flashing is for your device!
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
*Update*
I received the USB Jig and it did not work. Will be sending it in for JTAG repair in a few days. I have also been thinking about taking the phone back to the AT&T store and give them a bs story about it just stop working all of a sudden and get it replaced since I'm still under the 1yr warranty. But then again I hate refurbished replacements so I'll might as well send it in for repair.............???
KryptonKal-El said:
*Update*
I received the USB Jig and it did not work. Will be sending it in for JTAG repair in a few days. I have also been thinking about taking the phone back to the AT&T store and give them a bs story about it just stop working all of a sudden and get it replaced since I'm still under the 1yr warranty. But then again I hate refurbished replacements so I'll might as well send it in for repair.............???
Click to expand...
Click to collapse
Search around on here for warranty replacements. I've read a few threads where people have hard bricked and returned to AT&T for warranty replacements. One thing to keep in mind tho, if they were to look into and see that it was because you were modifying your device, after a few weeks you would have a fat 600$ charge on your bill.. I'm not saying its out of the question. Just read a lot and see what other peoples results were first!
Sent from my SGH-I747 using xda app-developers app
Wilcox12 said:
Foxhound is for the i9300 as stated above so JTAG is probably your only option! In the future double check to make sure the ROM you are flashing is for your device!
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Yeah, not to make the OP feel bad ( I feel your pain, really) but this should be a warning to all new flashers (myself included).
The International uses a quad core processor, and the AT&T uses a dual core. Not even close to being the same hardware and flashing the wrong rom is an invitation for disaster. This is not the first instance of this I have read either.
I know there is a tendency to say peeps need to watch what they're doing, but a big warning label would be nice, since the S3 comes in 2 hardware flavors.
I hope you get this worked out with a jig. I have read you can rig one up yourself if you're handy, but I have not seen the instructions to do so.
If you can get back in, I can personally verify that this rom flashes back to stock unrooted. Be sure to clear your cache too.
Michael503 said:
a big warning label would be nice, since the S3 comes in 2 hardware flavors..
Click to expand...
Click to collapse
a big warning label (bigger than what they already post) is not necessary, nor is it the devs responsibility to baby-proof everything. if you find yourself hunting around the internet on 12 different sites, looking for rooting guides and roms for the S3, you're wrong. stick to one place, like xda. know your model number, make sure you're in the right forum, read over the kernel/rom page to ensure you're flashing the files meant for your device.
a "big warning label" would only be encouraging the large amount of spoon-feeding that so many (noobs and lazy peeps) on this forum already expect and somebody would still flash the wrong file like an idiot.
cheers
xBeerdroiDx said:
a big warning label (bigger than what they already post) is not necessary, nor is it the devs responsibility to baby-proof everything. if you find yourself hunting around the internet on 12 different sites, looking for rooting guides and roms for the S3, you're wrong. stick to one place, like xda. know your model number, make sure you're in the right forum, read over the kernel/rom page to ensure you're flashing the files meant for your device.
a "big warning label" would only be encouraging the large amount of spoon-feeding that so many (noobs and lazy peeps) on this forum already expect and somebody would still flash the wrong file like an idiot.
cheers
Click to expand...
Click to collapse
I see you joined back in November. How'd you get so wise so fast?
No, I agree that it not the devs responsibility to make sure no one makes a mistake, still, for a phone that comes with 2 different mainboards, it might be a courtesy, just in case the user has misplaced one of the half dozen or so tabs he/she has open in their browser after power surfing for an hour. The OP made a mistake. It happens. Calling him (or me) an idiot or lazy, is neither helpful, or polite.
cheers right back atcha!
Let us find out how mush SDS has affected to the Galaxy Note 2 by voting.
Keep posting in the thread so that the thread is keep bumping and people can vote.
AFAIK most of the SDS occurs within first six month, so the Poll options are according to it.
Please download this application and check your FwRev of chip and then vote
If you look in the sds thrwad you'll find far more opinions.
Sent from my GT-N7100
Your poll doesn't cater for me.
Had my N7100 with 0xf1 for a bit less than six months, not SDS yet, but showing symptoms (freezes/resets).
gadgetuk437 said:
Your poll doesn't cater for me.
Had my N7100 with 0xf1 for a bit less than six months, not SDS yet, but showing symptoms (freezes/resets).
Click to expand...
Click to collapse
I think it's ironic how it's called Sudden Death Syndrome and yet people think theyre actually experiencing it's symptoms on the phone. Maybe it was labeled wrong but maybe someone can correct me?
Sent from my GT-N7100 using Tapatalk 2
bushako said:
I think it's ironic how it's called Sudden Death Syndrome and yet people think their actually experiencing it's symptoms on the phone. Maybe it was labeled wrong but maybe someone can correct me?
Sent from my GT-N7100 using Tapatalk 2
Click to expand...
Click to collapse
Couldn't agree more.
Sent from my GT-N7100 using xda app-developers app
I am confused should i get note 2 or not (because of SDS) i started this poll. but looks like many people have not used 0xf1 chip for six months
i dont know what to do.. should wait more for newer version of chip?
i dont know why but whenever i compare mobiles with note 2 i like only note2 but sds does not let me go ahead please suggest me what to do
nicholes said:
I am confused should i get note 2 or not (because of SDS) i started this poll. but looks like many people have not used 0xf1 chip for six months
i dont know what to do.. should wait more for newer version of chip?
i dont know why but whenever i compare mobiles with note 2 i like only note2 but sds does not let me go ahead please suggest me what to do
Click to expand...
Click to collapse
I think u can go for it as 4.1.2 fixes sds or custom kernel+custom recovery fixes that on 4.1.1, and I think newer stock of note 2 should have newer chips so at the end its ur call
has anyone of you face or seen any 32 GB note 2 is getting SDS?
nicholes said:
has anyone of you face or seen any 32 GB note 2 is getting SDS?
Click to expand...
Click to collapse
Lol I clicked thanks by accident but I wanted to say that it's only the 16gigs that's affected by sds.
Sent from my GT-N7100 using xda premium
gaurav2009 said:
I think u can go for it as 4.1.2 fixes sds or custom kernel+custom recovery fixes that on 4.1.1, and I think newer stock of note 2 should have newer chips so at the end its ur call
Click to expand...
Click to collapse
Are you sure 4.1.2 is SDS safe? Why?
I'm trying to find any information about this problem as my phone died 2 days ago and I want to avoid this situation in the future.
Samsung doesn't recognize this bug officially (or at least I didn't find this information) and there is no official claims 4.1.2 fixes this.
colibri2 said:
Are you sure 4.1.2 is SDS safe? Why?
I'm trying to find any information about this problem as my phone died 2 days ago and I want to avoid this situation in the future.
Samsung doesn't recognize this bug officially (or at least I didn't find this information) and there is no official claims 4.1.2 fixes this.
Click to expand...
Click to collapse
Sammy would never acknowledge the existence of sds officially nor they seem to know what is going to be the perfect solution to the problem.
nicholes said:
has anyone of you face or seen any 32 GB note 2 is getting SDS?
Click to expand...
Click to collapse
It only happens to the 16gig versions of the note 2 which has that chip revision afaik.
Sammath said:
It only happens to the 16gig versions of the note 2 which has that chip revision afaik.
Click to expand...
Click to collapse
How does a newbie know if thier Note 2 is this revision?
Sent from my GT-i9500 using XDA Premium HD app
mstickland said:
How does a newbie know if thier Note 2 is this revision?
Sent from my GT-i9500 using XDA Premium HD app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2093599
I have had this phone since October 23rd and have had no problems. If it did die, I would warranty it through T-Mobile. They've been good to me in the past where I sent back my old HTC Sensation three times, each time they got a new refurb to me within 3 days. :good:
No problems here with sds, no lags, freezes. Works fine, thinking about rooting but not yet, still fears about sds
Sent from my GT-N7100 using xda premium
I seen some of the method given that used to detect the faulty chip but i just curious as the result on my phone somehow shown contradict result. May i know which source are reliable to ensure that the phone chip is faulty.
1st check with IMEI, i get 3537 (understand that anything 3550 should be no problem)
2nd check with dial *#12580*369#, i get HW rev 1.300 as understand HW rev If 1.301 then it is good chip, 1.300 is bad chip
3rd check with eMMC check, i notice the result given are different as it shows positive result with no SDS reported and sane chip....
d33pbluez said:
I seen some of the method given that used to detect the faulty chip but i just curious as the result on my phone somehow shown contradict result. May i know which source are reliable to ensure that the phone chip is faulty.
1st check with IMEI, i get 3537 (understand that anything 3550 should be no problem)
2nd check with dial *#12580*369#, i get HW rev 1.300 as understand HW rev If 1.301 then it is good chip, 1.300 is bad chip
3rd check with eMMC check, i notice the result given are different as it shows positive result with no SDS reported and sane chip....
Click to expand...
Click to collapse
Got all the things you posted here. But few month ago, My phone is still in good mood. (at least i think that).
Type: VTU00M
FWrev: 0xF1
Only Type: VTU00M
FWrev: 0xF7
is safe as per XDA SDS thread. They also mentioned that JB 4.1.2 has safe stock kernel.
t seems my phone is broken now also duo the SDS-problem. I knew that I had a SGN2 with a Insane-chip. I've updated to version 4.1.2 (late version DLK7) kinda fast. Afterwards I decided to root my phone and flash the Perseus kernel with a built-in software SDS-fix. I've runned the eMMC program multiple times without a crash or problem. So I thought that my phone was not affected / corrupted yet. A couple of weeks ago the symptoms started. I had a phone-reboot when I clicked to update a application in Google Play. A couple days later another crash. I've did run the eMMC program again and it showed : Passed. Then it seemed suddenly the problem was not happening for roughly two weeks.
Last week my phone started to acting weird after a program update (LED LIGHT MANAGER). My first thought was that this was because of a bad LED LIGHT MANAGER update. So I've cleared the data and removed the application. But the problem occured afterwards.
I did a eMMC program test and my phone did reboot (did not pass the test). Then freezes and reboots started to happen frequently and the time between those were becoming shorter and shorter. Maybe it was caused by a program or something. So I've started in Safe-mode and see what happened. But even that made my phone freeze.Sometimes scrolling in mails, facebook or even deleting a picture is causing the freeze.
Now the phone is even freezing after like 2 minutes without dooing anything. And one time it didn't wanted to power on. A battery-remove and add was needed. Also on a restart I noticed that some datasetting of application where missing. I had to do the settings of Swiftkey-board again and from Whatsapp+ :S:S
Luckily got most of my datastored in the cloud with a good back-up of Titanium Back-up. I have a insurrence also on my phone. Upcoming wednesday gonna visit the Samsung Repair Store and ask them to replace my motherboard with a good chip. Phone is roughly : 7/8 months old now.
It seems that the software-fix (kernel and rom) are not the solution. Sooner or later everyone with that specific kind of broken Batch: VTU00M 16GB internal memory chips with revision 0xF1 will be a victim of this SDS problem. A software patch is definitely not the solution for this problem.
We keep in touch.
Regards,
IriseyouFall / Jurgen
I'm root and unlocked bootloader and I want to know if xperia ZL suffers from "Sleep of Death" issue like the Z...and does the fix applied to ZL as well..
Cause my zl kinda suffer from it...after a reboot the phone shut itself..it will stay longer if I connected to a charger but after a long period it will shut it self again...I think it's a software issue cause when in cwm, it doesn't shut down...but I have formatted to factory state and everything stock but the problem still persist...
I'm on latest 2.67 firmware and stock kernel but will relocking the bootloader will save my phone...if not, I'm gonna try to claim warranty and hopping they don't detect I'm already void the warranty even I'm relock again...
Hope someone can help....tq
Sent from my iPhone using Tapatalk Pro
martin132014 said:
I'm root and unlocked bootloader and I want to know if xperia ZL suffers from "Sleep of Death" issue like the Z...and does the fix applied to ZL as well..
Cause my zl kinda suffer from it...after a reboot the phone shut itself..it will stay longer if I connected to a charger but after a long period it will shut it self again...I think it's a software issue cause when in cwm, it doesn't shut down...but I have formatted to factory state and everything stock but the problem still persist...
I'm on latest 2.67 firmware and stock kernel but will relocking the bootloader will save my phone...if not, I'm gonna try to claim warranty and hopping they don't detect I'm already void the warranty even I'm relock again...
Hope someone can help....tq
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
Well, im 100% sure that problems on phone comes put when people root, change firmware, custom. etc all kind of (pirate stuff) not officilly from sony to the phone, i have always been stok official on every phone i had ( S2, S3, NOTE2, ZL) and nothing has happened to me with sudden death or sleep of death.
I just want to know WHY PEOPLE KNOWING ALL THIS ISSUES ON CUSTOM, LIKE BUGS ETC THEY STILL LIKE CUSTOM.... lol thats like to be MASOCHIST..
STICK to the stock.
danieldp1990 said:
Well, im 100% sure that problems on phone comes put when people root, change firmware, custom. etc all kind of (pirate stuff) not officilly from sony to the phone, i have always been stok official on every phone i had ( S2, S3, NOTE2, ZL) and nothing has happened to me with sudden death or sleep of death.
I just want to know WHY PEOPLE KNOWING ALL THIS ISSUES ON CUSTOM, LIKE BUGS ETC THEY STILL LIKE CUSTOM.... lol thats like to be MASOCHIST..
STICK to the stock.
Click to expand...
Click to collapse
I agreed with you, I always been stock, no root or unlocked bootloader. I rather be with a phone that have warranty just in case something happen, than been with a modified phone, death and not warranty if Sony found out.
Sent from my C6506 using xda app-developers app
Every phone I had I've modded the **** out of it. Yet I never had the problem that I've broken the phone. I don't know how people get their phone destroyed, the only reason I can think of is the fact that people don't read carefully and miss important details in a description or tutorial.
Sent from my C6503 using xda app-developers app
maclancer said:
I agreed with you, I always been stock, no root or unlocked bootloader. I rather be with a phone that have warranty just in case something happen, than been with a modified phone, death and not warranty if Sony found out.
Sent from my C6506 using xda app-developers app
Click to expand...
Click to collapse
Well that's good for ordinary people with ordinary stuff on their hand...other people doesn't like that and I'm one of it...well this is personal liking anyway...
I have used many android phone in range of model including iphone and all root and jailbreak...and some people love the change and love to put their phone to the limit...
Only recent phone I have problem with and old model don't have any problem...
Sent from my iPhone using Tapatalk Pro
einfachgaer said:
Every phone I had I've modded the **** out of it. Yet I never had the problem that I've broken the phone. I don't know how people get their phone destroyed, the only reason I can think of is the fact that people don't read carefully and miss important details in a description or tutorial.
Sent from my C6503 using xda app-developers app
Click to expand...
Click to collapse
I'm considered myself an experience on rooted phone...always double check when trying to flash or modded something....and always successful on it...if I brick it I always recover it again...only the current flagship I got problem with...I think this is a problem with some Sony phone that have problem on some of it...that something they miss...I work in Japanese factory and I know how they work....
Sent from my iPhone using Tapatalk Pro
martin132014 said:
I'm considered myself an experience on rooted phone...always double check when trying to flash or modded something....and always successful on it...if I brick it I always recover it again...only the current flagship I got problem with...I think this is a problem with some Sony phone that have problem on some of it...that something they miss...I work in Japanese factory and I know how they work....
Sent from my iPhone using Tapatalk Pro
Click to expand...
Click to collapse
bad luck you got a defective phone, cause mine is working like new with 0 issues.
I had rooted many other phones and also moding, but the truth is that nothing is much better than STOCK = 0 BUGS, and troubles.
danieldp1990 said:
bad luck you got a defective phone, cause mine is working like new with 0 issues.
I had rooted many other phones and also moding, but the truth is that nothing is much better than STOCK = 0 BUGS, and troubles.
Click to expand...
Click to collapse
Well that's true...I'm root and modded my phone always use stock rom...I am not a fan of custom rom but always modding to the limit...always trying to put something on to maximize it...
Bad luck or not, today I'm trying my luck again to go to Sony center to claim warranty on my defective phone...I have made a factory reset and relock my bootloader...so hoping Sony wont find out...if they did...moneys going down the drain...
Sent from my iPhone using Tapatalk Pro
I think we are to premature to say about issues with root, modified or custom roms because the Zl, Z ,Z1 they are babys come out few mounts ago and all the developers are trying hard to make it fly. I remember my HD2, I get that phone after 2 years of his release and I was flashing tons of roms everyday and I find many powerful and stable roms. So be patient.
eclyptos said:
I think we are to premature to say about issues with root, modified or custom roms because the Zl, Z ,Z1 they are babys come out few mounts ago and all the developers are trying hard to make it fly. I remember my HD2, I get that phone after 2 years of his release and I was flashing tons of roms everyday and I find many powerful and stable roms. So be patient.
Click to expand...
Click to collapse
Well, maybe but i think the problem is not in root or any roms...the phone is just defective..i got mine back from repair and work ok again...
And thats true about old phone...i used some HTC, and Sony's old phone, always flash something, and no problem occur...only todays phone, i always encounter many defects on it...great technology, but also fragile...
Sent from my C6502 using XDA Premium 4 mobile app
as far as i understand, its not because u rooted or unlocked but bcuz of a problem with the battery management syste(BMS).
there appears to be sum fault with battery or the bms, which causes the phone to shutdown.
unfortunately, the only solution is to change the battery. u will have to return ur phone to sony. but to claim warranty, u must unroot and relock the bootloader.
mind you, there is only a small number of phones with this problem.
this same issue happend with my ZL too. i returned and within one week, they returned a brand new phone to me.
mine was fully stock, locked bootloader and unrooted(the previous and the newer too)
new is working awesome.
hope this helps, if it does, u know where the thanks button is!
control freak said:
as far as i understand, its not because u rooted or unlocked but bcuz of a problem with the battery management syste(BMS).
there appears to be sum fault with battery or the bms, which causes the phone to shutdown.
unfortunately, the only solution is to change the battery. u will have to return ur phone to sony. but to claim warranty, u must unroot and relock the bootloader.
mind you, there is only a small number of phones with this problem.
this same issue happend with my ZL too. i returned and within one week, they returned a brand new phone to me.
mine was fully stock, locked bootloader and unrooted(the previous and the newer too)
new is working awesome.
hope this helps, if it does, u know where the thanks button is!
Click to expand...
Click to collapse
Was going to say I haven't experienced this issue... and my phone is rooted and unlocked...
Hi
Had the sds bug kill my n7100 and Samsung wouldn't fix under warranty saying the phone is scratched and therefore no warranty, amazing how easy it is to turn a fan into a hater but that's unrelated to this post.
After a private lab replaced my emmc they warned me not to flash a new rom but when I asked why they couldn't give me a proper explanation hence my post.
Can anyone elaborate more about this and explain what the risks are and what the reproductions are in flashing a new rom like omega for example? I'm fairly technical and have good knowledge about flashing roms restoring efs etc. So a technical explanation will be extremely appreciated.
Thanks
Sent from my GT-N7100 using Tapatalk
eMMC erase bug is related to Samsung's fault. The firmware versions >4.1.2 are belived to be safe. Check the threads about SDS here, there are more than just one.
In fact, the bug fix been done by a patch that gets loaded by each boot. One for the OS, one for the recovery mode. Most of the custom kernels or ROMs made for N7100 feature the SDS fix patch.
Actually, you should definitelly flash another ROM. Try to avoid using recovery mode before you have flashed safe rom or kernel. Any action done in the recovery mode with insane chip and android ver. earlier than 4.1.2 may cause sudden death of the device.
It is simply unacceptable insolence of Samsung to try to hide from customers the fact that SDS is a big, embarrassing faoult of themselves. Yes, they are searching for even a smallest scratch and try to convince people that THAT is a reason for sudden death. LOL! Just insist that the www is overfilled with information about that. Also i9300 has it, N7000 has a hard brick bug.
Saying that, I just have bought a new n7100 as it is amazing device with one of the lowest SAR values among all ever made cell phones. Strong reason to own it, especially now when the price has dropped after Note 3 is released.
Thanks for your answer, the lab actually replaced the emmc to the a sane chip now, shouldn't be hitting sds anymore.
They said that because this is not the original emmc it could cause problems when flashing roms, I was wondering why they would say that.
Sent from my GT-N7100 using Tapatalk
petelking said:
Thanks for your answer, the lab actually replaced the emmc to the a sane chip now, shouldn't be hitting sds anymore.
They said that because this is not the original emmc it could cause problems when flashing roms, I was wondering why they would say that.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Where did you get it fixed at? Thanks
Sent from my iPhone using Tapatalk 2
Local shop here in Israel
Is Israel there is common KASTAH policy for every fixed device.
Do nothing or have your own KASTAH ready. Not our business...
Sent from my GT-N7100 using Tapatalk
So you are saying this is just kisuy tachat?
im dealing with this Note 4 from verizon for someone right now and i cant get to do anything with this damn locked bootloader!
due to a unrelated issue i upgraded the phone to LP and now i cant root. but to make matters worse the brightness cant be lowered. i read how to fix it but i need a custom recovery to install the zip, i cant install a custom recovery because i cant root.
i tried downgrading but i cant because of the bootloader (Bootloops at verizon logo). cant install mulitsystem because of no root because of that bootloader. its a infinite loop. as much as i want root ill settle for fixing the brightness.
Turn on power saver mode. It dims the screen
What do you mean it won't lower? Restart device than try. Factory reset and see if lowers. If still no, get replacement device.
Sent from my SM-N910V using XDA Free mobile app
Turning on power savings didn't work.
And factory resetting also does not work.
The phone is OK, brightness control works in kk but it's a bug of upgrading to lollipop it's even stated in the list but below the list is a fix zip but I can't flash it because of no custom recovery
Sent from my C6902 using Tapatalk
I'm activating this phone and I feel like this is really going y drain the battery. Any help?
Sent from my C6902 using Tapatalk
xdarkmario said:
I'm activating this phone and I feel like this is really going y drain the battery. Any help?
Sent from my C6902 using Tapatalk
Click to expand...
Click to collapse
Request a replacement from Verizon. I have never heard of brightness issues with Lollipop
I can't send this to verizon I brought from eBay and replaced a part inside. And I force update to lollipop, no ota. It's a common issue with this phone if you update but I was supposed to root then update.
Sent from my C6902 using Tapatalk
xdarkmario said:
I can't send this to verizon I brought from eBay and replaced a part inside. And I force update to lollipop, no ota. It's a common issue with this phone if you update but I was supposed to root then update.
Sent from my C6902 using Tapatalk
Click to expand...
Click to collapse
Do you pay for total equipment coverage? If so none of that should really matter. Unless you modified the phone i doubt they will notice a replacement part.
drewcam888 said:
Do you pay for total equipment coverage? If so none of that should really matter. Unless you modified the phone i doubt they will notice a replacement part.
Click to expand...
Click to collapse
sure didn't. i brought the phone full knowing all responsibility for it. but sending it ti repair is totally out of the question, that would leave me phone less for some time. and plus i kind of have a thing against sending things in for repair 0_0
i assume unless someone knows otherwise i guess ill have to wait for a ota to fix it.
xdarkmario said:
sure didn't. i brought the phone full knowing all responsibility for it. but sending it ti repair is totally out of the question, that would leave me phone less for some time. and plus i kind of have a thing against sending things in for repair 0_0
i assume unless someone knows otherwise i guess ill have to wait for a ota to fix it.
Click to expand...
Click to collapse
When people were having a problem with this they were using a program called lux brightness in the Play Store.
cam1pbell said:
When people were having a problem with this they were using a program called lux brightness in the Play Store.
Click to expand...
Click to collapse
Heeey that did the trick! Thanks
Sent from my C6902 using Tapatalk