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

[Purple Lady]

I was going to go back to the E653 rom but I got stupid and went to settings and checked for an upgrade after putting the zip in the root directory like I think I had to on my T68 and it started downloading an update. Turns out that wasn't a stupid thing to do. Since the update I've had no crashes and no freezing. Here's a screenshot from settings

[downeaster59]

Originally Posted by Purple Lady

I was going to go back to the E653 rom but I got stupid and went to settings and checked for an upgrade after putting the zip in the root directory like I think I had to on my T68 and it started downloading an update. Turns out that wasn't a stupid thing to do. Since the update I've had no crashes and no freezing. Here's a screenshot from settings
Attachment 134198

Yes, that's the rom I'm on now. It's been smooth as silk for me so far. Glad it's working for you, too. Boyue seems to have fixed some bugs.

Every once in a while, a "mistake" isn't really one!

[Purple Lady]

Originally Posted by downeaster59

Yes, that's the rom I'm on now. It's been smooth as silk for me so far. Glad it's working for you, too. Boyue seems to have fixed some bugs.

Every once in a while, a "mistake" isn't really one!

I guess you got this by checking for an update on your device and letting it download? The version in the first post is from 11/24 and mine is 11/27.

[downeaster59]

Originally Posted by Purple Lady

I guess you got this by checking for an update on your device and letting it download? The version in the first post is from 11/24 and mine is 11/27.

Yes, that is correct. As soon as I installed the 11/24 version, I checked for an update and there indeed was one. Only three days newer, it seems, but it does seem better all around.

[Purple Lady]

Originally Posted by downeaster59

Yes, that is correct. As soon as I installed the 11/24 version, I checked for an update and there indeed was one. Only three days newer, it seems, but it does seem better all around.

Do you use the OverDrive app? The pages get cut off for me - the right side has part of the next page and the left side is cut off. This happens after a few pages into a chapter and is easiest to see if you set your margins to none.

[downeaster59]

Sorry, I've never used OverDrive. When I have some time tomorrow, I may try it, though, and see if I get the same effect you do.

[Purple Lady]

Originally Posted by downeaster59

Sorry, I've never used OverDrive. When I have some time tomorrow, I may try it, though, and see if I get the same effect you do.

I just heard back from OverDrive and it is a known bug for "a small number of devices with somewhat uncommon screen resolutions." They have an older version that doesn't have the bug on their website for anyone who's interested.

Maybe I should edit the build.prop and change the lcd density and see if I can find one that works and doesn't screw anything else up. Does anyone know what I could change it to that won't mess things up? It's currently set to 212.

[Purple Lady]

Originally Posted by Purple Lady

I just heard back from OverDrive and it is a known bug for "a small number of devices with somewhat uncommon screen resolutions." They have an older version that doesn't have the bug on their website for anyone who's interested.

Maybe I should edit the build.prop and change the lcd density and see if I can find one that works and doesn't screw anything else up. Does anyone know what I could change it to that won't mess things up? It's currently set to 212.

Whatever you do, don't set it to 240! You'll get "unfortunately system ui has stopped". Now to remember how to use adb! I have a copy saved, so I just need to replace the current with my saved one.

[Ranomez]

Hi everyone, I'm new and will buy my Wayteq xBook-60fl in 2 days (which is the hungarian version of the Boyue t61/Icarus Illumina E653) and have some questions that I would love if any of you could answer:

1. Is there any big risk in flashing the firmware of one of the others (like not working touchscreen)?
2. Is there any way to make a full backup of the rom in the format that can be flashed by rkflashtools?
3. What is the cpu in the device (I have my bet on rk3026)?
4. Is there any recovery-from-boot.p file or other file like that that would flash the stock recovery at boot that I need to be aware of and can it be safely removed or would I get a brick?
5. What is the button combination to boot into recovery?
6. Is there a bootloader mode that would let me execute fastboot commands and if yes what is the button combination to access it?
7. Can the stock kernel/recovery be unpacked normally or does it require rockchip specific unpack tools (asking this cause my Onda tablet requires specific amlogic versions of the unpack tools to decompile the kernel and recovery images)?
8. Did anyone before try to make a custom recovery (CWM/TWRP) for this device and did they put their work on github?

Thank you very much.

[downeaster59]

Originally Posted by Ranomez

Hi everyone, I'm new and will buy my Wayteq xBook-60fl in 2 days (which is the hungarian version of the Boyue t61/Icarus Illumina E653) and have some questions that I would love if any of you could answer:

1. Is there any big risk in flashing the firmware of one of the others (like not working touchscreen)?
2. Is there any way to make a full backup of the rom in the format that can be flashed by rkflashtools?
3. What is the cpu in the device (I have my bet on rk3026)?
4. Is there any recovery-from-boot.p file or other file like that that would flash the stock recovery at boot that I need to be aware of and can it be safely removed or would I get a brick?
5. What is the button combination to boot into recovery?
6. Is there a bootloader mode that would let me execute fastboot commands and if yes what is the button combination to access it?
7. Can the stock kernel/recovery be unpacked normally or does it require rockchip specific unpack tools (asking this cause my Onda tablet requires specific amlogic versions of the unpack tools to decompile the kernel and recovery images)?
8. Did anyone before try to make a custom recovery (CWM/TWRP) for this device and did they put their work on github?

Thank you very much.

I'll share what i know, and others can fill in the gaps.

1) Be careful with firmware. Yes, the firmware of some other devices will work on your device, but there are T61B and T61C devices out there. Use the wrong firmware and you have problems! B won't work on C, and vice versa. I have a T62B. The E653 firmware works on my device, with only a few glitches.
2) Check out the RK3026 E-readers Kitchen thread in this forum. You'll find some answers there, and people who can help.
3) Probably is RK3026, if it's like the T61.
4) That I do not know. Someone like nightboy may be able to help you there.
5) I've used ADB for that, so I don't know.
6) adb reboot-bootloader works for me. There are others, I know.
7) Not sure, but it probably needs the RK-specific packing tools. Again, check out the RK 3026 e-readers kitchen!
8) No one to my knowledge has made a custom recovery for any of these devices, whether CWM or TWRP. We'd all LOVE one!

Anyone else who knows the other answers, feel free to jump in.

[Ranomez]

Originally Posted by downeaster59

I'll share what i know, and others can fill in the gaps.

1) Be careful with firmware. Yes, the firmware of some other devices will work on your device, but there are T61B and T61C devices out there. Use the wrong firmware and you have problems! B won't work on C, and vice versa. I have a T62B. The E653 firmware works on my device, with only a few glitches.
2) Check out the RK3026 E-readers Kitchen thread in this forum. You'll find some answers there, and people who can help.
3) Probably is RK3026, if it's like the T61.
4) That I do not know. Someone like nightboy may be able to help you there.
5) I've used ADB for that, so I don't know.
6) adb reboot-bootloader works for me. There are others, I know.
7) Not sure, but it probably needs the RK-specific packing tools. Again, check out the RK 3026 e-readers kitchen!
8) No one to my knowledge has made a custom recovery for any of these devices, whether CWM or TWRP. We'd all LOVE one!

Anyone else who knows the other answers, feel free to jump in.

Thank you for the answers, I saw the e-reders kitchen thread after I posted my comment and for some reason couldn't edit my post to delete some of the questions as for question 8 I asked because I am planning to try to make a recovery (can't promise anything, I am not a developer, I can edit/customize a rom but didn't attempt to make a recovery since I had my htc touch pro 2 and that was 4 years ago and the recovery I made was not really working well, if I remember right it was not generating md5 files on backups) but I will first try to boot the generic rk3026 TWRP and CWM recoveries now that I know there is a bootloader mode (which I expect to not work mostly because the e-ink screen).

[nightboy]

Originally Posted by Ranomez

Hi everyone, I'm new and will buy my Wayteq xBook-60fl in 2 days (which is the hungarian version of the Boyue t61/Icarus Illumina E653) and have some questions that I would love if any of you could answer:

1. Is there any big risk in flashing the firmware of one of the others (like not working touchscreen)?
2. Is there any way to make a full backup of the rom in the format that can be flashed by rkflashtools?
3. What is the cpu in the device (I have my bet on rk3026)?
4. Is there any recovery-from-boot.p file or other file like that that would flash the stock recovery at boot that I need to be aware of and can it be safely removed or would I get a brick?
5. What is the button combination to boot into recovery?
6. Is there a bootloader mode that would let me execute fastboot commands and if yes what is the button combination to access it?
7. Can the stock kernel/recovery be unpacked normally or does it require rockchip specific unpack tools (asking this cause my Onda tablet requires specific amlogic versions of the unpack tools to decompile the kernel and recovery images)?
8. Did anyone before try to make a custom recovery (CWM/TWRP) for this device and did they put their work on github?

Thank you very much.

1.Yes
2.Yes
3-the SOC is rk3026
4.Yes, you have to delete /etc/recovery-resource.dat to stop the recovery's re-installation
5.To get into recovery mode, press & hold the refresh button for 5-6 sec then press the power button for 2-3 sec and keep holding the refresh button for 2-3 sec
6.Yes but I have not tested fastboot
7. what do you mean by "normally" or which tools your using ? ... anyway there are many tools to unpack the boot.img and recovery.img
8. I did. it is easy to build a bootable TWRP or CWM but they did not work since the eink screen does not work in these recoveries. Either the kernel src or a special "graphics.c" will make it possible to port these recoveries.

[Ranomez]

Originally Posted by nightboy

8. I did. it is easy to build a bootable TWRP or CWM but they did not work since the eink screen does not work in these recoveries. Either the kernel src or a special "graphics.c" will make it possible to port these recoveries.

I was thinking having a look on how they made the e-ink screen work in CWM on the Nook Simple Touch/Glowlight could give me some ideas on how to make it work on this one but as a temporary workaround (to first get a 100% working recovery and then worry about getting anything to show up on the screen) wouldn't it be possible to direct the video signal to an other screen via MHL (ofc I am just guessing it does support MHL, I do not know yet as I don't have the device yet, will be getting it in about 16h) I know that it can be done if the device supports it from the fact that I had a cheap "romanian" (made in china) tablet in my hands (not owned) that for some odd reason would show the recovery on the TV if I would boot in recovery with the MHL cable connected and I'm not even talking about a custom recovery but the stock recovery?

Anyway did you happen to post your sources on github or do you still have them and could send them to me, it would be of great help not having to start from 0 (even the final built img files could be of some help probably)?

An other question: were you building a recovery with kernel or without kernel (as far as I understand rockchip recoveries can have kernel integrated or not)?

[Ranomez]

Originally Posted by nightboy

4.Yes, you have to delete /etc/recovery-resource.dat to stop the recovery's re-installation

What type of re-installation is it and will it just re-install the old recovery or can it brick the device (asking this because on my tablet on the stock ROM there was a file called recovery-from-boot.p that if not deleted before flashing a custom recovery it would brick the tab on boot, didn't really read the file to see exactly what it did but I know some got bricked tabs like that and it is pretty clear it did not simply re-install the old recovery)?

Also I did look at any type of nook source I could find and unfortunately found nothing that would even give me an idea (was kinda expecting that but still had hope cause both devices have e-ink screens) so for now I think I will try to figure out the MHL method I described earlier (as soon as I get my device ofc and find out if it does or not support MHL), it will not be a on-the-go usable recovery but if I manage to figure that out it will be more than nothing, we will at least have a working recovery, but to say the truth I have absolutely no idea where to start from, except that one device I have never seen a recovery with MHL/HDMI support so I don't really know how that would even work.

[Ranomez]

Can someone please explain to me how on earth to wipe data, I only have a "erase sd card" checkbox in factory reset in settings and no button to actually wipe?