How To Install Rom Using Odin

You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.

• #one

Basically what the championship says. I'chiliad using ODIN to flash a patched boot.img, since apparently that'southward the only way to install this on a samsung device, and... well, I'm at a total loss virtually what to do. I'yard using version 3.13 of ODIN. I tried installing it past putting the file where information technology said AP (since the .tar file I took the original boot.img from also had that name), but it simply failed.

Does anyone take any idea as to how I should use ODIN to pull this off? I would appreciate any tips you could give me, since I'grand a total novice on this

• #ii

Okay, I've looked into this a bit further. It seems I'm not doing annihilation incorrect, but when I try flashing the patched kicking.img, a bulletin appears on my phone saying "Merely official released binaries are allowed to be flashed(Boot)". And it fails outright.
Is at that place any way to circumvent this aside from custom recoveries?

• #3

Okay, I've looked into this a scrap farther. It seems I'm non doing anything wrong, merely when I try flashing the patched kick.img, a bulletin appears on my phone saying "Merely official released binaries are allowed to be flashed(BOOT)". And it fails outright.
Is in that location whatsoever style to circumvent this aside from custom recoveries?

There is plenty info on xda already, why don't you just look for it?
your bulletin is related to oem unlock. Seek for information technology.

Sent from my SM-A605FN using Tapatalk

• #4

There is enough info on xda already, why don't you just look for it?
your message is related to oem unlock. Seek for it.

My phone is in fact already oem unlocked. I made sure of information technology.
I should probably have mentioned that in the first post... oh well.
If it's OEM unlocked, then it shouldn't have this problem, correct?

• #v

Okay, I've looked into this a bit farther. It seems I'1000 not doing anything incorrect, but when I effort flashing the patched boot.img, a bulletin appears on my phone saying "Only official released binaries are allowed to be flashed(BOOT)". And it fails outright.
Is there any way to circumvent this bated from custom recoveries?

There is a patched ODIN that is much more chill with binaries that may not exist official.

• #6

There is a patched ODIN that is much more chill with binaries that may not be official.

Splendid, thanks! I'll exam it out when I have time and and then get back to you

• #seven

There is a patched ODIN that is much more arctic with binaries that may not be official.

Um, first of all, sorry to reply to you then tardily. I had a lot of stuff to accept intendance of.
However, I want to say that the patched ODIN that you told me to use did not piece of work. In fact, everything ocurred the same manner as when I used the official version. It'due south very confusing.
Regardless, whatsoever further assist with this would be greatly appreciated, especially if it doesn't involve using a custom recovery
I really want to install Magisk, information technology seems actually useful...

• #8

When I kicking into download mode, it as well says that RMM state is "prenormal". Does that assistance?

• #10

What is your phone model? Which magisk paradigm are yous trying to wink? Did you lot enable "OEM Unlock" in developers settings?

My phone is a Samsung Galaxy J6, model SM-J600GT.
The Magisk I'm trying to flash is the about recent one, version 18.i, I think.
And I accept indeed enabled OEM Unlock.

• #11

My phone is a Samsung Galaxy J6, model SM-J600GT.
The Magisk I'thousand trying to flash is the most recent one, version xviii.one, I think.
And I have indeed enabled OEM Unlock.

Are you patching the kicking.img every bit a .tar? Maybe as .tar.md5

• #12

Are yous patching the boot.img as a .tar? Perchance as .tar.md5

I am indeed patching information technology every bit a .tar. How would I go about turning information technology into a .tar.md5 file?
I'm really starting to suspect it has to do with that RMM state being prenormal thing based on a few things I've read. I'm going to try waiting 7 full days of activeness and attempt to patch it again, unless I can find a improve solution.

• #xiii

I am indeed patching it every bit a .tar. How would I go near turning information technology into a .tar.md5 file?
I'm actually starting to suspect it has to practice with that RMM state being prenormal thing based on a few things I've read. I'thousand going to endeavor waiting 7 total days of activeness and endeavor to patch it once again, unless I can detect a better solution.

Probably a good idea. I've seen ppl simply add .md5 at the end to get Odin to recognize it.

• #14

Alright, and then it's settled. When I finally effort it out, I'll come back to yous guys.

• #xv

Well, then. I'm back, and have zilch to bear witness for information technology.
RMM State continues to exist prenormal, despite me keeping the phone active through 7+ days of activity. Booted information technology into download mode, aforementioned trouble: a bulletin maxim "Simply official binaries are allowed to be patched" and then zilch. I've waited fashion too long for this.

I need help. Whatever suggestions would be greatly appreciated. I don't accept any other ideas.

• #16

Last edited: Apr 24, 2022

• #17

Erm... what do you hateful by that?

• #eighteen

Erm... what do you hateful by that?

Jesus, I was about to annotate on the thread nearly the patched Odin without existence logged in.
Later logging in I got somehow redirected to this thread and didn't check. Sorry. :giddy:

• #19

Jesus, I was most to comment on the thread about the patched Odin without being logged in.
Subsequently logging in I got somehow redirected to this thread and didn't check. Sorry. :lightheaded:

S'okay. It's not like anyone only me checks this thread anyway, heh

• #20

S'okay. It'due south not like anyone but me checks this thread anyhow, heh

I just got my new Samsung Tab S5e today and was having the verbal aforementioned error equally you trying to flash it. I was able to "gear up" it past unselecting "Auto Reboot" in the Odin options.

HOWEVER! After it "successfully" flashed my Magisk-generated patched_boot.img.tar, I bootlooped hardcore until I restored the stock firmware. It was hard to become the tablet back into Download mode information technology was looping so much (had to force it into Recovery outset, and so select "Reboot to bootloader").

Your mileage may vary, and so go ahead and attempt unselecting Auto Reboot, but beware there'due south a skilful chance you'll bootloop like me.

Edit:

Yeah, okay, assuming you're on whatsoever Samsung device that shipped with Android Pie, installing Magisk got a lot more than complicated. Read these two things to get a lay of the state before proceeding:

https://topjohnwu.github.io/Magisk/samsung
https://forum.xda-developers.com/galaxy-s10/development/magisk-root-galaxy-s10-serial-t3918699/

Concluding edited: Apr 26, 2022

Similar threads

Source: https://forum.xda-developers.com/t/installing-magisk-using-odin.3910980/

Posted by: ortizbletismue.blogspot.com

Share this post