Hello people. I am facing an issue on my Moto X Play XT1562 Indian dual SIM variant. I recently unlocked bootloader and flashed SuperSU v2.46 on stock ROM 6.0.1 and I faced a bootloop. Then I removed the SuperSU via SuperSU uninstaller zip and flashed SuperSU V2.62 beta. Then it booted normally but my proximity sensor and other sensors related to Moto gestures i.e Camera gesture and Moto display stopped working. Even CPU-Z shows nothing on these sensors only. I tried factory reset, re-root, tried a new ROM (Pure Nexus 7.1.1) and also flashed stock firmware. Yet the sensors didn't work.
I don't think there's a hardware issue as I haven't dropped my phone and I have no screen protector.
Is there a fix for this issue?
Related
I'm running stock marshmallow 6.0 on my x play rooted with supersu 2.62-3, latest xposed and ultra kernel r5.
Sometimes it crashes and results in a bootloop, I've restored the firmware from a backup everytime this happens (starting from 0, like if it was a new device).
Does any one knows why this happens? I've tried to not install xposed and the same thing happens. My guess would be supersu, but for now I'm trying to not install ultra kernel and everything is fine for now but I will report if it happens again.
What version of supersu is the latest compatible with X Play? ASFAIK it's 2.62-3 am I right?
I use BETA-SuperSU-v2.62-3-20151211162651 and Xposed 3.0 alpha4 & v80-sdk23-arm without any issues on 6.0.1
I recall trying different SuperSU versions and had boot loop issues when I initially rooted my device, a forum post pointed me to that specific version.
Maybe give that version a try if that is not what you are using?
Disable all the Xposed modules, then re-enable one at a time to see if a specific program is causing the issue.
Remove Xposed all together.
Remove ultra kernel r5?
Move to 6.0.1?
Something is causing instability. That's the order I would try.
I removed Ultra Kernel and everything's fine atm. I checked and some people are having the same problem as mine with ultra kernel.
Hey folks,
i have a big problem updating my Axon 7 to B27. I've tried everything, stock system B20 then updating to B27, causes the same bootloop as restoring (system or TWRP Backup) B27 direct through TWRP.
The next thing is i can't update my Recovery to the newest TWRP version, i get only black screen if i start to the recovery after updating. Only the recovery from tenfar B20 root is working so far.
I'm unlocked and rooted, but tried to lock the bootloader with the same result as above.
@DrakenFX, @Unjustified Dev, maybe you have some ideas?
Best Regards
Even if i update with @DrakenFX B27 Bootstack and Update i only get to the SIM lock screen and the phone reboots.
Is nobody else facing this problems?
Anybody else using this rom? I've been using this for 2-3 days and its been solid.
Just dont forget to install the SIM patch on recovery and use SuperSU not the lineage_root_addon for root.
http://www.cyanogenmods.org/forums/topic/lineage-os-13-redmi-note-2-marshmallow-rom/
Edit: GPS and SIM working need to flash a patch.
Edit2: Magnetic sensor not working, Orientation sensor not working
Edit3: Nevermind, its the same lineageos13 by Dinolek on this thread: https://forum.xda-developers.com/re.../6-x-based-roms-nofearnohappy-kernel-t3494631
I flashed and lost the IMEI. I fixed it installing this patch (from TWRP)
SIM FIX using recovery:
https://www.androidfilehost.com/?fid=817550096634760617
Hi to all reading this, I have a moto g4 with an unlocked bootloader and the latest twrp installed. I recently tried downloading Magisk v14 and flashed it in twrp. This put my phone in a bootloop (which is now fixed) I now want to attempt flashing magisk again but I also don't want have any problems. What are the possible reasons for it not working?
I rooted using the standard process, unlock bootloader, flash twrp img, flash twrp zip, flash magisk zip. But now my fingerprints register but don't work when trying to unlock. Anyone else with same problems, or a solution to this one?
I'm sorry I solved it myself. It was due to my matte screen guard. It worked perfect after removing it.