Bootloop Fix for C67 series and Firmware 1.8.1

[patsos345]

I have a new Carta2 Plus with flickering problem after boot. Does anyone found a solution for this yet? Or is there anyone with the same model who has taken a full img backup and willing to share?

I already searched the forum for a solution, tried factory tools (for Carta2 1.8.1), still no joy. I contacted onyx for factory tools for Carta2 Plus and waiting. I get back when I have more updates. Thank you in advance.

[patsos345]

Ok after managed to get adb cli while C67ML running,

cat /proc/kmsg

shows flood of the same repeated messages, over and over again:

bat->full_times=11 bat->bat_capacity=100 bat->bat_status=4
<4>[  171.624630] ______magic schedule suspend state:0
<4>[  171.824453] ______magic schedule suspend state:0
<4>[  172.024254] ______magic schedule suspend state:0
<6>[  172.048082] qtaguid: ctrl_counterset(s 0 10033): insufficient priv from pid=398 tgid=354 uid=1000
<4>[  172.224061] ______magic schedule suspend state:0
<4>[  172.423865] ______magic schedule suspend state:0
<4>[  172.437347]
<4>[  172.437352]
<4>[  172.437356] bat->full_times=11 bat->bat_capacity=100 bat->bat_status=4
<4>[  172.623668] ______magic schedule suspend state:0
<4>[  172.823473] ______magic schedule suspend state:0
<4>[  173.023287] ______magic schedule suspend state:0
<4>[  173.223100] ______magic schedule suspend state:0
<4>[  173.422922] ______magic schedule suspend state:0
<4>[  173.437328]
<4>[  173.437333]
<4>[  173.437337] bat->full_times=11 bat->bat_capacity=100 bat->bat_status=4
<4>[  173.622741] ______magic schedule suspend state:0
<4>[  173.822550] ______magic schedule suspend state:0
<4>[  174.022357] ______magic schedule suspend state:0
<4>[  174.222166] ______magic schedule suspend state:0
<4>[  174.421980] ______magic schedule suspend state:0
<4>[  174.437344]
<4>[  174.437350]
<4>[  174.437354] bat->full_times=11 bat->bat_capacity=100 bat->bat_status=4
<4>[  174.621798] ______magic schedule suspend state:0
<6>[  174.705250] request_suspend_state: (on -> mem) at (2017-06-05 11:04:09.522315516 UTC)
<6>[  174.705355] rk29_backlight_pwm_suspend
<6>[  174.720259] request_suspend_state: (mem -> on) at (2017-06-05 11:04:09.537327145 UTC)
<4>[  174.821616] ______magic schedule suspend state:0
<6>[  174.837370] rk29_backlight_pwm_resume
<4>[  175.021452] ______magic schedule suspend state:0
<4>[  175.221290] ______magic schedule suspend state:0
<4>[  175.421130] ______magic schedule suspend state:0

If someone gets anything out of it, I will be glad to hear it.

[patsos345]

Well it seems that the messages above are generated from corrupted kernel partition. I managed to restore the right system, boot and recovery images from update.zip but the flickering remains. My only missing piece is kernel.img from C67ML Carta2 Plus...

[patsos345]

Finally I managed to restore my device to normal condition with the following full image:
https://pan.baidu.com/s/1kUSzNnT
For anyone having the same problems. Thanks everyone!

[Autarc]

Originally Posted by patsos345

Finally I managed to restore my device to normal condition with the following full image:
https://pan.baidu.com/s/1kUSzNnT
For anyone having the same problems. Thanks everyone!

Finally a solution which works! After flashing the image it runs again with 1.8.1 and also has the Playstore. Couldn't use the OTA update but entering recovery mode and installing the latest firmware from the website works fine. Already tried to contact Onyx itself but as they are quite busy couldn't help yet. Really happy to read again - thanks for the effort of you & everybody who assisted

[patsos345]

Glad to hear that my solution helped you out! I just wanted to ask you.. Do you experience unresponsive screen or buttons at random with your device? Is your screen not refreshing at the time? It happens on mine and I suspect hardware problem.

[patsos345]

Originally Posted by Autarc

Finally a solution which works! After flashing the image it runs again with 1.8.1 and also has the Playstore. Couldn't use the OTA update but entering recovery mode and installing the latest firmware from the website works fine. Already tried to contact Onyx itself but as they are quite busy couldn't help yet. Really happy to read again - thanks for the effort of you & everybody who assisted

Glad to hear that my solution helped you out! I just wanted to ask you.. Do you experience unresponsive screen or buttons at random with your device? Is your screen not refreshing at the time? It happens on mine and I suspect hardware problem.

[Autarc]

Originally Posted by patsos345

Glad to hear that my solution helped you out! I just wanted to ask you.. Do you experience unresponsive screen or buttons at random with your device? Is your screen not refreshing at the time? It happens on mine and I suspect hardware problem.

Not really, so far everything works quite well. Did you update to 1.8.2 too? Had to load the update manually but perhaps that helps.

[Mage3]

I'd really appreciate it if anyone could also share the full firmware package for Carta+

[patsos345]

The problem of freezing screen was caused by not updated boot.img. For some ugly reason, after firmware flash of factory tools + update.zip, my boot partition did not get updated. What I did was:

- Got su access to C67ML Carta2+ (flashed twrp recovery, mounted /system rw via adb, copied su binary to /system/xbin).
- Took backup of boot partition and flashed boot.img from latest update.zip. Got adb shell and run the following:

# dd if=/dev/block/mtd/by-name/boot of=/sdcard/boot_orig.img bs=4096
# dd if=/dev/zero of=/dev/block/mtd/by-name/boot bs=4096
# dd if=/sdcard/boot.img of=/dev/block/mtd/by-name/boot bs=4096

- Run manually the update recovery script (which also updates boot properly). If you don't do the above dd commands, script will fail.

# /system/etc/install-recovery.sh

Rebooted the device...
Now I have full working ebook reader....

[Mage3]

Thanks for sharing!
Where did you get the twrp for carta2+? I have Carta+ and I've tried to flash an image from here https://www.mobileread.com/forums/sh...d.php?t=275863 with no luck. The screen light goes on when I boot into recovery, but the screen itself seems dead. Any tips?

[patsos345]

Originally Posted by Mage3

Thanks for sharing!
Where did you get the twrp for carta2+? I have Carta+ and I've tried to flash an image from here https://www.mobileread.com/forums/sh...d.php?t=275863 with no luck. The screen light goes on when I boot into recovery, but the screen itself seams dead. Any tips?

I used the same TWRP recovery you mentioned. There is not a specific one for my device. In my case the touch screen was unresponsive in twrp recovery mode. I flashed it only to get adb shell and root my device. Otherwise twrp was completely useless for me.. If you experience any difficulties in normal operating mode, such as in my device, use my method with the specific flash images for your device.

Otherwise if it is only a recovery thing, don't bother. I personally find the need for a recovery useless if I have rooted device, since you can do almost anything with su and adb.

In any case, people in the twrp recovery thread might help you better, if you have problems with recovery.

[eReader fan]

Hi people. I know how to enter in recovery mode but I am on the bootloop too and can't find the way to enter in downlaod mode. I googleized it and also looket at the C67 wii, but nothing there.

How can I enter in downlaod mode with C67ML?

[Mage3]

I believe you refer to the (boot)loader mode - the mode used to flash firmware from pc with rkbatchtool/factory tool. If so, connect the reader to pc, hold the Back button under the screen and press reset button - reset hole is near the power button, release the Back button after you hear the sound of windows recognizing the device.

You may need to install drivers before connecting the ereader to your pc:

[Althelney]

Originally Posted by patsos345

Finally I managed to restore my device to normal condition with the following full image:
https://pan.baidu.com/s/1kUSzNnT
For anyone having the same problems. Thanks everyone!

Looks like this image link is dead, anyone have another link to it?