Now you can auto-debloat your Galaxy S4 beauty using my new Auto-Debloat S4 flashable zip!
Link: http://www.mediafire.com/download/awabu8cg5a19lj4/Debloat-SGS4.zip
This is tested working on my rooted, unlocked (bootloader) SGH-I337 (AT&T) running Stock AT&T JB 4.2.2 I337UCUAMDL and TWRP Recovery 2.5.0.2.
But it should work on just about any S4 ROM though the primary target is JB 4.2.2.
Now of course there are many ways to debloat your rooted S4. But you may find this one very useful.
By default, my flashable zip frees up 600MB of precious space in your 2.7GB /system partition by removing approximately 90 bloatware apks and their corresponding odex files! Run time is just over 30 seconds.
And the customizable database file (bloatware-apk-sorted.txt) is sorted by file size to help you focus on big bloats like Samsung’s Health app “SHealth2.apk” (88 MB).
Thus you can debloat even more by extracting the database “bloatware-apk-sorted.txt” from zip, changing filename suffixes from “.KEEP” to “.apk”, reinserting database and reflashing. Run time is shorter on the second and subsequent passes.
Want to "rebloat"? No problem: All bloatware is safely moved to a special directory: /sdcard/Download/Bloatware for quick recovery.
As usual, “I will let YOU DECIDE whether to wipe data!”
Here’s a clip of my original database “bloatware-apk-sorted.txt” showing some of the worst offenders --- at least in terms of file size:
-rw-r--r-- 1 root root 88540395 Apr 27 2013 SecSettings.KEEP
-rw-r--r-- 1 root root 87854416 Apr 27 2013 SHealth2.apk
-rw-r--r-- 1 root root 39695494 Apr 27 2013 Episodes.apk
-rw-r--r-- 1 root root 39428223 Apr 27 2013 SecGallery2013.KEEP
-rw-r--r-- 1 root root 36196565 Apr 27 2013 GroupPlay_20.apk
-rw-r--r-- 1 root root 33781912 Apr 27 2013 InteractiveTutorial.apk
-rw-r--r-- 1 root root 28792764 Apr 27 2013 SecContacts.KEEP
-rw-r--r-- 1 root root 27349911 Apr 27 2013 S-Voice_Android_phone_J.apk
-rw-r--r-- 1 root root 26746285 Apr 27 2013 Match3VS.apk
-rw-r--r-- 1 root root 25549401 Apr 27 2013 SMemo2.apk
-rw-r--r-- 1 root root 25440434 Apr 27 2013 Peel.apk
-rw-r--r-- 1 root root 23676201 Apr 27 2013 SamsungBooks.apk
-rw-r--r-- 1 root root 23168685 Apr 27 2013 AllSharePlay15.apk
-rw-r--r-- 1 root root 22967881 Apr 27 2013 ChatONV_J.apk
-rw-r--r-- 1 root root 22829640 Apr 27 2013 ClockPackage.KEEP
-rw-r--r-- 1 root root 22407406 Apr 27 2013 PolarisOffice5.KEEP
Click to expand...
Click to collapse
And here’s the script engine: auto-debloat.sh
#!/sbin/sh
echo " "
echo "Auto-Debloat for Samsung S4!"
echo "Initial Release (16 Jun 2013)"
echo "sendust7 @ xda developers"
bloatdir="/sdcard/Download/Bloatware"
bloatfile="/tmp/bloatware-apk-sorted.txt"
echo " "
echo "All bloatware files are suffixed by .apk in $bloatfile"
echo "System apps to be retained are suffixed by .KEEP in $bloatfile"
echo "All bloatware (apk and odex) will be moved to $bloatdir"
if [ -d $bloatdir ]; then
echo " "
else
echo " "
mkdir $bloatdir
fi
while read line; do
apkname=$(echo $line | cut -d" " -f9)
apkprefix=$(echo $apkname | cut -d"." -f1)
apkodex=$apkprefix.odex
if [ -f /system/app/$apkname ]; then
echo "Moving /system/app/$apkname to $bloatdir ..."
mv /system/app/$apkname $bloatdir
if [ -f /system/app/$apkodex ]; then
echo "Moving /system/app/$apkodex to $bloatdir ..."
mv /system/app/$apkodex $bloatdir
fi
fi
done < $bloatfile
Click to expand...
Click to collapse
Blessings Enjoy
Boom.
Can i use your application to debloat my Samsung Galaxy S4 Active SGH-i537. Running android 4.2.2. Its branded by AT&T and want to get rid of these crapy apps of AT&T. Kindly let me know.
Regards,
This is efs folder log file
Sun Jan 1 00:02:01 2012: nv data does not exist
Sun Jan 1 00:02:01 2012: default NV restored
Sun Jan 1 00:02:09 2012: OFFSET_FOR_PRESET2 writing input
Sun Jan 1 00:02:10 2012: 2nd NV built
Sun Jan 1 00:02:10 2012: NV data back-uped
Sun Jan 1 00:09:38 2012: check off
Sun Jan 1 00:00:04 2012: check off
Sun Jan 1 00:02:32 2012: 2nd NV built
Sun Jan 1 00:02:32 2012: NV data back-uped
Sun Jan 1 00:02:32 2012: check on
Sun Jan 1 00:00:34 2012: check off
Sat Sep 22 17:22:12 2012: check off
Sat Sep 22 09:23:16 2012: 2nd NV built
Sat Sep 22 09:23:16 2012: NV data back-uped
Sat Sep 22 09:23:16 2012: check on
Sat Sep 22 09:27:23 2012: check off
Sat Sep 22 09:27:46 2012: 2nd NV built
Sat Sep 22 09:27:46 2012: NV data back-uped
Sat Sep 22 09:27:46 2012: check on
Sat Sep 22 09:37:20 2012: fail - no checksum info
Sat Sep 22 09:37:20 2012: NV restored
Sat Sep 22 09:38:04 2012: OFFSET_FOR_PRESET1 writing input
Sat Sep 22 09:38:04 2012: 2nd NV built
Sat Sep 22 09:38:04 2012: NV data back-uped
Sat Sep 22 09:38:11 2012: OFFSET_FOR_PRESET2 writing input
Sat Sep 22 09:38:11 2012: 2nd NV built
Sat Sep 22 09:38:11 2012: NV data back-uped
Sat Sep 22 09:38:14 2012: OFFSET_FOR_PRESET2 writing input
Sat Sep 22 09:38:14 2012: 2nd NV built
Sat Sep 22 09:38:14 2012: NV data back-uped
Mon Aug 5 17:23:22 2013: input from cp
Mon Aug 5 17:23:22 2013: 2nd NV built
Mon Aug 5 17:23:23 2013: NV data back-uped
Fri Aug 30 19:41:01 2013: OFFSET_FOR_PRESET2 writing input
Fri Aug 30 19:41:01 2013: 2nd NV built
Fri Aug 30 19:41:01 2013: NV data back-uped
Hi,
I bought note 2 on ebay 2 Dec. 2013. before insert my sim card I decide to make an update with Kies...
After update imei was 0049..
I know my bad.. I had to check before update... but I do not know now is that note2 already broken or I broke during update...
so If it's not my fould I'll send it to seller.
I sent the NFS Log can some one help me ?
thank you
Hey I cnt help u with the log but I know a solution... you may flash the modem from the previous firmware you were running, and you will get ur imei correct
Sent from my GT-N7100 using XDA Premium 4 mobile app
http://forum.xda-developers.com/showthread.php?t=2567862
i posted this earlier. if you busted your efs try what i did.
if its only an imei issue try efs pro.
I gave my cell phone to samsung because still in warranty.
but they call today and said my serial number 00000000000 & not covered ask for 200€ !?*
I sent couple days ago my mobile to Samsung center (not seller or store) and they fix everything ?!* now everything fine...
even the serial and imei gone.. don't listen to others just try to send your mobile to send Samsung center.
The .. seller told me 200€ for fix this issue not covored bla bla....
Thank you guys..
I've scavenged the forums for kernel images in circulation and gathered a rather considerable collection of them. Here's the whole list, also including stock kernels for comparison (starting with 1.0.1, as this is the earliest version I have access to). I don't have direct links (didn't save them as I went on my collecting spree) but I renamed the files by the poster's name and the date of their post so each file should be easy to find through search. I also removed any duplicates (reposts).
The list is not by any means complete, and updates are most welcome but hopefully it's a good starting point, and others will find this summary helpful.
Using this thread you can identify if a kernel found somewhere else is the same as one of the "well-known" ones. The best way for this is to check the MD5 sum unless the file sizes obviously differ. Along with the kernel image list, there is also a comparison of other boot-related files (aka "the missing changelog") below.
Kernel Images (uImage)
All images in circulation seem to be based on Linux-2.6.29-omap1. The format of the data is as follows: the first column is the normalized filename (post date in YYYYMMDD format followed by the poster name). The second column is the creation date as recorded in the kernel (pulled from the image with mkimage -l). The third column is the image file size in bytes, and the ultimate, fourth column is the MD5 sum of the file.
Code:
uImage-20120122-verygreen Sun Jan 22 02:21:22 2012 1871536 4df25ed3887ded06e4894f31cc591767
uImage-20120326-mi100-multitouch Tue Mar 27 00:37:51 2012 1949768 35ae84d06b2397c3b1c3a18cf8489ddc
uImage-20120328-RenateNST-recommended Wed Mar 28 20:51:09 2012 2674768 2f30e452286187b4fd39a607ee08b460
uImage-20121002-guevor Tue Oct 02 23:57:28 2012 1922624 5389693e484ae478dba1ddd599af35f8
uImage-20121006-guevor Sat Oct 06 15:36:45 2012 1928808 117c33343bad9acc68642eaa0abca6cf
uImage-20121006-guevor-usbhost Fri Oct 05 02:12:02 2012 1927204 82e967e2b46401df642b803f386cbeec
uImage-20121014-guevor-166 Sat Oct 13 16:35:31 2012 1927292 6c4534cf34c3209cac23707de9bcd858
uImage-20121118-guevor-174 Fri Nov 16 21:30:24 2012 1929356 329b229f17fe08c235d352881c8bafa5
uImage-20121205-guevor-176-usbhost Wed Dec 05 19:36:24 2012 1929652 c9f649640131f1afa0e8a5b54883464e
uImage-20130525-waynesi Sat May 25 20:11:19 2013 1824476 67b0edb6bef76d119b60bd4ab86a525b
uImage-20130703-latuk Fri Jun 28 20:30:11 2013 2630460 15780cc3e9a8593627fd1c9608b068c9
uImage-20130703-latuk-nopowercheck Fri Jun 28 20:26:23 2013 2630736 18541b6fb9f2abd84daea77f3340d129
uImage-20130721-latuk-sd10 Mon Jul 15 18:21:51 2013 2630560 f43e6d9767e0d3dab18162b78a6fb7e3
uImage-20140813-Nookie-recommended Tue Apr 24 20:31:04 2012 2674584 69688487b17f6fa1202efba87aec3558
uImage-recovery-NookMgr-0.5.0 Sat Dec 08 11:46:06 2012 1827124 9366da88d7fc22b5019423b644e0fa6d
uImage-recovery-noogie Thu May 26 12:09:29 2011 1839448 0db7b475ef4dad39af21aa6af7619383
uImage-stock-101 Fri Jul 22 10:32:07 2011 1839824 a2408888c24986ec9ee9fac28bce08a4
uImage-stock-110 Sat Oct 29 15:45:55 2011 1841908 455700f060d49977da4adcce8e5516e8
uImage-stock-112 Tue Feb 28 05:38:36 2012 1841904 e056b6734c0420f3c1798f57fe4eb761
uImage-stock-121 Sat Dec 08 06:35:10 2012 1848944 a6a8bfa18ea3e7c74e87526881b980fd
The same list sorted by kernel build date:
Code:
20110526 uImage-recovery-noogie 1839448 0db7b475ef4dad39af21aa6af7619383
20110722 uImage-stock-101 1839824 a2408888c24986ec9ee9fac28bce08a4
20111029 uImage-stock-110 1841908 455700f060d49977da4adcce8e5516e8
20120122 uImage-20120122-verygreen 1871536 4df25ed3887ded06e4894f31cc591767
20120228 uImage-stock-112 1841904 e056b6734c0420f3c1798f57fe4eb761
20120327 uImage-20120326-mi100-multitouch 1949768 35ae84d06b2397c3b1c3a18cf8489ddc
20120328 uImage-20120328-RenateNST-recommended 2674768 2f30e452286187b4fd39a607ee08b460
20120424 uImage-20140813-Nookie-recommended 2674584 69688487b17f6fa1202efba87aec3558
20121002 uImage-20121002-guevor 1922624 5389693e484ae478dba1ddd599af35f8
20121005 uImage-20121006-guevor-usbhost 1927204 82e967e2b46401df642b803f386cbeec
20121006 uImage-20121006-guevor 1928808 117c33343bad9acc68642eaa0abca6cf
20121013 uImage-20121014-guevor-166 1927292 6c4534cf34c3209cac23707de9bcd858
20121116 uImage-20121118-guevor-174 1929356 329b229f17fe08c235d352881c8bafa5
20121205 uImage-20121205-guevor-176-usbhost 1929652 c9f649640131f1afa0e8a5b54883464e
20121208 uImage-recovery-NookMgr-0.5.0 1827124 9366da88d7fc22b5019423b644e0fa6d
20121208 uImage-stock-121 1848944 a6a8bfa18ea3e7c74e87526881b980fd
20130525 uImage-20130525-waynesi 1824476 67b0edb6bef76d119b60bd4ab86a525b
20130628 uImage-20130703-latuk 2630460 15780cc3e9a8593627fd1c9608b068c9
20130628 uImage-20130703-latuk-nopowercheck 2630736 18541b6fb9f2abd84daea77f3340d129
20130715 uImage-20130721-latuk-sd10 2630560 f43e6d9767e0d3dab18162b78a6fb7e3
RAM Disk Images (uRamdisk)
The missing changelog:
uRamdisk-stock-101 (Size: 185256, MD5: 054897f36c588b714f60bf41ebf7cbdf)
Initial version I have access to
uRamdisk-stock-110 (Size: 185298, MD5: ef473d179db2bf72bf6bd4cd3fd01dca)
/init.rc: Added:
Code:
# change permissions for calibration
chmod 0666 /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0050/forcecal
uRamdisk-stock-112 (Size: 185298, MD5: 5f3c7e2ffffd870454614a94ac4e33e5)
No changes
uRamdisk-stock-121 (Size: 185650, MD5: 6c2db57a6b9426ce10544fd9c8dc6f40)
/init
/init.rc: Added:
Code:
setprop_fromtoken ro.product.model /rom/devconf/ModelNumber
setprop_fromtoken ro.serialno /rom/devconf/DeviceID
Code:
chown system system /sys/class/leds/lcd-backlight/dim_brightness
chown system system /sys/class/leds/lcd-backlight2/dim_brightness
chown system system /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0040/dim_start
Code:
# Set default dim speed to 500ms
write /sys/devices/platform/i2c_omap.2/i2c-adapter/i2c-2/2-0040/dim_time 500
Code:
[STRIKE][COLOR="Red"]on property:sys.settings_system_version=3[/COLOR][/STRIKE]
[B][COLOR="Green"]on property:dev.bootcomplete=1[/COLOR][/B]
start bootcnt
Code:
service copyassets /system/bin/copyassets.sh
user root
oneshot
Non-Stock Changes to RAM Disk Images
Excluding the obvious meddling with ADB.
/init.rc: Governor change for uImage-20121118-guevor-174:
Code:
# Enabling DVFS with conservative governor
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor [STRIKE][I][COLOR="Red"]conservative[/COLOR][/I][/STRIKE][B][COLOR="Green"]smartassV2[/COLOR][/B]
/init.rc: Adding -f to omap-edpd:
Code:
service omap-edpd /system/bin/omap-edpd.elf [B][COLOR="Green"]-f[/COLOR][/B] -n --timeout=2 -pV220 --fbdev=/dev/graphics/fb0 -s /system/lib/dsp/subframeip_snode_dsp.dll64P -w /rom/devconf/EpdWaveform,/system/etc/default_waveform.bin
/system/bin/omap-edpd.elf --help said:
--fastupdate (-f) : fast update algorithm ON
Click to expand...
Click to collapse
Init Binaries inside the RAM Disk (uRamdisk:/init)
init-101-110-112 (Size: 127964, MD5: 738a02210409fd9e31837053cd3c9b29)
Stock init
init-121 (Size: 128000, MD5: 72e5c0d66e8fcb070fb67a004045b012)
Stock init updated for 1.2.1
init-20120122-verygreen (Size: 107344, MD5: 1243d422e4f0532ffdf12f21b6632902)
Alternative init that allows the use of USB keyboard
Recovery Kernel Images (uRecImg)
The recovery kernel is always the same as the main one, unless you use a custom recovery. Among custom recoveries, Clockwork RC2 uses uImage-stock-110. For Noogie and NookManager 0.5.0 it seems to be something else than the other images I discovered (see above).
Recovery RAM Disk Images (uRecRam)
For obvious reasons I am limiting myself to stock images here. The missing changelog:
uRecRam-stock-101 (Size: 1508577, MD5: ce1d033d97953051fc59012a4335bc96)
Initial version I have access to
uRecRam-stock-110 (Size: 1514136, MD5: 16379c824c1a2bd823cba9690d0a3edc)
/etc/dsp/baseimage.dof
/etc/dsp/subframeip_snode_dsp.dll64P
/sbin/omap-edpd.elf
/sbin/recovery
uRecRam-stock-112 (Size: 1514134, MD5: 530b055737a01694dd1ce30bfae3531b)
No changes
uRecRam-stock-121 (Size: 1517774, MD5: 7b6af9319f5543cdab853672f3a70dff)
/etc/dsp/subframeip_snode_dsp.dll64P (again)
/res/images/icon_installing.png
/res/images/icon_installing_factory.png
/res/images/icon_installing_rom.png
/sbin/recovery (again)
/build.prop: Added:
Code:
persist.nook.cust.region=US
/init (as in the main image, see above)
Wrap-up
I started collecting this information in particular to reach some conclusion which kernel would be best for my purposes [for the record: (i) looking to squeeze as much as possible from the display with NoRefresh or FastRefresh, (ii) performance optimizations if stable and without impact on battery life, (iii) no need for USB host but OK if not a drain on batery, (iv) GlowLight support not a factor as my device doesn't have one, (v) SDXC Class 10 support also not a factor]. At this point I don't see a strictly dominating choice. I'll edit the post when or if this changes.
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
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.