Hey guys
I am having an issue lately. My phone seems to be turning off randomly. It happens in my pocket most of the time, but one time i just left it on my desk, and a couple of hours later the phone was off for no reason.
Is this a common problem? I cannot bring this phone back, because I have bought it from someone else, and not from a shop.
Can it be linked to the power button? From my understanding is that the phone reboots itself instead of turning off when you hold the power button for a couple of seconds.
Thanks in advance.
Verstuurd van mijn GT-N7100 met Tapatalk
Chileno4Live said:
Hey guys
I am having an issue lately. My phone seems to be turning off randomly. It happens in my pocket most of the time, but one time i just left it on my desk, and a couple of hours later the phone was off for no reason.
Is this a common problem? I cannot bring this phone back, because I have bought it from someone else, and not from a shop.
Can it be linked to the power button? From my understanding is that the phone reboots itself instead of turning off when you hold the power button for a couple of seconds.
Thanks in advance.
Verstuurd van mijn GT-N7100 met Tapatalk
Click to expand...
Click to collapse
I hope it is not a symptom of a dying Note 2 because of the SDS (Sudden Death Syndrome).
Try updating to the latest firmware immediately and hope it sorts the problem.
What kernel are you running? Redpill kernel had/has some SOD issues where the phone won't wake up and needs to be turned off by holding the power button down, it may be something similar.
Sent from my GT-N7100 using xda premium
I'm not rooted, just running STOCK 4.1 Touchwiz. I ran eMMC check and it seems that I'm affected by the bug. What are my options? Does 4.1.2 fix this issue? Can I fix this issue without rooting?
owl74 said:
I hope it is not a symptom of a dying Note 2 because of the SDS (Sudden Death Syndrome).
Try updating to the latest firmware immediately and hope it sorts the problem.
Click to expand...
Click to collapse
It a "sudden death syndrome" meaning there are no symptoms. One minute your android is all nice and cuddly with you, you turn around to grab that fresh packet of durex and the next its lying dead with its tongue sticking out. Lol
Sent from the Rabbit Hole
Chileno4Live said:
I'm not rooted, just running STOCK 4.1 Touchwiz. I ran eMMC check and it seems that I'm affected by the bug. What are my options? Does 4.1.2 fix this issue? Can I fix this issue without rooting?
Click to expand...
Click to collapse
U better update it the latest dll7 if its not out for ur country yet download the firmware from Sam mobile and flash it with odin
Sent from my GT-N7100 using Tapatalk 2
I don't know if I should wait. I don't have the update yet in my country. The closest country to mine is Germany. The CSC is different though. Also, do I lose all my data as in a factory reset?
Verstuurd van mijn GT-N7100 met Tapatalk
Chileno4Live said:
I don't know if I should wait. I don't have the update yet in my country. The closest country to mine is Germany. The CSC is different though. Also, do I lose all my data as in a factory reset?
Verstuurd van mijn GT-N7100 met Tapatalk
Click to expand...
Click to collapse
A factory reset would make your Contacts, messages and other accounts go "boom".
No data would be wiped though so your pictures, media files will remain intact
The issue is not software related. It is most definitely hardware. The phone is flawed and shuts off on it's own under various conditions, all hardware related. I am not able to post externally due to not having enough posts yet. However, I have had the same issue on 3 Galaxy Note 2's from Verizon. I made a video that shows exactly what is going on and posted it on the following website...
wwwDOTgalaxynote2shutsoffDOTcom
You will have to paste that link in to a new browser and replace the DOTs accordingly to get to it, but once you see the video, you will be enlightened. Be sure to read the details I provided on that site as well. They go in to detail about the problems that I have had and the lack of proper support that Samsung is willing to provide.
Related
Sometimes the screen of my Galaxy Nexus freaks out; it behaves as if I'm touching the screen repeatedly while I'm not. It does not happen a lot, but I think it mostly occurs after pulling down the notification menu and touching a notification message there.
I have tried to reproduce this behavior (camera ready so I can video the screen of my GN), so far no luck. Anybody else experienced this?
Of course, as soon as I'm in bed and have put my camera away I experienced the issue again.
Will try again this evening.
That really sounds like a faulty screen I'm sorry to say. I had a similar issue with my HD2 two years ago, had to send it for replacement.
Hmmm I hope not. Since it's very hard to reproduce I doubt I can prove it in order to get a replacement.
It happens to me only when I'm charging the device. Do you use custom ROM? I'm suspecting that right now.
Nope, stock rom. I haven't even rooted it yet.
Finally caught it on video! It's not very focused but it clearly shows my problem.
http://www.youtube.com/watch?v=Z5_tUcosrtQ&feature=youtu.be
I don't think its a hardware problem because I'm mostly experiencing this problem at home. Today at work I used the phone the whole day without encountering this behavior. I'm 15 minutes home and the problem pops up again. Difference? At home the phone is connected to my WiFi. Any thoughts?
Does it happen when you're not holding the phone? I've had anomalies happen before when the phone is on table and not in my hand before. Or could be faulty driver for touchscreen chip.
Sent from my Galaxy Nexus using xda premium
@rbiter said:
Does it happen when you're not holding the phone? I've had anomalies happen before when the phone is on table and not in my hand before. Or could be faulty driver for touchscreen chip.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
No, it does not happen spontaneously. I happens when I'm using the phone.
I've read some threads for other devices concerning exact the same issue. There were opinions that it could be due to the static charge that gathers on the sensor.
Possible solution could be:
1) discharge the phone
2) remove the battery and wait for about 10-12 hours.
Try it may be it ill help you.
stopdogs said:
I've read some threads for other devices concerning exact the same issue. There were opinions that it could be due to the static charge that gathers on the sensor.
Possible solution could be:
1) discharge the phone
2) remove the battery and wait for about 10-12 hours.
Try it may be it ill help you.
Click to expand...
Click to collapse
Sounds like a longshot, but I will try it anyway. Thanks!
Reflash the phone with stock images and do a wipe if it still persits exchange it asap
Sent from my Galaxy Nexus using Tapatalk
noobdeagle said:
Reflash the phone with stock images and do a wipe if it still persits exchange it asap
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
The phone has a stock image. Also it's not rooted and I haven't touched the bootloader either.
I recently bought a new note 2, and everything was good and I love it!
But yesterday I was on the phone to a friend and initially I tried putting him on speaker phone, but the screen wouldn't turn on, only the soft touch keys at the bottom lit up. I thought nothing of it and continued my phone call.
It wasn't until he hung up I noticed i still coudn't the damn thing on. So i removed the battery and re inserted it. Here's where things get interesting though, now whenever i try to power it up, i get a little red light in my proximity sensor (i think) that flashes for about half a second.
I've tried soft rest, which does the same thing ( makes the proximity sensor light up for half a second)
Hard reset which does the same thing.
I haven't rooted the phone or anything. Luckily its still under manufacture warranty and I'll get samsung to have a look at it, but any thoughts on what it could be?
soljakid said:
I recently bought a new note 2, and everything was good and I love it!
But yesterday I was on the phone to a friend and initially I tried putting him on speaker phone, but the screen wouldn't turn on, only the soft touch keys at the bottom lit up. I thought nothing of it and continued my phone call.
It wasn't until he hung up I noticed i still coudn't the damn thing on. So i removed the battery and re inserted it. Here's where things get interesting though, now whenever i try to power it up, i get a little red light in my proximity sensor (i think) that flashes for about half a second.
I've tried soft rest, which does the same thing ( makes the proximity sensor light up for half a second)
Hard reset which does the same thing.
I haven't rooted the phone or anything. Luckily its still under manufacture warranty and I'll get samsung to have a look at it, but any thoughts on what it could be?
Click to expand...
Click to collapse
Well, I can tell the that the red light is normal, I get that too and its just because its booting up, when you turn your phone on, what happens exactly?
Thanks for the reply. When I press the power button, around a second later the red light blips for half a second and turns off, but the OS doesn't boot up and nothing happens.
soljakid said:
Thanks for the reply. When I press the power button, around a second later the red light blips for half a second and turns off, but the OS doesn't boot up and nothing happens.
Click to expand...
Click to collapse
Hmmm, This is the first time I heard of a situation like this... Try searching on the site or probably wait for someone to reply....
http://forum.xda-developers.com/showthread.php?t=2065626
Maybe you too.... Sorry that sucks.
This PSA was sent Flow style from my Note 2 N-7100
Now i am really getting worriyng about this, does note2 has started SDS ?
atleast 3-4 cases are reported with same symptoms.
Anyway can you tell
You were on which ROM when this happened?
Are you getting to reboot in recovery/download mod?
@dingokevin I had a read over the thread you linked, and I fear the worst has happened to my note 2. This seems like a serious issue and even a flaw with the motherboard perhaps? Thank the lord it is still under warranty. R.I.P old friend.
@dr.ketan Im not sure what SDS stands for... Yeah I was running stock touchwiz 4.1.1 I think. No modifications and no root what so ever, and nope :/ I tried holding down volume down key + home button + power but no cigar, just the proximity light flashes briefly.
SDS - sudden death syndrome
And if you are unable to get into download/recovery mode then nothing can be done except send it to service station. it highly suggests sudden death which is very known issue for SGS3.
Replying to your query at other thread, you will get motherboard replacement if it is under warranty.
Ahh thats probably whats happened then. Thanks guys, I'll send it off to samsung and have a word or two with them to see why this is happening to many people!
If possible share outcome here too.
Regards
dr.ketan said:
If possible share outcome here too.
Regards
Click to expand...
Click to collapse
Yeah defiantly will do. (Y) cheers
Same thing happened to my friends note 2 and some other people. Is sds happening to the note 2 also now ?? I am very worried
Sent from my GT-N7100 using xda premium
Or could be that screen was damaged somehow.
Sds bug generally happened due to long time in sleep mode.
It happened to him during call
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
Or could be that screen was damaged somehow.
Sds bug generally happened due to long time in sleep mode.
It happened to him during call
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I was just reading up on some possible causes here on XDA with peoples S3's and someone suggested corrupted NAND memory.. I think this maybe the case because before the phone call I had installed Gangster Rio (which i honestly did purchase off the play store, hand on heart) and after playing it for a while decided to un install it and get a refund. Could me doing this have caused the NAND memory to corrupt? The game is a pretty large file...
No imao no
Sent from my GT-N7100 using xda app-developers app
UtkarshGupta said:
No imao no
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I highly doubt it was screen damage, imho. I only received the phone last friday and have been cradling it like a fragile little baby, Its never been out of my sight lool.
Maybe i just got really unlucky and ended up with a faulty device.
If screen fault then in such case usually you can hear boot up sound. It seems your case very well fits to sds category only.
Sent from my GT-N7100 using xda premium
dr.ketan said:
If screen fault then in such case usually you can hear boot up sound. It seems your case very well fits to sds category only.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
Thank you good Dr. =P
dr.ketan said:
If possible share outcome here too.
Regards
Click to expand...
Click to collapse
Hi Guys,
Got up this morning having left my Note 2 turned on and on charge overnight to discover this same fault -
slow flashing Red light and phone totally dead.
Unable to do anything to rectify the situation.
Still under warranty of course, phone only released in October 2012.
Is this a fault with the phone which necessitates replacement or just a battery problem?
Would be grateful for any advice / guidance / help.
Thanks,
Mike Longley.
MJLONGLEY said:
Hi Guys,
Got up this morning having left my Note 2 turned on and on charge overnight to discover this same fault -
slow flashing Red light and phone totally dead.
Unable to do anything to rectify the situation.
Still under warranty of course, phone only released in October 2012.
Is this a fault with the phone which necessitates replacement or just a battery problem?
Would be grateful for any advice / guidance / help.
Thanks,
Mike Longley.
Click to expand...
Click to collapse
It seems also like SDS send it to Repair AFAIK is a chip problem, not battery so you can't do anything to repair it. If it is under warranty and with counter at 0 send it. They must repair it.
Enviat des del meu GT-N7100
Hi I have a galaxy s3 running the liquid smooth rom, and I think I have a power switch problem. Yesterday I woke up and pressed the power button and the phone just powered off. Now my phone will shutoff as soon as it boots up. It will only take 10 seconds for the phone to turn off. When I take the battery out and put it back in, the phone will boot on it's own. I took the phone apart and removed the power button to see if that was the problem and that didn't solve it. so I believe it's the actual power switch on the motherboard. Anybody know a fix or if I am giving the wrong diagnose.
Are you rooted? Try to flash a ROM to see if it may be a software problem. Unless the power button is stuck on the pressed position, which shouldn't be true since you checked it. Let me know how it goes!
Sent from my Illūsîøn'd Galaxy S³
Sounds like you're on the right track. Not sure of a fix though, sorry. Warranty? Insurance?
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
Sounds like you're on the right track. Not sure of a fix though, sorry. Warranty? Insurance?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
lol no warranty or insurance. I think I'm going to have to find someone who is skilled enough to put a new switch on the motherboard. If I do fix, I'll people know. I see people have had this same problem and thinks its the Sudden Death Syndrome and it's not. Maybe I'll make a video or something if it goes well
I'm pretty sure the sudden death only affected the international models on esrly firmware builds.
Looking forward to hearing if you get it fixed! Good luck!
Sent from my SGH-T999 using xda premium
1st possibility: power button got stuck
2nd possibility: sudden death syndrome (but I think it can be lesser possibility 'cause SDS was fixed from Android 4.1.2 version and only international Galaxy S3 models has SDS possibility,so if you use international model you're on the wrong forum, if not I doubt that it can be SDS )
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.
I have an HTC One V that mirrored and flipped everything after I did a factory reset. So when it boots, it boots flipped and mirrored. Also the bootloader is flipped and mirrored. Before the factory reset everything was working fine...
The touchscreen remains normal. So it's almost impossible to tap the right buttons. Anyone that has a solution or at least a cause?
Verstuurd vanaf een Galaxy Nexus met CM10
Not one other device with problems...?
Verstuurd vanaf een Galaxy Nexus met CM10
I've never heard if this happening. What recovery and ROM are you running
Sent from my PK7630000 using xda app-developers app
Everything stock. Got it from a friend who thinks I can fix it, but I don't think I can. Everything I read about Android devices that cope with this issue are sent back for repair under warranty. But this one doesn't have warranty anymore...
Verstuurd vanaf een Galaxy Nexus met CM10
Lex_Michdeandroid said:
Everything stock. Got it from a friend who thinks I can fix it, but I don't think I can. Everything I read about Android devices that cope with this issue are sent back for repair under warranty. But this one doesn't have warranty anymore...
Verstuurd vanaf een Galaxy Nexus met CM10
Click to expand...
Click to collapse
Can you upload some pictures? Not screenshoots, pictures taken to the working phone? I HAVE TO SEE IT!!!
I want too
Well, you're all a bit unlucky. The guy came and picked it up, before I got to take pictures of it. I'll ask him if he can take some for you guys.
Verstuurd vanaf een Galaxy Nexus met CM10
Some pictures...
He took a few pictures for me (you) to 'enjoy'...
Lex_Michdeandroid said:
He took a few pictures for me (you) to 'enjoy'...
Click to expand...
Click to collapse
the display inside seems messed up, red appears as blue on the photos..
was it dropped?
you might need a new one.
MameTozhio said:
the display inside seems messed up, red appears as blue on the photos..
was it dropped?
you might need a new one.
Click to expand...
Click to collapse
Well it's not mine. A friends kid got it from his mom. Don't know if it was dropped, but it was a used phone. The guy told me it was fine when he got it, but after a factory reset it flipped the screen. Don't know about the colors, haven't seen this HTC without this problem, so I only know it showing these problems. A few pictures of a normal one for reference perhaps? He didn't mention it was dropped.
It's not really important anymore, as the kid gave it back to his mother and he was promised a new one. A bit annoying, because he manages to break a phone a month and I get to try to fix them...
Verstuurd vanaf een Galaxy Nexus met CM10
Lex_Michdeandroid said:
Well it's not mine. A friends kid got it from his mom. Don't know if it was dropped, but it was a used phone. The guy told me it was fine when he got it, but after a factory reset it flipped the screen. Don't know about the colors, haven't seen this HTC without this problem, so I only know it showing these problems. A few pictures of a normal one for reference perhaps? He didn't mention it was dropped.
It's not really important anymore, as the kid gave it back to his mother and he was promised a new one. A bit annoying, because he manages to break a phone a month and I get to try to fix them...
Verstuurd vanaf een Galaxy Nexus met CM10
Click to expand...
Click to collapse
fun
well the kid probably dropped it and it just took a bit for the display to go defective..
If it was really just after a factory reset you can try to RUU it but it doesn't seem that way. If he dropped it I don't think it's just a display damage it's more likely something on the motherboard. Or maybe the connector unplugged a little
Sent from my HTC One V using xda app-developers app
I wish I had the chance to open it up... His other phone fell in the bathtub and he then hid the phone somewhere because he was afraid he would get into trouble. Of course not taking it apart immediately and putting it on rice... His father keeps thinking the water damage is fixable...
Verstuurd vanaf een Galaxy Nexus met CM10
Lex_Michdeandroid said:
I wish I had the chance to open it up... His other phone fell in the bathtub and he then hid the phone somewhere because he was afraid he would get into trouble. Of course not taking it apart immediately and putting it on rice... His father keeps thinking the water damage is fixable...
Verstuurd vanaf een Galaxy Nexus met CM10
Click to expand...
Click to collapse
how old is this kid xP
MameTozhio said:
how old is this kid xP
Click to expand...
Click to collapse
In my opinion not old enough to have a mobile phone. But maybe I'm the one who is getting too old.
guys, I dropped my HTC one v today. though it was working well untill I did restart it for some other reason. . n den it started showing the same characteristics as mentioned in above posts. display flipped and mirror imaged. touchscreen working as if display is not reversed. so operating that cell is difficult. . ofcrs colour s also got messed up. exactly nsame issue as mentioned jn above post.. could anybody bfind solution for this ..?
You are not alone I have my secondary device (HTC One V) and thats too up side down and mirrored. I hope you have some solution for me. I have tried resetting and even I have change my ROM and recovery but not luck. So I believe that it must be some hardware problem. My phone was once damaged very badly and the screen glass is broken already.
Sent from my Z10 using XDA Free mobile app
morfiq said:
You are not alone I have my secondary device (HTC One V) and thats too up side down and mirrored. I hope you have some solution for me. I have tried resetting and even I have change my ROM and recovery but not luck. So I believe that it must be some hardware problem. My phone was once damaged very badly and the screen glass is broken already.
Sent from my Z10 using XDA Free mobile app
Click to expand...
Click to collapse
The display can be mirrored in the kernel, it's really easy. I'll give you a kernel build with mirrored screen when I have some time.
You mean I need to flash another kernel?
Sent from my Z10 using XDA Free mobile app
morfiq said:
You mean I need to flash another kernel?
Sent from my Z10 using XDA Free mobile app
Click to expand...
Click to collapse
If it's a hardware problem and everything is displayed upside down (the bootloader and splash screen also), you can't fix it completely by modifying software. But you can tell your display driver in the kernel to display everything upside down.
This doesn't fix the problem, it's just a workaround and your bootloader, recovery and splash screen will still be displayed upside down.