Related
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
Code:
- Device platform: arm64-v8a
- Existing zip found
- Copying image to cache
- Unpacking boot image
! Unsupported/Unknown image format
! Installation failed
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
maretodoric said:
Hello everyone,
So this is the first time i had issue with magisk after the update.
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager then installing that zip - also from Magisk Manager, but it would say this:
So now i don't know what do to.
I did notice however, that after the Magisk update, it seem to have installed newest OTA update (with security patches from May), which usually it fails to install, i guess due to unlocked bootloader.
Any help would be greatly appreciated!
EDIT:
Managed to figure it out, it's been a long time since I've done this so i forgot that method I've tried is used to patch boot image, not to install zip file, my bad.
I booted into TWRP and extracted my current boot.img.
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Booted back into the system and *BAM*, got my root back!
Magisk is still the best! Thank you!
Click to expand...
Click to collapse
I'm also getting same error how did you managed to find the solution...
maretodoric said:
Magisk Manager proposed for me to install new version of Magisk, so i did, after installation finished, it advised to reboot, so i did
After reboot, phone came back up just fine but Magisk was not installed. I tried to download zip 19.2 (19200) from Magisk Manager.
[...]
Booted back into the system and using Magisk Manager, I've patched the boot.img
Downloaded the magisk_patched.img to PC and from fastboot, flashed the patched boot.img.
Click to expand...
Click to collapse
Similar problem here, but with Magisk 19.3.
Could you pass a link to patched boot image,you used? Can´t find it...
Thanks
I didn't download boot.img, it's best that you extract it yourself by using ADB.
Download adb software, there should be some tutorial here on forums how to find and get it (possibly https://forum.xda-developers.com/mi-a1/how-to/computer-setup-rooting-gcam-setup-t3731526) , but Windows 10 SHOULD natively have it (at least i did, i didn't have to install anything, already had ADB).
Now here comes the tricky part. I didn't remember this and i didn't write it down. When this happens again to me, i will be in huge .......
I'm sorry i can't help you, but try to google for info on how to extract boot.img from current installation using fastboot or adb.. not sure which, possibly fastboot.
Then you will have clean untouched boot.img from official repo. No need to wait for it to appear on xiaomi site.
If i find a tutorial, i will post it here. Please do the same if you find it before me.
GOT IT!!!
- Follow the previous tutorial if you do not have adb and fastboot, so you can install them. There should be plenty of tutorials how to install both of them
- After you installed it, download this version of TWRP https://dl.twrp.me/tissot/twrp-3.3.0-2-tissot.img.html to your desktop
- Connect your phone to your PC via USB cable
- Open command prompt (in Windows, hit CTRL+R then type in cmd)
- Change directory to desktop, for example type cd C:\Users\<username>\Desktop - replace "<username>" with your username ofcourse.
- Type adb reboot bootloader - it will boot to fastboot mode
- Once the phone is in fastboot mode, type fastboot boot twrp-3.3.0-2-tissot.img (keep cmd prompt open)
- It will boot into recovery, click on "Backup"
- Select "Boot"
- Click on Select Storage and there choose Internal Storage, click on OK
- Then on the bottom part of the screen, just swipe to right to extract boot.img (It should literally say "Swipe to Backup"). Pay attention to messages, it will display the directory where it will place the boot.img, but it will not be strictly named boot.img
- In my case, it's in Internal Storage/TWRP/BACKUPS/00bf23cc0904/2019-06-20-14-25-3_PKQ1/boot.emmc.win
You can either rename it to boot.img or just leave that name. But either way, open new magisk manager, select "Install" next to Magisk (not magisk manager), click on "Select and Patch a file", point to your new boot.img or boot.emmc.win.
Magisk will patch that image and show you the new location. Just download that file to your PC, on desktop, cmd again "adb reboot bootloader", and when it gets to fastboot mode, type "fastboot flash boot magisk_patched.img".
You should be good to go!
Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
https://www.youtube.com/watch?v=NSs08O6uGVI&t=324s
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!
Thank's it's work fine on custom gsi too, i just flash patch boot, vbmeta, finally install magisk success
I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.
Can I just do this on MIUI 11.0.5 Global?
Omborkar said:
Can I just do this on MIUI 11.0.5 Global?
Click to expand...
Click to collapse
Download patched boot.img for ur rom instead of 11.0.7 boot.img I uploaded. Or patch it yourself.
I have a problem. Everytime I do the wipe it says only: "Failed to mount "vendor"(invalid argument)"
What to do?
Google play not certified... after flashing and installed magisk... Got solution??? Thanks
I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.
vincecabalan said:
I've rooted my MoKee OS Android 10 rom. Can somebody help me change the system font? The font changer module in Magisk is not appearing in the search bar.
Click to expand...
Click to collapse
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee
Hello, what files do I need to rename to boot.img and recovery.img? I'm lost
3. Rename the patched boot file to boot.img
4. Rename the custom recovery to recovery.img
RsAbubokor4 said:
I Tried To Root Mokee But Failed. Can You Please Tell Me How You Root Mokee
Click to expand...
Click to collapse
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper
vincecabalan said:
Extract boot.img of installer mokee.zip Patch boot image https://patcher.yaalex.xyz/ select include magisk Expect to do uploud after downloading rename boot.img sdcard Go twrp flash boot install magisk manager apk
Credit to @idcamper
Click to expand...
Click to collapse
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.
speed_cars said:
I did according to this advice, uploaded boot.img to this site. Magisk works, but Wifi won't work . When I uploaded boot.img, Wifi works, then it shows that Magisk is not installed, but it was installed.
Click to expand...
Click to collapse
try this process after flash zip of the last magisk from reset factory
Can i do this on miui 11.0.3.0 indian rom based on Android 10. If yes then i need recovery.img pls help.
4. Rename custom recovery file to recovery.img
- where i can download this?, or this is the outcome of step 1?
Everything works fine, exept password. When i set new password, let's say it is 1234, i set the password in the setting, then i press the power button for lock screen, i put the password in as usual, but it just says try again over and over, im pretty sure that it is not my fault. Thanks for reply.
Anyone have patched boot 11.0.4?
jurubebaamarga said:
Well, a lot of people wanting to root global miui 11.0.7 and not being able to... So I did it on my Global redmi 7a - MIUI 11.0.7 Global.
Simple though. Apart from whats being said, u can update Magisk to v20.+ after flashing
the 19 version, through the app Magisk Manager automatically installed after flashing.
Prerequisites & Downloads:
- Your bootloader must be unlocked (https://en.miui.com/unlock/)
- ADB and Fastboot -> I did on windows version, maybe can be done on linux...
- patched boot.img for miui 11.0.7 global
- vbmeta.img
- Magisk v19.3 zip -> place it on the root of your external sdcard
This is basically copied from cg730620's post [Guide][Redmi 7A] TWRP, Root with Magisk, Custom ROM [GSI][Pie] and Avedroid's vid
1 - Unlock bootloader and flash stock miui 11.0.7 recovery rom, using miflash 2017
CAREFUL! On the lower right corner check the first option, "clean all", or you may end up with a locked bootloader.
-> exactly the same from the quoted post from now on, what differs is the files and we are only flashing magisk v19.3
"2. Install Minimal ADB and Fastboot
3. Rename patched boot file to boot.img
4. Rename custom recovery file to recovery.img
5. Place boot.img, recovery.img, vbmeta.img in Program Files (x86)/Minimal ADB and Fastboot/ folder
6. Turn off your phone.
7. Reboot phone to fastboot mode by holding Volume-down button while pressing On/Off-button. You know you are in fastboot mode when you see a cartoon bunny.
8. Connect the phone to your PC via USB.
9. On your PC open command prompt and nagivate to ADB folder, or open command prompt window directly from right-click menu in ADB folder; just right-click on empty space and choose 'Open command prompt here'
10. In command prompt, enter the following commands:
Code:
Code:
fastboot flash boot boot.img
Code:
Code:
fastboot flash vbmeta vbmeta.img
Code:
Code:
fastboot flash recovery recovery.img
11. Now reboot to recovery: Press Volume-Up button on your phone and enter the following in command prompt:
or just turn off the phone and reboot by holding Volume-Up and On/Off button (release On/Off when phone turns on, keep holding Volume-Up until you see screen of TWRP recovery)
12. Swipe to allow modifications. If TWRP asks for PIN, enter the PIN code you set for your unlock screen.
13. In TWRP choose Wipe > Advanced Wipe. Select 'Dalvik / ART cache', 'System', 'Data', 'Cache'. Then Swipe to Wipe.
18. In TWRP choose Install. Select the Magisk zip-file on your phone and then Swipe to confirm flash.
Reboot to system, open Magisk, update and there u go.
Same steps of the beginning of Avedroid's video, only with modified boot.img and Magisk Version
After 16:30 of the video he flashes a custom gsi rom which is not of the interest of this thread, just flash magisk.
Thanks to all who made it possible, especially Avedroid and cg730620
Post questions and answers here, please, NOT in PM.
Good luck!
Click to expand...
Click to collapse
I wish to obtain root / access to magisk,
Wanting to know if I can do this without losing data (having to delete system data)
Thank you
Hello.
So I was trying to root my Redmi 7A - v10.2.1 with TWRP 3.3.1 but now I am stuck in a bootloop.
What I did:
1. Flash boot.img
2. Flash recovery.img
3. Flash vbmeta.img
4. reboot
Phone rebooted to system and TWRP was installed.
Then I booted to TWRP to install Magisk-v23.0.zip,
I went to Advanced Wipe, then wiped 'Dalvik / ART cache', 'System', 'Data', 'Cache'.
When I rebooted, it went into a bootloop, when I go to TWRP it says 'No OS INSTALLED".
What did I do wrong? And how to recover?
Thanks.
Cinox said:
I did everything right, however, when it came to installing Magisk, the following error occurred: "Updater process ended with ERROR: 1".
So I redid the whole process, but before installing Magisk I did the following: I went to Mount, I deselected the System partition and after that the installation proceeded normally.
Well, I don’t know if this is the best way to fix this problem, I don’t understand much of these things, but it ended up working for me.
Thanks for the post
I will do some tests to see if everything is working.
Click to expand...
Click to collapse
Im also getting the same error,, but what do you mean by "deselected the System partition". I see "system_root" in Mount but not "System"
/*** BEGIN DISCLAIMER ***/
If you follow this procedure and lose every bit of content on your device / end up with a fancy paperweight, I, nor anyone involved with the referenced open source or otherwise licensed projects is responsible. It's all on you, and this will void your warranty. Do not proceed if you don't understand something. Chances are you will have a bad time.
/*** END DISCLAIMER ***/
Hey everyone - my Samsung Galaxy Tab A 10.1" (2019) - SM-T515 - recently applied a security update without my consent (The Samsung Android 11R September 8th 2021 Security update - side note, make sure that you turn off Samsung's push service ), which canned my previous root access. I use server software and internal port forwarding to do... Things on my device, so I needed my root access back.
Here's how I retrieved it, and how I put TWRP in place as my recovery partition in the process.
The Tools
Make sure you have these before you start. Because this is a Samsung device, you'll have to do some things under Windows, like using Frija and Odin (unfortunately).
1.) Frija - Available here - https://forum.xda-developers.com/t/tool-frija-samsung-firmware-downloader-checker.3910594/
2.) The latest SM-T515 / SM-T510 firmware from Samsung for your device's CSC (if you use the firmware for the wrong CSC code the most common problem that I have seen as a result is typically incorrect partition sizes after flashing, which can be corrected with TWRP). Frija is listed first, because you'll use Frija to get this directly from Samsung.
3.) Some kind of generic tool that you're comfortable with for working with archives. Ideally whatever tool you choose should be able to work with .tar, .gz, and .zip archives for this process. Personally I like 7-Zip on *Nix and Windows, and ZArchiver on Android.
4.) Odin (firmware flash tool by Samsung) - attached.
5.) The latest Samsung device USB drivers for your environment (they're fine as long as they enable both ADB and MTP correctly) - available here https://developer.samsung.com/mobile/android-usb-driver.html
6.) The latest TWRP image for Samsung SM-T5xx devices - available here https://androidfilehost.com/?fid=14943124697586374577 (and attached)
7.) ADB - downloading / installing and using adb are outside the scope of this post. It is available here - https://forum.xda-developers.com/t/...vers-15-seconds-adb-installer-v1-4-3.2588979/
8.) The latest Magisk APK file - available here https://github.com/topjohnwu/Magisk/releases/download/v23.0/Magisk-v23.0.apk
The Process
0.) Back up your stuff, and remove your SD card if it makes you more comfortable - do whatever you need to do to be comfortable with "I might lose EVERYTHING on this device." If you plan on following this procedure, you should know how to do this, and I'm not going to try to explain it. If you can't get past this part, you should stop while you're ahead and still have a device that boots.
1.) Unlock your bootloader.
2.) Download the most recent firmware package for your device using Frija and extract all of the individual .md5 files which it contains.
2.) Use Odin to flash the most recent firmware to your device, and factory reset / wipe / format partitions and caches until you have a clean device that boots correctly. If your partitions aren't sized properly at this point it isn't something to be too concerned with, as you can correct them later using TWRP.
3.) Turn developer options back on, enable USB debugging, set the default USB configuration to "File Transfer", connect your device to your PC and copy the Magisk APK over to the internal storage of your device.
4.) Remove .md5 from the filename of the AP file that was included in your firmware package from Samsung and extract its contents into its own directory.
5.) Extract the contents of the latest TWRP package for these devices into the same directory where you extracted the individual partition image files contained in the AP file. Overwrite contents in the destination directory as necessary. The TWRP package should contain three files - param.bin.lz4, recovery.img.lz4, and vbmeta.img.lz4 - If there are uncompressed images (.img files) that correspond to the LZ4 compressed images from the TWRP package in the AP file of your firmware package, remove them first. Odin will (understandably) freak out if you try to flash two different images to the same partition in the same flash operation.
6.) Compress the contents of your modified AP directory which now contains the TWRP package's contents into a tar ball on your PC, and then copy it somewhere that Magisk will be able to access it on the Internal storage of your device (the Downloads directory - "/storage/emulated/0/Downloads/" is a good choice).
7.) Copy the latest Magisk APK to your device (again, the Downloads directory is a good choice), and then install it on your device.
8.) Launch Magisk on your device and choose "Install". Be sure to uncheck the "Recovery Mode" option. We don't want to use "Recovery mode" for Magisk's patching process. Even though this is a Samsung device and this would normally be how to proceed, in this case we're using our own custom TWRP recovery partition, and we don't want Magisk to mess with it. So make sure you aren't patching the bootloader or recovery images in unnecessary ways with Magisk.
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition.
10). Let Magisk do its patching and when it has completed take note of where the patched file which it generated was written.
11.) Launch a command line / Powershell / Bash terminal where you can perform ADB commands, and issue the command "adb pull "/storage/emulated/0/Download/magisk_patched-23000_xYzXyZ.tar" (replace "XyZxYz" with whatever random sequence of characters that Magisk generated during its patching operations) to use ADB to download the patched AP file from your device.
12.) Power off your device.
13.) Reboot your device into FANCY download mode by holding the volume up and volume down keys simultaneously while inserting a USB cable that is connected to your PC into your device's USB C charger port. Your device should boot as you insert the USB cable and your bootloader should already be unlocked, so when prompted press the volume up button to continue.
14.) Launch Odin on your PC, and choose the BL, CP, CSC, and UserData images from the firmware package that you retrieved from Samsung to flash the corresponding slots in Odin. In the AP file slot, choose the Magisk patched AP file which contains TWRP as its recovery partition which you retrieved previously using ADB.
15.) Start the flash operation in Odin, and wait patiently for it to complete. Stay alert, because if you left "Auto reboot" checked in the Odin options, your device will reboot immediately upon completion, and there are actions that you need to take while the device is in its "off" state before it re-launches itself.
16.) Once the Odin flash operation has completed, boot to recovery mode. If you left "Auto reboot" checked in Odin, immediately as the flash operation completes, press and hold the power key and the volume up key and remove the USB cable from the device. Otherwise press and hold the power button and the volume down button until the device restarts, and while the device is in its "off" state remove the USB cable and press and hold the power button and the volume up button during device restart to enter recovery mode.
17.) Immediately upon entering recovery mode you should see TWRP do a couple of things that ensure that Samsung's device protection solutions don't remove it. Once those operations have completed, reboot into the system partition.
18.) Your device should be BASICALLY ready to go. Go through the steps to "complete" setup as you see fit. If you have not already done so, connect your device to a WiFi or to an LTE network and then launch the Magisk application.
19.) Magisk may want to download updates, if it does, let it do so.
20.) Once any necessary updates / downloads have completed, re-launch Magisk and it should present you with a prompt to the effect of "Magisk is installed, but additional configuration needs to be done on your device for it to work the right way. Do you want to reboot now?" If you've made it this far, the answer is "Yes, please do."
21.) After rebooting, your device will now be configured, and be running TWRP in its recovery partition, along with a properly Magisk rooted system partition.
22.) ????
23.) PROFIT!
I hope this helps some people out!
- The Scarecrow - 2021/09/22
Has anyone besides been successful?
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
I can provide screenshots from the device that I did this to if you would like.
It's pretty cool to see the TWRP logo on a Samsung Tab series device that's running Android 11.
I don't even get the little Samsung warning prompt during device bootup that says "This device's software can't be verified" or whatever Samsung's custom ROM message is. All I get is the "This device's bootloader is unlocked" message, no warning about the integrity of the software.
mydjtl said:
Has anyone besides been successful?
Click to expand...
Click to collapse
Follow this simple as he'll no need to read all these things
pankspoo said:
Follow this simple as he'll no need to read all these things
Click to expand...
Click to collapse
Yeah - pretty much exactly that, except I Magisk patched the system image, and then copied the TWRP package's vbmeta and recovery image into the AP file for the Odin flash, and then flashed every slot rather than just the AP.
is it systemless root?
Will this work on Galaxy Tab A sm-t595? on android 10?
or know of a root guide that will work with said device?
If you dont untick auto reboot, how do you fix any issues that happen because of it?
I rooted my t500 but I think it auto rebooted, which then caused a vbmeta error that stopped it booting. It worked again after flashing the stock rom, but now it gives a vbmeta error if I try to flash a modded rom to root it and I cant get oem unlock to appear in the stock os (download mode says its already unlocked tho)
Hello,
Code:
9.) In Magisk on your device, choose "Select and patch a file" and then choose the AP file that you created and copied to the device which now contains TWRP as its recovery partition
Step 9 yields an error on T515 : Unsupported/Unknown image format
I also tried to install AP patched file with Odin, same result.
Any idea ?
Damn this works so nicely, thanks mate! Cheers!
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
If there's enough demand I'll write a proper guide. Also if soft bricked you need to press both volume buttons and plug in usb at right point on restart.
jameswalker457 said:
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
Click to expand...
Click to collapse
Thanks @jameswalker457
Which one did you use CSC_HOME or CSC?
When I run with CSC, I get a 'fail' in ODIN However, it does run with CSC_HOME, BL and the patched AP - but it doesn't actually root the device.
Greatful for your help.
Thanks
Used BL AP (with patched boot.img) CSC and HOME_CSC in the userdata
kevinsims said:
Thanks @jameswalker457
Which one did you use CSC_HOME or CSC?
When I run with CSC, I get a 'fail' in ODIN However, it does run with CSC_HOME, BL and the patched AP - but it doesn't actually root the device.
Greatful for your help.
Thanks
Click to expand...
Click to collapse
See above. Missed the quotation
I'm not sure why we need a third thread for this:
SM-X200 root failed...
It's now a bricked tablet after a boot loop, I think should wait to magisk get an update. It won't power on or charge I think. I have two days trying to power on in several times and many key conbinations. No Samsung logo or something. Can I do...
forum.xda-developers.com
The best way to root samsung tab a8 2021 pls
Android 11 I got fast as f boot loop solution below btw An 4 gamers I got fps/ping boost solution below to
forum.xda-developers.com
I still do not have root. What I did:
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" tar -C AP_folder -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
For some reason I can't get from download mode to recovery w/o first booting the fresh android.
No boot loop, but no root either.
These are the file names I got from Samfw:
AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5
BL_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT.tar.md5
HOME_CSC_OMC_XAR_X200XAR1AVC1_CL23784803_QB49838021_REV00_user_low_ship_MULTI_CERT.tar.md5
The md5sum of the files:
AP stock: fa97e5cee1deaf26175b27d26df94266
AP patched: 006b12f713fc3caa127bc5cba01ae4b9
BL: 2172ca468462a46917d78e94157aed54
HOME_CSC: 5ede57b9ffe8059f3166dd5de6ef8721
The tar file worried me. It had file names like ./boot.img instead of boot.img. So I created a new file, with the patched boot.img, this way:
cd AP_folder
tar -cvf ../AP_patched.tar *
Then flashed that. Took longer than the previous tar.
On reboot, it asks me to press PWR to accept boot loader unlocked. Then a splash screen saying: unapproved software, then a few boot loops.
I got to recovery, factory reset, the tablet does the LONG boot, does the initial setup thing.
Install Magisk Manager, and root! Google Play still works.
Whoopee! I can now wait for a working TWRP.
jameswalker457 said:
Hello guys. I failed several times rooting this device and finally managed to root.
You need to extract AP tar and then replace the boot.img with a magisk patched one.
You then need to re tar the file using 7zip and flash as normal.
AP CSC HOME CSC and BL
Click to expand...
Click to collapse
Hello, I have a problem/doubt. I have the files AP, BP... etc I use 7zip to extract the boot.img ..... if I unzip all the AP XXX.tar.md5 the 7zip warns me that there is data after the file, it warns me of an error and at the end it stops in the fota . ...when I replace the boot.img in the AP folder by the one corresponding to the patched with Magisk and use the 7zip again to create the .tar the file does not work with ODIN...I do not know what step or mistake I make. Regards
PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
PS: Root! Thanks Jameswalker457 Cheers! ....
Translated with www.DeepL.com/Translator (free version)
IkeGolden said:
Hello, I have a problem/doubt. I have the files AP, BP... etc I use 7zip to extract the boot.img ..... if I unzip all the AP XXX.tar.md5 the 7zip warns me that there is data after the file, it warns me of an error and at the end it stops in the fota . ...when I replace the boot.img in the AP folder by the one corresponding to the patched with Magisk and use the 7zip again to create the .tar the file does not work with ODIN...I do not know what step or mistake I make. Regards
PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
PS: Root! Thanks Jameswalker457 Cheers! ....
Translated with www.DeepL.com/Translator (free version)
Click to expand...
Click to collapse
> if I unzip all the AP XXX.tar.md5
That is because a .tar.md5 is a tar file with an md5 concatenated to it.
> use the 7zip again to create the .tar the file does not
The proper tool to create .tar files is "tar".
>PS: I'm extracting the files instead of unzipping the .tar.md5 to see if that's the problem ....
Care to be more specific on how you did that?
>PS: Root! Thanks Jameswalker457 Cheers! ....
Good news.
Have root my SM-X205 (LTE) for 1 Feb Patch level but no go with latest May update.
Getting constant boot loop (exactly same process, magisk boot.bin etc) so rolled back to Feb for now.
lufee84 said:
Have root my SM-X205 (LTE) for 1 Feb Patch level but no go with latest May update.
Getting constant boot loop (exactly same process, magisk boot.bin etc) so rolled back to Feb for now.
Click to expand...
Click to collapse
What firmware version worked, and which failed?
X200XXU1AVC1 worked for me.
Yes, X205XXU1AVC1 works.
No luck with latest X205XXS1AVE1 (May Patch).
garyemiller said:
I'm not sure why we need a third thread for this:
SM-X200 root failed...
It's now a bricked tablet after a boot loop, I think should wait to magisk get an update. It won't power on or charge I think. I have two days trying to power on in several times and many key conbinations. No Samsung logo or something. Can I do...
forum.xda-developers.com
The best way to root samsung tab a8 2021 pls
Android 11 I got fast as f boot loop solution below btw An 4 gamers I got fps/ping boost solution below to
forum.xda-developers.com
I still do not have root. What I did:
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" tar -C AP_folder -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
For some reason I can't get from download mode to recovery w/o first booting the fresh android.
No boot loop, but no root either.
Click to expand...
Click to collapse
Not sure if this helps but i read an article that says you should patch the whole AP tar file rather than extract just the boot.img. Maybe because it patches the recovery and super etc img files too? I havet tried this yet as I cant even get my bootloader unlocked
dan.langridge88 said:
Not sure if this helps but i read an article that says you should patch the whole AP tar file rather than extract just the boot.img. Maybe because it patches the recovery and super etc img files too? I havet tried this yet as I cant even get my bootloader unlocked
Click to expand...
Click to collapse
Dunno where you read that, don't care. This works (as above):
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" cd AP_folder"
" tar -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
Note the fixed "tar" command. Do not use "tar -C".
garyemiller said:
Dunno where you read that, don't care. This works (as above):
1. unlocked bootloader
2. install magisk manager 24.3
3. Download X200XXU1AVC1 from Samfw
4. unzip the firmware
5. Untar the AP tar file
6. Extract boot.img, send to device, and patch with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
7. Replace boot.img with the newly patched one (renamed to boot.img)
8. Create a tar file from the AP folder using
" cd AP_folder"
" tar -cvf AP_patched.tar ."
9. "adb reboot bootloader" to download mode
10. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar
9. Flash via Odin, exit download mode, enter stock recovery, factory reset
Note the fixed "tar" command. Do not use "tar -C".
Click to expand...
Click to collapse
OK, I've un-tarred the AP tar.md5 and patched the old boot-img file on the device, renamed it and replaced the original boot.img in the AP "folder".
Steps 8 & 9 are a little confusing for me, if you could expand on those. Can I use 7zip to re-tar? Those look like DOS commands in step 8.
Ar-Pharazon said:
OK, I've un-tarred the AP tar.md5 and patched the old boot-img file on the device, renamed it and replaced the original boot.img in the AP "folder".
Steps 8 & 9 are a little confusing for me, if you could expand on those. Can I use 7zip to re-tar? Those look like DOS commands in step 8.
Click to expand...
Click to collapse
Slightly expanded:
1. unlocked bootloader
2. install magisk manager 24.3 on the tablet
3. Download X200XXU1AVC1 firmware from Samfw onto PC
4. unzip the X200XXU1AVC1 firmware zip file
5. Make a directory for the AP tar contents
"mkdir AP"
6. Untar the AP tar file into directory AP, all on one line:
"tar -xvf AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5 -C AP"
7. Change the current directoy to the AP directory:
"cd AP"
8. Using adb send boot.img, to the tablet,.
9. Patch boot.img with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
10. Using adb copy magisk_patched-24300-9Iez2.img from the tablet and into the AP directory.
11. Rename magisk_patched-24300-9Iez2.img to boot.img:
"mv magisk_patched-24300-9Iez2.img boot.img"
12 Create a tar file from the AP directory Note the space and period(".") after ".tar":
" tar -cvf AP_patched.tar ."
13. Use adb on PC to enter download mode on tablet:
"adb reboot bootloader"
14. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar as files to be flashed.
15. Flash via Odin, exit download mode, enter stock recovery, factory reset
How about that?
garyemiller said:
Slightly expanded:
1. unlocked bootloader
2. install magisk manager 24.3 on the tablet
3. Download X200XXU1AVC1 firmware from Samfw onto PC
4. unzip the X200XXU1AVC1 firmware zip file
5. Make a directory for the AP tar contents
"mkdir AP"
6. Untar the AP tar file into directory AP, all on one line:
"tar -xvf AP_X200XXU1AVC1_CL23784803_QB49828201_REV00_user_low_ship_MULTI_CERT_meta_OS11.tar.md5 -C AP"
7. Change the current directoy to the AP directory:
"cd AP"
8. Using adb send boot.img, to the tablet,.
9. Patch boot.img with magisk 24.3. Patched boot is magisk_patched-24300-9Iez2.img
10. Using adb copy magisk_patched-24300-9Iez2.img from the tablet and into the AP directory.
11. Rename magisk_patched-24300-9Iez2.img to boot.img:
"mv magisk_patched-24300-9Iez2.img boot.img"
12 Create a tar file from the AP directory Note the space and period(".") after ".tar":
" tar -cvf AP_patched.tar ."
13. Use adb on PC to enter download mode on tablet:
"adb reboot bootloader"
14. open Odin v3.14.1 and add BL, HOME_CSC, and the AP_patched.tar as files to be flashed.
15. Flash via Odin, exit download mode, enter stock recovery, factory reset
How about that?
Click to expand...
Click to collapse
I'm guessing those are Linux commands?
In any event, I made 7zip re-tar the AP folder with the patched boot.img, but it ends in .tar.tar
Is this an issue, or should/can it be renamed .tar.md5 like the original?
Ar-Pharazon said:
I'm guessing those are Linux commands?
In any event, I made 7zip re-tar the AP folder with the patched boot.img, but it ends in .tar.tar
Is this an issue, or should/can it be renamed .tar.md5 like the original?
Click to expand...
Click to collapse
I do them on Linux, but they can also work on WinBlows. Since I do not use M$ products, I can only say I've seen those commands work on WinBlows, but can't say how to set that up.
I also can't help you with 7zip, it can run on Linux, but never use it myself.
People have problems when they don't use "real" tar, so don't. Save yourself the pain.
You do not need to convert the .tar to a .tar.md5. Odin will use either file type. A .tar.md5 file is a .tar file with its md5 hash appended. Odin can use the file to verify the .tar integrity, but that is optional.
Ieudhd
i donloaded diud
Hello Sams10, did you make the bootloader before or not as explained in the tutorial.
You said your flasher with odin more detail would be welcome, how did you do there according to your comment your flashed directly in download mode without having done the manipulation for the bootloader and then did what.
bootloader unlocked and kg checking
every instructions for s10 is outdated including the lineage os website and youtube i have checked all
heimdalll latest 1.4.2 doesnt work with samsung s10.
19.9.2022 on latest android firmware new zealand firmware custom rom doesnt work , only europe and americas will work
Hello Sams10, already a little politeness because I said hello to you, you post 4 times without saying hello.
I don't understand the unlock bootloader ok then S10 is good s10 exynos or 5 G, I followed John Wu's tutorial as explained in the magisk thread on this forum no problem.
You have well modified in magisk AP of the official rom then trafer on your pc with adb pull then odin 3.14.4 flash the 4 files BL-AP patched-CP Home CSC.
g973F exynos, not 5g, u must be americas europe firmware , vodafone nz firmware probably doesnt work
this is my current download mode
my screen is cracked thats the purple lines and dead pixel on top left
Not work
Hello Sams10, you start in dowload mode you flash with odin 3.14.4 the official firmware the one mark in my signature me AUT or XEF lash the 4 BL-AP-CP-CSC files it will restart as on the first day. Then install magisk 25.2 you transfer AP on your S10, you modify with magisk you will have a file in internal memory in dowload magisk_patchedxxxx.tar you transfer it with ADB on the pc which in adb must give this adb pull /sdcard/Download/magisk_patched-25200_G3e9K.tar
once transferred ok you put yourself in dowload mode and you put the file BL -AP patched -CP -home CSC you start you let it restart and you open magisk to activate zygisk then you install the modules you will find here https://forum .xda-developers.com/t/discussion-magisk-the-age-of-zygisk.4393877/
instalation look here from john Wu https://topjohnwu.github.io/Magisk/install.html
read the instruction part, then when you have finished and root I will send you the file to remove the warning message at start-up ok
I use ap magisk patched and CSC , not home CSC when I flashed and had boot loop
Does it have to be an adb pull for the patched firmware from Android , I just use file transfer on windows to transfer the magisk patched ap file from the s10 to the windows
Try with home CSC as john wu says you have to do adb from s10 to pc with adb windows not send all.
Start the installation, and copy the patched tar file to your PC using ADB:
adb pull /sdcard/Download/magisk_patched_[random_strings].tar
DO NOT USE MTP as it is known to corrupt large files.
John Wu says CSC not home csc because he want to erase firmware data
Hello Sams10, yes you made a backup of your data before with smart switch or others. For me it worked if you follow the present tutorial look on my tutorial
1- The bootloader follow explanation Use vol down + vol up + USB cable plugged into a PC to boot the phone into download mode;
Long press vol up then confirm that you want to unlock the bootloader (this is only needed once);
* Please note that all your data will be erased, including internal memory, and the phone will restart!!
5- Let the phone start normally, go through the configuration and connect to the Internet (wireless or mobile data) in order to unlock
6- Make sure OEM Unlock is enabled in Developer Settings.
2- Once reboot install magisk 25.2 APK.
3- Download the official firmware on Samobile.com or frija you will find this on the forum.
4- Transfer the official firmware AP to the smartphone.
5- Open magisk recovery mode choose corrective mode choose the AP download press "let's go."
6- Once the modification is finished in the root directory, download a patched_magiskxxxx.img.tar file if found.
7- Transfer it with adb pull like this adb pull /sdcard/Download/patched_patched.magiskxxxx.img[.tar] you can rename it "patched_magisk.img.tar"
8- Put your smartphone in download mode Use vol down + vol up + usb cable connected to a PC to start the phone in download mode, briefly press vol up to
confirm that you want to enter download mode;
9- Open Odin latest version placed 4 files following BL-AP magisk patched.img.tar-CP-home CSC leaves auto start checked in odin option.
10- It will restart open magisk activated Zygisk restart install safetynet modules - shamiko-hidemagisk prop config-busybox nk-lposed see on this page https://forum.xda-developers.com/t/discussion-magisk-the-age -of-zygisk.4393877/
message #3-#6 to #9.
11- Install foxmagiskmodulemanager the catalog of modules for magisk here https://github.com/Fox2Code/FoxMagiskModuleManager/releases
12- Once rooted the security message for the removed open Odin place UP-param.tar in AP and flashed. See attached file
Up_param.tar download link on my mega here to know for S10 exynos for S10e- S10+ versions see 5G I don't know if it works.
Is this normal I have to wait about 30 minutes after power off to try get into download mode??
Maybe something is broken the phone like doesn't turn off properly or something, have to wait sometimes one hour