Kobo Vox Hacking Progress - Page 14

Difflugia · 03-18-2014, 02:52 PM

Quote:

Originally Posted by mightyzazz

Thanks, PeterT, that worked a treat! Have made real progress, but have now got stuck at the line

Password:
su: Authentication failure

a couple of lines before BACKING UP THE VOX
I used the only password I know, and that is the one I use for all of the other password request stages. Is there a second password, which I have forgotten about, perhaps created at the install of Lubuntu in the first place? If so, is it possible to retrieve it somehow? Once done, at what point can I pick up the task, or do I have to start again from scratch?

Thanks Again,

Roberto.

I checked a few forums and it looks like Lubuntu deactivates the root account by default. According to the posts I read, you should be able to run the command "sudo passwd root". You'll be asked to type a new password, which will be your root password from then on.

You can then pick up where you left off.

mightyzazz · 03-21-2014, 08:37 AM

Thanks again - that seemed to work fine.
tail -f /var/log/messages did not work on lubuntu, but a forum suggested trying
tail -f /var/log/syslog which gave me the following:-

office@office-desktop:~$ tail -f /var/log/syslog
Mar 22 01:10:14 office-desktop udisksd[1365]: Mounted /dev/sdb6 at /media/office/06841146-0c21-4589-96b8-d7397f4506b4 on behalf of uid 1000
Mar 22 01:10:24 office-desktop kernel: [ 241.875134] EXT4-fs (sdb5): warning: maximal mount count reached, running e2fsck is recommended
Mar 22 01:10:25 office-desktop kernel: [ 242.935358] EXT4-fs (sdb5): 2 orphan inodes deleted
Mar 22 01:10:25 office-desktop kernel: [ 242.935365] EXT4-fs (sdb5): recovery complete
Mar 22 01:10:26 office-desktop kernel: [ 244.121331] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
Mar 22 01:10:26 office-desktop udisksd[1365]: Mounted /dev/sdb5 at /media/office/3f497e60-5913-4a3a-ae7e-18fe045bca20 on behalf of uid 1000
Mar 22 01:11:46 office-desktop anacron[1027]: Job `cron.daily' started
Mar 22 01:11:46 office-desktop anacron[1654]: Updated timestamp for job `cron.daily' to 2014-03-22
Mar 22 01:17:01 office-desktop CRON[1707]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 22 01:24:27 office-desktop udisksd[1365]: Cleaning up mount point /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b (device 8:17 is not mounted)

so hopefully this means the same thing as the standard instructions, with me replacing sdb for sdc. Before I go on to making a back up copy of this disc, it would be great if someone could confirm that I am on the right track so far. Thanks, Roberto.

Difflugia · 03-21-2014, 08:57 AM

Quote:

Originally Posted by mightyzazz

Thanks again - that seemed to work fine.
tail -f /var/log/messages did not work on lubuntu, but a forum suggested trying
tail -f /var/log/syslog which gave me the following:-

office@office-desktop:~$ tail -f /var/log/syslog
Mar 22 01:10:14 office-desktop udisksd[1365]: Mounted /dev/sdb6 at /media/office/06841146-0c21-4589-96b8-d7397f4506b4 on behalf of uid 1000
Mar 22 01:10:24 office-desktop kernel: [ 241.875134] EXT4-fs (sdb5): warning: maximal mount count reached, running e2fsck is recommended
Mar 22 01:10:25 office-desktop kernel: [ 242.935358] EXT4-fs (sdb5): 2 orphan inodes deleted
Mar 22 01:10:25 office-desktop kernel: [ 242.935365] EXT4-fs (sdb5): recovery complete
Mar 22 01:10:26 office-desktop kernel: [ 244.121331] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
Mar 22 01:10:26 office-desktop udisksd[1365]: Mounted /dev/sdb5 at /media/office/3f497e60-5913-4a3a-ae7e-18fe045bca20 on behalf of uid 1000
Mar 22 01:11:46 office-desktop anacron[1027]: Job `cron.daily' started
Mar 22 01:11:46 office-desktop anacron[1654]: Updated timestamp for job `cron.daily' to 2014-03-22
Mar 22 01:17:01 office-desktop CRON[1707]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Mar 22 01:24:27 office-desktop udisksd[1365]: Cleaning up mount point /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b (device 8:17 is not mounted)

so hopefully this means the same thing as the standard instructions, with me replacing sdb for sdc. Before I go on to making a back up copy of this disc, it would be great if someone could confirm that I am on the right track so far. Thanks, Roberto.

Definitely. This particular bit is showing that (at least) two partitions on /dev/sdb were automatically mounted. You'll get a fuller view if you type the "tail -f /var/log/syslog" before plugging in the card reader. The "-f" on the tail command means that the command continues to display anything that is added to the file after the command is run. If it's already running when you plug in your card, you should see the USB information as it loads the device. Since the mounted partitions (sdb5 and sdb6) match the layout of the Vox, though, I think we can safely say that sdb is your card. In my instructions, then, you will replace sdc with sdb.

mightyzazz · 03-21-2014, 10:11 PM

Have got to the point when I am putting in the new 16GB replacement card when I got this message:-

root@office-desktop:/home/office# su
root@office-desktop:/home/office# dd if=/dev/sdb of=./vox_image.bin bs=512
exit
15523840+0 records in
15523840+0 records out
7948206080 bytes (7.9 GB) copied, 453.583 s, 17.5 MB/s
root@office-desktop:/home/office# exit
exit
root@office-desktop:/home/office# exit
exit
office@office-desktop:~$ tail -f /var/log/syslog
Mar 22 14:19:17 office-desktop udisksd[1328]: Cleaning up mount point /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b (device 8:17 is not mounted)
Mar 22 14:19:28 office-desktop udisksd[1328]: Cleaning up mount point /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b1 (device 8:18 is not mounted)
Mar 22 14:20:23 office-desktop udisksd[1328]: Cleaning up mount point /media/office/KOBOVOX (device 8:20 is not mounted)
Mar 22 14:21:02 office-desktop udisksd[1328]: Cleaning up mount point /media/office/3f497e60-5913-4a3a-ae7e-18fe045bca20 (device 8:21 is not mounted)
Mar 22 14:21:11 office-desktop udisksd[1328]: Cleaning up mount point /media/office/06841146-0c21-4589-96b8-d7397f4506b4 (device 8:22 is not mounted)
Mar 22 14:35:11 office-desktop whoopsie[1023]: online
Mar 22 14:36:39 office-desktop whoopsie[1023]: online
Mar 22 14:36:40 office-desktop whoopsie[1023]: online
Mar 22 15:02:47 office-desktop kernel: [ 3560.405247] sdb: detected capacity change from 7948206080 to 0
Mar 22 15:02:58 office-desktop kernel: [ 3571.401311] usb 1-1: USB disconnect, device number 3
Mar 22 15:04:52 office-desktop kernel: [ 3685.556024] usb 1-1: new high-speed USB device number 4 using ehci-pci
Mar 22 15:04:52 office-desktop kernel: [ 3685.689165] usb 1-1: New USB device found, idVendor=14cd, idProduct=121c
Mar 22 15:04:52 office-desktop kernel: [ 3685.689172] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=2
Mar 22 15:04:52 office-desktop kernel: [ 3685.689177] usb 1-1: Product: Mass Storage Device
Mar 22 15:04:52 office-desktop kernel: [ 3685.689181] usb 1-1: Manufacturer: Generic
Mar 22 15:04:52 office-desktop kernel: [ 3685.689185] usb 1-1: SerialNumber: 812320100708
Mar 22 15:04:52 office-desktop kernel: [ 3685.689699] usb-storage 1-1:1.0: USB Mass Storage device detected
Mar 22 15:04:52 office-desktop kernel: [ 3685.690524] scsi7 : usb-storage 1-1:1.0
Mar 22 15:04:52 office-desktop mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1"
Mar 22 15:04:52 office-desktop mtp-probe: bus: 1, device: 4 was not an MTP device
Mar 22 15:04:53 office-desktop kernel: [ 3686.688875] scsi 7:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
Mar 22 15:04:53 office-desktop kernel: [ 3686.689661] sd 7:0:0:0: Attached scsi generic sg2 type 0
Mar 22 15:04:53 office-desktop kernel: [ 3686.835557] sd 7:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
Mar 22 15:04:53 office-desktop kernel: [ 3686.836193] sd 7:0:0:0: [sdb] Write Protect is off
Mar 22 15:04:53 office-desktop kernel: [ 3686.836204] sd 7:0:0:0: [sdb] Mode Sense: 03 00 00 00
Mar 22 15:04:53 office-desktop kernel: [ 3686.837070] sd 7:0:0:0: [sdb] No Caching mode page found
Mar 22 15:04:53 office-desktop kernel: [ 3686.837079] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Mar 22 15:04:53 office-desktop kernel: [ 3686.842544] sd 7:0:0:0: [sdb] No Caching mode page found
Mar 22 15:04:53 office-desktop kernel: [ 3686.842554] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Mar 22 15:04:53 office-desktop kernel: [ 3686.843688] sdb: sdb1
Mar 22 15:04:53 office-desktop kernel: [ 3686.848001] sd 7:0:0:0: [sdb] No Caching mode page found
Mar 22 15:04:53 office-desktop kernel: [ 3686.848068] sd 7:0:0:0: [sdb] Assuming drive cache: write through
Mar 22 15:04:53 office-desktop kernel: [ 3686.848077] sd 7:0:0:0: [sdb] Attached SCSI removable disk
Mar 22 15:04:54 office-desktop kernel: [ 3687.289474] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Mar 22 15:04:54 office-desktop udisksd[1328]: Mounted /dev/sdb1 at /media/office/F82B-1AD3 on behalf of uid 1000

su
umount /dev/sdb1
exit
^C
office@office-desktop:~$
office@office-desktop:~$ su
Password:
root@office-desktop:/home/office# su
root@office-desktop:/home/office# umount /dev/sdb1
root@office-desktop:/home/office# exit
exit
root@office-desktop:/home/office# su
root@office-desktop:/home/office# dd if=./vox-image.bin of=/dev/sdb bs=512
dd: opening ‘./vox-image.bin’: No such file or directory
root@office-desktop:/home/office# exit

Any ideas?
Thanks,

Roberto.

mightyzazz · 03-21-2014, 10:12 PM

Happy to start from scratch or from any point in the process.

Difflugia · 03-25-2014, 10:51 AM

I didn't see it at first, but I looked again after a little sleep.

dd if=/dev/sdb of=./vox_image.bin bs=512
dd if=./vox-image.bin of=/dev/sdb bs=512

Note that in the first command (where we created the file), the name is "vox_image.bin" and in the second (where we're trying to use it), it's "vox-image.bin". I've updated my original instructions, but you just need to change the second command to:

dd if=./vox_image.bin of=/dev/sdb bs=512

and it should work fine. You should be able to pick up right at that point.

mightyzazz · 03-30-2014, 06:01 AM

Hi Guys - Sorry, it is me again. I feel as though I am nearly there. Looks like I have successfully created the image to the new card, but have got this message:-

root@office-desktop:/home/office# su
root@office-desktop:/home/office# mount -t ext4 /dev/sdb2 imagemount
root@office-desktop:/home/office# ls -al imagemount
total 110220
drwxr-xr-x 2 root root 4096 Nov 23 2011 .
drwxr-xr-x 24 office office 4096 Mar 30 22:45 ..
-rw-r--r-- 1 root root 112855466 Nov 19 2011 recovery_backup_signed.zip
root@office-desktop:/home/office# rm imagemount/recovery_backup_signed.zip
root@office-desktop:/home/office# cp update-rooted.zip imagemount/recovery_backup_signed.zip
cp: cannot stat ‘update-rooted.zip’: No such file or directory
root@office-desktop:/home/office# sync
root@office-desktop:/home/office# umount imagemount
root@office-desktop:/home/office# exit
exit
root@office-desktop:/home/office#

What does the line :cp: cannot stat ‘update-rooted.zip’: No such file or directory mean? Is it the same sort of problem that I had previously, with it being in a different location? Do I need to recreate it? Thanks, Roberto.

Difflugia · 04-03-2014, 09:36 AM

That means that it can't find the file "update-rooted.zip" in the current directory. I've looked through the instructions hoping that I made the same sort of mistake that I made before and if I did, I don't see it. You're close to being done, though, and recreating the zip file is probably the easiest way to make sure that it works.

First, based on your comments, it looks like your home directory is "/home/office". If you enter the "pwd" command, the response should be "/home/office". If that's the case, check to make sure that the update directory is there. Enter the command "ls -ald update". You should see something that looks very similar to this:

Code:

drwxr-xr-x 5 bowz users 4096 Mar 19 15:51 update

If you see this, there's a problem.

Code:

ls: cannot access update: No such file or directory

If that was OK, then do this step again:

Code:

cd update
zip -r9 ../update-rooted.zip .
cd ..

You should see output indicating that zip created the update-rooted.zip file and added a bunch of files to it. You should also be able to see the file in your current directory. If you type "ls -al update-rooted.zip", you should see something very similar to the following output.

Code:

-rw-r--r--   1 bowz users 171558652 Jan 19 18:21 update-rooted.zip

If you see this instead, there's a problem:

Code:

ls: cannot access update-rooted.zip: No such file or directory

If the file is there, you should be able to restart with "rooting your new card". If anything goes wrong, copy the output from the commands in this post (particularly the "zip" command) and I'll see if I can figure it out.

You're almost there!

mightyzazz · 04-04-2014, 02:50 PM

Hi Difflugia, tried it and here is the result. Again, I picked up from where I left off, but was unsure about unmounting etc., so did not do that.

office@office-desktop:~$ tail -f /var/log/syslog
Apr 5 07:12:12 office-desktop NetworkManager[755]: <info> (eth0): IP6 addrconf timed out or failed.
Apr 5 07:12:12 office-desktop NetworkManager[755]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled...
Apr 5 07:12:12 office-desktop NetworkManager[755]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started...
Apr 5 07:12:12 office-desktop NetworkManager[755]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Apr 5 07:12:22 office-desktop ntpd_intres[763]: parent died before we finished, exiting
Apr 5 07:12:52 office-desktop whoopsie[1047]: online
Apr 5 07:12:53 office-desktop whoopsie[1047]: online
Apr 5 07:16:54 office-desktop anacron[998]: Job `cron.daily' started
Apr 5 07:16:54 office-desktop anacron[1663]: Updated timestamp for job `cron.daily' to 2014-04-05
Apr 5 07:17:01 office-desktop CRON[1718]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Apr 5 07:18:31 office-desktop kernel: [ 423.264027] usb 1-1: new high-speed USB device number 2 using ehci-pci
Apr 5 07:18:31 office-desktop kernel: [ 423.397250] usb 1-1: New USB device found, idVendor=14cd, idProduct=121c
Apr 5 07:18:31 office-desktop kernel: [ 423.397258] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=2
Apr 5 07:18:31 office-desktop kernel: [ 423.397262] usb 1-1: Product: Mass Storage Device
Apr 5 07:18:31 office-desktop kernel: [ 423.397267] usb 1-1: Manufacturer: Generic
Apr 5 07:18:31 office-desktop kernel: [ 423.397271] usb 1-1: SerialNumber: 812320100708
Apr 5 07:18:31 office-desktop mtp-probe: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1"
Apr 5 07:18:31 office-desktop mtp-probe: bus: 1, device: 2 was not an MTP device
Apr 5 07:18:31 office-desktop kernel: [ 423.509569] usb-storage 1-1:1.0: USB Mass Storage device detected
Apr 5 07:18:31 office-desktop kernel: [ 423.510030] scsi6 : usb-storage 1-1:1.0
Apr 5 07:18:31 office-desktop kernel: [ 423.510326] usbcore: registered new interface driver usb-storage
Apr 5 07:18:32 office-desktop kernel: [ 424.508746] scsi 6:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS
Apr 5 07:18:32 office-desktop kernel: [ 424.509408] sd 6:0:0:0: Attached scsi generic sg2 type 0
Apr 5 07:18:32 office-desktop kernel: [ 424.656315] sd 6:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB)
Apr 5 07:18:32 office-desktop kernel: [ 424.656926] sd 6:0:0:0: [sdb] Write Protect is off
Apr 5 07:18:32 office-desktop kernel: [ 424.656932] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00
Apr 5 07:18:32 office-desktop kernel: [ 424.657551] sd 6:0:0:0: [sdb] No Caching mode page found
Apr 5 07:18:32 office-desktop kernel: [ 424.657558] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 5 07:18:32 office-desktop kernel: [ 424.663553] sd 6:0:0:0: [sdb] No Caching mode page found
Apr 5 07:18:32 office-desktop kernel: [ 424.663562] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 5 07:18:32 office-desktop kernel: [ 424.671713] sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 > sdb4
Apr 5 07:18:32 office-desktop kernel: [ 424.677852] sd 6:0:0:0: [sdb] No Caching mode page found
Apr 5 07:18:32 office-desktop kernel: [ 424.677873] sd 6:0:0:0: [sdb] Assuming drive cache: write through
Apr 5 07:18:32 office-desktop kernel: [ 424.677884] sd 6:0:0:0: [sdb] Attached SCSI removable disk
Apr 5 07:18:33 office-desktop kernel: [ 425.533543] EXT4-fs (sdb5): warning: mounting fs with errors, running e2fsck is recommended
Apr 5 07:18:33 office-desktop kernel: [ 425.534154] EXT4-fs (sdb6): warning: maximal mount count reached, running e2fsck is recommended
Apr 5 07:18:33 office-desktop kernel: [ 425.537645] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null)
Apr 5 07:18:33 office-desktop kernel: [ 425.560205] EXT4-fs (sdb6): mounted filesystem with ordered data mode. Opts: (null)
Apr 5 07:18:33 office-desktop kernel: [ 425.564739] FAT-fs (sdb4): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Apr 5 07:18:33 office-desktop udisksd[1403]: Mounted /dev/sdb4 at /media/office/KOBOVOX on behalf of uid 1000
Apr 5 07:18:33 office-desktop kernel: [ 425.600208] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
Apr 5 07:18:33 office-desktop udisksd[1403]: Mounted /dev/sdb5 at /media/office/3f497e60-5913-4a3a-ae7e-18fe045bca20 on behalf of uid 1000
Apr 5 07:18:33 office-desktop udisksd[1403]: Mounted /dev/sdb6 at /media/office/06841146-0c21-4589-96b8-d7397f4506b4 on behalf of uid 1000
Apr 5 07:18:33 office-desktop udisksd[1403]: Mounted /dev/sdb1 at /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b on behalf of uid 1000
ls -ald update
^C
office@office-desktop:~$ ls -ald update
drwxr-xr-x 2 office office 4096 Mar 21 23:04 update
office@office-desktop:~$ cd update
office@office-desktop:~/update$ zip -r9 ../update-rooted.zip .

zip error: Nothing to do! (try: zip -r9 ../update-rooted.zip . -i .)
office@office-desktop:~/update$ cd ..
office@office-desktop:~$ ls -al update-rooted.zip
ls: cannot access update-rooted.zip: No such file or directory
office@office-desktop:~$

Seeing as this is all good learning for me, would it help if I started from scratch and did it all in one go? Would we see my mistake then? Could I have done something wrong picking up from where I left off in a previous session? How do I search to see where the zip file is located on my system? In the file path /home/office/vox there is a file called update zip if that helps.
Roberto.

Difflugia · 04-07-2014, 04:29 PM

The update directory is empty (the "nothing to do" is telling you that there are no files to add to the zip). That means that something in "Preparing the Files" failed. At this point, it's probably easier for you to redo that section than for me to troubleshoot what exactly went wrong (you should just need to do that section, though... you shouldn't need to redo the backup). When that section's done and you try doing the zip command, the output should be a stack of files being added to the update-rooted.zip.

When I get some time, I'll redo that section and capture the output. I'll post it so you can check for differences that might indicate errors.

mightyzazz · 04-12-2014, 09:43 AM

Hi Guys. First off, a big thankyou to you all for your help so far. I followed your advice and it has worked up to a point. The rooted zip has installed, but I have stuffed up somewhere on the partitioning side. I know this because I have successfully put in my 16GB Sandisk card and did a factory restart and now have a brand new looking kobo vox with the superuser app on the apps page, which opens. However, the settings shows that the internal SD card has no memory, and I cannot download apps onto the kobo. I have put the old one back in and everything works fine. What would be the best way (commands)to get the necessary information on the terminal screen to post so you can see which bit I have gotten wrong? At this point:-

Enter "n" to create a new partition. Enter "e" to create an extended partition. Then enter partition number 3. Hit enter to select the default first sector and type "+4G" (for four gigabytes) for the last sector. ,did I do the right thing in typing +4G immediately after the default sector line and then hit return to get to the last sector? A line or two after that, I got an out of range message. I know I am nearly at the end of this, and can't believe I have even gotten this far.

Cheers,

Roberto.

mightyzazz · 04-18-2014, 12:27 AM

Don't know if I have done the right thing or not, but I have deleted partitions 6-3, and tried to start from that point. Have tried writing +4G after the first sector, but eventually I get a line saying out of range. Get a different error message when typing it after the next line for last sector. Also now seem to have lost partition 6 as an automatic option. Below is one of a few attempts.

Command (m for help): p

Disk /dev/sdb: 15.9 GB, 15931539456 bytes
4 heads, 16 sectors/track, 486192 cylinders, total 31116288 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xcf3814cc

Device Boot Start End Blocks Id System
/dev/sdb1 92160 616448 262144+ 83 Linux
/dev/sdb2 616449 1665025 524288+ 83 Linux

Command (m for help): n
Partition type:
p primary (2 primary, 0 extended, 2 free)
e extended
Select (default p): e
Partition number (1-4, default 3): 3
First sector (2048-31116287, default 2048): +4G
Last sector, +sectors or +size{K,M,G} (8388608-31116287, default 31116287):
Using default value 31116287

Command (m for help): n
Partition type:
p primary (2 primary, 1 extended, 1 free)
l logical (numbered from 5)
Select (default p): p
Selected partition 4
First sector (2048-31116287, default 2048):
Using default value 2048
Last sector, +sectors or +size{K,M,G} (2048-92159, default 92159):
Using default value 92159

Command (m for help): n
All primary partitions are in use
Adding logical partition 5
First sector (8390656-31116287, default 8390656): +3500M
Value out of range.
First sector (8390656-31116287, default 8390656):
Using default value 8390656
Last sector, +sectors or +size{K,M,G} (8390656-31116287, default 31116287):
Using default value 31116287

Command (m for help): w
The partition table has been altered!

Calling ioctl() to re-read partition table.

WARNING: Re-reading the partition table failed with error 16: Device or resource busy.
The kernel still uses the old table. The new table will be used at
the next reboot or after you run partprobe(8) or kpartx(8)
Syncing disks.
root@office-desktop:/home/office#

Cheers,
Roberto.

mightyzazz · 04-21-2014, 08:34 PM

Me again. I have started from scratch and stopped before expanding to 16Gb, and have now successfully rooted my Kobo and have 8Gb of memory. Thanks for all of your help. I did try Gparted on Lubuntu as an alternative form of expanding, but was equally unsuccessful. If anyone can give me some pointers on this last stage, using any method, I would be more than happy to take apart my Kobo again to complete this job.
Thanks,
Roberto.

mightyzazz · 06-09-2014, 09:11 AM

Hi, me again. Have now successfully rooted two kobo vox's but still have not been able to expand the partitions to 16Gb. I am sure I am doing something wrong at the creating new partition stage in terms of size allocation. Any pointers? Is there a youtube tutorial or something similar that I have not found yet? Cheers,
Roberto.

mightyzazz · 06-15-2014, 08:29 PM

Hi Guys. Not to worry. Having spent a very worthwhile weekend learning how to use Gparted properly, i have finally expanded my SD card. Thank you all so much for your help, it has been a fantastic learning experience. I have just fallen at the last small hurdle now. I have very limited Superuser options (updates/temp unroot and OTA survival) - which boxes should be ticked to get it to work? a fail message came up the first time I tried to run it and the Google update app did not work, so in the end I just started the whole SD card process from scratch, to begin with an unused superuser account without permissions. Do I need to install the google app fixer? When I install busybox or Connectbot etc, I used to get a root access permission request, which allowed them to work, but now i don't and they do not seem to be installed properly. Any ideas/ Cheers, Roberto.

03-25-2014, 10:51 AM	#201
Difflugia Testate Amoeba Posts: 3,049 Karma: 27300000 Join Date: Sep 2012 Device: Many Android devices, Kindle 2, Toshiba e755 PocketPC	I didn't see it at first, but I looked again after a little sleep. dd if=/dev/sdb of=./vox_image.bin bs=512 dd if=./vox-image.bin of=/dev/sdb bs=512 Note that in the first command (where we created the file), the name is "vox_image.bin" and in the second (where we're trying to use it), it's "vox-image.bin". I've updated my original instructions, but you just need to change the second command to: dd if=./vox_image.bin of=/dev/sdb bs=512 and it should work fine. You should be able to pick up right at that point. Last edited by Difflugia; 03-25-2014 at 10:54 AM.

04-03-2014, 09:36 AM	#203
Difflugia Testate Amoeba Posts: 3,049 Karma: 27300000 Join Date: Sep 2012 Device: Many Android devices, Kindle 2, Toshiba e755 PocketPC	That means that it can't find the file "update-rooted.zip" in the current directory. I've looked through the instructions hoping that I made the same sort of mistake that I made before and if I did, I don't see it. You're close to being done, though, and recreating the zip file is probably the easiest way to make sure that it works. First, based on your comments, it looks like your home directory is "/home/office". If you enter the "pwd" command, the response should be "/home/office". If that's the case, check to make sure that the update directory is there. Enter the command "ls -ald update". You should see something that looks very similar to this: Code: drwxr-xr-x 5 bowz users 4096 Mar 19 15:51 update If you see this, there's a problem. Code: ls: cannot access update: No such file or directory If that was OK, then do this step again: Code: cd update zip -r9 ../update-rooted.zip . cd .. You should see output indicating that zip created the update-rooted.zip file and added a bunch of files to it. You should also be able to see the file in your current directory. If you type "ls -al update-rooted.zip", you should see something very similar to the following output. Code: -rw-r--r-- 1 bowz users 171558652 Jan 19 18:21 update-rooted.zip If you see this instead, there's a problem: Code: ls: cannot access update-rooted.zip: No such file or directory If the file is there, you should be able to restart with "rooting your new card". If anything goes wrong, copy the output from the commands in this post (particularly the "zip" command) and I'll see if I can figure it out. You're almost there!

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

03-21-2014, 08:37 AM	#197
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Thanks again - that seemed to work fine. tail -f /var/log/messages did not work on lubuntu, but a forum suggested trying tail -f /var/log/syslog which gave me the following:- office@office-desktop:~$ tail -f /var/log/syslog Mar 22 01:10:14 office-desktop udisksd[1365]: Mounted /dev/sdb6 at /media/office/06841146-0c21-4589-96b8-d7397f4506b4 on behalf of uid 1000 Mar 22 01:10:24 office-desktop kernel: [ 241.875134] EXT4-fs (sdb5): warning: maximal mount count reached, running e2fsck is recommended Mar 22 01:10:25 office-desktop kernel: [ 242.935358] EXT4-fs (sdb5): 2 orphan inodes deleted Mar 22 01:10:25 office-desktop kernel: [ 242.935365] EXT4-fs (sdb5): recovery complete Mar 22 01:10:26 office-desktop kernel: [ 244.121331] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null) Mar 22 01:10:26 office-desktop udisksd[1365]: Mounted /dev/sdb5 at /media/office/3f497e60-5913-4a3a-ae7e-18fe045bca20 on behalf of uid 1000 Mar 22 01:11:46 office-desktop anacron[1027]: Job `cron.daily' started Mar 22 01:11:46 office-desktop anacron[1654]: Updated timestamp for job `cron.daily' to 2014-03-22 Mar 22 01:17:01 office-desktop CRON[1707]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Mar 22 01:24:27 office-desktop udisksd[1365]: Cleaning up mount point /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b (device 8:17 is not mounted) so hopefully this means the same thing as the standard instructions, with me replacing sdb for sdc. Before I go on to making a back up copy of this disc, it would be great if someone could confirm that I am on the right track so far. Thanks, Roberto.

03-21-2014, 10:11 PM	#199
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Have got to the point when I am putting in the new 16GB replacement card when I got this message:- root@office-desktop:/home/office# su root@office-desktop:/home/office# dd if=/dev/sdb of=./vox_image.bin bs=512 exit 15523840+0 records in 15523840+0 records out 7948206080 bytes (7.9 GB) copied, 453.583 s, 17.5 MB/s root@office-desktop:/home/office# exit exit root@office-desktop:/home/office# exit exit office@office-desktop:~$ tail -f /var/log/syslog Mar 22 14:19:17 office-desktop udisksd[1328]: Cleaning up mount point /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b (device 8:17 is not mounted) Mar 22 14:19:28 office-desktop udisksd[1328]: Cleaning up mount point /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b1 (device 8:18 is not mounted) Mar 22 14:20:23 office-desktop udisksd[1328]: Cleaning up mount point /media/office/KOBOVOX (device 8:20 is not mounted) Mar 22 14:21:02 office-desktop udisksd[1328]: Cleaning up mount point /media/office/3f497e60-5913-4a3a-ae7e-18fe045bca20 (device 8:21 is not mounted) Mar 22 14:21:11 office-desktop udisksd[1328]: Cleaning up mount point /media/office/06841146-0c21-4589-96b8-d7397f4506b4 (device 8:22 is not mounted) Mar 22 14:35:11 office-desktop whoopsie[1023]: online Mar 22 14:36:39 office-desktop whoopsie[1023]: online Mar 22 14:36:40 office-desktop whoopsie[1023]: online Mar 22 15:02:47 office-desktop kernel: [ 3560.405247] sdb: detected capacity change from 7948206080 to 0 Mar 22 15:02:58 office-desktop kernel: [ 3571.401311] usb 1-1: USB disconnect, device number 3 Mar 22 15:04:52 office-desktop kernel: [ 3685.556024] usb 1-1: new high-speed USB device number 4 using ehci-pci Mar 22 15:04:52 office-desktop kernel: [ 3685.689165] usb 1-1: New USB device found, idVendor=14cd, idProduct=121c Mar 22 15:04:52 office-desktop kernel: [ 3685.689172] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=2 Mar 22 15:04:52 office-desktop kernel: [ 3685.689177] usb 1-1: Product: Mass Storage Device Mar 22 15:04:52 office-desktop kernel: [ 3685.689181] usb 1-1: Manufacturer: Generic Mar 22 15:04:52 office-desktop kernel: [ 3685.689185] usb 1-1: SerialNumber: 812320100708 Mar 22 15:04:52 office-desktop kernel: [ 3685.689699] usb-storage 1-1:1.0: USB Mass Storage device detected Mar 22 15:04:52 office-desktop kernel: [ 3685.690524] scsi7 : usb-storage 1-1:1.0 Mar 22 15:04:52 office-desktop mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1" Mar 22 15:04:52 office-desktop mtp-probe: bus: 1, device: 4 was not an MTP device Mar 22 15:04:53 office-desktop kernel: [ 3686.688875] scsi 7:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS Mar 22 15:04:53 office-desktop kernel: [ 3686.689661] sd 7:0:0:0: Attached scsi generic sg2 type 0 Mar 22 15:04:53 office-desktop kernel: [ 3686.835557] sd 7:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) Mar 22 15:04:53 office-desktop kernel: [ 3686.836193] sd 7:0:0:0: [sdb] Write Protect is off Mar 22 15:04:53 office-desktop kernel: [ 3686.836204] sd 7:0:0:0: [sdb] Mode Sense: 03 00 00 00 Mar 22 15:04:53 office-desktop kernel: [ 3686.837070] sd 7:0:0:0: [sdb] No Caching mode page found Mar 22 15:04:53 office-desktop kernel: [ 3686.837079] sd 7:0:0:0: [sdb] Assuming drive cache: write through Mar 22 15:04:53 office-desktop kernel: [ 3686.842544] sd 7:0:0:0: [sdb] No Caching mode page found Mar 22 15:04:53 office-desktop kernel: [ 3686.842554] sd 7:0:0:0: [sdb] Assuming drive cache: write through Mar 22 15:04:53 office-desktop kernel: [ 3686.843688] sdb: sdb1 Mar 22 15:04:53 office-desktop kernel: [ 3686.848001] sd 7:0:0:0: [sdb] No Caching mode page found Mar 22 15:04:53 office-desktop kernel: [ 3686.848068] sd 7:0:0:0: [sdb] Assuming drive cache: write through Mar 22 15:04:53 office-desktop kernel: [ 3686.848077] sd 7:0:0:0: [sdb] Attached SCSI removable disk Mar 22 15:04:54 office-desktop kernel: [ 3687.289474] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Mar 22 15:04:54 office-desktop udisksd[1328]: Mounted /dev/sdb1 at /media/office/F82B-1AD3 on behalf of uid 1000 su umount /dev/sdb1 exit ^C office@office-desktop:~$ office@office-desktop:~$ su Password: root@office-desktop:/home/office# su root@office-desktop:/home/office# umount /dev/sdb1 root@office-desktop:/home/office# exit exit root@office-desktop:/home/office# su root@office-desktop:/home/office# dd if=./vox-image.bin of=/dev/sdb bs=512 dd: opening ‘./vox-image.bin’: No such file or directory root@office-desktop:/home/office# exit Any ideas? Thanks, Roberto.

03-21-2014, 10:12 PM	#200
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Happy to start from scratch or from any point in the process.

03-30-2014, 06:01 AM	#202
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Hi Guys - Sorry, it is me again. I feel as though I am nearly there. Looks like I have successfully created the image to the new card, but have got this message:- root@office-desktop:/home/office# su root@office-desktop:/home/office# mount -t ext4 /dev/sdb2 imagemount root@office-desktop:/home/office# ls -al imagemount total 110220 drwxr-xr-x 2 root root 4096 Nov 23 2011 . drwxr-xr-x 24 office office 4096 Mar 30 22:45 .. -rw-r--r-- 1 root root 112855466 Nov 19 2011 recovery_backup_signed.zip root@office-desktop:/home/office# rm imagemount/recovery_backup_signed.zip root@office-desktop:/home/office# cp update-rooted.zip imagemount/recovery_backup_signed.zip cp: cannot stat ‘update-rooted.zip’: No such file or directory root@office-desktop:/home/office# sync root@office-desktop:/home/office# umount imagemount root@office-desktop:/home/office# exit exit root@office-desktop:/home/office# What does the line :cp: cannot stat ‘update-rooted.zip’: No such file or directory mean? Is it the same sort of problem that I had previously, with it being in a different location? Do I need to recreate it? Thanks, Roberto.

04-04-2014, 02:50 PM	#204
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Hi Difflugia, tried it and here is the result. Again, I picked up from where I left off, but was unsure about unmounting etc., so did not do that. office@office-desktop:~$ tail -f /var/log/syslog Apr 5 07:12:12 office-desktop NetworkManager[755]: <info> (eth0): IP6 addrconf timed out or failed. Apr 5 07:12:12 office-desktop NetworkManager[755]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) scheduled... Apr 5 07:12:12 office-desktop NetworkManager[755]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) started... Apr 5 07:12:12 office-desktop NetworkManager[755]: <info> Activation (eth0) Stage 4 of 5 (IPv6 Configure Timeout) complete. Apr 5 07:12:22 office-desktop ntpd_intres[763]: parent died before we finished, exiting Apr 5 07:12:52 office-desktop whoopsie[1047]: online Apr 5 07:12:53 office-desktop whoopsie[1047]: online Apr 5 07:16:54 office-desktop anacron[998]: Job `cron.daily' started Apr 5 07:16:54 office-desktop anacron[1663]: Updated timestamp for job `cron.daily' to 2014-04-05 Apr 5 07:17:01 office-desktop CRON[1718]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Apr 5 07:18:31 office-desktop kernel: [ 423.264027] usb 1-1: new high-speed USB device number 2 using ehci-pci Apr 5 07:18:31 office-desktop kernel: [ 423.397250] usb 1-1: New USB device found, idVendor=14cd, idProduct=121c Apr 5 07:18:31 office-desktop kernel: [ 423.397258] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=2 Apr 5 07:18:31 office-desktop kernel: [ 423.397262] usb 1-1: Product: Mass Storage Device Apr 5 07:18:31 office-desktop kernel: [ 423.397267] usb 1-1: Manufacturer: Generic Apr 5 07:18:31 office-desktop kernel: [ 423.397271] usb 1-1: SerialNumber: 812320100708 Apr 5 07:18:31 office-desktop mtp-probe: checking bus 1, device 2: "/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-1" Apr 5 07:18:31 office-desktop mtp-probe: bus: 1, device: 2 was not an MTP device Apr 5 07:18:31 office-desktop kernel: [ 423.509569] usb-storage 1-1:1.0: USB Mass Storage device detected Apr 5 07:18:31 office-desktop kernel: [ 423.510030] scsi6 : usb-storage 1-1:1.0 Apr 5 07:18:31 office-desktop kernel: [ 423.510326] usbcore: registered new interface driver usb-storage Apr 5 07:18:32 office-desktop kernel: [ 424.508746] scsi 6:0:0:0: Direct-Access USB Mass Storage Device PQ: 0 ANSI: 0 CCS Apr 5 07:18:32 office-desktop kernel: [ 424.509408] sd 6:0:0:0: Attached scsi generic sg2 type 0 Apr 5 07:18:32 office-desktop kernel: [ 424.656315] sd 6:0:0:0: [sdb] 31116288 512-byte logical blocks: (15.9 GB/14.8 GiB) Apr 5 07:18:32 office-desktop kernel: [ 424.656926] sd 6:0:0:0: [sdb] Write Protect is off Apr 5 07:18:32 office-desktop kernel: [ 424.656932] sd 6:0:0:0: [sdb] Mode Sense: 03 00 00 00 Apr 5 07:18:32 office-desktop kernel: [ 424.657551] sd 6:0:0:0: [sdb] No Caching mode page found Apr 5 07:18:32 office-desktop kernel: [ 424.657558] sd 6:0:0:0: [sdb] Assuming drive cache: write through Apr 5 07:18:32 office-desktop kernel: [ 424.663553] sd 6:0:0:0: [sdb] No Caching mode page found Apr 5 07:18:32 office-desktop kernel: [ 424.663562] sd 6:0:0:0: [sdb] Assuming drive cache: write through Apr 5 07:18:32 office-desktop kernel: [ 424.671713] sdb: sdb1 sdb2 sdb3 < sdb5 sdb6 > sdb4 Apr 5 07:18:32 office-desktop kernel: [ 424.677852] sd 6:0:0:0: [sdb] No Caching mode page found Apr 5 07:18:32 office-desktop kernel: [ 424.677873] sd 6:0:0:0: [sdb] Assuming drive cache: write through Apr 5 07:18:32 office-desktop kernel: [ 424.677884] sd 6:0:0:0: [sdb] Attached SCSI removable disk Apr 5 07:18:33 office-desktop kernel: [ 425.533543] EXT4-fs (sdb5): warning: mounting fs with errors, running e2fsck is recommended Apr 5 07:18:33 office-desktop kernel: [ 425.534154] EXT4-fs (sdb6): warning: maximal mount count reached, running e2fsck is recommended Apr 5 07:18:33 office-desktop kernel: [ 425.537645] EXT4-fs (sdb5): mounted filesystem with ordered data mode. Opts: (null) Apr 5 07:18:33 office-desktop kernel: [ 425.560205] EXT4-fs (sdb6): mounted filesystem with ordered data mode. Opts: (null) Apr 5 07:18:33 office-desktop kernel: [ 425.564739] FAT-fs (sdb4): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. Apr 5 07:18:33 office-desktop udisksd[1403]: Mounted /dev/sdb4 at /media/office/KOBOVOX on behalf of uid 1000 Apr 5 07:18:33 office-desktop kernel: [ 425.600208] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null) Apr 5 07:18:33 office-desktop udisksd[1403]: Mounted /dev/sdb5 at /media/office/3f497e60-5913-4a3a-ae7e-18fe045bca20 on behalf of uid 1000 Apr 5 07:18:33 office-desktop udisksd[1403]: Mounted /dev/sdb6 at /media/office/06841146-0c21-4589-96b8-d7397f4506b4 on behalf of uid 1000 Apr 5 07:18:33 office-desktop udisksd[1403]: Mounted /dev/sdb1 at /media/office/57f8f4bc-abf4-0000-675f-946fc0f9f25b on behalf of uid 1000 ls -ald update ^C office@office-desktop:~$ ls -ald update drwxr-xr-x 2 office office 4096 Mar 21 23:04 update office@office-desktop:~$ cd update office@office-desktop:~/update$ zip -r9 ../update-rooted.zip . zip error: Nothing to do! (try: zip -r9 ../update-rooted.zip . -i .) office@office-desktop:~/update$ cd .. office@office-desktop:~$ ls -al update-rooted.zip ls: cannot access update-rooted.zip: No such file or directory office@office-desktop:~$ Seeing as this is all good learning for me, would it help if I started from scratch and did it all in one go? Would we see my mistake then? Could I have done something wrong picking up from where I left off in a previous session? How do I search to see where the zip file is located on my system? In the file path /home/office/vox there is a file called update zip if that helps. Roberto.

04-07-2014, 04:29 PM	#205
Difflugia Testate Amoeba Posts: 3,049 Karma: 27300000 Join Date: Sep 2012 Device: Many Android devices, Kindle 2, Toshiba e755 PocketPC	The update directory is empty (the "nothing to do" is telling you that there are no files to add to the zip). That means that something in "Preparing the Files" failed. At this point, it's probably easier for you to redo that section than for me to troubleshoot what exactly went wrong (you should just need to do that section, though... you shouldn't need to redo the backup). When that section's done and you try doing the zip command, the output should be a stack of files being added to the update-rooted.zip. When I get some time, I'll redo that section and capture the output. I'll post it so you can check for differences that might indicate errors.

04-12-2014, 09:43 AM	#206
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Hi Guys. First off, a big thankyou to you all for your help so far. I followed your advice and it has worked up to a point. The rooted zip has installed, but I have stuffed up somewhere on the partitioning side. I know this because I have successfully put in my 16GB Sandisk card and did a factory restart and now have a brand new looking kobo vox with the superuser app on the apps page, which opens. However, the settings shows that the internal SD card has no memory, and I cannot download apps onto the kobo. I have put the old one back in and everything works fine. What would be the best way (commands)to get the necessary information on the terminal screen to post so you can see which bit I have gotten wrong? At this point:- Enter "n" to create a new partition. Enter "e" to create an extended partition. Then enter partition number 3. Hit enter to select the default first sector and type "+4G" (for four gigabytes) for the last sector. ,did I do the right thing in typing +4G immediately after the default sector line and then hit return to get to the last sector? A line or two after that, I got an out of range message. I know I am nearly at the end of this, and can't believe I have even gotten this far. Cheers, Roberto.

04-18-2014, 12:27 AM	#207
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Don't know if I have done the right thing or not, but I have deleted partitions 6-3, and tried to start from that point. Have tried writing +4G after the first sector, but eventually I get a line saying out of range. Get a different error message when typing it after the next line for last sector. Also now seem to have lost partition 6 as an automatic option. Below is one of a few attempts. Command (m for help): p Disk /dev/sdb: 15.9 GB, 15931539456 bytes 4 heads, 16 sectors/track, 486192 cylinders, total 31116288 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xcf3814cc Device Boot Start End Blocks Id System /dev/sdb1 92160 616448 262144+ 83 Linux /dev/sdb2 616449 1665025 524288+ 83 Linux Command (m for help): n Partition type: p primary (2 primary, 0 extended, 2 free) e extended Select (default p): e Partition number (1-4, default 3): 3 First sector (2048-31116287, default 2048): +4G Last sector, +sectors or +size{K,M,G} (8388608-31116287, default 31116287): Using default value 31116287 Command (m for help): n Partition type: p primary (2 primary, 1 extended, 1 free) l logical (numbered from 5) Select (default p): p Selected partition 4 First sector (2048-31116287, default 2048): Using default value 2048 Last sector, +sectors or +size{K,M,G} (2048-92159, default 92159): Using default value 92159 Command (m for help): n All primary partitions are in use Adding logical partition 5 First sector (8390656-31116287, default 8390656): +3500M Value out of range. First sector (8390656-31116287, default 8390656): Using default value 8390656 Last sector, +sectors or +size{K,M,G} (8390656-31116287, default 31116287): Using default value 31116287 Command (m for help): w The partition table has been altered! Calling ioctl() to re-read partition table. WARNING: Re-reading the partition table failed with error 16: Device or resource busy. The kernel still uses the old table. The new table will be used at the next reboot or after you run partprobe(8) or kpartx(8) Syncing disks. root@office-desktop:/home/office# Cheers, Roberto.

04-21-2014, 08:34 PM	#208
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Me again. I have started from scratch and stopped before expanding to 16Gb, and have now successfully rooted my Kobo and have 8Gb of memory. Thanks for all of your help. I did try Gparted on Lubuntu as an alternative form of expanding, but was equally unsuccessful. If anyone can give me some pointers on this last stage, using any method, I would be more than happy to take apart my Kobo again to complete this job. Thanks, Roberto.

06-09-2014, 09:11 AM	#209
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Hi, me again. Have now successfully rooted two kobo vox's but still have not been able to expand the partitions to 16Gb. I am sure I am doing something wrong at the creating new partition stage in terms of size allocation. Any pointers? Is there a youtube tutorial or something similar that I have not found yet? Cheers, Roberto.

06-15-2014, 08:29 PM	#210
mightyzazz Enthusiast Posts: 32 Karma: 10 Join Date: Aug 2013 Device: kobo vox	Hi Guys. Not to worry. Having spent a very worthwhile weekend learning how to use Gparted properly, i have finally expanded my SD card. Thank you all so much for your help, it has been a fantastic learning experience. I have just fallen at the last small hurdle now. I have very limited Superuser options (updates/temp unroot and OTA survival) - which boxes should be ticked to get it to work? a fail message came up the first time I tried to run it and the Google update app did not work, so in the end I just started the whole SD card process from scratch, to begin with an unused superuser account without permissions. Do I need to install the google app fixer? When I install busybox or Connectbot etc, I used to get a root access permission request, which allowed them to work, but now i don't and they do not seem to be installed properly. Any ideas/ Cheers, Roberto.