[Q] yaffs2 corruption (directory hardlinks pointing to parent) - Desire Q&A, Help & Troubleshooting

Hi!
I am experiencing yaffs2 filesystem corruption on the data partition of my Desire.
The errors are always quite similar: Directory entries with empty names that point to the parent directory:
Code:
# ls -lia /data/data/com.android.providers.contacts/lib/databases
total 6
2006 drwxr-xr-x 1 10006 10006 2048 Apr 8 22:30
2006 drwxr-xr-x 1 10006 10006 2048 Apr 8 22:30 .
1737 drwxr-xr-x 1 1000 1000 2048 Apr 9 07:49 ..
It looks very similar to this report.
I've already tried several ROMs (most recently AceSMod007 and RevolutioN v3.0) but both use kernel 2.6.35.14-gingercakes-0.9-avs that maybe doesn't contain the fix.
Can anyone recommend a kernel that includes this patch?

Related

Blu Studio 5.3 - Customizing GUI Audio and Boot Animation

Hi there again. I was just browsing around my Blu Studio 5.3 using adb and found these customizing gems.
Boot Animation and Audio
The Studio 5.3 apparently uses a standard bootanimation.zip and bootaudio.mp3 for its bootup. These files are found in /system/media. Going to try a custom one.
Edit: Custom boot animations work including zips using jpg files. Just make sure that you create your zip in STORAGE mode only, don't use compression or it won't work.
User Interface Sounds
The sounds for alarms, notifications and ringtones are in /system/media/audio:
Code:
/system/media/audio
drwxr-xr-x 1 0 0 2048 Jan 1 2010 .
drwxr-xr-x 1 0 0 2048 Jan 1 2010 ..
drwxr-xr-x 1 0 0 2048 Jan 1 2010 alarms
drwxr-xr-x 1 0 0 2048 Jan 1 2010 notifications
drwxr-xr-x 1 0 0 2048 Jan 1 2010 ringtones
drwxr-xr-x 1 0 0 2048 Jan 1 2010 ui
Also, apparently we can customize the audio for the UI itself. I found these files listed in /system/media/audio/ui:
Code:
/system/media/audio/ui
drwxr-xr-x 1 0 0 2048 Jan 1 2010 .
drwxr-xr-x 1 0 0 2048 Jan 1 2010 ..
-rw-r--r-- 1 0 0 3753 Aug 1 2008 Effect_Tick.ogg
-rw-r--r-- 1 0 0 6193 Aug 1 2008 KeypressDelete.ogg
-rw-r--r-- 1 0 0 7972 Aug 1 2008 KeypressReturn.ogg
-rw-r--r-- 1 0 0 7392 Aug 1 2008 KeypressSpacebar.ogg
-rw-r--r-- 1 0 0 3753 Aug 1 2008 KeypressStandard.ogg
-rw-r--r-- 1 0 0 4661 Aug 1 2008 Lock.ogg
-rw-r--r-- 1 0 0 4666 Aug 1 2008 Unlock.ogg
-rw-r--r-- 1 0 0 5582 Aug 1 2008 VideoRecord.ogg
-rw-r--r-- 1 0 0 10289 Aug 1 2008 camera_click.ogg
-rw-r--r-- 1 0 0 8484 Aug 1 2008 focused.ogg
-rw-r--r-- 1 0 0 21471 Aug 1 2008 focusing.ogg
Hi guys,
As you can see I'm new at the forum, but I have a Motorola Atrix 4G, Rooted, Unlocked BOOTLOADER, and with the NOTTACHTRIX ROM Installed with the Darks Side Kernel....
I also recently bought a Blu Studio D510, and I have an issue with play music...
I tried with several music players, and I'm still not success...
All the type of files that I tried are .mp3 and .wma
Do you know were I need to put the files in order to used the music player?
Thank You...
Ing.MiguelSR said:
Hi guys,
As you can see I'm new at the forum, but I have a Motorola Atrix 4G, Rooted, Unlocked BOOTLOADER, and with the NOTTACHTRIX ROM Installed with the Darks Side Kernel....
I also recently bought a Blu Studio D510, and I have an issue with play music...
I tried with several music players, and I'm still not success...
All the type of files that I tried are .mp3 and .wma
Do you know were I need to put the files in order to used the music player?
Thank You...
Click to expand...
Click to collapse
I've seen that you placed your question to different threads dealing with BLU Studio 5.3, but nobody has answered yet,
I cannot tell you any wise advice either, because in my phone -- and presumably in case of others' also -- the stock Music Player finds the mp3 songs in the SD card, whichever folder they are in, and plays them normally.
Your op, system must be faulty then. A hard reset (after backup) may help.
Regards,
Tibor

[Q] I want to build CM12 for my D859(ChinaTelecom)

D859 has 2sims, I can't use other g3 template, right
I already read a loi of information from cm wiki about hout to build a cm,
but I still have any clue yet,
I got D859 official rom scr code yesterday from opensource.lge.com,
I don't know how can I start for building cm,
I need some help, thank you!:laugh:
Here is the list of the files
LGD859_Lollipop_LGD859_V20a_Android_opensource/android/external: $ ls -al
drwxr-xr-x 17 578 brctl
drwxr-xr-x 21 714 dnsmasq
drwxr-xr-x 44 1496 e2fsprogs
drwxr-xr-x 7 238 ebtables
drwxr-xr-x 12 408 gcc-demangle
drwxr-xr-x 25 850 iproute2
drwxr-xr-x 21 714 iptables
drwxr-xr-x 31 1054 iputils
drwxr-xr-x 15 510 junit
drwxr-xr-x 41 1394 libexif
drwxr-xr-x 20 680 libnetfilter_conntrack
drwxr-xr-x 16 544 libnfnetlink
drwxr-xr-x 18 612 libnl
LGD859_Lollipop_LGD859_V20a_Android_opensource/android/vendor/lge: $ ls -la
drwxr-xr-x 3 102 apps
drwxr-xr-x 3 102 build
drwxr-xr-x 5 170 external
drwxr-xr-x 3 102 factory
drwxr-xr-x 4 136 frameworks
drwxr-xr-x 3 102 prebuilt
drwxr-xr-x 4 136 system
LGD859_Lollipop_LGD859_V20a_Android_opensource/kernel: $ ls -al
-rw-r--r-- 1 5935 AndroidKernel.mk
-rw-r--r-- 1 18693 COPYING
-rw-r--r-- 1 94984 CREDITS
drwxr-xr-x 237 8058 Documentation
-rw-r--r-- 1 2536 Kbuild
-rw-r--r-- 1 252 Kconfig
-rw-r--r-- 1 210475 MAINTAINERS
-rw-r--r-- 1 53855 Makefile
-rw-r--r-- 1 364155 Module.symvers
-rw-r--r-- 1 17459 README
-rw-r--r-- 1 3371 REPORTING-BUGS
drwxr-xr-x 31 1054 arch
drwxr-xr-x 38 1292 block
drwxr-xr-x 89 3026 crypto
drwxr-xr-x 112 3808 drivers
drwxr-xr-x 55 1870 firmware
drwxr-xr-x 149 5066 fs
drwxr-xr-x 26 884 include
drwxr-xr-x 14 476 init
drwxr-xr-x 17 578 ipc
drwxr-xr-x 133 4522 kernel
drwxr-xr-x 150 5100 lib
drwxr-xr-x 79 2686 mm
drwxr-xr-x 62 2108 net
drwxr-xr-x 14 476 samples
drwxr-xr-x 91 3094 scripts
drwxr-xr-x 18 612 security
drwxr-xr-x 28 952 sound
drwxr-xr-x 14 476 tools
-rw-r--r-- 1 37204 tuxera_update.sh
drwxr-xr-x 9 306 usr
drwxr-xr-x 3 102 virt
and its readme file said
1. Android build
- Download original android source code ( L 5.0 ) from source.android.com
- Untar opensource packages of LGD859_L_V20a_Android.tar.gz into downloaded android source directory
a) cat LGD859_L_V20a_Android.tar.gza* | tar zxvpf -
- And, merge the source into the android source code
- Run following scripts to build android
a) source build/envsetup.sh
b) lunch 1
c) make -j4
- When you compile the android source code, you have to add google original prebuilt source(toolchain) into the android directory.
- After build, you can find output at out/target/product/generic
2. Kernel Build
- Uncompress using following command at the android directory
tar xvzf LGD859_L_V20a_Kernel.tar.gz
- When you compile the kernel source code, you have to add google original prebuilt source(toolchain) into the android directory.
- Run following scripts to build kernel
a) cd kernel
1) D859
b) make ARCH=arm CROSS_COMPILE=../prebuilts/gcc/linux-x86/arm/arm-eabi-4.8/bin/arm-eabi- g3-ctc_cn-perf_defconfig zImage -j4
* "-j4" : The number, 4, is the number of multiple jobs to be invoked simultaneously.
- After build, you can find the build image(zImage) at arch/arm/boot
3. how to build chromium34_lge (vendor\lge\external\chromium34_lge\src),
please refer to README.txt at the folder mentioned above.

Problem with Lineageos 16.0 Build for pme with proprietary blobs

Hello,
I just want to compile Lineageos 16.0 for my old HTC10 (PME).
I followed the guide at wiki.lineageos.org/devices/pme/build
I have synced the repo without issues.
Now I have the problem to integrate the proprietary blobs into the source tree.
I have extracted the files from an available ROM.
The files are now stored under
/android/system_dump/system
Code:
[email protected]:~/android/system_dump/system$ ls -al
insgesamt 2720
drwxr-xr-x. 20 root root 4096 Jan 1 2009 .
drwxrwxr-x 6 lineageos lineageos 4096 Sep 14 22:15 ..
drwxr-xr-x. 2 root root 4096 Jan 1 2009 addon.d
drwxr-xr-x. 55 root root 4096 Jan 1 2009 app
drwxr-xr-x. 3 root 2000 8192 Jan 1 2009 bin
-rw-------. 1 root root 7409 Jan 1 2009 build.prop
-rw-r--r--. 1 root root 116235 Jan 1 2009 compatibility_matrix.xml
drwxr-xr-x. 3 root root 4096 Jan 1 2009 customize
drwxr-xr-x. 21 root root 4096 Jan 1 2009 etc
drwxr-xr-x. 2 root root 4096 Jan 1 2009 fake-libs
drwxr-xr-x. 2 root root 4096 Jan 1 2009 fake-libs64
drwxr-xr-x. 2 root root 12288 Jan 1 2009 fonts
drwxr-xr-x. 5 root root 4096 Jan 1 2009 framework
drwxr-xr-x. 6 root root 16384 Jan 1 2009 lib
drwxr-xr-x. 6 root root 16384 Jan 1 2009 lib64
drwx------. 2 root root 16384 Jan 1 2009 lost+found
drwxr-xr-x. 3 root root 4096 Jan 1 2009 media
drwxr-xr-x. 62 root root 4096 Jan 1 2009 priv-app
drwxr-xr-x. 2 root root 4096 Jan 1 2009 product
-rw-r--r--. 1 root root 2524803 Jan 1 2009 recovery-from-boot.p
drwxr-xr-x. 8 root root 4096 Jan 1 2009 usr
drwxr-xr-x. 15 root 2000 4096 Jan 1 2009 vendor
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 xbin
Code:
[email protected]:~/android/system_dump/system/vendor$ ls -al
insgesamt 124
drwxr-xr-x. 15 root 2000 4096 Jan 1 2009 .
drwxr-xr-x. 20 root root 4096 Jan 1 2009 ..
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 app
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 bin
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 bt_firmware
-rw-------. 1 root root 6135 Jan 1 2009 build.prop
-rw-------. 1 root root 145 Jan 1 2009 default.prop
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 dsp
drwxr-xr-x. 14 root 2000 4096 Jan 1 2009 etc
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 firmware
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 firmware_mnt
drwxr-xr-x. 2 root 2000 4096 Jan 1 2009 framework
drwxr-xr-x. 8 root 2000 20480 Jan 1 2009 lib
drwxr-xr-x. 7 root 2000 12288 Jan 1 2009 lib64
drwxr-xr-x. 5 root 2000 4096 Jan 1 2009 overlay
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 radio
drwxr-xr-x. 3 root 2000 4096 Jan 1 2009 rfs
-rw-r--r--. 1 root root 23343 Jan 1 2009 ueventd.rc
Which files do I need? To which location must I copy the files so breakfast recognizes them?
Extract script did not work. It's for the old CyanogenMod 14.1. I have tried to edit the path variable to my lineageos source but it is still not working.
./extract-files.sh ~/android/system_dump/
(The extract script wasn't in the source tree so I copied it from github.com/LineageOS/android_device_htc_pme
But it's from the "cm14-1" source tree. I also copied the "setup-makefiles.sh" file)
Launching "breakfast pme" fails.
Code:
[email protected]:~/android/lineage$ source build/envsetup.sh
including device/generic/car/vendorsetup.sh
including device/generic/mini-emulator-arm64/vendorsetup.sh
including device/generic/mini-emulator-armv7-a-neon/vendorsetup.sh
including device/generic/mini-emulator-x86_64/vendorsetup.sh
including device/generic/mini-emulator-x86/vendorsetup.sh
including device/generic/uml/vendorsetup.sh
including vendor/lineage/vendorsetup.sh
including sdk/bash_completion/adb.bash
[email protected]:~/android/lineage$ breakfast pme
including vendor/lineage/vendorsetup.sh
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_pme".
13:17:58 dumpvars failed with: exit status 1
Device pme not found. Attempting to retrieve device repository from LineageOS (Github github.com/LineageOS).
Found repository: android_device_htc_pme
Default revision: lineage-16.0
Checking branch info
Default revision lineage-16.0 not found in android_device_htc_pme. Bailing.
Branches found:
cm-13.0
cm-14.1
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_pme".
13:18:00 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "lineage_pme".
13:18:01 dumpvars failed with: exit status 1
** Don't have a product spec for: 'lineage_pme'
** Do you have the right repo manifest?
What must I do that the proprietary blobs/ firmware filles are working with the "breakfast pme" command?
I would appreciate any help so I could start compiling lineageos 16.0 for my HTC10.
Thank you in advance.
regards
starbuck28

Rooting Samsung Galaxy Watch Active

Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
adfree said:
Depend what you expect...
Factory/Service Firmware called Combination Firmware is rooted...
I am using Combination Firmware as base... as Engineer sboot.bin (Bootloader) Engineer Kernel is inside...
From Stock Firmware only rootfs.img is modified... to have su Binary...
Problem...
SM-R500 nor other Galaxy variant tested...
Sugestion for you...
Flash Combination Firmware to see what kind of Root you can expect...
I could help you to modify Firmware Files... but OWN RISK...
Best Regards
Click to expand...
Click to collapse
I don’t mind to give it a try. Please share what you have?
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
adfree said:
Sorry.
I waste tooo much time with Tizen...
I have limited time... and energy...
The long way is here:
https://forum.xda-developers.com/smartwatch/gear-s3/gear-s3-android-wear-port-wip-t3584588
Somewhere inside this Thread are infos how to play with rootfs.img...
The "faster" way for you or both of us... is.
Flash Combination Firmware for SM-R500 to see if this is what you want...
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
COMBINATION-FT40_R500XXU1ASG1.tar.md5
These 2 FT40 seems leaked and available... maybe somewhere in public...
I am too lazy to search for you.
TRy hard enough and in 2 days you can pm me... if you not able to find it...
Maybe I will upload for you...
But again.
What kind of magic you expect from Rooting of your SM-R500?
So I can make decission to help you... or maybe waste my time with other things.
Best Regards
Edit 1.
Code:
COMBINATION-FT40_R500XXU1[B]ASA5[/B].tar.md5
ASA5 I have on my HDD... I could upload...
Edit 2.
Uupsi.. I have both FT40...
Still no idea if somewhere public Link available...
Edit 3...
Lesson 1.
https://forum.xda-developers.com/showpost.php?p=73503787&postcount=150
You "need" netOdin Tool for Flashing Firmware...
I will upload for you:
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
Need some time for upload...
Plese remember:
Own risk!
Best Regards
---------- Post added at 04:28 AM ---------- Previous post was at 03:35 AM ----------
Code:
COMBINATION-FT40_R500XXU1ASA5.tar.md5
https://www.file-upload.net/download-13786815/COMBINATION-FT40_R500XXU1ASA5.tar.md5.7z.html
Own risk!
Best Regards
Click to expand...
Click to collapse
Sorry for the late reply and thank you adfree for your effort, but I already have and tested the combination firmware and It is not what I'm looking for! Now I'm trying to figure the pinout so I can connect it directly.
Done first attempt with DSL1 Firmware...
Waiting for feedback...
Meanwhile...
A
To enable Root access... SDB Tool required...
Code:
sdb root on
A.1
To enable su from Shell...
Additional steps required...
Code:
sdb root on
sdb shell
mount -vo remount,rw /
chmod -v +sx /usr/bin
Code:
sdb root off
Then you can su from shell...
Code:
su
then it asks for password... password is:
Code:
tizen
B
To check if you can now play with rootfs.img "on the fly"...
Code:
sdb root on
Or you have enbled the other way...
Code:
sdb shell
Code:
mount -vo remount,rw /
Now you can for instance delete poweron poweroff Animation... you can do more but this is safe... nothing will explode.
Code:
sdb root on
Switched to 'root' account mode
sdb shell
sh-3.2# cd /usr/share/edje
sh-3.2# ls -a1l
total 1280
drwxr-xr-x 5 root root 4096 Jun 27 2019 .
drwxr-xr-x 131 root root 4096 Jun 27 2019 ..
-rw-r--r-- 1 root root 322470 Apr 19 2019 360x360_PowerOff.edj
-rw-r--r-- 1 root root 227171 Apr 19 2019 360x360_PowerOn.edj
-rw-r--r-- 1 root root 6065 Apr 19 2019 csc-ani.edj
-rw-r--r-- 1 root root 6221 Apr 19 2019 factory-reset-util.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 images
drwxr-xr-x 2 root root 4096 Jun 27 2019 include
-rw-r--r-- 1 root root 295340 Apr 19 2019 poweroff.edj
-rw-r--r-- 1 root root 411726 Apr 19 2019 poweron.edj
-rw-r--r-- 1 root root 5656 Apr 19 2019 voice-control-elm.edj
drwxr-xr-x 2 root root 4096 Jun 27 2019 xwalk
Code:
rm poweron.edj
and/or
Code:
rm poweroff.edj
Be carefully what you remove or replace...
Best Regards
Seems to work... DSL1 rooted... tested in coop with:
Code:
COMBINATION-FT40_R500XXU1[B]ASL2[/B]
For some dump action I need some infos about partition layout...
Code:
[B]cat /proc/partitions[/B]
Example output from SM-Z130H and SM-R760...
Code:
major minor #blocks name
7 0 10052 loop0
7 1 17408 loop1
254 0 146152 zram0
179 0 3817472 mmcblk0
179 1 1024 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1024 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 1024 mmcblk0p6
179 7 1024 mmcblk0p7
179 8 1024 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 9216 mmcblk0p10
179 11 2048 mmcblk0p11
179 12 2048 mmcblk0p12
179 13 2048 mmcblk0p13
179 14 8192 mmcblk0p14
179 15 8192 mmcblk0p15
179 16 8192 mmcblk0p16
179 17 8192 mmcblk0p17
179 18 8192 mmcblk0p18
179 19 4096 mmcblk0p19
179 20 2048 mmcblk0p20
179 21 32768 mmcblk0p21
179 22 131072 mmcblk0p22
179 23 2641920 mmcblk0p23
179 24 917504 mmcblk0p24
179 96 512 mmcblk0rpmb
179 64 4096 mmcblk0boot1
179 32 4096 mmcblk0boot0
179 128 7749632 mmcblk1
179 129 7748608 mmcblk1p1
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 boot -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cm -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 15 Apr 6 09:52 cpnvcore -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Apr 6 09:52 csa -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Apr 6 09:52 csc -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 16 Apr 6 09:52 module -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 15 Apr 6 09:52 param -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk1 -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk2 -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 15 Apr 6 09:52 recovery -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 steady -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Apr 6 09:52 system-data -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 15 Apr 6 09:52 tup -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Apr 6 09:52 user -> ../../mmcblk0p13
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 16 Apr 6 09:52 modules -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 10 Apr 6 09:52 ramdisk -> ../../ram0
lrwxrwxrwx 1 root root 15 Apr 6 09:52 ramdisk-recovery -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Apr 6 09:52 rootfs -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 16 Apr 6 09:52 tizen -> ../../mmcblk0p13
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 320K 1 loop /opt/share/zoneinfo
loop1 7:1 0 13.6M 1 loop /usr/share/locale
zram0 254:0 0 279.3M 0 disk [SWAP]
mmcblk0rpmb 179:24 0 512K 0 disk
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 32M 0 part
|-mmcblk0p2 179:2 0 8M 0 part /csa
|-mmcblk0p3 179:3 0 2M 0 part
|-mmcblk0p4 179:4 0 20M 0 part
|-mmcblk0p5 179:5 0 8M 0 part
|-mmcblk0p6 179:6 0 8M 0 part
|-mmcblk0p7 179:7 0 3M 0 part
|-mmcblk0p8 259:0 0 16M 0 part
|-mmcblk0p9 259:1 0 16M 0 part
|-mmcblk0p10 259:2 0 16M 0 part /usr/lib/modules
|-mmcblk0p11 259:3 0 190M 0 part /opt/system/csc
|-mmcblk0p12 259:4 0 158M 0 part /opt
|-mmcblk0p13 259:5 0 1.9G 0 part /opt/usr
|-mmcblk0p14 259:6 0 1.3G 0 part
| `-rootfs 253:0 0 1.2G 1 crypt /
`-mmcblk0p15 259:7 0 256K 0 part
Thanx in advance.
Best Regards
Here the answer.
Thanx. :good:
SM-R500 DSL1
Code:
sh-3.2# cat /proc/partitions
major minor #blocks name
1 0 20480 ram0
1 1 20480 ram1
7 0 34240 loop0
7 1 384 loop1
254 0 284980 zram0
179 0 3817472 mmcblk0
179 1 8192 mmcblk0p1
179 2 2048 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 512 mmcblk0p4
179 5 512 mmcblk0p5
179 6 28160 mmcblk0p6
179 7 20480 mmcblk0p7
259 0 8192 mmcblk0p8
259 1 2048 mmcblk0p9
259 2 6144 mmcblk0p10
259 3 3072 mmcblk0p11
259 4 18432 mmcblk0p12
259 5 18432 mmcblk0p13
259 6 10240 mmcblk0p14
259 7 4096 mmcblk0p15
259 8 194560 mmcblk0p16
259 9 172032 mmcblk0p17
259 10 1873408 mmcblk0p18
259 11 1439744 mmcblk0p19
259 12 256 mmcblk0p20
179 24 512 mmcblk0rpmb
179 16 4096 mmcblk0boot1
179 8 4096 mmcblk0boot0
Code:
sh-3.2# ls -l /dev/disk/by-partlabel
total 0
lrwxrwxrwx 1 root root 16 Feb 8 11:11 afpc -> ../../mmcblk0p15
lrwxrwxrwx 1 root root 16 Feb 8 11:11 boot -> ../../mmcblk0p12
lrwxrwxrwx 1 root root 16 Feb 8 11:11 cm -> ../../mmcblk0p11
lrwxrwxrwx 1 root root 15 Feb 8 11:11 csa -> ../../mmcblk0p1
lrwxrwxrwx 1 root root 16 Feb 8 11:11 csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 15 Feb 8 11:11 module -> ../../mmcblk0p5
lrwxrwxrwx 1 root root 16 Feb 8 11:11 nad_fw -> ../../mmcblk0p14
lrwxrwxrwx 1 root root 15 Feb 8 11:11 nad_refer -> ../../mmcblk0p3
lrwxrwxrwx 1 root root 15 Feb 8 11:11 param -> ../../mmcblk0p9
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk1 -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk2 -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 recovery -> ../../mmcblk0p13
lrwxrwxrwx 1 root root 16 Feb 8 11:11 rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 15 Feb 8 11:11 smsn -> ../../mmcblk0p4
lrwxrwxrwx 1 root root 16 Feb 8 11:11 steady -> ../../mmcblk0p20
lrwxrwxrwx 1 root root 16 Feb 8 11:11 system-data -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tup -> ../../mmcblk0p6
lrwxrwxrwx 1 root root 15 Feb 8 11:11 tyd -> ../../mmcblk0p2
lrwxrwxrwx 1 root root 16 Feb 8 11:11 up_param -> ../../mmcblk0p10
lrwxrwxrwx 1 root root 16 Feb 8 11:11 user -> ../../mmcblk0p18
Code:
sh-3.2# ls -l /dev/disk/by-label
total 0
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk -> ../../mmcblk0p8
lrwxrwxrwx 1 root root 15 Feb 8 11:11 ramdisk-recovery -> ../../mmcblk0p7
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-csc -> ../../mmcblk0p16
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-rootfs -> ../../mmcblk0p19
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-system-da -> ../../mmcblk0p17
lrwxrwxrwx 1 root root 16 Feb 8 11:11 tizen-user -> ../../mmcblk0p18
Code:
sh-3.2# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 33.4M 1 loop /usr/share/locale
loop1 7:1 0 384K 1 loop /opt/share/zoneinfo
mmcblk0 179:0 0 3.7G 0 disk
|-mmcblk0p1 179:1 0 8M 0 part /csa
|-mmcblk0p2 179:2 0 2M 0 part
|-mmcblk0p3 179:3 0 1M 0 part
|-mmcblk0p4 179:4 0 512K 0 part
|-mmcblk0p5 179:5 0 512K 0 part
|-mmcblk0p6 179:6 0 27.5M 0 part
|-mmcblk0p7 179:7 0 20M 0 part
|-mmcblk0p8 259:0 0 8M 0 part
|-mmcblk0p9 259:1 0 2M 0 part
|-mmcblk0p10 259:2 0 6M 0 part
|-mmcblk0p11 259:3 0 3M 0 part
|-mmcblk0p12 259:4 0 18M 0 part
|-mmcblk0p13 259:5 0 18M 0 part
|-mmcblk0p14 259:6 0 10M 0 part
|-mmcblk0p15 259:7 0 4M 0 part
|-mmcblk0p16 259:8 0 190M 0 part /opt/system/csc
|-mmcblk0p17 259:9 0 168M 0 part /opt
|-mmcblk0p18 259:10 0 1.8G 0 part /opt/usr
|-mmcblk0p19 259:11 0 1.4G 0 part /
`-mmcblk0p20 259:12 0 256K 0 part
mmcblk0boot0 179:8 0 4M 1 disk
mmcblk0boot1 179:16 0 4M 1 disk
mmcblk0rpmb 179:24 0 512K 0 disk
zram0 254:0 0 278.3M 0 disk [SWAP]
Code:
mmcblk0p1 CSA
mmcblk0p2 TYD
mmcblk0p3 NAD_REFER
mmcblk0p4 SMSN
mmcblk0p5 MODULE
mmcblk0p6 TUP
mmcblk0p7 RAMDISK-RECOVERY
mmcblk0p8 RAMDISK
mmcblk0p9 PARAM
mmcblk0p10 UP_PARAM
mmcblk0p11 CM
mmcblk0p12 BOOT
mmcblk0p13 RECOVERY
mmcblk0p14 NAD_FW
mmcblk0p15 AFPC
mmcblk0p16 CSC
mmcblk0p17 SYSTEM-DATA
mmcblk0p18 USR
mmcblk0p19 ROOTFS
mmcblk0p20 STEADY
mmcblk0boot0 BOOT0
mmcblk0boot1 BOOT1
mmcblk0rpmb RPMB --->protected... NOT readable
mmcblk0 Full 4 GB eMMC
Best Regards
SM-R500 DSL1 summary for dd action... dump partitions... :angel:
We have 20 partitions p1 - p20
+ 3 additional
We are writing to USR partition p18... remember limited space... ca, 1500 MB free
Code:
dd if=/dev/mmcblk0boot0 of=/opt/usr/media/bootloader0.bin
dd if=/dev/mmcblk0boot1 of=/opt/usr/media/bootloader1.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0rpmb of=/opt/usr/media/rpmb.bin[/B][/COLOR]
dd if=/dev/mmcblk0p1 of=/opt/usr/media/csa.bin
dd if=/dev/mmcblk0p2 of=/opt/usr/media/tyd.bin
dd if=/dev/mmcblk0p3 of=/opt/usr/media/nad_refer.bin
dd if=/dev/mmcblk0p4 of=/opt/usr/media/smsn.bin
dd if=/dev/mmcblk0p5 of=/opt/usr/media/module.bin
dd if=/dev/mmcblk0p6 of=/opt/usr/media/tup.bin
dd if=/dev/mmcblk0p7 of=/opt/usr/media/ramdisk-recovery.bin
dd if=/dev/mmcblk0p8 of=/opt/usr/media/ramdisk.bin
dd if=/dev/mmcblk0p9 of=/opt/usr/media/param.bin
dd if=/dev/mmcblk0p10 of=/opt/usr/media/up_param.bin
dd if=/dev/mmcblk0p11 of=/opt/usr/media/cm.bin
dd if=/dev/mmcblk0p12 of=/opt/usr/media/boot.bin
dd if=/dev/mmcblk0p13 of=/opt/usr/media/recovery.bin
dd if=/dev/mmcblk0p14 of=/opt/usr/media/nad_fw.bin
dd if=/dev/mmcblk0p15 of=/opt/usr/media/afpc.bin
dd if=/dev/mmcblk0p16 of=/opt/usr/media/csc.bin
dd if=/dev/mmcblk0p17 of=/opt/usr/media/system-data.bin
[COLOR="Red"][B]dd if=/dev/mmcblk0p18 of=/opt/usr/media/usr.bin[/B][/COLOR]
[COLOR="Red"][B]dd if=/dev/mmcblk0p19 of=/opt/usr/media/rootfs.bin[/B][/COLOR]
dd if=/dev/mmcblk0p20 of=/opt/usr/media/steady.bin
Red marked Commands...
rootfs to dump is not really usefull... remember free space...
usr is written to usr partition... so never possible to dump in 1 step...
rpmb read protected,,, found no way on Wearables...
To pull all files from Media folder...
Code:
sdb pull /opt/usr/media/
Or pull file by file with filename... example:
Code:
sdb pull /opt/usr/media/[B]csa.bin[/B]
Best Regards
To dump "whole" eMMC...
Limitation we have only maximum 1,8 GB... so we have tiny problem to put whole 4 GB...
To check free space...
Example taken from my SM-R760...
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 85M 51M 63% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.6M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/apps
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 120M 1.8G 7% /opt/usr/media
sh-3.2# df -a
Filesystem 1K-blocks Used Available Use% Mounted on
rootfs 1298824 1064480 204612 84% /
devtmpfs 347224 0 347224 0% /dev
none 0 0 0 - /proc
sysfs 0 0 0 - /sys
/dev/mmcblk0p14 1298824 1064480 204612 84% /
/dev/mmcblk0p12 141376 86868 51276 63% /opt
/dev/mmcblk0p10 13847 253 13287 2% /usr/lib/modules
securityfs 0 0 0 - /sys/kernel/security
smackfs 0 0 0 - /sys/fs/smackfs
tmpfs 359712 24 359688 1% /dev/shm
devpts 0 0 0 - /dev/pts
tmpfs 359712 2628 357084 1% /run
tmpfs 359712 0 359712 0% /sys/fs/cgroup
cgroup 0 0 0 - /sys/fs/cgroup/systemd
pstore 0 0 0 - /sys/fs/pstore
cgroup 0 0 0 - /sys/fs/cgroup/net_cls
cgroup 0 0 0 - /sys/fs/cgroup/cpu,cpuacct
cgroup 0 0 0 - /sys/fs/cgroup/freezer
cgroup 0 0 0 - /sys/fs/cgroup/memory
debugfs 0 0 0 - /sys/kernel/debug
tmpfs 359712 60 359652 1% /tmp
configfs 0 0 0 - /sys/kernel/config
/dev/loop0 384 384 0 100% /opt/share/zoneinfo
/dev/loop1 34176 34176 0 100% /usr/share/locale
/dev/mmcblk0p11 187373 102462 81020 56% /opt/system/csc
/dev/mmcblk0p2 6907 1218 5117 20% /csa
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr
tmpfs 71940 80 71860 1% /run/user/5001
tmpfs 71940 0 71940 0% /run/user_ext/5001
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/apps
vip_cgroup 0 0 0 - /sys/fs/cgroup/vip
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/home/owner/media
/dev/mmcblk0p13 1936976 122612 1797980 7% /opt/usr/media
Taken from here:
https://opensource.com/article/18/7/how-check-free-disk-space-linux
First attempt:
Code:
dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd stopps if usr partition is full...
Could lead to sideeffect...
But could be enough to pull result...
Code:
sh-3.2# dd if=/dev/mmcblk0 of=/opt/usr/media/full4GB_eMMC.bin
dd: writing to `/opt/usr/media/full4GB_eMMC.bin': [COLOR="Red"][B]No space left on device[/B][/COLOR]
3596569+0 records in
3596568+0 records out
1841442816 bytes (1.8 GB) copied, 151.265 s, 12.2 MB/s
Code:
sh-3.2# df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 1.3G 1.1G 200M 84% /
devtmpfs 340M 0 340M 0% /dev
/dev/mmcblk0p14 1.3G 1.1G 200M 84% /
/dev/mmcblk0p12 139M 83M 53M 61% /opt
/dev/mmcblk0p10 14M 253K 13M 2% /usr/lib/modules
tmpfs 352M 24K 352M 1% /dev/shm
tmpfs 352M 2.5M 349M 1% /run
tmpfs 352M 0 352M 0% /sys/fs/cgroup
tmpfs 352M 60K 352M 1% /tmp
/dev/loop0 384K 384K 0 100% /opt/share/zoneinfo
/dev/loop1 34M 34M 0 100% /usr/share/locale
/dev/mmcblk0p11 183M 101M 80M 56% /opt/system/csc
/dev/mmcblk0p2 6.8M 1.2M 5.0M 20% /csa
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr[/B][/COLOR]
tmpfs 71M 80K 71M 1% /run/user/5001
tmpfs 71M 0 71M 0% /run/user_ext/5001
[COLOR="Red"][B]/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/apps
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/home/owner/media
/dev/mmcblk0p13 1.9G 1.9G 0 100% /opt/usr/media[/B][/COLOR]
Code:
sdb pull /opt/usr/media/full4GB_eMMC.bin
pulled full4GB_eMMC.bin 100% 1756MB
1 file(s) pulled. 0 file(s) skipped.
/opt/usr/media/full4GB_eMMC.bin 552 KB/s (1841442816 bytes in 3255.896s)
Pull seems 1 hour...
Best Regards
Code:
sh-3.2# dd if=/dev/mmcblk0 | gzip > /opt/usr/media/full4GB_eMMC.bin.gz
gzip: stdout: No space left on device
Creates corrupt/unfinished archive file... but have 2200 MB inside... few more as uncompressed...
Better we split... and find other way for user partition...
.
.
.
Best Regards
Maybe found something...
Code:
sdb shell dd if=/dev/mmcblk0boot1>testme11.bin
sdb shell dd if=/dev/mmcblk0boot0>testme11more.bin
sdb shell dd if=/dev/mmcblk0rpmb>testme11moreAA.bin
Now need more time for next attempt...
Code:
sdb shell dd if=/dev/mmcblk0>FULLeMMCoverSDB_WiFi.bin
4 GB !
IMHO 1 - 2 hours...
Best Regards
Rooted SM-R500 DSL1 Firmware is here:
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
If Questions... better ask BEFORE...
Best Regards
Hmmm... I don't know why...
But if I direct dump to PC... then additional crap is written...
2 Bytes...
Code:
0D0D
I have Tizen handset... SM-Z130H... with Tizen 2.4...
Here this work as it seems, tested with Command:
Code:
sdb shell dd if=/dev/mmcblk0boot1>Z1_boot1.bin
This partition is ever empty... contains only 00... so IMHO good reference...
But my Z1 is connected via USB cable...
No idea if 0D0D cames because some TCP problem...
Best Regards
With SM-R760 we have luck...
Combination Firmware not mandatory for Tizen 4 Root...
Only RAMDISK taken from Combination Firmware...
Maybe this is also working for SM-R500... need to be tested.
Attached is ramdisk.img from FT40 ASL2 for SM-R500...
Best Regards
I0T said:
Hey guys!
I'm searching around and I couldn't find a way to root SM-R500 Samsung Galaxy Watch Active (Tizen 4.0.0.3). I found a lot of firmware on different websites, but I couldn't find a rooted one. Any suggestions ...
Thanks
Click to expand...
Click to collapse
Hey there! Could you finally root the SM-R500? Is it still alive? Have the same model here... I used to root all Samsung I had but this is my very first watch so I do not want to mess it yet without anyone proofs
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
adfree said:
Your Firmware Version?
I have only rooted DSL1 for SM-R500...
Best Regards
Click to expand...
Click to collapse
Hi adfree, It seems DSL1, lastest Samsung update.. I have read about combination firmwares etc.. but not tired anything without being sure cause is the most expensive watch i ever bought..
The most combinations firms seems for others than R500, I don't know either about knox on watch if will be tripped too and will left samsung pay useless or it works different than phones..
Yesterday I downloaded all tizen SDK tools etc... and sideloaded tpk apps to watch, they install but could not run them propperly.. but I guess all this is about to test yet as it is a "new watch" ...sorry my ignorance but I come from a LG watch from 2015 omg I had to update myself... xD
Thank you and have a nice day !
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
adfree said:
@Albayeah
Sorry.
In main I am talking with my self... about Rooting...
No idea why user not confirm in public...
I know he used the old method with Combination Firmware first... then my rooted rootfs,img...
The new way... is to flash only RAMDISK from Combination Firmware, then my rooted files.
So Round 1:
with netOdin
https://forum.xda-developers.com/showpost.php?p=81799723&postcount=15
Round 2.
with netOdin
IGNORE the Combination Firmware files
https://forum.xda-developers.com/showpost.php?p=81762345&postcount=838
Only this:
https://www.file-upload.net/download-13891175/2020_DSL1_smR500_ROOT_v1.7z.html
Own Risk!
But I am 99,9 % sure this is working. :angel:
Best Regards
Click to expand...
Click to collapse
Many thanks! I am going to save your files by the moment because I am still afraid of messing something definetly on the watch with no reverse..
Maybe I have to do more research..
I hope I dont bother you with my questions but if you already rooted.. could you use samsung apps as usual..? Like samsung health, samsung pay.. won't prompt a security message or disable any functions, any apps..?
Sorry cause i am kinda confused with that details..
On phone I use Samsung apps hiding with magisk etc... cause it is rooted but it is Android, but what about watch with tizen and no magisk..? Will disable the apps just like in the phone, or is it knox unrecoverable? :silly:
Sorry for my inexperience maybe all this sounded silly to you XDD
Best wishes to all on these hard times :good:

where to begin to port to a newer Lineage Release?

Hey Guys,
i wanted to check what to do, for trying to port a newer Lineage release to this device.
Any hints where to begin?
I luckily compiled the 14.1 branch yesterday.
But what to do next?
Regards for the hints
I've been investigating this recently as well. I started looking at LineageOS 16.0 branch and the Exynos5420 kernal/rom code on github ("https://github.com/exynos5420"), as I am running a build on the tablet from here:-
"https://download.exynos5420.com/LineageOS-14.1-Vanilla/chagalllte/"
BTW, I'm a late/newcomer to android rom development, and I may be off track/incorrect anyways.
I've attempted building branch lineage16.0 with Exynos5420 and currently throws this error :-
bionic/libc/include/bits/fortify/fcntl.h:63:26: error: use of undeclared identifier 'O_TMPFILE'
__clang_error_if(__open_modes_useful(flags), "'open' " __open_too_few_args_error)
The bionic libc wants a definition for O_TMPFILE , I think is to be resolved from the
kernel headers under the kernel device tree at:- kernel/samsung/exynos5420/include/asm-generic/fcntl.h
Of course there is no definition of 'O_TMPFILE' in this header file.
Looks like a later linux kernel version (or patches) to the Exynos5420 kernel code/device is required with headers defining O_TMPFILE.
All I can suggest for porting a newer lineageOs is, get started experimenting/building.
Find/pick up a later device kernel source code tree
For me there is alot to learn and few up-to-date guides
Good luck
bluess57 said:
I've been investigating this recently as well. I started looking at LineageOS 16.0 branch and the Exynos5420 kernal/rom code on github ("https://github.com/exynos5420"), as I am running a build on the tablet from here:-
"https://download.exynos5420.com/LineageOS-14.1-Vanilla/chagalllte/"
BTW, I'm a late/newcomer to android rom development, and I may be off track/incorrect anyways.
I've attempted building branch lineage16.0 with Exynos5420 and currently throws this error :-
bionic/libc/include/bits/fortify/fcntl.h:63:26: error: use of undeclared identifier 'O_TMPFILE'
__clang_error_if(__open_modes_useful(flags), "'open' " __open_too_few_args_error)
The bionic libc wants a definition for O_TMPFILE , I think is to be resolved from the
kernel headers under the kernel device tree at:- kernel/samsung/exynos5420/include/asm-generic/fcntl.h
Of course there is no definition of 'O_TMPFILE' in this header file.
Looks like a later linux kernel version (or patches) to the Exynos5420 kernel code/device is required with headers defining O_TMPFILE.
All I can suggest for porting a newer lineageOs is, get started experimenting/building.
Find/pick up a later device kernel source code tree
For me there is alot to learn and few up-to-date guides
Good luck
Click to expand...
Click to collapse
Add the following lines in the header file kernel/samsung/exynos5420/include/asm-generic/fcntl.h https://github.com/alexenferman/and...mmit/e97a38cefdb63305f85139c4409a597759388081 and you are good to go.
I tried compiling 16.0 for chagallwifi (T800) over the fall and ran into a number of compiler problems, but when I finally got it to compile, the resulting image wouldn't boot. A lot of those problems have now been fixed in gerrit.
I also tried 15.1 last week, but ran into a number of compile problems. Then I noticed a lot of activity on https://github.com/exynos5420 and https://review.exynos5420.com/ wrt to 16.0 so I tried again yesterday and today and I had to make 2 modifications for it to compile, but the result is an image that won't boot. The recovery image won't boot meaning somethings wrong with the boot/kernel stage.
Hopefully the team will make more modifications over the holidays and I will have a bootable 16.0 image?
retiredtab said:
I tried compiling 16.0 for chagallwifi (T800) over the fall and ran into a number of compiler problems, but when I finally got it to compile, the resulting image wouldn't boot. A lot of those problems have now been fixed in gerrit.
I also tried 15.1 last week, but ran into a number of compile problems. Then I noticed a lot of activity on https://github.com/exynos5420 and https://review.exynos5420.com/ wrt to 16.0 so I tried again yesterday and today and I had to make 2 modifications for it to compile, but the result is an image that won't boot. The recovery image won't boot meaning somethings wrong with the boot/kernel stage.
Hopefully the team will make more modifications over the holidays and I will have a bootable 16.0 image?
Click to expand...
Click to collapse
Unpack the recovery and show me the files inside. You might be missing the init files on the recovery, like I did with the Snapdragon Galaxy S3
alexenferman said:
Unpack the recovery and show me the files inside.
Click to expand...
Click to collapse
Code:
$ abootimg -x recovery.img
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
$ ls -al
total 16000
drwxrwxr-x 2 l l 4096 Dec 22 21:11 .
drwxrwxr-x 14 l l 4096 Dec 22 21:11 ..
-rw-rw-r-- 1 l l 167 Dec 22 21:11 bootimg.cfg
-rw-rw-r-- 1 l l 3336396 Dec 22 21:11 initrd.img
-rw-rw-r-- 1 l l 8183825 Dec 22 21:11 recovery.img
-rw-rw-r-- 1 l l 4842048 Dec 22 21:11 zImage
$ cat bootimg.cfg
bootsize = 0x7ce011
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name =
cmdline = buildvariant=eng
retiredtab said:
Code:
$ abootimg -x recovery.img
writing boot image config in bootimg.cfg
extracting kernel in zImage
extracting ramdisk in initrd.img
$ ls -al
total 16000
drwxrwxr-x 2 l l 4096 Dec 22 21:11 .
drwxrwxr-x 14 l l 4096 Dec 22 21:11 ..
-rw-rw-r-- 1 l l 167 Dec 22 21:11 bootimg.cfg
-rw-rw-r-- 1 l l 3336396 Dec 22 21:11 initrd.img
-rw-rw-r-- 1 l l 8183825 Dec 22 21:11 recovery.img
-rw-rw-r-- 1 l l 4842048 Dec 22 21:11 zImage
$ cat bootimg.cfg
bootsize = 0x7ce011
pagesize = 0x800
kerneladdr = 0x10008000
ramdiskaddr = 0x11000000
secondaddr = 0x10f00000
tagsaddr = 0x10000100
name =
cmdline = buildvariant=eng
Click to expand...
Click to collapse
Sorry I meant Ramdisk of the recovery
$ ls -al 16/out/target/product/chagallwifi/ram*
-rw-rw-r-- 1 l l 1766995 Dec 22 17:49 ramdisk.img
-rw-rw-r-- 1 l l 9298176 Dec 22 17:49 ramdisk-recovery.cpio
-rw-rw-r-- 1 l l 3336396 Dec 22 17:49 ramdisk-recovery.img
/media/l/16/16/out/target/product/chagallwifi$
Code:
$ ./unpack_ramdisk ramdisk.img
6493 blocks
$ cd ramdisk/
$ ls -al
total 2248
drwxrwxr-x 16 l l 4096 Dec 22 22:01 .
drwxrwxr-x 3 l l 4096 Dec 22 22:01 ..
drwxr-xr-x 2 l l 4096 Dec 22 22:01 acct
lrwxrwxrwx 1 l l 11 Dec 22 22:01 bin -> /system/bin
lrwxrwxrwx 1 l l 50 Dec 22 22:01 bugreports -> /data/user_de/0/com.android.shell/files/bugreports
drwxrwx--- 2 l l 4096 Dec 22 22:01 cache
lrwxrwxrwx 1 l l 13 Dec 22 22:01 charger -> /sbin/charger
dr-xr-xr-x 2 l l 4096 Dec 22 22:01 config
lrwxrwxrwx 1 l l 17 Dec 22 22:01 d -> /sys/kernel/debug
drwxrwx--x 2 l l 4096 Dec 22 22:01 data
-rw------- 1 l l 1334 Dec 22 22:01 default.prop
drwxr-xr-x 2 l l 4096 Dec 22 22:01 dev
lrwxrwxrwx 1 l l 11 Dec 22 22:01 etc -> /system/etc
-rw-r----- 1 l l 2313 Dec 22 22:01 fstab.universal5420
-rwxr-x--- 1 l l 1637644 Dec 22 22:01 init
-rwxr-x--- 1 l l 1154 Dec 22 22:01 init.environ.rc
-rwxr-x--- 1 l l 29431 Dec 22 22:01 init.rc
-rwxr-x--- 1 l l 1524 Dec 22 22:01 init.samsung.rc
-rwxr-x--- 1 l l 2458 Dec 22 22:01 init.target.rc
-rwxr-x--- 1 l l 26408 Dec 22 22:01 init.universal5420.rc
-rwxr-x--- 1 l l 8107 Dec 22 22:01 init.universal5420.usb.rc
-rwxr-x--- 1 l l 2399 Dec 22 22:01 init.universal5420.wifi.rc
-rwxr-x--- 1 l l 7690 Dec 22 22:01 init.usb.configfs.rc
-rwxr-x--- 1 l l 5646 Dec 22 22:01 init.usb.rc
-rwxr-x--- 1 l l 511 Dec 22 22:01 init.zygote32.rc
drwxr-xr-x 2 l l 4096 Dec 22 22:01 mnt
drwxr-xr-x 2 l l 4096 Dec 22 22:01 odm
drwxr-xr-x 2 l l 4096 Dec 22 22:01 oem
-rw-r--r-- 1 l l 25053 Dec 22 22:01 plat_file_contexts
-rw-r--r-- 1 l l 7212 Dec 22 22:01 plat_hwservice_contexts
-rw-r--r-- 1 l l 7102 Dec 22 22:01 plat_property_contexts
-rw-r--r-- 1 l l 1551 Dec 22 22:01 plat_seapp_contexts
-rw-r--r-- 1 l l 14700 Dec 22 22:01 plat_service_contexts
drwxr-xr-x 2 l l 4096 Dec 22 22:01 proc
lrwxrwxrwx 1 l l 15 Dec 22 22:01 product -> /system/product
drwxr-xr-x 3 l l 4096 Dec 22 22:01 res
drwxr-x--- 2 l l 4096 Dec 22 22:01 sbin
lrwxrwxrwx 1 l l 21 Dec 22 22:01 sdcard -> /storage/self/primary
-rw-r--r-- 1 l l 384688 Dec 22 22:01 sepolicy
drwxr-x--x 2 l l 4096 Dec 22 22:01 storage
drwxr-xr-x 2 l l 4096 Dec 22 22:01 sys
drwxr-xr-x 2 l l 4096 Dec 22 22:01 system
-rw-r--r-- 1 l l 5359 Dec 22 22:01 ueventd.rc
-rw-r--r-- 1 l l 3373 Dec 22 22:01 ueventd.universal5420.rc
lrwxrwxrwx 1 l l 14 Dec 22 22:01 vendor -> /system/vendor
-rw-r--r-- 1 l l 7011 Dec 22 22:01 vendor_file_contexts
-rw-r--r-- 1 l l 1989 Dec 22 22:01 vendor_hwservice_contexts
-rw-r--r-- 1 l l 218 Dec 22 22:01 vendor_property_contexts
-rw-r--r-- 1 l l 0 Dec 22 22:01 vendor_seapp_contexts
-rw-r--r-- 1 l l 0 Dec 22 22:01 vendor_service_contexts
-rw-r--r-- 1 l l 65 Dec 22 22:01 vndservice_contexts
alexenferman said:
Sorry I meant Ramdisk of the recovery
Click to expand...
Click to collapse
Or do you mean the initrd.img inside the recovery.img file?
Here is the initrd.img inside recovery.img
Code:
$ xz -dc < initrd.img | cpio -idmv
acct
bin
bugreports
cache
config
d
data
default.prop
dev
etc
etc/mke2fs.conf
etc/mkshrc
etc/recovery.fstab
fstab.universal5420
init
init.rc
mnt
odm
odm/app
odm/bin
odm/firmware
odm/framework
odm/lib
odm/lib64
odm/overlay
odm/priv-app
oem
plat_file_contexts
plat_hwservice_contexts
plat_property_contexts
plat_seapp_contexts
plat_service_contexts
proc
product
prop.default
res
res/images
res/images/erasing_text.png
res/images/error_text.png
res/images/font.png
res/images/font_menu.png
res/images/ic_back.png
res/images/ic_back_sel.png
res/images/ic_factory_reset.png
res/images/ic_factory_reset_sel.png
res/images/ic_options_advanced.png
res/images/ic_options_advanced_sel.png
res/images/ic_reboot.png
res/images/ic_reboot_sel.png
res/images/ic_system_update.png
res/images/ic_system_update_sel.png
res/images/icon_error.png
res/images/installing_security_text.png
res/images/installing_text.png
res/images/logo_image.png
res/images/loop00000.png
res/images/loop00001.png
res/images/loop00002.png
res/images/loop00003.png
res/images/loop00004.png
res/images/loop00005.png
res/images/loop00006.png
res/images/loop00007.png
res/images/loop00008.png
res/images/loop00009.png
res/images/loop00010.png
res/images/loop00011.png
res/images/loop00012.png
res/images/loop00013.png
res/images/loop00014.png
res/images/loop00015.png
res/images/loop00016.png
res/images/loop00017.png
res/images/loop00018.png
res/images/loop00019.png
res/images/loop00020.png
res/images/loop00021.png
res/images/loop00022.png
res/images/loop00023.png
res/images/loop00024.png
res/images/loop00025.png
res/images/loop00026.png
res/images/loop00027.png
res/images/loop00028.png
res/images/loop00029.png
res/images/no_command_text.png
res/images/progress_empty.png
res/images/progress_fill.png
res/images/stage_empty.png
res/images/stage_fill.png
res/keys
sbin
sbin/acpi
sbin/adbd
sbin/awk
sbin/base64
sbin/basename
sbin/blockdev
sbin/bu
sbin/cal
sbin/cat
sbin/chcon
sbin/chgrp
sbin/chmod
sbin/chown
sbin/chroot
sbin/chrt
sbin/cksum
sbin/clear
sbin/cmp
sbin/comm
sbin/cp
sbin/cpio
sbin/cut
sbin/date
sbin/dd
sbin/df
sbin/diff
sbin/dirname
sbin/dmesg
sbin/dos2unix
sbin/du
sbin/e2fsck
sbin/e2fsdroid
sbin/e2fsdroid_static
sbin/echo
sbin/env
sbin/expand
sbin/expr
sbin/fallocate
sbin/false
sbin/file
sbin/find
sbin/flock
sbin/fmt
sbin/free
sbin/fsck.exfat
sbin/fsck.ext4
sbin/fsck.f2fs
sbin/fsck.ntfs
sbin/fsck_msdos
sbin/getenforce
sbin/getprop
sbin/grep
sbin/groups
sbin/gunzip
sbin/gzip
sbin/head
sbin/hostname
sbin/hwclock
sbin/id
sbin/ifconfig
sbin/inotifyd
sbin/insmod
sbin/install
sbin/ionice
sbin/iorenice
sbin/kill
sbin/killall
sbin/ln
sbin/load_policy
sbin/log
sbin/logname
sbin/losetup
sbin/ls
sbin/lsmod
sbin/lsof
sbin/lspci
sbin/lsusb
sbin/md5sum
sbin/microcom
sbin/mkdir
sbin/mke2fs
sbin/mke2fs_static
sbin/mkfifo
sbin/mkfs.exfat
sbin/mkfs.ext4
sbin/mkfs.f2fs
sbin/mkfs.ntfs
sbin/mknod
sbin/mkswap
sbin/mktemp
sbin/modinfo
sbin/modprobe
sbin/more
sbin/mount
sbin/mount.ntfs
sbin/mountpoint
sbin/mv
sbin/netstat
sbin/nice
sbin/nl
sbin/nohup
sbin/od
sbin/paste
sbin/patch
sbin/pgrep
sbin/pidof
sbin/pkill
sbin/pmap
sbin/printenv
sbin/printf
sbin/ps
sbin/pwd
sbin/readlink
sbin/realpath
sbin/reboot
sbin/recovery
sbin/renice
sbin/resize2fs
sbin/restorecon
sbin/rm
sbin/rmdir
sbin/rmmod
sbin/runcon
sbin/sed
sbin/sendevent
sbin/seq
sbin/setenforce
sbin/setprop
sbin/setsid
sbin/sgdisk
sbin/sh
sbin/sha1sum
sbin/sha224sum
sbin/sha256sum
sbin/sha384sum
sbin/sha512sum
sbin/sleep
sbin/sload.f2fs
sbin/sort
sbin/split
sbin/sswap
sbin/start
sbin/stat
sbin/stop
sbin/strings
sbin/stty
sbin/swapoff
sbin/swapon
sbin/sync
sbin/sysctl
sbin/tac
sbin/tail
sbin/tar
sbin/taskset
sbin/tee
sbin/time
sbin/timeout
sbin/top
sbin/touch
sbin/toybox_static
sbin/tr
sbin/true
sbin/truncate
sbin/tty
sbin/tune2fs
sbin/ueventd
sbin/ulimit
sbin/umount
sbin/uname
sbin/uniq
sbin/unix2dos
sbin/unzip
sbin/uptime
sbin/usleep
sbin/uudecode
sbin/uuencode
sbin/vmstat
sbin/watchdogd
sbin/wc
sbin/which
sbin/whoami
sbin/xargs
sbin/xxd
sbin/yes
sbin/zcat
sbin/zip
sdcard
sepolicy
storage
sys
system
tmp
ueventd.rc
ueventd.universal5420.rc
vendor_file_contexts
vendor_hwservice_contexts
vendor_property_contexts
vendor_seapp_contexts
vendor_service_contexts
vndservice_contexts
18161 blocks
I have a 16.0 SM-T800 build booting now. Now I have to go through and see what works and doesn't work. This will take a couple of days.
I will also document what patches I needed to make this work not only for myself, but for other future builders.
Please join the exynos5420 team to contribute to getting LineageOS 16 fully functional.
retiredtab said:
I have a 16.0 SM-T800 build booting now. Now I have to go through and see what works and doesn't work. This will take a couple of days.
I will also document what patches I needed to make this work not only for myself, but for other future builders.
Click to expand...
Click to collapse
What did you have to fix? I am building Los 16 for a Los 14 device too, kernel appears to be working, but it does not boot.
bluess57 said:
Please join the exynos5420 team to contribute to getting LineageOS 16 fully functional.
Click to expand...
Click to collapse
I will submit gerrit patches once the 16.0 code all settles down. There are camera + sensor + hal changes still to be merged. So far all bugs that I have found seem to be due to the pending or merge changes.
Some of the changes made to chagalllte weren't made to chagallwifi so it was relatively easy to copy them.
alexenferman said:
What did you have to fix? I am building Los 16 for a Los 14 device too, kernel appears to be working, but it does not boot.
Click to expand...
Click to collapse
What device are you building for? Are you building for a tab S platform?
If a device doesn't boot, I find adb logcat very helpful.
I also use this utility.
Install logcat-colorize on Ubuntu using the Snap Store | Snapcraft
Get the latest version of logcat-colorize for on Ubuntu - logcat-colorize
snapcraft.io
retiredtab said:
I will submit gerrit patches once the 16.0 code all settles down. There are camera + sensor + hal changes still to be merged. So far all bugs that I have found seem to be due to the pending or merge changes.
Some of the changes made to chagalllte weren't made to chagallwifi so it was relatively easy to copy them.
Click to expand...
Click to collapse
yeah I only have a chagalllte so some of the other devices get overlooked.
As to what's currently not functioning:-
camera video recording
sensors /sensor hal may not be fully functional
RIL
+ whatever else I can't recall atm
alexenferman said:
What did you have to fix? I am building Los 16 for a Los 14 device too, kernel appears to be working, but it does not boot.
Click to expand...
Click to collapse
by does not boot, do you mean it is stuck at the lineageos 3 rings startup animation?
bluess57 said:
As to what's currently not functioning:-
camera video recording
sensors /sensor hal may not be fully functional
RIL
+ whatever else I can't recall atm
Click to expand...
Click to collapse
What I found so far.
Doesn't work
1. home button doesn't wake up tablet. I think I know what is wrong and I'm compiling another new build, but it will take about 1 hour to complete.
2. screen rotation - which I think is due to pending merge hal/sensor changes
3. MTP, this could be due to my eng build for debugging purposes
4. camera - changes not merged. When I try a repopick -t Camera-Bringup, I get cherry-pick errors so I'm going to wait until it's all merged before I test camera.
Works
1. wifi (5 and 2.4)
2. bluetooth
3. brightness
4. external audio
5. audio through headphones
6. GPS - needs this yet to merged patch
https://review.exynos5420.com/c/exynos5420/android_device_samsung_chagalllte/+/7362
I'm not a git expert. Everytime I use it, I struggle with the commands to upload patches. But most of the problems with chagallwifi are because chagalllte commits aren't applied to it which is understandable if the developers have the LTE version.
it will be very good to switch to Los 16 SM-T800 please guys continue
bluess57 said:
yeah I only have a chagalllte so some of the other devices get overlooked.
Click to expand...
Click to collapse
I also have a SM-T700 klimtwifi which I can build and test for. However, I have more than one SM-T800 so I will build for T800 first and get all the bugs worked out and then build T700 later.

Categories

Resources