yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] docsmith:
qualcomm hsusb drivers

I used a win 7 64bit home premium notebook to install the hsusb drivers, and it was not necessary to use windows xp mode.

You should enable usb debugging mode on the ereader (I think under settings -> applications -> development (or was it advanced?)) and make sure it is on when you plug the usb cable to your pc and ereader. Turn off usb mass storage mode (pull down the menu information bar) if you want to use adb. Windows will try to install new drivers and you select search for drivers from specific location, go to where you put the android-drivers folder and ango into amd64 folder (for 64 bit windows in my case, but if you have 32 bit windows you may need to use i386 folder instead) and it will install one of the drivers.If it does not install repeat for the other hsusb ports found by windows new hardware wizard until one of the 6 ports installs correctly. If I remember correctly, I repeated this process for the Qualcomm_driver folder until another of the unknown hardware devices were installed. With two working I could ether turn on mass storage mode by the pull down menu from the devices information bar, or have it in adb mode.

With my bricked device my pc still does not have drivers for the other ports, but the adb mode and mass storage drivers are useable as you can see from the screen capture. Pls let me know if you need further information.

You will also need to install the android sdk (and slect the files for working on a android 2.3.5 system)

One tip if your device hangs up is to press power and volume up at the same time for about 10 seconds and the device will reboot (and should be recogized by adb)
[Android Q&A, Help & Troubleshooting] imachine:
Ordered mine this morning through collectkorea - will be joining you soon - I think this device should be able to run CM9 :)

I like CM9 because the browser has been updated enough to work well with a webpage I need to use for work. Other than that, well - ICS or jbean = :)
[Android Q&A, Help & Troubleshooting] drewid4:
Half way there?

Hi all, Iv been following this thread for a while. I have managed to use my Kyobo as more than a reader for a week or so. I have been installing by via adb commands, downloading from blackmart (which I sideloaded using adb install) and moving to the SD card and installing via another installing app. I have managed to cover up the kyobo nonsense with go launcher but AndroidMarket/PlayStore remains illusive. I understand that I may need to root my device still if I want this to work but I can't seem to get the reader into fast boot, and my cmd writing is amateurish at best.

Any advice or ideas on how to get my Kyobo into the AppMarket without rooting would be great, otherwise the often questionable delights of Blackmart may remain my only option.
[Android Q&A, Help & Troubleshooting] docsmith:
Fastboot

Getting fastboot to start is via (with device off) power button and volume down (continuous press for several seconds), or if device is on/ not responding press power & volume up for about 10s, and after the device switches off and about to reboot press volume down. If you mistimed it and adb has started instead, you can try the adb command

adb reboot bootloader

The adb command works on my rooted machine but I dont know if it works with the original firmware.

With go launcher, did you use it to redefine the home screen launched by the home button from the kyobo reader app to the go launcher, and is this working reliably? I am unsure whether it was after I used go launcher to redefine my home screen or whether it was the google over the air update that caused my machine to boot to blank screen, and it is now bricked until som kind soul can post a full adb backup of their firmware for me to restore my machine.

---------- Post added at 03:17 PM ---------- Previous post was at 03:05 PM ----------

How much did you pay for in total? I paid 99000 won in the kyobo bookstore, but that included sales tax which I could not reclaim when I left Korea.

I look forward to your joining us and helping create a custom recovery based on CM9.
[Android Q&A, Help & Troubleshooting] imachine:
I paid ~135$ with shipping. Got it in 4 days, arrived an hour ago, still not rooted - will play with it later. It's not as superb as I've seen but it's pretty interesting nonetheless. Once I get root I'll fully see the potential.

The device I ordered has the following firmware revision/version:

2.3.5, 20111219.
[Android Q&A, Help & Troubleshooting] docsmith:
Backup via adb?

Can you please post a backup of your brand new machine using adb backup command to generate the backup file which has extension ab. I have bricked my reader and I am desperate to get a backup of the whole system to restore it.
[Android Q&A, Help & Troubleshooting] imachine:
Here's how I got root and market working on my Kyobo:

1) Updated to latest (201206) firmware from m.kyobobook.co.kr/mirasol/update.zip (put it on sd card, rebooted, once booted back in, chose to wipe fully both device and sd, rebooted).

Switched to English, now USB debugging is enabled and when I go into ./adb shell and type 'su' I am root. Cool.

No need to fiddle with boot.img, the following instructions:

Are the ones I used - however - in fixsu.sh I needed to change the line

/system/bin/mount -o remount,rw /dev/block/mmcblk0p23 /system

into

/system/bin/mount -o remount,rw /dev/block/mmcblk0p12 /system

it seems the /system resides elsewhere in my device.

I didn't bother with the .db hack since non-market updates were already enabled by default with the 201206 firmware.

I later put in market on the device, however I was unable to push the files directly, so I pushed them to /data/local/tmp, chown/chgrp to root, chmod .apk 644 and the init file in /etc/, logged in to adb with ./adb shell, su'd, remounted /system rw and copied them manually from /data/local/tmp into /system/app/ and /etc, respectively.

Chmodded 777 and ran fix-shared-user.sh, the device rebooted as expected, and now market etc work - I just installed Maps, Google Drive, Adobe Flash and Adobe Reader.

Good times so far :)

Read below.

If you used the scripts blindly on 201206 firmware, you possibly remounted the wrong device as /system, henceforth causing the drama you're now experiencing.

-----

If you encounter issues, here's how to force a hardware reboot, thanks to http://www.the-digital-reader.com/2...d-with-a-kyobo-mirasol-ereader/#.UBGD8iNT12M:

"Hard Reset

I’ve just picked up another tip. If your device freezes, you can force a reboot. Press and hold the power button and up volume button for 5 seconds. Then try to turn it on again."

-----

My device seems to hang quite some lot (it hanged 4 times today, I haven't used it before rooting so actually it's hard to say whether it's hardware or software related).

After running V6 supercharger script, I have not yet had the device hang.
[Android Q&A, Help & Troubleshooting] imachine:
Whoopdee-doo - I've got Google Talk, Calendar and Contacts to sync :)

What I did:

* pulled gapps-gb-20110828-signed.zip from goo.im

* cp'ed:

GoogleCalendarSyncAdapter.apk
GoogleContactsSyncAdapter.apk
MediaUploader.apk
Talk.apk

into /system/app (after remounting /sytem/ as rw ofcourse)

I'm not sure if MediaUploader.apk is necesary, but I threw it on there anyway.

After reboot, Google Calendar and Google Contacts sync with my google accounts and Talk logs in! :)

I installed gtalk with video from gapps-gb-20110828-newtalk-signed.zip - it logs in correctly, haven't tested the video chat yet, I presume video decoding down and audio up and down would work.

I still cannot download anything using stock browser (the Downloads.apk or whatever it's called app is missing). Can someone provide the apk with correct API level (2.3.5) ? Maybe I could just use CM7 rom for another device and get the .apk from there?
[Android Q&A, Help & Troubleshooting] docsmith:
I'm eagerly awaiting your system.img post so that I can inbrick my device via fastboot.

One possible cause for your system hangs may be the small cache size in the original firmware, Before my machine bricked I experimented with cache fixer to move the cache - it helped fix some apps but others apps still crashed.
[Android Q&A, Help & Troubleshooting] faisal400:
also me, i need to unbrick my device
[Android Q&A, Help & Troubleshooting] imachine:
ok, I have modified my system with:

1) stock 2.3 latin font (including Polish diactrics, for example)

2) market and root.

3) google contacts, google calendar, and google talk sync.

4) busybox-1.19-wraithdu (latest from v6 thread)

I also used v6 supercharger (v6_9_Rc10) that helped the hangs and overall snapiness. (if you recover from this .img you might be in need to re-run the v6 supercharger script).

Cache gets sorted with the init script modified accordingly to the rooting or market post (/etc/init.qcom.post_boot.sh).

Here you go guys:

dd of=system.img if=/dev/block/mmcblk0p12

409600+0 records in

409600+0 records out

209715200 bytes transferred in 30.383 secs (6902386 bytes/sec)

md5:

53c82ccc908a78daff75650fdd271190 system.img

http://imc.mlink.net.pl/system-27072012.img.tgz

If I'm doing something with the above against anybody's intellectual property, please inform me and I will remove access to the above file. Regards.
[Android Q&A, Help & Troubleshooting] docsmith:
Imachine: I succeeded in flashing system using fastboot (but I had to extract your gz archive twice with 7zip. The first time produces an img file that is 209725440 byte which is too large to flash but running 7zip again on this file creates a file that is 209715200 bytes which is exactly the right size to flash system using fastboot.

Many thanks!!! I now have adb shell commands working again but my device is stll booting into a blank screen...

Did you change the boot.img or recovery.img from those found on the update.zip and is it possible to post an image of data as I dont have any files in my data partition either (possibly explains why I have blank screen on bootup)
[Android Q&A, Help & Troubleshooting] imachine:
data is not a problem because data gets wiped when you, well, 'wipe data' ;) so it's personal stuff on there. do you get adb logcat? can you run adb shell? if there's a way to invoke a cache/data wipe from adb shell, you should be good to go :)

here's how it looks over here:

# fdisk -l /dev/block/mmcblk0

Disk /dev/block/mmcblk0: 3856 MB, 3856662528 bytes
1 heads, 16 sectors/track, 470784 cylinders
Units = cylinders of 16 * 512 = 8192 bytes

Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 12801 102400 c Win95 FAT32 (LBA)
Partition 1 does not end on cylinder boundary
/dev/block/mmcblk0p2 * 12801 12863 500 4d Unknown
Partition 2 does not end on cylinder boundary
/dev/block/mmcblk0p3 12863 13051 1500 46 Unknown
Partition 3 does not end on cylinder boundary
/dev/block/mmcblk0p4 13051 471296 3665967+ 5 Extended
Partition 4 does not end on cylinder boundary
/dev/block/mmcblk0p5 16385 16509 1000 47 Unknown
/dev/block/mmcblk0p6 16510 16759 2000 5d Unknown
/dev/block/mmcblk0p7 16760 17143 3072 58 Unknown
/dev/block/mmcblk0p8 17144 17783 5120 48 Unknown
/dev/block/mmcblk0p9 17784 18658 7000 50 Unknown
/dev/block/mmcblk0p10 18659 19042 3072 4a Unknown
/dev/block/mmcblk0p11 19043 19426 3072 4b Unknown
/dev/block/mmcblk0p12 19427 45026 204800 83 Linux
/dev/block/mmcblk0p13 45027 176098 1048576 83 Linux
/dev/block/mmcblk0p14 176099 177122 8192 83 Linux
/dev/block/mmcblk0p15 177123 178146 8192 83 Linux
/dev/block/mmcblk0p16 178147 453090 2199552 83 Linux
/dev/block/mmcblk0p17 453091 453730 5120 60 Unknown
/dev/block/mmcblk0p18 453731 471296 140527+ 83 Linux

and these are the running system mounts:

/dev/block/mmcblk0p12 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p13 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p14 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p16 /NAND ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p13 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered,noauto_da_alloc 0 0

I can dump 14,16, 12 you already have, 2 looks like boot, the rest I don't know about :)

Maybe try to adb shell into the device if it boots and you can get adb access, and su; fdisk -l /dev/block/mmcblk0 in order to see the differences between our devices.

I guess you could always try to pull the update.zip from kyobobook.co.kr onto your sd card's root and boot into recovery. Maybe it would work now?
[Android Q&A, Help & Troubleshooting] faisal400:
i unbricked the mirasol

i used boot.img and recovery.img from kyobo update

then used system.img from (imachine) post

fastboot flash boot path to boot.img

fastboot flash recovery path to recovery.img

fastboot flash system path to system.img

fastboot reboot

and it worked

it was trial and error

and the truth i don't what the command do, i know it flashes the img and thats it, where and why and which folders or other, i dont know
[Android Q&A, Help & Troubleshooting] docsmith:
I am using the boot.img and recovery.img from the official update.zip and your system.img. I had previously completetly deleted data (including any directory structures such as data/local/tmp and also have done fastboot -w which wipes the data and cache.)

I get "segmentation fault" when I try su.

I dont have write permission for /data. I can get into adb shell but cant run fdisk since I dont have permission. With the mount commnd I can confirm that system is in blk12

(see attachment of screen mount screen capture).

Since I cant write to file I can only do screen capture. The processes running in my adb shell (see picture attached) and the logcat output (obtained from adb logcat -d > logs.txt) are also attached.

Imachine - can you please explain in detail your post #65 on how you got root using the official boot.img or update.zip? What do you mean by boot into recovery (is it adb boot recovery?) where did you get the option to fully wipe device and sd?
[Android Q&A, Help & Troubleshooting] sobolz:
Hi, imachine! Do you have Google Maps and Drive actually working? My device freezes every time I try to launch GMaps of in fact any other map-related app.

Does anyone have working Maps at all? Or is it only me so unlucky?
[Android Q&A, Help & Troubleshooting] docsmith:
Imachine: From the logcat output I am getting errors on boot up because I don't have required files in the data partition. Can you please post an image of the data partition (blk13). I am not interested in your personal data, so pls backup an image with all your data, ( so you can restore later) and then do a factory reset to wipe all your personal stuff, before creating the data.img of a factory-like build that I can use to restore the data partition. This is probably the simplest path I have to inbrick my device.
[Android Q&A, Help & Troubleshooting] sobolz:
Thanks! I'll try that.
[Android Q&A, Help & Troubleshooting] docsmith:
IMachine: It is very kind of you to include some useful apps in the data.img, but I found there is a limit on size of img file that can be sent to the data partition using fastboot. I have been experimenting to try to build my own data.img from a directory of ext4 files using mkfs.yaffs2.x86 on a ubuntu system and I discoverd that fastboot can send about 180MB sized data.img file (but unfortunately fails in writing the data.img with the error message "FAILED partiton table doesn't exist"). When I try to send a 280MB size data.img file fastboot errors out immediately with the message "FAILED (remote data too large)".

Hence I guess only a skeleton data partition image, perhaps with a data.img file less than ~200MB (not sure of the exact limit) is needed. I probably only need the directory stuctures for dalvik_cache, local/tmp, and probably whatever system or mirasol related setup files that are in there.

At present only fastboot has write access to my machine (I can no longer use throwaway's method of rooting since I cant push any file to a nonexistant data/local/tmp and dont have adb write priviledge to push to any directory at present as remount fails without su priviledge)

EDIT UPDATE: After much experimenting I found /NAND/ was mounted as read write, and thus /NAND/ could be used instead of the missing /data/local/tmp as the temporary location for pushing the (modified with /NAND/ replacing all occurences of /data/local/tmp) fixsu.sh and busybox etc. I now have get root access again after rebooting with the modified boot.img (found in throwaways' post #5 in this thread).

Now I only need help to identify and get the correct configuation files to put into the data partition to unbrick....
[Android Q&A, Help & Troubleshooting] imachine:
Well, I guess this solution is screwed for you then because the data partition will always be 1GB in size - even if I populate it with files or not - that's the parition's size. So, you'll push "0'es", but still will have to push 1GB.

I think by the solution you could use is to pull the recovery partition, modify it so it runs adb as root, boot into recovery, and dd /dev/block/mmcblk0 image (which will include the, possibly broken by you earlier, partition table) from an earlier prepared 8GB sd card. 8GB, because /dev/block/mmcblk0 is 4GB.

I plan on trying to port ClockworkModRecovery to the Kyobo, so maybe once that's in place, you'll be able to use that solution.

Like another user wrote here, having boot.img, recovery.img and the system.img I posted earlier should be enough.

---------- Post added at 08:01 PM ---------- Previous post was at 08:00 PM ----------

Post your logcat output starting from boot till boot is finished.
[Android Q&A, Help & Troubleshooting] docsmith:
My logcat output is attached. The simplest solution maybe, if you already prepared your data.img , is for me to use dd to restore it on my machine even if fastboot cant? Can you pls post your pristine data.img (I will need help with the parameters to use with the dd command to recover it).
[Android Q&A, Help & Troubleshooting] imachine:
Sure, you could just dd the image file.

Here's the file:

http://imc.mlink.net.pl/data-28072012.img.tgz

As usual, tar -zxf data-28072012.img.tgz, copy it onto your sd, once it's there, boot, go into adb, su, and then:

dd of=/dev/block/mmcblk0p13 if=/sdcard/data-28072012.img bs=4096k

This needs you be able to su from adb. But, the errors you have, don't look like *crucial* errors-this is just dalvik-cache - from what I know, it ought to get rebuilt automatically if missing. I purged dalvik-cache dir contents from my data.img anyway.

I think the data recovery won't do you much, you'll have to dd the entire mmcblk0 image, includng the partition table etc.
[Android Q&A, Help & Troubleshooting] docsmith:
My sdcard was not mounted on bootup so I could not put the 1GB img file onto the filesystem for dd to work. However after much trial and error I managed to build a data.img using ubuntu

make_ext4fs -l 200M -a data data.img datadir

, where datadir is the name of the directory that I had archived all my original data partition files (using adb pull data datadir) before I trashed it. This allowed me to flash it using

fastboot flash userdata data.img

.

Not surprisingly my original boot problem remained. and from the logcat output (attached) that problem might be caused by the go launcher app that I had installed to replace the kyobo home screen. Has anyone got similar problem of booting to blank screen (with the light coming on after about 1 minute ) after installing go launcher and can anyone suggest how to fix this?

With the restored data partition, my sdcard mounted properly and I could then use imachine's data.img using dd as he suggested . I also fast boot flashed the system with imachines system image and tried both the boot img from update.zip and the boot.img from throwaway's post #5 (only throwaway's boot.img allows me root access).

But I still boot to a blank screen (second logcat output file) and I cant see why apart from the android javavm failing to start. With Imachine's data img and system img the bootup is crashing earlier than with my original data.img and it fails to even mount the sdcard..
[Android Q&A, Help & Troubleshooting] imachine:
Did you purge both kyobo homescreen and golauncher? My data.img contains adwlauncher, I would delete go launcher if that is what causes your issues. I personally think its something else.
[Android Q&A, Help & Troubleshooting] docsmith:
IT seems the partition sizes etc of my machine are identical to the ones you listed with fdisk in your earlier post.

Using your data.img and system.img with the rooted boot.img from throwaway post #5, I still boot to a blank screen but the display lights up (and after a few minutes turns off as if the power management is working ok). The full logcat is attached. The logcat indicates it is now booting ok to zygote but the following errors apear:

I/Zygote ( 89): ...preloaded 1829 classes in 3426ms.

E/Zygote ( 89): setreuid() failed. errno: 17

I/Zygote ( 89): Preloading resources...

W/Zygote ( 89): Preloaded drawable resource #0x1080093 (res/drawable-hdpi/sym_def_app_icon.png) that varies with configuration!!

..

E/libEGL ( 177): eglSetSwapRectangleANDROID:1848 error 3008 (EGL_BAD_DISPLAY)

I/SystemServer( 177): Entered the Android system server!

I/SystemServer( 177): Entropy Service

W/zipro ( 195): Unable to open zip '/data/local/bootanimation.zip': No such file or directory

E/SurfaceFlinger( 177): eglSwapBuffers: EGL error 0x3008 (EGL_BAD_DISPLAY)

and at the end there are some errors related to su.

E/Database( 421): sqlite3_open_v2("/data/data/com.noshufou.android.su/databases/permissions.sqlite", &handle, 6, NULL) failed

E/Su.PermissionsDbService( 421): encountered an exception, schedule a restart

E/Su.PermissionsDbService( 421): android.database.sqlite.SQLiteException: unable to open database file

Do you see similar errors in your logcat? Have you got any suggestions on how to unbrick? Maybe one of the low level configuration files got screwed up by go launcher when it redirected the home button from the kyobo program to its own custom menu and corrupted whatever configuration file that is being referred to by the warning message "drawable resource #0x1080093 (res/drawable-hdpi/sym_def_app_icon.png) that varies with configuration!!" The mysterious configuration file is not on boot, system or data partitions as these have been flashed.
[Android Q&A, Help & Troubleshooting] imachine:
Go launcher shouldn't do that, it just writes as a default app, I set adwlauncher as default and boot fine. I'll have a look some time soon,won't promise anything else.
[Android Q&A, Help & Troubleshooting] docsmith:
I copied the various configuration files found on root eg by

adb shell
$ login root
# /system/xbin/cp init.rc /sdcard

and have attached them. Can someone please help me in my attempts to unbrick my mirasol by doing a binary file compare (e.g. using windows command window fc command) of these files with those on your machine? Pls post if you see some differences.

(These configuration files are on my machine after flashing boot, systemrecovery and data partitions from imachine's data and system and the kyobo boot and recovery images.

The *.rc files are text files but init is a binary file.)
[Android Q&A, Help & Troubleshooting] docsmith:
Bad recovery ?how to unbrick?

My kyobo is booting to blank screen, and no matter what changes i try i cant get anything to display on screen. When i try using the system.img and data.img kindly provided by imachine, the boot seems to happen twice, suggesting it is using the recovery.img and not booting successfully.

Maybe the recovery.img in the official update.zip is broken?

Can someone pls back up their kyobo, then delete any personal stuff and do a full backup of all (boot, system,recovery and data) partitions to help me unbrick?
[Android Q&A, Help & Troubleshooting] primalmike:
Kyobo?

I know this might be the wrong thread to ask, but...does anyone know where I might get one to toy with?

I found a place online (shopereaders) and ordered and they had to cancel because it's been discontinued. Checked Ebay, ShopKorea, etc., with no luck.

Any help would be greatly appreciated. :confused: