Database Develop

[I9001] [SCRIPT] [ODIN] How to create an Odin package from a cwm-zip (or backup)

The script (see below) works as follows:
1. It takes the correct files from the BaseRom folder and copies them to the BuildOdin folder
2. If boot or recovery images exist in NewRom folder (extracted from the cwm zip) it will copy them to the BuildOdin folder too
3. It will create the system.img.ext4 file in the BuildOdin folder
4. It will copy the system folder in the NewRom folder to the system.img.ext4 file
5. It will tar and md5 the files in BuildOdin folder
So make sure you have:
1. The adsp.mbn, amss.mbn, cache.img.ext4 and preload.img.ext4 in the BaseRom folder
2. The boot.img and recovery.img in the NewRom folder (or BaseRom)
3. The system folder in the NewRom folder
And run the script
Code:
#!/bin/sh
echo 'Requesting password to allow running as root...'
sudo echo 'Thanks :)!'
# Make folder
if [ ! -d "BuildOdin" ]
then
mkdir BuildOdin
fi
# Copy BaseRom files
cp BaseRom/adsp.mbn BuildOdin/adsp.mbn
cp BaseRom/amss.mbn BuildOdin/amss.mbn
cp BaseRom/cache.img.ext4 BuildOdin/cache.img.ext4
cp BaseRom/preload.img.ext4 BuildOdin/preload.img.ext4
# Copy boot image
if [ -s NewRom/boot.img ]
then
cp NewRom/boot.img BuildOdin/boot.img
else
cp BaseRom/boot.img BuildOdin/boot.img
fi
# Copy recovery image
if [ -s NewRom/recovery.img ]
then
cp NewRom/recovery.img BuildOdin/recovery.img
else
cp BaseRom/recovery.img BuildOdin/recovery.img
fi
# Create system image
mysyssize=`du -s -h NewRom/system | awk 'BEGIN{FS="[M]"} {print $1}'`
mysyssizeincreased=$((mysyssize+50))
echo 'Filesize will be' $mysyssizeincreased 'MB'
echo 'dd empty image...'
dd if=/dev/zero of=BuildOdin/system.img.ext4 bs=1M count=$mysyssizeincreased >&- 2>&-
echo 'make it ext4...'
mke2fs -F -T ext4 BuildOdin/system.img.ext4 >&- 2>&-
echo 'mounting...'
sudo mount -t ext4 -o loop BuildOdin/system.img.ext4 /mnt >&- 2>&-
echo 'copying system...'
cp NewRom/system/* /mnt -rp
sync
echo 'unmounting...'
sudo umount /mnt
# Create Odin and Odin MD5 files
cd BuildOdin
echo 'tarring...'
tar -cf MyOdinpack.tar adsp.mbn amss.mbn boot.img cache.img.ext4 preload.img.ext4 recovery.img system.img.ext4
echo 'copying...'
cp MyOdinpack.tar MyOdinpack.tar.md5
echo 'md5sum...'
md5sum -t MyOdinpack.tar>>MyOdinpack.tar.md5
echo 'done!'
It looks like it works. I do have some stuff I am wondering about:
1. I have added 50 MB to the filesize, with 30 MB additional I still got a not enough diskspace error. Wondering why...
2. Will it work this way? When looking at a cwm-zip it does contain a system folder but they also contain some other stuff... who knows... anyone care to test?
Well, looks like it's not all that easy. The script works, it creates a file with the exact same files as the one created with dd on the device, but for some reason when using it in Odin, it doesn't work...
Creating the Odin package is superfast now, but will still require some more testing. I guess I should do it with a ROM that I have done before... but too lazy atm...
Btw, this way I could create an Odin package from a CWM backup too If ever needed, just let me know
Regards,
Nika.

you could try making system.img file, then rename it to system.img.ext4. Sound foolish probably, but sometimes these double extensions are just added as an indicator. in this case for the system to look up what partition type to take. (I could be horribly wrong tho. But there are like 0 tools on internet for an ext4 maker so not many options available)

Maybe create an empty ext4 image on PC, mount loopback in cwm and copy files to it.
Sent from my GT-I9001 using XDA App

Create image on your phone using busybox
Edit: I updated the script.
I played a bit with the busybox:
my working dir is /sdcard/external_sd/imgtest!
DD a file of ~300MB
busybox dd if=/dev/zero of=myimg.img bs=1M count=300
Create a ext4 filesystem on this img
busybox mke2fs -F -T ext4 -L Image myimg.img
Create a new /dev node, named "loop99", type "block device" (b), and some major and minor number
busybox mknod /dev/block/loop99 b 7 99
Prepare your new loop device with an img file (delete is with losetup -d /dev/block/loop99)
busybox losetup /dev/block/loop99 /sdcard/external_sd/imgtest/myimg.img
Mount it finally
busybox mount /dev/block/loop99 /sdcard/external_sd/imgtest/mymnt
Now you may copy what you want, say /system, to this img.
And unmount it (make sure it's not in use anymore)
busybox umount /dev/block/loop99
Maybe invoke some commands to check the size of /system? A quick one liner would be
busybox df /system -h | grep /system | awk 'BEGIN{FS="[M]"} {print $2}' | awk 'BEGIN{FS="[.]"} {print $1}'
Could be part of the shell script, saved to a variable and increased by some MB just to make sure^^
A very quick and dirty script:
#!/bin/sh
mysyssize=`busybox df /system -h | grep /system | awk 'BEGIN{FS="[M]"} {print $2}' | awk 'BEGIN{FS="[.]"} {print $1}'`
mysyssizeincreased=$((mysyssize+20))
mkdir /sdcard/external_sd/myimages
mkdir /sdcard/mnt/
mkdir /sdcard/mnt/mymnt
cd /sdcard/external_sd/myimages
echo Filesize is $mysyssizeincreased
echo Now dd a new image for your folder
echo dd in progress...
busybox dd if=/dev/zero of=myimgfile.img bs=1M count=$mysyssizeincreased
echo mke2fs with type ext4 on your file...
busybox mke2fs -F -T ext4 -L Imagename myimgfile.img
echo create new dev-node...
busybox mknod /dev/block/loop99 b 7 99
echo apply loopback setup on this node...
busybox losetup /dev/block/loop99 /sdcard/external_sd/myimages/myimgfile.img
echo mounting new image...
busybox mount /dev/block/loop99 /sdcard/mnt/mymnt
echo done!
echo
echo now copy your system files over preserving permissions...
cp /system/* /sdcard/mnt/mymnt -rp
sync
busybox umount /sdcard/mnt/mymnt
losetup -d /dev/block/loop99
rm /dev/block/loop99
echo done!
echo done!
echo done!
echo
Click to expand...
Click to collapse
Save as a .sh script and execute it. I tried with some ssh server on phone and shell on my PC.
Worked fine, but to be sure a test with a restore would be needed, so treat it as highly experimental.

Very nice, much appreciated!!! Will try (convert) them on ubuntu one of these days as I'd prefer to do the job on a dual-cpu machine

Well then you should skip the steps with mknod and so on. Mount is much more powerful there, so you should be able to do it with these commands:
dd if=/dev/zero of=/tmp/image bs=1M count=300
mkfs.ext4 /tmp/image
mount -o loop /tmp/image /mnt

Hmmm... getting a "is not a block special device" message when ext4-ing in linux. Either the command file is incorrect, or I need to suppress that message somehow... more news soon

Okay!! Here's the first version of the script:
Code:
#!/bin/sh
echo 'Requesting password to allow running as root...'
sudo echo 'Thanks :)!'
# Make folder
if [ ! -d "BuildOdin" ]
then
mkdir BuildOdin
fi
# Copy BaseRom files
cp BaseRom/adsp.mbn BuildOdin/adsp.mbn
cp BaseRom/amss.mbn BuildOdin/amss.mbn
cp BaseRom/cache.img.ext4 BuildOdin/cache.img.ext4
cp BaseRom/preload.img.ext4 BuildOdin/preload.img.ext4
# Copy boot image
if [ -s NewRom/boot.img ]
then
cp NewRom/boot.img BuildOdin/boot.img
else
cp BaseRom/boot.img BuildOdin/boot.img
fi
# Copy recovery image
if [ -s NewRom/recovery.img ]
then
cp NewRom/recovery.img BuildOdin/recovery.img
else
cp BaseRom/recovery.img BuildOdin/recovery.img
fi
# Create system image
mysyssize=`du -s -h NewRom/system | awk 'BEGIN{FS="[M]"} {print $1}'`
mysyssizeincreased=$((mysyssize+50))
echo 'Filesize will be' $mysyssizeincreased 'MB'
echo 'dd empty image...'
dd if=/dev/zero of=BuildOdin/system.img.ext4 bs=1M count=$mysyssizeincreased >&- 2>&-
echo 'make it ext4...'
mke2fs -F -T ext4 BuildOdin/system.img.ext4 >&- 2>&-
echo 'mounting...'
sudo mount -t ext4 -o loop BuildOdin/system.img.ext4 /mnt >&- 2>&-
echo 'copying system...'
cp NewRom/system/* /mnt -rp
sync
echo 'unmounting...'
sudo umount /mnt
# Create Odin and Odin MD5 files
cd BuildOdin
echo 'tarring...'
tar -cf MyOdinpack.tar adsp.mbn amss.mbn boot.img cache.img.ext4 preload.img.ext4 recovery.img system.img.ext4
echo 'copying...'
cp MyOdinpack.tar MyOdinpack.tar.md5
echo 'md5sum...'
md5sum -t MyOdinpack.tar>>MyOdinpack.tar.md5
echo 'done!'
It looks like it works. I do have some stuff I am wondering about:
1. I have added 50 MB to the filesize, with 30 MB additional I still got a not enough diskspace error. Wondering why...
2. Will it work this way? When looking at a cwm-zip it does contain a system folder but they also contain some other stuff... who knows... anyone care to test?
The script works as follows:
1. It takes the correct files from the BaseRom folder and copies them to the BuildOdin folder
2. If boot or recovery images exist in NewRom folder (extracted from the cwm zip) it will copy them to the BuildOdin folder too
3. It will create the system.img.ext4 file in the BuildOdin folder
4. It will copy the system folder in the NewRom folder to the system.img.ext4 file
5. It will tar and md5 the files in BuildOdin folder
So make sure you have:
1. The adsp.mbn, amss.mbn, cache.img.ext4 and preload.img.ext4 in the BaseRom folder
2. The boot.img and recovery.img in the NewRom folder (or BaseRom)
3. The system folder in the NewRom folder
And run the script
Regards,
Nika.

Well, looks like it's not all that easy. The script works, it creates a file with the exact same files as the one created with dd on the device, but for some reason when using it in Odin, it doesn't work...
Creating the Odin package is superfast now, but will still require some more testing. I guess I should do it with a ROM that I have done before... but too lazy atm...
Btw, this way I could create an Odin package from a CWM backup too If ever needed, just let me know

nikagl said:
Well, looks like it's not all that easy. The script works, it creates a file with the exact same files as the one created with dd on the device, but for some reason when using it in Odin, it doesn't work...
Creating the Odin package is superfast now, but will still require some more testing. I guess I should do it with a ROM that I have done before... but too lazy atm...
Btw, this way I could create an Odin package from a CWM backup too If ever needed, just let me know
Click to expand...
Click to collapse
I've been searching the forums for a general way to make Odin-flashable ROMs from CWM backups. I'm particularly interested in doing this for Samsung Galaxy 10.1/8.9/7.7 tabs (Honeycomb). Many tutorials use ADB and datadumps, which is fine but is very device-specific, and I haven't found one for the Honeycomb Galaxy Tabs. Using CWM backups seem cleanest and least-device specific way.
So I *AM* interested in how you would start with a full CWM backup, and (not using any base ROMs) get an Odin-flashable .tar.md5 file.

hmmmm bht ho gya hia yaar

kblam said:
I've been searching the forums for a general way to make Odin-flashable ROMs from CWM backups. I'm particularly interested in doing this for Samsung Galaxy 10.1/8.9/7.7 tabs (Honeycomb). Many tutorials use ADB and datadumps, which is fine but is very device-specific, and I haven't found one for the Honeycomb Galaxy Tabs. Using CWM backups seem cleanest and least-device specific way.
So I *AM* interested in how you would start with a full CWM backup, and (not using any base ROMs) get an Odin-flashable .tar.md5 file.
Click to expand...
Click to collapse
Hi kblam,
Well... it's still a work in progress. Not sure why it doesn't work at the moment, but here's my current script:
Code:
#!/bin/sh
echo 'Requesting password to allow running as root...'
sudo echo 'Thanks :)!'
# Make folder
if [ ! -d "BuildOdin" ]
then
mkdir BuildOdin
fi
# Copy BaseRom files
cp BaseRom/adsp.mbn BuildOdin/adsp.mbn
cp BaseRom/amss.mbn BuildOdin/amss.mbn
cp BaseRom/cache.img.ext4 BuildOdin/cache.img.ext4
cp BaseRom/preload.img.ext4 BuildOdin/preload.img.ext4
# Copy boot image
if [ -s NewRom/boot.img ]
then
cp NewRom/boot.img BuildOdin/boot.img
else
cp BaseRom/boot.img BuildOdin/boot.img
fi
# Copy recovery image
if [ -s NewRom/recovery.img ]
then
cp NewRom/recovery.img BuildOdin/recovery.img
else
cp BaseRom/recovery.img BuildOdin/recovery.img
fi
# Create system image
mysyssize=`du -s -h NewRom/system | awk 'BEGIN{FS="[M]"} {print $1}'`
mysyssizeincreased=$((mysyssize+50))
echo 'Filesize will be' $mysyssizeincreased 'MB'
echo 'dd empty image...'
dd if=/dev/zero of=BuildOdin/system.img.ext4 bs=1M count=$mysyssizeincreased >&- 2>&-
echo 'make it ext4...'
mke2fs -F -T ext4 BuildOdin/system.img.ext4 >&- 2>&-
echo 'mounting...'
sudo mount -t ext4 -o loop BuildOdin/system.img.ext4 /mnt >&- 2>&-
echo 'copying system...'
cp NewRom/system/* /mnt -rp
sync
echo 'unmounting...'
sudo umount /mnt
# Create Odin and Odin MD5 files
cd BuildOdin
echo 'tarring...'
tar -cf MyOdinpack.tar adsp.mbn amss.mbn boot.img cache.img.ext4 preload.img.ext4 recovery.img system.img.ext4
echo 'copying...'
cp MyOdinpack.tar MyOdinpack.tar.md5
echo 'md5sum...'
md5sum -t MyOdinpack.tar>>MyOdinpack.tar.md5
echo 'done!'
Taking out all unnessesary comments and commands, what it's supposed to do is the following:
1. First copy the files from the BaseRom (the ones you usually do not extract either):
Code:
cp BaseRom/adsp.mbn BuildOdin/adsp.mbn
cp BaseRom/amss.mbn BuildOdin/amss.mbn
cp BaseRom/cache.img.ext4 BuildOdin/cache.img.ext4
cp BaseRom/preload.img.ext4 BuildOdin/preload.img.ext4
2. Then take the boot and recovery from another folder as they usually need to be based on another kernel (f/e Skyhigh kernel ) and/or recovery (f/e CWM/Faemod):
Code:
cp NewRom/boot.img BuildOdin/boot.img
cp NewRom/recovery.img BuildOdin/recovery.img
3. Take the size of the new image (based on the system folder size + 50):
Code:
mysyssize=`du -s -h NewRom/system | awk 'BEGIN{FS="[M]"} {print $1}'`
mysyssizeincreased=$((mysyssize+50))
4. Create an empty system image
Code:
dd if=/dev/zero of=BuildOdin/system.img.ext4 bs=1M count=$mysyssizeincreased >&- 2>&-
5. Convert it to ext4
Code:
mke2fs -F -T ext4 BuildOdin/system.img.ext4 >&- 2>&-
6. Mount it and copy the new system files (can be unzipped from the cwm-zip) and unmount
Code:
sudo mount -t ext4 -o loop BuildOdin/system.img.ext4 /mnt >&- 2>&-
cp NewRom/system/* /mnt -rp
sync
sudo umount /mnt
7. The rest is same to building other md5 odin files. Combine them with tar and calculate and add the md5 sum
Code:
tar -cf MyOdinpack.tar adsp.mbn amss.mbn boot.img cache.img.ext4 preload.img.ext4 recovery.img system.img.ext4
cp MyOdinpack.tar MyOdinpack.tar.md5
md5sum -t MyOdinpack.tar>>MyOdinpack.tar.md5
As mentioned - I am not sure why the system image created this way does not work yet (I only tested it once) - maybe someone else is willing to test?
Regards,
Nika.

[Q] Odex Script For User (/data/app) Apps :)

Dear bros and members here,
I want some script for using dexopt-wrapper to some location
Example: if there is file in (/sdcard/app)
then the script should prompt two request:
the first is the apk file name
and the other is the odex file name and should execute
dexopt-wrapper /sdcard/app/name.of.the.apk /sdcard/app/name.of.the.odex
Please, I want this in shell script

Here you are:
Code:
#!/system/bin/sh
# In the name of Allah
tmp=/data/local/tmp
mkdir $tmp > /dev/null 2>&1
BCP="`cat /init.rc | grep BOOTCLASSPATH`"
echo $BCP>$tmp/fbcp.txt
sed -e 's/export BOOTCLASSPATH //g' $tmp/fbcp.txt>$tmp/bcp.txt
BCP="`cat $tmp/bcp.txt`"
rm $tmp/fbcp.txt
rm $tmp/bcp.txt
echo "Please enter the name of app to odex:"
echo "Example: Browser"
echo "--->"
read APP
if [ ! -f /sdcard/app/${APP}.apk ]; then
echo "Requested app not found."
echo "Please check the app name again."
else
dexopt-wrapper /sdcard/app/${APP}.apk /sdcard/app/${APP}.odex ${BCP}
zip -d /sdcard/app/${APP}.apk classes.dex
echo "Done!"
fi;
Sent from my E15i using Tapatalk 2

Ahmad.H said:
Here you are:
Code:
#!/system/bin/sh
# In the name of Allah
tmp=/data/local/tmp
mkdir $tmp > /dev/null 2>&1
BCP="`cat /init.rc | grep BOOTCLASSPATH`"
echo $BCP>$tmp/fbcp.txt
sed -e 's/export BOOTCLASSPATH //g' $tmp/fbcp.txt>$tmp/bcp.txt
BCP="`cat $tmp/bcp.txt`"
rm $tmp/fbcp.txt
rm $tmp/bcp.txt
echo "Please enter the name of app to odex:"
echo "Example: Browser"
echo "--->"
read APP
if [ ! -f /sdcard/app/${APP}.apk ]; then
echo "Requested app not found."
echo "Please check the app name again."
else
dexopt-wrapper /sdcard/app/${APP}.apk /sdcard/app/${APP}.odex ${BCP}
zip -d /sdcard/app/${APP}.apk classes.dex
echo "Done!"
fi;
Sent from my E15i using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot bro!

There's a syntax error.
I type in the terminal and output is looked like this
/sdcard/odex.sh: 4: Syntax error: Bad fd number
anyway, I fix it to
line 4: mkdir $tmp > /dev/null 2&>1
but it still doesn't work..
Many errors in shell script.. Please test it and correct something.. Please bro..
I really like your script if it would be executable because it has classes.dex delete function..
Thanks

Sailfish SDK on the Touchpad with libhybris

HP Touchpad running Sailfish SDK with libhybris....
Yep.. Using ICS\CM9 because I tried and tried and tried with CM10.1 and no go.
Started with an N950 Nokia Sailfish SDK Image from a meego thread.
=) You thought it would be a video of the touchpad and sailfish eh? Maybe later..
NOTE. There is ZERO Applications with this. It is just the SDK. Not worth messing with unless you REALLY want to. You WILL need to create a lvm partition that is /dev/store/ubuntu formatted as ext3 that is around 2gb or more.. And you will need to create some space on boot. Take a look at the Ubuntu Touch Partition Creator on the Ubuntu Touch thread.. or just create it yourself..
It is just like this except we have the touchscreen working and a mouse if you want with a y cable.
If you need help with Hybris give me a shout.. and you DO NOT have an HP Touchpad.. Read the end of my ubuntu touch thread or around page 30 and on to read what I did.
Jolla is about to come out with an awesome porting guide for the OS. And it just involves using the .zip file from cyanogenmod.. No recompiling. I just wanted to do this for fun.
hybris was not easy to install for ICS. I configured with ics headers and built with jb headers from nfc during make and removed test_gps from the Makefiles... do not run make clean.. just make install.
Woot Woot!
Thanks to STSKeeps... because.. he invented libhybris starting on a HP Touchpad. Yep.. I bet sailfish sdk has seen the touchpad before. =)
Thanks to.. SourenAraya from the meego thread.
http://talk.maemo.org/showthread.php?p=1387183
Not like Ubuntu Touch at all.. No LXC container.. no chroot.. just /system folder.. and you can use it.
http://gdurl.com/N-C1/download RootFS
http://gdurl.com/T0IP/download Kernel
This kernel uses a console=ttyS0 but your better off using console=ttyUSB0 and a prolific rs-232 to usb adapter... and getting a getty\console if you want to look around while its up. Or create the HP Touchpad headphone jack uart cable that requires a 4 pin headphone cable with a mic and stereo speakers. Google it.. I bought the cable but never spliced it.
Important files\folders that were changed
/system
/libhybris (make install only)
/headertest
/var/lib/environment/compositor/* (EGL_PLATFORM=null)
/usr/bin/wifi
/usr/bin/ts_srv
/lib/systemd/system/ts_srv.service
/lib/systemd/system/wifi.service
/lib/systemd/system/default.target.wants
/lib/modules
/lib/firmware
.bashrc
That is where the root filesystems differ. /usr/bin/wifi does more then you think.

My notes.. in case I lose this file.. most of the info here is not useful.. but.. whatever.
Got Tearing???? hehehe
cp arch/arm/boot/uImage ~/moboot/tools
cd ~/moboot/tools
rm uImage.Mer
rm uRamdisk
rm kernel.img
./uimage-extract uImage
rm uImage
mkimage -A arm -O linux -T kernel -C none -a 0x40208000 -e 0x40208000 -n "Kernel" -d kernel.img uImage
mkimage -A arm -O linux -T ramdisk -C none -a 0x60000000 -e 0x60000000 -n "Image" -d ramdisk.img uRamdisk
mkimage -A arm -O linux -T multi -a 0x40208000 -e 0x40208000 -C none -n "multi image" -d uImage:uRamdisk uImage.Mer
cat uImage.Mer | novacom put finemo-apps-wayland | Nemo Apps | pattern
| nemo-complete-wayland | Nemo Comple-> | pattern
| nemo-mobile-session-wayland | Wayland con-> | package
| nemo-rnd-wayland | Nemo RND Wa-> | pattern
| nemo-ux-wayland le:///boot/uImage.Mer
sed -i '$ a nameserver 8.8.8.8' > /etc/resolv.conf
echo "nameserver 8.8.8.8" > /etc/resolv.conf
./autogen.sh --prefix=/usr --enable-wayland --with-android-headers=/headertest --with-default-egl-platform=ics --enable-debug --enable-mesa --enable-trace
./autogen.sh --prefix=/usr --enable-debug --enable-mesa --enable-trace --enable-alinker=jb
QT_QPA_EGLFS_DEPTH=24 /usr/lib/qt5/bin/qmlscene -platform eglfs
QT_QPA_EGLFS_DEPTH=32 /usr/lib/qt5/bin/qmlscene -platform eglfs
QT_QPA_EGLFS_DEPTH=16 /usr/lib/qt5/bin/qmlscene -platform eglfs
QT_QPA_EGLFS_PHYSICAL_WIDTH=1024 QT_QPA_EGLFS_PHYSICAL_HEIGHT=768
QT_WAYLAND_GL_CONFIG=brcm_egl QT_QPA_EGLFS_WIDTH=1024 QT_QPA_EGLFS_HEIGHT=768 QT_QPA_EGLFS_DEPTH=24 QT_QPA_PLATFORM=eglfs /usr/lib/qt5/bin/qmlscene -platform eglfs ./usr/lib/qt5/examples/qtwayland/qml-compositor/main.qml
QT_QPA_EGLFS_HIDECURSOR=1 QT_QPA_EGLFS_PHYSICAL_WIDTH=400 QT_QPA_EGLFS_PHYSICAL_HEIGHT=300 QT_QPA_EGLFS_DEPTH=24 /usr/lib/qt5/bin/qmlscene -platform eglfs
zypper install make gcc automake libtool wayland-devel gcc-c++ libX11-devel
./autogen.sh --prefix=/usr --enable-wayland --with-android-headers=/headertest --enable-mesa --enable-debug --enable-trace --with-default-egl-platform=null
make
make install
[[email protected] libhybris]# mv eglplatform_null.la eglplatform_jb.la
[[email protected] libhybris]# mv eglplatform_null.so eglplatform_jb.so
test_glesv2 works!
gpasswd -a nemo hybris
gpasswd -a root hybris
echo 5.9.68.173 repo.pub.meego.com | tee -a /etc/hosts
echo 5.9.68.173 releases.nemomobile.org | tee -a /etc/hosts
move hybris into external!!!!
remove sgx and n950 stuff
egl-utils eglext-tests!!!!!!!!!!!!!!!!!!
releases.nemomobile.org
zypper in qt5-qtwayland-wayland_egl-examples qt5-plugin-imageformat-jpeg qt5-plugin-platform-eglfs qt5-qtsvg-plugin-imageformat-svg gettext
./autogen.sh --prefix=/usr --enable-gallium-llvm --enable-gallium-egl --with-state-trackers=egl --enable-glew=no --enable-glw=no --enable-glut=no --enable-gles1=yes --enable-gles2=yes --enable-egl=yes --enable-gallium-egl --enable-osmesa=no --with-egl-platforms=fbdev,wayland --enable-glx-tls --enable-glx=yes --enable-dri=no
/home/justin/UTA/ubuntu/hybris ./usr/lib/qt5/examples/qtwayland/qml-compositor/WindowChrome.qml
PRODUCT_PACKAGES += \
libcamera_compat_layer \
libis_compat_layer \
libmedia_compat_layer \
libsf_compat_layer \
libui_compat_layer \
direct_camera_test \
direct_input_test \
direct_media_test \
direct_sf_test \
libubuntu_application_api \
ubuntuappmanager \
ubuntu_chroot \
uchroot \
upstart-property-watcher
./autogen.sh --prefix=/usr --with-x --enable-gallium-llvm --with-dri-drivers=swrast --with-state-trackers=egl --enable-glew=no --enable-glw=no --enable-glut=no --enable-gles1=yes --enable-gles2=yes --enable-egl=yes --enable-gallium-egl --enable-osmesa=no --with-gallium-drivers=swrast --with-egl-platforms=x11,fbdev,wayland --enable-glx-tls --enable-glx=yes --enable-dri
nemo-apps-wayland | Nemo Apps | pattern
| nemo-complete-wayland | Nemo Comple-> | pattern
| nemo-mobile-session-wayland | Wayland con-> | package
| nemo-rnd-wayland | Nemo RND Wa-> | pattern
| nemo-ux-wayland
Sat Nov 16 17:09:11 EET 2013
./autogen.sh --prefix=/usr --with-x --enable-gallium-llvm --with-dri-drivers=swrast --with-state-trackers=egl --enable-glew=no --enable-glw=no --enable-glut=no --enable-gles1=yes --enable-gles2=yes --enable-egl=yes --enable-gallium-egl --enable-osmesa=no --with-egl-platforms=x11,fbdev,wayland --enable-glx-tls --enable-glx=yes --enable-dri
PATH="/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/home/nemo/bin:/sbin"
Sat Nov 16 17:09:11 EET 2013
I/gralloc (19700): width = 163 mm (159.568 dpi)
I/gralloc (19700): height = 122 mm (159.895 dpi)
QT_QPA_EGLFS_PHYSICAL_WIDTH=163 QT_QPA_EGLFS_PHYSICAL_HEIGHT=122 QT_QPA_EGLFS_DEPTH=32 QT_QPA_PLATFORM=eglfs /usr/lib/qt5/bin/qmlscene -platform eglfs
I/SurfaceFlinger( 1111): EGLSurface: 8-8-8-0, config=0x7
cd /dev
rm -f /dev/log
mkdir /dev/log
chmod 777 /dev/log
cd /dev/log
ln -s /dev/log_main main
ln -s /dev/log_system system
ln -s /dev/log_events events
ln -s /dev/log_radio radio
mkdir /dev/graphics
cd /dev/graphics
ln -s /dev/fb0 fb0
chmod 666 /dev/graphics/fb0
chmod 666 /dev/fb0
chmod 666 /dev/genlock
chmod 666 /dev/log*
chmod 666 /dev/log/*
chmod 666 /dev/kgsl*

Looks promising!. I can't wait to try Jolla on my tablet, long live the Touchpad

you make my day man, now waiting for jola
thank you

Hi, there this sounds great.
Can you Tell me where I find instructions for installing Nemo Mobile on the TP?
I Remember having it installed on the N900 about 2 years ago.
Thanks a lot:fingers-crossed:

Coffee Cactus said:
Hi, there this sounds great.
Can you Tell me where I find instructions for installing Nemo Mobile on the TP?
I Remember having it installed on the N900 about 2 years ago.
Thanks a lot:fingers-crossed:
Click to expand...
Click to collapse
I have a private image and kernel that runs it. It doesnt do that much.. I think. I haven't really played with it.. I did have a gui and touch though.
I suppose I can retry with 3.0.1 and then upload it....
I got the nemo thing from... hmm how did I build it? For nemo.. I think I built it from the instructions for another device.. then I compiled my own /system folder and compiled libhybris. Got that working.
Then I went after Qt5.. Then it worked. It was also a pain to get hybris to work with ics.. that I remember.
OH.. move hybris into external!!!!
remove sgx and n950 stuff
egl-utils eglext-tests!!!!!!!!!!!!!!!!!!
Most likely I compiled an image for the Nexus or just downloaded one, but then after it booted on the touchpad kernel with the nemo ramdisk built into the kernel and most likely modified, I started to remove stuff with yum or whatever.. before recompiling hybris.. the n950 packages screwed stuff up and broke the touchscreen?
Anyway.. it ended up working.. don't think I tested sound or bluetooth or wifi though. pretty sure settings was blank? Nemo needed more work? Doubt that will happen because of Jolla and Sailfish.

Ho to back up of the whole memory block (via adb)

Dears maybe now I can make double post but I hang on that step from guide from this site.
Phone is after wipe data and I need rescue data from it for that I want to make RAW image to recover data.
What I do until now:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
but in results get:
1|ASUS_I001_1:/ # /system/xbin/busybox nc -1 -p 5555 -e /system/xbin/busybox dd
5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0 <
nc: invalid option -- 1
BusyBox v1.32.0-Stericson (2020-07-18 18:33:24 EDT) multi-call binary.
Usage: nc [OPTIONS] HOST PORT - connect
nc [OPTIONS] -l -p PORT [HOST] [PORT] - listen
-e PROG Run PROG after connect (must be last)
-l Listen mode, for inbound connects
-lk With -e, provides persistent server
-p PORT Local port
-s ADDR Local address
-w SEC Timeout for connects and final net reads
-i SEC Delay interval for lines sent
-n Don't do DNS resolution
-u UDP mode
-v Verbose
-o FILE Hex dump traffic
-z Zero-I/O mode (scanning)
1|ASUS_I001_1:/ #
Why I get that this parameter is invalid:
nc: invalid option -- 1
And to the end, if that don't work to me, next step also don't work.
Open another Cygwin terminal and type:
Code:
adb forward tcp:5555 tcp:5555
cd /path/to/store/the/backup ---> this is correct, should I creat some folder on HHD and insert here his name?
nc 127.0.0.1 5555 | pv -i 0.5 > mmcblk0.raw --> that means I should have ftp serwer?

[CLOSED]How make copy all android via adb

Mod edit: @Vergiliusz Thread closed as duplicate of
Ho to back up of the whole memory block (via adb)
Dears maybe now I can make double post but I hang on that step from guide from this site. Phone is after wipe data and I need rescue data from it for that I want to make RAW image to recover data. What I do until now: adb forward tcp:5555...
forum.xda-developers.com
Please review the XDA Forum Rules with special emphasis on rule no. 5 and post only once - and such a subject not in development!
Regards
Oswald Boelcke
Dears maybe now I can make double post but I hang on that step from guide from this site.
Phone is after wipe data and I need rescue data from it for that I want to make RAW image to recover data.
What I do until now:
adb forward tcp:5555 tcp:5555
adb shell
su
/system/xbin/busybox nc -l -p 5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0
but in results get:
1|ASUS_I001_1:/ # /system/xbin/busybox nc -1 -p 5555 -e /system/xbin/busybox dd
5555 -e /system/xbin/busybox dd if=/dev/block/mmcblk0 <
nc: invalid option -- 1
BusyBox v1.32.0-Stericson (2020-07-18 18:33:24 EDT) multi-call binary.
Usage: nc [OPTIONS] HOST PORT - connect
nc [OPTIONS] -l -p PORT [HOST] [PORT] - listen
-e PROG Run PROG after connect (must be last)
-l Listen mode, for inbound connects
-lk With -e, provides persistent server
-p PORT Local port
-s ADDR Local address
-w SEC Timeout for connects and final net reads
-i SEC Delay interval for lines sent
-n Don't do DNS resolution
-u UDP mode
-v Verbose
-o FILE Hex dump traffic
-z Zero-I/O mode (scanning)
1|ASUS_I001_1:/ #
Why I get that this parameter is invalid:
nc: invalid option -- 1
And to