Hi All
Please see steps below to make stock rooted firmware for flashing in odin:
1 unpack stock odin firmware for your update
2 copy AP file to tablet and patch with magisk - copy the resulting "magisk_patched.tar" to your firmware folder when patching finishes
3 get your TWRP file of choice and load it onto this website https://cruelkernel.org/tools/bootimg/ - patch it to the date matching your firmware's security patch date - March 2021 in the case of CUB7 (I HAVE BEEN USING THE 3.13 TWRP BY MENTALMUSO QUITE HAPPILY SINCE SEPTEMBER LAST YEAR)
4 Open magisk_patched.tar with 7zip and delete recovery.img.lz4. You then need to rename the TWRP file you date patched "recovery.img"
5 Drop this recovery.img into the magisk_patched.tar you have opened with 7zip
6 extract the vbmeta.img in magisk_patched.tar and set this aside
7 extract the BL file to a folder, delete the vbmeta.img.lz4 which is there and replace that with the vbmeta.img from Magisk_patched.tar from step 6
8 re-zip the bl folder using 7zip.
you now have the stock rooted odin files you can flash in odin for a seamless and data safe update!
TO UPDATE DEVICE WHEN YOUR FILES ARE MADE:
1 reboot to download mode
2 load Magisk_patched.tar in AP, BL in BL, CP in CP (T865 only) and HOMECSC in CSC slot and flash these with Auto reboot off in odin
3 Press vol down and power to exit download and then press and hold vol up and power until you are in TWRP
4 Flash the Multidisabler 3.1 from @ianmacd here
5 reboot your updated device to system!!!
Related
finally! succesfully patch my mk4 rom using heimdall on osx, now my wifi is working thanks so much doc... in case somebody wants to know how
dr ketans wifi patch http://forum.xda-developers.com/showthread.php?t=2531965
1: download GUI Tar https://www.macupdate.com/app/mac/14503/gui-tar
2. download dr ketan wifi patch, extract contents
3. edit file patch.tar.md5 to patch.tar
4. extract the contents of patch.tar using GUI Tar, files are param.bin, tz.img
5. from heimdalls utilities tab download your PIT file
6. go to flash tab, browse through your downloaded pit file.
7. under partitions press add, in partition details > partition name choose tzsw, in file choose tz.img (the file you extracted using GUI Tar)
8. again, under partitions press add, in partition details > partition name choose param, in file choose param.bin (the file you extracted using GUITar)
9. click restart, your device will reboot after flashing
hit thanks if u think i helped you
thanks again dr ketan for your awesome patch....
Reference Thread
Samsung Galaxy S4 I9500 Lollipop Modems and Bootloaders
Technical background
Actually, we have a dedicated thread that should host updated modems and bootloaders (for both I9500 and I9505). However, the thread was no longer updated since 2014, even the OP is never online since 2014. So, I created this thread to host all Lollipop bootloaders and modems for I9500.
Why do need we update our modem and bootloader?
As you may know, firmwares are updated often, as long as our device still get support from Samsung. Custom ROMs does the same. And often new updates are giving problems with incorrect version of your modem or bootloader (like you installed Lollipop firmware on KitKat bootloader). We need to update our modem and bootloader to ensure the maximum compatibility available and will keep us secure, everywhere (althrough we need an additional protection too).
Installation procedure
Installation via recovery (modem only):
Make sure you've installed the latest version of CWM/PhilZ/TWRP. I'd recommend TWRP.
Make sure you've done an EFS backup (just to be safe).
Reboot to Recovery mode by combination of Power+Home+Vol(+) buttons.
a. For CWM, select Install zip from sdcard.
b. For PhilZ, select Install zip then select Install zip from sdcard0 or sdcard1.
c. For TWRP, select Install.
Navigate to modem zip.
a. For CWM/PhilZ, select "Yes, instal ..."
b. For TWRP, swipe Install button.
Reboot to system.
If after installation of modem your baseband version is Unknown, restore your EFS backup.
Installation via Odin (modem and/or bootloader):
Make sure you've installed the latest version of Samsung USB Drivers on your computer.
Make sure you've done an EFS backup (just to be safe).
Reboot to Download mode by combination of Power+Home+Vol(-) buttons and proceed by pressing Vol(+).
Plug your phone to your computer.
Extract the archive (if compressed).
Open Odin and select modem and/or bootloader .tar or .tar.md5 file(s) into the corresponding location.
Select Start to proceed.
In case if your modem and/or bootloader isn't updated, repeat step 3-6, untick Auto Reboot, and select Start to proceed. Then, do a hard reboot by holding power button for 10 seconds.
If after installation of modem your baseband version is Unknown, restore your EFS backup.
How to contribute
You're welcome to send your contribution. Make sure that version you want to contribute isn't listed on this thread. You need two files: modem.bin and sboot.bin. You could obtain by extracting both files from stock firmware .tar.md5 using 7-Zip on Windows or Archive Manager on Ubuntu (remove .md5 extension first).
Packing into .tar file(s) (modem and/or bootloader):
You need an Ubuntu-installed machine or any distribution based on Ubuntu installed on your machine.
Move both files into your working directory.
Open Terminal and move it into your working directory. Example, if you're working on Desktop folder, enter this command:
Code:
$ cd Desktop
Pack one by one files using these commands:
Code:
$ tar -h ustar -c modem.bin > MODEMVER.tar [COLOR=Green]# Modem[/COLOR]
$ tar -h ustar -c sboot.bin > BOOTLOADERVER.tar [COLOR=Green]# Bootloader[/COLOR]
Replace MODEMVER.tar and/or BOOTLOADERVER.tar with version you're packing. Example, if you're packing I9500UBUHOK1 modem, change MODEMVER.tar to I9500UBUHOK1-MODEM.tar.
Add md5 checksum into .tar file(s) using this command:
Code:
$ md5sum -t PACKAGE.tar >> PACKAGE.tar
Replace PACKAGE.tar with .tar file(s) you've created. If you've more than one .tar file, insert one first and repeat this for another one.
Finally, rename file(s) using this command:
Code:
$ mv PACKAGE.tar PACKAGE.tar.md5
Replace PACKAGE with .tar file(s) you've created (without .tar extension).
Compress it into zip file(s) then attach it here or upload to somewhere else.
If you're a bit lazy to do all these steps above, grab any Odin flashable .tar files, delete everything and replace it with modem.bin or sboot.bin then rename it.
Packing into .zip file (modem only):
Download the attached template below.
Open it with any archiver app.
Put modem.bin inside modem folder.
Rename the .zip file to the version you've included.
Attach it here or upload it somewhere else.
This list is incomplete. Help me to complete this list by contributing.
Note: Sorted by the changelist number.
Latest:
UBUHPB2 (Latin America)
Changelist number: 7068753
Download: Modem Zip - Odin | Bootloader
UBUHOK2 (Latin America)
Modem version: UBUHOK1
Changelist number: 6332925
Download: Modem Zip
XXUHPB3 (Middle East and Africa)
Modem version: XXUHPB1
Changelist number: 6164126
Download: Modem Zip - Odin | Bootloader
XXUHOC6 (South East Asia)
Modem version: DXUHOA1
Changelist number: 3943544
Download: Modem Zip
Thread closed at OP's request.
Is there a way to root samsung j4 plus model : j415gn?
Download the firmware on sammobile. Then extract the folder. Extract the ap tar file and there is a file called boot.img.lz4. Download lz4 latest version and drag the boot.img.lz4 and open with lz4(just drag it onto the lz4). Now you will have a boot.img. transfer this to your phone via mtp. Select install in magisk and then patch a file. Select the boot.img. You now have a patched boot img. Download zarchiver and convert it to tar format. Now flash this file in the ap slot in Odin. After reboot, the phone will auto factory erase. After it has finished erasing, power off the phone and hold the recovery combo. Now reboot to system and immediately hold the recovery combo. Set up your device and enjoy magisk
I got a backup of my boot.img in the twrp menu , then patched it with magisk, moved it to the computer and compressed it to boot.tar and renamed it to boot.img.tar
After flashing it with odin my phone just restarted with no changes ??
Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up
Feox said:
Hello guys! I'm trying to install a patched boot.img file from my Samsung Galaxy A03 for root but I can't. Every time in download mode when I want to flash the magisk_patched file renamed to boot.img and compressed to boot.tar with Odin, I get 3 types of errors:
The first is that during the flash, Odin for no reason suddenly crashes
The second is that I get a message from succeed 0/failed1
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
No ports defect is present in my opinion because the phone is perfectly detected when it is in normal mode and I can freely access its storage on my PC.
I have a phone with version number A035GXXU1AVC1 and I downloaded the correct firmware for my phone here: https://samfw.com/firmware/SM-A035G/AMO/A035GXXU1AVC1
The steps I went through are:
1) Enable developer mode and enable OEM unlock to unlock payload boot
2) Unlock the bootloader in the Download Mode
3) Download the firmware from the given link
4) Installed Magisk latest version on the phone
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
6) Move this isolated copy of boot.img into the phone to patch it with Magisk
7) Once patched, no errors in Magisk
8) Move the patched copy to the PC then rename it to boot.img and create a tar file containing this patched boot.img
9) Open Odin and in Downloade Mode try flashing the patched boot.tar file but that's where it gets stuck and Odin errors show up
Click to expand...
Click to collapse
Feox said:
The last is that the program freezes on SetupConnection while the cable is well connected from the PC to the phone.
Click to expand...
Click to collapse
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.
ethical_haquer said:
I had the above issue myself, and after searching I found this answer and it actually worked, even though it seems silly.
Click to expand...
Click to collapse
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...
Feox said:
Sorry for the late reply, I was busy with several other things... When I try the steps in the answer you gave me, I now have Odin freezing on File analysis with versions 3.13.1 and 3.14.4. With the version I was using, 3.10.6, Odin suddenly started crashing instantly this time rather than displaying the errors mentioned in my first message in this thread... I don't know what to do... I tried to Root a Samsung Galaxy A02s, an A12 and before that an old Huawei Y6 from 2014 years ago and I had the same problem every time which is that Odin gives me random errors like what I present for this A03...
Click to expand...
Click to collapse
So you are following the official installation instructions? I'm pretty sure you don't have to:
Feox said:
5) Extract the files from the downloaded firmware AP file with Winrar and make an isolated copy of the boot.img
Click to expand...
Click to collapse
as the official installation instructions for a Samsung device running A9 or higher say:
"
Unzip the firmware and copy the AP tar file to your device. It is normally named as AP_[device_model_sw_ver].tar.md5
Press the Install button in the Magisk card
If your device does NOT have boot ramdisk, check the “Recovery Mode” option
Choose “Select and Patch a File” in method, and select the AP tar file
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.
"
It doesn't sound like you have to isolate the boot.img.
Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?
Feox said:
Oh OK thanks man! I go try tonight to make a patched OS with Magisk with the entire AP file. What I have do is patch only the boot.img IN the AP file.
And last question. How to know if the phone have ramdisk? Ramdisk is the RAM or nothing to see?
Click to expand...
Click to collapse
Just read the official installation instructions I linked to. I only copied part of it and pasted it here so you could see it.