[X]Assistant

[Mak76simka]

Description | Discussion пїЅ | Firmware [F] пїЅ | Firmware [H] пїЅ | Development / Creation and porting of firmware пїЅ

пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ/пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ пїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ/пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ "Samsung" пїЅпїЅ пїЅпїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ Exynos-3 3475 пїЅ пїЅпїЅпїЅ пїЅпїЅпїЅпїЅпїЅпїЅпїЅпїЅ download

Device or OS, firmware:Samsung Android 5.1 / 6.0 / 7.0

I propose to all those who are not indifferent to combine their knowledge in the decision to create custom firmware for our smartphone !!!

Instructions, links, manuals, etc.

• Assembly instructions for ANDROID from sources
  
• Android update-script
  
• OEM software from device manufacturers

Current firmware / port development

CWM TWRP / Root Kernels / Recovery

Tools

• Toolkit developer mods based on Android
  
• PIT Magic - Samsung PIT Creator, Editor, Analyzer
  
• Odin

Links to other sites and forums with useful information

• http: //forum.xda-devel...ung-galaxy-j1-t3444010

If there are unrealistic questions ...

Ask here:

• Telepathic communication

Post has been editedVolkoffstein - 09.02.18, 09:08

Reason for editing: added rubricator

[Joenka]

Hmm ...

The fact is that in J120F the SD mount parameters were already written in 3 different places. Which one of them actually mounted SD - you need to find out empirically.

In J120H did everything the same, but the SD was not mounted: (

To whom it is interesting to play with source codes, here is the tree of the device on which TWRP is assembled:
https://github.com/joenka/android_device_j120h

[Joenka]

Hats off to Samsung. After 5 letters, they still posted the latest kernel sources:
SM-J120F_CIS J120FXXU1APC3
It is necessary to download new and old and compare what dopili.

[Joenka]

Who will tell?
I correctly understand that after the zImage core file is obtained, you should pack it into tar (tar cvf zImage.tar zImage), then switch to bootloader mode on the phone (adb reboot-bootloader) and flash it: adb flash boot \ sdcard \ zImage.tar

[-WOLF-]

Joenka, not. Tar firmware only native software. Through heimdall, you can flash boot.img. Which is made ordinary mkbootimg from the kernel and ramdisk.

[Joenka]

-Wolf-,

Strangely, if you unpack boot.img via mkbootimg and immediately pack it back, the size of the new boot_new.img becomes larger.

If you unpack boot_new.img and pack again into boot_new2.img, the size will no longer increase.

In addition, if you unpack boot_new.img, then in the information part img_info ramdisk_offset became 0x21000000 (and was 0x11000000) and tags_offset = 0x20000100 (and was 0x10000100)!

Those. It turns out that mkbootimg repacks clumsily?

[rstp14]

Who knows, can you tell me?
So I tried to make my firmware, but Odin writes "FAIL", if it is flashed. Why it happens?

Post has been editedrstp14 - 21.07.16, 06:50

[Joenka]

rstp14,

Your question from the series: Two crocodiles fly, one is green, the other is in Africa, how old is a hedgehog?

1. Firmware on what is done: Tree, Android Sources, etc.
2. You received the firmware in what form during the assembly, in what form did you create it for Odin? Those. What composition?

Well, at least the first two points will at least understand what you are doing :)

[rstp14]

Joenka,
Just unpacked .tar.md5, changed the system.img, cutting out the Google trash and Samsung TTS from it (A program for text-to-speech that takes up a lot of space). Then he packed all the right back.

Used:
cygwin
Android Kitchen
mkyaffs2image
TAR.MD5 PACKAGER

P.S. Composition:
.tar.md5 with system.img and boot.img files

Post has been editedrstp14 - 21.07.16, 08:30

[Joenka]

rstp14,
And why did you have only system.img and boot.img? Try to leave all the files for a start and try not to change anything, just unpacked and packed back and tried to flash. Those. step by step check where the jamb.

I would do this:
1. Just unpacked, packed, tried to flash (Sewing / Not sewing)
2. Unpacked, replaced recovery.img with a custom TWRP (the one that is obviously working), packed it, trying to flash it (Sewing / Not sewing)
3. Unpacked, tried to play around with system.img: they took any file, at least the one that responds to the buttons (I wrote a little higher how to switch the Home button and App_switch), repacked, tried to flash (Sew / Not sew)
4. If all 3 points are overcome: now we clean the system.img from the "garbage". We pack, set, check.

[rstp14]

Joenka,
I'll try it now.
By the way, here's a little weird thing:
7-zip does not open the original system.img, but opens the one that is obtained after packaging using mkyaffs2image

[rstp14]

I understood. Still, the mkyaffs2image application incorrectly builds system.img.

Advise any other application that can package the files in system.img.

[-WOLF-]

rstp14,
Samsung SM-J120F / H / DS Galaxy J1 (2016) - Discussion (Post -WOLF- # 49802866)

[Joenka]

Who picked the thread sboot.bin?

1. In the firmware, sboot.bin is a separate file and weighs approximately 1.5 MB
2. Analyzing sboot.bin in IDA I had a doubt that this is a binary for ARM (I tried to analyze the whole bin for ARM code and did not meet any acquaintances for assembler and C constructions),
judging by the insides, it looks more like an image with a set of files, because at least the exif graphics (same jpg) in sboot.bin is in the form of files! However, I never found the file names themselves in the binary (as well as the address links to the beginning of the files, although I admit that without knowing the initial offset in sboot.bin it’s impossible to correctly determine the address) and something tells me that the names are in another place, namely:
3. If you unload via adb the block to which sboot.bin is written, then the file size is about 4 MB, and this is already more than 1.5 MB of sboot.bin firmware.

I'm going to try to unzip the block, removed from the phone.

I mean that removing knox from system does not save us from the very presence of many references to knox - in boot.img for example (in initialization files), as well as in the compiled TWRP (after all, it uses files from the official firmware) .rc for example, and others).

Suppose from recovery.img and boot.img I can clear out the mention of knox, but what to do with sboot.bin? And after all, it is in it that this notorious line about SEANDROID ENFORCE ... is tra-ta-ta and does not allow you so calmly to fill the phone with a new BOOT and SYSTEM, collected for example on CyanogenMod sorets ....

To whom it is interesting, join, advise, study .....

Post has been editedJoenka - 22.07.16, 11:10

[-WOLF-]

Joenka,
This is the shortest way to the brick.

[Joenka]

-Wolf-,
So no one doubts it :) But it’s interesting: :)

Why brick? without sboot.bin download mode will not work for sure, but what about recovery? Although at the entrance to the seandroid recovery ... it means sboot it also tugs :( Yes, it turns out there are some attempts for the sboot.bin firmware :) :) :) :) :)

[-WOLF-]

Joenka,
You're trying to pick an initial bootloader.

Moreover, there are all sorts of TrustZone, which will not allow you to endure all the protection.

[Joenka]

-Wolf-,
The problem is that sboot.bin turned out to be an empty 4MB file received via adb. (under the root). I hasten to suggest that since it was not possible to count, then I would not even write a note.

[Joenka]

-Wolf-,
Only part of the firmware! The block itself 4 MB weighs. And in the firmware only 1.4 MB sboot.bin.

And the fact that it is read, it is written, and so it is clear, otherwise why would this unit be on the phone at all? :) :) :)

I mean, I couldn’t read through adb, but that doesn’t mean that it’s impossible to count using other tools.


On the other hand, the TWRP is assembled and works, although it says that they say enforcing ... So, theoretically, it is also possible to assemble the firmware custom. Moreover, in sboot there are only 2 lines of Kernel Seandroid and Recovery Seandroid, i.e. if Kernel starts up, then everything else goes.

Actually, I was worried about the question of whether it is possible to sew only the system from Cyanogenmod or is it necessary to boot.img exactly the Cyan assembled too, stitch it?

Post has been editedJoenka - 22.07.16, 15:35

[-WOLF-]

Joenka @ 07/22/2016, 3:34 PM

Only part of the firmware! The block itself 4 MB weighs. And in the firmware only 1.4 MB sboot.bin

Well, you are like a little :) There just places left free for the future.

Joenka @ 07/22/2016, 3:34 PM

And the fact that it is read, it is written, and so it is clear, otherwise why would this unit be on the phone at all? :) :) :)

The prohibition of reading or writing is not obliged to prohibit the execution of the memory. A fairly frequent combination of rights is + x-r + w. In this case, the program contained in the memory can transfer control (for example, this is the firmware of some simple device). Also, no Chinese will be able to merge it from the device and analyze, there is no access to reading. But the manufacturer itself can release software updates (encrypted) that will overwrite the old firmware.

Joenka @ 07/22/2016, 3:34 PM

This does not mean that it can not be considered using other tools.

Sometimes, manufacturers are tough, but usually JTAG can do anything.

Joenka @ 07/22/2016, 3:34 PM

TWRP then assembled and works, although it says that they say enforcing

Yes, for example KingRoot repacks the kernel, so that it is not SEAndroid. And SuperSU makes it so that the bootloader does not swear. You can look at his script, by the way, everything is simple there.

Joenka @ 07/22/2016, 3:34 PM

Is it possible to sew only the system from Cyanogenmod or is it mandatory that the boot.img is Cyan assembled, too, stitched?

I'm not sure that CM will start without its kernel and ramfs. Although I see no obstacles to this
boot.img is not really a bootloader, as it seemed from the name, but KERNEL + RAMDISK.
If the SM can run on runoff cores, it should start. But here I am not an expert.

[TrOLOLO718]

Made the first outline of the device tree for assembling the CM forSM-J120F (!). I will be glad to any help.
Device tree -tyk
Kernel sources -tyk
Vendor -tyk

Post has been editedTrOLOLO718 - 05.08.16, 21:48