Related
http://www.xda-developers.com/android/hard-brick-bug-on-galaxy-s-ii-and-note-leaked-ics-kernels/
Maybe someone who is a little more savvy in this field could take a look?
Here is a very good article and discussion about the issue:
http://forum.xda-developers.com/showthread.php?t=1644364
Sent from my SGH-T989 using xda premium
this is kinda scary but so far I never had any problem
We don't even have any kernel source. There is a leaked kernel but that didn't cause any brick in our devices. Also note that the article does not mention sgh t989 or sgh 727 and all its sub variants. If this was the case for us you would see many more "[Q] plz halp I haz brick " threads
Sent from my SGH-T989 using XDA
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
kahm said:
Hey guys. I just came over from the Sprint version of this phone (Epic 4G touch), and while I know that this article dosen't say that it pertains to our device specifically, one of the devs over there got in touch with samsung about the issues. You can see their progress here:
http://forum.xda-developers.com/showthread.php?t=1644364
For those who don't want to read (and I don't blame you if you don't want to, it's heavy stuff and I needed to have it explained to me), long story short: The memory chips (known as the EMMC) in the phone have their own firmware embedded in them, independent of the ROM, kernel, modem, etc. In that firmware, there's a bug that writes a string of zeros to an area of the firmware itself, kind of a self distrusting thing. It's only for certain revisions of the EMMC firmware, and it's only triggered by a specific low-level wipe function that is commonly used in recoveries (I'm not sure which, one of the partition wipes I think), and it for some reason seems to happen more with an ICS based kernel more than in a GB.
Given the nature of EMMC chips and the fact that multiple devices might share these same physical type of EMMC memory chips, it's hard to say how many different kinds of phones and devices might be affected, but it's safer to assume that we might be, rather than to think that we're safe based on this article alone.
There's no official solution as of yet, as far as I know. Samsung has started to patch their 4.x kernels to work around this specific wipe function, thus avoiding triggering the bug, and I think this is because rewriting the EMMC firmware itself is more risky and perhaps harder to do on a wide scale, but again, I'm not sure of their reasons. But, we do know that they're working to find some way around the bugs, and those who built custom kernels also removed/modified that wipe command to work around this bug with success.
Again, I know this doesn't say that it applies to our phones, but because of what was discovered on the Epic 4G touch, I believe that it *may* apply to many, many Samsung phones and devices, and just to be safe, I figure I should share this with you all.
The solution that we were using for time being was: never, ever do any recovery functions from a ICS based kernel/recovery. Always ODIN a GB based kernel/recovery to do what you need to do, then flash the proper ICS back. Kind of tedious, but it worked and prevented me from ever bricking when a LOT of other people were. Food for thought, everyone
TL;DR: You should probably avoid doing anything in an ICS based recovery/kernel on any Samsung device until we hear from them that they've worked out this bug.
Click to expand...
Click to collapse
Finally someone with a brain! Thanks for the post
Sent from my SGH-T989 using xda premium
Scary stuff indeed, has anyone confirmed that our devices (T989) is affected by this bug?
Back on the original Epic we used Odin to get the next version. I think it was 2.1 to 2.2 roms. I've always wondered how safe it was to revert to GB by flashing after installing ICS
Sent from my SGH-T989 using xda premium
[Q] plz halp I haz brick
Disregard. Funny how you figure out your issue just seconds after you post and open yourself up to ridicule.
DOH!
mharmon said:
I seem to have hard-bricked my SGH-T989 phone after flashing task650-aokp-Build-36. I don't know if it's a superbrick, but nothing I can do seems to make any difference. The phone does not seem to respond and does not seem to power off, power on or go into download mode. I have swapped with a known good battery and I know that's not the issue. I've tried using a USB jig and that doesn't help. I've contacted Samsung and I should be shipping it to them Monday.
If anyone has any advice, I'm willing to try anything otherwise I'm going to take my lumps and ship my phone off.
Click to expand...
Click to collapse
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Micronads said:
Pull your battery sd card and sim card out. leave phone sitting with everything pulled for about an hour. put it back together and try again. make sure your battery is charged for sure. it would suck if it was nothing but a dead battery
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
mharmon said:
Thanks for the quick response. I've tried pulling the battery, USB jig, etc. and can't get it to power on, off or go into download mode. I know what I did wrong. I made a rookie mistake and flashed a ROM meant for my AT&T I777. I feel stupid for bricking my phone.
Click to expand...
Click to collapse
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Micronads said:
Sounds like you are fizzucked then. Sorry to hear that. That is what sucks about having different phones and flashing stuff. Got to keep track of what is what.
Sent from my Galaxy SII T-mobile using xda premium
Click to expand...
Click to collapse
Yeah sounds dead to me. Send in for warranty. Oh well, stuff happens. Good luck to you!
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Id rather risk bricking than rock without 4.04
Sent from my SGH-T989 using xda premium
Nobody has said it is necessary applicable to this device.
jim93 said:
Nobody has said it is necessary applicable to this device.
Click to expand...
Click to collapse
You're right, it doesn't say it's applicable to our device. But it also doesn't say our device is one of the safe GS2 variants. As you can see in my signature, I'm also using 4.0.4. And if you read my post history, I recommend it to everyone. I'm just saying that it hasn't been proven safe yet, but there's also no proof its dangerous either.
Sent from my SGH-T989 using xda premium
ICS has been flashed to these phones probably a half million times by now. If it was causing bricks we would have heard about it.
Sent from the iPhone graveyard.
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
Also, people should know that the listed phones in the OP are Exynos based and T989, i727/r and i717 are Qualcomm based. This has been discussed in the skyrocket forums and some devs have explained that.
Just my 2 cents.
kahm said:
I've seen like two threads about bricking in this forum in the last two days. How could you say that there's no proof? I'm sorry to say it but I think everyone is being a little too cautiously optimistic. There's no harm in being safe. If you guys actually read about this, you'd realize that its not ICS causing bricks, its any ICS based recovery.
Click to expand...
Click to collapse
The brick in this thread was due to flashing an i777 rom to a t989. Flashing an i777 rom to t989 regardless of OS will brick your phone.
It seems to be all exynos based, but thanks for the heads up, man.
So I bought my gf a one v and she loves it. One month after using it (stock, unrooted) it just went dead. Doesn't charge and doesn't get into bootloader (but not the QHSUSB_DLOAD and Blank Screen issue). Guy at repair told me that this was an issue with the ICS kernel causing a hard brick. Now, I naturally sent phone for repair since it is a warranty case. So far so good, lets just hope they get it done fast.
My question is though: should I root device and flash another ROM with presumably no such issues so I can avoid a future brick? I mean, I'm using a rooted desire and have no issues for over 2 years, now just didn't want to mess with the new phone of my gf and thought 'hey, lets keep it stock'... But the thought that it would die again after having it repaired is really discouraging. My gf is kind of frustraded and I don't want this to happen again. But are there such issues with custom ROMs for the One V? Like I said, I'm using the good old desire and don't know much about the one v, so I would really apreciate if you can tell me - because if such an issue is possible on custom roms, there is no point to bother flashing and voiding warranty.
Thanks for your time guys!
Well at the moment we have only modified stock ROM for this device and one custom kernel (in beta state) which is still an ICS kernel.
However you''ll never know whether this happens again or not. But one thing you can know for sure is that if you unlock the bootloader and install a custom kernel and ROM and it happens again then your are screwed because you lost your warranty.
Maybe you should wait a bit for some stable custom rom. Because an unstable and buggy ROM would make your gf even more frustrated and andgry
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
1ceb0x said:
1. In no other galaxy, no other planet... IT IS NOT A KERNEL FAULT! it may at well be a piece of poorly made phone. you should get another one from the warranty. I can 100% say that you will not have any problems. The kernel doesn't suddenly causes hard brick to your phone. If it does, do you know how many phones running ICS are there? Or One V's...
I have flashed alpha/beta/final kernels/roms for millions of times, no problems whatsoever.
in no way this is a kernel/soft problem. more likely the flash drive from your gf's phone, died!
Click to expand...
Click to collapse
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
falconyx said:
Thx dude, I was sort of wondering how this could really be a kernel problem, since the guy over at the repair told me so - 'Its a kernel issue with ICS'... well, I hope he was really wrong and the device we receive (hopefully soon) will be proper
Click to expand...
Click to collapse
That guy should really make his homework. In no way a kernel can brick the phone. If this was true, the phone will not boot and work for weeks in the first place. Its not like the kernel has a "time-bomb" inside and it triggers when it is set.
As I said, it is a phone problem, something hardware has failed.
Hopefully it will be fixed for you gf and she will not have any problems in the future.
It happens in India too
My htc one v got bricked suddenly while using it. Forums at internet says it happens if battery charge goes below certain limit. Mine it went down to 24%
It happened to me when my battery level was 14%. now I have to pay 200$ for repairs. (because I live in Iran.)
HTC ONE V dead
falconyx said:
Oh well, thanks for the insight my friend..So, If I got this right, if I root and flash one of the current roms and it bricks again, I will still not be able to acces bootloader? And is this really a kernel issue with ICS? I'm willing to even flash a GB rom, if it is possible, in order to avoid this...gf won't mind for sure lol, if this delivers a stable phone in the future
P.S. Does this even happen with other ICS roms/on other stock ICS devices? Or did HTC just screw up on this one? I can understand a phone bricking when changing hboots or other tinkering, but just dieing like that is pretty damn stupid. And from what I read it happens to quite a few other one v users...Hope noone of you guys gets to experience this crap
Click to expand...
Click to collapse
Hi My HTC one V just died , I didn't know how it was happened . 10 minutes before I made I call and just after sometime It stopped working .
Even it is not charging at all, mobile is out of warranty. don't really know what to do ..
Any suggestion would be appreciated .
Regards
Manoj
Hey guys. I'm just coming to the 4g touch after hard bricking my Fascinate. I'm a little hesitant to flash an ICS rom on this thing after the brick. From what I'm reading here it seems ICS roms on this phone are even less stable than they are on the Fascinate and causing a lot of hard bricks.
Really the only differences I noticed in ICS were the ability to pull down the notifications bar from the lock screen(which I absolutely loved) and the panorama camera option which can be had using Camera ICS. Is there something else I'm missing?
With better battery life, better performance and stability in GB, what brings you to ICS prior to source being released?
iztel said:
Hey guys. I'm just coming to the 4g touch after hard bricking my Fascinate. I'm a little hesitant to flash an ICS rom on this thing after the brick. From what I'm reading here it seems ICS roms on this phone are even less stable than they are on the Fascinate and causing a lot of hard bricks.
Really the only differences I noticed in ICS were the ability to pull down the notifications bar from the lock screen(which I absolutely loved) and the panorama camera option which can be had using Camera ICS. Is there something else I'm missing?
With better battery life, better performance and stability in GB, what brings you to ICS prior to source being released?
Click to expand...
Click to collapse
The risk of bricking has been minimized through the hard work of our Devs and programming community. If you thoroughly read and follow posted installation instructions you aren't likely to brick.
People mainly brick when they get in a rush, or try and take short cuts or simply disregard posted instructions.
There are plenty of enhancements in ICS over GB, I'd suggest people flash a ROM and explore them for yourself. Just read, read, read and ask questions before you ever take any step you are unsure of.
I'll agree with Esoteric68 here. She's spot on about the 'brick' issue. Do you research before you do anything!
As to the why of it? This is xda developers the people here tend to be into tweaking (in the non-meth sense) with technology and like to ride the bleeding edge of technology or squeeze out the most from the old stuff.
I've like the ICS builds for some of the items you've mentioned. Plus I get to stay ahead of the curve, as it where with my technology. Myself I've only had one application that won't support ICS and found another one to supplant it. I like the smoothness and tweaks I can do with ICS.
There are some really great developers here and some awesome ROMs to play with. Just, as already mentioned, read 1st and be careful.
I was scared to flash ICS for a couple months because it wasn't official but I've done my research like everyone says to do. I can't tell you how many times I've flashed ICS roms this past week, not one scare. Just read up and do as the devs say and you'll be good. If you're not sure, ask questions.
I've got the same question as the op roughly. I know that it isn't much of a risk flashing ICS nowadays, but am wondering what in ICS was worth it for people to make the change. I've looked around and don't see too many features really that I don't see in GB so i feel like i'm missing something.
I'm also one who appreciates all the work the devs do to put together these roms for all of us with all the tweaks they put in. Like I mentioned I'm just now waiting to get my 4g touch in the mail tomorrow after bricking my Fascinate. I had been running a number of ICS roms on my Fassy prior to the brick and while I loved playing with them it seemed like the tweaks the devs put into the roms were unrelated to the actual update of the OS. I had been flashing roms for that phone since the early Froyo days so I had thought I had a pretty good idea of what I was doing and always read the proper way to flash things but then one fateful day I tried to flash the latest MIUI coming from MIUI 1.2.9 and ended up with a bootloop, I think I forgot to wipe date/cache. No problem I thought, this has happened before, just ODIN stock and start over. But then something went terribly wrong in ODIN and now I'm left with a phone that won't turn on, won't charge and comes up as "unrecognized" on my pc. If I could just get it into download mode I could save it but I haven't been able to. Now it's got me a little more cautious of what I flash and how often I'll be flashing.
Maybe the devs can answer this since they know more about insides of the OS. Are there things you can modify in ICS that were not possible in GB?
There is a very long and technical thread about the ICS 'super bricking' issue here: http://forum.xda-developers.com/showthread.php?t=1644364
Basically Sammy screwed the pooch with the way ICS kernels make(s) calls to wipe partitions, particularly the EMMC controller.
It's actually a 'hard coded' firmware thing. But since it is firmware, it should be fixable via a firmware flash. It's just we don't really have that code access from Sammy and they seem to be dragging their feet on this.
There are even OTA updates in Europe (France primarily) that are superbricking a load of Galaxy Notes!
sfhub, Entropy512, garwynn and others with way more skills than most are on it. Esoteric68, robertm2011 and a few others took the risk and spent the time to test the workarounds and fixes that were put together. And you'll see from all the activity here that if caution is used you can pretty safely flash away. Since I've had time this week I've actually flashed about 8 different ROMs and restored nandroids too.
Just keep in mind to read the OPs of any ROM and follow their flashing instructions, read the 'how not to brick' stickies etc.
sfhub, chris41g and Agat put together some great 'safe' kernels.
If you're truly worried you can always use sfhub's one-click to get you to a stock FF18 build - kernel, ROM and modem at one shot.
ICS builds are really quite different in the structure to GB. So yes, as a developer, there are a few more things you can do. It's just a matter of figuring out where things are.
Good luck and have fun!
my location services and gps were horrendous with the el29 update, on ICS its soooooo much better, that made it worth the risk to me
I read and read and read and read a little more until I no longer saw it as a risk. It became more of a "why not?" Now that I have experienced ICS I will never go back. I really like the streamlined multitasking. I think that is the prominent feature. :cyclops:
The old adage is: Don't fly higher than your willing to fall.
In this situation, practice techniques, development and ROMs on a device you're not afraid of bricking. Consider it a "tool of the trade". The OLED phones are starting to appear in pawn shops for little money.
I have asurion insurance and am trying to find a reason to use it so I didn't waste my money
Sent from my SPH-D710 using Tapatalk 2
By far my favorite feature is the swipe away notifications. The few times I have been back on GB that was the first thing that bothered me. I can never go back. Especially after tasting AOSP. TouchWiz is trash for me. I suggest you try CM9 or AOKP. Both excellent ROMs with great support right now. There are many more reasons why ICS is superior, depending on preference I suppose, but the bottom line is at this point, with safe recoveries being released, your chance of bricking are I'd say slim provided you follow instructions. I have flashed probably 40 Roms over the last few months. Only time I soft bricked was cause I tried to cowboy up and not follow directions...
Sent from my SPH-D710 using xda premium
I'm confused. Whats the risk?
ICS is dead simple to install if you know how to read.
(genuinely curious seeing as i've had ICS (in different forms) on my E4GT since it was possible. Currently on CM9.)
Yep I echo everyone's advice. Ask questions!
I got the phone a month ago and remember starting a thread asking a ton of questions and I got all the help I needed.
Flashing roms and the terminology (had never heard of Odin) was completely different from the last phone I had, so I am glad I did my homework before taking the plunge.
Sent from my SPH-D710 using XDA
There's no risk...
Sent from my SPH-D710 using Tapatalk 2
It is safe to flash ICS using ODIN and the newer recoveries. FF18 should be safe, I used it a few times, el26 is the recommend kernel/recovery to flash any cwm zip with as far as anything that includes wiping partitions.
Just remember ODIN ODIN ODIN!
Flash ICS based roms at your own risk, stay away from wipe data/factory reset on any ICS rom until it has been confirmed working on new roms. When using other ICS roms and you are not sure, DO NOT FACTORY RESET OR WIPE DATA. USE ODIN TO GET BACK TO A SAFE KERNEL.
Sent from my piece of crap Zio until i get a replacement E4GT using XDA Premium app
What risk? Read the how to's and no so how to's, and the risk gets eliminated.
Sent from my SPH-D710 using xda premium
Watch this thread... Soon there should be no risk at all!!!
http://forum.xda-developers.com/showthread.php?p=28400468
Sent from my SPH-D710 using xda premium
HELP
Can anyone tell me if it is safe to install a build version of ICS to my already flashed epic 4g touch? Any help its greatly appreciated!
Thanks
ICS isn't where you get in trouble. Its going back to gb or doing a factory reset wipe. Use calks wipe all instead of using wipes in an ICS recovery and you will be golden. Read the how not to brick my phone thread if you are really paranoid.
Blu Kuban
Its what all the cool kids are using.
Noob trolled the troll that tried to troll the Noob.
~~~coal686~~~
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...
I rooted my deviced on the second day that I took it out of the box, so I didn't play much with completely stock rom. However, I could still notice that after rooting, the fingerprint sensor wasn't as fast as it was. Today I flashed May factory image, because I have been facing some problem and I have to say, that IT FEELS LIKE A DIFFERENT PHONE. In a positive way, of course. With root, when the phones idled for 15mins sometimes it had 2-3 seconds of delay between placing the finger on the sensor and vibration of unlocking. Maybe for some of you it's not of a big deal, but I use it in 99% of unlocks, so it matters pretty much and affects impressions on the phone. Of course, after half an hour I started to feel that anxiety,fear and my hand started to shake, because of not having EXKM. Did you guys noticed those delays? I want to play with complete stock for a couple of days to see how it performs in smoothness and battery life and then I decide what to do.
I thought my mind was playing tricks on me since rooting and going on elemental kernel 4 days ago. But yup, there definitely is a lag in fingerprint recognition after going to sleep for a while.
Hey,
Did it happend with a custom rom like PureNexus ?
Sent from Nexus 5X using Tapatalk.
I haven't tested it with any custom rom yet.
Try before a rom to wipe cache etc.
Then make an backup and flash a rom.
Sent from Nexus 5X using Tapatalk.
I've noticed this too, on stock it was really fast, on stock+elementalx it has some delay
With root and TWRP, all the rest stock, i have not those 2 seconds of delay. It's fast as it should be.
So it must be ElementalX issue then.
Confirming, stock ROM + ElementalX and there's a brief lag here, too.
Might be an ElemantalX issue then yea. No delays with my stock rom + kernel device.
This thread is a perfect example of people that do things to their phones yet have no idea what is happening. It boggles my mind. Its pretty clear that no one here (this thread) knows what root is. If they did, well, they would be the ones posting this.
Simply becoming the root user cant break the fingerprint scanner. That's just ridiculous, asinine, retarded. Being the all-powerful superuser simply means you can make system level changes. It alone cant break things like a gun on a table cant kill someone. If something broke while you were hyped up on root juice, it was your idiot self that did it. Since being root cant just break something, that leaves whatever you did with your newfound godlike powers...or what you blindly flashed with your custom recovery that wields that same power. (READ ME)
So, what did you do with your new abilities? You flashed a glorious, magical kernel (custom kernels are awesome, I'm just dramatizing this a bit). Do you know what a kernel is? Didn't think so. Among other things it contains the hardware device drivers. Yes, you guessed it, the fingerprint scanner is hardware. Its pretty easy to determine that that is the root (lol) of your problem. (READ ME)
The solution is to let the kernel dev know of the issue and help him resolve it, or flash a different custom kernel or the plane jane stock kernel. Problem magically solved.
HERE is a noob oriented article about root you may enjoy reading.
HERE is a slightly more technical one.
I tried not to be to much of a jerk and make it kind of funny yet helpful. If this offended you...go pound sand/salt/crackers/whatever up your delicate a$$. :good: