> Attention!

New threads need to be created only inroot partition! In the future, they will be processed by moderators.



ONYX BOOX C68 - Firmware [Android] | [6 "] [E-Ink Carta HD] [1072 Г— 1448/758 Г— 1024] Yes



Rep: (215)
Firmware forONYX BOOX C68 and modifications
C68 Series: Darwin 6 / Darwin 5 / Vasco da Gama 3 / My first book
Comparison of modifications | Discussion пїЅ | Firmware пїЅ | Common questions - Owners Club пїЅ

Discussion of firmware for Onyx Boox C68 series: Darwin 6 / Darwin 5 / Vasco da Gama 3 / My first book
Specifications
Operating system: Android 4.4.4
Screen Type: E-Ink Carta, 16 shades of gray, 14: 1 contrast ratio
Screen size, inches: 6"
Screen resolution: 1072 Г— 1448 (Carta HD in D6) / 758 Г— 1024
Touch screen: Yes
Built-in lights: diodes of two colors: blue and orange - with a separate adjustment of the intensity and, accordingly, the shade of the backlight; 13 diodes in Darwin 6 (7 blue and 6 yellow), the rest of the modifications 10 diodes (5 each color)
Supported text formats: EPUB, PDF, FB2, FB2.ZIP, TXT, DJVU, HTML, DOC, DOCX, RTF, CHM, TCR, PRC (MOBI)
Supported graphic formats: JPEG, BMP, PNG, TIFF
Audio support: There is no hardware support in the models of McCenter - the exclusive distributor in the Republic of Belarus, the Russian Federation, the USA, Ukraine
RAM, mb .: 1024 (at D6, D5) / 512 (at VdG3, IPC)
Built-in memory, mb .: 7456mb - user available about 5GB
Memory Card Support: Yes
Bluetooth support: Not
USB connector: Micro usb without USB OTG
Wi-Fi support: Yes
Text-to-Speech support: Not
Battery capacity, mAh: 3000 (actually:2 months in sleep mode without using the device, or23 thousand pages without backlight, or 10-18 thousand pages with backlight)
Sizes, mm: 170×117×8,7
Weight, gr .: 182
Equipment: e-book, USB cable, user manual, warranty card, charger, smart cover case (Vasco da Gama 3 has no last two points)
Products webpage: https://onyx-boox.ru/
Firmware updates 20.05.2019
C68 - n / d
Darwin 6 - 1.9.1-mc 2019-05-18_17-05 34d2f05 from the official site
Darwin 5 - 1.9.1-mc 2019-05-18_17-53 34d2f05 from the official site
Vasco da Gama 3 - 1.9.1-mc 2019-05-20_10-06 34d2f05 from the official site
My first book - ( 1.8.3 ) -simple-mode 2018-12-17_10-05 c8eb09a from the box
History of firmware changes
2019-05-20_10-06_1.9.1_34d2f05 VDG3
2019-05-18_17-53_1.9.1_34d2f05 D5
2019-05-18_17-05_1.9.1_34d2f05 D6
Improved mail performance.
Updated version of NeoReader.
Improved work OReader.
Updated browser version.
A number of other changes have been made.
Fixed known bugs.

2019-04-01_21-38_1.9.1_9e503ee D5, VdG3
Improved email client.
Added the ability to set book covers as screensavers.
The new version of the program OReader 1.7509500.
Improved system performance.
Removed unnecessary applications.
A number of other minor bugs fixed.
A number of other minor changes have been made.

2019-03-13_22-10_1.9.1_f18fffd D5
from the official forum for testing problems with bright / flickering lights

2018-12-18_11_42_1.9.1_9cafc8a D6
Added the ability to display the cover as a sleep screen saver.
Updated version of NeoReader.
Increased speed and stability.
A number of other changes have been made.
Fixed known bugs.

In the air, updates do not arrive and are not found when "checking on the server" from the settings
Instructions for installing firmware updates.
Ruth: getting on the reader

History of changes caps
05/28/19 Firmware updates D6, D5, VDG3, a remark that OTA does not work
04/21/19 Firmware updates for D5, VdG3
03/22/19 Firmware Update D5
02/08/19 Installing firmware updates (qq1978)


Post has been editedOptom - 02.06.19, 15:59



Rep: (220)
Optom @ 12/16/18, 14:22*
In the markup 28mb lost
With markup everything is fine, there are no address intersections, just a small piece is not registered in the markup file and this piece is most likely not allocated anywhere.
You can of course try another program to pull it out and see if there is something interesting there.
Optom @ 12/16/18, 16:25*
In principle, should not interfere with taking a dump
That's right, this is not a reason rkdump-eru interrupt the process of dumping.
Optom @ 12/16/18, 14:22*
ro.secure = 1 and ro.debuggable = 0
ro.secure = change to 0, it can affect the menu, it suddenly appears.
If in the same place there are such lines as:
persist.sys.gestureup = false
persist.sys.gesturedown = false
persist.sys.gestureleft = false
persist.sys.gesturedouble = false
persist.sys.gestureright = false
persist.sys.gesturec = false
persist.sys.gesturev = false
persist.sys.gesturem = false
persist.sys.gesturee = false
persist.sys.gestureo = false
persist.sys.gesturew = false
persist.sys.gesturez = false
persist.sys.gestures = false
persist.sys.gestureonoff = false
Then they need to be deleted, since they can disable the menu in Recovery.

Post has been editedFOV5 - 16.12.18, 16:00



Rep: (215)
Optom @ 12/16/18, 14:22*
In the markup 28mb lost
miscalculated. not 28, but 12 is obtained, right?
FOV5 @ 16.12.18, 17:12*
You can of course try another program to pull it out
I started to watch - the rkandroidtool in the dump from any offset gives the contents of the parameter, repeated a number of times in a row ...



Rep: (220)
Optom @ 12/16/18, 18:06*
miscalculated. not 28, but 12 is obtained, right?
That's right, it turns out that 12 MB.
40 0000h - 3F 2000h - 8000h =6000h (size in sectors) , starting sector 3F 2000h + 8000h = 3F A000h
those. region starts from sector3F A000h by sector 3F FFFFh size in 6000h sectors.
p.s. To get the size in bytes, you need to multiply the results of the initial sector and the size in sectors by 512 bytes, since the data obtained is measured in sectors, and in one sector it is 512 bytes.

Post has been editedFOV5 - 17.12.18, 05:39



Rep: (215)
* FOV5, in the same place, the size in blocks of 512 bytes seems to be, not 1024; so 24mb divided by 2, isn't it?

Post has been editedOptom - 16.12.18, 16:31



Rep: (220)
Optom @ 12/16/18, 6:30 PM*
same size in blocks

that's right, I completely forgot what else you need to multiply by 512 ... because the size of Recovery 10000h * 512 and only then it turns out 32 MB ....

Post has been editedFOV5 - 16.12.18, 17:31



Rep: (3)
Good day. How is darvin 6 battery case? There was MK 2, it was charged twice a week.

Post has been editedAlex Peshin - 17.12.18, 13:26
Reason for editing: correction



Rep: (215)
* Alex Peshin, I cannot say anything definitively - I have not noticed. Subjective per day sleepno more than 1-2% nifiga does not go away. Let's try a semi-synthetic test on D5 - with minimal complexity for me as an experimenter =) If you are interested in a particular technique - offer

1. Reader is able out of the box. Charged to 100%. The backlight is off, wifi is off, auto power off - never. The reader under the cover in a dream is not used for its intended purpose - I wake up once a day by opening the cover (from 2 days I began to press the status bar and check the battery consumption schedule, because I was surprised that the indicator does not change - I will have to experiment for so long =)
results
Week 1: Day 0 - Day 7: 100% (-0)
Week 2: Day 8 - Day 14: 100% (-0)
Week 3: Day 15 - Day 21: 100% (-0)
Week 4: Day 22 - Day 28: 100% -80% (-20)
Day 22: 100% (-0)
Day 23: missed
Day 24: 93% (-7/2)
Day 25: 90% (-3)
Day 26: 87% (-3)
Day 27: 83% (-4)
Day 28: 80% (-3)
Week 5: Day 29 - Day 35: 80% -56% (-24)
Day 29: 76% (-4)
Day 30: 73% (-3)
Day 31: 70% (-3)
Day 32: 66% (-4)
Day 33: 63% (-3)
Day 34: 59% (-4)
Day 35: 56% (-3)
Week 6: Day 36 - Day 42: 56% -32% (-24)
Day 36: 52% (-4)
Day 37: 49% (-3)
Day 38: 45% (-4)
Day 39: 42% (-3)
Day 40: 38% (-4)
Day 41: 35% (-3)
Day 42: 32% (-3)
Week 7: Day 43 - Day 49: 32% -8% (-24)
Day 43: 28% (-4)
Day 44: 25% (-3)
Day 45: 22% (-3)
Day 46: 18% (-4)
Day 47: 15% (-3)
Day 48: 11% (-4) low charge warning
Day 49: 8% (-3)
Week 8: Day 50 - Day 56: 8% -5% (-3)
Day 50: 5% (-3)
Day 51: 5% (-0)
Day 52: 5% (-0)
Day 53: 5% (-0)
Day 54: 5% (-0)
Day 55: 5% (-0)
Day 56: 5% (-0)
Week 9:
Day 57: 5% (-0)
Day 58: 5% (-0)
Day 59: 5% (-0)
Day 60: 5% (-0)
Day 61: 0% (-5)

Seriously?! 0.o
himself in shock
The first week was a horizontal flow schedule.
In the second week, the android stopped understanding what was happening. Writes "battery consumption unknown"
In the third week it became annoying
Fourth week made a surprise

The fifth week is a steady decline of nominally about 3.5% per day. If, as surveyors write, this trend continues to zero, then we can expect a total duration of such a life of 1 second of wakefulness per day — about 50 days. And this coincidentally returns to my original estimate: for a day of sleep, the reader should actually eat no more than 2% of the charge (regardless of what the indicator shows)

Eighth week: unexpected. Apparently, the story is similar to the previous generation of Monte Cristo, who lived on the last 1% for almost longer than the other 99%. Although I hope that the situation is not quite the same and my experiment will end soon. Still, a month in sleep mode already have exactly
I will update this post along the way.

Questions on the firmware while paused. A discussion of the firmware I propose to transfer to a separate branch:ONYX BOOX C68 - Firmware [Android].
If there is a good moderator with a minute of free time - I will ask you once again to transfer the firmware questions to a new branch, or you will flood it (I first of all) with specific questions XD

Post has been editedOptom - 17.02.19, 12:39



Rep: (215)
Leave a link to the threadRockChip rk3188 and newer, kernel build and more.
maybe there will be some useful observations on the updated version of the chip

Added by:
Wiki on our chiphttp://rockchip.wikidot.com/rk3128
Datasheethttp://rockchip.fr/RK3128%20datasheet%20V0.6.pdf

And furtherCS918 [Android]
And furtherMK888 / K-R42 / CS918 / MK908 / T428 / Ugoos UG300 / IRU R9 - Firmware

Post has been editedOptom - 17.12.18, 23:01



Rep: (558)
* Optom, here's another link surfaced with the dumper MK888 / K-R42 / CS918 / MK908 / T428 / Ugoos UG300 / IRU R9 - Firmware (Post SergSanFran # 31615465)

Post has been editedcergor - 20.12.18, 14:22



Rep: (0)
* olegus642 , I did not solve the problem as such, but if you click the icon next to the clock and complete the processes / clear the memory, although it clears 30 mb each, it hangs less often + you can not close, but you can go to the main screen or open new books right from the application I doubt that this is an iron problem.



Rep: (0)
forsc123 firmware has been released. before this tech support sent me an update file. sense zero. Now I downloaded the firmware. threw in the root and the book writes no new updates. maybe they sent me the firmware but the version of the vermia did not change the hotch on their site. I don't understand anything ....



Rep: (558)
* olegus642, In a personal firmware file.



Rep: (558)
Damn, you need system.img, with current symlinks (http://onyx-boox.ru/support/boox_darwin6



Rep: (215)
* cergor, how upx disassembled?



Rep: (558)
Still, I will pick the other day options. Here found an interesting link, you will need to tryhttps: // reverseenginee ... mware-nrv-for-analysis



Rep: (0)
And where this update from off site on Darwin 6 to throw in the book, in which folder? Wherever I throw, I do not see the update.



Rep: (558)
* forsc123, according to all canons - it is necessary to place the update in the root of the internal flash drive (or cd card). And with the name update.zip.



Rep: (0)
I sort of threw it there .. I do not see it ... maybe I’m doing something wrong? maybe the file that sent tech support and this firmware is the same? The version number of the firmware in my book remains the same ... can you tell me something?



Rep: (558)
* olegus642, if the update of the version you have already installed, the system will not see the new version.



Rep: (220)
olegus642 @ 12.21.18, 08:33*
I sort of threw it there .. I do not see it ... maybe I’m doing something wrong?
If you have a complete firmware in the img format from Onyx, then it will not see it from the SD card, since it is not signed with a corresponding signature that characterizes your model. (Such firmware from the manufacturer is intended only for firmware from a PC). In order for the device to see the OTA update, they need to be placed in the root of the SD card namedupdate.zip , and if the signature with the device matches, then it should see it. If you throw it on the inside, then try throwing it on an external SD card (provided that if there is a corresponding opportunity for the book).

Your case is more complicated, since recently Onyx in the latest models on Android 4.4 and above (for example in the books BOOX Max 2) began to use some specific UPX format, that is not known at all what and how to open it, there are suspicions that They use some kind of encryption method, because of what the content looks like a mess of hexadecimal code. You can, as a variant of Update.zip, unpack and put the update.upx file contained in it into the root of the SD card, and then check the book’s reaction to this file. You can also try the manual update option, with a choice of the location of these files (such as such an option should be present).

Post has been editedFOV5 - 21.12.18, 12:01


Full version    

Help     rules

Now: 28.06.19, 10:13