Kobo Vox Hacking Progress - Page 15

mightyzazz · 10-01-2014, 07:05 PM

Hi Everyone. My kids have been enjoying their rooted vox's immensely - thanks. I have a perhaps overly ambitious question, but I was wondering how easy it would be for me to try and upgrade the android version on one of these machines? I am sure it is out of my depth, but is it even feasible? Is all I have to lose an sd card?

Cheers,

Roberto.

Difflugia · 10-03-2014, 09:47 AM

Quote:

Originally Posted by mightyzazz

Hi Everyone. My kids have been enjoying their rooted vox's immensely - thanks. I have a perhaps overly ambitious question, but I was wondering how easy it would be for me to try and upgrade the android version on one of these machines? I am sure it is out of my depth, but is it even feasible? Is all I have to lose an sd card?

Cheers,

Roberto.

Kobo has stopped supporting the Vox and no third party ever supported the Vox hardware in new Android releases. At this point, it is what it is.

hecatae · 11-16-2014, 04:43 PM

Latest sourcecode for our kobo vox imx51 chipsets:

http://www.freescale.com/webapp/sps/...ode=IMXANDROID

still gingerbread, 2.3.4 from what I can tell,

mightyzazz · 11-21-2014, 06:54 AM

I am sure this is a dumb question, but what does that mean? Will I be able to update the vox in some way in the future?
Thanks,

Roberto.

Difflugia · 11-21-2014, 10:21 AM

Quote:

Originally Posted by mightyzazz

I am sure this is a dumb question, but what does that mean? Will I be able to update the vox in some way in the future?
Thanks,

Roberto.

It's not a dumb question.

The linked code is what's known as a "reference implementation" of Android and is probably what Kobo started with. Even if the code works as-is on a Vox (not a foregone conclusion), it is still the same major version (Gingerbread) that's already on the Vox, so it doesn't offer a path to upgrading to Jellybean or Kit Kat.

mightyzazz · 11-22-2014, 03:56 PM

Thanks for the info. I have already learnt so much from you and am always keen to push things further and give stuff a try, even if the improvements (if any!) are minimal.

Roberto.

mightyzazz · 12-27-2014, 04:53 PM

Hi Difluggia, me again. Hope you can help me out one more time. I needed to redo the whole vox hacking/expansion. Everything seemed to go fine, as I now have a bit more knowledge of Linux, and Lubuntu also kindly gives me visual clues of folder locations much like windows, so i know where things are located now and can see when a lot of things go wrong. However, my end result this time was an unrooted but expanded sd card, with no errors detected. There was a deviation from your protocol, however, because your link for the Superuser-3.1.3-arm-signed.zip gave a server not found message repeatedly, so in the end I found another one from a google search, which appears to be the same size etc. A close comparison of your protocol and my terminal info shows this only? discrepancy - could this be where I am going wrong? Your protocol:-

total 169040
drwxr-xr-x 4 bowz users 4096 Jan 19 18:21 .
drwxr-xr-x 193 bowz users 16384 Jan 19 18:18 ..
-rw------- 1 bowz users 1324669 Jan 19 17:56 Superuser-3.1.3-arm-signed.zip
drwxr-xr-x 2 bowz users 4096 Jan 19 18:16 fwparts
drwxr-xr-x 4 bowz users 4096 Jan 19 17:56 superuser
-rw-r--r-- 1 bowz users 171558652 Jan 19 18:21 update.zip

mine instead reads:-

total 168852
drwxrwxr-x 4 office office 4096 Dec 28 06:45 .
drwxr-xr-x 20 office office 4096 Dec 28 06:38 ..
drwxrwxr-x 2 office office 4096 Dec 28 06:40 fwparts
drwxrwxr-x 4 office office 4096 Dec 28 06:39 superuser
-rw-r--r-- 1 office office 1324669 Dec 26 18:09 Superuser-3.1.3-arm-signed.zip

Any ideas? Like I said, the copying of files and expansion, seemed to work - it looks like either the su file did not successfully get included, or has not been detected.

Thanks,

Roberto.

Below is the full extent of my work, in case my error was elsewhere. As you can see, I attempted this a couple of times, and only moved files/destinations where they are put in different places on lubuntu.

office@office:~$ tail -f /var/log/syslog
Dec 28 06:32:19 office kernel: [ 114.712085] usb 3-2: new full-speed USB device number 3 using uhci_hcd
Dec 28 06:32:32 office dbus[437]: [system] Activating service name='org.freedesktop.UPower' (using servicehelper)
Dec 28 06:32:32 office dbus[437]: [system] Successfully activated service 'org.freedesktop.UPower'
Dec 28 06:32:34 office kernel: [ 129.824067] usb 3-2: device descriptor read/64, error -110
Dec 28 06:32:49 office kernel: [ 145.040050] usb 3-2: device descriptor read/64, error -110
Dec 28 06:32:49 office kernel: [ 145.256042] usb 3-2: new full-speed USB device number 4 using uhci_hcd
Dec 28 06:33:00 office kernel: [ 155.664034] usb 3-2: device not accepting address 4, error -110
Dec 28 06:33:00 office kernel: [ 155.776105] usb 3-2: new full-speed USB device number 5 using uhci_hcd
Dec 28 06:33:10 office kernel: [ 166.184033] usb 3-2: device not accepting address 5, error -110
Dec 28 06:33:10 office kernel: [ 166.184090] hub 3-0:1.0: unable to enumerate USB device on port 2
Dec 28 06:34:25 office kernel: [ 241.510097] usb 1-8: USB disconnect, device number 6
Dec 28 06:34:25 office udisksd[1281]: Cleaning up mount point /media/office/9016-4EF8 (device 8:17 no longer exist)
Dec 28 06:34:26 office kernel: [ 241.580179] FAT-fs (sdb1): unable to read boot sector to mark fs as dirty
Dec 28 06:34:38 office kernel: [ 253.696075] usb 1-7: new high-speed USB device number 7 using ehci-pci
Dec 28 06:34:38 office kernel: [ 253.829199] usb 1-7: New USB device found, idVendor=14cd, idProduct=121c
Dec 28 06:34:38 office kernel: [ 253.829206] usb 1-7: New USB device strings: Mfr=1, Product=3, SerialNumber=2
Dec 28 06:34:38 office kernel: [ 253.829211] usb 1-7: Product: Mass Storage Device
Dec 28 06:34:38 office kernel: [ 253.829215] usb 1-7: Manufacturer: Generic
Dec 28 06:34:38 office kernel: [ 253.829219] usb 1-7: SerialNumber: 812320100708
Dec 28 06:34:38 office kernel: [ 253.829698] usb-storage 1-7:1.0: USB Mass Storage device detected
Dec 28 06:34:38 office kernel: [ 253.831307] scsi5 : usb-storage 1-7:1.0
Dec 28 06:34:38 office mtp-probe: checking bus 1, device 7: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-7"
Dec 28 06:34:38 office mtp-probe: bus: 1, device: 7 was not an MTP device
Dec 28 06:34:39 office kernel: [ 254.828796] scsi 5:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
Dec 28 06:34:39 office kernel: [ 254.829511] sd 5:0:0:0: Attached scsi generic sg2 type 0
Dec 28 06:34:39 office kernel: [ 255.124822] sd 5:0:0:0: [sdb] 30898176 512-byte logical blocks: (15.8 GB/14.7 GiB)
Dec 28 06:34:39 office kernel: [ 255.125524] sd 5:0:0:0: [sdb] Write Protect is off
Dec 28 06:34:39 office kernel: [ 255.125532] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
Dec 28 06:34:39 office kernel: [ 255.126138] sd 5:0:0:0: [sdb] No Caching mode page found
Dec 28 06:34:39 office kernel: [ 255.126144] sd 5:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 06:34:39 office kernel: [ 255.130782] sd 5:0:0:0: [sdb] No Caching mode page found
Dec 28 06:34:39 office kernel: [ 255.130790] sd 5:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 06:34:39 office kernel: [ 255.131787] sdb: sdb1
Dec 28 06:34:39 office kernel: [ 255.138776] sd 5:0:0:0: [sdb] No Caching mode page found
Dec 28 06:34:39 office kernel: [ 255.138786] sd 5:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 06:34:39 office kernel: [ 255.138792] sd 5:0:0:0: [sdb] Attached SCSI removable disk
Dec 28 06:34:39 office kernel: [ 255.462438] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Dec 28 06:34:39 office udisksd[1281]: Mounted /dev/sdb1 at /media/office/9016-4EF8 on behalf of uid 1000
^C
office@office:~$ ^C
office@office:~$ cd
office@office:~$ rm -rf vox
office@office:~$ mkdir vox
office@office:~$ cd vox
office@office:~/vox$ mkdir superuser
office@office:~/vox$ cd superuser
office@office:~/vox/superuser$ unzip ~/Downloads/Superuser-3.1.3-arm-signed.zip
Archive: /home/office/Downloads/Superuser-3.1.3-arm-signed.zip
signed by SignApk
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: system/app/Superuser.apk
inflating: system/bin/su
office@office:~/vox/superuser$ cd ..
office@office:~/vox$ cd fwparts
office@office:~/vox/fwparts$ cat x* > ../update.zip
office@office:~/vox/fwparts$ cd ..
office@office:~/vox$ ls -al
total 167556
drwxrwxr-x 4 office office 4096 Dec 28 06:41 .
drwxr-xr-x 20 office office 4096 Dec 28 06:38 ..
drwxrwxr-x 2 office office 4096 Dec 28 06:40 fwparts
drwxrwxr-x 4 office office 4096 Dec 28 06:39 superuser
-rw-rw-r-- 1 office office 171559138 Dec 28 06:41 update.zip
office@office:~/vox$ cd fwparts
office@office:~/vox/fwparts$ cat x* > ../update.zip
office@office:~/vox/fwparts$ cd ..
office@office:~/vox$ ls -al
total 168852
drwxrwxr-x 4 office office 4096 Dec 28 06:45 .
drwxr-xr-x 20 office office 4096 Dec 28 06:38 ..
drwxrwxr-x 2 office office 4096 Dec 28 06:40 fwparts
drwxrwxr-x 4 office office 4096 Dec 28 06:39 superuser
-rw-r--r-- 1 office office 1324669 Dec 26 18:09 Superuser-3.1.3-arm-signed.zip
-rw-rw-r-- 1 office office 171559138 Dec 28 06:45 update.zip
office@office:~/vox$ mkdir update
office@office:~/vox$ cd update
office@office:~/vox/update$ unzip ../update.zip
Archive: ../update.zip
signed by SignApk
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA
inflating: META-INF/com/google/android/update-binary
inflating: META-INF/com/google/android/updater-script
inflating: build.prop
inflating: recovery-uramdisk.img
inflating: system.img
inflating: u-boot.bin
inflating: uImage
extracting: update
inflating: uramdisk.img
office@office:~/vox/update$ cd ..
office@office:~/vox$ mkdir imagemount
office@office:~/vox$ su
Password:
root@office:/home/office/vox# mount -t ext4 update/system.img imagemount -o looproot@office:/home/office/vox# cp superuser/system/app/Superuser.apk imagemount/app/
root@office:/home/office/vox# cp superuser/system/bin/su imagemount/bin/
root@office:/home/office/vox# chmod 4755 imagemount/bin/su
root@office:/home/office/vox# umount imagemount
root@office:/home/office/vox# exit
exit
office@office:~/vox$ cd update
office@office:~/vox/update$ zip -r9 ../update-rooted.zip .
adding: system.img (deflated 37%)
adding: uImage (deflated 1%)
adding: build.prop (deflated 53%)
adding: u-boot.bin (deflated 45%)
adding: uramdisk.img (deflated 0%)
adding: recovery-uramdisk.img (deflated 0%)
adding: META-INF/ (stored 0%)
adding: META-INF/CERT.SF (deflated 42%)
adding: META-INF/com/ (stored 0%)
adding: META-INF/com/google/ (stored 0%)
adding: META-INF/com/google/android/ (stored 0%)
adding: META-INF/com/google/android/updater-script (deflated 73%)
adding: META-INF/com/google/android/update-binary (deflated 35%)
adding: META-INF/CERT.RSA (deflated 31%)
adding: META-INF/MANIFEST.MF (deflated 42%)
adding: update (stored 0%)
office@office:~/vox/update$ cd ..
office@office:~/vox$ tail -f /var/log/syslog
Dec 28 06:37:22 office anacron[882]: Job `cron.daily' terminated
Dec 28 06:37:22 office anacron[882]: Normal exit (1 job run)
Dec 28 06:47:01 office CRON[2136]: (root) CMD (test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ))
Dec 28 06:48:40 office kernel: [ 1096.498922] EXT4-fs (loop0): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 06:52:11 office kernel: [ 1306.740076] hub 1-0:1.0: over-current condition on port 8
Dec 28 06:52:11 office kernel: [ 1307.524051] usb 1-8: new high-speed USB device number 8 using ehci-pci
Dec 28 06:52:12 office kernel: [ 1307.657174] usb 1-8: New USB device found, idVendor=14cd, idProduct=121c
Dec 28 06:52:12 office kernel: [ 1307.657181] usb 1-8: New USB device strings: Mfr=1, Product=3, SerialNumber=2
Dec 28 06:52:12 office kernel: [ 1307.657186] usb 1-8: Product: Mass Storage Device
Dec 28 06:52:12 office kernel: [ 1307.657190] usb 1-8: Manufacturer: Generic
Dec 28 06:52:12 office kernel: [ 1307.657194] usb 1-8: SerialNumber: 812320100708
Dec 28 06:52:12 office kernel: [ 1307.657693] usb-storage 1-8:1.0: USB Mass Storage device detected
Dec 28 06:52:12 office kernel: [ 1307.659363] scsi6 : usb-storage 1-8:1.0
Dec 28 06:52:12 office mtp-probe: checking bus 1, device 8: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-8"
Dec 28 06:52:12 office mtp-probe: bus: 1, device: 8 was not an MTP device
Dec 28 06:52:13 office kernel: [ 1308.656651] scsi 6:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
Dec 28 06:52:13 office kernel: [ 1308.657378] sd 6:0:0:0: Attached scsi generic sg2 type 0
Dec 28 06:52:13 office kernel: [ 1308.798575] sd 6:0:0:0: [sdb] 15523840 512-byte logical blocks: (7.94 GB/7.40 GiB)
Dec 28 06:52:13 office kernel: [ 1308.799188] sd 6:0:0:0: [sdb] Write Protect is off
Dec 28 06:52:13 office kernel: [ 1308.799194] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
Dec 28 06:52:13 office kernel: [ 1308.799812] sd 6:0:0:0: [sdb] No Caching mode page found
Dec 28 06:52:13 office kernel: [ 1308.799818] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 06:52:13 office kernel: [ 1308.805315] sd 6:0:0:0: [sdb] No Caching mode page found
Dec 28 06:52:13 office kernel: [ 1308.805322] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 06:52:13 office kernel: [ 1308.815959] sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 > sdb4
Dec 28 06:52:13 office kernel: [ 1308.819718] sd 6:0:0:0: [sdb] No Caching mode page found
Dec 28 06:52:13 office kernel: [ 1308.819729] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 06:52:13 office kernel: [ 1308.819739] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Dec 28 06:52:14 office kernel: [ 1309.663262] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 06:52:14 office udisksd[1281]: Mounted /dev/sdb1 at /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b on behalf of uid 1000
Dec 28 06:52:14 office kernel: [ 1309.694964] FAT-fs (sdb4): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Dec 28 06:52:14 office kernel: [ 1309.706793] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 06:52:14 office udisksd[1281]: Mounted /dev/sdb4 at /media/office/KOBOVOX on behalf of uid 1000
Dec 28 06:52:14 office kernel: [ 1309.780331] EXT4-fs (sdb6): warning: checktime reached, running e2fsck is recommended
Dec 28 06:52:14 office kernel: [ 1309.784799] EXT4-fs (sdb6): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 06:52:14 office udisksd[1281]: Mounted /dev/sdb2 at /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b1 on behalf of uid 1000
Dec 28 06:52:14 office kernel: [ 1309.820229] EXT4-fs (sdb5): warning: checktime reached, running e2fsck is recommended
Dec 28 06:52:14 office kernel: [ 1309.830549] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 06:52:14 office udisksd[1281]: Mounted /dev/sdb6 at /media/office/151028b9-8c2f-49ba-8d70-5f2148f2c09e on behalf of uid 1000
Dec 28 06:52:14 office udisksd[1281]: Mounted /dev/sdb5 at /media/office/3df28825-869b-4e96-9de1-a8286fafff19 on behalf of uid 1000
su
^C
office@office:~/vox$ su
Password:
root@office:/home/office/vox# umount /dev/sdb1
root@office:/home/office/vox# umount /dev/sdb2
root@office:/home/office/vox# umount /dev/sdb3
umount: /dev/sdb3: not mounted
root@office:/home/office/vox# umount /dev/sdb4
root@office:/home/office/vox# umount /dev/sdb5
root@office:/home/office/vox# umount /dev/sdb6
root@office:/home/office/vox# exit
exit
office@office:~/vox$ su
Password:
root@office:/home/office/vox# dd if=/dev/sdb of=./vox_image.bin bs=512
15523840+0 records in
15523840+0 records out
7948206080 bytes (7.9 GB) copied, 459.955 s, 17.3 MB/s
root@office:/home/office/vox# exit
exit
office@office:~/vox$ tail -f /var/log/syslog
Dec 28 07:04:41 office kernel: [ 2056.797827] sd 7:0:0:0: [sdb] No Caching mode page found
Dec 28 07:04:41 office kernel: [ 2056.797838] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 07:04:41 office kernel: [ 2056.806206] sd 7:0:0:0: [sdb] No Caching mode page found
Dec 28 07:04:41 office kernel: [ 2056.806218] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 07:04:41 office kernel: [ 2056.807238] sdb: sdb1
Dec 28 07:04:41 office kernel: [ 2056.815084] sd 7:0:0:0: [sdb] No Caching mode page found
Dec 28 07:04:41 office kernel: [ 2056.815097] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 07:04:41 office kernel: [ 2056.815107] sd 7:0:0:0: [sdb] Attached SCSI removable disk
Dec 28 07:04:41 office kernel: [ 2057.426312] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Dec 28 07:04:41 office udisksd[1281]: Mounted /dev/sdb1 at /media/office/9016-4EF8 on behalf of uid 1000
^C
office@office:~/vox$ su
Password:
root@office:/home/office/vox# umount /dev/sdb1
root@office:/home/office/vox# exit
exit
office@office:~/vox$ su
Password:
root@office:/home/office/vox# dd if=./vox_image.bin of=/dev/sdb bs=512
15523840+0 records in
15523840+0 records out
7948206080 bytes (7.9 GB) copied, 2272.87 s, 3.5 MB/s
root@office:/home/office/vox# exit
exit
office@office:~/vox$ tail -f /var/log/syslog
Dec 28 07:44:34 office AptDaemon.Worker: INFO: Simulating trans: /org/debian/apt/transaction/c603ca103ed849038dac72029669fa40
Dec 28 07:44:37 office AptDaemon.Worker: INFO: Committing packages: dbus.Array([dbus.String('kpat')], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s')), dbus.Array([], signature=dbus.Signature('s'))
Dec 28 07:44:50 office AptDaemon.Worker: INFO: Processing transaction /org/debian/apt/transaction/c603ca103ed849038dac72029669fa40
Dec 28 07:46:21 office kernel: [ 4557.009029] sdb: detected capacity change from 15819866112 to 0
Dec 28 07:46:35 office kernel: [ 4571.390133] usb 1-8: USB disconnect, device number 9
Dec 28 07:47:34 office dbus[437]: [system] Reloaded configuration
Dec 28 07:49:52 office dbus[437]: message repeated 31 times: [ [system] Reloaded configuration]
Dec 28 07:49:58 office dbus[437]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper)
Dec 28 07:49:59 office dbus[437]: [system] Successfully activated service 'org.freedesktop.PackageKit'
Dec 28 07:50:02 office AptDaemon.Worker: INFO: Finished transaction /org/debian/apt/transaction/c603ca103ed849038dac72029669fa40
Dec 28 07:50:38 office kernel: [ 4813.840050] usb 1-8: new high-speed USB device number 10 using ehci-pci
Dec 28 07:50:38 office kernel: [ 4813.973206] usb 1-8: New USB device found, idVendor=14cd, idProduct=121c
Dec 28 07:50:38 office kernel: [ 4813.973214] usb 1-8: New USB device strings: Mfr=1, Product=3, SerialNumber=2
Dec 28 07:50:38 office kernel: [ 4813.973218] usb 1-8: Product: Mass Storage Device
Dec 28 07:50:38 office kernel: [ 4813.973222] usb 1-8: Manufacturer: Generic
Dec 28 07:50:38 office kernel: [ 4813.973226] usb 1-8: SerialNumber: 812320100708
Dec 28 07:50:38 office kernel: [ 4813.973706] usb-storage 1-8:1.0: USB Mass Storage device detected
Dec 28 07:50:38 office kernel: [ 4813.974294] scsi8 : usb-storage 1-8:1.0
Dec 28 07:50:38 office mtp-probe: checking bus 1, device 10: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-8"
Dec 28 07:50:38 office mtp-probe: bus: 1, device: 10 was not an MTP device
Dec 28 07:50:39 office kernel: [ 4814.972691] scsi 8:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
Dec 28 07:50:39 office kernel: [ 4814.973579] sd 8:0:0:0: Attached scsi generic sg2 type 0
Dec 28 07:50:39 office kernel: [ 4815.257677] sd 8:0:0:0: [sdb] 30898176 512-byte logical blocks: (15.8 GB/14.7 GiB)
Dec 28 07:50:39 office kernel: [ 4815.258285] sd 8:0:0:0: [sdb] Write Protect is off
Dec 28 07:50:39 office kernel: [ 4815.258291] sd 8:0:0:0: [sdb] Mode Sense: 03 00 00 00
Dec 28 07:50:39 office kernel: [ 4815.258908] sd 8:0:0:0: [sdb] No Caching mode page found
Dec 28 07:50:39 office kernel: [ 4815.258915] sd 8:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 07:50:39 office kernel: [ 4815.264419] sd 8:0:0:0: [sdb] No Caching mode page found
Dec 28 07:50:39 office kernel: [ 4815.264427] sd 8:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 07:50:39 office kernel: [ 4815.267537] sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 > sdb4
Dec 28 07:50:39 office kernel: [ 4815.278658] sd 8:0:0:0: [sdb] No Caching mode page found
Dec 28 07:50:39 office kernel: [ 4815.278668] sd 8:0:0:0: [sdb] Assuming drive cache: write through
Dec 28 07:50:39 office kernel: [ 4815.278676] sd 8:0:0:0: [sdb] Attached SCSI removable disk
Dec 28 07:50:40 office kernel: [ 4816.193002] EXT4-fs (sdb6): warning: checktime reached, running e2fsck is recommended
Dec 28 07:50:40 office kernel: [ 4816.227104] EXT4-fs (sdb2): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 07:50:40 office kernel: [ 4816.238650] EXT4-fs (sdb6): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 07:50:40 office kernel: [ 4816.264354] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 07:50:40 office udisksd[1281]: Mounted /dev/sdb2 at /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b1 on behalf of uid 1000
Dec 28 07:50:40 office kernel: [ 4816.304118] FAT-fs (sdb4): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Dec 28 07:50:40 office kernel: [ 4816.308250] EXT4-fs (sdb5): warning: checktime reached, running e2fsck is recommended
Dec 28 07:50:40 office kernel: [ 4816.311693] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 07:50:40 office udisksd[1281]: Mounted /dev/sdb1 at /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b on behalf of uid 1000
Dec 28 07:50:40 office udisksd[1281]: Mounted /dev/sdb6 at /media/office/151028b9-8c2f-49ba-8d70-5f2148f2c09e on behalf of uid 1000
Dec 28 07:50:40 office udisksd[1281]: Mounted /dev/sdb4 at /media/office/KOBOVOX on behalf of uid 1000
Dec 28 07:50:40 office udisksd[1281]: Mounted /dev/sdb5 at /media/office/3df28825-869b-4e96-9de1-a8286fafff19 on behalf of uid 1000
^C
office@office:~/vox$ su
Password:
root@office:/home/office/vox# mount -t ext4 /dev/sdb2 imagemount
root@office:/home/office/vox# ls -al imagemount
total 110220
drwxr-xr-x 2 root root 4096 Nov 23 2011 .
drwxrwxr-x 6 office office 4096 Dec 28 06:55 ..
-rw-r--r-- 1 root root 112855466 Nov 19 2011 recovery_backup_signed.zip
root@office:/home/office/vox# rm imagemount/recovery_backup_signed.zip
root@office:/home/office/vox# cp update-rooted.zip imagemount/recovery_backup_signed.zip
root@office:/home/office/vox# sync
root@office:/home/office/vox# umount imagemount
root@office:/home/office/vox# exit
exit
office@office:~/vox$ tail -f /var/log/syslog
Dec 28 08:34:29 office udisksd[1281]: Mounted /dev/sdb3 at /media/office/4 on behalf of uid 1000
Dec 28 08:34:29 office kernel: [ 7444.833235] EXT4-fs (sdb6): recovery complete
Dec 28 08:34:29 office kernel: [ 7444.853361] EXT4-fs (sdb6): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 08:34:29 office udisksd[1281]: Mounted /dev/sdb6 at /media/office/5 on behalf of uid 1000
Dec 28 08:34:29 office kernel: [ 7445.120081] EXT4-fs (sdb5): recovery complete
Dec 28 08:34:29 office kernel: [ 7445.135535] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
Dec 28 08:34:29 office udisksd[1281]: Mounted /dev/sdb5 at /media/office/6 on behalf of uid 1000
Dec 28 08:36:14 office udisksd[1281]: Cleaning up mount point /media/office/4 (device 8:19 is not mounted)
Dec 28 08:36:25 office udisksd[1281]: Cleaning up mount point /media/office/6 (device 8:21 is not mounted)
Dec 28 08:36:37 office udisksd[1281]: Cleaning up mount point /media/office/5 (device 8:22 is not mounted)
^C
office@office:~/vox$ su
Password:
root@office:/home/office/vox# umount /dev/sdb1
root@office:/home/office/vox# umount /dev/sdb2
root@office:/home/office/vox# umount /dev/sdb3
umount: /dev/sdb3: not found
root@office:/home/office/vox# umount /dev/sdb4
umount: /dev/sdb4: not mounted
root@office:/home/office/vox# umount /dev/sdb5
umount: /dev/sdb5: not found
root@office:/home/office/vox# umount /dev/sdb6
umount: /dev/sdb6: not found
root@office:/home/office/vox# exit
exit
office@office:~/vox$ su
Password:
root@office:/home/office/vox# dd if=/dev/sdc of=./vox_image.bin bs=512
dd: failed to open ‘/dev/sdc’: No such file or directory
root@office:/home/office/vox# dd if=/dev/sdb of=./vox_image.bin bs=512
30898176+0 records in
30898176+0 records out
15819866112 bytes (16 GB) copied, 903.603 s, 17.5 MB/s
root@office:/home/office/vox# su
root@office:/home/office/vox# umount /dev/sdb1
root@office:/home/office/vox# umount /dev/sdb2
root@office:/home/office/vox# umount /dev/sdb3
umount: /dev/sdb3: not mounted
root@office:/home/office/vox# umount /dev/sdb4
root@office:/home/office/vox# umount /dev/sdb5
root@office:/home/office/vox# umount /dev/sdb6
root@office:/home/office/vox# exit
exit
root@office:/home/office/vox# su
root@office:/home/office/vox# dd if=/dev/sdb of=./vox_image.bin bs=512
15523840+0 records in
15523840+0 records out
7948206080 bytes (7.9 GB) copied, 443.982 s, 17.9 MB/s
root@office:/home/office/vox# exit
exit
root@office:/home/office/vox# su
root@office:/home/office/vox# umount /dev/sdb1
root@office:/home/office/vox# umount /dev/sdb2
umount: /dev/sdb2: not mounted
root@office:/home/office/vox# umount /dev/sdb3
umount: /dev/sdb3: not found
root@office:/home/office/vox# umount /dev/sdb4
umount: /dev/sdb4: not mounted
root@office:/home/office/vox# umount /dev/sdb5
umount: /dev/sdb5: not found
root@office:/home/office/vox# umount /dev/sdb6
umount: /dev/sdb6: not found
root@office:/home/office/vox# exit
exit
root@office:/home/office/vox# su
root@office:/home/office/vox# dd if=./vox_image.bin of=/dev/sdb bs=512
15523840+0 records in
15523840+0 records out
7948206080 bytes (7.9 GB) copied, 2248.78 s, 3.5 MB/s
root@office:/home/office/vox# exit
exit
root@office:/home/office/vox# su
root@office:/home/office/vox# mount -t ext4 /dev/sdb2 imagemount
root@office:/home/office/vox# ls -al imagemount
total 110220
drwxr-xr-x 2 root root 4096 Nov 23 2011 .
drwxrwxr-x 6 office office 4096 Dec 28 06:55 ..
-rw-r--r-- 1 root root 112855466 Nov 19 2011 recovery_backup_signed.zip
root@office:/home/office/vox# rm imagemount/recovery_backup_signed.zip
root@office:/home/office/vox# cp update-rooted.zip imagemount/recovery_backup_signed.zip
root@office:/home/office/vox# sync
root@office:/home/office/vox# umount imagemount
root@office:/home/office/vox# exit
exit
root@office:/home/office/vox#

Difflugia · 12-28-2014, 02:42 PM

Quote:

Originally Posted by mightyzazz

Hi Difluggia, me again. Hope you can help me out one more time. I needed to redo the whole vox hacking/expansion. Everything seemed to go fine, as I now have a bit more knowledge of Linux, and Lubuntu also kindly gives me visual clues of folder locations much like windows, so i know where things are located now and can see when a lot of things go wrong. However, my end result this time was an unrooted but expanded sd card, with no errors detected. There was a deviation from your protocol, however, because your link for the Superuser-3.1.3-arm-signed.zip gave a server not found message repeatedly, so in the end I found another one from a google search, which appears to be the same size etc. A close comparison of your protocol and my terminal info shows this only? discrepancy - could this be where I am going wrong?

I looked through and don't see an obvious problem. If it boots but isn't rooted, I would expect the problem to be here:

Code:

root@office:/home/office/vox# mount -t ext4 update/system.img imagemount -o looproot@office:/home/office/vox# cp superuser/system/app/Superuser.apk imagemount/app/
root@office:/home/office/vox# cp superuser/system/bin/su imagemount/bin/
root@office:/home/office/vox# chmod 4755 imagemount/bin/su
root@office:/home/office/vox# umount imagemount
root@office:/home/office/vox# exit

That looks OK (particularly setting the permissions, where I'd expect the problem to be), so I'm kind of at a loss. I did, though, have a weird glitch after first rooting that I never did actually figure out (it "fixed itself"), so maybe it's the same thing?

mightyzazz · 12-28-2014, 09:08 PM

Thanks Difflugia. Is there any way you can tell if the superuser app is present in any form on my Kobovox sd card, either when it is running inside the apparently unrooted tablet, or in a card reader on a linux PC?

By the way, this is a huge boost to my confidence that I have not done anything particular wrong this time round!

Difflugia · 12-29-2014, 08:05 PM

I don't have the Vox with me and this is from memory, but I think it's right (or close to it).

From the Vox, you can use either ES File Explorer or a terminal emulator. ES File Explorer gives you a Windows-like folder browser and the terminal emulator gives you a linux shell.

From a terminal, "ls -a -l /system/bin/su" should show permissions (on the left) of "-rwsr-xr-x". If the "s" is an "x", then that would cause the problem. The "chmod 4755" command is responsible for that, so repeating the part of the directions that copy the su binary to the card would fix it. The other half is the SuperUser app, so if SuperUser (I think the app icon is the android robot with an eyepatch) isn't in your app list, then that's the problem.

Finally, it's supposed to ask you if you want to grant superuser access when something uses "su". It's possible to tell it "no" in a way that it denies access and never asks you again. To fix that, run "Settings" and go to the "Applications" tab. Find the SuperUser app and select "clear data".

If everything's working, you should be able to type "su" into the terminal emulator and it will pop up a window asking if the terminal emulator can have superuser access. Say "yes" and your prompt should change from "$" to "#".

mightyzazz · 01-03-2015, 02:39 PM

Hi Difflugia. Of course you were right. I did a full rerestart according to your instructions rather that pressing the restart button hidden on the inside back of the tablet - and the superuser icon appeared and works fine! Happy New Year! Roberto.

Difflugia · 01-03-2015, 09:47 PM

Quote:

Originally Posted by mightyzazz

Hi Difflugia. Of course you were right. I did a full rerestart according to your instructions rather that pressing the restart button hidden on the inside back of the tablet - and the superuser icon appeared and works fine! Happy New Year! Roberto.

I'm glad it worked for you. It's also good to know that I wasn't crazy when I had the problem and rebooting "magically" fixed it!

vph · 03-10-2015, 10:02 AM

Hi Difflugia,
thanks to all the information you provided I managed to root and clean my kobo vox.
Now after removing all the apk according your list above, on the bottom of the screen there is a bar with links like "Just for You", "Shop Kobo" etc which are no more active and useful.
Do you know of a way to edit these links and replace them with something more useful?

Best Regards,
vph

vph · 03-10-2015, 01:36 PM

Found it!
Replaced the default launcher with ADW and now it is perfect!!

hecatae · 04-11-2015, 12:13 PM

What's the easiest way to fully remove google apps from the vox?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Touch Hacking into the Kobo Touch	stef70	Kobo Developer's Corner	60	03-04-2017 11:32 AM
Kobo Vox, Kobo preorder	shannont	Kobo Tablets	5	12-17-2012 09:52 PM
What Can the Kobo Vox Do?	pokee	Kobo Tablets	36	11-18-2011 03:00 AM
Where do you use your kobo vox?	ron1959	Kobo Tablets	8	11-04-2011 09:57 PM
Kobo won't read books already in progress	La Coccinelle	Kobo Reader	3	11-29-2010 03:29 PM

10-01-2014, 07:05 PM	#211
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Hi Everyone. My kids have been enjoying their rooted vox's immensely - thanks. I have a perhaps overly ambitious question, but I was wondering how easy it would be for me to try and upgrade the android version on one of these machines? I am sure it is out of my depth, but is it even feasible? Is all I have to lose an sd card? Cheers, Roberto.

11-16-2014, 04:43 PM	#213
hecatae MoDaCo News Team Posts: 6 Karma: 63180 Join Date: Dec 2012 Location: Northamptonshire Device: Kobo Vox	Latest sourcecode for our kobo vox imx51 chipsets: http://www.freescale.com/webapp/sps/...ode=IMXANDROID still gingerbread, 2.3.4 from what I can tell,

11-21-2014, 06:54 AM	#214
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	I am sure this is a dumb question, but what does that mean? Will I be able to update the vox in some way in the future? Thanks, Roberto.

11-22-2014, 03:56 PM	#216
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Thanks for the info. I have already learnt so much from you and am always keen to push things further and give stuff a try, even if the improvements (if any!) are minimal. Roberto.

12-28-2014, 09:08 PM	#219
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Thanks Difflugia. Is there any way you can tell if the superuser app is present in any form on my Kobovox sd card, either when it is running inside the apparently unrooted tablet, or in a card reader on a linux PC? By the way, this is a huge boost to my confidence that I have not done anything particular wrong this time round!

12-29-2014, 08:05 PM	#220
Difflugia Testate Amoeba Posts: 3,049 Karma: 27300000 Join Date: Sep 2012 Device: Many Android devices, Kindle 2, Toshiba e755 PocketPC	I don't have the Vox with me and this is from memory, but I think it's right (or close to it). From the Vox, you can use either ES File Explorer or a terminal emulator. ES File Explorer gives you a Windows-like folder browser and the terminal emulator gives you a linux shell. From a terminal, "ls -a -l /system/bin/su" should show permissions (on the left) of "-rwsr-xr-x". If the "s" is an "x", then that would cause the problem. The "chmod 4755" command is responsible for that, so repeating the part of the directions that copy the su binary to the card would fix it. The other half is the SuperUser app, so if SuperUser (I think the app icon is the android robot with an eyepatch) isn't in your app list, then that's the problem. Finally, it's supposed to ask you if you want to grant superuser access when something uses "su". It's possible to tell it "no" in a way that it denies access and never asks you again. To fix that, run "Settings" and go to the "Applications" tab. Find the SuperUser app and select "clear data". If everything's working, you should be able to type "su" into the terminal emulator and it will pop up a window asking if the terminal emulator can have superuser access. Say "yes" and your prompt should change from "$" to "#".

01-03-2015, 02:39 PM	#221
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Hi Difflugia. Of course you were right. I did a full rerestart according to your instructions rather that pressing the restart button hidden on the inside back of the tablet - and the superuser icon appeared and works fine! Happy New Year! Roberto.

03-10-2015, 10:02 AM	#223
vph Junior Member Posts: 2 Karma: 10 Join Date: Apr 2013 Device: Kobo vox	Hi Difflugia, thanks to all the information you provided I managed to root and clean my kobo vox. Now after removing all the apk according your list above, on the bottom of the screen there is a bar with links like "Just for You", "Shop Kobo" etc which are no more active and useful. Do you know of a way to edit these links and replace them with something more useful? Best Regards, vph

03-10-2015, 01:36 PM	#224
vph Junior Member Posts: 2 Karma: 10 Join Date: Apr 2013 Device: Kobo vox	Found it! Replaced the default launcher with ADW and now it is perfect!!

04-11-2015, 12:13 PM	#225
hecatae MoDaCo News Team Posts: 6 Karma: 63180 Join Date: Dec 2012 Location: Northamptonshire Device: Kobo Vox	What's the easiest way to fully remove google apps from the vox?

Advert

Advert