TWRP for Amlogic devices.

[Ichijoe]

I dont mind starting from scratch and since there was no mouse I was screwed anyways. That said AND A BIG THANK YOU FOR RESPONDING SO FAST. Took a chance and reset device which I think cleared root file so mouse could work. Then used the file to root a G-Box Q and used root checker to confirm.

I wanted to do a bunch of stuff tonight but got caught on this for two hours. I am a newb that tries to dabble and getting it to work gives me a huge high. Thank you guys for this thread.

So yeah if this happens to you reset box and go forth and conquer.

Seiously thank you for responding I started freaking out then got it.

I think I may have found your "Problem"... The fact that I've never even heard of a G-Box Q, kinda leads me to the conclusion that your "Device" is sadly not supported.... Yet? Kinda reminds me of where I was ~ca October last Year when I tried to install the ENY8 version of TWRP (under some delusion), that it could've worked on my 1G/8G MXIII. Which not having not knowing any better left me in a softbricked state. Till I was able to reflash 109k4 though the USB BURNER TOOL. Sadly kinda defeating the purpose of wanting TWRP in the first place.

Now that the K200 version of TWRP is out... Still have to test it... I'm about 50% of the way there. (e.g. Having been successful at making a Backup), all that remains is to see if I can actually use this Image to recover my Device again.

Not knowing anything of your Device... Perhaps its still kinda new? I can't really understand why it wasn't already rooted at the Factory level. But, I gather that even the MXIII originally was locked at the start too. Thankfully this is no longer the case though.

The only advice I could try to offer you would be to try downloading, and installing whatever stock Firmware you need to. If you had really booked the Recovery Partition as badly as that. Then your probably are going to need something along the lines of a USB BURNER TOOL, and a PC to reflash a stock Firmware.

But, again I never even heard of the G-Box Q, assuming its anything like the MXQ then it'll likely be an S805 SoC, and so definitely incompatible with anything you'll find here. As these Recoveries were meant for the S802 SoC's.
So it looks like you have some work to do in trying to figure out exactly what it is that you have on your hands, and then how to recover it back again to a semblance of Stock.

Having kinda been there myself... (Only after having my MXIII for ~20 Minutes!!), I really do wish you the best of luck.

[litan1106]

They are standard android images. So split-bootimg.pl and gzip will do the trick, but i don't know if changing partitions mountpoints will make it backup.

I noticed there is 3 files with different partitions. twrp.fstab, recovery.fstab and fstab.amlogic

I made a few changes on the recovery.fstab and recreated the image file using the mkbootimg.

I flashed it but I couldn't see the twrp screen like the one you provide. Please help. I would like to know which file should I edit.

[litan1106]

They are standard android images. So split-bootimg.pl and gzip will do the trick, but i don't know if changing partitions mountpoints will make it backup.

I noticed there is 3 files with different partitions. twrp.fstab, recovery.fstab and fstab.amlogic

https://github.com/litan1106/mibox2-...d3d?diff=split
I made a few changes on the recovery.fstab and recreated the image file using the mkbootimg.

I flashed it but I couldn't see the twrp screen like the one you provide. Please help. I would like to know which file should I edit.

[vn800art]

Looking for a safe solution - Beelink MXIII Plus : TWRP Backup

Hello all and Abdul PT
Trying to put this device in TWRP recovery but I didn't succeed! It always boot from internal one .
I tried with recoverys for Minix devices ( Last two recommended ones in this thread ) no luck.
Changed two microsd I have, always worked with another device, Mxq S85.
As first, what is the way to understand if my reset button is working properly, as I find it to be triky more than others I have.
Second I attach here the original internal recovery and I remember the device spec:
MXIII Plus Amlogic S812
2gb internal, 8gb whole space ( available 5,26 after boot )
Board n200 from Netxeon, Mali 450MP Gpu - AP6335 dual band wifi
APi level 19 , rom KOT49H.20150114 , kernel 3.10.33
Looking for a recovery of the whole system before I make some mistake touching here and there !!!
Here is the link to original recovery extracted from what is reported to be the same rom found on Chinagadget review

https://drive.google.com/folderview?id=0B-5VVZWMc6mLb2s4azNMUk5IZDQ&usp=sharing

Thanks for Your interest !
Regards
Alessandro

[litan1106]

I noticed there is 3 files with different partitions. twrp.fstab, recovery.fstab and fstab.amlogic

https://github.com/litan1106/mibox2-...d3d?diff=split
I made a few changes on the recovery.fstab and recreated the image file using the mkbootimg.

I flashed it but I couldn't see the twrp screen like the one you provide. Please help. I would like to know which file should I edit.
[ATTACH=CONFIG]10820[/ATTACH][ATTACH=CONFIG]10821[/ATTACH][ATTACH=CONFIG]10822[/ATTACH]

What base and pagesize should I use to pack my img using the mkbootimg?

I tried it with 0x10000000

mkbootimg --kernel kernel.gz --ramdisk insecure_initramfs.cpio.gz --base 0x20000000 --pagesize 2048
--cmdline 'no_console_suspend=1' -o insecure_boot.img

[abdul_pt]

Hello all and Abdul PT
Trying to put this device in TWRP recovery but I didn't succeed! It always boot from internal one .
I tried with recoverys for Minix devices ( Last two recommended ones in this thread ) no luck.
Changed two microsd I have, always worked with another device, Mxq S85.
As first, what is the way to understand if my reset button is working properly, as I find it to be triky more than others I have.
Second I attach here the original internal recovery and I remember the device spec:
MXIII Plus Amlogic S812
2gb internal, 8gb whole space ( available 5,26 after boot )
Board n200 from Netxeon, Mali 450MP Gpu - AP6335 dual band wifi
APi level 19 , rom KOT49H.20150114 , kernel 3.10.33
Looking for a recovery of the whole system before I make some mistake touching here and there !!![emoji14]
Here is the link to original recovery extracted from what is reported to be the same rom found on Chinagadget review

https://drive.google.com/folderview?id=0B-5VVZWMc6mLb2s4azNMUk5IZDQ&usp=sharing

Thanks for Your interest !
Regards
Alessandro

I will give you a link later today for you to test.


Tapatalked

[abdul_pt]

What base and pagesize should I use to pack my img using the mkbootimg?

I tried it with 0x10000000

mkbootimg --kernel kernel.gz --ramdisk insecure_initramfs.cpio.gz --base 0x20000000 --pagesize 2048
--cmdline 'no_console_suspend=1' -o insecure_boot.img

Edit TWRP.fstab

I don't pass any arguments.

Tapatalked

[litan1106]

Edit TWRP.fstab

I don't pass any arguments.

Tapatalked

Thanks, I used unmkbootimage to unpack your (mibox2) image and mkbootimage without any arg to repack.
I flashed the repacked image but it didn't get to the teamwin screen.

[vn800art]

Thanks

Quote
I will give you a link later today for you to test.


Tapatalked
Unquote


Thanks Abdul, will test and report , do not hurry!
Alessandro

[abdul_pt]

Quote
I will give you a link later today for you to test.


Tapatalked
Unquote


Thanks Abdul, will test and report , do not hurry!
Alessandro

Please test this image - https://www.freak-tab.de/abdul_pt/am..._Plus_S812.img

Try on SDcard. I expect that some partitions won't be available for backup like boot/recovery/logo.

[vn800art]

Sorry to be so Noobish, I have a Minix x7 flashed 10 times and tested almost 10 builds, more and more phones, over xda etc, but THE QUESTION IS : how I can tell if my hidden reset button is actually working? Every time I try only internal recovery is booting ( and I also have MXq s85, flashed and used Twrp from Daemonium in it, I am going to try his last build). Tried also in the two Usb ports, nothing different!

Inviato dal mio Nexus 5 utilizzando Tapatalk

[abdul_pt]

There's two possibilities, or the HW button has a malfunction or it's not yet implement on bootloader since that is a new device and the vendor might not yet manage to do it.

You can 'dd' it to emmc, if it doesn't work just revert back to stock.

Tapatalked

[vn800art]

Sorry, I believe you must explode Your sentence:" 'dd' it to emmc", because this is out of my mind! Sorry to be so noobish!
Anyway, device is stock atm, wanted only to have a Nandroid backup of it

Inviato dal mio Nexus 5 utilizzando Tapatalk

[abdul_pt]

Copy the image to Internal SD
Open terminal window or adb shell and do
dd if=/path/to/image of=/dev/block/recovery
sync;sync
Now you can reboot to recovery to test

Tapatalked

[vn800art]

Thanks a lot, helpless without Your suggestion, will try asap!

Inviato dal mio Nexus 5 utilizzando Tapatalk