[Guide][Root & MOD]Icarus Illumina (E653) AND Boyue T61+T62

[cameld00d]

Originally Posted by nightboy

Please check build.prop

Assuming ADB is working

Run the following command:

adb pull /system/build.prop

open build.prop and read the date (ro.build.date)
The img's system's files were given in July.

if it is not July, then there must be a problem in the connection.(IMG has not been installed)

You should also try factory reset (using adb):

adb shell
wipe data

there are many ways to fix your problem. But, I had a similar experience connecting these type of devices to laptops.

Don't have a lot of time this week, but I did try the factory reset as you recommended with adp and it reset to Chinese but no touchscreen still :-(

ANY advice would be SO appreciated. I don't want to have to deal with sending this back to China. I LOVED it when it was working. I should have left well-enough alone and not updated.

[nightboy]

Originally Posted by cameld00d

Don't have a lot of time this week, but I did try the factory reset as you recommended with adp and it reset to Chinese but no touchscreen still :-(

ANY advice would be SO appreciated. I don't want to have to deal with sending this back to China. I LOVED it when it was working. I should have left well-enough alone and not updated.

Download

"Boyue T62 Update 07/22/2014" zip file.

Rename it to update.zip

connect your device.
Copy it to adb's folder.
run:

adb push update.zip /mnt/sdcard/

Wait for it to finish.

Then Power off your device. (by holding power button for 10 sec)

Wait few sec then press and hold the refresh button (first) and the power button (second) for 5 sec.
Release the Power button but keep holding the refresh button for 5 more sec .
Release the refresh button and it should boot into recovery & install the update.zip

[ft.parham]

I'm sorry I was busy a bit.
When dear nightboy is here your problem will be solved☺ don't worry

[alejoc]

Hi, and thanks for the will to help. This is my whole build.prop:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=rk30sdk-eng 4.2.2 JDQ39 liyongdong.20141020.162910 test-keys
ro.build.version.incremental=liyongdong.20141020.1 62910
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=2014年 10月 20日 星期一 16:32:26 CST
ro.build.date.utc=1413793946
ro.build.type=eng
ro.build.user=liyongdong
ro.build.host=liyongdong-desktop
ro.build.tags=test-keys
ro.product.model=rk30sdk
ro.product.brand=Boeye
ro.product.name=T62B
ro.product.device=T62B
ro.product.manufacturer=Boeye
ro.product.locale.language=zh
ro.product.locale.region=CN
persist.sys.language=zh
persist.sys.country=CN
ro.product.board=rk30sdk
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.wifi.channels=
ro.board.platform=rk3026
# ro.build.product is obsolete; use ro.product.device
ro.build.product=T62B
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=rk30sdk-eng 4.2.2 JDQ39 liyongdong.20141020.162910 test-keys
ro.build.fingerprint=rk30sdk/rk30sdk/rk30sdk:4.2.2/JDQ39/liyongdong.20141020.162910:eng/test-keys
ro.build.characteristics=tablet
ro.boeye.provider=rk
ro.boeye.product=rk3026
ro.boeye.machine=Boyue-T62B
ro.boeye.order=China-T62B
ro.boeye.version=Boyue-Ereader_V1.0.0-2014102016
ro.boeye.customer=Boyue
net.hostname=Boyue_T62B
persist.sys.localevar=
persist.sys.timezone=Asia/Shanghai
persist.boeye.homepage=http://www.baidu.com
persist.boeye.shutdowntime=-1
persist.boeye.shortstandby=120000
persist.boeye.def_time_12_24=24
persist.boeye.preinstall=1
persist.boeye.updatemodel=Boyue-T62B
persist.boeye.statusbar=1
persist.boeye.notification=true
persist.boeye.inputMethod=com.android.inputmethod. pinyin/.PinyinIME
UserVolumeLabel=boyue
ro.boeye.shortstandby=1
ro.boeye.desktop=com.boyue.boyuelauncher
persist.service.adb.enable=1
persist.adb.notify=0
# end build properties
#
# system.prop
#

#rild.libpath=/system/lib/libreference-ril.so
#rild.libargs=-d /dev/ttyUSB2
# Default ecclist
ro.ril.ecclist=112,911

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
ro.sf.lcdc_composer=0
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ril.function.dataonly=0
persist.sys.strictmode.visual=false
dalvik.vm.jniopts=warnonly
ro.rksdk.version=RK30_ANDROID4.2.2-SDK-v1.00.00
sys.hwc.compose_policy=6
sys.wallpaper.rgb565=0
sf.power.control=2073600
sys.rkadb.root=0
ro.sf.fakerotation=false
ro.rk.MassStorage=false
ro.rk.systembar.voiceicon=false
ro.rk.systembar.tabletUI=true
wifi.interface=wlan0
ro.tether.denied=false
ro.sf.lcd_density=212
sys.resolution.changed=false
ro.rk.screenoff_time=60000
ro.rk.def_brightness=200
ro.rk.homepage_base=http://www.google.com/webhp?client={CID}&source=android-home
ro.rk.install_non_market_apps=false
ro.default.size=100
ro.product.usbfactory=rockchip_usb
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.factory.tool=0
ro.kernel.android.checkjni=0
ro.rk.bt_enable=true
ro.factory.storage_policy=0
persist.sys.usb.config=mass_storage
testing.mediascanner.skiplist=/mnt/sdcard/Android/
ro.product.version=1.0.0
ro.product.ota.host=www.rockchip.com:2300
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

I already did the factory reset via ADB to no avail. When I try to enter recovery mode, I only get the Android image with the warning sign, but nothing else happens.

Originally Posted by nightboy

Please check build.prop

Assuming ADB is working

Run the following command:

adb pull /system/build.prop

open build.prop and read the date (ro.build.date)
The img's system's files were given in July.

if it is not July, then there must be a problem in the connection.(IMG has not been installed)

You should also try factory reset (using adb):

adb shell
wipe data

there are many ways to fix your problem. But, I had a similar experience connecting these type of devices to laptops.

[cameld00d]

Originally Posted by nightboy

Download

"Boyue T62 Update 07/22/2014" zip file.

Rename it to update.zip

connect your device.
Copy it to adb's folder.
run:

adb push update.zip /mnt/sdcard/

Wait for it to finish.

Then Power off your device. (by holding power button for 10 sec)

Wait few sec then press and hold the refresh button (first) and the power button (second) for 5 sec.
Release the Power button but keep holding the refresh button for 5 more sec .
Release the refresh button and it should boot into recovery & install the update.zip

Trouble is, this problem happened because I updated to that image... obviously I will still try it again once I have a sec.

Is there an alternative image? Any chance they have posted a newer update somewhere that someone can find? I looked but had no luck.

[fil9998]

Hi everybody!

Anyone figured out how to add dictionaries to stock adobe reader or / and KOREADER or / and moon+ reader ?

I downloaded stardict 's dictionaries but cannot figure out how to install them on these readers.

Thank you so much for your kind help.

[Purple Lady]

Originally Posted by fil9998

Hi everybody!

Anyone figured out how to add dictionaries to stock adobe reader or / and KOREADER or / and moon+ reader ?

I downloaded stardict 's dictionaries but cannot figure out how to install them on these readers.

Thank you so much for your kind help.

Moon+ uses Color Dict dictionary which uses Stardict data.

[nightboy]

cameld00d & alejoc

The image that you have installed is a beta ROM
ro.product.name=T62B
It could be unofficial release.

I have another tool which allow you to flash any partition (require some input). But before posting it, could you tell me what type of error you got when you tried to downgrade your ereader using posted img & RK Batch Tool ?

You are still using the beta ROM :
ro.boeye.version=Boyue-Ereader_V1.0.0-2014102016

[alejoc]

I flashed the IMG without problems and the recovery appears saying everything is normal and all partitions are flashed. The problem comes after rebooting because the reader still does not read the screen inputs. The same happens if I flash the image from July 22 and the newer beta. I will gladly try your other tool.

Originally Posted by nightboy

cameld00d & alejoc

The image that you have installed is a beta ROM
ro.product.name=T62B
It could be unofficial release.

I have another tool which allow you to flash any partition (require some input). But before posting it, could you tell me what type of error you got when you tried to downgrade your ereader using posted img & RK Batch Tool ?

You are still using the beta ROM :
ro.boeye.version=Boyue-Ereader_V1.0.0-2014102016

[nightboy]

Originally Posted by alejoc

I flashed the IMG without problems and the recovery appears saying everything is normal and all partitions are flashed. The problem comes after rebooting because the reader still does not read the screen inputs. The same happens if I flash the image from July 22 and the newer beta. I will gladly try your other tool.

I did not get it.

After flashing July 22's IMG have you checked "build.prop" ?
Does it actually install July 22 ROM (System, kernel, Bootloader, recovery) ?

[cameld00d]

Originally Posted by alejoc

Hi, and thanks for the will to help. This is my whole build.prop:



I already did the factory reset via ADB to no avail. When I try to enter recovery mode, I only get the Android image with the warning sign, but nothing else happens.

I will post my build prop but I will say I never installed the 10 beta, only the July 22 rom update. I have not been able to install anything else since that. Can't use the touchscreen whatsoever. Buttons work fine.

[alejoc]

This is the new build.prop I get and I am also enclosing a screenshot of the recovery flashing the partitions:

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=rk30sdk-eng 4.2.2 JDQ39 dela.20140705.201025 test-keys
ro.build.version.incremental=dela.20140705.201025
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Jul 5 20:14:14 CST 2014
ro.build.date.utc=1404562454
ro.build.type=eng
ro.build.user=dela
ro.build.host=dela-pc
ro.build.tags=test-keys
ro.product.model=rk30sdk
ro.product.brand=Boeye
ro.product.name=T62
ro.product.device=T62
ro.product.manufacturer=Boeye
ro.product.locale.language=zh
ro.product.locale.region=CN
ro.product.board=rk30sdk
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.wifi.channels=
ro.board.platform=rk3026
# ro.build.product is obsolete; use ro.product.device
ro.build.product=T62
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=rk30sdk-eng 4.2.2 JDQ39 dela.20140705.201025 test-keys
ro.build.fingerprint=rk30sdk/rk30sdk/rk30sdk:4.2.2/JDQ39/dela.20140705.201025:eng/test-keys
ro.build.characteristics=tablet
ro.boeye.provider=rk
ro.boeye.product=rk3026
ro.boeye.machine=Boyue-T62
ro.boeye.order=China-T62-XVGA
ro.boeye.version=Boyue-Ereader_V1.0.0-2014070520
ro.boeye.customer=Boyue
net.hostname=Boyue_T62
persist.sys.localevar=
persist.sys.timezone=Asia/Shanghai
persist.boeye.homepage=http://www.baidu.com
persist.boeye.shutdowntime=-1
persist.boeye.shortstandby=120000
persist.boeye.def_time_12_24=24
persist.boeye.statusbar=1
persist.boeye.inputMethod=com.android.inputmethod. pinyin/.PinyinIME
UserVolumeLabel=boyue
ro.boeye.shortstandby=1
ro.boeye.desktop=com.boyue.boyuelauncher
persist.service.adb.enable=1
persist.adb.notify=0
# end build properties
#
# system.prop
#

#rild.libpath=/system/lib/libreference-ril.so
#rild.libargs=-d /dev/ttyUSB2
# Default ecclist
ro.ril.ecclist=112,911

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.config.alarm_alert=Alarm_Classic.ogg
persist.sys.language=zh
persist.sys.country=CN
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
ro.sf.lcdc_composer=0
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
ril.function.dataonly=0
persist.sys.strictmode.visual=false
dalvik.vm.jniopts=warnonly
ro.rksdk.version=RK30_ANDROID4.2.2-SDK-v1.00.00
sys.hwc.compose_policy=6
sys.wallpaper.rgb565=0
sf.power.control=2073600
sys.rkadb.root=0
ro.sf.fakerotation=false
ro.rk.MassStorage=false
ro.rk.systembar.voiceicon=false
ro.rk.systembar.tabletUI=true
wifi.interface=wlan0
ro.tether.denied=false
ro.sf.lcd_density=212
sys.resolution.changed=false
ro.rk.screenoff_time=60000
ro.rk.def_brightness=200
ro.rk.homepage_base=http://www.google.com/webhp?client={CID}&source=android-home
ro.rk.install_non_market_apps=false
ro.default.size=100
ro.product.usbfactory=rockchip_usb
wifi.supplicant_scan_interval=15
ro.opengles.version=131072
ro.factory.tool=0
ro.kernel.android.checkjni=0
ro.rk.bt_enable=true
ro.factory.storage_policy=0
persist.sys.usb.config=mass_storage
testing.mediascanner.skiplist=/mnt/sdcard/Android/
ro.product.version=1.0.0
ro.product.ota.host=www.rockchip.com:2300
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

[Image violates guidelines for size - MODERATOR]

Originally Posted by nightboy

I did not get it.

After flashing July 22's IMG have you checked "build.prop" ?
Does it actually install July 22 ROM (System, kernel, Bootloader, recovery) ?

[cameld00d]

I can get it to work with adb but it won't let me update anything. Just shows the little android laying on its back with an exclamation point above it. Can't get RK batch to recognize it. Also tried fastboot to load an image but it just says "waiting on device" and does nothing.

I never get what you get, alejoc; rk batch tool have never recognized the machine. Never shows any connected devices. Sometimes windows shows it as a rockchip usb device and sometimes it shows up as an adb device. I can use adb only when it is connected as an adb device, and rk batch will not detect it in either case. The adb reboot command while holding refresh seems to change it from adb device to rockchip device but then I can't do anything with it until I reboot it into adb device mode.

Hmm, and I try and pull the build prop and consistently am getting "remote object '/system/build.prop' does not exist" now that I have done a reset. And I can't do another reset for whatever reason (adb shell, wipe data

Blah, guess I will see what I can do with some other manual tools like http://www.addictivetips.com/mobile/...-phone-device/

[alejoc]

cameld00d: does RK Batch show the device with the pink indicator or not at all? If you have Windows 8, the problem lies there. Try formatting with a Windows 7 machine.

Originally Posted by cameld00d

I can get it to work with adb but it won't let me update anything. Just shows the little android laying on its back with an exclamation point above it. Can't get RK batch to recognize it. Also tried fastboot to load an image but it just says "waiting on device" and does nothing.

I never get what you get, alejoc; rk batch tool have never recognized the machine. Never shows any connected devices. Sometimes windows shows it as a rockchip usb device and sometimes it shows up as an adb device. I can use adb only when it is connected as an adb device, and rk batch will not detect it in either case. The adb reboot command while holding refresh seems to change it from adb device to rockchip device but then I can't do anything with it until I reboot it into adb device mode.

Hmm, and I try and pull the build prop and consistently am getting "remote object '/system/build.prop' does not exist" now that I have done a reset. And I can't do another reset for whatever reason (adb shell, wipe data

Blah, guess I will see what I can do with some other manual tools like http://www.addictivetips.com/mobile/...-phone-device/

[Catire]

Have you guys tried installing the Icarus firmware? might help fix things