I have a strange problem that I just noticed. The back and menu button no longer lights up or respond when I press. I just got my phone a few days ago...was working before.
Anyway, I decided to root with root de la vega, and then apply the regionfree by chainfire. Everything seem to work fine. The only thing is my phone did not have the "reactivation lock" option under security. I read somewhere that some phones don't have that.
After that, I noticed I don't have a back or menu button that lights up....I tried doing factory reset, unroot, reflash firmware from sammobile. Also did data wipe, cache wipe...still it remains the same. I read somewhere about the generic.kl file in systems that has the key layout which seem to have been changed and nothing listed for the menu and back...I've edited that and make it "wake_dropped" as I think it's supposed to.
None of these work. STill not responding. However, S-Pen does make it work...but no lighting up. I checked and it's not becuase touch light is turned off.
Any idea what happened? Seem like it's a problem with software given s-pen can make it respond. EVerything else is working fine...There's no damage since I have received the phone..I assumed it was related to the rooting and regionfree.
Any help is greatly appreciated and urgently needed. I am tempted to update to 4.4.2 and see if it will fix it as a last resort but want to make sure we have tried everything we can while in root.
Please help
Strange problems like this could very likely be from a dirty flash causing corruption. By "dirty flash" I mean one or more of:
- bad cable
- loose cable
- bad USB port
- heavy electromagnetic interference
The Note 3 has a common problem with bad USB connections.
To be safe you should not continue using the current firmware. The best option is to
- wipe cache, system, data, and Dalvic cache
- flash stock firmware
- flash de le Vega again
then continue with what you had planned.
Frank
see below
I found this thread for galaxy note 2. Also another post about editing a file to swap the button on note 2
http://forum.xda-developers.com/sho...really appreciate someone's input about this.
These are the values on my SM-900T:
key 139 MENU
key 158 BACK
Did you wipe system, data, cache, and Dalvik cache, then flash stock before rooting again?
Frank
Frank Westlake said:
These are the values on my SM-900T:
key 139 MENU
key 158 BACK
Did you wipe system, data, cache, and Dalvik cache, then flash stock before rooting again?
Frank
Click to expand...
Click to collapse
Oh really? Interesting...guess that's not the problem. I have read that in others that it would be 139 Menu Wake_dropped. I changed it to that but no improvement. I'll change it back.
I did wipe system data, cache...reflashed the oficial ROM from Sammobile...didn't know how to do dalvik cache wipe as it was not option in recovery. Went back to unroot official 4.3 but exactly same problem...then I rerooted again...still same problem. Deleted the dalvik content manually, read somewhere that's what you can do to wipe. Re wipe and factory reset. All that and no improvement.
The only thing I found is the S-Pen does make the button to respond when I press with S-pen..but not light up. but it will not respond with finger.
I am not sure what else I can do. Could it be a problem with the firmware file? I redownloaded it...thought I'll try it all again.
Otherwise, I could only think of updating to 4.4.2 maybe it iwll fix it. IF so, what's the best cleanest way to install...OTA from 4.3 or do flash from Odin? Can I flash with Odin wihtout root in the official 4.3 ROM? Does it need USB debugging if that's all I am doing?
Thanks again...
newr said:
All that and no improvement.
Click to expand...
Click to collapse
Then the chance that the problem is due to applying Root de la Vega is very slight.
If after going back to stock and then rooting again, if you did not reapply the regionfree then it is not likely the problem either.
There is still the likelihood of it being a bad USB cable connection during transfer. The Note 3 USB port does not provide a tight connection and the heavy cable and plug which comes with the Note 3 makes the connection even more poor. It could be that just one millisecond of disconnection caused bad data to be transferred and that bad data caused some program to write to the wrong memory address causing permanent hardware damage. This kind of thing is impossible to track down and it is why manufacturers don't want to accept responsibility for rooted devices. If this is what happened then upgrading to 4.4.2 will not fix it. You said "went back to unroot official 4.3 but exactly same problem", which I interpret to mean that going back to stock did not fix it.
My recommendation is to return it to stock and see if your provider will accept it for warranty exchange.
Frank
ADDED:
Tell them it was probably caused by a bad cable connection while you had the device connected to your computer.
If I want to put it back in Stock with 4.4.2 shld u do Ota or can I flash the new b4 rom Odin? I don't know if it hardware pb, from what I read from note 2, ppl had problems after updating to 4.3 before
Sent from my Galaxy Nexus using XDA Free mobile app
i m facing same problem after rooting if you get any solution please send to [email protected]
Me three....!
Same problem! Everything was working great until I rooted with kingoroot. Now capacitive buttons won't respond unless using s-pen. Tried doing a factory reset, flashing stock firmware with odin, re-rooting with CF-Auto-Root.. nothing seems to fix it.
I had a similar issue with the back button on my N900W8 not working after rooting by flashing SuperSU. Turned out to be a kernel bug, according to this thread, and flashing idleKernel fixed it for me. I'm not sure what the differences are between the options here, but: https://idlekernel.com/ I used the version from the /touchwiz-lollipop/ folder on my otherwise stock ROM and the back button worked fine again after that. Might be similar for you guys with your menu buttons.
Jaitsu said:
I had a similar issue with the back button on my N900W8 not working after rooting by flashing SuperSU. Turned out to be a kernel bug, according to this thread, and flashing idleKernel fixed it for me. I'm not sure what the differences are between the options here, but: https://idlekernel.com/ I used the version from the /touchwiz-lollipop/ folder on my otherwise stock ROM and the back button worked fine again after that. Might be similar for you guys with your menu buttons.
Click to expand...
Click to collapse
This worked!! Thank you so much
Related
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Iantuition said:
So basically I did this:
http://forum.xda-developers.com/showthread.php?t=2538991
But unfortunately, I hadn't realized that the mobile hotspot was sealed up in that update. So I looked it up, and saw that someone had recommended this:
http://forum.xda-developers.com/showthread.php?p=48326067
So I went into TWRP and installed it. But that didn't work. When I booted back up EVERY app was crashing immediately except the stock Samsung apps (Messaging, Email, etc.). I tried to reverse it with the original framework-res.apk but when I did, the phone would get stuck at the AT&T logo (which was silent). I went back and forth a few times (when I applied that tethering mod, the phone would boot; when I tried to reverse it, it wouldn't), then did a factory reset in TWRP. After that, the phone booted, but the Setup Wizard would crash. So I did a Nandroid restore in TWRP and now the phone hangs at the AT&T logo no matter what I do.
My question is, what can I do now? I have a replacement device coming through warranty just in case, but it would be much better to just fix this one. However, I want to be certain and not HARD brick the phone...
Click to expand...
Click to collapse
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
bellifritz said:
I have never been able to restore a stock 4.3 nandroid without everything crashing. I have always had to go back into recovery and wipe data/factory reset and wipe cache and dalvik cache then reboot and go through the whole setup process again. If that doesn't work you could try installing the stock debloat ROM from this thread. That's what I am running and it works great. http://forum.xda-developers.com/showthread.php?t=2540998
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
winosxbuntu said:
if you can get back to twrp , clear everything then flash the official correct file that yu want then see if that works...restore your apps/data after a clean refresh for your phone
remember panicking and being paranoid with flashing/rooting is not a a good idea, always rethink what you did wrong, let the phone cool down, research know what you re doing then fix it
dont rush, cuz rushing leads to bricks (learned from experience from day 1 with root)
Click to expand...
Click to collapse
Okay. Which official file though? and should I clear the system and boot partitions too?
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Okay. Which official file though? and should I clear the system and boot partitions too?
Click to expand...
Click to collapse
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
winosxbuntu said:
try this two links, everything on flashing 4.3 stock/rooting and fix http://forum.xda-developers.com/showthread.php?t=2540998
http://forum.xda-developers.com/showpost.php?p=46804338
either one will work
AND dont clear everything just cache/dalvik/format system/ factory reset BUT follow the instructions given for that rom to avoid any problems
Click to expand...
Click to collapse
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Iantuition said:
How'd you do that? Just the regular factory reset? Cause the setup wizard wouldn't even run after that.
Hit the power button to make the screen go to sleep. Hit the power button again to wake it up. Nothing should be crashing while you are on the lock screen so just hold the power button until the power menu appears and select power off. Once it powers off hold the volume up, home button and power button until you see the blue words in the upper left corner of the screen I believe it says loading recovery. Release the power button but continue holding the other 2 buttons until recovery loads. Now wipe data, cache and under advanced wipe dalvik cache. Reboot and everything should quit crashing but you will have to setup your account and apps again. That is the only way that I can get stock touchwiz 4.3 nandroids to work.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Iantuition said:
Okay so I just leave boot alone. Let us pray, LOL. And sorry if I've sounded like a supernoob but I'm trying to be REALLY careful.
Click to expand...
Click to collapse
it will work, i agree with what bell said. unless its hard bricked then no worries just keep calm and fix the damn phone
I have a T-Mobile Note 3, all stock, not rooted. I recently installed the lollipop update, and now my screen rotation stops working.
A reboot fixes it, but it will stop working again later in the day.
I have auto rotate on, smart rotate is not on, auto brightness is on (a search said this worked but it was for an older firmware).
Has anyone seen this or possibly know a good fix?
Wow, nobody else has seen this?
WatermelonSlim said:
I have a T-Mobile Note 3, all stock, not rooted. I recently installed the lollipop update, and now my screen rotation stops working.
A reboot fixes it, but it will stop working again later in the day.
I have auto rotate on, smart rotate is not on, auto brightness is on (a search said this worked but it was for an older firmware).
Has anyone seen this or possibly know a good fix?
Click to expand...
Click to collapse
hello
i had a few issues when i upgraded from 4.4.2 to 5.0 stock lollipop... first of all check if the baseband shows same as the build name.. it should both finish in OB6 ....also try booting the phone in safe mode to see if its and app/tweak error... u could also try a factory reset or a full factory reset from recovery screen with a full wipe and cache and dalvik cache erased but i dont know if its possible in stock android recovery since first thing i do when i unbox the phone is to root... always running rooted and with custom recoveries since i like to mod and tweak my phone i suggest you to try to root and release your phone full potential hope this works for you.
Sent from my SM-N900T using XDA Free mobile app
Reinstalling the lollipop firmware may correct it.
Odin, Kies or whatever method you used, try a reinstall.
Pp.
PanchoPlanet said:
Reinstalling the lollipop firmware may correct it.
Odin, Kies or whatever method you used, try a reinstall.
Pp.
Click to expand...
Click to collapse
I just went to Settings, General, About Device, Check for Updates and installed it from there. When I go there now it says the device is up to date, so no way to do it the same way as the first time.
Tostido has a full firmware zip available, you can download extract and reflash using Odin 3.09.
Find it here http://forum.xda-developers.com/showthread.php?p=59257327
This will reinstall the latest update and should correct rotation problem.
Pp.
Funny thing is my wife has the same issue on hers. I guess we'll both have to reflash.
Is there a way to flash that toastido version without losing everything? I have a bunch of apps installed, pictures, memos to myself, etc.
WatermelonSlim said:
Funny thing is my wife has the same issue on hers. I guess we'll both have to reflash.
Is there a way to flash that toastido version without losing everything? I have a bunch of apps installed, pictures, memos to myself, etc.
Click to expand...
Click to collapse
sure there is... i suggest you to root your device... its very easy and means no harm unless you start playing with system stuff but basically it just unleash your phone full power.... and once you rooted you just install titanium backup which is the best back up ever (in my opinion) and u do a full system data/user data back up which it will save ALL phone and apps settings and data and you just save the titanium back up folder to your pc and then put it back once you done flashing... also be careful once u flash and you are reverting the back up since the error might be a misconfiguration somewhere... but u can choose manually which stuff u wanna restore like accounts messages phone call history and more... also remember to root back again and installing a custom recovery like TWRP or CWM so i can flash stuff and back up and get a better recovery experience and also u could flash the SD card write fix since on newer versions phone wont let you write data directly to a SD card.... hope it helps at all and good luck
Sent from my SM-N900T using XDA Free mobile app
In the past few days after flashing alliance v2 i noticed that my phone would freeze then power cycle when I attempted to make or receive a call. Everything else works, I tried a different rom and still having the same issue. Any ideas?
eeeeeeeeek said:
In the past few days after flashing alliance v2 i noticed that my phone would freeze then power cycle when I attempted to make or receive a call. Everything else works, I tried a different rom and still having the same issue. Any ideas?
Click to expand...
Click to collapse
Take a look at posts 2 and 3 of this thread.
http://forum.xda-developers.com/showthread.php?t=3067828
HELP!!! Need a PIT file for N4
Odd problems that carry past factory reset and ROM flashes require a better flush. And clean install.
samep said:
Take a look at posts 2 and 3 of this thread.
http://forum.xda-developers.com/showthread.php?t=3067828
HELP!!! Need a PIT file for N4
Odd problems that carry past factory reset and ROM flashes require a better flush. And clean install.
Click to expand...
Click to collapse
So I had already started when I saw that, though the second post on that thread is a little confusing. However I had already odin back, booted up, but didn't wipe it, so instead I hooked it up to samsung kies, and did a full restore from kies. Made a test call, still froze, and crashed. So re rooted and put twrp then did an excessive number of advanced wipes. I even used the repair option to repair system then data. Just flashed vision and waiting on it too boot to see. Should I move further questions to that thread?
eeeeeeeeek said:
So I had already started when I saw that, though the second post on that thread is a little confusing. However I had already odin back, booted up, but didn't wipe it, so instead I hooked it up to samsung kies, and did a full restore from kies. Made a test call, still froze, and crashed. So re rooted and put twrp then did an excessive number of advanced wipes. I even used the repair option to repair system then data. Just flashed vision and waiting on it too boot to see. Should I move further questions to that thread?
Click to expand...
Click to collapse
I'd suggest keeping your posts on this thread. Just referred to that to save time.
Try the steps. Ask if not clear. If it sounds too extreme, start with the factory reset, Odin and factory reset again before flashing a deodexed ROM like Alliance. Update with results.
eeeeeeeeek said:
So I had already started when I saw that, though the second post on that thread is a little confusing. However I had already odin back, booted up, but didn't wipe it, so instead I hooked it up to samsung kies, and did a full restore from kies. Made a test call, still froze, and crashed. So re rooted and put twrp then did an excessive number of advanced wipes. I even used the repair option to repair system then data. Just flashed vision and waiting on it too boot to see. Should I move further questions to that thread?
Click to expand...
Click to collapse
Ii did as follows and tried several other ways, same results on factory image, unless I have a bad image, I pulled it off of one of the forums here
Are you powering down prior to Odin of stock tar? Did you use your PC to download the tar? Have you tried doing this without the sdcard? The full wipes are important.
Try the NIE stock tar.
http://forum.xda-developers.com/showthread.php?p=56853341
samep said:
Are you powering down prior to Odin of stock tar? Did you use your PC to download the tar? Have you tried doing this without the sdcard? The full wipes are important.
Try the NIE stock tar.
Click to expand...
Click to collapse
Ive wiped everything and formatted data repeatedly......I had a nand backup i forgot about, I'm going to restore that and see. I haven't tried flashing anything without the sd card from recovery, I have removed my SD card for the moment. It does seem like this is the issue, something with the partition. It's of course possible I didn't follow directions properly, though I feel I have. I'll also try NIE if need be. It's very bizzare issue. everything else works fine.
Update: Flashed NK2 stock tar, tried to make a call, same thing, phone freezes and powercycles.
Update 2: I even tried a different dialer, same results. Could a hardware issue cause this?
My suggestion is to try the factory reset, power down, Odin and Dial*##72786# to reprovision the phone; data profile update and try again.
Still fails? Could be hardware failure.
Anyone else?
samep said:
My suggestion is to try the factory reset, power down, Odin and Dial*##72786# to reprovision the phone; data profile update and try again.
Still fails? Could be hardware failure.
Anyone else?
Click to expand...
Click to collapse
Ive done all of this, even the 72786, tried wifi calling too just to be sure. maybe something with the antennai
Outside of a good suggestion, I'd stay with stock, call Sprint support. If not resolved there, setup a tech appointment.
Sent from my SM-N910P using Tapatalk
I really apologize if this in the wrong section, or forum, but I am very worried. Earlier I was messing around and I tried flashing the Xposed framework for lollipop. I have TWRP and I made a nandroid backup, I flashed it, all was well, and I rebooted. Well It was hanging for a while, too long, on the cyanogenmod booting screen. It was active, it wasnt frozen, the circle kept coming out from the logo.
I was like "damn, it must not have worked." So I powered off, hopped into recovery, and flashed the nandroid backup I had made.
Well now I have the same problem, It gets to the logo, and continuously flashes the circle, just nothing ever happens. Ive had it trying to boot for probably 10 mins now while I am typing this. I can get to recovery no problem, and have nandroid backups made, so I mean there has to be a way to fix it.
Can anyone help? Also, I'm working with a mac computer but I can pull up parallels desktop if need be.
Thanks in advance.
ALSO,
Where can I download a stock rom for 4.4.2 for The Galaxy Tab 8.4 T320
The only link I found is on some weird 3rd party website and is gonna take 9 hours to download. It is a .zip file and I need it to be able to work with odin, so hopefully there is a .tar in the zip correct?
All this crap because of stupid Xposed. omg.
Sorry guys, im freaking out.
Also, I think I have an idea why it wont boot..
I cannot clear the Cache, or the dalvik cache. It says "E/ Failed to mount : ' Cache" and same for dalvik cache.
And When I try to "repair filesystem" it also cannot mount cache and says the cache size it 0, and free space is 0. Someone please help. I don't want to cry myself to sleep tonight.
Also, I am downloading a stock rom right now, but it is one from Canada, I couldnt find one from the USA. But it was the one with the most downloads, so it doesnt matter where it's from as long as it is for my model, SM-T320, correct?
NOBODY, has any suggestions? God I'm gonna end up trying this on my own and ending up with a hard brick. Please, out of any of the 30 people who have viewed this, anybody?! :/
-Disregard this post-
I did it, ****ers!
Thanks for all the help!
As in, I flashed the stock rom with odin, and It was sucessfull.
Then I flashed TWRP and restored my nandroid. All was well.
A little late since you fixed it, but for future reference incase someone else has the problem.
XAR firmware is for the USA wifi models,
you could also flash with Samsung kies back to stock (downloads off samsung servers), though odin works too.
you could of disabled xposed with this command line if you had a custom recovery like twrp,
TWRP - Advanced - Terminal command
touch /data/data/de.robv.android.xposed.installer/conf/disabled
There is also a key combination that can disable it too not sure if it works with the lolipop beta though
http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9883
Quick explanation of the safemode: It was developed by @Tungstwenty and makes it possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled, which prevents most of Xposed's actions (e.g. no hooks are made and no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.
Click to expand...
Click to collapse
otyg said:
A little late since you fixed it, but for future reference incase someone else has the problem.
XAR firmware is for the USA wifi models,
you could also flash with Samsung kies back to stock (downloads off samsung servers), though odin works too.
you could of disabled xposed with this command line if you had a custom recovery like twrp,
TWRP - Advanced - Terminal command
touch /data/data/de.robv.android.xposed.installer/conf/disabled
There is also a key combination that can disable it too not sure if it works with the lolipop beta though
http://forum.xda-developers.com/showpost.php?p=51306764&postcount=9883
Click to expand...
Click to collapse
Thanks man, but I think my whole problem was something was corrupted with the Cache, it said I had 0 cache memory, with 0 free,
And I couldnt clear the cache, or dalvik cache for the life of me. Or even mount it for that matter.
I'm really thankful for all the posts I found on this website though, that's where I got the idea to flash it with Odin.
Help ! I own an LG G3 and randomly had a problem with the stock messaging app as it was failing and crashing, so then I decided to reboot my phone but as it rebooted, it was still the same except it had a stock background, no knock code, and my home + recent apps buttons do not function at all but show touch feedback... also when I long press my recent apps button it brings up the settings tab which it should do, which is odd, also my return/back button still works fine. I switched my background to my original one and enabled knock code again, then tried rebooting, hot booting, and powering off and on the phone but nothing worked it even reset my background again to stock and disabled my knock code. I can answer any questions other questions, Any help would be appreciated, Thank You !
Edit: Notifications do not show and the stock camera shortcut ( Hold volume down ) stopped working.
I'd probably try a factory reset if you haven't already. Also list your current software version and carrier info., which might be helpful to us in helping you.
How to factory reset the LG G3
http://www.androidpit.com/how-to-factory-reset-the-lg-g3
Be sure to backup your messages/address book, that problem sounds like an excellent candidate for a factory reset solution.
redduc900, you have a private message from me.
c627627 said:
Be sure to backup your messages/address book, that problem sounds like an excellent candidate for a factory reset solution.
Click to expand...
Click to collapse
I have Titan Backup (free version ), can I back everything up, factory reset, and the reload my phone ?
redduc900 said:
I'd probably try a factory reset if you haven't already. Also list your current software version and carrier info., which might be helpful to us in helping you.
Click to expand...
Click to collapse
It's a Sprint phone, software version LS990ZV4
I was gonna use that as a last resort, but I'll give it a try. Guess I'll have to reroot my phone... Again
TheAllOriginal said:
It's a Sprint phone, software version LS990ZV4
I was gonna use that as a last resort, but I'll give it a try. Guess I'll have to reroot my phone... Again
Click to expand...
Click to collapse
Well, if you are rooted, you might try going into your custom recovery and wiping cache and dalvik-cache.
Since you suspect the messaging app, maybe wipe the data for that one as well? You'd lose all your messages, of course.
epidenimus said:
Well, if you are rooted, you might try going into your custom recovery and wiping cache and dalvik-cache.
Since you suspect the messaging app, maybe wipe the data for that one as well? You'd lose all your messages, of course.
Click to expand...
Click to collapse
I don't have a custom recovery, whoops. The messaging app was fixed after the first reboot, which is when my phone booted that all the other problems occurred. Thinking of just backing everything up and factory resetting, although I wonder if I back up my phone and reset it then load my back up would the problem persist ? as maybe it stems off the soft/firmware, feel like this is the problem since the buttons show touch feedback but do not work.
TheAllOriginal said:
I don't have a custom recovery, whoops. The messaging app was fixed after the first reboot, which is when my phone booted that all the other problems occurred. Thinking of just backing everything up and factory resetting, although I wonder if I back up my phone and reset it then load my back up would the problem persist ? as maybe it stems off the soft/firmware, feel like this is the problem since the buttons show touch feedback but do not work.
Click to expand...
Click to collapse
Glad you seem to have it resolved.
BTW, a couple of notes and suggestions on best practices:
1. If you root and intend in any way on using the elevated permissions to modify your system, you should install a custom recovery, such as TWRP. This will allow you to backup your entire system at any time and restore in the event of an oooops! event.
2. If/when you have a custom recovery:
NEVER accept an OTA (over the air) update. It will bork your phone.
NEVER perform a factory reset from a stock ROM. It will bork your phone.​