Hi, there
My device is A50(SM-A505F), Region: Vietnam
I was received an update in March, so I want to root my device with Magisk. I have file AP( downloaded in Samfirm), I patched AP in Magisk and then flashed it into Odin but that was blocked although I wipe date/factory reset, OEM unlocked. So why my device was blocked?
I need an support from developers' s Magisk
wikiuse said:
Hi, there
My device is A50(SM-A505F), Region: Vietnam
I was received an update in March, so I want to root my device with Magisk. I have file AP( downloaded in Samfirm), I patched AP in Magisk and then flashed it into Odin but that was blocked although I wipe date/factory reset, OEM unlocked. So why my device was blocked?
I need an support from developers' s Magisk
Click to expand...
Click to collapse
Problem is not magisk but samsung.
Apart from unlocking bootloader check in download mode. If you have KG ( and/or RMM ) state being prenormal you won't be able to install magisk.
spawnlives said:
Problem is not magisk but samsung.
Apart from unlocking bootloader check in download mode. If you have KG ( and/or RMM ) state being prenormal you won't be able to install magisk.
Click to expand...
Click to collapse
Can you speak in more detail? I am not understand
wikiuse said:
Can you speak in more detail? I am not understand
Click to expand...
Click to collapse
Can you post or copy your download ( Odin ) mode screen.
spawnlives said:
Can you post or copy your download ( Odin ) mode screen.
Click to expand...
Click to collapse
My device was rooted by Magisk, but it auto random reboot
I need a file to fix it!
Related
Hi all guys Thanks for having help on this forum.
In short, my problem is.
I wanted to do the usual root procedures with on board Android 8.0 latest firmware no brand update, then put supersu on sd card go to download mode, odin, twrp flash, wipe total, flash twrp supersu and reboot.
After starting everything in place but as soon as I restarted, a red text appeared, from there it is no longer in recovery nor on the system I can only go to download mode but I have tried everything not flasha nothing is blocked by rmm state of samsung.
Ok after explaining the problem what can I do? Do you have a solution?
P.Š. I asked around and they told me that it takes the samsung box I have to pass by force there?
Dantes991 said:
Hi all guys Thanks for having help on this forum.
In short, my problem is.
I wanted to do the usual root procedures with on board Android 8.0 latest firmware no brand update, then put supersu on sd card go to download mode, odin, twrp flash, wipe total, flash twrp supersu and reboot.
After starting everything in place but as soon as I restarted, a red text appeared, from there it is no longer in recovery nor on the system I can only go to download mode but I have tried everything not flasha nothing is blocked by rmm state of samsung.
Ok after explaining the problem what can I do? Do you have a solution?
P.Š. I asked around and they told me that it takes the samsung box I have to pass by force there?
Click to expand...
Click to collapse
You should have deleted "security log agent" in system/app before rebooting.
stonedpsycho said:
You should have deleted "security log agent" in system/app before rebooting.
Click to expand...
Click to collapse
Yes i detected log security agent
Dantes991 said:
Yes i detected log security agent
Click to expand...
Click to collapse
Once I deleted that it has been fine for me. The post below may help you though.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
stonedpsycho said:
Once I deleted that it has been fine for me. The post below may help you though.
https://forum.xda-developers.com/showpost.php?p=75360965&postcount=22
Click to expand...
Click to collapse
but I can not flash the twrp
Dantes991 said:
but I can not flash the twrp
Click to expand...
Click to collapse
I think you need to flash the stock rom with Odin and basically start again.
You could just flash the dev-base rom which is basically just the stock rom but with all the above disabled already.
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
neoquor said:
I own the Japanese version of Note9 SM-N960D (SC-01L) SM-N960J (SCV40).
Currently using 9.0 pie.
I want to get the route, but when I wipe with TWRP, I fall into the boot loop.:crying:
Even if you install Magisk and RMM-State_Bypass, it will not start.
I also installed no-verity-opt-encrypt-6.1.zip or no-verity-opt-encrypt-6.0.zip.
Does anyone know how to get root of this Note9 terminal and start it?
Click to expand...
Click to collapse
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
bober10113 said:
you might need to flash a custom kernel( or at least a patched one after data format. or it will just bootloop)
also please read dr ketans guide in the general discussion section and use method 1.
Click to expand...
Click to collapse
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
neoquor said:
Thank you for your reply.
Which kernel should be rewritten?
Which discussion page is [dr ketans guide in the use method 1]?
I would be happy if you could tell me.
Click to expand...
Click to collapse
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
bober10113 said:
https://forum.xda-developers.com/galaxy-note-9/how-to/root-note-9-n960f-fd-experimental-t3832143/
Click to expand...
Click to collapse
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
neoquor said:
Thank you for teaching me.
However, TWRP freezes during installation of "N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip" and cannot be installed.
what should I do?
Click to expand...
Click to collapse
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
bober10113 said:
what do you mean? have you tried to flash again? also do you choose magisk option and kernel option during setup?
Click to expand...
Click to collapse
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
neoquor said:
I tried the following:
1. Burn carrier genuine ROM with Odin
2. Launch download mode again and write [TWRP_3.2.3-0_N9600_beta3.tar.md5] with Odin
3.TWRP immediately after Method 2
4.Wipe → FORMAT DATA → yes with TWRP
5.Reboot to recovery mode and mount system etc.
6.Install → microSD card menu → “N960F_DS_N_PIE_Root_for_OEM_issue_devices_V5.zip” → Install
Freeze the installation screen.
The terminal I am using is snapdragon.
Click to expand...
Click to collapse
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
bober10113 said:
oh snapdragon really? that's why. i thought the japanese model was Exynos. very sorry for that mistake.
then please go to:
https://forum.xda-developers.com/showpost.php?p=77721998&postcount=2
there is guidance in that post towards the end regarding twrp and root.
also i think if you flash twrp, boot to twrp, flash decryption fix then format, reboot back to twrp and then flash latest patched kernel:
https://mega.nz/#F!XlkXxYZK!-KlTcLtsQ14eQBTa-AUNhA!T4lmyYJC
(taken from mentalmuso's thread i linked)
to flash .img choose install image button in twrp then select kernel.img then select destination partition:
boot
Click to expand...
Click to collapse
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
i really dont know. im on exynos device. people with n9600 will have to help you as i have no experience with snapdragon.
sorry
neoquor said:
Thank you for your kindness! Made progress. But there is a new problem.
After installing the WETA kernel, TWRP and Magisk were able to boot in a retained state.
However, there is a problem, and after restarting, a green screen of security error is displayed and it cannot be started.
Next, after installing the kernel, I installed no-verity-opt-encrypt-6.1.zip and Magisk.
While holding TWRP and Magisk, I was able to start and restart without any problems.
However, if NFC cannot be used and PIN code lock is applied, the lock cannot be released at all even if the correct PIN code is entered.
Please give me advice.
Click to expand...
Click to collapse
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob! Just like @neoquor, I am using a Snapdragon Note 9 (SCV40/SM-N960J) from the carrier au. I was able to successfully boot with the firmware of another Japanese carrier variant SM-N960D/SC-01L (carrier DoCoMo) and @klabit87 's N9600 klabit kernel.
Following the Magisk installation instructions from @topjohnwu 's GitHub, my installation was a bit windy (trial-and-error), but I (1) launched Odin and flashed my Magisk-patched SC-01L AP binary along with BL, CP, and CSC; and (2) after falling into the bootloop, I flashed klabit's official N9600 TWRP build, and (3) flashed klabit's N9600 kernel.
After that, success--finally! Dekita!
bober10113 said:
try:
https://forum.xda-developers.com/ga...velopment/kernel-n9600-klabit-kernel-t3992637
use just the kernel
Click to expand...
Click to collapse
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
neoquor said:
Thanks, Bob!
With this, Snapdragon Note 9 (SCV40 / SM-N960J) did not reach the boot loop and succeeded in rooting!
However, when I start it, "It's a non-genuine kernel" is displayed and I can't start some apps I want to use.
What should i do?
Click to expand...
Click to collapse
Dear NeoQuor, did you find any solution ?
I have the same problem I I flashed patched magisk with boot.img file it is flashed 100% but I'm not able to boot to android. it keeps restarting on the boot loop.
I just found one source this guy he is able to root SCV40
https://support.halabtech.com/index.php?a=downloads&b=folder&id=77034
i look forward to a solution for my phone to be rooted.
regards,
Sher
I also have SCV40, and the only reason I need to root my SCV40 because I need to edit and rewrite ro.confiq.tima=1 to 0 so that I'll be able to use S-Health, but in the end I can't root my SCV40, It is impossible, but I did rooting my friend's Note9 and it work well. I guess there's still no one can root SCV40 Until today.
Hello, is it possible to unlock bootloader and root with magisk Galaxy A71 Dual Sim?
Yes
Sloobot said:
Yes
Click to expand...
Click to collapse
Can you tell me how?
Unlock the bootloader in the developer options after that download your phones firmware install magisk manager on your phone and patch the AP file after that flash it using odin and that should do the trick!
Sloobot said:
Unlock the bootloader in the developer options after that download your phones firmware install magisk manager on your phone and patch the AP file after that flash it using odin and that should do the trick!
Click to expand...
Click to collapse
Don't you need to unlock the bootloader in download mode? And I need to download the firmware that my phone have?
XterYT said:
Don't you need to unlock the bootloader in download mode?
Click to expand...
Click to collapse
First you need to turn off oem and after that you do that and yes you need the phones firmware samfw.com
I bought a second phone Sam Galaxy s10 SM-G973F Exynos with display dead(Can be seen but green).
Iam doing inner os things with scrcpy
What things have i done till now??
I downloaded firmware from Frija.
I unlocked bootloader
I patched AP file with magisk app and ramdisk says no
I Used BL,CP and Home CSC with magisk pached image as AP with Odin
I got a bootloop
I flashed back to stock by reflashing with AP file without patching.
But the previous baseband version of stock binary 9(G973FXXUEHVB9) changed to G***********VC6.
Should I download VB9 for to work???
My wrong.
Hello Léon FH, these version VB9 me I have the version there G973FXXUFHVE1 - XEF (France) Android 12 S (May 2, 2022)
You have successfully transferred with ADB the AP magisk_patched mobile via pc.
meric57 said:
Hello Léon FH, these version VB9 me I have the version there G973FXXUFHVE1 - XEF (France) Android 12 S (May 2, 2022)
You have successfully transferred with ADB the AP magisk_patched mobile via pc.
Click to expand...
Click to collapse
I said, When I transfer Magisk_patched image, It bootloops.
After clearing dalvik, wiping, Iam ablw to get to it.
I flashed magisk.zip too(Which is useless in device with no ramdisk)
But still, no root in magisk manager.
Iam not able to root with magisk patched image.....
I patched magisk.zip also
No hope
Leon FH said:
Iam not able to root with magisk patched image.....
I patched magisk.zip also
No hope
Click to expand...
Click to collapse
You can install CSC instead CSC HOME. You will lose everything you installed.
If you install HOME CSC try this: #2,668
Look here https://forum.xda-developers.com/t/magisk-root-for-the-galaxy-s10-series.3918699/
I think you misunderstood redone all from A to Z take the official firmware S10 SM-G973F exynos android 12 UI 4.1 look at the one I have in my signature.
You backup your data with smart switch then you flash the official Android 12 XEF firmware. G973FXXUEHVC6 install magisk 25.1 the firmware AP r transfer to the S 10 and modify it with magisk once done you will have a file in internal memory magisk_patched xxx.tar you transfer it either directly to the pc or as john Wu says with adb for no lose bytes of the file it must 6.02 GB.
Then you open odin you put 4 files there BL-AP patched- BL HOME CSC you flash at startup install magisk and you activate zygisk in parameter once which is rooted you turn off and you start in download mode are you flash up_param.tar with odin take the one at https://forum.xda-developers.com/attachments/up_param-tar.5645391/ for rooted device
I hope you will understand complicated to explain
meric57 said:
Look here https://forum.xda-developers.com/t/magisk-root-for-the-galaxy-s10-series.3918699/
I think you misunderstood redone all from A to Z take the official firmware S10 SM-G973F exynos android 12 UI 4.1 look at the one I have in my signature.
You backup your data with smart switch then you flash the official Android 12 XEF firmware. G973FXXUEHVC6 install magisk 25.1 the firmware AP r transfer to the S 10 and modify it with magisk once done you will have a file in internal memory magisk_patched xxx.tar you transfer it either directly to the pc or as john Wu says with adb for no lose bytes of the file it must 6.02 GB.
Then you open odin you put 4 files there BL-AP patched- BL HOME CSC you flash at startup install magisk and you activate zygisk in parameter once which is rooted you turn off and you start in download mode are you flash up_param.tar with odin take the one at https://forum.xda-developers.com/attachments/up_param-tar.5645391/ for rooted device
I hope you will understand complicated to explain
Click to expand...
Click to collapse
Just like you said. I patched the rom. put it into odin. flashed it. Installed magisk 25.1 apk . No sign of root.
Leon FH said:
Just like you said. I patched the rom. put it into odin. flashed it. Installed magisk 25.1 apk . No sign of root.
Click to expand...
Click to collapse
You need patch onley AP. Copy AP on PC with ADB.
Try connect phone with PC with USB vcable. Open ADB and in ADB type 'adb reboot recovery' and Enter. After restart phone you you should have rooted phone.
ZmisiS said:
You need patch onley AP. Copy AP on PC with ADB.
Try connect phone with PC with USB vcable. Open ADB and in ADB type 'adb reboot recovery' and Enter. After restart phone you you should have rooted phone.
Click to expand...
Click to collapse
Thanks man. It worked!!✌
Leon FH said:
Thanks man. It worked!!✌
Click to expand...
Click to collapse
I should go adb reboot recovery to see root always??
Leon FH said:
I should go adb reboot recovery to see root always??
Click to expand...
Click to collapse
No. Install Root Essentials. For restart phone, open Root Essentials select Rebooter, click on Reboot Recovery and it is it. If you accidentally lose root, just repeat the type 'adb reboot recovery' and Enter.
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
22350 said:
Haven't been on android in a while.
Picked up a galaxy tab a for free.
Tried to load unlock bootloader / install driver / install odin and twrp
now the unit only boots into odin download or samsung download
got patched odin and tried to install the firmware from sam site. Fails every time. Computer sees the device.
Any tips?
Click to expand...
Click to collapse
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
lewmur said:
Not nearly enough info. What steps did you take? Did you succeed in unlocking the bootloader? Did the tablet reboot after that? Did in factory reset? Did you re-enable Dev mode and OEM? What version of Odin? What version of stock ROM do you have? Did you flash VBmeta Disabler?
Click to expand...
Click to collapse
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
this is what the screen says when i try to flash
no content in your post
22350 said:
I was not able to get supersu into the root folder, but I understood that if you turn on developer mode and OEM unlock, you had unlock. I have not been able to figure out how to get supersu into the root folder.
It did boot after that.
I am using odin 3.14.1_3b patched
using the usa rom from samobile T380DXU3CSL2_T380XAR3CSJ1_XAR
don't know what version of stock rom, but it updated right before I did any of this.
Did not know about VBmeta Disabler.
Click to expand...
Click to collapse
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
lewmur said:
You need to do a lot more reading. Forget everything you know about rooting because it won't help with this tablet. There is a link in the first post in this tread about how to unlock the bootloader and enabling Dev mode and OEM is only the very first step. You can't do anything else until that is complete and each step is important. Also in the first post is the stock version you'll need to flash before flashing VBmeta and TWRP.
Click to expand...
Click to collapse
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
22350 said:
Ok I will do that, but since I am stuck in odin download will I be able to get supersu installed anymore?
I installed twrp with Odin, but that’s when everything went sideways
Click to expand...
Click to collapse
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
lewmur said:
Actually the thread you need to read is here. That has the link to instructions for unlocking the bootloader. Your next step will be to use Sammobile to download the stock version shown in that thread and flash it with Odin. That should get you back to a bootable ROM. Also, forget about supersu. Magisk is used to root these tablets.
edit: MY BIG MISTAKE. I thought you had a T500 tablet but looking closer to your post, you must have a T380 and the thread I linked won't work for a T380. You'll have to search for a thread for rooting your tablet. Sorry about that. I don't even know if the T380 has a locked bootloader. But your next step will be to flash the stock ROM you downloaded to get back to a bootable ROM.
Click to expand...
Click to collapse
Yea, well that's the issue. i am in odin downloading, with the correct rom from samobile, but the flash fails each time
i ended up using these two
Stock ROM for the SM-T380 Android 9, Bloatware free TWRP backup
Since there aren't any Custom ROM for the SM-T380 I made this TWRP back from my tablet, running on stock Pie I took all the bloatware, Knox out to add some root mods, and latest updates with Magisk root with Safetynet Passing. No other personal...
forum.xda-developers.com
[TWRP 3.2.1-1] [ROOT] Tab A SM-T380/T385 - 10/02/2018
Unofficial release -TWRP recovery for the Galaxy Tab A - T380/T385, Qualcomm MSM8917 TWRP 3.2.1-0 Released Dec 9, 2017 TWRP 3.2.1-0 is out now for most currently supported devices. What's new in 3.2.1-0: * minui fixes (cryptomilk) *...
forum.xda-developers.com