TWRP for Amlogic devices.

[Twisted714]

fingerprint=Amlogic/q201_3G/q201_3G:6.0.1/MHC19J/20170921:userdebug/test-keys
is a q201 model with 3GB ram and android 6.01. You can find in this forum all that you need.

i need android 6.0.1. they have that?

[phumap]

@Magendanz: Is twrp for 905d (p230) available now?
Regards.

[Yemble]

OMG, this is a f*****g nightmare! Has anyone got a working TWRP for the Sunvell T95U-Pro 2Gb/16Gb running stock (rooted) Android 7.1.1 (AmLogic S912 - Nov 2016)? I have no idea about reference boards, or any of the internal components, partitions, etc., I just want a way to get Magisk 16 installed on this box without stuffing it up (again). I have never had any issue before locating a working version of TWRP for any phone or tablet.

Alternatively, can Un-SU and Magisk be successfully flashed via the AmLogic stock recovery (in a single session)? If so, how exactly?

*** EDIT ***

TWRP 3.0.2-Nougat for T95U-Pro here: https://mega.nz/#!poAmXTTL!geVautNHm...N95aHqTrGCqRVE
Sunvell T95U-Pro 2Gb/16Gb stock (rooted) Android 7.1.1 ROM here: https://mega.nz/#!v5RHwLhB!2crBWXomk...KrAYEApgF03Ikg

Use AmLogic Burn_Card_Maker v2.0.3 to burn ROM directly from TF card.
TWRP 3.0.2 works perfectly on Sunvell T95U-Pro 2Gb/16Gb running stock (rooted) Android 7.1.1 booted onto a 32Gb SanDisk UHS-1 TF (FAT-32).
Magisk 16 successfully installed (Un-SU flashed first).

[kos25k]

hello.pleeeease someone tell me a working twrp version for my new Vorke Z6 as I can't live with xposed!!!thankssss.

[avlaid]

I am looking for a TWRP for my Tanix Tx7 box (Amlogic s905x, p212 board with Andoid 7.1.2, 2GB/32GB). Could anyone give a hint where to get it?

Guest thank you for the offer. There is no Nougat firmware download available for the device, that is why I tried to backup mine with TWRP

Nougat firmware for TX7 here https://mega.nz/#!8VxwyDLK!swvvVOEe-...DBpJH64ky1f-Po

[Twisted714]

@Magendanz good morning.
after installing and using the recovery twrp.q201_N-3.2.1-0.img i have learned the it was compiled with omni 5 and so states in default.prop . i have trying to use gapps but it get stopped because it errors and quits. how can i get around that. does it it have to be compiled with omni 7? my head is spinning from all this. i have the img i got from zoomtak that is a 6.0 to 7.1.2 update. it doesnt split the way the 6.0.1 rom did. could you fix it for me?
Thanks

If you dump the kernel command line on the box by typing cat /proc/cmdline, you’ll notice the following argument:

androidboot.slot_suffix=_a

This is confusing install scripts like OpenGApps into detecting an A/B partition layout, which they're not using. That kernel command line parameter should be removed in the bootloader, but there's nothing I can do in TWRP to fix it.

For now, my workaround is to just comment out the lines in the OpenGApps install script that check for this.

[soldiaz]

I feel confused. Installed AIDA64 right away trying checkup of my WECHIP V8 box. Under SYSTEM / BOARD it says A95x_R1. Is this right? I cannot find entries such like q201..p20 and so on....

When I serach for A95x_R1 then I get boxes with ROCKCHIP! Mine is an AMLOGIC S905W.

[foz]

Anyone compiled TWRP or can tell me how to compile a TWRP for a Zoomtak Vplus running 7.1.2 please ? i have the firmware

[t211flyer]

FYI and thanks to Magendanz, I was able to flash twrp.q201_N-3.2.1-0.img from page 96, post 1440; to my Vorke Z6. Then once flashed, I was able to install Magisk. I used Rashr (from the Play Store) to flash the recovery image using the "Recovery from Storage" option. The Vorke Z6 is a TX92 S912 android tv box with Android 7.1.1

[Twisted714]

Anyone compiled TWRP or can tell me how to compile a TWRP for a Zoomtak Vplus running 7.1.2 please ? i have the firmware

cant tell you how to compile it, but i think it takes the same twrp i used. which is this one q201_N-3.2.1-0.img

http://freaktab.org/08f573fa17afdae3

[dbkalyan]

Guest Hi. Just looking for guidance. I have a M8S box which i had bricked. Managed to find a working software and got it going. I tried to flash 5.1 Lollipop onto it through TWRP. IT IS NOT BRICKED but TWRP has gone into a loop. It's preventing the launcher from working. I am thinking of doing a factory reset. Is there any other way out of it? This box has turned out to be a clone box not original.

[dbkalyan]

Guest Hi. Just looking for guidance. I have a M8S box which i had bricked. Managed to find a working software and got it going. I tried to flash 5.1 Lollipop onto it through TWRP. IT IS NOT BRICKED but TWRP has gone into a loop. It's preventing the launcher from working. I am thinking of doing a factory reset. Is there any other way out of it? This box has turned out to be a clone box not original.

subsequent to above I am getting following messages;
E:Find_File Error opening '/sys/class/leds/LCD -backlight"
E: Unable to find partition size for "/bootloader '

I assume backlight is for smartphones. More concern with bootloader. Every thing worked perfectly when I flashed the OS and software and now the launcher is not working .

Any assistance would be appreciated .

[phatboyj420]

Okay, I generated a few builds of TWRP 3.2.1-0 just to see if I could get it working, and I'm happy to report success:

• twrp.q201_N-3.2.1-0.img
• twrp.q20x-3.2.1-0.img
• twrp.p21x-3.2.1-0.img

There aren't many changes, but I've updated the GitHub repo here: https://github.com/Magendanz/android_device_amlogic

Also, in order to build version 3.2.1-0, you've got to use the following local_manifest.xml:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="omnirom"
review="gerrit.omnirom.org"
fetch="https://github.com/omnirom" />

<remove-project name="android_bootable_recovery" />
<project path="bootable/recovery" name="android_bootable_recovery" remote="omnirom" revision="android-8.0" groups="pdk-cw-fs"/>
</manifest>

Remember, the "_N" suffix is for Nougat projects, which have a separate DTB partition. The ones ending in "x" are VideoStrong variations on the Amlogic q201 and p212 reference boards.

anybody , @Magendanz

A couple of Questiions for you, if you don't mind.

1.) Witch Version of TWRP should I be using for the AML-912 Mecool BB2-Pro 16GB/3GB DDr4.


I'm currently running the SCV1 Rom and using the TWRP Built into it and have various issues the built in TWRP sais its for a S905 device but it does backup and restore if I'm not using adopted storage.
If however I am using adopted storage, it will backup but if I have any apps or data migrated to it, it will restore everything until it gets to the data partition and then it will fail with an error about unable to fork data or something similar to that and it doesn't seem to matter where I'm restoring the backup from it fails the same way wether it be from internal or external source.


2.) While using adopted storage and going to the filemanager within The TWRP noted above I cant seem to be able to view/find/access any of the contents that should be located on the internal SD. Infact under /sdcard in TWRP-filemanager the only content shown is the TWRP folder and contents there of if ive made any backups to internal.
Also i have explored all other directories such as /data/media and several others with the same results. Furtemore, directories such as /mnt and /storage arent listed at all.

So I guesse to sum it up my actual question is, is this normal behavior for the TWRP-filemanager when using adopted storage, or is it a result of using the wrong TWRP version for my device, wich would bring me back to question #1.



Thank You in advance for any advice or assistance you may offer.

...
.

[markjoren]

Hi all,
I have Vorke z1 android box and now I installed abdul TWRP 3.0.2.0 for backup to my current rom. when I am trying to make backup of my current rom from TWRP the error message appearing "/sbin/postrecoveryboot.sh process ended with error:17". ( see below image). however, my backup is completed successfully.
my concern now, is it safe to restore this backup even i got the above error message while backup ? why am getting this error while backup ?
Please any one can help me here ?
also any one can give me the Super SU zip file to flash from TWRP so I can get root excess.
am using vorke z1 android version 6.01 M.
Please Please any one help me here.
thanks in advance.
Please see below image for error message while doing backup.

[phatboyj420]

Hi all,
I have Vorke z1 android box and now I installed abdul TWRP 3.0.2.0 for backup to my current rom. when I am trying to make backup of my current rom from TWRP the error message appearing "/sbin/postrecoveryboot.sh process ended with error:17". ( see below image). however, my backup is completed successfully.
my concern now, is it safe to restore this backup even i got the above error message while backup ? why am getting this error while backup ?
Please any one can help me here ?
also any one can give me the Super SU zip file to flash from TWRP so I can get root excess.
am using vorke z1 android version 6.01 M.
Please Please any one help me here.
thanks in advance.
Please see below image for error message while doing backup.

that error message is Normal as far as I can tell, I mean I get the same error and can restore

http://www.supersu.com/download Go to site and download it from there use 2.82 for system-less Root or the older 2.79 for the regular SuperSU of Old links attached Also