> Attention!

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


168 pagesV  1 2 3 4 5 6 > »  
 
REPLY
> Onyx Boox C67ML - Firmware
FOV5
Message#1
23.06.15, 05:08
Veteran
********
[offline]

Group: Friendssavagemessiahzine.com
Messages 1328
Check in: 11.03.13

Reputation:-  219  +

Firmware series of booksC67ML, such as:Onyx Boox C67ML DARWIN, ONYX BOOX C67ML Magellan 3, ONYX BOOX C67ML Magellan 2
DescriptionandDiscussion Onyx Boox C67ML DARWIN
DescriptionandDiscussion Onyx Boox C67ML, Magellan 2 & Afteglow 2
DescriptionandDiscussion Onyx Boox C67ML Magellan 3

If the device does not have a full firmware, but only the update.zip file, then first make a dump from the device and save it somewhere.
To create a full firmware, most likely you will have to contact experienced users on the forum with a dump.
And if you do not make it, then you have to do a paid repair.

Drivers
Drivers are needed for firmware from a computer, as well as for access to the reader byadb.
Current driver installation wizard:Attached fileDriverAssitant_v4.5.zip(9.35 MB)
Brief instruction:
1. Unzip, run DriverInstall.exe
2. If before that there were other drivers (old or from another RockChip device) - remove them by clicking the Uninstall Driver button
3. Install the driver with the Install Driver button
4. For Windows XP, after installing the driver using the wizard, connect a reader - a new device will be found, perform an automatic search and installation to complete the installation of the drivers
5. Check that the drivers are installed:
1. Standard UMS Connection - USB Mass Storage (for transferring files)
= usually no additional drivers are required
- USB Device Controllers \ USB storage device, as well as Disk devices \ rochchip _usb USB Device are reflected in the device manager
- when the USB-drive mode is activated on the reader in My Computer, the external BOOX USB-drive appears
- in FactoryTool device type - MSC
- in RKBatchTool the rectangle "Connected Devices" should be pink
- in RKAndroidTool "Found RKAndroid Mass Storage Usb"

2. Connection in Bootloader mode (for flashing images):
= login instructionsin the FAQand below
- in FactoryTool device type - Loader
- in the RKBatchTool rectangle "Connected Devices" will turn green
- in RKAndroidTool "Found RKAndroid Loader Rock Usb"

3. Connection in ADB mode - Android Debug Bridge (for using the ADB utility and applications using it)
= activate the Application \ "USB Debugging" option on the reader
- in the device manager, an additional Android Device \ Android Composite ADB Interface appears
- in adb reader is reflected when displaying a list of devices
Original firmware
Information about products and updates in PDF on January 5, 2018
Official updates as of2018/12/21
C67ML series (Pearl HD screen)C67ML Carta SeriesC67ML Carta2 SeriesC67ML Carta + (plus) SeriesC67ML Carta2 + (plus) Series
A selection of firmware for full recovery
Remarks andimportant warnings
1. Firmware update should be chosen exactly for the model indicated on the back of the reader and the identifier that is reflected in the settings: menu-settings-about device-model (or about device-system update-model number). There is only one exception so far: Darwin 1 and Magellan 3 have the same identifier.
2. Important!Firmware 1.7.5 / 1.7.4-mc and higher are suitable for readers with a 3000 mAh battery.
3. Important!Before updating the firmware from version to 1.8.0 inclusive to version 1.8.1 and higher, readers with the old markup (purchased until the fall of 2016) are required to first install the full firmware from the computer with the new partition markup. After this update, you can install it as usual.A little more detail and instructions
4. To roll back to the previous version of the firmware, it is enough to install the update.zip update of the corresponding version - request technical support or search here on the forum (sometimes the previous version is available on the official update page)
5. If after the update minor bugs appear that are not described in the subject, it is recommended to reset personal data (settings). If there are no glitches, it is not necessary to do a reset.
Instruction
1. Download the update.zip update file to your computer.
2. Charge the device battery to at least 50%.
3. Copy the update.zip file, without unpacking the archive, to the device in the root directory of the internal memory via a USB cable. Then unplug the cable.
4. Connect a mains charger.
5. Go to Settings>About the device>System updates>Check for updates in memory.
6. There will be a question about confirming the desire to update the system. Click "Update."
7. The firmware will start. Lasts about 5 minutes.
8. If the system menu appears in the process, select Reboot now with the paging buttons and confirm the selection by pressing the Power button.
9. Wait for the user interface to load.
10. Delete the firmware installation file after the reader is loaded.
11. After carrying out the firmware procedure for Google Play to work correctly, it is recommended to reset your personal data.
Emergency install updates
If the reader does not boot in normal mode, you can try to install the update from recovery mode. Enter recovery: turn off the reader (you can press the reset clip next to the power button), hold down the central Back button, turn on the reader, hold Back until Recovery appears. There was a boot-animation - then the Back button was accidentally released earlier.
1. You can flash update.zip from an external sd card - the item apply update from external storage
2. You can flash (re) the last update launched from the shell — if it is saved in the cache — select Apply update from cache
3. You can transfer the reader to ADB Sideload mode (what is it?) and upload update.zip from a computer using the command line utility ADB

Fresh firmware for ONYX BOOX books produced in Russia

Modified firmware
Installation is generally similar to the original firmware.
In most cases, the instruction manual is attached to the firmware and it is indicated with which program to upload the firmware.

Firmware fromCergor :

Firmware fromTigdin :
Changed sched_child_runs_first setting to defeat the touchscreen glitch, added support for scripts

Important! Instructions - be sure to read!
Important! Before upgrading the firmware to version 1.8.1 and higher, check the total amount of internal memory available to the user, including the space occupied by user files: "settings - work with memory is available" or connect the reader to the computer as an external drive. If the volume is more than 5.07GB, it will be necessary to remap memory before updating. Read more
Before any actions (changing the firmware and system applications, root, etc.) it is better to backup the firmware usingrkDumper. Instructions in different variations:(0), (1), (2), (3).
Do not experiment with the firmware, if you still do not know how to roll back the changes or restore the reader.
For new modelsCarta2 +, Сarta +, Darwin 3, Darwin 4, Vasco da Gama 2 while there are no full-fledged official firmware for recovery.
In most cases, the selection of firmware comes with instructions and indicates with which program to upload the firmware.

How to open the device riviz without opening the case
General notes and warnings
1. Full firmware are designed to restore the device to work after software failures, when installing the update.zip update does not help or is impossible
2. Important!The instructions assume that when installing the full firmware, user data is lost - make a backup copy!
3. The firmware procedure is somewhat more complicated than an ordinary update, and ordinary users can be advised to contact the service center. At the same time, everything can be done on its own, and it is very, very difficult to "turn" the reader on this platform. But in any case, everything that you do - you do at your own peril and risk.
4. Full firmware suitable for devices of the same generation and with the same screens and interchangeable within the series:
  • C67ML series (Pearl HD screen): C67ML, Magellan 2
  • C67ML Carta Series: Carta, Darwin, Magellan 3, Vasco da Gama, Dontsova Book
  • C67ML Carta2 Series: Carta2, Darwin 2
  • C67ML Carta + (plus) Series: Carta + (plus), Darwin 3, Vasco da Gama 2
  • C67ML Carta2 + (plus) Series: Carta2 + (plus), Darwin 4
5. The model is listed on the back of the reader, the identifier of the installed firmware is displayed in the settings: settings menu-about device-model (or about device-system update-model number).
6. Important!Firmware 1.7.5 / 1.7.4-mc and higher are suitable for readers with a 3000 mAh battery.
7. If, as a result of installing the full firmware, the identifier changed: for example, you switched from the Carta + firmware to Darwin 3 - then you need to install the updates in the future, focusing on the new firmware identifier.
8. To roll back to a previous firmware version, it is enough to install the update.zip update of the corresponding version - request technical support or search here on the forum (sometimes the previous version is available on the official update page)
Enter the bootloader mode for flashing the system image
Pre-charge the reader and perform any convenient sequence of actions:
  • connect the reader to the PC, press and hold the central Back button, briefly press reset (the button under the paper clip next to the power button), hold Back a little more until a beep sounds when the device is connected to the PC
  • turn off the reader (if you hang up and other problems, you can turn off by briefly pressing the reset button next to the power button), hold the central Back button, connect the reader to the PC, hold Back a little more before the audio signal about connecting the device to the PC
  • connect the reader to the PC, run RKBatchTool, click the Switch button, one of the rectangles in the program will change its color from pink to green
  • connect the reader to the PC, run the utilityrkDumperwith swt key
Reader without battery:
  • open RKBatchTool on PC, connect the reader with the central Back button pressed, the rectangle in rkBatchTool will turn green
  • if the rectangle becomes green, and then gray again, you need to catch that moment of defining the reader in bootloader mode before it falls off. You can click the reset clip and notice the device’s ready time. You may have to start the firmware process with the reset button pressed and then release it, because the device may be “lost” even before the program goes to the firmware

Firmware firmware is an up-to-date method
1. Preparation
1.1. Download the full firmware for your model from the forum or request technical support:
support@onyx-boox.ru for books MakTsentr (travelers) and sales@onyx-international.com for books from the manufacturer.
1.2. Download and install drivers DriverAssitant - is in the selection (download from the forum), installation is simple through DriverInstall.exe
1.3. Download the firmware utility:Attached fileFactoryTool-v1.42e-MC.zip(13.8 MB)
MakTsentr technical support still recommends using rkBatchTool to switch the reader to the firmware mode, but it is possible without this program.
1.4. Charge the reader at least 50% or better
2. Flash Full Firmware
2.1 Open Factory Tool
In some sets, there may be hieroglyphs in the name of the program directory - it is better to remove them before running.
For convenience, go to the English language in the program interface: the Earth icon in the top button bar is the second item. Next we work with the top row of buttons.
Attached Image
2.1.1 Firmware - select the firmware file * .img
If downloaded as a zip archive, you need to unpack it first. It takes some time to load the program; after the operation, the path to the firmware file will appear in the Firmware line
Run button for now skip
2.1.2 Select mode: Upgrade or Restore
According to the official instructions, select Restore.
2.1.3 Demo button - select the OemImage.img file from the Factory Tool folder
2.1.4. Tick ​​the Demo below to the left of the path to the OemImage.img file
In this image, custom content: dictionaries, pre-installed books, etc. If it is not included with the Factory Tool, simply skip this item.
2.2 Turn off the reader
If the reader does not load, you can click the reset clip next to the power button
2.3 Clamp the central BACK button on the reader, connect the reader to the computer, without releasing the BACK
Windows will detect the device, pick up the previously installed drivers, Port [x] - Loader will appear in the usb device list in the Factory Tool, you can release the BACK button
2.4 in the Factory Tool, select the usb port with a defined reader
In most versions of the instructions of this item is not. Apparently, applicable to situations when several readers are connected at once (?)
2.5 Click Run in the top row of buttons.
2.6 We control the firmware process on the line of the selected port. After successful firmware, the corresponding entry will appear in the window to the right of the list, and the green number of successful firmware in the lower right corner of the program will increase by one. Reader will reboot
2.7 After rebooting the reader in the Factory Tool, click Stop, close the program
3. Update to the latest firmware version with a regular update.zip update.
Depending on the settings in the firmware itself, light side effects are possible when loading the reader after uploading the full firmware image:
- in the list of applications there may be test utilities with names in Chinese - hieroglyphs; the message "Please check the pre-intalled books, dictionary and tts" will be displayed. To hide the test applications and pop-up message, select the "Delete test applications" item in the "Applications" window menu. Read more -Firmware (Post eire # 42541059)
- the reader can boot without the initial settings and in Chinese. Briefly in pictures, how to switch to another language:Onyx Boox C67ML - Firmware (Post Optom # 62804808)
Firmware with rkBatchTool - the method was mainly used for firmware up to 1.8.0
1. Download the system image file * .img and rkBatchTool (the utility folder can be named BatchTool_For_eink)
2. Charge the device.
3. (Optional) Remove the memory card (if installed)
4. (Optional) Uncheck "USB debugging" if it is installed. To do this, go to Settings>Applications>Application settings>Development
5. Connect the device to the PC.
6. Ensure that the PC has identified a new device.
7. Run RKBatchTool (depending on system settings, you may need to run as administrator)
7.1. If the Chinese kit is used:
>If there is an error at startup, remove the hieroglyphs from the program path.
>To switch the language from Chinese to English in the program interface - the leftmost button in the bottom row, and select another item in the list.
8. Click on the "..." button at the end of the FW Path field. Select the firmware file * .img (operating system image). The "Connected Devices" rectangle should be pink.
9. Click the Switch button. The device will go into Bootloader mode. Switch Done Success appears in the program window.<1>. The "Connected Devices" rectangle will turn green. If this does not happen, in the device manager, select the new device that appears and specify the path for the drivers. The drivers are located in the folder Driver or RockUsb (download separately). Also, the path to the driver must be specified if you have previously flashed any other device using RKBatchTool.
10. Click on the Upgrade button. The update will begin.
11. Wait until the firmware is complete,
>The main signal is a green line in the program window with information on successful firmware.
Then the device will boot up in the working mode, and there will be a question about activating the USB-drive mode.
>The first "regular" download can last much longer than usual. When it seemed to me that it would never end, disconnected the usb from the reader (this could have been done before, but not before the appearance of the message about the completion of the firmware in the program window !!!) - and the reader booted up at the same second. According to some reviews, if the download lasts a very long time, you can try to press (briefly) the back button or on (in the second case, the book will show the sleep screensaver - and press the button again - the book will load)
12. Firmware finished.
Depending on the settings in the firmware itself, light side effects are possible when loading the reader after uploading the full firmware image:
- in the list of applications there may be test utilities with names in Chinese - hieroglyphs; the message "Please check the pre-intalled books, dictionary and tts" will be displayed. To hide the test applications and pop-up message, select the "Delete test applications" item in the "Applications" window menu. Read more -Firmware (Post eire # 42541059)
- the reader can boot without the initial settings and in Chinese. Briefly in pictures, how to switch to another language:Onyx Boox C67ML - Firmware (Post Optom # 62804808)

Firmware with rkAndroidTool - used to restore Orav sections from dump
Instructions in the topic rkDumper -[TOOL] rkDumper (Post _Danila_Master_ # 38778836)
You can add, perhaps, just a couple of comments:
- when connecting to a PC, it is better to use a USB 2.0 cord, since with USB 3.0 RKAndroidTool may not see the book
- format the button Erase IDB is not necessary.
How to adjust the backlight brightness
1. Regulated through the status of the line, you need to tap on the clock and everything will become clear.
2. You can call the adjustment menu in the stock reader Oreader and NeoReader, tapping in the reader in the center of the screen, a menu will appear, you need to select the characteristic Lightbulb icon with the signatureMoon light
3. In NeoReader, Oreader, AlReader, you can adjust the backlight by swiping your finger along the right edge of the screen.
How to take a dump from your book!
To remove the dump with the rkDump utility, Root and Debug Mode are not needed, I will lay out the utility with a shortcut in which the necessary parameters for launching are already specified.

Need to:
1. Download utility:Attached filerkDumper.7z(9.88 MB)
2. Unzip the file to the root of drive C or D
3. Run RkBatchTool
4. Using the Readme (rus) .txt instruction or the Instructions in docx format, connect the book to the PC via USB cable.
5. Transfer the book to the PC flashing mode via USB using the above instructions for flashing the book - i.e. boot into Boot Loader mode
(p.s. note, in this mode, you can also switch through Total Commander with an ADB module and installed ADB drivers for the system)
6. When the indicator in the RkBatchTool application turns green, we will no longer need RkBatchTool and can close it.
7. Start the application with a shortcut named rkDumper with a drive letter in the name to which the archive was unpacked - the dump will start from the book.
8. Upon completion of the dump, the book will reboot itself and boot up in normal mode.
9. The Output folder will appear in the rkDumper folder, you will need to pack it and put it in the cloud, providing a link for downloading.

I need to upload all the files, the userdata.img file is optional, I probably don’t need it to create the firmware.

p.s. If you decide to unpack the file to another disk, then in the properties of the shortcut, specify the drive letter where the file was unpacked.
Have a nice dump! ;)
Solving the problem of paging pages in FBReader from the store.
In the firmware, starting with versions 170, there is a button with two arrows in the status line [<>], which switches the mode of the paging buttons to the volume adjustment mode [+ -]. In the original firmware from MakTsentr, this feature was disabled, but in my mode, I returned this feature to the status line, as there are a lot of readers who scroll through Vol + and Vol - by changing the ro.onyx.no_pg_vol_swith = parameter in the Build.prop file from value 1 to value 0.

Another way to solve the problem
Useful tips for familiarization and self-education
Additional links in the topic
Surveys
The results of the survey on readers
Attached Image
Survey results for book format preferences
Attached Image
If the user has a weak Internet, it makes sense to useDownload Master .

Post has been editedFOV5 - 27.01.19, 16:16
Reason for editing: Added full firmware to Darwin 4 v1.8.2-mc 2017-11-29_12-28 387f096, created from the provided dump
Feonik
Message#2
11.07.15, 15:02
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

Shadow @ 06/22/2015, 9:35 PM*
When flashing on a device from McCenter, it can lead to cyclic loading of the device.
Out of this state, only having the full version of the firmware to your device for its firmware from a PC.


I have just recently bought Darwin from MakTsentr.
And who knows where to get this full version of the firmware to your device for its firmware from a PC?
And did anyone try to flash this firmware? Does it cycle the device?
Feonik
Message#3
11.07.15, 15:53
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

FOV5 @ 07.07.2015, 14:34*
full dump of your device


Can you tell at least about what to do?
Feonik
Message#4
11.07.15, 21:37
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

FOV5 @ 07.07.2015, 16:12*
If the device does not have Root, then you need to install it.


Looking for a way to make root found a themeRK3026 E-Readers Kitchenwith your participation. They downloaded rk_tool21_how_to.zip in the first message, in which, in turn, a very useful instruction (in the instructions_readme_first.txt file) appeared on how to make a full backup without root. As a result, I received the same files that you indicated to do.

To boot into the bootloader mode gave the command (from the same topic)
adb reboot-bootloader

Adb took from the Android SDK, which without any problems identified the device.

Drivers from the mentioned topic, I put it from the file RK3026Rockusb_v3.6.zip, but later I found the "Rockusb Driver 3.7.zip" there, but I did not use it. I installed the driver after switching to bootloader mode.

In the same archive rk_tool21_how_to.zip there is a utility
./Flasher_tool/ROM_Flash_Tool_137.exe
but she does not see my reader in any mode (normal, bootloader, recovery). In this connection, the question arose how to upload the received files from the PC back to the reader.

For reference: to go to recovery mode:
Turn off the device completely.
Press the lower center button (under the BOOX inscription).
Holding the lower central button, turn on the device by long pressing the power button.
The menu navigation keys are paging buttons, the selection button is the power button.

P.S. A little later I'll upload the received files.

Posted on 07/11/2015 21:37:

FOV5 @ 07.07.2015, 16:12*
Downloadable [attachment = "6522560: BackupRK.zip"]


I understand that someone else could come in handy, so please correct - in your message there is no working link to the specified file.
Feonik
Message#5
11.07.15, 21:52
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

The backup files from my reader are attached to the message.

In the archive, among other things:
Parameter.img - the original file obtained through ROM_Dumper_Tool.exe, start 0, count 2
Parameter.txt - slightly edited with the calculated size of user.img

Attached files

Attached fileOutput.part01.rar(100 MB)
Attached fileOutput.part02.rar(100 MB)
Attached fileOutput.part03.rar(19.49 MB)


Post has been editedFeonik - 11.07.15, 22:22
Feonik
Message#6
11.07.15, 22:18
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

FOV5 @ 07.07.2015, 16:12*
from this data you can make a full version of the firmware


If it does not complicate, then please describe the process how to do it yourself.

I would also be very grateful for the information on how to reassign the hardware buttons to the necessary actions in the files of the firmware itself.
Feonik
Message#7
11.07.15, 22:25
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

Feonik @ 07/11/2015, 20:37*
In the same archive rk_tool21_how_to.zip there is a utility
./Flasher_tool/ROM_Flash_Tool_137.exe
but she does not see my reader in any mode (normal, bootloader, recovery). In this connection, the question arose how to upload the received files from the PC back to the reader.


Turned out to be inattentive. In the same topic in the first post paragraph
B) How to install IMG files OR (Restore your device's data)

Post has been editedFeonik - 11.07.15, 22:26
Feonik
Message#8
11.07.15, 22:34
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

Feonik @ 07/11/2015, 21:18*
If it does not complicate, then please describe the process how to do it yourself.


I think I'm on the right track, correct, if you made a mistake. Found the file in the same topic
RKwinTools_v134.rar
with everything you need and instructions in Russian. With his help, you can, as I understand it, sew root.

I'm studying now.
Feonik
Message#9
11.07.15, 22:57
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

I would be grateful for any information on how to change the sections of the device's internal NAND memory. In particular, to increase the available space for applications.
Feonik
Message#10
12.07.15, 00:33
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

Using RKwinTools_v134, I repacked system.img, adding the su file from its bundle, and SuperSU.apk took a new one from this forum and renamed it to that name, replacing the one in RKwinTools_v134.

To repack, you need to know the file system.img. In this device, it is ext3, found out in a Linux virtual machine using the command
file system.img

After building a new image, system.img filled with rk_tool21_how_to \ ROM_Dumper_Tool.exe

After downloading and running SuperSU, he suggested updating the binary file (su), which I agreed with. I chose the "normal" mode, without TWRP, everything went well.

Post has been editedFeonik - 12.07.15, 00:37
Reason for editing:
Feonik
Message#11
12.07.15, 01:41
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

To upload new firmware from the above files in this thread
BOOX + C67ML + Carta + V1.7.2_rc1.part1.rar
BOOX + C67ML + Carta + V1.7.2_rc1.part2.rar

I had to replace the contents of such files in the unpacked recovery.img and system.img files:
Unpack / System / build.prop
Unpack / Recovery / ramdisk / default.prop

Replaced all occurrences
MC_C67ML_Carta
on
C67ML_Carta

I did not change only in lines (I cite only the beginning of lines):
ro.build.description =
and
ro.build.fingerprint =

After that, he collected new images and uploaded through ROM_Dumper_Tool.exe.

The firmware file update.zip from the rar-archive was placed on the sd-card inserted into the device.
I turned it off, turned it on in recovery mode (when the BOOX button is pressed, a long press on the power button).
Next, using the paging buttons and the power button, I chose
applay update from external storage
and further chose the file
update.zip
after which the firmware was installed.

Further in the main menu I chose
reboot system now
and the device has been reset.

After downloading, you had to re-select the language, time zone, etc.

The device works fine without cyclic reboot. All pictures with Darwin are gone, now relatives from Onix.

I could not find how to redefine the settings of the buttons, as it was in my native firmware.

By long pressing the shutdown button, there used to be the Restart item, except for Shutdown and Cancel, now it is gone.

I replaced all the pictures (in the off and in standby mode) with my own through the File Manager, a long press on the picture file - Set as screen saver. After that, I rebooted the device. One "but" - you can replace 1-3 pictures in the standby mode, but it seems that there is also a 0th one, which is shown on the first transition after rebooting into the standby mode. After she does not show, but also to change how, did not understand.

All books from the native firmware remained in place.

Post has been editedFeonik - 12.07.15, 02:16
Feonik
Message#12
12.07.15, 02:18
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

I really hope to find a solution to redefine the hardware buttons in the system files by changing the key codes, etc.
Feonik
Message#13
12.07.15, 02:25
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

Feonik @ 07/11/2015, 21:57*
To repack, you need to know the file system.img. In this device, it is ext3, found out in a Linux virtual machine using the command
file system.img


Sorry, there is no possibility to edit already.

Judging by the file
Unpack / Recovery / ramdisk / etc / recovery.fstab
there is still ext4 file system.
Feonik
Message#14
12.07.15, 13:23
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

FOV5 @ 07.12.2015, 02:17*
Choosing Ext4 - system.img just won’t figure it out

That's the thing that understands. Disassembled as ext2 / 3 and as ext4, compared pofaylovo - all one on one.

Actually, what are we saying? Just got to give the mount command in adb shell:
rootfs / rootfs ro, relatime 0 0
tmpfs / dev tmpfs rw, nosuid, relatime, mode = 755 0 0
devpts / dev / pts devpts rw, relatime, mode = 600 0 0
proc / proc proc rw, relatime 0 0
sysfs / sys sysfs rw, relatime 0 0
none / acct cgroup rw, relatime, cpuacct 0 0
tmpfs / mnt / secure tmpfs rw, relatime, mode = 700 0 0
tmpfs / mnt / asec tmpfs rw, relatime, mode = 755, gid = 1000 0 0
tmpfs / mnt / obb tmpfs rw, relatime, mode = 755, gid = 1000 0 0
none / dev / cpuctl cgroup rw, relatime, cpu 0 0
/ dev / block / mtdblock8 / system ext4 ro, noatime, nodiratime, barrier = 1, data = ordered, discard 0 0
/ dev / block / mtdblock6 / data ext4 rw, nosuid, nodev, noatime, nodiratime, barrier = 1, data = ordered, discard 0 0
/ dev / block / mtdblock5 / cache ext4 rw, nosuid, nodev, noatime, nodiratime, barrier = 1, data = ordered, discard 0 0
/ sys / kernel / debug / sys / kernel / debug debugfs rw, relatime 0 0
/ dev / block / vold / 31: 9 / mnt / sdcard vfat rw, dirsync, nosuid, nodev, noexec, relatime, uid = 1000, gid = 1015, fmask = 0002, dmask = 0002, allow_utime = 0020, codepage = cp437 , iocharset = iso8859-1, shortname = mixed, utf8, errors = remount-ro 0 0
/ dev / block / vold / 31: 9 / mnt / secure / asec vfat rw, dirsync, nosuid, nodev, noexec, relatime, uid = 1000, gid = 1015, fmask = 0002, dmask = 0002, allow_utime = 0020, codepage = cp437, iocharset = iso8859-1, shortname = mixed, utf8, errors = remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro, relatime, size = 0k, mode = 000 0 0

That is ext4.

FOV5 @ 07.12.2015, 02:17*
Before upgrading to version 1.7.2, did you modify System.img and Recovery.img from your book, which you got by merging partitions on a PC?
In fact, you could simply edit the build.prop file in the System folder, but Recovery, of course, had to be pulled out of the device and modified. It can be seen in a cyclic reboot without its modification.

Yes, I just took the images of these sections, modified them and poured them back. Because of my carelessness, I initially uploaded an unmodified system, then began to search through all the unpacked files from all images, found it in recovery. It so happened that replaced everywhere. In the end, everything works.

FOV5 @ 07.12.2015, 02:17*
Can you lay out sections of your book after updating to version 1.7.2?

Yes, only a little later, again I returned everything to my native state and reset the settings in order to save a clean system for the backup.

FOV5 @ 07.12.2015, 02:17*
Interestingly, for example, in the Recovery mode we don’t see the menu

Now, and I'm curious, who has this "we"? )

FOV5 @ 07.12.2015, 02:17*
If it doesn't complicate, I would like to see in the photo how your menu looks in Recovery.

Yes, it's over, but again, a little later.

FOV5 @ 07.12.2015, 02:17*
Backup.img is an interesting file that is essentially similar to update.img possible without the system.img section included in it. I'll try to disassemble it.
I disassembled - in fact it turned out to be a piece of the update.img file, because when parsing I shut up on pulling out the system.img - which, due to cropping the file, it is damaged and the process just hung.

It is strange that it is damaged. I pulled out the data from the parameter, now I’ve re-pulled everything after the reset - this file is one to one in comparison.

FOV5 @ 07.12.2015, 02:17*
Keep the full firmware version

I thank for the help, I will look.

Post has been editedFeonik - 12.07.15, 13:24
Feonik
Message#15
12.07.15, 13:42
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

FOV5 @ 07.12.2015, 12:34*
Inattentively doing, you see in your native section repacked from ext2 / 3 to ext4.

No, not really. I pulled the system.img through ROM_Dumper_Tool.exe and immediately saved a copy of it and did not use it anywhere else. Now checked again - unpacked by both teams.

FOV5 @ 07.12.2015, 02:17*
Backup.img ... Disassembled

Can you tell me what you have done with it?

FOV5 @ 07.12.2015, 12:34*
And you look at the topic of Gmini A6LHD for a start, then you will understand - where it is with us ...

Yes, I looked in, it was just curious to clarify, thank you.

Feonik @ 07/12/2015, 12:41*
unpacked by both teams

Or still, the file utility from Linux turned out to be right, and here it is simply mounted as ext4.

Post has been editedFeonik - 12.07.15, 13:43
Feonik
Message#16
12.07.15, 13:56
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

Feonik @ 07/12/2015, 12:42*
Can you tell me what you have done with it?


FoundimgRePackerRKand they took it apart. Now I understand the disassembled.
Feonik
Message#17
12.07.15, 14:42
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

FOV5 @ 07.12.2015, 12:56*
The process itself, as I did, clearly did not use the RKwinTools_v134 utility.

Used from your ownmessagesin the forum I mentioned earlier. Executed command 5, moved the received contents of System to another folder, then executed command 6. Then compared - one to one. Now I have checked the contents of the command files from RKwinTools_v134 - different commands are executed, but the result is the same.

FOV5 @ 07.12.2015, 12:56*
I had to resort to heavy artillery AndImgTool

I tried it - loops in the file
rockdev / Image / system.img
trying to pull it out, as I understand it. In the Task Manager there are counters of read / write operations, but the number of bytes read / written does not change. When those counters reached nearly 1,000,000,000, it stopped. As a result, the system.img file was in the amount of 38178816.

Then I compared the results with imgRePackerRK_104 - AndImgTool turned out to be more correct, since for the kernel.img and boot.img files there were correct signatures at the beginning of the files, KRNL, and there were no signatures from imgRePackerRK_104.
Feonik
Message#18
12.07.15, 14:47
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

FOV5 @ 07.12.2015, 12:56*
Can you describe the process of pulling out sections for owners of books C67ML Magellan 2?

So I have Darwin. Although, as I understand, they are similar. And so I have already said that in the archive with that utility there is a file "instructions_readme_first.txt" with quite detailed instructions. And in quite understandable English)

Although yes, it will be possible. But for C67ML Magellan 2 there will be other values ​​from the parameter, since there the internal memory size is 4 GB, not 8, as in Darwin.
Feonik
Message#19
12.07.15, 14:55
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

Feonik @ 07.12.2015, 13:47*
AndImgTool turned out to be more correct, since for the kernel.img and boot.img files there were correct signatures in the beginning of the files, KRNL, and there were no definite signatures from imgRePackerRK_104 at all.

I compared it more carefully - the only difference is in the presence of this signature at the beginning of the file (byte 8) and of a tail of a byte in 4. The rest is the same, as I see.
FOV5
Message#20
12.07.15, 14:56
Veteran
********
[offline]

Group: Friendssavagemessiahzine.com
Messages 1328
Check in: 11.03.13

Reputation:-  219  +

Feonik @ 07/12/2015, 16:47*
But for C67ML Magellan 2 there will be other values ​​from parameter
These values ​​have been known for a long time and most likely they coincide with the Chinese / European version, and it will not be difficult to get it out of Backup.img.

Feonik @ 07/12/2015, 16:42*
Used from your own message
Strangely, I also tried it, I really figured it out, but it will not always be like that, system.img will come across with experience, and they will get rid of it.

Post has been editedFOV5 - 12.07.15, 15:16


--------------------
Books: Pocket Book 902 Pro, Gmini A6LHD 2014 release
Phones: Nokia N97, DNS S4502
Tablet: DNS AirTab P83
Feonik
Message#21
12.07.15, 16:32
User
****
[offline]

Group: Friendssavagemessiahzine.com
Messages 98
Check in: 04.11.11
ONYX BOOX C67ML DARWIN

Reputation:-  11  +

FOV5 @ 07.12.2015, 13:56*
Strange, also tried, really figured out

Here is some answer to this weirdness:
Ext4Extractor version 1.5.2 Created by And_PDA Based on sources ext4_unpacker
Extractor for images in EXT2 \ EXT3 \ EXT4 \ SPARSE formats

That is, this utility doesn’t care exactly what file system format it is given to.

168 pagesV  1 2 3 4 5 6 > » 


 mobile version    Now: 05/01/19 10:14