I am trying to:
* run backtrack image on my slide the small custom smaller image not the +4gig one for fat32
* get RW to /system for su updated and allow rootkeeper to 'work' http://forum.xda-developers.com/showthread.php?p=21219704
* I seen several tutorials but I am not sure what one to follow .. i have S-ON and I assume I need that off for su to update within clockwork etc ... none of the other root apps work.. the superuser.apk is installed and I allow perms but nothing seems to work.. I am hoping it is a easy fix ..
INFO:
Code:
# CM 7
Linux localhost 2.6.32.17-cyanogenmod-g46ca326 #1 PREEMPT Thu Apr 21 20:36:02 EDT 2011 armv6l GNU/Linux
ESPRESSO PVT SHIP S-ON
HBOOT-1.02.0000
MICROP-0620
When I try to mount loop etc ..
Code:
# losetup /dev/loop254 $kit/bt5.img
losetup /dev/loop254 $kit/bt5.img
losetup: /dev/loop254: No such file or directory
# ls /dev/loop254
ls /dev/loop254
/dev/loop254
# uname -a
uname -a
# busybox mknod /dev/loop2 b 7 0
busybox mknod /dev/loop2 b 7 0
mknod: /dev/loop2: File exists
# mount -o loop,noatime -t ext2 $kit/bt5.img $mnt
mount -o loop,noatime -t ext2 $kit/bt5.img $mnt
mount: can't setup loop device: No such file or directory
# losetup /dev/block/loop7 $kit/bt5.img
losetup /dev/block/loop7 $kit/bt5.img
losetup: /dev/block/loop7: No such file or directory
# losetup /dev/block/loop2 $kit/bt5.img
losetup /dev/block/loop2 $kit/bt5.img
losetup: /dev/block/loop2: No such file or directory
# losetup /dev/loop2 $kit/bt5.img
losetup /dev/loop2 $kit/bt5.img
losetup: /dev/loop2: No such file or directory
# losetup /dev/loop7 $kit/bt5.img
losetup /dev/loop7 $kit/bt5.img
losetup: /dev/loop7: No such file or directory
# ls /dev/loop2
ls /dev/loop2
/dev/loop2
# ls /dev/loop7
ls /dev/loop7
/dev/loop7
#
well first of all you're in the wrong forums...
try this forum instead.
you have an HTC Espresso, Mytouch 3G Slide.
this is the HTC Glacier, Mytouch 4G.
Hy.
I have a HTC HD2 with a dead touch screen (I can read, but touch is not reactive). I could reset it to factory settings via buttons. So I have a Windows Welcome screen.
I can also enter HSPL.
Is it possible to flash the device, and install Android without working screen ?
Once I have Android, I can do stuff with the device, and use it as VNC client, and manage remotly via ssh. My problem is to install Android on it. Most tutos say at one step or an other to activate ActiveSync in Windows, what is not possible for me.
I am used to HTC Sensation, and to all classic Android tools (adb, fastboot). I have Windows and Linux hosts.
Classic tutos are not usable for me.
Otherwise, the device will go for sale, for peaces. 10€.
Thanks.
voldown + power --> bootloader,
fhlash hspl
flash radio 2.15.50
flash magldr
use toolkit to apply partition size and cwm
into cwm
flash rom from zip
no touchscreen necessary
the instruction about activesync is a red herring, , it doesn't refer to the app on the PC, and it doesn't require winmo to be running on the phone either, it just means get a usb connection.
however if you have trouble flashing hspl, then manually updating windowsmobiledevicecenter (find it on microsoft website) will help fix driver errors, and later, when you get into magldr and start using 'usb flasher' you may wanna install 'myphoneexplorer' for the android drivers it comes with.
^That's true, but you might have a problem with Aroma installer. I think it may work with the volume keys too, but if it doesn't then you'll have to find a ROM which doesn't use Aroma (most relatively old ROMs don't) and flash that instead.
Nigeldg said:
^That's true, but you might have a problem with Aroma installer. I think it may work with the volume keys too, but if it doesn't then you'll have to find a ROM which doesn't use Aroma (most relatively old ROMs don't) and flash that instead.
Click to expand...
Click to collapse
Aroma does work without touchscreen, buttons can be used to select the default choices, (can't recall if volume buttons can used to change selected option, so may need to edit ROM zip so the defaults are what you want). The issue I'd see is how you go about issuing commands and starting apps; it's possible of course - there are commands to simulate screen presses (monkeyrunner) and command to start apps/processes but those commands can get complicated.
If you get a VNC system set up without touchscreen then could you add your procedure?
I am stuck at almost last step: pushing CWM: I have downloaded Recovery-400 from http://www.filecrop.com/Clockworkmod-Recovery-hd2.html , but I get the RSPL error message. I have Windows XP SP3 with .NET3 SP1, so i am admin, i have EnterBootloader.exe and rapidtool.exe, and I have unticked the USB stuff in ActiveSync ... but i am still stuck at the RSPL error :/
About going further: if I have ADB access from CWM, I will just install Armel by copying from my Sensation (Debian Armel have been installed using LinuxInstaller by Galoula). If i don't have adb, I will have to pre-install it in the zip, and reflash. In short, I push a chrootable env, and find an init script that will run sshd after boot. Once I have ssh, i'm done.
I had to install RAPI.dll, and CEUTIL.dll (found in google), re-install ActiveSync, and use a very specific ROM. HD2toolkit did not work at all for me. I forgot how I installed MAGDLR, but it was PITA to install it. And once installed, I spent 2 days on trying to use it. Putting ROMs on uSD does not allow to install the from SD.
After viewing http://cdn.youtubeavi.com/view-video/0TpYHpfHW-8 (confirmed by reading http://resetguide.com/2012/05/how-to-install-android-on-hd2-nand/ ), I saw that amongst my 1GB of data downloaded in the last days, I did not have the file ANDR_install.exe; I downloaded all possible ROMs until I find one having this magic file: http://forum.xda-developers.com/showthread.php?t=893637 . Only this ROM has andr_install.exe . And when I ran it, it worked on the first time (while of course having HD with MAGLDR on option 5: USB flash).
Now, my HD2 started Android. I still can not use it at all for now, but at least, I have made a step.
adb works, so it will probably be very easy for me. From ADB, I can do almost anything: install APKs(pm install), getprop, remount /system rw, install Debian manually ... the hardest part may be to click on buttons, but I can find a WA for this: create minimal apps on my other Android phone, using Tasker with AppFactory, apps which will be able to send keystrokes, and start them as required. Long way, but should work (if I don't have CPU uncompat issues). Anyway, without touch pad, it's not gonna stay a "phone"; it will mostly be a VNC-viewer for other devices (like my RaspberryPi).
Hell I am lucky: both HTD HD2 and HTC Sensation use the exact same CPU: "ARMv7 Processor rev 2 (v7l)" . Gonna be trivial to have fun around An example to install a VNC-client:
Code:
[email protected] /tmp $ adb -s SH169V80XXXX pull /data/app/android.androidVNC-1.apk
1703 KB/s (245795 bytes in 0.140s)
[email protected] /tmp $
[email protected] /tmp $ adb -s 0123456789ABCDEF install android.androidVNC-1.apk
2015 KB/s (245795 bytes in 0.119s)
pkg: /data/local/tmp/android.androidVNC-1.apk
Success
[email protected] /tmp $
Same for server.
Like in my Sensation (definitly, I am lucky), I have a free folder in the default PATH :
Code:
localhost / # echo $PATH
/sbin:/system/sbin:/system/xbin:/system/bin
localhost / # ls /system/
app dmesg.txt framework lost+found lost+found xbin
bin etc lib lost+found media
build.prop fonts lost+found lost+found usr
localhost / #
so, let's populate it
Code:
localhost / # df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 205.9M 0 205.9M 0% /dev
tmpfs 205.9M 0 205.9M 0% /mnt/asec
/dev/block/mtdblock1 127.3M 118.8M 8.5M 93% /system
/dev/block/mtdblock3 248.8M 65.2M 183.5M 26% /data
/dev/block/mtdblock2 40.0M 1.1M 38.9M 3% /cache
/dev/block/vold/179:1
3.7G 2.3G 1.4G 63% /mnt/sdcard
/dev/block/vold/179:1
3.7G 2.3G 1.4G 63% /mnt/secure/asec
localhost / # mount -o remount,rw /dev/block/mtdblock1 /system
localhost / # cd /system/
localhost system # ln -s /data/local/bin/ sbin
localhost system #
Now add my personal boot script:
Code:
localhost system # cd /etc/init.d/
localhost init.d # ls -l
-rwxrwxrwx 1 root root 365 Feb 29 2008 00banner
-rwxrwxrwx 1 root root 27 Oct 9 2010 01sysctl
-rwxrwxrwx 1 root root 229 Feb 29 2008 03firstboot
-rwxrwxrwx 1 root root 105 Feb 29 2008 04modules
-rwxrwxrwx 1 root root 1593 Feb 29 2008 05mountsd
-rwxrwxrwx 1 root root 794 Feb 29 2008 20userinit
localhost init.d # ln -s /data/local/bin/rc.local 99doublehp
localhost init.d #
and populate /data as required:
Code:
bash-3.2# tar -czf bin.tgz /data/local/bin/
tar: removing leading '/' from member names
bash-3.2#
[email protected] /tmp $ adb -s SH169V80XXXX pull /data/app/bin.tgz
3660 KB/s (411734 bytes in 0.109s)
[email protected] /tmp $
[email protected] /tmp $ adb -s 0123456789ABCDEF push bin.tgz /data/local/tmp/
1972 KB/s (411734 bytes in 0.203s)
[email protected] /tmp $
localhost / # tar -xvzf /data/local/tmp/bin.tgz
data/local/bin/
data/local/bin/cpu
data/local/bin/rc.local
data/local/bin/psa
[...]
ah ... at last, ONE difference:
Code:
localhost / # head -n1 /system/sbin/psa
#!/system/bin/bash
localhost / # which bash
/system/xbin/bash
localhost / #
localhost / # cd /system/bin/
localhost bin # ln -s ../xbin/bash .
localhost bin #
No way to edit each and every script ^^
Most important one for debugging:
Code:
localhost ~ # vibrate 100
Voltage not provided. Using default 3100 mV.
/system/sbin/vibrate: line 37: /sys/devices/virtual/timed_output/vibrator/voltage_level: No such file or directory
localhost ~ # vibrate 500
Voltage not provided. Using default 3100 mV.
/system/sbin/vibrate: line 37: /sys/devices/virtual/timed_output/vibrator/voltage_level: No such file or directory
localhost ~ #
Let's prepare the SDcard for Debian use; since CM6 does not have mkfs.ext3, I did that on my workstation.
Code:
localhost / # mkdir -p /data/local/mnt/sdcard_ext
localhost / # mount /dev/block/mmcblk0p1 /data/local/mnt/sdcard_ext/
localhost / #
I should have started by this (to help understand these logs), but it's never too late:
on HD: vi /etc/bash/bashrc
PS1='\[\033[01;31m\][email protected]\[\033[01;34m\]:\w\[\033[00m\] '
on Sensation: vi $HOME/.bashrc
PS1='\[\033[01;31m\][email protected]\[\033[01;34m\]:\w\[\033[00m\] '
This prompt is handy so that I can do copy-paste of the prompt itself for use with scp and rsync: if I am at one place in ssh, I can copy the prompt to scp a file there from an other machine.
So ... I was about to copy my Debian: I put both SDcards in the workstation.
Code:
[email protected]:~ cp -a /media/uSD_ext3/Linux /media/Hmmm/
Remove sshd keys to force regen ( /etc/ssh/ssh_host_*). Update hostname (it never properly worked in Armel).
... I'll continue overnight.
doublehp said:
I
After viewing http://cdn.youtubeavi.com/view-video/0TpYHpfHW-8 (confirmed by reading http://resetguide.com/2012/05/how-to-install-android-on-hd2-nand/ ), I saw that amongst my 1GB of data downloaded in the last days, I did not have the file ANDR_install.exe; I downloaded all possible ROMs until I find one having this magic file: http://forum.xda-developers.com/showthread.php?t=893637 . Only this ROM has andr_install.exe . And when I ran it, it worked on the first time (while of course having HD with MAGLDR on option 5: USB flash).
Click to expand...
Click to collapse
...because thats the old, outdated way of installing android,, pre-nand recovery, , and those are old, outdated android roms which is why only they have the 'magic' (now obsolete) file.
samsamuel they may be outdated, but I love CM6 (after 1h of use, I find it very good), and no other method worked (4 or 5 other different methods all ended up in the RSPL.cpp issue).
To take control of my new Android, a friend told me to try AndroidScreenCast. It's some kind of VNC, specially written for Android.
Once Android is installed, you can have fun with it, without touchpad, by using http://code.google.com/p/androidscreencast/ . I am lucky that on CM6, adb was enabled by default. Download http://androidscreencast.googlecode.com/svn/trunk/AndroidScreencast/dist/androidscreencast.jnlp and run it with
Code:
javaws androidscreencast.jnlp
I will try to not use it at all. I tried it, just so that I can tell "it works", and discard all welcome menus. Did not even configure Wifi.
[Thread edited and changed, because partially solved]
Device: asus Nexus 7
Android Version: 4.2.2
Build: JDQ39
rooted
I have installed SSHDroidPro (v1.9.6) - https://play.google.com/store/apps/details?id=berserker.android.apps.sshdroidpro and Terminal IDE (v2.02) - https://play.google.com/store/apps/details?id=com.spartacusrex.spartacuside
Code:
/storage/emulated/legacy # which rsync
/storage/emulated/legacy # which mkdir
/data/data/berserker.android.apps.sshdroidpro/home/bin/mkdir
Code:
-rwx------ 1 u0_a86 u0_a86 1012309 Dec 5 2011 /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync
What do I have to do, that _this_ rsync is used by SSHDroidPro? I would like to use all shell.commands from Terminal IDE with SSHDroidPro.
It helped to copy rsync set the permissions to 755 and link it:
Code:
cp /data/data/com.spartacusrex.spartacuside/files/system/bin/rsync /data/data/berserker.android.apps.sshdroidpro/dropbear
ls -l /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
-rwxr-xr-x 1 root root 1012309 Mar 10 01:37 /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
ls -l /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
lrwxrwxrwx 1 root root 60 Mar 10 01:38 /data/data/berserker.android.apps.sshdroidpro/home/bin/rsync -> /data/data/berserker.android.apps.sshdroidpro/dropbear/rsync
And then:
Code:
/storage/emulated/legacy # which rsync
/data/data/berserker.android.apps.sshdroidpro/home/bin/rsync
The rest of the posting was deleted, because it was a bug in my script. But what can I do, so the ssh-server can use the commands ot the IDE-Terminal?
Hi, this is a guide to install a Linux image on your rooted Android phone with the debootstrap + chroot method.
In this guide, we'll install a Debian image, but the steps are practically the same, with a few tweaks.
If you need help to install a Linux image, feel free to ask on this thread.
For this guide, all credit goes to them:
http://linux-expert.net/?Trucs_et_astuces___Android___Tutoriel_%3A_Chroot_Debian (in french)
http://forum.xda-developers.com/showthread.php?p=45457799
http://forum.xda-developers.com/showthread.php?t=2312013
http://forum.xda-developers.com/showthread.php?t=631389
http://forum.xda-developers.com/showthread.php?t=1418546
http://forum.xda-developers.com/showpost.php?p=5671794&postcount=124
VNC
________________
I. On your PC
So first, you have to create the .img file that will contain the OS.
In a GNU/Linux environment (PC) and with the root permissions, type these commands:
Code:
# mkdir debian
# dd if=/dev/zero of=wheezy-armhf.img bs=1M count=0 seek=2048
[COLOR="Red"](NOTE: "of=" will be the name of our .img file and "seek=" the size of the file (MB). Here, we create a file named "wheezy-armhf.img" of 2 GB)[/COLOR]
# mkfs.ext4 -F wheezy-armhf.img
# mount -o loop wheezy-armhf.img /debian
Then we have to fill up the filesystem.
Code:
# debootstrap --foreign --arch=armhf wheezy debian/
# umount debian
Finally, move it to your SD Card. In my case, I moved it on /data/local/
II. On your phone
On your phone, in a terminal emulator and with the root permissions, type the following commands:
Code:
# mount -o rw,remount rootfs /
# export LINUXROOT=/linux
(NOTE: here we'll install Debian on the root of the internal memory, in "/", but we can also install Debian on the SD Card or in /data/loca/linux by changing the path after "LINUXROOT=")
# mkdir $LINUXROOT
# busybox mknod /dev/block/loop100 b 7 100
# losetup /dev/block/loop100 /sdcard/wheezy-armhf.img
# mount -t ext4 /dev/block/loop100 $LINUXROOT
# chroot $LINUXROOT /bin/sh
# export PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
# /debootstrap/debootstrap --second-stage
The debootstrap's second part should start. Grab a cup of coffee while it's working!
When it's finish, leave the chroot by typing
Code:
# exit
# su
Let's mount the filesystem. We're close!
Code:
# mount -t proc none /proc
# mount -t sysfs none /sys
# mount -o bind /dev /dev
# mount -t devpts none /dev/pts
Now, we have to set the environment variable. Ensure that you have set the correct path of LINUXROOT in case you've chosen another path than /linux.
Code:
# export LINUXROOT=/linux
# export TMPDIR=/tmp
# export USER=root
# export HOME=/root
# export SHELL=/bin/bash
# export TERM=linux
# export LC_ALL=C
# export LANGUAGE=C
# export LANG=C
And finally, chroot.
Code:
# chroot $LINUXROOT /bin/bash
su
Welcome on Debian!
III. DNS and Mirrors
Set a DNS. We'll set the free Google DNS but you can set yours if you want.
Code:
echo -e "domain local\nsearch local\n" >> /etc/resolv.conf
echo -e "# DNS Google\nnameserver 8.8.8.8\nnameserver 8.8.4.4\n" >> /etc/resolv.conf
You can add mirrors to your sources.list if you want. I'm french so I added french mirrors:
Code:
# echo -e "## Debian Wheezy sources.list\n\n" > /etc/apt/sources.list
# echo -e "## Debian.org FR mirror\ndeb http://ftp.fr.debian.org/debian/ wheezy main contrib non-free\ndeb-src http://ftp.fr.debian.org/debian/ wheezy main contrib non-free\n\n" >> /etc/apt/sources.list
# echo -e "## Debian security updates\ndeb http://security.debian.org/ wheezy/updates main contrib non-free\ndeb-src http://security.debian.org/ wheezy/updates main contrib non-free\n >> /etc/apt/sources.list
IV. VNC
To access your Debian in a graphical environment from your PC or your phone, you have to set up a VNC Server and install a Desktop Environment. Let's install VNC and LXDE.
We'll follow the steps described on the LXDE wiki:
Code:
su
# apt-get update
# apt-get install lxde
# apt-get install tightvncserver
Set up the VNC server by typing the following command, which will ask you to set two passwords (let the second password if you want):
Code:
# vncserver
Kill the session:
Code:
# vncserver -kill :1
Go to /root/.vnc/ and edit the xstartup file: comment out #/etc/X11/xsession and add these two lines:
icewm
lxsession
Click to expand...
Click to collapse
To start a VNC session, type "vncserver -geometry x". For the Nexus 4, we would type "vncserver -geometry 1184x768"
To access your Desktop Environment from your phone, download android-vnc-viewer and launch it.
In the password field, type your password. In the address field, type "127.0.0.1", in port type "5901" and select 24-bit color (4bpp).
V. Script
I've made three scripts to mount, launch and unmount Debian. Whenever you reboot your phone, you'll have to mount Debian, set the environment variables and chroot.
VI. Credit
All credit goes to them:
http://linux-expert.net/?Trucs_et_astuces___Android___Tutoriel_%3A_Chroot_Debian (in french)
http://forum.xda-developers.com/showthread.php?t=2312013
http://forum.xda-developers.com/showthread.php?t=631389
http://forum.xda-developers.com/showthread.php?t=1418546
http://forum.xda-developers.com/showpost.php?p=5671794&postcount=124
VNC
Sorry for my bad english, I hope this will help
EDIT: Feel free to correct me!
Hi, I have 2021 updates, if someone interested. Tested with rooted LineageOS 17 (selinux permissive - not sure if required, my ROM is permissive, didn't set it explicitly):
for 32-bit ARM, ext4 created by 64-bit Linux didn't work, obviously there is some 64-bit feature that was not supported at least with my kernel (3.14). I've in the end created the FS on the Android, but using "-O '^64bit'" could be sufficient in the Linux. UPDATE: I've in the end used F2FS instead of EXT4.
above mknod+losetup+mount didn't work for me (neither 'mount -o loop -t ext4 <img>'), I've used 'mount -t ext4 $(losetup -sf /sdcard/stable-armhf.img) $LINUXROOT' in the end (obviously the device name needs to be saved somewhere if one wants to cleanly umount)
there was issue with network access denied even if you are root, see here. I've fixed it by creating the group 'inet/3003' in the chroot and issuing 'newgrp inet' inside it (more details in the link).
Anyways, thanks a lot for the above instructions, it helped me much!
Hi all,
I've been trying to create a Stock Rooted Lollipop Rom for the last few days and I'm stuck. I was trying to do this without using the 5.0 exploits. I was originally on stock rooted 4.4.2 w/ Safestrap. I used muniz_ri's "[How-To] Update to N900V_NK1 - 4.4.4 and Keep Root" and got rooted 4.4.4. I next extracted the zip and tar file then reviewed what was in them. I tried to mimic what muniz_ri did and I was able to get the OB6 rom to boot but SuperSu force closed and I couldn't see su in /system/xbin, permission denied. I rooted with the exploit and unlocked bootloader and flashed Jasmine Rom. I've even attempted to create a flashable system.img with su and SuperSu and I get the hanging Verizon logo. If anyone can help I would appreciate it.
Thanks,
BlueKalel
out of curiosity I did a differential comparison of the system.img between the stock and "rooted" versions that @muniz_ri provided.
e.g.
Code:
$ echo 'Samsung NK1 stock system'
$ [b]simg2img[/b] stock_system.img.ext4 raw_system.img.ext4
$ su /bin/bash
# mkdir /tmp/nk1
# losetup /dev/loop0 raw_system.img.ext4
# mount -t ext4 -o ro /dev/loop0 /tmp/nk1
# (cd /tmp/nk1 ; find . -type f -exec md5sum {} \; ) 2>&1 | tee stock_system_md5s.txt
# chown user.user stock_system_md5s.txt
# umount /tmp/nk1
# losetup -d /dev/loop0
# rm raw_system.img.ext4
# echo 'Rooted NK1 system - not in sparse format, no need for simg2img'
# losetup /dev/loop0 rooted_system.img.ext4
# mount -t ext4 -o ro /dev/loop0 /tmp/nk1
# (cd /tmp/nk1 ; find . -type f -exec md5sum {} \; ) 2>&1 | tee rooted_system_md5s.txt
# chown user.user stock_system_md5s.txt
# umount /tmp/nk1
# rmdir /tmp/nk1
# losetup -d /dev/loop0
# exit
$
$ echo 'here is the magic'
$ cat rooted_system_md5s.txt stock_system_md5s.txt | sort +1 -2 | uniq -u 2>&1 | tee unique_file_listing.txt
The listing produced is all unique files between the two system images; note they can be unique for two reasons:
(1) A file of that path-name is only present in one but not the other (a file is deleted from one or added to one)
(2) A file of that path-name is present in both but has been modified. You'll see duplicate file path-names in this case.
Having done this comparison for the system images, some things seem rather evident in @muniz_ri deltas; but others are less obvious (note lib/libsupol.so appears in the rooted version)
Code:
e75410f8e31fe505adb26d6a07725689 ./app/Superuser.apk
04cdb55b01d687afa2e085e300cdbe77 ./bin/ddexe
c8bc38e34a3d0456de08f06ec6102956 ./bin/ddexe
c8bc38e34a3d0456de08f06ec6102956 ./bin/ddexe_real
c2d5c3f94c41024eedb4569779597cf6 ./bin/.ext/.su
7beeb0980b778711a4ca30c78a418346 ./csc/contents.db
d514e14350f60f8d6a72aabd6d505722 ./csc/customer.xml
9279436a75cb1012f9999aec603beb33 ./csc/default_application_order.xml
a78afd02d69756736fd8df51776fe588 ./csc/default_workspace_cp.xml
2d46ed4aacf78532d176fbcc0ccdde8f ./csc/default_workspace.xml
b72d13ff1e0e383fa513768313a85c58 ./csc/easylauncher_default_workspace.xml
7f8bb831c5ebbe1d9ad2148dfd57a5b4 ./csc/feature.xml
ab29f88da583a4e04c4d5be423b9ca06 ./csc/others.xml
e17ce2e847276854abf3ec37ca592d4a ./csc/sales_code.dat
2a2931bfef9a2d7c8fd5b6f93e3917c9 ./CSCVersion.txt
fc48464a541cf5dc039f1147f7365e1a ./etc/autorun.iso
d41d8cd98f00b204e9800998ecf8427e ./etc/csc_apks_list.txt
d41d8cd98f00b204e9800998ecf8427e ./etc/csc_remove_apks_list.txt
d41d8cd98f00b204e9800998ecf8427e ./etc/csc_ringtones_list.txt
d41d8cd98f00b204e9800998ecf8427e ./etc/csc_user_apks_list.txt
d41d8cd98f00b204e9800998ecf8427e ./etc/csc_user_remove_apks_list.txt
45f27ea81dacdd6ba8a0722bd1065d01 ./etc/enforceskippingpackages.txt
d41d8cd98f00b204e9800998ecf8427e ./etc/hidden_apks_list.txt
b026324c6904b2a9cb4b88d6d61c81d1 ./etc/.installed_su_daemon
75fe72f2c977635bf2182a1be274345b ./etc/install-recovery.sh
acb73ff1de53675b420a7b14b9eac263 ./finder_cp/cpdata.xml
98357ec8dd72bbcdc39677204bfe05a4 ./finder_cp/web_cp_logo_baidu.png
abea7fc2866484fe9bb86e5aa9b98d6d ./finder_cp/web_cp_logo_bing.png
529173df0ef025a403fa5e0af5bc05df ./finder_cp/web_cp_logo_daum.png
8809f9b7fcdb679a0d66c8c7e7271281 ./finder_cp/web_cp_logo_google.png
58400ecde3dc101babed2a5db8c5a95d ./finder_cp/web_cp_logo_naver.png
c9b13d0610cd161ef48ac69796627d8f ./finder_cp/web_cp_logo_yahoo.png
c2ca061f4f83b44dc6a01579c8236493 ./hidden/INTERNAL_SDCARD/mobitv/dca.config
d84e60fbfe2f9aea6c2fbf268fb9fa8a ./hidden/INTERNAL_SDCARD/mobitv/foa.config
863ed2e929f24ad577905e92308a8800 ./hidden/INTERNAL_SDCARD/Samsung/Music/Over_the_horizon_2013.mp3
8d97de61b73bc6345001aab0e5b2cfdf ./lib/libsupol.so
b00734ca4cbc75ab17e7f04d7d72606f ./sipdb/en_US.zip
e7d85e3154308a40cba592273b34fcc0 ./sipdb/es_US.zip
56e0a71b160da01cbacdd606f6a21d0c ./sipdb/ko_KR.zip
86661c0d2d76cebf4f2f98e5cedb1fba ./sipdb/vi_VN.zip
5b43113a786dd197457a7da544e417bf ./sipdb/zh_CN.zip
bedf281b2ca0cea7b578c56146f61cfb ./SW_Configuration.xml
d41d8cd98f00b204e9800998ecf8427e ./VODB/en_US/checked
3fab613e69ed7bbdb4037227f40b3e93 ./VODB/en_US/en_US-ak-cur.lite.res
d2c7826b54f158388d5d631f7cc4eb94 ./VODB/en_US/en_US.lang
fbb63aed41785d843a3ede94dd5ebba5 ./VODB/en_US/en_US-lk-text.lite.res
d0fddf901a952652d327db6d353c39c5 ./VODB/en_US/files.txt
d41d8cd98f00b204e9800998ecf8427e ./VODB/es_US/checked
37233ae458dc58cce4e1cf3dfc7199bf ./VODB/es_US/es_MX-ak-cur.lite.res
de0e1db152031b405c3f94786519553b ./VODB/es_US/es_MX-lk-text.lite.res
95bf163ae41a21bfb03bde5994d32b47 ./VODB/es_US/es_US.lang
1f5d5bb76aacf2ecaf4efaede1d2de27 ./VODB/es_US/files.txt
d41d8cd98f00b204e9800998ecf8427e ./VODB/ko_KR/checked
f147743aa0e4c81acb66bde88e540cb7 ./VODB/ko_KR/files.txt
daf9861d29a51e989c9a4349cab1f0d2 ./VODB/ko_KR/ko_KR_johab-ak-cur.lite.res
d8598fec91290155e692b48e35c00c14 ./VODB/ko_KR/ko_KR_johab-lk-text.lite.res
ce79e020530910f70cf99e1ef075338d ./VODB/ko_KR/ko_KR.lang
d41d8cd98f00b204e9800998ecf8427e ./VODB/vi_VN/checked
1826e916c633326238aece3f625068d8 ./VODB/vi_VN/files.txt
93dd91b00a3aa970f6cd287a51c86eb8 ./VODB/vi_VN/vi_VN-ak-cur.lite.res
a7858ae999d0595bed5364d116df7f90 ./VODB/vi_VN/vi_VN.lang
ee7501f7588d98febaafa095a8bab689 ./VODB/vi_VN/vi_VN-lk-text.lite.res
d41d8cd98f00b204e9800998ecf8427e ./VODB/zh_CN/checked
8507d9d93801d26c0c112f913aa4a1c0 ./VODB/zh_CN/files.txt
c914ab0bf6f02ea6c607813d4a60d911 ./VODB/zh_CN/zh_CN_gb18030-ak-cur.lite.res
a992e77a706e8be8b182d2829b946069 ./VODB/zh_CN/zh_CN_gb18030-lk-text.lite.res
1d1b38601002c263be46a7970f427aba ./VODB/zh_CN/zh_CN.lang
c6d2482325d35384ce19e34723bb7652 ./wallpaper/lockscreen_default_wallpaper.png
c2d5c3f94c41024eedb4569779597cf6 ./xbin/daemonsu
c2d5c3f94c41024eedb4569779597cf6 ./xbin/su
c2d5c3f94c41024eedb4569779597cf6 ./xbin/sugote
57dd3b21dfb238a3065299851db9fc91 ./xbin/sugote-mksh
521005a1a9a03e118db633e9626b7221 ./xbin/supolicy
Obviously, you will want to unpack the boot images & their ramdisks and follow a similar forensic procedure there.
Hope this helps. Obviously, this is not a comprehensive - for instance it won't flag differences in meta-data such as file modes (permissions), ownership, or extended attributes (which is how SElinux characteristics are stored). Those could easily also create issues if they differ.