Samsung, please...

>>56408654
>flash CF autoroot

BUG YOU TELL ME :^)

no op you rilly dum you deserve it

>>56408654
f*cking epic XD

>>56408654
>buying samshit

>>56408679
what would be better then?
flash Supersu through TWRP?

>Buying an S6

>>56408654
>I voided the warranty with third party software
>This is the manufacturers fault
Are you really blaming this on Samsung? You can't be serious, surely?

Flashed custom rom (after erasing /system, dalvik, cache) - problem stayed.

went back to stock via their shitty SmartSwitch: problem persisted.
well fuck that

>>56408709
rules is always always unlock bootloader first(if locked) fastboot install custom recovery and backup whole rom, when something fuck up you can restore it

>>56408654
>buys Samsung S6 (touchwiz included)
>roots it
>Unresponsive
>blames Samsung
Halo faggot. I didn't even blame my Smartphone when I rooted mine and somehow upgraded into air touch (literally hovering your finger for accessing the phone).

>>56408755
This

>>56408755
kind of.
even after getting rid of all changes made by me, problem stayed.

>>56408654
>put overwide rims on car tires
>set camber to -30 degrees
>stanced to 2mm above ground
>tires explode
>"fucking Hondas!"

No, OP you're just subnormal.

>>56408799
** Mutated

Judging by the comments root is a bad thing. What? Like you havent done it? oh please.

Rooted my S3 (3 years ago), flashed CM 11, done so much shitey to it, never got any serious problems.

>>56408775
seems stock firmware still installed there, that's why is laggier. check the internal by an app like link2sd (it has a system dalvik etc partition) or find a new rom.

>>56408940
finaly someone who doesnt dick around.

thanks, but what am i supposed to look for when checking the internal?

>>56408985
>finaly someone who doesnt dick around.
That's the reason why his phone still works but yours doesn't.