- Jodin3 linux как установить
- Как прошить Samsung в Mac OS и Linux
- Содержание
- Рекомендуем вам получение root прав в 1 клик, используя Rootkhp Pro
- Как прошить Samsung в Mac OS и Linux
- Как пользоваться JOdin3 в Mac OS
- Как пользоваться JOdin3 в Linux
- JOdin3: прошиваем Samsung в Mac OS и Linux
- Mac OS и Linux не для установок прошивок?
- Прошиваем Samsung в Mac OS и Linux с помощью JOdin3
- Используем JOdin3 в Mac OS
- Используем JOdin3 в Linux
- [Utility] Odin for Linux . (JOdin3 CASUAL)
- Breadcrumb
- Toby4213
- iamhugo
- Metalhead32423
- mgc123
- Zakku
- Toby4213
- henk_j
- HonestOtter
- StoneRcold
- phoenixbyrd
- Toby4213
- xdausernl
- xdausernl
- Toby4213
- xdausernl
- Toby4213
- xdausernl
- Toby4213
- xdausernl
Jodin3 linux как установить
Новые темы необходимо создавать только в корневом разделе! В дальнейшем они будут обработаны модераторами.
Если Вы выложили новую версию программы, пожалуйста, сообщите об этом модератору нажав на вашем сообщении кнопку «Жалоба».
Samsung JOdin3
Версия: r1142
Последнее обновление программы в шапке: 16.01.2021
Краткое описание:
JOdin3 — неофициальный, бесплатный, кросс-платформенный Odin на Java с поддержкой macOS и Linux (для устройств Samsung).
Описание:
Официальный Odin | Мобильный Odin
Odin, как известно — это бесплатный, стабильный и потому весьма популярный инструментов для работы с прошивками смартфонов и планшетов Samsung Galaxy. Но работает он только с Windows. Для Mac OS X же требуется сначала JOdin3.
JOdin3 — инструмент тоже неофициальный, но бесплатный, в достаточной степени функциональный, позволяет использовать Odin с macOS и поэтому тоже популярный.
Из основных и самых полезных возможностей JOdin3 выделить можно следующие:
- возможность устанавливать стоковые прошивки Samsung;
- возможность устанавливать Custom Kernel;
- возможность устанавливать т.н. кастомные рекавери, в том числе TWRP Recovery;
- возможность устанавливать файлы root;
- поддержка файлов .tar или .tar.md5.
Само собой, с помощью JOdin3 всё это делать можно с Mac-а и MacBook-а. При определенных условиях, а именно:
- требуется предварительно скачать и установить на комп платформу Java RunTime для MAC OS X (линк) и инструмент Heimdall в версии для macOS (линк либо, если с этой версией возникают проблемы, то ищем более свежую тут);
- далее надо удалить полностью фирменные программки Samsung KIES и Smart Sync (если таковые имеются);
- и установить на Mac Samsung USB Driver pack для своей модели Galaxy (можно отсюда).
- По факту загрузки установки всего нужного по этому списку и удаления всего ненужного, можно приступать к главному.
Сначала качаем и устанавливаем JOdin3 на Mac (линк), а также скачиваем и складываем на видном месте файлы прошивки (.tar). Далее по порядку:
- подключаем Galaxy к Mac-у и включаем режим «Отладка по USB» (в меню разработчика);
- запускаем JOdin3 на компе (зеленая кнопка под ID:COM указывает на то, что подключение состоялось успешно):
- Как перепрошить Galaxy с Mac-а в JOdin3
- в окне JOdin3 активируем опцию PDA и указываем путь к файлу прошивки;
- перезагружаем смартфон в режим загрузки (для этого надо одновременно нажать кнопки «Питание» + «Увеличение громкости» + «Домой» или «Bixby«);
- в JOdin3 активируем опцию «Auto-Reboot«;
- запускаем процедуру установки прошивки кнопкой «Start«;
- на запрос PIT-файла жмем «Yes» и далее — «ОК» и «Start«;
- дожидаемся завершения процедуры установки (PASS) и перезагружаем Galaxy (на это потребуется еще минут 10-15).
Как-то так…
Cистемные требования: Windows 10/7/8/8.1/XP 32/64 bit, Mac OS X 10.7 и выше, Linux + Наличие Java
Русский интерфейс: Нет
Скачать:
Версия: r1142 JOdin3CASUAL-r1142-dist.zip ( 85,09 МБ )
Источник
Как прошить Samsung в Mac OS и Linux
Содержание
Если у вас есть Android смартфон или планшет от Samsung, то вы 100% знаете что прошить его можно с помощью программы Odin, но работает она только под операционной системой Windows. Командой Rootgadget была найдена JOdin3 – программа для прошивки Samsung под Linux и Mac OS.
Рекомендуем вам получение root прав в 1 клик, используя Rootkhp Pro
Раньше пользователям Макбуков и Линуксоидам приходилось в обязательном порядке искать компьютер с установленным Windows чтобы прошить Samsung на Андроиде, то есть установить новую прошивку.
Как прошить Samsung в Mac OS и Linux
Утилита Jodin, написанная на JAVA, является кроссплатформенной и позволяет прошить Samsung под MAC OS, Linux, и Windows.
Как пользоваться JOdin3 в Mac OS
Сначала вам надо скачать и установить
После запуска JOdin3 используйте его как обычную программу ODIN
Как пользоваться JOdin3 в Linux
Скачиваем и устнавливаем
После этого JOdin3 можно использовать как обычный ODIN и установить новую прошивку на Самсунг.
Источник
JOdin3: прошиваем Samsung в Mac OS и Linux
Если вы продвинутый пользователь Android, то наверно вы наверняка прошиваете Samsung в Odin, но он существует только для Windows. JOdin3 прошиваем Samsung в Mac OS и Linux!
Mac OS и Linux не для установок прошивок?
Если вы на вашем компьютере установлен Linux или вы используете MacBook или iMac на котором установлена Mac OS, то наверняка вы как и многие другие пользователи Android использующие смартфоны или планшеты компании Samsung, то наверняка вы знаете, что прошить данные устройство в данных операционных системах невозможно установить новую прошивку и приходиться искать компьютер с Windows.
Оказывается выход есть! С помощью кроссплатформенной утилиты JOdin3 которая работает на Java, можно легко прошить ваш Samsung на Linux или Mac OS.
Прошиваем Samsung в Mac OS и Linux с помощью JOdin3
Вначале рассмотрим как пользоваться программой для прошивки JOdin3 в Mac OS.
Используем JOdin3 в Mac OS
Для того чтобы использовать JOdin3 вам необходимо скачать и установить на Mac несколько утилит:
После того как вы установите Java и Heimdall на ваш Mac запустите JOdin3, а далее используете данную программу как обычный Odin для прошивки Samsung.
Используем JOdin3 в Linux
Для того чтобы использовать JOdin3 в Linux вам необходимо установить следующее:
После того как вы установите Java 8, запустите JOdin3, а далее используете данную программу как обычный Odin для прошивки Samsung.
Вот и все! Больше статей и инструкций читайте в разделе Статьи и Хаки Android. Оставайтесь вместе с сайтом Android +1, дальше будет еще интересней!
Источник
[Utility] Odin for Linux . (JOdin3 CASUAL)
Breadcrumb
Toby4213
Senior Member
I have finally found a working version of Odin for Linux!
JOdin 3 Casual powered by Heimdall
You need at least Java 8, if you don’t have it already:
To see the java version type:
iamhugo
New member
Metalhead32423
Member
Download jdoin .gz file, decompress it to your directory you want e.g /home/username/programs/jodin/
than right click on the file «JOdin3CASUAL» and open it, if you have installed java 8.
mgc123
New member
Zakku
Member
Toby4213
Senior Member
henk_j
Senior Member
HonestOtter
Senior Member
Looks like Oracle not supporting Java 9 through PPA
I downloaded files and it looks like «old» version
Can someone explain to me how to get «new» version because I am trying to install firmware on Note9
I just spent 4 hours looking through youtube and the web trying to get the «new» version of jodin.
ty for any help given.
StoneRcold
New member
Why odin needs su access
Odin needs su access because the underlying adb shell needs root to execute programs on the device itself, which Odin will need to do in order to perform the update/root procedure. I’m not an advanced android engineer, but I know linux well enough to know running arbitrary code on an attached peripheral is a security hole and should not be run unless one knows what they are doing (hence needing su, since admins are the ones that should know if a program is malicious)
phoenixbyrd
Member
Hi! Can this be installed on Arm64, specifically through a containerized instance of linux? Asking for a friend!
OK, so to explain the reasoning behind the question. I’ve been trying to explain to this dude why this won’t work but he refuses to listen because odin is in the linux repositories despite the software description saying something about MRI machines. He now finally after a couple hours understands the difference between that odin and this odin. FINALLY.
He wants to run this odin on his TabS4 through linux on dex in order to flash his note 9. I know. I tried. Maybe someone here can explain it better to him, I have him keeping an eye on these comments.
Toby4213
Senior Member
Hi! Can this be installed on Arm64, specifically through a containerized instance of linux? Asking for a friend!
OK, so to explain the reasoning behind the question. I’ve been trying to explain to this dude why this won’t work but he refuses to listen because odin is in the linux repositories despite the software description saying something about MRI machines. He now finally after a couple hours understands the difference between that odin and this odin. FINALLY.
He wants to run this odin on his TabS4 through linux on dex in order to flash his note 9. I know. I tried. Maybe someone here can explain it better to him, I have him keeping an eye on these comments.
I highly doubt that this would work for the sole reason that odin and for that matter fastboot and adb, need OS level access to the usb controller. DeX in desktop mode would take up the only available usb-c port, this would be a problem since on pc you need to connect the phone directly to the mainboard on the pc instead of using a usb hub. Without the docking station this *might* work but then again I doubt that the linux container has enought OS level permissions to use the usb port in that way. On the bright side, arm64 shouldn’t be a problem since java is also available on arm. This means that the odin .jar should be able to run and show the gui but flashing wouldn’t be possible but you could give it a try. If odin doesn’t work try fastboot on android(not in DEX), links below.
With fastboot you could flash twrp and with that could flash root and custom roms and so on. This nowadays is the preferred method anyway, since you wouldn’t depend on a usb cable to f*** up the rom flash.
xdausernl
Member
Using JOdin3 with ‘sudo’ shows ‘java.lang.OutOfMemoryError: Java heap space’
These are recommendations I’d found:
Heap size specifies the amount of dynamic memory to be made available to the JVM code.
For systems with less than 1 GB of physical memory, use a maximum heap size of 256 MB, and an initial heap size of 0 MB.
For systems with 2 GB memory, use a maximum heap size of 768 MB, and an initial heap size of 256 MB.
For larger systems (more than 2GB), use a maximum heap size of 1024 MB, and an initial heap size of 512 MB.
Is that also suitable for JOdin3?
This is the current error I’ve got:
Exception in thread «Thread-78» java.lang.OutOfMemoryError: Java heap space
at CASUAL.communicationstools.heimdall.odin.OdinFile.extractOdinContents(OdinFile.java:145)
at CASUAL.communicationstools.heimdall.odin.Odin.getHeimdallFileParametersFromOdinFile(Odin.java:50)
at com.casual_dev.jodin.JOdinController.getHeimdallCommandFromOdinPackageList(JOdinController.java:621)
at com.casual_dev.jodin.JOdinController.access$3300(JOdinController.java:54)
at com.casual_dev.jodin.JOdinController$13.run(JOdinController.java:572)
at java.lang.Thread.run(Thread.java:745)
How do I edit the ‘heap space’ settings for JOdin3 in Linux Mint 19.1?
xdausernl
Member
I have finally found a working version of Odin for Linux!
JOdin 3 Casual powered by Heimdall
You need at least Java 8, if you don’t have it already:
To see the java version type:
That’s all good and JOdin3 launched, yet while uncompressing the system.img file (about 1.5GB) the following error shows:
[VERBOSE]Heimdall Device detected!
verified file /home/location/Downloads/OudereStockRom-4.4.2kk/T210XXBNH4_T210OXABNH4_HOME/T210XXBNH4_T210OXABNH4_HOME.tar.md5
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/boot.img
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/recovery.img
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/PBL.bin
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/param.lfs
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/loke_2nd.bin
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/loke_pxa988.bin
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/system.img
Exception in thread «Thread-31» java.lang.OutOfMemoryError: Java heap space
at CASUAL.communicationstools.heimdall.odin.OdinFile.extractOdinContents(OdinFile.java:145)
at CASUAL.communicationstools.heimdall.odin.Odin.getHeimdallFileParametersFromOdinFile(Odin.java:50)
at com.casual_dev.jodin.JOdinController.getHeimdallCommandFromOdinPackageList(JOdinController.java:621)
at com.casual_dev.jodin.JOdinController.access$3300(JOdinController.java:54)
at com.casual_dev.jodin.JOdinController$13.run(JOdinController.java:572)
at java.lang.Thread.run(Thread.java:745)
Toby4213
Senior Member
These are recommendations I’d found:
Heap size specifies the amount of dynamic memory to be made available to the JVM code.
For systems with less than 1 GB of physical memory, use a maximum heap size of 256 MB, and an initial heap size of 0 MB.
For systems with 2 GB memory, use a maximum heap size of 768 MB, and an initial heap size of 256 MB.
For larger systems (more than 2GB), use a maximum heap size of 1024 MB, and an initial heap size of 512 MB.
Is that also suitable for JOdin3?
This is the current error I’ve got:
Exception in thread «Thread-78» java.lang.OutOfMemoryError: Java heap space
at CASUAL.communicationstools.heimdall.odin.OdinFile.extractOdinContents(OdinFile.java:145)
at CASUAL.communicationstools.heimdall.odin.Odin.getHeimdallFileParametersFromOdinFile(Odin.java:50)
at com.casual_dev.jodin.JOdinController.getHeimdallCommandFromOdinPackageList(JOdinController.java:621)
at com.casual_dev.jodin.JOdinController.access$3300(JOdinController.java:54)
at com.casual_dev.jodin.JOdinController$13.run(JOdinController.java:572)
at java.lang.Thread.run(Thread.java:745)
How do I edit the ‘heap space’ settings for JOdin3 in Linux Mint 19.1?
That’s all good and JOdin3 launched, yet while uncompressing the system.img file (about 1.5GB) the following error shows:
[VERBOSE]Heimdall Device detected!
verified file /home/location/Downloads/OudereStockRom-4.4.2kk/T210XXBNH4_T210OXABNH4_HOME/T210XXBNH4_T210OXABNH4_HOME.tar.md5
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/boot.img
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/recovery.img
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/PBL.bin
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/param.lfs
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/loke_2nd.bin
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/loke_pxa988.bin
decompressing file:/tmp/CASUALroot-2019-07-28-20.56.18/system.img
Exception in thread «Thread-31» java.lang.OutOfMemoryError: Java heap space
at CASUAL.communicationstools.heimdall.odin.OdinFile.extractOdinContents(OdinFile.java:145)
at CASUAL.communicationstools.heimdall.odin.Odin.getHeimdallFileParametersFromOdinFile(Odin.java:50)
at com.casual_dev.jodin.JOdinController.getHeimdallCommandFromOdinPackageList(JOdinController.java:621)
at com.casual_dev.jodin.JOdinController.access$3300(JOdinController.java:54)
at com.casual_dev.jodin.JOdinController$13.run(JOdinController.java:572)
at java.lang.Thread.run(Thread.java:745)
xdausernl
Member
Thanks Toby4213, you’re right . and I have been there but didn’t know how to use it as this is all new for me so I’m sorry for being a noob.
But I still remain unable to get the job done.
Using your line of code with or without ‘sudo’ results in this error:
Error: Unable to access jarfile JOdin3CASUAL.jar
Do I need to take some additional steps?
Toby4213
Senior Member
Thanks Toby4213, you’re right . and I have been there but didn’t know how to use it as this is all new for me so I’m sorry for being a noob.
But I still remain unable to get the job done.
Using your line of code with or without ‘sudo’ results in this error:
Error: Unable to access jarfile JOdin3CASUAL.jar
Do I need to take some additional steps?
Sorry for being rude earlier, had a bad day.
Alright so this is what you both have to do:
1. As stated in my original post make sure you have java installed.
2. Download the JOdin archive file linked in my original post
3. Unpack the archive into a folder. Linux Mint should automatically generate a folder called «JOdin3CASUAL-linux-R991»
4. navigate into this folder using the terminal(you can right click and select open «terminal in this folder» or similar) type: cd ./JOdin3CASUAL-linux-R991
5. once you are in the JOdin3CASUAL-linux-R991 folder type ls into the terminal. You should see 2 folders «app» and «runtime» and a file called «JOdin3CASUAL»
6. Type cd ./app
7. again type ls and now you should see the file «JOdin3CASUAL.jar» among another file and a folder
8. Now you can run the .jar file with the before mentioned command: java -Xms512m -Xmx2g -jar JOdin3CASUAL.jar
I hope everything is clear now. If you have any questions feel free to ask. I absolutely encourage the use of Linux and compared to ****ty Windows 10 it is an absolute dream to work and tinker with.
I would recommend that you start to learn how to use the terminal/console. It is really easy once you know what you are doing. Here is a great link to get started: http://linuxcommand.org/
xdausernl
Member
Sorry for being rude earlier, had a bad day.
Alright so this is what you both have to do:
1. As stated in my original post make sure you have java installed.
2. Download the JOdin archive file linked in my original post
3. Unpack the archive into a folder. Linux Mint should automatically generate a folder called «JOdin3CASUAL-linux-R991»
4. navigate into this folder using the terminal(you can right click and select open «terminal in this folder» or similar) type: cd ./JOdin3CASUAL-linux-R991
5. once you are in the JOdin3CASUAL-linux-R991 folder type ls into the terminal. You should see 2 folders «app» and «runtime» and a file called «JOdin3CASUAL»
6. Type cd ./app
7. again type ls and now you should see the file «JOdin3CASUAL.jar» among another file and a folder
8. Now you can run the .jar file with the before mentioned command: java -Xms512m -Xmx2g -jar JOdin3CASUAL.jar
I hope everything is clear now. If you have any questions feel free to ask. I absolutely encourage the use of Linux and compared to ****ty Windows 10 it is an absolute dream to work and tinker with.
I would recommend that you start to learn how to use the terminal/console. It is really easy once you know what you are doing. Here is a great link to get started: http://linuxcommand.org/
Toby4213
Senior Member
Alright so I finally got it working myself. I haven’t used jodin for a long time.
Ok so first make sure that you have JavaFX installed. For that just type sudo apt install openjfx in the terminal.(This might be optional for you, if you get an error containing JavaFX thats the command to fix it)
Since JOdin doesn’t quite work when launched via the .jar file the only way to get it to run is to use the binary. Thats the file in the very first folder just called «JOdin3CASUAL».
But since we are not running the jar directly we cant add -Xmx2g as a launch option. In order to get the bigger heap size type export _JAVA_OPTIONS=-Xmx2g in the terminal. You have to run this everytime you close the terminal window. In order to keep this setting permanently add this line to the .profile file in your home directory.
After that go into the folder with app, runtime and JOdin3CASUAL and type: sudo ./JOdin3CASUAL
Hope this works for you.
Cheers
xdausernl
Member
Alright so I finally got it working myself. I haven’t used jodin for a long time.
Ok so first make sure that you have JavaFX installed. For that just type sudo apt install openjfx in the terminal.(This might be optional for you, if you get an error containing JavaFX thats the command to fix it)
Since JOdin doesn’t quite work when launched via the .jar file the only way to get it to run is to use the binary. Thats the file in the very first folder just called «JOdin3CASUAL».
But since we are not running the jar directly we cant add -Xmx2g as a launch option. In order to get the bigger heap size type export _JAVA_OPTIONS=-Xmx2g in the terminal. You have to run this everytime you close the terminal window. In order to keep this setting permanently add this line to the .profile file in your home directory.
After that go into the folder with app, runtime and JOdin3CASUAL and type: sudo ./JOdin3CASUAL
Hope this works for you.
Cheers
I took all the steps you wrote down for me and I got JOdin working, finally..
But there goes something wrong still.
Because . uploading the stock ROM (1,5GB) should take a while, is not done in just a few minutes.
Uploading all the files should take at least 10 minutes to complete.
Yet, in the end, it does say reset in green though.
And I’m quite sure that something is wrong, because I didn’t see the blue status bar on the Samsung tablet during the upload process.
Uploading the extracted files seperately in Heimdall, 10 pieces out of the stock ROM, will take 10 — 15 minutes to complete and the largest of them all is the ‘system.img’ file which is 1,2 or 1,5GB in size.
With Heimdall I do see the status bar in both the program while uploading and in blue the same status bar on the Samsung tablet.
On the end of the day, I still have a rooted and faulty Android system running on that Samsung tablet.
Somehow the clean factory default is not loaded when the Samsung device reboot after all uploads with Heimdall.
Although the software uploaded is Android 4.4.2 for Tab3 7.0 8GB WiFi, with all the correct changes, date of build and country code.
Is there a final method to clean out the current faulty content of the Samsung Tab3 device?
Источник