Develop Bugs

capacitive button not working after root?

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

[Q] Please tell me this isnt a brick.

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.

Accidentally Botched SW3 Firmware by Flashing TWRP

When I got my SW3 last summer, I stupidly ignored all those warnings about flashing TWRP to recovery, mostly because I didn't see what harm could come of it. However, while investigating a battery drain that's persisted despite multiple flashes to stock and more than a few attempts to use crpalmer's LCA43 kernel, I discovered via my SW3's kernel log that it's got some serious weirdness going on with its firmware.
As it turns out, it's reloading the pedometer firmware every three seconds. This happens because every time it loads the firmware, it promptly encounters some manner of error while running it, which then prompts Android to try to reload the firmware. My first hint that this was a firmware issue came from the fact that I can't access any sensor data via the developer menu. Under 'Manufacturer: Menu-Launcher' at the bottom of Developer Options, the entries for Accelerometer, Gyro, Magnetometer, and Compass are all blank, while Ambient Light Sensor and Step Counter are perpetually stuck at 0.0.
After trying everything I could think of in my attempts to fix this issue, I then began investigating other variations from stock that I'd had over the months that I've had my SW3. Rooting didn't appear to change anything related to the firmware, and crpalmer's LCA43 kernel (and craigcharlie's simple MTP mod and, later on, alex6600's modified version of the kernel itself) didn't appear to cause any of the issues I'd been experiencing for anyone else. Finally, I found a comment somewhere about the fact that flashing TWRP to recovery instead of just booting it would really mess things up because it uses a device tree different from the SW3's stock device tree.
Since then, I've been trying everything I can imagine to fix this, but I haven't had any success thus far. Because of that and a few other reasons, I haven't been able to mess with this since the end of January, but I'm really getting tired of my SW3 only lasting for about 6-8 hours with pretty minimal use. I think the closest I got to any sort of progress was using dd to individually flash partitions that'd been uploaded, but I don't think I was ever able to find an upload of mmcblk0p19, dt-blob.
Does anyone have any ideas about what I might be able to do to fix this? Specifically, I'm curious to know whether or not dding partitions damaged when I flashed TWRP should work; if so, would someone be so kind as to either post or PM me dded copies of the relevant partitions? Thanks in advance for the help!

Repair with PCCompanion. Did that some weeks ago. Version is LCA43.

If pc companion does not work (and it probably wont), hold down the button on boot, and you can force it to usb mode. If that does not work, hit the button twice to go to fastboot and flash the original OS (look for the repair threads).
Good luck.
Sent from my SM-T810 using Tapatalk

Hey, @Flippy498, I broke something again Help again... Sorry

Hey, i'm assuming that @Flippy498 is going to reply, because he is the god of these forums, but after helping me figure out how to flash roms the right way, I have been enjoying ViperOneM9 6.1.0 alot, but for some reason the stock navbar was broken after the flash, oh well, Viper comes with one that I particularly like, problem solved. I have no idea why I did this, but I installed an apk of paphonb's custom navbar, to demonstrate to a friend that android is quite obviously superior, in terms of customization, and I showed him, then went on with my day, I saw this cool feature (I don't remember what it was but i'm getting to that) in the paphonb Custom Navigation Bar app, so I turned it on just to see how it works... And everything hit the fan.... My phone popped up the dreaded "system.ui has stopped" and sent me back to the lock screen. But now when ever I swipe up to put in my pattern to unlock I can see the dots momentarily, then the phone black screens. When I press the power button again it brings me to the lock screen again.....
Then I opened an ADB shell, and using my knowledge acquired from you I ran the command "adb uninstall xyz.paphonb.systemuituner"
It suceeded
I then wiped the Cache, and Dalvik cache through TWRP, but the issue persisted.
I still get the black screen/crash when swiping up to unlock, which means that I must be able to fix the issue using ADB right? I don't really know what to do now, so so help would be much appreciated!!!

First of all, did you try dirty flashing your current rom (installing it without wiping any data)? If that doesn't fix the issue then you need to think about the following:
Are there any data you don't want to lose on that phone? If yes, try to boot to twrp, connect it with your PC and to copy everything that you need from the internal storage to your PC. If the PC doesn't recognize the phone directly you should try the mount menu in TWRP.
If there is no data you don't want to lose or if you already copied all you need you simply clean flash the rom (installing it with deleting all data on your phone).
Please be aware that there's a small chance that your issue isn't caused by the app that you used but by the infamous dead nand issue. If twrp starts throwing out a lot of mounting errors during any of the steps and if you face an error while trying to boot to download or recovery mode at the same time then the evidence is clear that the nand died.
Sent from my HTC One M9 using XDA Labs

Bluetooth App Missing, Random Reboots, Deleted System Partition, No ROM in Storage

I've also posted this on Reddit and the OnePlus forums, but I'm hoping I can find an answer here, too.
Long story short: I really messed up my phone and I'm looking for help getting it to at least boot into the system. Lots of weird, confusing things have happened within the past few days, so bear with me; might be a long story, but I'll try to give you the abridged version.
I run locked and unrooted. I flashed OOS Beta 3 over 4.7.6 on my 5T, wiped my cache, and everything was wonderful for a week. Then one day, I got a system message saying "Bluetooth has stopped". I cleared that and thought nothing of it, but I got another message saying "Bluetooth keeps stopping". This message would actually pop up (with no exaggeration) every second. I could only stop the messages completely after going to the Bluetooth app and clearing the data, then disabling Bluetooth Scanning.
I figured the problem would fix itself, but the next day when I tried to connect to my car via Bluetooth, my phone would freak out again like the previous day. I had to listen to a CD like it was 1996. I thought I could fix the problem with a Factory Reset. As soon as I hit the Welcome screen, "Bluetooth has stopped". When I went to check the Storage section of the Bluetooth app in the Applications list, the app portion read 0 bytes. What? Even when I went into Settings --> Bluetooth and tried to turn it on, nothing would happen. I thought maybe I should revert back to 4.7.4 and start from the very beginning.
That served no purpose. The Bluetooth symbol did show temporarily in the Status bar as I was setting up my phone, but eventually disappeared, with the Bluetooth app once again taking up a whopping 0 bytes. I've done various combinations of installs, but I cannot get Bluetooth to function normally. And at some point, my phone developed a new problem: any time I hit the Bluetooth button in Quick Settings, the phone would eventually reboot on its own. Later, it wouldn't need any input from me at all. It would just be sitting in the Lock screen and reboot.
Icing on the cake: I got desperate, unlocked the bootloader, deleted the system and cache partition in fastboot, then wiped the data in Recovery with the hope that doing a completely fresh install would fix the problem, but at some point my internal storage got wiped and now I have no ROM on my phone to install. Even better: I'm having some real problems trying to install OOS (any version) on my phone via ADB sideload. I keep getting the message "cannot read <filename.zip>", even though it's in the correct folder.
I am currently back on my OnePlus 3 and the proud owner of a very sleek brick. I used to root and unlock Nexus devices and Moto X's, so I'm pretty embarrassed that I managed to ruin my phone while it was running (basically) all stock. It can still boot into Bootloader and stock Recovery. Is there anything at all that I can do to at least load OOS (or any ROM)? Do I have to send it back to OnePlus and beg for a replacement? Will they even take this phone in it's current state? Am I just SOL?
I've run out of ideas and patience. I'm really hoping someone out there can help me. At the very least, thanks for reading my long sob story. Hopefully this never happens to you.

try flash orero based twrp and flahs stock 5.0.3 zip in twrp, see if it works. then figure out the reset.
Why would you delete system from fastboot? Does people not formating partition from recovery more often？
The twrp I use
https://forum.xda-developers.com/oneplus-5t/development/recovery-twrp-3-2-1-0-oreo-8-0-8-1-t3729673

Update: I managed to unbrick my phone using an unbrick tool. The process was pretty painless and it will revert your 5T back to OOS 4.7.4 no matter what you did to it. Props to Drasm19 from the OnePlus forums and the geniuses behind this tool! Funnily enough, I was ultimately led back here:
https://forum.xda-developers.com/oneplus-5t/how-to/oneplus-5t-unbricking-tool-confirmation-t3733012
You guys more than likely already knew about this tool, but definitely keep this in mind if you manage to brick your phone like I did.
Now I'm back to my original problem: Bluetooth is really messed up. This is what I'm talking about:
https://imgur.com/gallery/eEkbX
No matter what I do, no matter how many times I flash any version of OOS, this is always the result. As you can see, even with the toggle in the "on" position, Bluetooth refuses to do what it's supposed to do and the app takes up 0 bytes. Something is up...
I've searched a lot of threads that reference Bluetooth issues, but it looks like I'm the only one with this problem. I'm open to any and all suggestions that'll help me solve this and get back to using my 5T. I already miss those awesome navigation gestures.
Thanks again for your time and help.

im not really a developer type, but a while back it was easy to root and un root with kingo. and i could put things in the system with FX. please bare with me a sec.. p9's i like, but getting some glitches. when the gboard went byby, on reset, i had to set up my welcome screen by shouting at the phone.. 'at sign' does give you @ but to get capitals you have to trick it, eg. 'USA' to get an upper case 'u'
anyway, i got in, and got gboard from 'my apps' ..fine but of course, wont survive another reset.
so about the missing bluetooth.. iv got the directory info. and the missing files. thanks ..but i didnt want to wipe the phone, it seems rooting has become a can of worms.
wouldnt it be nice if there was a nice (no root) app , to run bluetooth from the apps ? so that 'joe blow' doesnt have to throw his phone away, cos it doesnt work in the car ect.. thanks