My goal is to get a GSI with Android 11 or higher installed with the corresponding Mint Kernel. The reason being is I can't Magisk root a GSI (tried various methods like: Magisk patch TWRP recovery, install Magisk zip in recovery) and I believe the ramdisk=no is the problem on the SM-A505W variant of the Galaxy A50. I have rooted Pixel phones easily in the past.
I read a suggestion somewhere that installing Mint Kernel could help make rooting easier since Magisk is pre-installed (true?), but I can't get any GSI + Mint Kernel to boot.
GSIs attempted = lineage 18.1, 19.1, Palladium (android 11), SparkOS, Pixel Experience (android 11, 12)
I've then gone to fetch the corresponding Mint Kernel from https://github.com/FreshROMs/android_kernel_samsung_exynos9610_mint/releases
Is my variant just not able to work with Mint Kernel? I'm sure someone, somewhere knows a GSI and Mint Kernel combo that works and allows for Magisk rooting. If so, pls identify versions and any methods you used.
frustrated
p.s. Magisk 25.2 is my preference as I like this version best so far
p.s.s. I do use the key combo to boot from recovery vs system when trying to boot with Magisk when using only a GSI. Only been able to root stock firmware by Magisk patching AP file and flashing with ODIN, then using key combo VOL_UP + POWER (hold a few seconds) when powering phone to boot.
If you're able to boot a GSI with the stock kernel but not the Mint kernel, it sounds like the latter has some dependencies that a GSI does not provide.
Not having ramdisk should not prevent root. Using the stock kernel and a GSI, flash Magisk in TWRP following the GSI; once you install the Magisk app, you should have root access. This is the method I use on my Tab A 8.0, running the AOSP 13 GSI with the CUK4 kernel.
V0latyle said:
If you're able to boot a GSI with the stock kernel but not the Mint kernel, it sounds like the latter has some dependencies that a GSI does not provide.
Not having ramdisk should not prevent root. Using the stock kernel and a GSI, flash Magisk in TWRP following the GSI; once you install the Magisk app, you should have root access. This is the method I use on my Tab A 8.0, running the AOSP 13 GSI with the CUK4 kernel.
Click to expand...
Click to collapse
After GSI is installed, with stock kernel, once I flash Magisk 25.2 in TWRP (tried several TWRP versions I could find 3.5, 3.6, 3.7...) when I boot with VOL_UP + POWER (held for a few seconds) I either boot into recovery again OR dont have root when booted into android.
I believe this is the procedure (from what I've read).
With stock firmware, I get root holding VOL_UP + POWER (for a few seconds prior to booting). I dont use TWRP in this case, rather ODIN to flash Magisk patched AP file.
GreekFire123 said:
After GSI is installed, with stock kernel, once I flash Magisk 25.2 in TWRP (tried several TWRP versions I could find 3.5, 3.6, 3.7...) when I boot with VOL_UP + POWER (held for a few seconds) I either boot into recovery again OR dont have root when booted into android.
I believe this is the procedure (from what I've read).
Click to expand...
Click to collapse
If you're flashing Magisk in TWRP, you don't need to boot into recovery. The recovery hijack is only for use with the stock recovery; no key combo is needed to enable root.
Again, the Ramdisk field does not have anything to do with whether or not you have root. When in the Magisk app, the Installed field should show the Magisk verision (25200). If it says N/A, you don't have root.
If you continue to have issues, this is what I suggest:
Use Odin to reflash everything back to stock
Flash the latest TWRP build for your device
Boot into TWRP, format both /system and /data (do NOT wipe /boot)
Install GSI to /system
Install Magisk
Reboot to system
V0latyle said:
If you're flashing Magisk in TWRP, you don't need to boot into recovery. The recovery hijack is only for use with the stock recovery; no key combo is needed to enable root.
Again, the Ramdisk field does not have anything to do with whether or not you have root. When in the Magisk app, the Installed field should show the Magisk verision (25200). If it says N/A, you don't have root.
If you continue to have issues, this is what I suggest:
Use Odin to reflash everything back to stock
Flash the latest TWRP build for your device
Boot into TWRP, format both /system and /data (do NOT wipe /boot)
Install GSI to /system
Install Magisk
Reboot to system
Click to expand...
Click to collapse
thanks for the reply.
Followed the above steps, "installed" field = N/A so no root
Can't believe how hard it is to get root on this device with a GSI...
Using TWRP from: https://www.recovery-mode.com/twrp/twrp-3-7-0-for-samsung-galaxy-a50-a505x-update-20221026.html
TWRP file/version download=TWRP_v3.7.0-Unofficial_a50-1666700564.tar
GreekFire123 said:
thanks for the reply.
Followed the above steps, "installed" field = N/A so no root
Can't believe how hard it is to get root on this device with a GSI...
Using TWRP from: https://www.recovery-mode.com/twrp/twrp-3-7-0-for-samsung-galaxy-a50-a505x-update-20221026.html
TWRP file/version download=TWRP_v3.7.0-Unofficial_a50-1666700564.tar
Click to expand...
Click to collapse
Weird. Do you get any errors in TWRP when flashing Magisk?
Were you able to root the stock ROM?
V0latyle said:
Weird. Do you get any errors in TWRP when flashing Magisk?
Were you able to root the stock ROM?
Click to expand...
Click to collapse
Installation completed (appeared) successfully in TWRP. No errors when I read line-by-line. I installed it as a zip.
I can root the stock ROM, but didn't do it on this attempt before installing GSI. I followed the instructions above to a tee just to make sure.
To root the stock ROM I have to magisk patch the AP file (from stock) and flash that with ODIN. Then use special key combo to boot (VOL_UP + POWER) with root.
GreekFire123 said:
Installation completed (appeared) successfully in TWRP. No errors when I read line-by-line. I installed it as a zip.
I can root the stock ROM, but didn't do it on this attempt before installing GSI. I followed the instructions above to a tee just to make sure.
To root the stock ROM I have to magisk patch the AP file (from stock) and flash that with ODIN. Then use special key combo to boot (VOL_UP + POWER) with root.
Click to expand...
Click to collapse
you can't flash magisk as zip to the recovery on old samsung devices "read magisk FAQs for samsung devices". Check out the fresh discord server so that you can get more assistance directly from the dev.
Related
After Root open beta 17 stook on boot logo
Any solution
Amar5373 said:
After Root open beta 17 stook on boot logo
Any solution
Click to expand...
Click to collapse
Well is it really too hard to explain your problem in proper sentences? So you wanted to root your phone. What did you use? Magisk? SuperSU? Which version? I can't help you if you don't provide information..
I have the same problem. Neither SuperSu nor Magisk works.
persa2011 said:
I have the same problem. Neither SuperSu nor Magisk works.
Click to expand...
Click to collapse
supersu not working please help
Use SuperSu 2.82
2.82 works fine for me! Many thanks!
My Steps For Stock OB17 Zip *Same Steps for Magisk V12 Or SuperSu V2.82*
Code:
Flash latest TWRP From Blu_Spark V35 Or Stock TWRP
Format Data Reboot TWRP
Wipe All
Copy [URL="http://downloads.oneplus.net/oneplus-3/oneplus_3_oxygenos_openbeta_17/"]OB17[/URL], [URL="https://forum.xda-developers.com/devdb/project/dl/?id=25000"]TWRP V35[/URL], [URL="http://www.supersu.com/download"]SuperSU V2.82[/URL] To Internal Storage
Flash OB17
Select Flash IMG, Install TWRP Reboot TWRP (So Stock Rom Doesn't Replace With Stock Recovery)
Wipe Cache/Dalvik
Flash SuperSU
Reboot = Profit
*Optional*
Take A Backup Of Rooted Boot IMG (If You Flash A Custom Kernel And Run Into Issues You Can Restore Rooted Boot IMG With Ease)
Flash Kernel Of Choice (Beware Because Of No Source Code And Kernel Changes Might Be Some Issues With Custom Kernels)
TO root latest beta an stable version you can follow this guide:
As the title says I am unable to boot after flashing Magisk (tried v16 and v15.3). It boots fine without magisk but of course no root and no custom recovery. Any help would be appreciated. Didn't have any problems on the previous stable build.
You need to first flash OOS 5.1 let it boot, then go to fastboot and flash twrp then go to twrp and flash magisk, only way to get root
hello, that's what I did and it worked well
this has happened here since 5.0.4
Try to use lastest blu-spark's TWRP, then flash 5.1 & Magisk without extra boot in the middle.
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
ToucanSam said:
Things I noticed when upgrading:
A) The latest TWRP for dumpling appears to be broken. I get an error mounting /vendor when I use it. I switched to the previous version (20180309) and the error went away and everything seems to work.
B) You may very well have Xposed installed. If you do, there is an SDK bump between OOS 5.0.x and 5.1.x (26 -> 27). You'll need to disable this module either before you install the update (or assuming you already have) remove the module using something like Magisk Manager for Recovery to remove it (reboot to recovery, install module, run mm from terminal, follow prompts).
-Toucan
Click to expand...
Click to collapse
It's not broken. The vendor error message is because it was recently updated to work better with Project treble, which uses a hidden partition for the vendor. You can simply ignore the error and it will work fine. Or if you flash a treble ROM, the error will then go away.
I just got the phone. Format it in recovery.
Flash latest blu spark twrp (v.8.73).
Flash the Oos ob06.
Reboot to system. Set the phone, instal apps from Play.
Reboot to Fastboot.
Reflash recovery.
Reboot to recovery.
Flash Magisk 15.3. Reboot to system. OK.
Updated Magisk with Magisk.
Hi, Can anyone help me. in my oneplus 5T after installing new rom it is working smooth but i can't upgrade to new updates. in recovery mode the files seems to be decrypted and cant find any folders where i copied the updation . instead new files are found and can't access and find any of the folders of my own. this happened after i input the security lock. i wiped the entire data and installed new roms still it seems so. somebody please help me to find a solution for this
Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
mmedei9 said:
Has anyone managed to root their device by patching their boot image and not installing a custom recovery (TWRP)?
I am referring to the method described on the Magisk website:
https://topjohnwu.github.io/Magisk/install.html#boot-image-patching
Click to expand...
Click to collapse
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
polfrank said:
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery
mmedei9 said:
Do you suspect that the reason rooting via patching boot doesn't work is the encryption then? I'd be willing to disable encryption to obtain root with stock recovery
Click to expand...
Click to collapse
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?
polfrank said:
Not exactly. I suspect that it is the reason for bootloop when trying to install Magisk on the Chinese device. Because Magisk does not work on the Chinese device, even if you flash and close avb2.0, you get bootloop.
In global device + global rom, you can disable avb2.0 through TWRP after flashing Magisk, and then reboot normally to get a perfectly rooted phone while keeping encryption.
But if you flash the rooted boot.img through fastboot, how are you going to close avb2.0?
Click to expand...
Click to collapse
Of the handful of tutorials on the forums, which would you recommend for flashing TWRP and rooting the device?
Would it require me flashing the global rom in the place of my global (EEA) rom?
polfrank said:
I think this would work with the xiaomi.eu rom. And I say it because when I install Magisk through TWRP, it works without the need to close AVB2.0 etc etc. Just install Magisk, reboot and you're good to go.
You need TWRP in order to flash the Xiaomi.eu rom though. Except if you flash all the partitions of the rom one by one through fastboot. And then flash the rooted boot.img.
Side note: I have not managed to root ANY rom (Chinese/global) on the Chinese device while keeping encryption. It always leads to bootloop, except if you disable forceencrypt, which of course leads to loss of encryption.
Click to expand...
Click to collapse
Attention because there will be no more updates for the redmi note 8 pro concerning the rom xiaomi.eu! (announcement on their site ...)
I flashed patched boot image without disabling avb and now I'm stuck in bootloop.
Is it necessary to disable avb before flashing patched image through fastboot?
Hi everyone.
I had a issue and i really want help
I had unlock the OEM,and after installing the twrp and format data (to remove the forced encrypt), i had flash the Disable_Dm-Verity_ForceEncrypt zip file.
Okay, after that i have restarted the device and configure as my away to use, after that, booted on recovery again and flashed the magisk.
But i wanna encrypt my device, and when i go to configs->security and encrypt area, says that my device its not encrypted. Okay, i followed the steps and when i gonna try to encrypt the device, the process start and... some seconds after, the phone just restart and nothing has done.
The onlys changes that i have made on system is: root and flashed a splash.img(without that stupid warning of unlocked bootloader)
I really want to encrypt my device, so, if i get stolen, the thief wont get my user data.
Can anyone help me?
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Thanks sir, i will try!
marstonpear said:
Flash the stock rom and and don't flash the encryption disabler next time. You don't need to install TWRP to flash Magisk either, you can just boot it and then flash Magisk. Also you don't even need TWRP, you can just follow the guide in the forum to install Magisk by booting the magisk patched boot.img for your version of the stock ROM and then install Magisk manually via Magisk Manager.
TL;DR : Flash stock ROM and do the same things except flashing dm-verity-disabler, you don't need that for Magisk or TWRP.
Click to expand...
Click to collapse
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
mrkeitsuke said:
Sir, i really need twrp now, its there any way i can enable encrypt after rooting the device? (to sure that, if gets stolen, the data need to be wipped out or the password must be given on twrp)
Same issue, i tried to encrypt on security menu,reboot and nothing was done.
@edit
Better, without TWRP, i can flash other zips via magisk/stock recovery?
Click to expand...
Click to collapse
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
marstonpear said:
I'm not sure what you're trying to do here, do you want to have TWRP + stock encryption?
If so you can just boot TWRP and flash the TWRP installer package (.zip) inside TWRP to do that. And you don't need to change anything, currently I have TWRP installed and encryption enabled on my Stock ROM.
But if you're trying to get TWRP's own encryption, sadly that doesn't work.
You can also use TWRP without flashing/installing it, just go to the directory TWRP is stored in, open a command line, connect your phone and boot it with this command :
Code:
fastboot boot twrp.img
then flash whatever you'd like.
DO NOT lock your bootloader after you flash something on TWRP, this will most probably brick the device.
Click to expand...
Click to collapse
I want to stick with the stock rom rooted, with the twrp installed and the user data encrypted
So i can flash things through TWRP even i have encrypt enabled?
@edit
dont worry about bootloader, i will keep unlocked
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
a1291762 said:
It's perfectly fine to have TWRP and/or Magisk and encryption using stock ROM.
Flash stock ROM (erase user data)
Install TWRP
install Magisk
Don't flash the encryption Disabler. As its name implies, it disables the automatic encryption of the userdata partition.
Click to expand...
Click to collapse
:highfive: i had done this and... i think its working!!! :crying::crying::crying:
(crying for emotion, almost thirty factory resets to get an good result :crying::crying::crying
Anyway, if anything bad occurs, i will update here, thanks a1291762 and marstonpear
I Have difficulties rooting my Z1 compact (amami).
My goal is to have stock rom, rooted with Magisk.
Steps I took:
1. Unlocked the bootloader (manufacturer way)
2. Flashed latest stock rom
3. Booted, installed Magisk manager, downloaded magisk.zip and enabled USB debugging
4. Flashed TWRP through ADB
5. Booted into TWRP, tried to install the zip, I get an error “unsupported image format”
6. If I reboot after faliure, I can’t get into stock rom anymore (just black backlit screen), so I have to reflash stock rom again.
I have tried different versions of TWRP, Magisk, and tried rezipping magisk.zip.
Any help is greatly appreciated.
Same issue here. Will let you know how I solve it.
Edit: My solution, might not be 100% what you were after, but this is good for me:
Reflash stock rom 236 LP with EMMA
Flash kernel v18.1 from here https://forum.xda-developers.com/so...rnel-advanced-14-5-0-242-kernel-v1-0-t3096060 (fastboot flash boot boot.img)
Enter rom and adb reboot recovery (power + voldown didn't work)
Flash Supersu zip
Flash debloater zip from here https://forum.xda-developers.com/cr...p-debloat-lp-690-correct-functioning-t3076161
This nets me a debloated stock 5.1.1 install with root and busybox, all I need. I could never get fastboot flash recovery to boot any rom after flashing from recovery, so after a lot of struggle I'm happy this way.
If Magisk is a must, I would try the method described here https://forum.xda-developers.com/so...m-unrooted-t3682932/post76105039#post76105039