Related
So question is, when we ill we be able to successfully root Android M?
Have tired with TWRP. get stuck on HTC One boot screen.
Had to flash stock ROM via stock recovery...
***
TWRP 2.8.7.0
SupersU 2.46 (also tried beta version 2.52 zip
You need to use latest SuperSU 2.65. Download
When TWRP want to install SuperSU check "Do not install" and reboot.
Hmm, I've done the above and it seemed to install correctly, but the SuperSU app which I installed from the zip is saying "no SU binary installed".
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Sent from my HTC One M9 using Tapatalk
scoot0073 said:
Once you flash the superSU zip you then need to install the app from the play store and open the app to finish the process
Click to expand...
Click to collapse
Thanks, I've also tried the app store app, it says "no SU binary installed".
For me, I can't install SuperSU as system app. (not currently available in system-less root mode). And Twrp says I'm not rooted, asks to install
Try 2.64.zip no problems for me
Running 2.65
2.64 didn't work either, still get the same problem. Think I'll just try to install it the system way.
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
It worked well for me too:
http://forum.xda-developers.com/showpost.php?p=64493553&postcount=296:bien:
Gandalforce said:
Try starting from scratch. Flash stock ROM. RE flash twrp and beta supersu
Click to expand...
Click to collapse
MegaGalan said:
It worked well for me too[/url]
Click to expand...
Click to collapse
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
BenPope said:
I just reinstalled the 3.35.617.12 RUU, then TWRP 2.7.8.1_CPTB-B1, then flashed the 2.64 SuperSU zip without making system writable, rebooted without letting TWRP install su, then installed the play store app and I still get the same problem.
I just can't see what I'm doing wrong. The custom boot.img is built by the installation script - I don't need to get it from anywhere, do I? Or a custom kernel that supports it?
There doesn't seem to be the custom mount point.
If I set the /data/.supersu to SYSTEMLESS=false, it installs in the system, but bootloops (just doesn't boot, there's a repeated init permission problem with the su daemon).
Click to expand...
Click to collapse
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
sssssbarn said:
Using the same vers or twrp as you, with 2.65, zero issues.
Though i have had that problem in the past, ended up being a bad zip file.
Do you want my copy of twrp and supersu?
Click to expand...
Click to collapse
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
BenPope said:
That's a kind offer. The md5sums would be sufficient, I guess.
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
sssssbarn said:
Try these:
https://drive.google.com/file/d/0B0US5WgszgfdOTRuLUFBZ3pNQlk/view?usp=docslist_api
https://drive.google.com/file/d/0B0US5WgszgfdNDRsODFybzhlRDA/view?usp=docslist_api
Exact files i used
Click to expand...
Click to collapse
thanks for the files... fyi you transposed the numbers in the version of twrp. it is 2.8.7.1.
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Gandalforce said:
Okay, so now i tired to flash SuperSU 2.66, annddd i get stuck in bootloop.
Only 2.65 works solid.
Any thoughts?
Click to expand...
Click to collapse
I had problems with 2.66 as well. I reported it with a logcat and sticking with 2.65 for now
Same
Gandalforce said:
Same
Click to expand...
Click to collapse
Yeah same here.
Had to install TWRP twrp-2.8.7.1_CPTB-B1-hima and BETA-SuperSU-v2.65-20151226141550. then finally booted in to the OS.
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Diaa toulba said:
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Click to expand...
Click to collapse
Install Twrp or other custom recovery, dissable update cm recovery first in dev option, then install supersu.
Hello thanks a lot for your reply but twrp custom recovery requires root access
Diaa toulba said:
Hello thanks a lot for your reply but twrp custom recovery requires root access
Click to expand...
Click to collapse
What do you mean? Did you installed twrp manager app? Not that app, you need to flash Twrp/cwm.zip file through cm recovery. Or find the cwm/twrp.tar file and flash by Odin.
NeoLogY said:
What do you mean? Did you installed twrp manager app? Not that app, you need to flash Twrp/cwm.zip file through cm recovery. Or find the cwm/twrp.tar file and flash by Odin.
Click to expand...
Click to collapse
Yes I though you meant the app
I didn't know that can you give me the link to download twrp.rar
Diaa toulba said:
Yes I though you meant the app
I didn't know that can you give me the link to download twrp.rar
Click to expand...
Click to collapse
check it under Grand Android Development thread, there are twrp and cwm in zip file, can be flash through recovery. Same thread with cm12.1 that you flashed.
Flash superuser zip.
Your Rom is Pre-Rooted But you need to flash latest Superuser.zip to gain Root accesses .
Diaa toulba said:
Hello guys
I havea problem after CyanogenMod 12.1 installation on i9082
Everything works fine but
I can't have root access, it seems that the device got unrooted after the ROM
I have tried to enable developer options
And I checked root access in the setting to Apps and ADB
but I still get unrooted messages when I try to open an application that requires root
Also I tried to flash supersu from CM recovery but the installation stops in the middle
I tried several different versions of supersu but still the same problem.
Click to expand...
Click to collapse
OK now I installed CWM v.6 custom recovery
But when itry to flash the supersu zip file it gives installation complete dialogue but when I reboot I can't see the supersu icon and Im still unrooted
Diaa toulba said:
OK now I installed CWM v.6 custom recovery
But when itry to flash the supersu zip file it gives installation complete dialogue but when I reboot I can't see the supersu icon and Im still unrooted
Click to expand...
Click to collapse
Try type this in dialer *#1234#* or *#*#1234#*#*. If any of 5hose doesn't work, visit supersu thread.
OK I tried these lines but nothing happened can you give me link to supersu thread?
cm12 has root disabled by default. Activate it from developer options.
Or you can flash supersu
Diaa toulba said:
OK I tried these lines but nothing happened can you give me link to supersu thread?
Click to expand...
Click to collapse
After you flash supersu, did any app need root worked? Which version supersu did you flashed?
Used the non systemless one( 2.56 and below).
http://forum.xda-developers.com/showthread.php?t=2868133
Also might wanna try twrp recovery.
now it worked! the problem was that i had supersu installed but it was disabled from the app store thats why i didn't see its icon in the apps
thanks alot for your help, man :good:
Diaa toulba said:
now it worked! the problem was that i had supersu installed but it was disabled from the app store thats why i didn't see its icon in the apps
thanks alot for your help, man :good:
Click to expand...
Click to collapse
Good to know. New thing I've learned from your issue. Thanks for that.
I got the same problem as above I just flash su2.76 but it didn't worked out the cm update rec. Is disable ... It give installation completed but doesn't get rooted..
Disclaimer
Your warranty is now void. I am not responsible if this in anyway bricks your device or anything else that might go wrong and you cant restore it back. It is assumed that you are familiar with TWRP environment and fastboot in case you need to restore stock.
Click to expand...
Click to collapse
This was last updated on 07/02/2017
This guide will tell you how to install magisk (or magiskify as the app calls it) in order to make systemless mods possible for everything. The thing about magisk is as everything is systemless you can just uninstall magisk in the end and take an ota update without having to worry about what in your system had changed. For custom roms, though not as important, systemless mods are useful for stuff like passing safetynet.
For G4/G4 plus there is no support for Android Pay(at least where I live as there is no h/w for NFC) but various banking apps and apps like Pokemon Go.
First of all, if you want to pass safetynet you will need to use the MagiskSU method to root. This root is based on phh Superuser.
This means if you have anything like SuperSU or phh Superuser then you need to unroot first. Magisk will still work if its systemless but safetynet will not.
Also if you have Xposed installed and enabled, then it will not pass safetynet.
Requirements
1. Unlocked bootloader
2. TWRP installed
This is untested in stock NPJ25-93.11/12/14. If someone can test and report I can update this.
Please flash a custom kernel like elementalX if you are on stock rom
If you are stuck in a bootloop the you need to restore your current boot.img and everything will return back to as it was.
Steps
Take a TWRP backup of current rom. Just the boot image should be enough but everything will make it safer.
1. If you are using a custom rom, I recommend you start from a fresh flash. A dirty flash works as well.
A clean boot.img is recommended as debugging is more difficult without it.
A unrooted rom (Like official Lineage-OS) is best but if you are using a pre-rooted rom then you would need to use the UnSU script by osm0sis (tested on unofficial Lineage by Silesh.Nair)
Get UnSU script from here:
https://forum.xda-developers.com/showthread.php?t=2239421
https://forum.xda-developers.com/showpost.php?p=63615067
2. Download the latest magisk zip and uninstaller from the Magisk release thread.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. After flashing your ROM (or your clean stock rom if you will), flash the magisk zip using TWRP. If your rom is unrooted, Magisk will provide a root solution. If you are rooted with systemless SuperSU, magisk integrates itself there but you will not pass safetynet.
4. Reboot and install magisk manager from play store. Enable Magisk Hide. You can pass safetynet now.
Magisk also supports systemless host files(for Adaway) and busybox support from the app itself. You can just enable and reboot.
If you are on MM, then you can install xposed through magisk itself(but no safetynet support in this case)
Also magisk already has ports of Viper4Android as well. Creating your own mod is simple as well. For further guide search in the Magisk forum. Excellent guides are published there.
Credits:
topjohnwu for Magisk and MagiskSU development
osm0sis for unSU script
shreps for porting TWRP
mrinmaydhar for kernel info
None of this is my work. All I did was compile it so that it becomes easier for others.
If I missed anything please remind me. This is my first thread so everything might not be smoothest.
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
mrinmaydhar said:
Shouldn't we flash a custom kernel like elementalx if we are on stock rom. I think current root methods have problems with the stock boot image.
Click to expand...
Click to collapse
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
guessingagain said:
So it's working fine after flashing ElementalX first? Because I remember it boot looped before but I am not sure which version it was. If you have tested please report back so that I can add that to the post.
Click to expand...
Click to collapse
So without custom kernel, it bootloops. Any custom kernel would do
mrinmaydhar said:
So without custom kernel, it bootloops. Any custom kernel would do
Click to expand...
Click to collapse
OP updated. thanks for this info.
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
aSuperSaiyanG0D said:
I keep getting this error, any ideas what could be causing it?
I'm on stock rom (marshmallow) and I already removed supersu
Click to expand...
Click to collapse
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
mrinmaydhar said:
Nope. SuperSU exists. Search the threads for stock boot image of your ROM. Flash it and then continue installation of Magisk.
Click to expand...
Click to collapse
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
aSuperSaiyanG0D said:
I have a nandroid backup of my entire system before I installed supersu and Elemental Ex, would restoring just the boot suffice?
Click to expand...
Click to collapse
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
guessingagain said:
Yeah. But flash ElementalX though. Just skip SuperSU. If anything goes wrong just restore the boot partition.
If you want to just remove SuperSU, disable root access from within the app then perform full unroot. But it's usually better to flash stock boot.img as everything is cleaner in that case.
Edit: did you try flashing the unsu script first? Did that fail?
Click to expand...
Click to collapse
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
If I do a ROM update do I need to unSU and flash Magisk again?
Covalex said:
If I do a ROM update do I need to unSU and flash Magisk again?
Click to expand...
Click to collapse
As every ROM update flashes a clean boot.img it's necessary to flash magisk again. If your ROM comes prerooted you need to unsu otherwise not needed.
But you have to flash magisk Everytime after a ROM update. As long as you don't uninstall before updating, all your settings should be fine though.
aSuperSaiyanG0D said:
Yes I tried the unsu zip and it went thru without any errors but magisk still gave me that error
Click to expand...
Click to collapse
Did ElementalX help? Any problems after that?
guessingagain said:
Did ElementalX help? Any problems after that?
Click to expand...
Click to collapse
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
aSuperSaiyanG0D said:
No problems other than the same error about supersu being installed.
However last night I tried flashing a custom rom "resurrection remix" and magisk installed fine, downside was titanium backup didn't really like magisks root and it wouldn't restore my apps, it just froze.
Has titanium backup worked for you?
Click to expand...
Click to collapse
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
guessingagain said:
Just tried. Works for me. Normally I install the apps through play store and just restore data. Tried restoring firefox it works. Maybe it's a specific problem. Are you sure that restoring with SuperSU works without errors
Magisk is known to have problems with tibackup. A fix may be incoming(maybe an update to tibackup).
Click to expand...
Click to collapse
Yes titanium backup works fine with my SuperSU on stock, and on my tablet (Nexus 7 2013) I installed magisk and titanium works as intended.
So maybe something was just iffy with titanium backup last night, actually come to think of it I don't think Resurrection Remix comes with BusyBox.
I'll try again but install BusyBox first when I get more time.
Would using the wrong unSU version affect safetynet detection?
Covalex said:
Would using the wrong unSU version affect safetynet detection?
Click to expand...
Click to collapse
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
guessingagain said:
As long as the there are no SU links and executables left, using any unSU script should be fine.
If you are on a custom rom check /system/bin/su and /system/xbin/su are there or not.
BTW which script did you use to unSU?
Click to expand...
Click to collapse
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Covalex said:
I used unSU like you linked, but it was an older version. Reflashing the rom, updated unSU and magisk fixed safetynet.
Click to expand...
Click to collapse
You used this right?
https://forum.xda-developers.com/showpost.php?p=63615067
Or is there another unSU script that is updated? If so can you link that?
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Abbieru said:
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Click to expand...
Click to collapse
Your flashing 2.79 sr3 and TWRP rc1
mac796 said:
Your flashing 2.79 sr3 and TWRP rc1
Click to expand...
Click to collapse
I did.
Abbieru said:
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Click to expand...
Click to collapse
Abbieru said:
I did.
Click to expand...
Click to collapse
Do you have pw set up. Is TWRP asking for it when you boot to recovery are u on a custom ROM
mac796 said:
Do you have pw set up. Is TWRP asking for it when you boot to recovery are u on a custom ROM
Click to expand...
Click to collapse
Yes it asks for the password. I don't use a custom ROM
Abbieru said:
Yes it asks for the password. I don't use a custom ROM
Click to expand...
Click to collapse
Have you used that su download before. Maybe you got corrupted download. I'm not on feb yet. Maybe that has something to do with it
Try sr2. Had the same on latest tipsy sr3 didn't work. Sr2 works.
Abbieru said:
I recently sideloaded an OTA update which caused me to lose root and TWRP. I reinstalled TWRP but SuperSU will not work. I have the correct one zip. I tried many times and it won't work. When I open the SuperSU app it says there are no SU binaries installed. Any advice? I really don't understand.
Click to expand...
Click to collapse
Can you send a screen shot of what you are flashing? The actual files
Abbieru said:
Yes it asks for the password. I don't use a custom ROM
Click to expand...
Click to collapse
Last time I got in a jam I flashed boot image to a and b and that should bring your stock recovery back. Then boot TWRP again and install TWRP then boot to system once, then flash su. I think that's what I did.
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
cicish said:
Hi guys, I rooted my redmi note 8 yesterday. Everything went well except two things: on boot the error message said that "there is an internal problem" and the phone reboots/shuts down itself.
Any thoughts?
Click to expand...
Click to collapse
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
niceman2007 said:
You should explain the problem obviously if you want a help, if your phone still working you should flash twerp.img to be able to root it and solve any existing problem by flashing new rom
Click to expand...
Click to collapse
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
cicish said:
Hey thanks for answer.
Actually i did everything correctly, flashed latest twrp, tried several roms, oficial, unoficial etc., But still no result. After all these, ive flashed the stock rom which solved the problem but phone is no more rooted. So..
Click to expand...
Click to collapse
If you still want to root it again,after flasing new rom go to twero and then go to wipe then format,you should format your phone after rom flashing,try this and inform me
Yes yes! I want to root phone once again. So the steps are these:
1) booting into twrp with adb from pc.
2) from the twrp menu wiping and formating the data
3) instaling new rom
Is this true?
Thanks!
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
You mean that its possible to have root access on stock rom?
Leeban Joseph said:
If you want to root you don't have to install another custom rom unless you don't like the stock rom. If you like your current stock rom, then flash twrp in fastboot and download the latest magisk stable zip and also diasble dm-verity zip. Using twrp first flash disable dm-verity zip and then magisk zip, wipe dalvik cache and reboot to system, hopefully you would have root permission.
Click to expand...
Click to collapse
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
cicish said:
Hey, I was able to flash magical using twrp but can't flash dm-verity. It gives me some error 1 with no description. I could flash magisk. What can the problem be? Thanks!
Click to expand...
Click to collapse
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Leeban Joseph said:
From your stock rom extract the boot.img and place it on your SD card. Flash the boot image using twrp or you can also flash in fastboot, then reboot. Now boot to twrp recovery and flash dm-verity first and then magisk zip. Worked for me I'm having root permission with stock rom.
Click to expand...
Click to collapse
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
cicish said:
UPDATE: after another custom rom install failure, i got back to stock miui 11 with miflash tool. the problem is now that when i unlock the bootloader and try to flash magisk and disable-dm-verity, the system refuses to boot. the redmi note 8 logo is sticked on boot. i dont understand what i am doing incorrectly. if there are any suggestions im ready to try.
Click to expand...
Click to collapse
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Leeban Joseph said:
Is your bootloader unlocked right now or did you lock it while flashing using miflash tool.
Click to expand...
Click to collapse
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
cicish said:
the bootloader was unlocked. everything went kinda fine, until i flashed youtube vanced from magisk: when i did that, the system was unable to boot. i don't know what's happening. is there anything to do with kernel or something? really interesting what i am doing wrong.
Click to expand...
Click to collapse
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Leeban Joseph said:
I think it may be because of YouTube vanced module. If you remove the module you might be able to boot. In twrp in the advanced option select file manager and then select data/adb/magisk/ in that you will find the list of installed modules, select the one which is causing the problem and delete that folder and try to reboot.
Click to expand...
Click to collapse
I've already flashed the stock rom but this will help me next time! Thanks!
I'll stop trying for some days cause I'm really tired with tweaking so thanks and will get back!
cicish said:
i could grant the root permission on stock rom before you wrote this. thank you very much! but i still have a problem with a custom rom as it randomly turns off or reboots the device. strange
Click to expand...
Click to collapse
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
the_weird_aquarian said:
Your device reboots randomly on custom rom because probably it was made for tianma display and you have hauxing display
Click to expand...
Click to collapse
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
cicish said:
Hey, thanks for the answer. i've just googled about it and you are right. checked the TP version and it says that i have huaxing display. in the Lineage OS thread the moderator wrote that the next update will fix that bug. hopefully ill be able to install custom rom. also if you know, are there any custom roms for huaxing display? thank you man!
Click to expand...
Click to collapse
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
the_weird_aquarian said:
currently bootleggers rom,PE official and unofficial and drepfest all have reboot issues in huaxing display. Haven't tried any other rom yet..still on MIUI..waiting to get the issue fixed asap.
Click to expand...
Click to collapse
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
cicish said:
i've tried Lineage OS too and it also has reboot issue. i've checked a thread here https://forum.xda-developers.com/redmi-note-5-pro/development/derp-kernel-clang-4-4-138-t3804996 that flashing a different kernel when you have flashed a custom rom can fix the problem. idk if its safe to do
Click to expand...
Click to collapse
that thread is for redmi note 5 pro..and flashing different kernel probably won't solve it because I know few guys flashed genom kernel but still ended up with reboot in huaxing display. Maybe waiting for fix is better.