TWRP_RK3368_3.1.0-0_170318

[followmsi]

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!

Yes, it´s fine like this .. you can go to mount menu and mount other partitions as well.
Did you try ? Does it work ? Of course, only if the partition exists.


PS: "__bionic_open_tzdata:" Does not want to find anything. I'm curious about how to fix that.

Where and when do you get the "bionic" messages in my new TWRP version ?
If you have the same output as above, you don´t have a "bionic" issue.

Or do you just want to know ..how to fix the bionic messages for your own compilation ?
I will explain to you .. no problem.

Pls confirm !

Can you pls post the output of the followig command ... just to be safe

adb shell cat /tmp/recovery.log

Cheers

[dkholm56]

So the only way to install this is to already have TWRP installed? I have the M8 Pro 64 bit and I can't get any TWRP on this box? Is there not a way to install it without having TWRP already installed as recovery.
thanks

[followmsi]

So the only way to install this is to already have TWRP installed? I have the M8 Pro 64 bit and I can't get any TWRP on this box? Is there not a way to install it without having TWRP already installed as recovery.
thanks

No .. it´s the most easiest way

On the first page ...

For installation via flashify .. etc.

TWRP_3.0.2-0_RK3368_V160607.img

Cheers

[kerenmac]

Yes, it´s fine like this .. you can go to mount menu and mount other partitions as well.
Did you try ? Does it work ? Of course, only if the partition exists.


PS: "__bionic_open_tzdata:" Does not want to find anything. I'm curious about how to fix that.

Where and when do you get the "bionic" messages in my new TWRP version ?
If you have the same output as above, you don´t have a "bionic" issue.

Or do you just want to know ..how to fix the bionic messages for your own compilation ?
I will explain to you .. no problem.

Pls confirm !

Can you pls post the output of the followig command ... just to be safe

adb shell cat /tmp/recovery.log

Cheers

I have uploaded the log content here: http://txt.do/5bze3
I hope you find a clue there.
Thanks for the offer, but I'm a total noob in Android world and I'm a quite busy person (it's 2:45AM in Spain ). Also, I'd prefer not to destroy my first Android device .
Regards.

[followmsi]

I have uploaded the log content here: http://txt.do/5bze3
I hope you find a clue there.
Thanks for the offer, but I'm a total noob in Android world and I'm a quite busy person (it's 2:45AM in Spain ). Also, I'd prefer not to destroy my first Android device .
Regards.

Perfect logs .. no bionic problems at all !
You still not confirmed .. but I understand now .. you want to know how to fix ...

You need to add the folder like we said before ..

/system/usr/share/zoneinfo ... here you copy the file tzdata only .. from system folder from build process ...

got it ?

cheers

[kerenmac]

Perfect logs .. no bionic problems at all !
You still not confirmed .. but I understand now .. you want to know how to fix ...

You need to add the folder like we said before ..

/system/usr/share/zoneinfo ... here you copy the file tzdata only .. from system folder from build process ...

got it ?

cheers

I have been able to update the tzdata downloading the latest tzdata binary file from bionic github repo and substituting it with Terminal (I found some steps). Now the log looks clean, but the date goes back to 1/1/2011 on every system startup. Here you have the log: http://txt.do/5b74k
I have done an small research and it seems that TWRP 3.0.2-0 has some problems with this, but even if it has a problem I should have seen a difference somehow, but updating the tzdata has done nothing in my case, it has only removed those "tzdata not found" messages (it might be important, but as nothing has changed it is wasted time).
Thanks and regards.

[followmsi]

I have been able to update the tzdata downloading the latest tzdata binary file from bionic github repo and substituting it with Terminal (I found some steps). Now the log looks clean, but the date goes back to 1/1/2011 on every system startup. Here you have the log: http://txt.do/5b74k
I have done an small research and it seems that TWRP 3.0.2-0 has some problems with this, but even if it has a problem I should have seen a difference somehow, but updating the tzdata has done nothing in my case, it has only removed those "tzdata not found" messages (it might be important, but as nothing has changed it is wasted time).
Thanks and regards.

When you compile .. inside the out folder is also a system folder .. there is one tzdata .. your own tzdata .. try with this one, not from GitHub.
And better ?

But just a second .. before we get confused.
The Logs here are using my version .. and you have always 2011 ..

when you start you normal Android System .. which time do you have .. adb shell logcat ?

Edit: checked recovery in geekbox again .. have correct date from time of the recovery boot.

What is the date of backups you do ? .. all in 2011 ?

[dkholm56]

No .. it´s the most easiest way

On the first page ...

For installation via flashify .. etc.

TWRP_3.0.2-0_RK3368_V160607.img

Cheers

Tried the above image with Flashify, but when I select the image from sd using ES File Explorer Flashify seems to crash with just a white screen. Any idea why that happens. My box is the M8 Pro rk3368 64 bit.

Thanks

[followmsi]

Tried the above image with Flashify, but when I select the image from sd using ES File Explorer Flashify seems to crash with just a white screen. Any idea why that happens. My box is the M8 Pro rk3368 64 bit.

Thanks

Actually I wrote flashify because some users from here which used it successfully... I personally use rockchip tools for Linux.

How do you flash images today ?
Are you able to flash a single partition today ?

If not .. have a try ..

https://onedrive.live.com/?authkey=%21AKwElTGRNqaMHg0&id=5842EE9E65C3FAF6%21151&cid=5842EE9E65C3FAF6

There is a tool for Windows .. AndroidTool_Release_v2.35_TWRP_Windows_ENG.zip

Try this one .. replace the old TWRP file with the new one ..
Or flash new Version after you installed the Version from the tool via TWRP.

We just want to replace recovery .. nothing more !

Good luck ..

[dkholm56]

Actually I wrote flashify because some users from here which used it successfully... I personally use rockchip tools for Linux.

How do you flash images today ?
Are you able to flash a single partition today ?

If not .. have a try ..

https://onedrive.live.com/?authkey=%21AKwElTGRNqaMHg0&id=5842EE9E65C3FAF6%21151&cid=5842EE9E65C3FAF6

There is a tool for Windows .. AndroidTool_Release_v2.35_TWRP_Windows_ENG.zip

Try this one .. replace the old TWRP file with the new one ..
Or flash new Version after you installed the Version from the tool via TWRP.

We just want to replace recovery .. nothing more !

Good luck ..

Thanks for the reply.
I'll give the tool a try. I haven't been able to flash anything on this box yet??? I have tried using the OTA update method via SD, USB Burning Tool, Flashify, Rashr. I can't even get it to connect using adb???
really strange....

[followmsi]

Thanks for the reply.
I'll give the tool a try. I haven't been able to flash anything on this box yet??? I have tried using the OTA update method via SD, USB Burning Tool, Flashify, Rashr. I can't even get it to connect using adb???
really strange....

The Windows Tool from above is using Loader mode .. where you need to connect USB cable to xour Box.
It's not adb .. but you have to bring you Box into Loader more ..
Try to make "reboot loader" from terminal app inside Android ..

Here on freaktab are more tools to backup you existing Rom .. extract .. etc.

Pls search .. you will find.

Good luck !

[followmsi]

Bug fix release ...

- Fixed bug for system partition mounting / unmounting.

Update.ZIP_TWRP_RK3368_3.0.2-1_160622.zip

TWRP_RK3368_3.0.2-1_160622.img


Enjoy !

[androidfr33k]

followmsi ,

Thanks for sharing this great work of yours. I have tried your SuperSu and Twrp v 3.02 on my Zidoo X6 Pro and everything seems to work just fine. There is some bug however and not related to your version of Twrp. With Abdul's version 2.8.7 I have the same issue where the remote controller won't work nor will a USB keyboard or mouse work unless I connect a male to male USB cable to the Zidoo to power the ports, then I have functional mouse and keyboard but not remote. I am ok with that for now but wondered if you had any ideas as to why the USB is not powered in TWRP or do I have to configure this for TWRP?

I also had to use Oneroot.apk released by the Zidoo team to root the device. I was not sure how to root it any other way, unless installing Supersu does this automatically?

I also cannot figure out how to install TWRP from scratch. I do have an Abdul twrprecovery.img and after renaming it to recovery.img and uploading it to the X6 via Android tool I still have the stock android recovery and not TWRP? Is there some kind of security in place for Android 5.1.1 possible preventing this?

Also do you have both versions of TWRP the updater and full img? If so I can try the full img version to see if it will work on Android tool v2.35. It actually will work and says ok in the end it just wont boot to twrp not sure what the deal is. I don't think it actually gets installed because I don't see a TWRP folder anywhere on the Android device, maybe hidden or does not exactly replace the original recovery partition even though it does flash successfully according to Android tool v2.35. I am just trying suggest some possibilities. The TWRP image resides on the recovery partition correct? Maybe it is not active, but very unclear why the android recovery is still in place?

Thanks

[followmsi]

Hi

RK3368 is the same CPU .. but the rest is different.
USB works on "most" devices, even with special tricks, like you did.

There is no configuration for USB inside GUI.
You may edit the ramdisk itself to fit your USB config.
Assuming all USB stuff works well in Android System, e.g. the kernel is working fine.

On my device I can use USB keyboard and und USB Mouse and micro USB for adb at the same time.


SuperSu is the root tool .. if installed on Android L it "should" work without any special Flags.
No need for other tools.


Yes, a lot of Android systems do restore original recovery.
SuperSu is trying to kill this mechanism too

If you work with flash tools, like you do, use the .img . May rename it to recovery.img, for better handling.

But otherwise you do correct, the system is replacing the "stock" recovery while booting.
Try SuperSu.zip via TWRP .. this should solve this problem.

But zidoo is even more special with their "secure" way of doing .. isnt it ?

[androidfr33k]

Hi

RK3368 is the same CPU .. but the rest is different.
USB works on "most" devices, even with special tricks, like you did.

There is no configuration for USB inside GUI.
You may edit the ramdisk itself to fit your USB config.
Assuming all USB stuff works well in Android System, e.g. the kernel is working fine.

On my device I can use USB keyboard and und USB Mouse and micro USB for adb at the same time.


SuperSu is the root tool .. if installed on Android L it "should" work without any special Flags.
No need for other tools.


Yes, a lot of Android systems do restore original recovery.
SuperSu is trying to kill this mechanism too

If you work with flash tools, like you do, use the .img . May rename it to recovery.img, for better handling.

But otherwise you do correct, the system is replacing the "stock" recovery while booting.
Try SuperSu.zip via TWRP .. this should solve this problem.

But zidoo is even more special with their "secure" way of doing .. isnt it ?

Thanks so much for the reply. I believe Zidoo may have a twist to their rom to besides the system placing the original recovery back into place. I had a lengthy discussion with the Zidoo tech team and they are going to release a rooted/twrp full image rom in the next release v1.0.39 and also include a full version 1.0.39 normal zidoo rom. I told them they would be the first company to do such a thing that normally 3rd party developers get in there and make the roms more customizable and more attractive. Of course for them its a selling point so they are giving it a try. They did make the ones that were bought from the market with roooted rom but not TWRP. The reason they stopped doing it is because the OTA updates stop working but I told them if you have TWRP, people can update with a zip version of the rom. I am not sure if they got that part of it though?

I figured out the problem even though I know I flashed the original zidoo boot.img since it was an OTA update I grabed the boot.img from it apparently did not have the kernel within it or did not replace Lonix's kernel. Lonix takes the Zidoo rom and tromsmart kernel to make a custom rom for the tronsmart tv box. To make things easier on me I flash that rom since it rooted and has twrp already as part of the rom then I have to replace the kernel with the original Zidoo rom. This is really tricky if I don't have the full img rom because OTA updates make it difficult to extract the kernel and resource files from them. I had to grab a kernel and resource file from a Full rom version that is like 3 versions earlier from OTA updates.

The USB is working now but not the TV controller.

Thanks Again!!