I want to have a Samsung Stock based ROM and a LOS/AOSP ROM on my phone and switch between them, but I can't get it working. I always end up on a bootloop at the S7 Edge logo.
My bootloader and modem is updated to latest version. I wanted to install Hyper ROM and LOS 16.
So I first installed Hyper ROM, downloaded the latest version of Dual Boot Patcher, open it, allow root access, go to ROMs in the app, select my System to set the kernel. Then I go to patcher section, add the LOS-zip, gapps-zip and magisk-zip (does magisk even work with this? have tried without but also no luck) and patch them as secondary. I reboot into recovery, flash patched LOS and gapps, reboot aaaand... I'm stuck at a bootloop.
This seems to happen no matter what I try, how I switch them around, also if I patch the Hyper ROM zip as primary first. Nothing seems to help. Am I doing something wrong here?
Related
Just installed Nougat stock ROM for my S7 Edge with ODIN, and trying to root.
I installed TWRP latest version 3.01 and immediately after installed supersu 2.79 SR3 from TWRP.
At first I could not boot the phone because it kept saying I used the wrong PIN code for boot. I reflashed stock rom and was able to boot again (same PIN) - disabled PIN on boot, and reflashed TWRP and supersu, but it keeps hanging at the Samsung Logo.
Flashing stock rom solves it, but I still want to root it..
What am I doing wrong?
currently there is no reliable root for nouget roms. It is being worked on.
Cosmic Blue said:
currently there is no reliable root for nouget roms. It is being worked on.
Click to expand...
Click to collapse
Thanks for replying.
In this case - even if the goal is to root - it seems the problem is with TWRP.. Even if I do not root, but just install TWRP, the neverending bootlogo shows up..
Nougat OS has been changed that all the old rooting and twrp need to be updated.
It will be a while till developers can modify the os to allow changes.
Have posted the same question in the TWRP S7 thread that I did not see before posting this one - sorry
I was waiting for a root enabler for oreo (41.3.A.2.24), and I could find https://forum.xda-developers.com/xperia-x-performance/how-to/guide-stock-kernel-root-twrp-drm-fix-41-t3711837.
But this link is for version 41.3.A.0.401 and it does not work for everybody including me.
Since androplus still didn't bring out a new version of his kernel I tried the method from the above link.
But I'm using newer versions than in the description, I use TWRP 3.2.0, Magisk manager 5.2.2 and Magisk 15.2.
I can install the new version, twrp, the new boor image and Magisk 15.2.
I can boot and Magisk runs but the Safetynet control failes and Magisk does not enable root.
On the installation of the boot image, twrp and magisk I got some messages (marked in red)
unable to mount storage
failed to mount
Before I tried with magisk manager 5.5.1 and magisk 15.1 but then I got stuck at boot time at the sony logo.
Does anybody have a way to root Oreo (the latest version), enable DRM and enable root?
Ok I started all over again and I noticed I didn't follow the procedure first time.
So I excluded the FOTA kernel but whatever else I check no full wipe is done, I can always see the previous installed apps, it does not matter if I check Cust-reset, master-reset or reset-wipe-reason, the system is not wiped.
So that's my first problem, how to wipe the previous install.
Flashing the rom seems to be OK, same thing for flashing boot_oreo.img and twrp-3.1.1-0-dora.img.
I'm not sure about twrp 3.2.0.0 because this version is off-line now, so I tried with TWRP 3.1.1.0 and 3.2.1.0 but they all gave me the same result.
Problems start when I have to flash drmfix.zip, safety-net cleaner or magisk 15.2. The procedure tells me the flash is ok but have a look at thet attached images, I get errors while flashing. One picture for drmfix, one for safety-net-cleaner and one for magisk 15.2
After flashing all of this I can boot successfully but when I try to get root in ES File Explorer pro, it does not work. When I go into Magisk and try the afety-net check I get ctsProfile false and basicIntegrity False.
So the rom does work but I do not get root.
I tried all of this with the Italian rom 41.3.A.2.24.R1E ? I can start all over again with the UK version 41.3.A.2.24.R2E but I do not know if this makes any sense.
So can anybody tell me what to do to get it all going?
deboopi2 said:
I was waiting for a root enabler for oreo (41.3.A.2.24), and...
Click to expand...
Click to collapse
1 - Do use always Adrian DC latest fully working TWRP build for dora.
2 - You don't need a 3rd party kernel to achieve that, instead, you can easily create your own one, based always on stock kernel!
Thats the SELinux's problem.
Flash this first then flash magisk
https://forum.xda-developers.com/xp...ment/mod-sony-stock-patcher-xperia-x-t3528148
Hey, so I wanted to install a custom ROM (LineageOS 14.1) anyway, I found this site that was showing me how to but first i needed to unlock bootloader and install TWRP, i clicked on the steps for that and it brought me here:
https://devsjournal.com/how-to-root...to_unlock_Bootloader_of_Motorola_Moto_G4_Plus
I followed all the steps on that page, even installing the SuperSU, but this is where the problem began. After rebooting from installing SuperSU i was stuck on a black screen (not even backlight) and a white blinking LED light next to the fingerprint scanner. I began to look around for a fix and i found this site:
https://forum.xda-developers.com/2015-moto-g/help/problem-boot-flashing-supersu-t3507127
I followed the steps but nothing worked. Then i tried this:
https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
but that still didn't work. Flashing a new ROM does not fix the problem, and it seems nothing will. I am able to get into the bootloader and I am also still able to get into TWRP but i can't boot into ROM. I need help.
I should have attached this before but here is a picture of the bootloader. After typing in all those command the only thing that changed was the yellow text that says Software status: Modified
1) What ROM are you trying to flash onto your device?
2)The issue here appears to be that you've rooted on the stock ROM - what those pages don't mention is that those steps only work for Marshmallow stock ROMs - attempting to root on the stock Motorola Nougat ROM may cause you to bootloop and you need a custom kernel to root on stock Nougat ROMs. One way around this may be to flash a custom kernel such as ElementalX 2.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 then attempt to boot. You can boot to TWRP, connect your device to your computer, which should show up as internal storage. There, you should be able to copy a download of the custom kernel to your device and flash through TWRP. If you made a backup before rooting, you could re-flash just the boot (kernel) partition to restore a clean stock kernel then attempt to flash the custom kernel and then root.
3)You could alternatively boot to TWRP and flash Lineage. You do not need root at all to flash custom ROMs - just an unlocked bootloader. Root for installing custom ROMs is unnecessary. Be aware to flash the Lineage build matching your TWRP (i.e. 32 bit Lineage if you're running the official TWRP or any other 32 bit TWRP recovery for athene, 64 bit Lineage only is flashable with the 64 bit TWRP, else you'll get an error 255 on flashing). As always, flashing a new custom ROM requires a /system, /data and /cache wipe at least - possibly an internal storage wipe, so back up to your computer or the cloud as necessary.
4)As for the modified status, that may have been from rooting on the stock kernel. That can disappear if you were to flash a stock OTA onto your device, but that would mean flashing the NPJ25.93-14.7 Sept 2017 security patch stock ROM (latest leak we have for XT1644 devices as far as I recall), and then taking OTA updates up to April 2018 which may be risky.
echo92 said:
1) What ROM are you trying to flash onto your device?
2)The issue here appears to be that you've rooted on the stock ROM - what those pages don't mention is that those steps only work for Marshmallow stock ROMs - attempting to root on the stock Motorola Nougat ROM may cause you to bootloop and you need a custom kernel to root on stock Nougat ROMs. One way around this may be to flash a custom kernel such as ElementalX 2.0.1 https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836 then attempt to boot. You can boot to TWRP, connect your device to your computer, which should show up as internal storage. There, you should be able to copy a download of the custom kernel to your device and flash through TWRP. If you made a backup before rooting, you could re-flash just the boot (kernel) partition to restore a clean stock kernel then attempt to flash the custom kernel and then root.
3)You could alternatively boot to TWRP and flash Lineage. You do not need root at all to flash custom ROMs - just an unlocked bootloader. Root for installing custom ROMs is unnecessary. Be aware to flash the Lineage build matching your TWRP (i.e. 32 bit Lineage if you're running the official TWRP or any other 32 bit TWRP recovery for athene, 64 bit Lineage only is flashable with the 64 bit TWRP, else you'll get an error 255 on flashing). As always, flashing a new custom ROM requires a /system, /data and /cache wipe at least - possibly an internal storage wipe, so back up to your computer or the cloud as necessary.
4)As for the modified status, that may have been from rooting on the stock kernel. That can disappear if you were to flash a stock OTA onto your device, but that would mean flashing the NPJ25.93-14.7 Sept 2017 security patch stock ROM (latest leak we have for XT1644 devices as far as I recall), and then taking OTA updates up to April 2018 which may be risky.
Click to expand...
Click to collapse
Yea i should have been more clear on what ROM i was trying to flash, i wanted to flash LineageOS but when i try to flash it and boot i still get the same problem, the led light just blinks over and over until i unplug the phone or go into the bootloader. Maybe i have the wrong version of something? All i know is that the phone was working perfectly fine before and it is the XT1644 model. It had all its updates up to date but i just wanted to install LineageOS, i do now realize that you don't need root to flash a custom ROM but also i don't know where to find files for the kernel you are talking about, I also did not make a backup (lets just say im pretty stupid and i know i should have). If you have any info or need any more to further assist me, let me know. Thank you for responding!
So i tried flashing the custom kernel and it looked like everything was working, but the phone still won't boot, it just flashes the LED light, also i reinstalled LineageOS after wiping all the cache and internal storage and stuff but it still hasn't worked.
Hey, i got good news, i was able to get the phone to boot by downloading and following these steps here: https://forum.xda-developers.com/mo...e-npj25-93-t3549369/post70843323#post70843323
The phone now is working and i will attempt to install LineageOS once more. Thank you for you help!
After a painful rooting process, I finally achieved root with Magisk 19.1 and unlocked bootloader. I decided to load Super V20 ROM this morning but it has never finished the boot process. It's sticking on the Verizon boot animation. As far as the stock phone, I had version VS99510B and Android 7.0, running TWRP 3.2.1-0. When I went through the options in the Aroma loader for Super ROM, I don't think I chose anything crazy. I selected Magisk & MK2000 kernel (though, that didn't have any effect on the static screen; I was told it would).
After the first load attempt, I went back into TWRP, triple-wiped everything and reflashed again. Same effect. It just won't move past the Verizon boot animation. What could be the issue? Is there anything I can fix here or do I need to reload all the stock software? If that is the case, do I need to go back to 10B or would a newer version work better? I do intend to load a custom ROM at some point but I just want to get this phone functioning again.
Right now, I do have access to recovery (TWRP 3.2.1-0) so all is not lost. Got any help?
Thanks all.
LG V20 VS995, attempting Super V20 4.1 (8.2.18), Magisk 19.1, TWRP 3.2.1-0
Hey guys,
So I grabbed the latest factory image, patched boot with Magisk, and flashed it to the phone. Works great.
But now I want to use TWRP. I can't figure out how to get TWRP on this device.
It seems there's no recovery partition, so I can't use fastboot flash recovery twrp.img. I know I can flash arter97's kernel, which has TWRP baked-in, but I'm trying to figure out how to do it with the stock-Magisk-patched kernel.
Can someone please hit me with a clue-stick?
-edison
get the razer phone 2 arter97 kernel and flash to boot. twrp will be installed.
Marcos8760 said:
get the razer phone 2 arter97 kernel and flash to boot. twrp will be installed.
Click to expand...
Click to collapse
I'm on the PSMR3-RC002 version. Which version of Arter97 kernel works and is stable? Also, does this effect the Magisk root availability, or do I need to run Magisk patch on Arter's Kernel? I had used R12 in the past, prior to the new Magisk Boot-patch scheme, and also lost TWRP afterwards. I haven't gone and tried to reflash Arter97-R12 since I didn't want to bork anything and couldn't find an definitive answer.
MoPhoMike said:
I'm on the PSMR3-RC002 version. Which version of Arter97 kernel works and is stable? Also, does this effect the Magisk root availability, or do I need to run Magisk patch on Arter's Kernel? I had used R12 in the past, prior to the new Magisk Boot-patch scheme, and also lost TWRP afterwards. I haven't gone and tried to reflash Arter97-R12 since I didn't want to bork anything and couldn't find an definitive answer.
Click to expand...
Click to collapse
@MoPhoMike,
I use arter kernel v12.0, seems to be as stable as can be, no hiccups or issues with 12 for me and have been running 12 for about a year.
Flash arter kernel to boot "fastboot flash boot arterxxx.img" xxx is for whichever version you flash or how you named the img.
Once the arter kernel is flashed, i then boot into TWRP. Either from bootloader on your phone, select recovery or use fastboot commands.
Then you can flash magisk from TWRP.
.
NOTE, i have some posts where folks say to boot up the phone after flashing arter kernel, then reboot to recovery and flash magisk. I do it the way i noted above and never had issues.
****No need to patch Magisk that I'm aware of****
Hope this helps...
The new version of Magisk doesn't install via recovery, but from Magisk Manager, and in doing so, it patches the boot.img from the app, then reboots, which then removes TWRP. I may just try to flash arter12 and see what happens. It sucks, because I don't have TWRP installed, and therefore can't make a nandroid backup.