So i flashed twrp on top of the stock rom and it just keeps bootlooping it not even getting to the samsung logo just the galaxy s6 splash screen
Heres a odin screenshot http://prntscr.com/h13jdx
Flash Magisk. It' s dm-verity
arkasha17 said:
Flash Magisk. It' s dm-verity
Click to expand...
Click to collapse
its need to flash magisk when you are on stock and flash twrp recovery?
what cause the dm-verity and what is that ?
paul222008 said:
its need to flash magisk when you are on stock and flash twrp recovery?
what cause the dm-verity and what is that ?
Click to expand...
Click to collapse
Just search. From twrp flash Magisk.
Inviato dal mio SM-G920F utilizzando Tapatalk
DON'T FLASH MAGISK v14.0
Like the others said, you need to flash magisk but don't flash magisk v14.0. I had huge issues with my SM-G920F with magisk v14.0 (I kept on losing root, modules didn't work correctly...) so I just went back to the last working version, which was v13.3. You can still install the same modules (by manually flashing them through apps like flashify), but you will never lose root (or at least I haven't). I lost root after 3 minutes of use on average on v14.0 and never lost it once on v13.3. However, the best way to do so it to run the uninstall script in twrp if you had magisk previously installed and then flash the older versions. The older versions can be found on the original magisk developer section right at the bottom where it says downloads.
Related
I have a Honor 8 with Emui 5.0.1, Android 7 model FRDL09 , build FRD- L09C432B394.
I have unlocked the bootloader and installed 3.0.3-0 Twrp but when i try to install SuperSU from the recovery i can't (the phone start the operation but after 2 or 3 seconds on the screen there are some very fast message and the phone just reboot. I was able to read the message that is:
- System-less Mode, Boot Image Support required
- creating image
I tried with 2 different version of SuperSU (sr3-SuperSU-2.79-Sr3- 2017 0114223742.zip and SuperSU-v2.82-Sr5-Permissive.zip but i have the same problem
Anyone can help to figure out what i'm doing wrong?
Tia
Install twrp 3.1.1 from open kirin thread.
I use magisk for root, and any problem with this recovery.
I use EMUI 5 b402.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
xuso77 said:
Install twrp 3.1.1 from open kirin thread.
I use magisk for root, and any problem with this recovery.
I use EMUI 5 b402.
https://forum.xda-developers.com/honor-8/development/twrp-t3566563
Click to expand...
Click to collapse
Yea i just did that reading better the forum and i figured out that i was using the wrong twrp version
I still used the official SuperSu 2.82, do you think it is better go for magisk?
Thank you for your reply
For me is better magisk.
When I want update my device, I uninstall magisk with the uninstalled twrp zip, and then, I update with the full update package and 0 problems.
xuso77 said:
For me is better magisk.
When I want update my device, I uninstall magisk with the uninstalled twrp zip, and then, I update with the full update package and 0 problems.
Click to expand...
Click to collapse
Sadly i can't find the original rom of my phone so i can't reflash it to remove the changes done by SuperSU so i need to stick with it even if i want to try magisk
Flash this Version from TWRP
SR1-SuperSU-v2.82-SR1-20170608224931.zip
Hi all,
Just tried to flash the latest Magisk (16.0) from TWRP on my honor 8 running B360 and am now in a a bootloop.. Nothing new fixing this but does anyone know what version of magisk will work or why this could have happened? I'm keen to get it working!
Cheers
So I've tried to flash back to an unrooted rom and must've broken something because I now cannot get into TWRP at all. I fastboot flash version 3.1.1-1 which has worked for me countless times and fastboot says it flashes fine but when I try and boot into it with power+vol up the phone goes off for a second, vibrates, pauses for another second before vibrating again and then showing the device cannot be trusted screen. Has anyone ever had this? I'm not sure what else to try here (I also tried flash stock recovery and it does the same thing)
Edit: Got TWRP back, I think my device must be on an earlier version (even though it's corrupt). In case anyone else finds this, this thread helped me https://forum.xda-developers.com/honor-8/help/please-help-boot-enter-recovery-t3660408/page3
First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.
Mumtaz77 said:
First of all: if after flash magisk and you have a bootloop, just flash the uninstall package from magisk website. This package revert back to the original kernel and uninstall magisk.
Second job: if you want to install magisk, first install magisk manager app. And before flash the magisk from twrp, in the magisk manager check the "Preserve force encryption" and "Preserve AVB 2.0/dm-verity". If this option (or just the first) not checked, the magisk flashing results is a bootloop.
Click to expand...
Click to collapse
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!
JoshSnitz said:
Oh thanks for the info I didn't know that (have never used magisk) - I'll give it a go tomorrow!
Click to expand...
Click to collapse
Unfortunately it didn't work - resulted in the bootloop again
Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?
xuso77 said:
Latest stable v16 works fine.
What twrp version have?
You have the 3.1.1 openkirin version?
Click to expand...
Click to collapse
Yeah, using twrp-3.1.1-1-frd.img. Phone is EMUI 5.0, android 7.0 FRD-L09C432B360
Edit: I have the AL version with dual sim that I've re-branded. Could this be causing an issue?
I don't think so, but I don't know.
Can you try to flash the last magisk developer version, or wait for another user that rebranded the honor.
Good luck!
You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.
hackslash said:
You have to use older version of Magisk. V16 only works on newer firmwares. Try v13 or v14, they both will work flawlessly.
Click to expand...
Click to collapse
Oh, I'll give it a go. Is it more reliable to just flash through fastboot or the zip through twrp?
Edit: Both v14 and 13 gives boot loop when flashed from twrp
I updated my op6 from 5.1.6 to 5.1.8 using twrp. But after that i lost root access and lost twrp recovery. Then i flashed the twrp and magisk again. the phone gets rooted but wifi is broken after doing this. Has any of u have the same issue as mine?
davidsamuelib said:
I updated my op6 from 5.1.6 to 5.1.8 using twrp. But after that i lost root access and lost twrp recovery. Then i flashed the twrp and magisk again. the phone gets rooted but wifi is broken after doing this. Has any of u have the same issue as mine?
Click to expand...
Click to collapse
I had that same issue today - i downloaded the rom from OnePlus directly, flashed it back to factory, and then followed the instructions in
Code:
https://forum.xda-developers.com/oneplus-6/how-to/oneplus-6-magisk-root-oos-5-1-5-t3794440
Works like a charm without TWRP for me.
davidsamuelib said:
I updated my op6 from 5.1.6 to 5.1.8 using twrp. But after that i lost root access and lost twrp recovery. Then i flashed the twrp and magisk again. the phone gets rooted but wifi is broken after doing this. Has any of u have the same issue as mine?
Click to expand...
Click to collapse
Did you reflash twrp directly after OS update without rebooting?
Correct. Reboot is not required. Boot to recovery, flash OOS, flash TWRP and Magisk and reboot.
After updating os.
Flash twrp
Reboot recovery
Flash magisk.
Follow this order and the problem will be solved. I had the same problem too.
davidsamuelib said:
I updated my op6 from 5.1.6 to 5.1.8 using twrp. But after that i lost root access and lost twrp recovery. Then i flashed the twrp and magisk again. the phone gets rooted but wifi is broken after doing this. Has any of u have the same issue as mine?
Click to expand...
Click to collapse
You are losing wifi because you have one of the early versions of twrp that used a kernel from HOS.
The magisk non twrp method works great.
Also, there is an updated thread about rooting that has the new TWRP installer. It wont break wifi.
https://forum.xda-developers.com/oneplus-6/how-to/guide-how-to-install-official-twrp-t3801558
Basically you boot into twrp, Install latest rom, run the updated twrp installer, install magisk.
Thats the new normal on this phone btw (install rom, install twrp, install magisk) because the kernel is part of recovery or something like that lol
Hi, the title says almost all... I can't get past the TWRP screen on both official TWRP and Bluespark one, only solution is flashing Magisk but i have to remove it in order to use some Apps that detect it, any advice...?
Fastboot flash a 5.1.9 rom and update from there, if ur not gonna run magisk do you need twrp?
Did you try to use the latest Uninstaller?
whizeguy said:
Fastboot flash a 5.1.9 rom and update from there, if ur not gonna run magisk do you need twrp?
Did you try to use the latest Uninstaller?
Click to expand...
Click to collapse
I need twrp so I can flash magisk if I need it.
And yes, tried to use latest versions of Magisk and, obviously, the Uninstaller, every time I run the Uninstaller it just boot back to twrp.
Anyway I've solved by dirty flashing Pie, now it's working, thanks
I'm running stock ROM on unlocked bootloader with root through Magisk. I've been using TWRP, but changed over to Blu_spark TWRP recently.
Every time I update my OS Ota, I lose TWRP and Magisk. The Magisk app is installed, but the ROM is not rooted. If course, if I try to install patch the system so it's rooted through the Magisk app, it says that it can't unpack the file. If I reboot to recovery to install from there, I get the stock recovery, not TWRP.
I tried to re-install TWRP and Magisk once before, and borked my phone. I had to quote and start from scratch. I lost all data since I wasn't rooted and Titanium Backup would not run.
What is the proper way to get TWRP and Magisk back after an OTA update?
Flash them after you flash update zip. If you don't you will lose recovery and root every time. Gets overwritten by stock recovery. Normal behavior
Sent from my ONEPLUS A6003 using Tapatalk
So you're saying that instead of doing the OTA update, I should download the update from here, and manually update it ? Can I just install the update? I'm rooted, (well, I was) so the OTA will only download the full update. Is that required instead of the update?
I really have to do a full re-install for every update? That sucks. A lot.
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
MickyFoley said:
Full reinstall? No. You just have to flash the full ROM. This doesn't mean, you'll loose all your data: Just TWRP, Magisk and (if you have it) your custom kernel. You only have to flash TWRP (or simply boot into it), Magisk and kernel (again: if you have it) after the update. Done.
Click to expand...
Click to collapse
Ok. Cool. I tried that last time, but it failed. As a result, I'm a bit anxious about doing it again. Hopefully, I won't have any problems this time.
Thanks for the info.
I have had similar troubles as you, here's an overview of how to solve those problems.
OTA through OS:
Download and install OTA
Use Magisk Manager to download the TWRP A/B retention script and install it
Install Magisk to current and inactive slot
Reboot
Guys I am using latest blu_spark twrp. my bootloader is unlocked and I am running oxygenOS openbeta23. Following is my problem.
My flash order: (Note: already I have bue_spark twrp recovery running without issues)
1. Flash the full OTA(openbeta)
2. Flash the blu_spark twrp zip file on both active and non active slots.
3. Flash the latest magisk zip file. If step 3 is not successful means I will try to reboot in to recovery and again flash the magisk installer zip.
Until some time back all this worked fine. But for last 2-3 times although the flashing process of twrp zip on both slots ends with success message, when I reboot to recovery from twrp in order to flash magisk, the device boots in to stock recovery. I don't know how even after flashing twrp zip on both slots successfully why the devices bootbback to stock recovery. Then to have blu_spark twrp I have to connect my device to a computer in fastboot mode and then boot in to custom recovery using the blu_spark twrp image file and again flash the blu_spark twrp zip file which is inconvenient and also requires a computer.
Am I missing anything here?? If yes why this method was working perfectly before? Please somebody help.
Regards,
Sivabalan K
I flash in following order my stable updates
Flash full rom zip
Flash bluespark recovery
Restart into bluespark recovery
Flash magisk
Restart into Android
Everything works flawless. Magisk installed with all the modules running
Hi guys,
Don't you need to disable lock pattern/PIN or fingerprint/face ID? And don't need to uninstall magisk modules?
I never update my OP6 from my initial unlock/twrp/magisk and I'm a bit anxious to do it now...
Thanks
PS : I'm using original twrp (3.2.3-1), is this a problem?