Related
I have just received an OTA update to 2.3.6. I have been connecting my Note to my laptop using Kies for the last few days to see if it was available that way but there was no mention of an update. So I was pleased when I did an update check using Settings on my phone and discovered one was available OTA. It is good getting OTA updates just like on the Nexus One so there is no risk of installing the wrong firmware or making a mistake using Kies.
So what difference does the update make?
received my note yesterday and had OTA 2.3.6 XXKKA also 15 megs size.
also interested to know the differences
i bought from carphonewarehouse and got OTA 2.3.6 this morning too.
ps. its stock phone with no root.
So this removes root and CWM?
Edit: apparently root and apps are not touched on this update according to the other thread about this.
Just downloaded and install failed, it said to try using kies...
Sent from my GT-N7000 using xda premium
just downloaded update via phones updater and installing now...ill report back with more info after
ok successful.. phone updated to
2.3.6
N70000XXKK5
kernel = KKA
ok i can confirm root is left alone and all apps and settings preserved
HTC Chris said:
So this removes root and CWM?
Edit: apparently root and apps are not touched on this update according to the other thread about this.
Just downloaded and install failed, it said to try using kies...
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
Have the same. It failed to update, said to try by kies. I also have rooted stock ROM.
Maybe we should unroot ?
buk_grudziadz said:
Have the same. It failed to update, said to try by kies. I also have rooted stock ROM.
Maybe we should unroot ?
Click to expand...
Click to collapse
That may be the case, so I'll probably do this later today since it's almost 3am. I don't want to set everything up tonight.
Or we can just wait for a custom ROM that will have the update.
Edit: I don't understand though why people who are rooted in the other thread got it to work.
Sent from my GT-N7000 using xda premium
people rooting doesnt effect the updating. im rooted and ive just completed update fine.... download the update via wifi like i did and it works great.. see my post above
DAMIEN123_666 said:
people rooting doesnt effect the updating. im rooted and ive just completed update fine.... download the update via wifi like i did and it works great.. see my post above
Click to expand...
Click to collapse
That's how I downloaded the update.
Sent from my GT-N7000 using xda premium
Thanks for the thread! I've nicely updated my phone
Also got 2.3.6 OTA today. Phone is from the Polish Plus+ telco. Seems much snappier all around. Will be interesting to see if battery life improves too. Also the stylus seems more accurate but it's hard to say...
Bring on ICS!
mine fails the wifi update. tried 3 times. my phone is rooted.
fire up kies and says that kj4 is the latest
perhaps its to do with the method you used for rooting.
iirc, there are a couple of different root methods, some of them seem to affect the tamper counter (cant think of what its really called). maybe the update is only available for those who still have the counter at 0?
dont quote me on this though, im still a nubblet on the tweaking side of android.
i followed http://forum.xda-developers.com/showthread.php?t=1329360
to root.
Gaugerer said:
I have just received an OTA update to 2.3.6. I have been connecting my Note to my laptop using Kies for the last few days to see if it was available that way but there was no mention of an update. So I was pleased when I did an update check using Settings on my phone and discovered one was available OTA. It is good getting OTA updates just like on the Nexus One so there is no risk of installing the wrong firmware or making a mistake using Kies.
So what difference does the update make?
Click to expand...
Click to collapse
Can this UK version turn off focus sound and camera sounds??
ballfire said:
i followed http://forum.xda-developers.com/showthread.php?t=1329360
to root.
Click to expand...
Click to collapse
It seems rooting has nothing to do with it. I've rooted by the CF-Root method 2.
Maybe any other changes make the problem (theme mods ?)
buk_grudziadz said:
It seems rooting has nothing to do with it. I've rooted by the CF-Root method 2.
Maybe any other changes make the problem (theme mods ?)
Click to expand...
Click to collapse
I don't have theme mods, I disabled go launcher ex, and unfroze my bloatware too
Sent from my GT-N7000 using xda premium
HTC Chris said:
I don't have theme mods, I disabled go launcher ex, and unfroze my bloatware too
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
What about AndroidIceCreamSandwichtheme by movmo ?
buk_grudziadz said:
What about AndroidIceCreamSandwichtheme by movmo ?
Click to expand...
Click to collapse
No I had to revert back to the stock theme since the dialer had problems. Worst case scenerio I may have to wait for a custom ROM, maybe ill try updating through kies later.
Sent from my GT-N7000 using xda premium
I rooted my note with Chainfire's tutorial using the zergrush method and installed the new KKA kernel.
My phone downloaded this new update but failed to flash it on reboot. I think I'll just wait and see if Chainfire releases his own version or there is a rom with it built in.
After just playing around with odin.
I think i have found a fix.
I flashed http://downloads.fairview5.com/i337/I337UCUEMJ6_full_wipe.tar.md5.7z through odin and it went through for the first time.
Then i used the pit file called "SGS-I337_16GB.pit" idk where it is but it's on the forums
Note:This will upgrade your phone to 4.3 and there are no root methods for 4.3 as of right now.Plus there might be some problems with the playstore.(i haven't encounter any yet)
Also remember that you can go to bestbuy and ask them to flash your phone so you can stay on 4.2.2. This is for people who just want to fix it now instead of going to a store.
Credit to jball and rayburne for telling me to put the downsides and other opitions
Cool deal buddy
Sent from my GT-I9505 using XDA Premium 4 mobile app
Odischeese said:
After just playing around with odin.
I think i have found a fix.
I flashed http://downloads.fairview5.com/i337/I337UCUEMJ6_full_wipe.tar.md5.7z through odin and it went through for the first time!!!!!!
Then i used the pit file called "SGS-I337_16GB.pit" idk where it is but it's on the forums
And now i have recovery!
Not just recovery, but i have my phone back!!!!
Click to expand...
Click to collapse
isn't that the leaked 4.3 fw?
xuanphucn said:
isn't that the leaked 4.3 fw?
Click to expand...
Click to collapse
Yes and it works like a charm.
I still have no clue why it can flash with odin if you're on MF3, regardless i am happy with it as it is the only rom that you can flash (that i know of) if you're on MF3.
Just a word of caution to anybody who wants to try this, there is no root method for it and playstore is having some issues installing some apps.
Edit, here's the thread discussing mj6 and some of the issues people are having http://forum.xda-developers.com/showthread.php?p=46860747
Playstore?
jd1639 said:
Just a word of caution to anybody who wants to try this, there is no root method for it and playstore is having some issues installing some apps.
Click to expand...
Click to collapse
I am having no problems with the playstore as of right now.I'm downloading over 4gb of apps right now. I'll post back if there's any problems.:good:
After downloading 4GB of apps, there were no problems.
Odischeese said:
Yes and it works like a charm.
I still have no clue why it can flash with odin if you're on MF3, regardless i am happy with it as it is the only rom that you can flash (that i know of) if you're on MF3.
Click to expand...
Click to collapse
I'm MF3 as you know and I'm using Omega V12 4.2.2 and it's a rom .I use Safestrap with no problems
Sent from my GT-I9505 using XDA Premium 4 mobile app
jball said:
I'm MF3 as you know and I'm using Omega V12 4.2.2 and it's a rom .I use Safestrap with no problems
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes but i was talking about flashing with odin though
Some people with the MF3 problem couldn't even get to their stock recovery like me:crying:
This is the only ROM i know of that you can flash with odin on MF3.
Even if you don't have a stock recovery you should have been able to use Safestrap. I don't have stock recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app
jball said:
Even if you don't have a stock recovery you should have been able to use Safestrap. I don't have stock recovery
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I was ****ed big time. I did install SS but like i told you yesterday, SS ****ed up the wiping and it looked like SS just deleted itself. The reason why i said that because SS never came up. My phone never could go past the bootlogo nor bring up the 2 SS options. If i had SS at the time then i would of never came to forums lol
Odischeese said:
After just playing around with odin.
I think i have found a fix.
I flashed http://downloads.fairview5.com/i337/I337UCUEMJ6_full_wipe.tar.md5.7z through odin and it went through for the first time!!!!!!
Then i used the pit file called "SGS-I337_16GB.pit" idk where it is but it's on the forums
And now i have recovery!
Not just recovery, but i have my phone back!!!!
Click to expand...
Click to collapse
Odischeese said:
I was ****ed big time. I did install SS but like i told you yesterday, SS ****ed up the wiping and it looked like SS just deleted itself. The reason why i said that because SS never came up. My phone never could go past the bootlogo nor bring up the 2 SS options. If i had SS at the time then i would of never came to forums lol
Click to expand...
Click to collapse
I'm glad you were able to fix your phone and share with other to help them out, but I feel this title is a little misleading.
Yes you are fixing a soft bricked MF3 phone but the fix is upgrading them to MJ6 4.3. I understand a fixed MJ6 phone is better than a broken MF3 phone but I think it should be mentioned in your instructions. Best Buy is an alternative to fixing your phone and remaining on 4.2.2. Maybe a fix is around the corner for MF3 soft bricks that won't apply to MJ6 devices (yes I agree high unlikely but it should be mentioned this is upgrading the user to 4.3).
Sorry to hear your troubles with Safestrap. I'm on MF3 using SS and not had a problem. I think I have installed most of the 4.2.2 ATT and International Roms without issue. With what you described above about SS, I can only guess that SS has a bug that you encountered that affected your stock slot or you mistakenly wiped or flashed something to your stock slot that hosed your MF3 stock slot. Either way glad you recovered and shared your fix.
rayburne said:
I'm glad you were able to fix your phone and share with other to help them out, but I feel this title is a little misleading.
Yes you are fixing a soft bricked MF3 phone but the fix is upgrading them to MJ3 4.3. I understand a fixed MJ3 phone is better than a broken MF3 phone but I think it should be mentioned in your instructions. BB is an alternative to fixing your phone and remaining on 4.2.2. Maybe a fix is around the corner for MF3 soft bricks that won't apply to MJ3 devices (yes I agree high unlikely but it should be mentioned this is upgrading the user to 4.3).
Sorry to hear your troubles with Safestrap. I'm on MF3 using SS and not had a problem. I think I have installed most of the 4.2.2 ATT and International Roms without issue. With what you described above about SS, I can only guess that SS has a bug that you encountered that affected your stock slot or you mistakenly wiped or flashed something to your stock slot that hosed your MF3 stock slot. Either way glad you recovered and shared your fix.
Click to expand...
Click to collapse
Yeah I was just a little over exited finding a fix and quickly made a title.
I'll edit the instructions a little more...
Thanks for catching my mistakes :good:
Odischeese said:
Yeah I was just a little over exited finding a fix and quickly made a title.
I'll edit the instructions a little more...
Thanks for catching my mistakes :good:
Click to expand...
Click to collapse
Naw man, I'm not claiming you made any mistakes :good:
Just trying to help others who read the OP to fully understand the fix.
I'm just glad you found an alternative fix to Best Buy and shared it with others!
rayburne said:
Naw man, I'm not claiming you made any mistakes :good:
Just trying to help others who read the OP to fully understand the fix.
I'm just glad you found an alternative fix to Best Buy and shared it with others!
Click to expand...
Click to collapse
Ahh ok
what do you think i should rename the title btw???
"Optional fix to a MF3 brick" point of no return
Sent from my GT-I9505 using XDA Premium 4 mobile app
Thanks man, you got me back up and running... I know it's not ideal but it works...
jball said:
"Optional fix to a MF3 brick" point of no return
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
"Optional fix to a MF3 brick point of no return"
the entire quote???
Sure
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hi,
i had CM 11 for a while but recently the bugs get worse then less. In the moment i cant make any call for example.
I tried Sammys 4.3, but the experience was very bad too. Pretty buggy, some apps wont work...and slow like hell.
So im thinking of going back to the latest 4.1.2 sammy rom.
I lost a bit the overview about efs and all this stuff.
Is there any problem to expect doing this? What was the latest or best version of 4.1.2?
Thanks
Your EFS folder version can normally be determined by what modem you have installed.
If you have flashed stock 4.3 it would more than likely be EFS v2
I think you should be ok to just flash a stock rom in odin but just let someone confirm this or just have a quick search. If you want to make sure it shows as official in download mode, then use triangle away to sort that
nearlygod said:
Hi,
i had CM 11 for a while but recently the bugs get worse then less. In the moment i cant make any call for example.
I tried Sammys 4.3, but the experience was very bad too. Pretty buggy, some apps wont work...and slow like hell.
So im thinking of going back to the latest 4.1.2 sammy rom.
I lost a bit the overview about efs and all this stuff.
Is there any problem to expect doing this? What was the latest or best version of 4.1.2?
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2455207
It uses efs v2 to be sure u dont run into troubles download a v2 efs modem for your region.
And backup!!!!!!!
Sent from my GT-I9300 using xda app-developers app
dannylow79 said:
http://forum.xda-developers.com/showthread.php?t=2455207
It uses efs v2 to be sure u dont run into troubles download a v2 efs modem for your region.
And backup!!!!!!!
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Is that the latest? I dont know dannylow79.
I always had the cwm versions of wanam or Justarch
I think all the latest 4.1.2 had EFS2. What about bootloader. Are there anymore problems to expect?
thanks
nearlygod said:
Is that the latest? I dont know dannylow79.
I always had the cwm versions of wanam or Justarch
I think all the latest 4.1.2 had EFS2. What about bootloader. Are there anymore problems to expect?
thanks
Click to expand...
Click to collapse
These roms are pure stock, i know because i build them. the lite version had all the bloatware taken out.
Ofcourse your are free to choose the ROM you trust. Just take a look in the treads of the ROM of your liking.
I jumped to cm myself.
Sent from my GT-I9300 using xda app-developers app
I've run Samsungs 4.3, CM11 and then downgraded to Samsung 4.1.2 MG4 (from Sammobile), just fine, no IMEI issues at all.
I've tried this two times and both I had the same result. I downgraded back to 4.2.2 with the D80110g_00.kdz for the tmobile g2. Then I rerooted it and added philz touch recovery. I flashed with the kitkat baseband in the cloudystock 1.1 fourm, then the rom with the patched 801 kernel after. Everything boot's up ok, and the phone works. But when I turn off the screen and back on its all grayed out with yellow lines. I have the reboot the phone for the screen to show up again. Can someone tell me what I am doing wrong?
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
JPrinceStar said:
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
Click to expand...
Click to collapse
baseband stays the same when flashing other roms. Pretty sure the rom zips don't touch baseband unless specified otherwise. Glad it worked for ya btw
Sent from my LG-D801 using xda app-developers app
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
JPrinceStar said:
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
Click to expand...
Click to collapse
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
v2.2v said:
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
batmanonastick said:
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
Click to expand...
Click to collapse
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Did anyone out there figure this out?
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
I think you hit the nail on the head with G build comment. I got my phone about a month ago from TMO and it came pre-installed. I wonder if something in the actual hardware is ever so slightly different with the latest G2s...
I flashed with the C build and it didn't fix it also, guess I'll stay on 4.2.2 till there is a official kitkat root.
Anyone around in this thread with the line problem willing to test a kernel?
mackster248 said:
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
Click to expand...
Click to collapse
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
sam298 said:
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
Click to expand...
Click to collapse
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
v2.2v said:
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
KennyJive said:
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Click to expand...
Click to collapse
JPrinceStar said:
Did anyone out there figure this out?
Click to expand...
Click to collapse
SeVIIn said:
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
Click to expand...
Click to collapse
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
dr87 said:
Anyone around in this thread with the line problem willing to test a kernel?
Click to expand...
Click to collapse
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
mackster248 said:
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
Click to expand...
Click to collapse
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
frettfreak said:
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
Click to expand...
Click to collapse
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
yeah it did ship with KK. pretty sure i have seen the thread regarding the autorec app. But will let you know! Thanks!
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
Mackster I'm on 4.2.2 which is rooted, is there anyway I could use a custom kitkat rom without getting the white lines? I dont want to keep downgrading everytime it happens.
Hello everyone.
For the past two weeks I have been having this frustrating issue. Since I couldn't find a suitable rom for my canadian note 3, I decided to go back to stock rom but when I flash one through ODIN, back button just doesn't work!
when I went back on flashing custom roms, it works perfectly! what's the problem? I did install the latest official stock rom! :crying:
-----------------
I forgot to mention, the back button works when I use the S-Pen in stock roms. the back button just hates my fingers
There may be a problem of button configuration on the stock room.
Of you have root access then you can change the button layout.
Once compare the button layout of the stock rom with the custom rom.
Sent from my Moto G using XDA Free mobile app
---------- Post added at 10:37 PM ---------- Previous post was at 10:33 PM ----------
IIABODEII said:
Hello everyone.
For the past two weeks I have been having this frustrating issue. Since I couldn't find a suitable rom for my canadian note 3, I decided to go back to stock rom but when I flash one through ODIN, back button just doesn't work!
when I went back on flashing custom roms, it works perfectly! what's the problem? I did install the latest official stock rom! :crying:
Click to expand...
Click to collapse
I think below guide may give you some idea.
http://galaxy-note2.wonderhowto.com...-2-for-easier-left-handed-navigation-0146943/
Sent from my Moto G using XDA Free mobile app
@shibaa987 the problem is, the area where the back button is is completely unresponsive. When I touch the back button, not even the backlight turns on.
IIABODEII said:
@shibaa987 the problem is, the area where the back button is is completely unresponsive. When I touch the back button, not even the backlight turns on.
Click to expand...
Click to collapse
I got your problem. Sometimes back I had the same problem on a Sony Xperia phone. Part of the display was not taking touch input.
Initially i thought the digitizer was corrupted. I also changed my ROM but no luck.
And then I just stick to one rom. Finally after some days it just got solved automatically.
I suggest you to check the stock rom with a custom rom kernel which will work with the stock rom.
Sent from my Moto G using XDA Free mobile app
shibaa987 said:
I got your problem. Sometimes back I had the same problem on a Sony Xperia phone. Part of the display was not taking touch input.
Initially i thought the digitizer was corrupted. I also changed my ROM but no luck.
And then I just stick to one rom. Finally after some days it just got solved automatically.
I suggest you to check the stock rom with a custom rom kernel which will work with the stock rom.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
can a custom kernel solve the problem?
See... Different roms are built by different developers and you may not know how much buggy they are.
If you have a custom rom where you don't have this issue and the rom is perfect for you then you can chose one accordingly.
Sent from my Moto G using XDA Free mobile app
shibaa987 said:
See... Different roms are built by different developers and you may not know how much buggy they are.
If you have a custom rom where you don't have this issue and the rom is perfect for you then you can chose one accordingly.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
YES! it finally works. I never thought a kernel would cause the problem. I put too much trust on the stock rom . Thanks man!
Awesome - what kernel did you flash to fix this? I have the same phone with the same problem (SM-N900W8 with Stock 5.0)
ste52653 said:
Awesome - what kernel did you flash to fix this? I have the same phone with the same problem (SM-N900W8 with Stock 5.0)
Click to expand...
Click to collapse
Same, please let us know which? tytytytyty
I had the same problem and the same phone after rooting stock lollipop with cf-autoroot. Back button would not work. So I installed custom recovery and Resurrection remix ROM and back button works again and couldn't be happier!
ste52653 said:
Awesome - what kernel did you flash to fix this? I have the same phone with the same problem (SM-N900W8 with Stock 5.0)
Click to expand...
Click to collapse
Camorda said:
Same, please let us know which? tytytytyty
Click to expand...
Click to collapse
sorry guys i forgot to check this thread, i'll attach the kernel I used. Unfortunately I don't remember which thread i got it from but I hope it helps. Use it at your own risk!