hello guys just got Android 11 update and I'd like to know how to root, I've never rooted this device defore so i need a full tutorial thanks in advance
Install magisk manager get your phones firmware from samfw or any other site transfer the AP file to your phone open magisk manager click install , patch a file and select the ap file after its patched get the file using adb "adb pull" and then flash it with magisk including bl csc and the rest. Like this response if it helped you
Sloobot said:
Install magisk manager get your phones firmware from samfw or any other site transfer the AP file to your phone open magisk manager click install , patch a file and select the ap file after its patched get the file using adb "adb pull" and then flash it with magisk including bl csc and the rest. Like this response if it helped you
Click to expand...
Click to collapse
worked for me. thank you so much
from samsung galaxy A71 Android 11
AsifMohiuddin said:
worked for me. thank you so much
from samsung galaxy A71 Android 11
Click to expand...
Click to collapse
Im glad to hear that
Do you mean flash it with Odin? I don't see how I can flash the tar with Magisk.
Sloobot said:
Install magisk manager get your phones firmware from samfw or any other site transfer the AP file to your phone open magisk manager click install , patch a file and select the ap file after its patched get the file using adb "adb pull" and then flash it with magisk including bl csc and the rest. Like this response if it helped you
Click to expand...
Click to collapse
Do you mean flash it with Odin? I don't see how I can flash the tar with Magisk. Sorry for the double post. I don't know how I can delete the other message.
Codename_Falcon said:
Do you mean flash it with Odin? I don't see how I can flash the tar with Magisk. Sorry for the double post. I don't know how I can delete the other message.
Click to expand...
Click to collapse
Yes im talking about odin but now there is another method
So what about the Samsung Pass status? R11 ?? A715F/DS
Related
To those wo have trouble to root their phones!
Try to use a command line lz4 tool, to extract the boot.img from boot.img.lz4. I tried before with 7Zip and it didn't worked. After I tried a command line tool, even the sizes of the boot images were different. This did the trick for me
best regards
nebkas
nebkas said:
To those wo have trouble to root their phones!
Try to use a command line lz4 tool, to extract the boot.img from boot.img.lz4. I tried before with 7Zip and it didn't worked. After I tried a command line tool, even the sizes of the boot images were different. This did the trick for me
best regards
nebkas
Click to expand...
Click to collapse
which one? could u please link to that tool or share here your using?
an-_-dro said:
which one? could u please link to that tool or share here your using?
Click to expand...
Click to collapse
I used that one. Just drop off the boot.img.lz4 on the .exe file.
nebkas said:
I used that one. Just drop off the boot.img.lz4 on the .exe file.
Click to expand...
Click to collapse
i also used that but still not successful >_<
i thought different tool, but anyway thanks.
an-_-dro said:
i also used that but still not successful >_<
i thought different tool, but anyway thanks.
Click to expand...
Click to collapse
I'm sorry. I also flashed the complete downloaded firmware(all files) before I extracted the boot.img.lz4 from it. maybe thats why it worked?
nebkas said:
I'm sorry. I also flashed the complete downloaded firmware(all files) before I extracted the boot.img.lz4 from it. maybe thats why it worked?
Click to expand...
Click to collapse
maybe 4 or 5 attempts with different patched img but i never make it hahaha of course i also flashed complete downloaded firmware after and wait 7 days between each attempt.
I struggled a lot too yesterday(got my device yesterday ). I used also this one to repack the .img and flashed it with the odin version in the bin directory.
7zip is enough to wrap img file to tar
an-_-dro said:
7zip is enough to wrap img file to tar
Click to expand...
Click to collapse
yes, maybe. But who knows what all the apps are doing. that file makes it to a tar.md5.
Thanks OP... it worked on my A605FN.
I was unable to patch the boot image in Magisk Manager as it returned error.
I tried your tool and it patched.
Wouldn't it be simpler to just flash the last Asphyx twrp build, and then flash magisk from twrp?
Sent from my SM-A605FN using Tapatalk
pr1jker said:
Wouldn't it be simpler to just flash the last Asphyx twrp build, and then flash magisk from twrp?
Sent from my SM-A605FN using Tapatalk
Click to expand...
Click to collapse
Sure, but there wasn't any twrp working when I started the Thread
Hello. I am having an issue getting my oem unlock option back. I have followed every tutorial that I could find trying to get rmm back to normal status and have had my a600t1 on for 39 days nonstop. If anyone could give advice or just point me in the right direction I would greatly appreciate it. I'm at a loss. Thanks in advance for any help
guess maybe nobody can help with my issue. i dont know about you all but its polite to answer even if the answer is no.
Just share I have rooted my Samsung Galaxy A6 2018 SM-A600G Android 9 Pie with Magiskm you can watch this video https://youtu.be/1y1p7-Hzm_o
for rooting it, I have to install Magisk twice, one for prevent boot loop after install TWRP and second for rooting after install MagiskManager.
I have a problem with root. I can't set fingerprint because the System crash. After crash i have to install over again. I have notice that twrp recovery have an error when i go in internal storage It have 0mb and i must format
SubGenius said:
Thanks OP... it worked on my A605FN.
I was unable to patch the boot image in Magisk Manager as it returned error.
I tried your tool and it patched.
Click to expand...
Click to collapse
did you have boot.img for this devise but for 9.0 thx
Hey guys,
currently my S10+ is on Android 9, rooted and with TWRP:
Do you guys have any idea how I can update to the final Android 10 firmware without losing all my data, root and TWRP? (My CSC is DBT anyway btw)
Regards!
Download the newest firmware. Extract the firmware. Copy ap file to your download folder in the phone .Magisk patched the ap file. Now copy the magisk patched tar file back your pc. Open odin load BL, magisk patched ap, cp and home csc (retains all your data). Now flash it. Remember to hold power, bixby and volume up aka combo keys
Will it work? I think no
Player04 said:
Download the newest firmware. Extract the firmware. Copy ap file to your download folder in the phone .Magisk patched the ap file. Now copy the magisk patched tar file back your pc. Open odin load BL, magisk patched ap, cp and home csc (retains all your data). Now flash it. Remember to hold power, bixby and volume up aka combo keys
Click to expand...
Click to collapse
Thanks for the reply. I'll try it out!
henio1195 said:
Will it work? I think no
Click to expand...
Click to collapse
I'll try it out and report back. Why do you think it won't work?
Hmm I think that would so easy. Geiti created new root(magisk) for beta android 10 and for official 10 doesn't work.
I tried yesterday install android 10 for my S10 (SM-G973F, only magisk) but installation stopped on recovery. I had to stop the installation. Fortunately, the system still works.
I am rooted on my s10+, android 10.
Pls tell US what you did
Player04 said:
Download the newest firmware. Extract the firmware. Copy ap file to your download folder in the phone .Magisk patched the ap file. Now copy the magisk patched tar file back your pc. Open odin load BL, magisk patched ap, cp and home csc (retains all your data). Now flash it. Remember to hold power, bixby and volume up aka combo keys
Click to expand...
Click to collapse
Mine is Note 10+ (N976B) somehow its imei is pre-patched when i purchased, now it needs chimera everytime i do update(because it removes the network & imei info from the device).. what if i try your method will it wipe those certificates (which are patched by chimera) ? Please reply . Thanks
Hello, i just installed Magisk 24.1 successfully on my new Galaxy A52s 5G, but somehow since then the camera also does not work anymore. Every time i open the systems camera app (or any other app that uses the camera) a popup says "Warning. Camera failed.". I do not know where this comes from or how to fix it. Rebooting a few times, clearing cache, correcting the permissions of builds.prop and the safe mode did not solve the problem.
Any help would be appreciated, thanks
What exactly did u do? U didn't give any details!!
Ayan Chakraborty said:
What exactly did u do? U didn't give any details!!
Click to expand...
Click to collapse
Because there is not much more i could tell you. I rooted the phone by patching the AP of the firmware and then flashing it. After that, the camera did not work anymore. But it seems like as if other people had the same problem, which is probably due to samsung now apparently killing the camera when it detects root. **** samsung for that.
Extract the boot.img from AP.tar
Patch the boot.img using magisk app.
Pack the modified boot.img into a .tar file
Flash all stock files using Odin. Reboot to download mode and flash modified boot.tar
See how it goes. Full AP should not be patched ideally.
Ayan Chakraborty said:
Extract the boot.img from AP.tar
Patch the boot.img using magisk app.
Pack the modified boot.img into a .tar file
Flash all stock files using Odin. Reboot to download mode and flash modified boot.tar
See how it goes. Full AP should not be patched ideally.
Click to expand...
Click to collapse
Nevermind, i just installed Universal SafetyNet Fix and the cameras suddenly work again. Seems like that was it.
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.
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
jcunwired said:
It's been years since I've rooted an Android device so I gotta say it's been fun getting back to it, if a little bit frustrating. This is the first Samsung device I've owned and I can't wait to get another ROM. Here's what I've done, many times, without success.
1. unlock bootloader
2. download Samfw.com_SM-X200_XAR_X200XXU2CWC1_fac (went from Android 11 to 13)
3. flashed above firmware with Odin3 v3.14.1
4. setup device (basic - bypassed Google login, Samsung installs and options)
5. installed Magisk-v26.1 on tablet
5. Extracted boot.img from AP_.tar, copied to tablet, patched with magisk, back to PC, created boot.tar from magisk patch
6. Odin flash again, added BL from firmware, AP was patched boot.tar from magisk, CSC from firmware.
I've read to flash only the patched boot image (.tar), to patch the full AP package, to flash boot image and add back to AP file, and I've tried all three without success.
My first attempt was with X200XXU1AVC1, with the same result, so I flashed the Android 13 for all subsequent steps.
I feel like I've done everything correctly and could use some guidance in resolving why I can't achieve root.
EDIT: resolved, i didn't know about sideloading magisk!
Click to expand...
Click to collapse
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
lewmur said:
I don't understand what you mean by "sideloading magisk". Did you read my post #84? That work with the previous version of Android 13, CWA3. I just copied Magisk apk to the SD card and installed it from there.
Click to expand...
Click to collapse
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
jcunwired said:
Select update from adb in recovery, then:
adb devices
adb sideload Magisk-v26.1.zip
Click to expand...
Click to collapse
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
lewmur said:
I know how to do it. I just don't understand what difference it makes. Why not just copy it to the tablet and install it?
Click to expand...
Click to collapse
Because I was in ADB and like you said, what difference does it make?
jcunwired said:
Because I was in ADB and like you said, what difference does it make?
Click to expand...
Click to collapse
The difference is that your post said you installed Magisk and used it to patch the boot.img and it didn't work. Then the edit said you solved it by using adb to sideload magisk and that solved the problem. I'm still trying to understand how it did.