I have seen that many people are having trouble in rebooting into the Recovery using the Advanced Restart Power Menu or the Quick Settings Reboot Tile on all the Nougat Roms like Lineage OS 14.1 and Resurrection Remix. The fix is very simple. You just need Root permissions to reboot directly into the recovery I have tried this on all the Nougat Roms which have this problem and Root fixes all of them. It is practically not a bug. The Roms come with no root permissions by default that is why this is happening. LOS 14.1 users flash the Root addon and RR users flash Magisk v12 or whichever is the latest version.
thank you
salimtn said:
thank you
Click to expand...
Click to collapse
I am glad that i was able to help you Please press the thanks button if this fix works for you. It motivates me a lot to help others:laugh:
Related
Hi.
I have used crDroid and I have wanted to uninstall system app, so I needed to root. All proces of rooting has been fine (by Odin), but after reboot operating system does not start and I have not got TWRP! Thank you for all your help to me!
Kubex52 said:
Hi.
I have used crDroid and I have wanted to uninstall system app, so I needed to root. All proces of rooting has been fine (by Odin), but after reboot operating system does not start and I have not got TWRP! Thank you for all your help to me!
Click to expand...
Click to collapse
Of course it will not boot. crDroid is rooted by default.
You probably tried to flash cf-auto root and that's ONLY for stock roms. Never ever use it for custom roms because every custom rom has standard root.
Because crDroid is based on CM you probably have to enable root in developer settings or flash the latest supersu trough TWRP.
You need to reflash your rom to get your rom booting again though.
Thank you!
Lennyz1988 said:
Of course it will not boot. crDroid is rooted by default.
You probably tried to flash cf-auto root and that's ONLY for stock roms. Never ever use it for custom roms because every custom rom has standard root.
Because crDroid is based on CM you probably have to enable root in developer settings or flash the latest supersu trough TWRP.
You need to reflash your rom to get your rom booting again though.
Click to expand...
Click to collapse
my sph-l720t wont tun on past logo screen after teying to root. how can i fix this? thanks Dallas
Duwhop31 said:
my sph-l720t wont tun on past logo screen after teying to root. how can i fix this? thanks Dallas
Click to expand...
Click to collapse
No idea. You haven't told us how you tried to root.
Hi guys,
I need a proper guide how to install/flash magisk on RR Oreo.
Try to flash it through TWRP and no go. Seems likely i need to flash stock image or probably stock recovery.
Thanks.
same here
For me it's working on any Oreo, just flash in twrp.
If you don't see magisk app after reboot just do another reboot and it'll be there.
Sent from my HTC One using XDA Labs
Hi,
i have an general Question in which sequence the root might been installed? On my OP2 should be working Lineage so does the root installed after flashing custom rom und gapps or before? Lineage overwrite an existing root if i didnt flash in a correct sequence.
Or is it possible that Magisk 18.1 are incompatible with Lineage 15.1?
If someone can answer this question it will makes the flashing procedere for my first time safer.
Best regards
sense92 said:
Hi,
i have an general Question in which sequence the root might been installed? On my OP2 should be working Lineage so does the root installed after flashing custom rom und gapps or before? Lineage overwrite an existing root if i didnt flash in a correct sequence.
Or is it possible that Magisk 18.1 are incompatible with Lineage 15.1?
If someone can answer this question it will makes the flashing procedere for my first time safer.
Best regards
Click to expand...
Click to collapse
flash lineage+gapps, reboot and do the initial setup, reboot in twrp and flash magisk, reboot and install magisk manager manually(lately it's not installed automatically for some reason and root doesn't work without the app).
https://github.com/phhusson/treble_experimentations/wiki/Huawei-Honor-7X
I made a page on PHH wiki for treble GSI flashing. I was able to get the Lineage and AOSP working. Most features work. I am unable to test phone features as i use this to play games only. i have set up instruction to get working to a point. This is for people who have 8.0 and boot loader unlocked
shadowsiul said:
https://github.com/phhusson/treble_experimentations/wiki/Huawei-Honor-7X
I made a page on PHH wiki for treble GSI flashing. I was able to get the Lineage and AOSP working. Most features work. I am unable to test phone features as i use this to play games only. i have set up instruction to get working to a point. This is for people who have 8.0 and boot loader unlocked
Click to expand...
Click to collapse
On latest rr v18 wifi didn't work for me. I flashed rr worked ok but couldn't get gapps installed. I tried installing twrp and flashing gapps. But wouldn't boot. Also I flashed magisk ended up in a boot loop. Thought I might have bricked my device. Flashed stock recovery and did a factory reset. Still wouldn't boot. I couldn't get back into fastboot. Finally with power plus vol up and vol down took me to install update recovery. From there I held power plus vol down to get to fastboot and was about to install twrp and restore a backup of emui. Treble is definitely not for beginners. Know what your doing and do some research before you proceed.
TREBLE IS STILL VERY EXPERIMENTAL. NOT STABLE.
allrockedout said:
On latest rr v18 wifi didn't work for me. I flashed rr worked ok but couldn't get gapps installed. I tried installing twrp and flashing gapps. But wouldn't boot. Also I flashed magisk ended up in a boot loop. Thought I might have bricked my device. Flashed stock recovery and did a factory reset. Still wouldn't boot. I couldn't get back into fastboot. Finally with power plus vol up and vol down took me to install update recovery. From there I held power plus vol down to get to fastboot and was about to install twrp and restore a backup of emui. Treble is definitely not for beginners. Know what your doing and do some research before you proceed.
TREBLE IS STILL VERY EXPERIMENTAL. NOT STABLE.
Click to expand...
Click to collapse
That is very true. If you have a github account please do help edit the page so other do not possible brick their phones.
Guys,
Anyone successful so far in setting up Magisk 17.1 on stock B35 A2017U + TWRP 3.2.1.0?
I tried following ways but everytime I flash the Magisk 17.1 using TWRP, it boot loops to recovery mode. I tried clearing Dalvik + cache everytime but in vain.
1. Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop.
2. Flash Super SU, Install Magisk 5.9.1 -> uncheck encryption, uncheck "restore dm-verify" -> Boot into TWRP and flash Magisk 17.1 -> Clear Dalvik+Cache and Restart -> Recovery Bootloop
I cannot use Super SU, blanket root due to bank & workplace apps security restrictions.
Any help/guidance will be is appreciated.
Cheers
Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.
marcdw said:
Any reason you need 17.1? If there's no pressing need go with something like 16.4. Seems to work better for some folks.
Click to expand...
Click to collapse
Thanks.
Thinking of trying with v16.7 first. If that works then great.
mandrax.prime said:
Thanks.
Thinking of trying with v16.7 first. If that works then great.
Click to expand...
Click to collapse
it does. i'm staying on 16.7
It would be nice to always have a working version of Magisk as Google updates their Safety Net. We have to update as they update.
I ran into problems today with Magisk 18.1 on the latest official LineageOS 15.1, nothing I did was able to get magisk to work (no icon, no error messages).
Has anyone else tried?
Magisk should work fine on LOS, I use it (Magisk) when I have to (i.e. when there is a particular use for it, like converting a systemless mod to a system-installed mod).
On B35, no go, phone will bootloop. Magisk should work fine on stock ROMs up to B15 N, maybe also with the B25 and B32 OTAs too. I'm not a ZTE stock ROM fan, I dont spend alot of time rooting stock, but from the few tests I did,those were my results.
If you have an exFAT SD card, installing Magisk on stock ROM may make your SD falsely show up as corrupt, only solution is to use the inferior/antiquated FAT32 filesystem.
Maybe one day I'll write my own open source root solution, just to show the Android community that Magisk isnt the only game in town for rooting modern ROMs on modern devices. I dont need to hide from SafetyNet, I dont need stupid systemless mods, I just need root that work reliably. I know this will fall on deaf ears, but Magisk is more trouble than it's worth, I'd recommend staying unrooted instead of using it. @topjohnwu is a genius and means well, I'm sure, but in the real world Magisk just isnt reliable enough.
I tried Magisk 17.3, 18.0, and 18.1 on Axon 7 B19 and B35- bootloop on every try
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Have you tried to change your twrp? What's the exact file name of it? Did you tried magisk 17.1?
Amer28 said:
Hello!
I am beyond frustrated by this constantly reappearing issue. No matter what I've tried, I simply cannot seem to get Magisk to work correctly with number of different Andoid ROMS.
Currently I'm on: Bootleggers 4.0 Android PIE (Stable - Shishuffed?)
Everything works fine, but as soon as I flash Magisk in recovery, the following bootup will show the background of booted up phone with a text in the middle appears: "Phone is starting..." And it stays that way until I force reboot by holding down the power button.
The flashable zip file itself causes no problems that I could see. It all looks fine during the install.
I also tried my luck with SuperSU but on that I get the Failure to patch Sepolicy error (regardless if I set Sepolicy Enforced or Disabled).
I just cannot seem to get a root working... The only time it worked without any issues is when I tried out the crdroid rom, but that was probably because the rom comes with su addon (nether magisk nor supersu)
If I could install THAT addon to Bootleggers, I'd be happy but flashing the su addon zip doesn't do anything as I suspected, but tried it anyway.
The versions of Magisk I tried were: 17.3, 18.0 and 18.1
My twrp is the one with experimental decyrption support - a feature that works perfectly without a hitch btw.
I would appreciate any and all help offered.
I would just like to have some kind of a supersu working.. After research, there were a few mentions of KingoRoot but I do not want to go that route - if possible.
Click to expand...
Click to collapse
Phone is starting is a bug on cr droid, los also. I don't know fixes. But don't worry you are not the only one with this issue.
Try Magisk beta 19.0. I had the same problem as you with 18.0 and 18.1, but 19.0 solved it for me...