TWRP for Amlogic devices.

Just copy it over in TWRP File Manager and set permissions to chmod 744. You might also need to set SELinux permissions, but that will be done automatically when you apply file contexts in make_ext4fs.

[Jancales]

Thanks for your response, I'll give it a try.

Is this a simple copy and paste job, or do i need to use Terminal or any other software?

Migrating the kernel module (*.ko file in /system/lib) for the display could work.

[Jancales]

Guest Off topic to this thread, but since you're a developer I hope you're able to answer my question.

I flash a custom firmware to a device with an lcd display. Afterwards the display doesn't work any more.

Is there a way, probably by moving files from the stock rom to the custom rom, to make the display work again?

If the stock p212 version I made doesn't work, just let me know. I've actually got one of those for testing, but it's only 1GB DRAM and so I don't use it much.

[mikhoul]

Guest Do you know if somebody have built a TWRP V3.1.1.0 for the Nexbox A95X 2gb/16gb (P212) ?


Regards

Well, yes and no. You can convert the raw images to what USB Burning Tool needs using abootimg and make_ext4fs (and trimming bootloader in a hex editor). However, you still need the u-boot binaries from an existing Amlogic burn package for that device. You're just replacing the *.PARTITION files in the tmp/level1 directory, but without those u-boot files (DDR.USB, UBOOT.USB, aml_sdc_burn.UBOOT) you can't flash it to the device.

[Jancales]

Guest Apologies if this question is answered already, but 95 pages is a lot to go through.

I have made a TWRP backup from my firmware, and now want to install it on some other devices of mine.

The problem is that on those devices you can't install or boot into TWRP recovery, also burn card maker doesn't work because you can't boot in stock recovery either, so the only way to install a firmware is with usb burning tool.

Is there a way to make an image file from the TWRP backup, or some way to backup to an image file?

The devices are S905X and I used TWRP 3.0.2

[mozes]

TWRP for Alfawise H96 Pro+ ??

[abuzainalabedeen]

Anyone here help me to create trwp recovery for this device

this is offical recovery image
https://drive.google.com/file/d/0B-F...xxRnBLU0E/view

This is link for software
http://www.icone.bz/downloads/Androi...p?id=stwo_1371

And this is link for information about this device
http://www.icone.bz

[ssarava9]

I have nexbox a95x and after flashing a zip file im unable to boot into system, it keeps bringing to twrp recovery, any suggestions on how to load into systems from TWRP recovery ?
Please help as im stuck

[Xannytech]

i did exactly what you did. Then examining what you did for q201_64 i came to the same conclusion...more than a 64 it's revised q201.
Anyway in my case it's really a mistery, i changed also the partitions from my system, but nothing changed, only my systemcontrol_static it's 577.560bytes, but until it boots correctly i'm not worried... Thanks again.

This was a while ago, and so my memory isn't that fresh. I had success building with the old Android 6.0.1 device configuration on twrp-5.1 branch, but I modified the following:

- Removed secondary bootloader from BOARD_MKBOOTIMG_ARGS (which contained dtb)
- Added TW_NO_SCREEN_BLANK := true
- Swapped in new OEM kernel
- Used OEM stock recovery fstab.amlogic, init.rc, ueventd.amlogic.rc, and kernel modules (dwc3.ko & dwc_otg.ko)
- Reverted to older version of systemcontrol_static (210,932 bytes)

That last item was what fixed my display sync issues, which could also be remedied by unplugging the HDMI connector and plugging it back in. What definitely didn't work was moving to twrp-7.1 branch or switching to ARM64 CPU architecture. (Ironically, I called the project q201_64. I should really rename it q201_N.)

[Xannytech]

Hi Guest i'm trying to build TWRP for a non commercial device i got for a external project it's based on q201 board and was born with 7.1.2 64bit android, i read in this thread you faced my same issue bulding the GT1 64bit recovery, can i ask you a hint, like how did you solve your recovery booting issue? i tried also your q201_64 tree (with my kernel and recovery files) but without success.
Did you compile it with 5.1 or 7.1 branch?

Thanks, i did it everything many days before i found this thread, and i tried obviously also with your device tree... twrp never booted i asked just because i read here your message and i'm having the same issues:
"So, Beelink just released an official (non-beta) Nougat firmware for the GT1 (GT1_702N0). I'd hoped to start custom ROM development on this firmware, but was surprised to find that it wouldn't boot to my current TWRP recovery. The bootloader displays the splash logo, then just hangs.

Frankly, this really surprised me, since the Amlogic recovery includes its own kernel. The hardware is unchanged, so the only thing that's changed in the code path is the bootloader.

Anyone have an idea why the Android 7.1 bootloader might not boot to a TWRP recovery partition that worked in Android 6.0.1 with the same hardware?

(I rebuilt TWRP for AMD64 using twrp-7.1 branch and new OEM recovery kernel, and that had no effect. Still hangs after splash logo.)"
So it was a Display Sync issue? I don't think so because is simply freezed, but i can try different systemcontrol if this is the case .

I compiled with 5.1, just like I described in the README.md. With these Nougat builds, you've got to carry over the kernel from stock recovery, since they're often dependent on the device tree partition and don't include the dtb as a 2nd stage bootloader.

The one big gotcha I had with the q201_64 and q20x builds was a display sync problem when using the newer versions of systemcontrol. I had to revert to an earlier version to the display to behave. Other than that, I just used the system I described here: http://freaktab.com/node/676576