Develop Bugs

Bad Flash? Constant Blue LED

I flashed a Venum Rom and realized I didnt like it as much as the Mijahz? Slim n Trim well I tried going back to that and after abou ten minutes of it just sitting there doing nothing I pulled the battery, probably a bad mistake. Well now all Im getting is a black screen with constant Blue LED. I tried Power-Volume UP/Down. It doesnt show up on my computer. Im pretty this phone is now a sexy paper weight. Does anybody have any insight on how to fix this?

i know when that happen to me it was bricked couldnt get it to go in to odin mode or anything.. even took it to sprint they ended up giving me a new one because i had insurance

LeKtRiCzzz said:
I flashed a Venum Rom and realized I didnt like it as much as the Mijahz? Slim n Trim well I tried going back to that and after abou ten minutes of it just sitting there doing nothing I pulled the battery, probably a bad mistake. Well now all Im getting is a black screen with constant Blue LED. I tried Power-Volume UP/Down. It doesnt show up on my computer. Im pretty this phone is now a sexy paper weight. Does anybody have any insight on how to fix this?
Click to expand...
Click to collapse
congrats, you have a new expensive paper wight, hope you have fancy paper

Did you flash a GB kernel to wipe and reflash the perivous ROM? or did you wipe on an ICS kernel? (Blue light of death)

Sounds like you did a factory reset with the wrong recovery...just go to sprint and say it won't turn on and you don't know why, you'll get another one for free, if you have tep, 35 if you don't...ALWAYS USE ODIN OR MOBILE ODIN TO FLASH EL26 KERNEL BEFORE FLASHING!!! (I bricked once too lol)
Sent from my SPH-D710 using xda

LeKtRiCzzz said:
I flashed a Venum Rom and realized I didnt like it as much as the Mijahz? Slim n Trim well I tried going back to that and after abou ten minutes of it just sitting there doing nothing I pulled the battery, probably a bad mistake. Well now all Im getting is a black screen with constant Blue LED. I tried Power-Volume UP/Down. It doesnt show up on my computer. Im pretty this phone is now a sexy paper weight. Does anybody have any insight on how to fix this?
Click to expand...
Click to collapse
Unfortunately it sounds like you are a victim of the EMMC brick. Mijjah's Slim-n-Trim is an AOKP based ROM whereas most Venum ROM's are based on TW. These generally require flashing EL26 CWM then flashing the new ROM.
At this point your best bet is to take it in and see if you can get it replaced/swapped.
Good luck!

I know where I went wrong when i flashed the venum it didnt keep the EL26 CWM instead it added its own and I didnt think anything of it. I called sprint and i sould be getting a new one in the mail on mnday

welcome to brick city... I bricked last week and can't afford the $100 deductible for insurance. I'll be sending mine to Samsung for repair soon.
Sent from my piece of crap Zio until i get a replacement E4GT using XDA Premium app

Did the same thing last week. Brick city! You must pay attention to what recovery you are on or this will happen. Took to sprint since blue light of death would not let me get to anything. I paid the 35 and they exchanged it.
Sent from my SPH-D710 using xda app-developers app

The BootLoops continue

Alright. Phone started to act rather weird after my messages were randomly deleted and i went from GB,ICS,and to JB and then back. So i then wiped my phone, went back to stock using the method posted in XDA-Developers T-Mo SGS2's method.After doing so it seemed to be working fine and then i got into a bootloop and thought nothing of it, Wiped the cache and continued.
Worked fine for a couple of Hours and then it went into another bootloop, at least 5-9 times in a matter of 2-3 hours. I was told to do a Darkside Cache wipe, Did so and It worked for about 2 days until it started acting up even worse now. I did ANOTHER complete stock using the same method as mentioned before and it seemed as if that did absolutely nothing.
This is turning out to be VERY frustrating and i wish to have a permanent fix for this..

Seshin said:
Alright. Phone started to act rather weird after my messages were randomly deleted and i went from GB,ICS,and to JB and then back. So i then wiped my phone, went back to stock using the method posted in XDA-Developers T-Mo SGS2's method.After doing so it seemed to be working fine and then i got into a bootloop and thought nothing of it, Wiped the cache and continued.
Worked fine for a couple of Hours and then it went into another bootloop, at least 5-9 times in a matter of 2-3 hours. I was told to do a Darkside Cache wipe, Did so and It worked for about 2 days until it started acting up even worse now. I did ANOTHER complete stock using the same method as mentioned before and it seemed as if that did absolutely nothing.
This is turning out to be VERY frustrating and i wish to have a permanent fix for this..
Click to expand...
Click to collapse
I had these problems and got a replacement and they went away...I'd you have warrantee, i would do that...
Sent from my SGH-T989 using xda premium

djtheraven said:
I had these problems and got a replacement and they went away...I'd you have warrantee, i would do that...
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
Had this phone since December...No warranty .I believe i do have Insurance though

If u have insurance you warranty is not void. Even if it's out of warranty. It will cost 5 bucks
Sent from my SAMSUNG-SGH-T989 using Tapatalk 2

get a fresh download
make sure MD5 sums match, get a fresh download... upon returning to stock you need to wipe the phone as well as human ly or android possible wipe factort wipe system wipe sdcard not external_sd but internal and usb under settings reset wipe usb as well. darside super wipe wipe dalvick. make sure its clean then prceed to odin ... Odin doesnt wipe for you. and after you boot up you cab do darksidecachewipe after a fresh install to fix permissions as well.

Rushing said:
make sure MD5 sums match, get a fresh download... upon returning to stock you need to wipe the phone as well as human ly or android possible wipe factort wipe system wipe sdcard not external_sd but internal and usb under settings reset wipe usb as well. darside super wipe wipe dalvick. make sure its clean then prceed to odin ... Odin doesnt wipe for you. and after you boot up you cab do darksidecachewipe after a fresh install to fix permissions as well.
Click to expand...
Click to collapse
As of Now it seems to be working fine (How it seems EVERY morning after i wake up for about 4 hours or until around 12-1PM)So if it DOES in fact mess up i'll do just this.But can you point me to a fresh Download?I did just get it about a week or two ago from the forums here.Feeling kinda iffy about wiping my internal SD card..But i'll do about everything else if it acts up again.Thanks !

Seshin said:
Had this phone since December...No warranty .I believe i do have Insurance though
Click to expand...
Click to collapse
Isnt there a one year warranty on the SGS2? Also, sounds like a bad power button.
Sent from the pink Unicorn from the Darkside.

LoopDoGG79 said:
Isnt there a one year warranty on the SGS2? Also, sounds like a bad power button.
Sent from the pink Unicorn from the Darkside.
Click to expand...
Click to collapse
Not from what I was told by T-Mo. They said i had an only 30 day warranty

Seshin said:
Not from what I was told by T-Mo. They said i had an only 30 day warranty
Click to expand...
Click to collapse
Contact Samsung, though you will need a receipt.
Sent from the pink Unicorn from the Darkside.

Seshin said:
Not from what I was told by T-Mo. They said i had an only 30 day warranty
Click to expand...
Click to collapse
I had the phone for 5 months and it costs 5 bucks... it's a year warrantee not 30 days...you have 30 days to return the phone when you bought it probably..and if you fave insurance then you can return any time
Sent from my SGH-T989 using xda premium

GSIII will not turn on

I just rooted and installed the JellyBomb rom for the GS3 for a friend. They didn't like the rom, so I remembered that there was a GS3 version of Android Revolution HD. I flashed the phone and hit reboot in TWRP and now nothing. I realized just now that the roms are different for the carriers but I possibly installed a rom for a different carrier. Nonetheless, the phone still isn't doing anything. It won't power on. I get no screen. Nothing. Is it completely bricked? How can I at least get back to Download mode for Odin?

MrAutomatic said:
I just rooted and installed the JellyBomb rom for the GS3 for a friend. They didn't like the rom, so I remembered that there was a GS3 version of Android Revolution HD. I flashed the phone and hit reboot in TWRP and now nothing. I realized just now that the roms are different for the carriers but I possibly installed a rom for a different carrier. Nonetheless, the phone still isn't doing anything. It won't power on. I get no screen. Nothing. Is it completely bricked? How can I at least get back to Download mode for Odin?
Click to expand...
Click to collapse
Good friend. You bricked his phone. Way to not read.

The Root said:
Good friend. You bricked his phone. Way to not read.
Click to expand...
Click to collapse
That's all you have to say? Can I unbrick the phone?

MrAutomatic said:
That's all you have to say? Can I unbrick the phone?
Click to expand...
Click to collapse
Nope, probably should have done some more research before breaking someone else's phone for them. Hope you got a good job cuz I'd make you buy a brand new one
I like to break stuff!

-EViL-KoNCEPTz- said:
Nope, probably should have done some more research before breaking someone else's phone for them. Hope you got a good job cuz I'd make you buy a brand new one
I like to break stuff!
Click to expand...
Click to collapse
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.

It's bricked if it was an international version Rom. There's usually nothing you can do. Hopefully your friend can take it back to store say it was doing update and it never came back on. I hope he's a good friend. You can't get back into download mode at all because the partitions are different and your download and recovery are no longer in existence.
Transmitted with a portable device using Xparent Blue Tapatalk 2

edfunkycold said:
It's bricked if it was an international version Rom. There's usually nothing you can do. Hopefully your friend can take it back to store say it was doing update and it never came back on. I hope he's a good friend. You can't get back into download mode at all because the partitions are different and your download and recovery are no longer in existence.
Transmitted with a portable device using Xparent Blue Tapatalk 2
Click to expand...
Click to collapse
Thank you for giving me a real explanation and not just running your mouth. She works for the carrier so she won't have an issue getting the phone replaced. I just hate inconveniencing them. It's just ridiculous that everything went smooth up until that point. What I don't understand is why the phone won't even power back on, at all, but oh well. She says they can have another to her within a day.

MrAutomatic said:
Thank you for giving me a real explanation and not just running your mouth. She works for the carrier so she won't have an issue getting the phone replaced. I just hate inconveniencing them. It's just ridiculous that everything went smooth up until that point. What I don't understand is why the phone won't even power back on, at all, but oh well. She says they can have another to her within a day.
Click to expand...
Click to collapse
here ill explain on the International S3 their Kernel partition is stored where on the US variant our bootloader is stored. So when you flash a international rom it wipes your bootloader because thats where the kernel goes on the international

This same thread will come up in about five hours. I will insult that person too. Learn what you're doing. I'm tired of these threads and they won't ban people who do this. I don't think you should be doing custom stuff to phones if you know this little. Is that more clear?

evo4gnoob said:
here ill explain on the International S3 their Kernel partition is stored where on the US variant our bootloader is stored. So when you flash a international rom it wipes your bootloader because thats where the kernel goes on the international
Click to expand...
Click to collapse
This will prevent it from even powering on or getting into Download mode? Sheesh.

MrAutomatic said:
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
Click to expand...
Click to collapse
I get that those replies probably werent the most soothing, but all of this could have been avoided and replying like that does not help you resolve you problem.
Now I dont know who you are or how much you looked into it, but next time make sure you stick to the development sections of the phone you're trying to flash
Sent from my PG06100

MrAutomatic said:
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
Click to expand...
Click to collapse
No problemo! Happy to help
I like to break stuff!

MrAutomatic said:
Thanks for your words of encouragement. It's nice to know there are still jack-asses around when you are in a tight spot to criticize your mistake.
Click to expand...
Click to collapse
Hey, I'm not trying to be a jackass. Maybe I am, but you have to imagine the frustration of people like myself who read for months before even trying to root a phone. You have to understand what you're doing with your device and especially a friend's. Every phone that goes back and was exchanged because a of a "bad OTA" helped create the excuse for an off-contract $500 Samsung Epic to become a $600-$700 Samasung Galaxy S3. I have never bricked a device. I tested Triangle Away for the first time on this phone for Chainfire and tested countless leaked kernels for Agat on the Epic Touch. My devices are fine because i knew what I was doing. This is why you should read.

MrAutomatic said:
This will prevent it from even powering on or getting into Download mode? Sheesh.
Click to expand...
Click to collapse
Yes since the partitions are different so let's say its supposed to format cache then on the US variant it will format something else. So the System doesn't get installed and the wrong things get formatted. You'd think you could just go back to boot loader but its wiped since the partition was different
Sent from my SPH-L710 using xda app-developers app

evo4gnoob said:
Yes since the partitions are different so let's say its supposed to format cache then on the US variant it will format something else. So the System doesn't get installed and the wrong things get formatted. You'd think you could just go back to boot loader but its wiped since the partition was different
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
For a little comparison, go install linux beside windoze on a separate partition using wubi, then delete the linux install and see if your computer will boot up. Oh no it won't boot because windows can no longer find the MBR (Master Boot Record, which is a PC bootloader) Just like borking the bootloader on a mobile device means that the device no more worky.
I like to break stuff!

-EViL-KoNCEPTz- said:
For a little comparison, go install linux beside windoze on a separate partition using wubi, then delete the linux install and see if your computer will boot up. Oh no it won't boot because windows can no longer find the MBR (Master Boot Record, which is a PC bootloader) Just like borking the bootloader on a mobile device means that the device no more worky.
I like to break stuff!
Click to expand...
Click to collapse
Ah. Hahaha. Good memories
I did this exact thing on my first linux install. Yay for recovery disks lol
Second time around I made sure I chainloaded into windows first and wrote the vista MBR. :good:
Sent from my PG06100

CNexus said:
Ah. Hahaha. Good memories
I did this exact thing on my first linux install. Yay for recovery disks lol
Second time around I made sure I chainloaded into windows first and wrote the vista MBR. :good:
Sent from my PG06100
Click to expand...
Click to collapse
I keep a rescatux disk taped to the bottom of my laptops for just such emergencies. I can't tell you how many times I've decided to upgrade or change my linux distro and hosed the MBR. Even done it a few times when the install was "successful" and linux would boot fine but windoze was MIA :banghead: only problem with a mobile device is once the bootloaders blown there's no rescue disk equivalent for the home user. Sometimes jtag can fix it but not if it doesnt come on at all
I like to break stuff!

Lol..... You did almost the same mistake I managed to do (Was my first time EVER rooting and flashing a rom). Just call sprint an play dumb. You might have to pay a fee but that's all you can really do at this point. After that mistake, I always stay in the Sprint GS3 forum along with researching all my roms, add ons, along with themes that I flash beforehand and reading the reviews on them.

Not to defend anyone but everyone was a newbie at one point but I do agree with if your not sure ask questions and read before flashing
Sent from my SPH-L710 using xda app-developers app

The root is blunt but speaks the truth. If you read. You would have seen that there are threads of people who have bricked their phone. So if you would have searched you would have seen what to do. Sheesh there's even a sticky to remind you not to flash international ROMs on the US variants.
http://forum.xda-developers.com/showthread.php?t=2156714
http://i1202.photobucket.com/albums/bb374/TexasEpic/ThePeoplesROM-KennyGlass123/daniel4653.png

[Q] Sprint S3 HardBrick - CM10.1 Cause?

I rooted my GS3 December and have flashed various different ROMs since then, but lately I've been sticking with the CM10.1 nightlies. I hadn't updated the ROM in a while... the last version I flashed was a slightly-stable nightly from the end of March (I can't remember the exact version). Day before yesterday, the CMUpdater decides to tell me that 'Oh, look! There's an update for your ROM!'
So, it downloaded the EXPERIMENTAL M3 20130411 (which, after doing research after flashing, has lots of bugs and shouldn't have used that one ) and flashed it. I wiped the cache and Dalvik cache (didn't do factory wipe since I wasn't changing ROMs) -- and everything appeared fine.
I was in the middle of actively using my phone last night (playing Ingress, should any of you be familiar) and the screen suddenly blacked out on me. I knew I still had 50% battery life, so when I couldn't get my phone to respond at all... I got a bit worried. After reading through as many threads as I have now, I am 100% certain that it is hardbricked.
I've been hesitant to post on the forums here just because compared to a lot of others, I would be considered a n00b... especially since I happen to be female, but I do know what I'm doing -- so I KNOW I didn't accidentally flash the i9000 version, or anything like that.
Anyone hear of this before?
Also -- I will probably go with the JTAG repair. I was looking at MobileTechVideos and it looks like I'll end up going with them, but does anyone know how long it takes to get a phone back from them?

Going to assume you attempted a battery pull. I've played round with a ton of ROMs, every so often one will flip out and freeze at a completely black screen. Power button does nothing.
Sent straight outta Compton

peskyheart said:
I rooted my GS3 December and have flashed various different ROMs since then, but lately I've been sticking with the CM10.1 nightlies. I hadn't updated the ROM in a while... the last version I flashed was a slightly-stable nightly from the end of March (I can't remember the exact version). Day before yesterday, the CMUpdater decides to tell me that 'Oh, look! There's an update for your ROM!'
So, it downloaded the EXPERIMENTAL M3 20130411 (which, after doing research after flashing, has lots of bugs and shouldn't have used that one ) and flashed it. I wiped the cache and Dalvik cache (didn't do factory wipe since I wasn't changing ROMs) -- and everything appeared fine.
I was in the middle of actively using my phone last night (playing Ingress, should any of you be familiar) and the screen suddenly blacked out on me. I knew I still had 50% battery life, so when I couldn't get my phone to respond at all... I got a bit worried. After reading through as many threads as I have now, I am 100% certain that it is hardbricked.
I've been hesitant to post on the forums here just because compared to a lot of others, I would be considered a n00b... especially since I happen to be female, but I do know what I'm doing -- so I KNOW I didn't accidentally flash the i9000 version, or anything like that.
Anyone hear of this before?
Also -- I will probably go with the JTAG repair. I was looking at MobileTechVideos and it looks like I'll end up going with them, but does anyone know how long it takes to get a phone back from them?
Click to expand...
Click to collapse
It's usually about 5-7 days from leaving your mailbox to returning to it, depends on their backlog of devices to fix. With the recent influx of "I just derped and flashed an international rom but found the right place to whine" threads they may be a little slower than before. But they are one of the best services and highest recommended on XDA. I wouldn't trust any of those $25 jtag from ebay guys with a flip phone. What does your phone currently do? If anything? Do you get any LED when pulling the battery and rebooting? LED when plugged in? Show up in "my devices" when connected to PC? Any sound when you try and power it up? If any of those occur your OLED might have burned out, actually happened to one memeber here (cbass+some numbers) back in the fall last year. Can you boot it into download mode(from powered off vol- + home + power)? Or recovery mode (vol+ + home + power)?
☆SoA: Son's of Android™☆
I like to break stuff!

As above, I've heard tell of pulling battery for a bit.
Seems some AT&T users had issues as well. Good luck.

-EViL-KoNCEPTz- said:
It's usually about 5-7 days from leaving your mailbox to returning to it, depends on their backlog of devices to fix. With the recent influx of "I just derped and flashed an international rom but found the right place to whine" threads they may be a little slower than before. But they are one of the best services and highest recommended on XDA. I wouldn't trust any of those $25 jtag from ebay guys with a flip phone. What does your phone currently do? If anything? Do you get any LED when pulling the battery and rebooting? LED when plugged in? Show up in "my devices" when connected to PC? Any sound when you try and power it up? If any of those occur your OLED might have burned out, actually happened to one memeber here (cbass+some numbers) back in the fall last year. Can you boot it into download mode(from powered off vol- + home + power)? Or recovery mode (vol+ + home + power)?
☆SoA: Son's of Android™☆
I like to break stuff!
Click to expand...
Click to collapse
Since my phone quit on me while I was on the road, I attempted to plug it into my car charger to see if it would do anything. It did nothing. I have pulled the battery and I left it out all night... still nothing. There was a glimmer of hope when I pulled the battery and plugged it in -- I got the red LED to come on and my computer looked like it found it, but when I pulled up the driver box, it was searching for the "DHSUSB_DLOAD" driver.
I've tried both boot techniques -- phone won't respond to either. I've tried to go through ODIN to see if it would recognize it... nothing. Tried the Toolkit and fastboot too.
Bah! Next time -- I'll be reading BEFORE flashing.

peskyheart said:
Since my phone quit on me while I was on the road, I attempted to plug it into my car charger to see if it would do anything. It did nothing. I have pulled the battery and I left it out all night... still nothing. There was a glimmer of hope when I pulled the battery and plugged it in -- I got the red LED to come on and my computer looked like it found it, but when I pulled up the driver box, it was searching for the "DHSUSB_DLOAD" driver.
I've tried both boot techniques -- phone won't respond to either. I've tried to go through ODIN to see if it would recognize it... nothing. Tried the Toolkit and fastboot too.
Bah! Next time -- I'll be reading BEFORE flashing.
Click to expand...
Click to collapse
I think the DHSUB_DLOAD means it's hard-bricked, but it wouldn't hurt to try out Hamspiced's solution over here. This person was getting issues because of a bad flash, and it worked for him. Might be worth a try.
Just as a quick aside, you mentioned you flashed the "EXPERIMENTAL M3 20130411." I cannot seem to find this anywhere on the goo.im d2spr page for CM. I was thinking that maybe it's an international Rom, but it's not in the i9300 goo.im page, either. I'm stumped to where you actually got this zip.

Sounds like your OTA updater flashed an international version instead of the d2spr version. This is why I never OTA multi device roms.
☆SoA: Son's of Android™☆
I like to break stuff!
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
topherk said:
I think the DHSUB_DLOAD means it's hard-bricked, but it wouldn't hurt to try out Hamspiced's solution over here. This person was getting issues because of a bad flash, and it worked for him. Might be worth a try.
Just as a quick aside, you mentioned you flashed the "EXPERIMENTAL M3 20130411." I cannot seem to find this anywhere on the goo.im d2spr page for CM. I was thinking that maybe it's an international Rom, but it's not in the i9300 goo.im page, either. I'm stumped to where you actually got this zip.
Click to expand...
Click to collapse
It came from the OTA updater built into the rom. It's obviously for the wrong device, most likely an international version with that DHUSB_DLOAD error. That occurs when you flash an international rom because their /boot partition and /misc partition are reversed with the d2spr so she now has a /misc partition in place of her /boot partition so theres no kernel, no bootloader/download mode and no recovery. The only option is JTag repair or paying the deductible for asurion(if she has TEP)
☆SoA: Son's of Android™☆
I like to break stuff!

-EViL-KoNCEPTz- said:
Sounds like your OTA updater flashed an international version instead of the d2spr version. This is why I never OTA multi device roms.
☆SoA: Son's of Android™☆
I like to break stuff!
---------- Post added at 12:28 PM ---------- Previous post was at 12:24 PM ----------
It came from the OTA updater built into the rom. It's obviously for the wrong device, most likely an international version with that DHUSB_DLOAD error. That occurs when you flash an international rom because their /boot partition and /misc partition are reversed with the d2spr so she now has a /misc partition in place of her /boot partition so theres no kernel, no bootloader/download mode and no recovery. The only option is JTag repair or paying the deductible for asurion(if she has TEP)
☆SoA: Son's of Android™☆
I like to break stuff!
Click to expand...
Click to collapse
Well -- it's good to know that the CMUpdater can do that now... grrr. Never again... I swear.
And you can find that CM ROM I talked about on their downloads website -> d2spr -> Snapshot
When I flashed it, I swore up and down it said d2spr... very strange. Very aggravating.

peskyheart said:
Well -- it's good to know that the CMUpdater can do that now... grrr. Never again... I swear.
And you can find that CM ROM I talked about on their downloads website -> d2spr -> Snapshot
When I flashed it, I swore up and down it said d2spr... very strange. Very aggravating.
Click to expand...
Click to collapse
Maybe the right filename on the wrong file, it happens. That's why I never use OTAs on multi device ROMs like CM, I always make sure I downloaded it from the right section and check the updater script if I'm wary of the validity of the download, like no device name in the file name.
☆SoA: Son's of Android™☆
I like to break stuff!

[Q] Uncontrollable behavior on Galaxy note 2 sgh-t889

Hello to all!
I have Galaxy note 2 SGH-T889 with ROM Slim-4.4.4.build.9.0-OFFICIAL-8278
Kernel: [email protected] #6 3.0.101-India-v4.3.8-OC-LTE-AOSP_Hybrid-lollypop
Sometimes, mostly after finishing call, it happens that it begins in totally chaotic manner launch apps, make calls, go into settings menu and etc. Only reboot helps which is quite difficult to initiate in this case.
Can somebody suggest something?

It looks like your phone is possessed....try an exorcism....lol...
No, but did you try the old factory reset?
Sent from my SGH-T889 using xda premium

Did you change anything in the Development Options like the back ground process?

//No, but did you try the old factory reset?
Yes, it was done just before reflashing.
//Did you change anything in the Development Options like the back ground process?
No.
Now i think can it be Xposed framework? I didn't install much modules. Just couple. For network and something else. Now it is uninstalled already.

Hello!
Can anybody, please, give me more answers? I don't know what to do...
I made all wipes and factory reset and reinstalled pure Slimkat 4.4.4
Still problem continues...

If you got oil or grease anywhere on your phone it can mess it up like that. Take it out of its case if you have one and clean it with a cloth dampened with peroxide. Clean front and back and the inside and outside of the case too. Hope that helps.

EdKeys said:
If you got oil or grease anywhere on your phone it can mess it up like that. Take it out of its case if you have one and clean it with a cloth dampened with peroxide. Clean front and back and the inside and outside of the case too. Hope that helps.
Click to expand...
Click to collapse
Thank you!! Now i am paying attention to the screen during talk and will experiment further with that.
Can you please suggest we something about kernel? Because my Agni kernel looks like not so stable