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
Related
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?
Hi,
I have a problem on my phone (Asus Zenfone 2 Laser running on rooted android 6) : I can't turn wifi on, when i click on the wifi button it does absolutely nothing...
It happened when I updated from magisk 16 to magisk 17, I got bootlooped due to a bug, after this I flashed the uninstall magisk zip and I flashed magisk 16 again, and it happened at this moment.
I already tried :
Updating to magisk 17.1 (the fixed version)
Power cycling my phone
Restoring a rootless save
(I try to avoid the factory reset but if there's no other solutions I'll do it.)
Need help for reflashing kernel
Yami.Neko said:
Hi,
I have a problem on my phone (Asus Zenfone 2 Laser running on rooted android 6) : I can't turn wifi on, when i click on the wifi button it does absolutely nothing...
It happened when I updated from magisk 16 to magisk 17, I got bootlooped due to a bug, after this I flashed the uninstall magisk zip and I flashed magisk 16 again, and it happened at this moment.
I already tried :
Updating to magisk 17.1 (the fixed version)
Power cycling my phone
Restoring a rootless save
(I try to avoid the factory reset but if there's no other solutions I'll do it.)
Click to expand...
Click to collapse
Hi again,
Update : I learnt on the magisk wiki that this issue can be solved by reflashing the kernel.
So if anyone can help me to reflash my actual kernel/a new one compatible with my ze500kl, aka Zenfone 2 laser. (My actual kernel is "3.10.49-perf-gcb6a1aa")
Thanks in advance !
Hi again,
I tried to flash the image of my original firmware's zip (found in this zip from the official Asus website)
http: //prntscr.com/kpoq3d
My phone booted normally but I still can't turn the wifi on...
Afterwards I tried to flash the firmeware's zip from twrp, wich didn't worked.
(I also tried to sideload via ADB, wich didn't worked too.)
Hi.
I've just received a brand new Nubia Z17S and have found a problem when trying to flash Magisk.
I've been able to unlock the bootloader and install TWRP. Then, after formatting data and rebooting again, I've flashed Magisk 16.0, since I had the zip file on a flash drive. My idea was to update to the latest Magisk release later from Magisk Manager.
Magisk 16.0 appears to flash correctly, and the superuser feature works fine, but Magisk log shows a mount error and Magisk isn't activated. So I have a rooted phone, but I can't pass SafetyNet check. If I try to flash the universal Safetynet module, Magisk throws an error and from TWRP it says Magisk sisn't installed, which is right (it's installed but unable to activate).
To check if a newer version solves the issue, I've tried to upgrade to Magisk 17.1 from Magisk Manager. It seems to install fine, but then the phone only boots into fastboot mode, over and over again, and never gets to start Android. I've had to flash a stock rom from the emergency recovery mode, flash TWRP and Magisk 16.0 again. Now I have a rooted phone but Magisk stays unusable.
Has anyone here been able to make Magisk 17.1 work on Z17S? Or should I stick to 16.0 until a fixed version is released?
Thanks.
Hi, I forgot to mention I was finally able to flash Magisk 17.3.
In order to do so, I had to wipe everything and revert to the latest stock rom, v 1.11, and then I flashed TWRP again and flashed Magisk 17.3 from there. The first time the phone booted, it got stuck on the "Be yourself" message. But then, after wiping data, the phone finally booted, and Magisk is working fine. The phone is rooted and I pass the SafetyNet check.
]Can anyone help me I was from India, I installed TWRP for English version at last I get, I had installed all miui ROM, MOKEE, tebble, rom, no one works now at last I was using EN 111 works fine... But FINGERPRINT, WIFI, HOTSPOT are not working,... It says FINGERPRINT ENROLLMENT DIDN'T WORK TRY AGAIN WITH DIFFERENT... WIFI IS NOT SEARCHING... CLOSE ON OPENING NO SCANN
---------- Post added at 04:31 AM ---------- Previous post was at 04:29 AM ----------
Can anyone help me I was from India, I installed TWRP for English version at last I get, I had installed all miui ROM, MOKEE, tebble, rom, no one works now at last I was using EN 111 works fine... But FINGERPRINT, WIFI, HOTSPOT are not working,... It says FINGERPRINT ENROLLMENT DIDN'T WORK TRY AGAIN WITH DIFFERENT... WIFI IS NOT SEARCHING... CLOSE ON OPENING NO SCANN
jman0 said:
Has anyone here been able to make Magisk 17.1 work on Z17S?
Click to expand...
Click to collapse
Of course yes. It's not big deal.
https://forum.xda-developers.com/pr...ment/8-1-0-t3839168/post77963413#post77963413
Hello, i have an issue that my Wifi stopped working on my device, it is unable to be turned on, only thing that works is mobile data, after unlocking, everything was still fine, but after rooting using magisk, it stopped working. Is there any fix for this issue? Ive already tried other things but they failed.
You tried to flash vendor.img
Xiaomi Firmware Updater
The ultimate script that provides firmware packages for Xiaomi devices.
xiaomifirmwareupdater.com
The phone has been fully reset, and all works fine now, but i still need to know safe way to root the device.
Update : ive succesfully rooted using proper magisk zip using OrangeFox recovery and it was a success, this thread is no longer needed to be replied.
With latest Stock ROM for M307FN (M307FNXXU4CUJ2) the Auto Rotation is working. But after flashing TWRP and rooting with Magisk the Auto Rotation is not working. Tried several things like
adding 'ro.sf.hwrotation=180' into build.prop (which wasn't written there)
adding 'libgnustl_shared.so' file to system/lib (which wasn't also there...but also not on Stock)
But the problem is still there. Does anybody know how to fix this?
I feel your pain, let us know when you find a fix lmao. Trying for days.
Also someone tried to report the bug on magisk github, but didn't post a log so it got closed... Maybe imma try posting a log...
Would be nice if you do this. TIll yet, i did not found a solution. I flashed a Custom ROM and the Auto Rotation is working again (but therefore a lot of other things do not)
You have to patch the latest version of TWRP with the latest magisk canary and flash the image to the recovery partition. Reboot and the rotation must be working properly.
I'm willing to do this again, but tell me: Where do you see a difference in the way i was doing and the steps you did wrote?
If the version of TWRP does not match the version of magisk canary it results in a bug - auto rotatation not working. So if magisk has an update and twrp not yet, it is better to wait for both before updating one of them and the bonus bug.
Tell me: What TWRP version matches a specific Magisk version? Where do you have this information from?
In my case there was no update. I installed latest Magisk and TWRP on a freshly installed Stock ROM.
And you did not replied to my previous question.