I had the problem with replacing the broken glass on my TF201 that caused an inverted X-axis. Thanks to the solution provided by flumpster, I was able to get the fix the problem in the stock JB ROM (10.4.2.18) so that the inversion is corrected there, however the problem still exists in TWRP. I understand why. I asked in the TWRP IRC chat support if there were any fixes or patches that could be applied that would correct the issue. I was told that I needed to compile my own TWRP to load with the fix and that there were flags that could be set to flip either axis. I've looked into it but at the moment I am a little overwhelmed with the process of setting up the build environment and making sure I have everything in order to do this as I have never compiled anything from source before. Is there anyone out there that could possibly do a build of a compatible version of TWRP that would fix this issue? Many thanks to anyone who can.
Related
Hello,
I have compiled custom kernel based on samsung update1 drop. I am able to compile and build the kernel along with initramfs based on the stock kernel. However, I get stuck at the booloader screen.
My searches so far did not turn up a way for being able to get some sort of early console communication to see where the problem is. Can someone give me a guidance on how I can figure out where the problem lies.
Thank you in advance
Ordered parts to get access to UART for console messages. As explained in
http://forum.xda-developers.com/showthread.php?t=1143190&highlight=serial+cable
and
http://forum.xda-developers.com/showthread.php?t=1010314
hopefully that will help
Hello friends. So I am officially stumped. I have an issue with my kernel bootlooping. The interesting thing is, eventually it boots. After about 5-10 minutes of bootloop, it just boots. Weird right?
See, I merged a lot of code with my kernel and I'm not sure what is causing the bootloop. Here is my source: https://github.com/Snepsts/kernel_e980
It started on the add intelli-plug commit (which also includes intelli-thermal) it is probably important to mention disabling intelli-plug and thermal (and only one of each) all have the same outcome. I have also tried wiping the board back to its original state. I'm assuming its one of the core changes or nr_running changes. But I cannot find any way to get a log of the issue as it is not in a stable state during bootloop to give me logs from adb. I also cannot compile intelli-plug without the changes I made. And I really want to have it. I have looked for code I may be missing but cannot find any. I have made many different test kernels and taken the ramdisk and config from the latest official cm build for my device. Does anybody have any ideas? If you need anymore info please let me know. Thanks for any help in advance.
Sent from my LG-E980 running Carbon KitKat & E980 Kernel+
Hi everyone,
I recently have a problem on my (old) TF201. The touch screen works fine, except the right and left edge. When I turn on Developer options and enable 'Show touches' i clearly see that when I move my finger to the right or left it sort of 'snaps' to the edge. So there a small stroke (left and right) that doesn't respond to input. Very frustrating when trying to point out something on the very right or left of the screen
I've opened my TF201 to see it wasn't a loose cable; but everything is in place. No difference.
Anyone an idea?
I did replace the factory ROM with a custom recovery (TWRP) and used
http://forum.xda-developers.com/devdb/project/dl/?id=6853 to install once a CROMBi-kk ROM for TF300t. Maybe this generates this screen edge fault? If so; how do I revert back to TF201? My TF201 thinks it's a TF300 now.
Thanks for reading this problem.
Hi,
Same problem here. It looks like it started after installing KatKiss. I was previously using Cyanogenmod without any problem. I thought that this could be caused by the new bootloader, but the problem persisted even after reverting back to the stock BL and ROM.
I even tried to replace the touch screen, no luck.
Have you been able to fix the issue?
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
[email protected] said:
In case somebody else with the same problem finds this post, here is how I fixed the problem
http://forum.xda-developers.com/tran...2#post62361792
Unfortunately this apparently doesn't work for everybody...
Click to expand...
Click to collapse
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
altya said:
I tried ur method but may I know which Kernel did u reflash to? U mentioned default kernel so u mean grimlock lite 5.1?
Click to expand...
Click to collapse
I am not sure exactly which kernel it was. But as I explained, I first installed Androwook AiryBean 2.31.
Then I used the "Androwook airyBean 2.31 Kernel Installer" to reinstall the default Androwook kernel, meaning the default kernel shipped with the kernel installer. That probably not Grimlock lite 5.1... See this page to download the kernel installer (and the Androwook ROM): http://forum.xda-developers.com/showthread.php?t=2407248
Maybe I should clarify a bit:
1. I completely wiped the tablet and did a clean installation of Androwook, following the instructions to the letter, including the 30 to 60 minutes wait "for the system to cache itself", followed by a restart. At that point, I still had the issue with the screen edges.
2. I then re-installed the kernel, again following the instructions to the letter. After the final reboot, the problem was gone.
3. And I finally re-installed KatKiss (v26). Since then I enjoyed my TF201 without any issues.
The reason why I tried to re-install the default kernel is because of the following quote:
HairyBean 2.31 Kernel Installer will allow you to try different kernel options without re-flashing the rom. It will also clean up bits left behind by the previous kernel before installing a new one
Click to expand...
Click to collapse
I am not sure that this is what solved the problem, but this is definitely a software issue. And since wiping the tablet multiple time, downgrading to stock and trying various ROMs didn't do anything, this was my last hope. It worked for me, and I hope that it will work for you too...
I can confirm that this is a software issue. After installing the reverse axis kernel of Hairy bean, the unresponsive areas in the touch screen was also reversed! I tried the solution provided above, unfortunately without success. Is it right to assume that everyone got this issue after installing Katkiss version after V26?
jan3586 said:
Is it right to assume that everyone got this issue after installing Katkiss version after V26?
Click to expand...
Click to collapse
I don't think so. I got the problem with an earlier version of KatKiss, and I believe (but may be mistaken) from the research I did in the past that a few people ran into this problem with other custom ROMs.
Thanks, are you using ver 2 of the kernel installer?
Sent from my Nexus 4 using XDA Free mobile app
jan3586 said:
Thanks, are you using ver 2 of the kernel installer?
Click to expand...
Click to collapse
Yes, it was version 2 that I used.
My Kindle Fire HDX 7'' got hammered (literally). I fixed the dents, un-bent the chassis, replaced the lcd+digitizer and it's working again, but the accelerometer seems to be dead so I can't rotate the display. I tried with several "sensors test" apps, and they don't detect the chip (InvenSense ). I think maybe some contact broke because of the mainboard getting bended and it need to be resoldered, but I'm unable to locate the chip on the board.
Do you know where the chip is?
ttortuga123 said:
My Kindle Fire HDX 7'' got hammered (literally). I fixed the dents, un-bent the chassis, replaced the lcd+digitizer and it's working again, but the accelerometer seems to be dead so I can't rotate the display. I tried with several "sensors test" apps, and they don't detect the chip (InvenSense ). I think maybe some contact broke because of the mainboard getting bended and it need to be resoldered, but I'm unable to locate the chip on the board.
Do you know where the chip is?
Click to expand...
Click to collapse
Join a question. I have the same problem. I tried all versions of the TWRP flashable firmware, with no result. Also tried to drop, hit, use a magnet. Somebody know where the chip is? How to fix it?
Syuriy said:
Join a question. I have the same problem. I tried all versions of the TWRP flashable firmware, with no result. Also tried to drop, hit, use a magnet. Somebody know where the chip is? How to fix it?
Click to expand...
Click to collapse
I had the same problem but after I reflashed my rom it started working again. Try that if u can, or maybe if on stock downgrade to 3.2.8 then update back that might have the same effect
Syuriy said:
Join a question. I have the same problem. I tried all versions of the TWRP flashable firmware, with no result. Also tried to drop, hit, use a magnet. Somebody know where the chip is? How to fix it?
Click to expand...
Click to collapse
CocoBun said:
I had the same problem but after I reflashed my rom it started working again. Try that if u can, or maybe if on stock downgrade to 3.2.8 then update back that might have the same effect
Click to expand...
Click to collapse
Same. Flashed LinOS 14.1 on known good device and rotation stopped working. Tried common solutions but issue persisted. Wiped and flashed CM 13 (rotation started working again) then LinOS 14.1 with full wipes. No issues with rotation since. No logical explanation but 'ROM hopping' (for lack of better term) has reported worked for others experiencing rotation issues. Sounds nutty.
I tried to install all TWRP flashable firmware Nexus, Stock, CM 11 12 13 14, LOS with wipe and format data. No result!!!
Syuriy said:
I tried to install all TWRP flashable firmware Nexus, Stock, CM 11 12 13 14, LOS with wipe and format data. No result!!!
Click to expand...
Click to collapse
Out of ideas. Indeed may be a hardware problem. Hopefully you can find an app that supports reasonably convenient orientation selection (common UX places controls in a permanent notification).
After rooting my s9+ with the modified Magisk, my phone sometimes becomes unresponsive. I cannot identify any sort of trigger for this to happen, it just does. The AOD displays but does not update. The notification LED still blinks, but when I go to unlock the phone it freezes and I am forced to soft reset it. I am root with Magisk and have TWRP installed. I followed Max Lee's tutorial on how to root the S9+. Any ideas on why this is happening and how to fix it?
Hey, Did you have any luck with this, i am having the exact same issue?
having the same problem i followed Max Lee video and everything work fine until the phone started freezing
same issue on the G960F/DS....
wonder who can help us regarding with this issue.
For everyone having this freezing after rooting...attention to detail is absolute paramount, go back and re-read the twrp thread by jesec. For those (possibly those having freezing issues) who find that challenging, here is a snippet of jesec exact words..." Samsung implemented security measures such as "Real-time Kernel Protection (RKP)" and "RKP Control Flow Protection".
Those security measures are intended to block control flows such as privilege escalation, memory kernel code modification, etc which are not authorized by Samsung.
If those are not disabled, processes (such as daemon of root solutions) that violated those security rules will fall into deadlock.
Deadlocked processes will then consume large amount of resources (leads to performance issues, battery drains) and eventually crash the system.
Technically it is possible to disable those security measures by hex editing stock kernel but just simply flash a custom kernel is better in my opinion.
TL;DR: Flash custom kernel before root or be screwed.
To reiterate...flash a custom kernel before root or be SCREWED
I'm not saying this is 100% u guys issue, but seems kinda likely?
can someone post links or steps on how to fix this freezing lock screen issue, i tried reading the threads but did not find anything, thanks
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
crs_dev said:
I was facing the exact same issue after using his tutorial.
I've tested SOD Killer from the Playstore so far it's working fine! No freezes anymore .
Installing a custom kernel like elementalX should also work.
Click to expand...
Click to collapse
Can we flash this Elementalx over the N965F_Root_for_OEM_issue_devices/Magisk we already installed ?
I already installed the TWRP, No-verity opt encrypt and the N965F_Root_for_OEM_issue_devices package on my friend's 960F.
I would be really greatful if anyone could help me with this.
I had the same issue after having troubles initially getting Lineage flashed and working on my S9.
I removed Magisk, reset and it still was freezing after a lock.
I reflashed Lineage through TWRP and now all seems to be back to normal with no freeze after lock.
Possibly try the steps I did and see if they worked out for you.
hey guys, you solved the issue?
i experience same Problem..
Any one notice , this issue occurs after we apply lock screen password or biometric security. in my device i notice, when i apply lockscreen password or biometric lock my phone freeze. after i remove all lock and set default to swipe...its not freezing. anyone sees that
I solved the same issue (1 hour ago, so I hope it's fixed now) installing first:
ElementalX Kernel
and than installing:
G965_Root_for_OEM_issue_devices_V5 (the lastest available right now)
Following the instruction on the XDA Thread
Hope this can be helpfull to solve it
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
KevAngelo14 said:
Its because of dm verity issues...i assume that you rooted the phone over an odin flashable stock rom. To fix this try installing either a patched stock kernel from Soldiers website or other custom kernels if you consider doing over(under)clocking.
Click to expand...
Click to collapse
What is the different in Soldie between Patched Kernel and ELS custom kernel?