TWRP_RK3368_3.1.0-0_170318

[kerenmac]

I tested the TWRP 3.0.2 that you recommended (after updating SuperSU) and now It has got the same problems that I had before, and now it doesn't mount external_sd and it doesn't go fullscreen (small detail), so basically TWRP is an accessory on my MK68 at the moment. How can i solve it or go back to the other TWRP version?
Thanks.

[scooter2014]

I just check on my mk68 twrp load ok with sd you have to select sd. I load and flash older firmware it work but dumb move on my part have to re flash it now lol... Maybe later today u re load. I didnt try zip for update su just from file install from flash tool.

[followmsi]

I tested the TWRP 3.0.2 that you recommended (after updating SuperSU) and now It has got the same problems that I had before, and now it doesn't mount external_sd and it doesn't go fullscreen (small detail), so basically TWRP is an accessory on my MK68 at the moment. How can i solve it or go back to the other TWRP version?
Thanks.

Tested external SD -- no problems . just made a restore from it

No full screen is a "feature" - some people have HDMI overscan problems ..the same proplem like you - but the other way around .)
Now all can see the full screen .. even a bit smaller

What TWRP did you use before ?

[followmsi]

I just check on my mk68 twrp load ok with sd you have to select sd. I load and flash older firmware it work but dumb move on my part have to re flash it now lol... Maybe later today u re load. I didnt try zip for update su just from file install from flash tool.

While testing restore from external_sd card I saw TWRP will format "internal_sd" as Exfat and restore all the data on Exfat partition ...
Andoid L .. does not like ExFAt .. it will not mount the internal_sd .. -> problem for L .. will hopefully fix this soon.

Android M does not have "internal_sd" anymore.

Cheers

Update: .. no Problem at all .. if you play too much, you should expect strange issues too.
i did some exFAT testing on my other box and did not revert the change ..
changed back the filesystem to fat32 and made new restore, all fine on fat32.
Android L is mounting again ..

No problems !

[son1979]

What is the actual problem right now ?

Thanks

Thank you, you modify the TWRP I have received, has been brushed into the TV box

However, I am in the TWRP interface, can not operate, the use of USB mouse or keyboard can not operate!

Can only use the power key on the remote control, can not operate unlock and do other operations!

PS: the use of USB OTG switching line. Also unable to use USB mouse or keyboard.

[followmsi]

Thank you, you modify the TWRP I have received, has been brushed into the TV box

However, I am in the TWRP interface, can not operate, the use of USB mouse or keyboard can not operate!

Can only use the power key on the remote control, can not operate unlock and do other operations!

PS: the use of USB OTG switching line. Also unable to use USB mouse or keyboard.

Inside normal Android system you have no problems to use mouse / keyboard ?
Just inside TWRP is does not work ?

On my kernel keyboard is working fine ... also inside TWRP !
Depends on your hardware ..

USB-OTG is normally for flashing firmware..not connecting devices.

Pls have a look into this folder .. https://onedrive.live.com/?authkey=%...42EE9E65C3FAF6

4 different versions : lollipop kernel - with / without resource.img

recovery-new_lollipop-res.img

recovery-new_lollipop.img

same with mmallow kernel ...

recovery-new_mmallow-res.img

recovery-new_mmallow.img

Have a try ..

[kerenmac]

While testing restore from external_sd card I saw TWRP will format "internal_sd" as Exfat and restore all the data on Exfat partition ...
Andoid L .. does not like ExFAt .. it will not mount the internal_sd .. -> problem for L .. will hopefully fix this soon.

Android M does not have "internal_sd" anymore.

Cheers

Update: .. no Problem at all .. if you play too much, you should expect strange issues too.
i did some exFAT testing on my other box and did not revert the change ..
changed back the filesystem to fat32 and made new restore, all fine on fat32.
Android L is mounting again ..

No problems !

Changing the format made the trick. I don't know why but it had NTFS format. Changed format to exFat and now it's working well, it has the timezone problem (reverts back to 2011 on every reboot), but at least everything else is working as it should. Thanks a million.
I won't give to the timezone problem importance, as I the box is always connected to Internet only needs 10 seconds until date and hour get updated.

Regards!

EDIT: Android is not detecting the MicroSD in exFAT, I'm going to try with FAT32. I don't understand why it can hold NTFS and not exFAT. I would really appreciate not to be attached to FAT32 limitations, but some research over the internet hasn't returned solutions. HELP!

[followmsi]

Changing the format made the trick. I don't know why but it had NTFS format. Changed format to exFat and now it's working well, it has the timezone problem (reverts back to 2011 on every reboot), but at least everything else is working as it should. Thanks a million.
I won't give to the timezone problem importance, as I the box is always connected to Internet only needs 10 seconds until date and hour get updated.

Regards!

EDIT: Android is not detecting the MicroSD in exFAT, I'm going to try with FAT32. I don't understand why it can hold NTFS and not exFAT. I would really appreciate not to be attached to FAT32 limitations, but some research over the internet hasn't returned solutions. HELP!

I am not sure if we can include this into the rockchip Android kernel.. maybe we can compile a new kernel with exFAT.

[kerenmac]

I am not sure if we can include this into the rockchip Android kernel.. maybe we can compile a new kernel with exFAT.

It seems to be working fine with Fat32. I'll stay like that, I won't spend more time with these tv box, it is not worth the lost time.
Regards.

[son1979]

Inside normal Android system you have no problems to use mouse / keyboard ?
Just inside TWRP is does not work ?

On my kernel keyboard is working fine ... also inside TWRP !
Depends on your hardware ..

USB-OTG is normally for flashing firmware..not connecting devices.

Pls have a look into this folder .. https://onedrive.live.com/?authkey=%...42EE9E65C3FAF6

4 different versions : lollipop kernel - with / without resource.img

recovery-new_lollipop-res.img

recovery-new_lollipop.img

same with mmallow kernel ...

recovery-new_mmallow-res.img

recovery-new_mmallow.img

Have a try ..

This tvbox has only one USB port, tested all you sent to you my img, can not operate

Can normally see the interface, can not unlock and operation, it appears that the remote control key configuration or hardware configuration is not the same

Kernel has been using Image Kitchen Android transplant, the same situation, can not be operated

TWRP official description is to support the USB mouse, and I am the mouse hardware compatibility issues? thank you！

[followmsi]

This tvbox has only one USB port, tested all you sent to you my img, can not operate

Can normally see the interface, can not unlock and operation, it appears that the remote control key configuration or hardware configuration is not the same

Kernel has been using Image Kitchen Android transplant, the same situation, can not be operated

TWRP official description is to support the USB mouse, and I am the mouse hardware compatibility issues? thank you！

But You can normally use USB Mouse or keyboard inside Android System ?
remote control will not work.

Can you connect via adb to recovery shell ?

If this is working you may try OTG cable for Mouse.

[followmsi]

The TWRP sources are now fully integrated into rockchip Android M sources ..

If there is a new TWRP version coming .... "git pull" and we are done

And here is the first full 64Bit TRWP version for RK3368 devices ... based on Android M - what else

TWRP_3.0.2-0_RK3368_V160607

- Fresh compiled TWRP 3.0.2-0 on rockchip Android M sources -> 64Bit version
- Fixed "HDMI overscan" -> you should see the full screen now.
- Added Linux partition "linuxroot" for dualOS setup.
- "Internal_SD" exists even on Unified Storage setup. (if you are on android M you will see "can´t mount internal_sd" -> this is ok !)
- data encryption/decryption is compiled into this version now - but not tested.
- fstab optimization for RK3368

Cheers

[kerenmac]

The TWRP sources are now fully integrated into rockchip Android M sources ..

If there is a new TWRP version coming .... "git pull" and we are done

And here is the first full 64Bit TRWP version for RK3368 devices ... based on Android M - what else

TWRP_3.0.2-0_RK3368_V160607

- Fresh compiled TWRP 3.0.2-0 on rockchip Android M sources -> 64Bit version
- Fixed "HDMI overscan" -> you should see the full screen now.
- Added Linux partition "linuxroot" for dualOS setup.
- "Internal_SD" exists even on Unified Storage setup. (if you are on android M you will see "can´t mount internal_sd" -> this is ok !)
- data encryption/decryption is compiled into this version now - but not tested.
- fstab optimization for RK3368

Cheers

Installed (RKM MK68 - SC V1.3C). Working OK. No full-screen, but it does not matter, just 2-3cm black spaces around the main window. I like the blue theme, really nice. Everything seems to be working fine. I prefer the updated storage and mnt partitions, very clean. Thanks a million for the update.
PS: "__bionic_open_tzdata:" Does not want to find anything. I'm curious about how to fix that.

[followmsi]

Installed (RKM MK68 - SC V1.3C). Working OK. No full-screen, but it does not matter, just 2-3cm black spaces around the main window. I like the blue theme, really nice. Everything seems to be working fine. I prefer the updated storage and mnt partitions, very clean. Thanks a million for the update.
PS: "__bionic_open_tzdata:" Does not want to find anything. I'm curious about how to fix that.

Thanks for feedback.
You get bionic_open_data ?
hmmmm .. Need to check this ..
Pls Mount System and try again. .? Still Bionic message ?

It's cosmetic .. but still .. there are a lot of discussions about the Bionic stuff ..

The screen size is a feature for the people who have HDMI Overscan.
Like me on the old Sony tv
I see it full screen now

Cheers


EDiT:

Since I have integrated the "geekbox" tzdata file I don´t have any problems with bionc messages anymore.
They are part of this release.

Pls make .. with "unmounted" system ..

adb shell ls -la /system/usr/share/zoneinfo
drwxr-xr-x 2 root root 0 Jan 1 1970 .
drwxr-xr-x 3 root root 0 Jan 1 1970 ..
-rw-r--r-- 1 root root 494261 Jan 1 1970 tzdata

You get the same result ?

Thanks

[kerenmac]

Thanks for feedback.
You get bionic_open_data ?
hmmmm .. Need to check this ..
Pls Mount System and try again. .? Still Bionic message ?

It's cosmetic .. but still .. there are a lot of discussions about the Bionic stuff ..

The screen size is a feature for the people who have HDMI Overscan.
Like me on the old Sony tv
I see it full screen now

Cheers


EDiT:

Since I have integrated the "geekbox" tzdata file I don´t have any problems with bionc messages anymore.
They are part of this release.

Pls make .. with "unmounted" system ..

adb shell ls -la /system/usr/share/zoneinfo
drwxr-xr-x 2 root root 0 Jan 1 1970 .
drwxr-xr-x 3 root root 0 Jan 1 1970 ..
-rw-r--r-- 1 root root 494261 Jan 1 1970 tzdata

You get the same result ?

Thanks

Yes, exactly the same result (From Terminal en TWRP with the System unmounted). Some time ago I tried to fix it putting some (missing) files that had relation with the timezone, but nothing happened.
In TWRP only Cache, Data and Micro SDCard are mounted. Is that fine?
Thanks!