Hey,
I flashed twrp and then flashed Magisk and SuperSu in MIUI 10.2.4.0, 10.2.5.0 and 11.0.7.0... After flashing and rebooting my phone was not rooted, I tried many versions of Magisk and many times. But didn't work, anyone have any working files?? And does custom rom/kenrel helps rooting the device.
Thank you..
you need to patch the boot img. you can find patched boot img for older roms like that
nvm i had 2 tabs looked the same
Related
Hi guys, I faced some trouble while installing xposed with my galaxy A500F.
Here are the problem, my phone keep on boot into recovery (twrp) when i flashed any zip files except the root file recommended by this thread. http://forum.xda-developers.com/samsung-a-series/development/recovery-samsung-galaxy-a52015-sm-a500f-t3360802 .
I have tried other TWRP and Cynogen Recovery which is still the same. This one from the link which at least let me boot into normal.
The only method for me to boot into normal is to flash to the stock firmware via odin which then I need to reroot, reinstall twrp and try to figure out is there any other method with.
Restoring backup are not working as well for twrp which still boot back to the recovery. Some flash files, which event better ( this refer to the deodex http://forum.xda-developers.com/sam...nt/deodex-deodexed-samsung-galaxy-a5-t3232134 ) which stuck in that samsung loding screen while booting.
Any help would be thankful
Jacker31 said:
Hi guys, I faced some trouble while installing xposed with my galaxy A500F.
Here are the problem, my phone keep on boot into recovery (twrp) when i flashed any zip files except the root file recommended by this thread. http://forum.xda-developers.com/samsung-a-series/development/recovery-samsung-galaxy-a52015-sm-a500f-t3360802 .
I have tried other TWRP and Cynogen Recovery which is still the same. This one from the link which at least let me boot into normal.
The only method for me to boot into normal is to flash to the stock firmware via odin which then I need to reroot, reinstall twrp and try to figure out is there any other method with.
Restoring backup are not working as well for twrp which still boot back to the recovery. Some flash files, which event better ( this refer to the deodex http://forum.xda-developers.com/sam...nt/deodex-deodexed-samsung-galaxy-a5-t3232134 ) which stuck in that samsung loding screen while booting.
Any help would be thankful
Click to expand...
Click to collapse
Hello:
- First, TWRP to use and it is the only one that does not give me trouble installing ROMs Marshmallow (as Resurrection Remix, AICP or CM13) is the v3.0.0.1 of mygalaxya (download here). Steps for install: here
- Second, if you are in ROM Stock 5.0.2 and just want TWRP to install Xposed, I recommend using the v2.8.7 (here) does not give problems at all, although no use to install ROMs Marshmallow.
- Third, it is not necessary deodex the ROM to install Xposed, since there is a modified version of Xposed that works perfectly both as Deodex and Odex ROMs, you can download it from here.
If after using TWRP 3.0.0.1 (or higher) and enters Recovery restart always, I recommend the v2.8.7 flash on it for a normal boot.
I hope the information is usefull. :good:
I flashed magMa ux 8.5 rom for my n900t and i saw the Magisk systemless root and i got intrested! So i installed Magisk v12 with SuperSU but i found there was conflict with it so i wanted Magisk v12 with MagiskSU!
I tried dirty flashing the Magisk v12 + MagiskSU over the Magisk V12 + SuperSU! Which caused (im guessing here) caused my boot.img to get corrupted or damaged because it installs into ramdisk!
I tried a nandroid back to my old rom which, worked, wiped in twrp to reflash the rom, which also worked, but installing the magisk to the ramdisk and what it does ends up failing!
I can still boot into my system with root but it causes some conflicts with apps, such as snapchat as it thinks i have magisk still but i only have supersu! And i cannot full unroot from SuperSU app because, i think the boot.img is corrupted!
Would flashing a stock boot.img fix my problems, then reflashing rom again? Or would i have to reflash the whole stock samsung rom and things?
Im on Note 3 N900T! If reflashing the boot.img would work could someone provide a link to download the N900T!!! boot.img?
Thanks
What you call boot.img is the kernel.
Stock kernel won't work with a MM port like magma.
I advise you to do a full wipe from twrp then flash magma.
Before that, refer to the rom's thread for extensive informations about Magisk and systemless root.
Hi, I recently installed the lineage 14.1 os and Gapps on my phone but now I'm having trouble rooting it. I tried rooting it with Kingoroot but it reboots on 90%. So I googled it and apparently I need to flash the SuperSU zip file. So I rebooted in recovery and tried flashing the zip. It didn't want to flash at first because the zip verivication was on so I turned it off and the flash said successful. But it didn't work. Can someone help me rooting my phone?
unknowncath said:
Hi, I recently installed the lineage 14.1 os and Gapps on my phone but now I'm having trouble rooting it. I tried rooting it with Kingoroot but it reboots on 90%. So I googled it and apparently I need to flash the SuperSU zip file. So I rebooted in recovery and tried flashing the zip. It didn't want to flash at first because the zip verivication was on so I turned it off and the flash said successful. But it didn't work. Can someone help me rooting my phone?
Click to expand...
Click to collapse
Lineage os is prerooted you can enable root from developer settings
I've messed everything up and now I'm devastated!
My S8 stucks at the very first screen (where it says: SAMSUNG GALAXY S8 - powered by android). It doesn't boot further this very specific screen. I have tried to update Magisk and Magisk Manager but only Magisk Manager seems to get updated successfully while the app suddenly says that the latest version of Magisk Manager required Magisk V19.XX hence I've tried to install it via TWRP. According to log screen, I've managed to install magisk via TWRP but after booting up, I opened Magisk Manager where it now says that Magisk isn't installed. I therefore boot into TWRP and tried to fix it since some apps of mine that required root access wasn't working anymore. So, I thought I must have lost root access. I once again boot into recovery, I uninstalled magisk and install an older version of magisk and magisk manager and also the no_verity patch. After that my Galaxy S8 won't boot up. It just stucks at the very first screen. My S8 (international version) is still on Nougat stock samsung firmware and I can enter TWRP but the phone remains freeze and stubbornly refused to boot up.
I'm quite devastated and I hope you guys can help me fix this issue!
Thank you!
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
tosmaniac said:
Hi, well sorry if I am stating the obvious but I would format and install one of the many custom roms available...
Click to expand...
Click to collapse
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
cocolish said:
Are there any solutions other than flashing a custom rom? Meanwhile, I have managed to flash Android 9 via ODIN and have TWRP installed but it won't boot up and stucks at the very first booting screens.
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Have you tried just flashing stock rom only to see if it boots up. You may have to do a clean install.
Problem sounds like you haven't decrypted phone and flashed no verity zip file.
You won't need to flash a custom rom to fix this.
As for magisk have a look through this very helpful guide for installs and troubleshooting.
https://www.didgeridoohan.com/magisk/HomePage
I've managed to solve this issue by myself. But still, thank you so much! It's the thought that counts ? And yes, I've figured out that I haven't decrypt my S8. But everything is absolutely fine now and I feel extremely relieved. It took me 1 day to fix this major issue and I've encountered lots of difficulties while trying to fix this like bootloops, system won't boot up and managed to stuck at the very first booting screen again and the phone boot past the first booting screen and stucks at the second booting screen, and also bootloader error and stuffs like where realization hit me that I can't restore my nandroid backup while still on Nougat because after restoring it won't boot up. I therefore managed to flash Android 9 and twrp. My S8 is now on Android Pie with custom recovery and rooted (via Magisk).
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.