[ROM] XTMOD-ATV X96 Max - GT1 and some U211 devices - S905X2 Android 8.1 [Android TV]

[raruba]

Yes i tried.

Use the USB burning tool v2.1.7.1, load the rom and then hit the start button. Hold down the reset button on box, while holding, plug in the USB cable from computer to the USB port on box and then plug in the power cord also while still holding reset on box and wait for connect sound on computer, then let go of reset on box.....should work......this box takes extra power for some reason.

[Prins_007]

During the burn card maker process, did you select all erase eeprom options.
I'd try a couple more times using these options.

Yes i tried.

[resansid]

Hi Friend,

I tried what you wrote and unfortunately it didn't work. I think that the ATX firmware did something with my box. :-( it look likes it's locked. Pin Short Cut doens't work also.

During the burn card maker process, did you select all erase eeprom options.
I'd try a couple more times using these options.

[Prins_007]

Sorry for late reply, I used burn card maker V2.02 and the image I used to create sd card was X96Max_V311_4G_8.1_20190625.img.
I think the important point is the reset switch has to be connected fully until the partition error and beyond during flash so keep it connected all the way until box update via sd card.
Please update us on your trial using these steps. Hope this helps.

Hi Friend,

I tried what you wrote and unfortunately it didn't work. I think that the ATX firmware did something with my box. :-( it look likes it's locked. Pin Short Cut doens't work also.

[raruba]

Some of the earlier versions worked on X96 max but you loose the clock display and I could never tell if the box is ON or OFF. So I personally went back to using X96 based ROMs only.

Hey thanks, and I agree with you about loosing the clock display...I need to know if my box is on for sure.

[resansid]

Does the GT1 mini 95X2 version work on the X96 Max 4g 64g box????

Some of the earlier versions worked on X96 max but you loose the clock display and I could never tell if the box is ON or OFF. So I personally went back to using X96 based ROMs only.

[resansid]

Hi friend,

Thank you, kan you tel me wich files you have put in the SD card to recover and where i can find the files? May be this will help. Then i can try the steps you mention abo e :-)

Sorry for late reply, I used burn card maker V2.02 and the image I used to create sd card was X96Max_V311_4G_8.1_20190625.img.
I think the important point is the reset switch has to be connected fully until the partition error and beyond during flash so keep it connected all the way until box update via sd card.
Please update us on your trial using these steps. Hope this helps.

[raruba]

Finally, we recently upgraded the firmware for GT-King and GT1 mini, and the GT1 mini 95X2 version can now be upgraded to Android 9.0. For details, please see the link below:

https://forum.freaktab.com/forum/tv-...ards-announced

Does the GT1 mini 95X2 version work on the X96 Max 4g 64g box????

[Prins_007]

Had a similar issue when I tried updating to Android_P Rom and everytime it would crash with some "partition error". I think the switch pressing using a toothpick was no longer working.
I work in an Electronic Mfg industry so I asked one of the solder lady to run external wires connecting to switch. I then connected them and then booted up the Box with burn card created sd card with the image and volla the box started in update mode and successfully recovered.
I also was able to update to Android P 07/22/2019 ROM using USB burning tool 2.1.7 later on. I tucked the two wires underneath the box using a tape so they are well hidden and can be used in future. Hope this encourages you to try additional steps and recover the dead box. Don't loose hope yet. Goodluck

Hi friend,

Thank you, kan you tel me wich files you have put in the SD card to recover and where i can find the files? May be this will help. Then i can try the steps you mention abo e :-)

[resansid]

Hi,

Thank you for your help.
Always get the AML dtb issue. I don't know what the XTM_ATV_4_4.img did :-( It seems that the only firmware that get passed the AML issue is this firmware. All other firmwares get stuk. But the issue of the XTM_ATV_4_4.img firmware now is that one get stuk at Vendor check. 96%... and about the loop i waited sometimes 30min sometimes hours if i was busy, the box stays on.

Had a similar issue when I tried updating to Android_P Rom and everytime it would crash with some "partition error". I think the switch pressing using a toothpick was no longer working.
I work in an Electronic Mfg industry so I asked one of the solder lady to run external wires connecting to switch. I then connected them and then booted up the Box with burn card created sd card with the image and volla the box started in update mode and successfully recovered.
I also was able to update to Android P 07/22/2019 ROM using USB burning tool 2.1.7 later on. I tucked the two wires underneath the box using a tape so they are well hidden and can be used in future. Hope this encourages you to try additional steps and recover the dead box. Don't loose hope yet. Goodluck

[Prins_007]

If you try to flash the original ROM, do you also always get the AML dtb error, or it flashes 100% but gets stuck at bootlogo?
I was wondering.. how long you waited at bootlogo before pulling the plug?
Sometimes it takes a longer time to move forward.

Enviado do meu POCOPHONE F1 atrav?s do Tapatalk

Hi,

Thank you for your help.
Always get the AML dtb issue. I don't know what the XTM_ATV_4_4.img did :-( It seems that the only firmware that get passed the AML issue is this firmware. All other firmwares get stuk. But the issue of the XTM_ATV_4_4.img firmware now is that one get stuk at Vendor check. 96%... and about the loop i waited sometimes 30min sometimes hours if i was busy, the box stays on.

[TheBlackening]

Also tried today... The short nand or pin seems to do nothing specially. What i don't understand is why the only Rom who passed the aml_dtb is de XTM_ATV_4_4.img but with vendor issue. all other rom/firmware get stuck at aml_dtb....

Thank you for trying helping me :-) i appreciate.

If you try to flash the original ROM, do you also always get the AML dtb error, or it flashes 100% but gets stuck at bootlogo?
I was wondering.. how long you waited at bootlogo before pulling the plug?
Sometimes it takes a longer time to move forward.

Enviado do meu POCOPHONE F1 atrav?s do Tapatalk

[raruba]

version 5.5.0 took like 20s to unpack it, version 4.0.0 didn't unpack it aven after 12 hours. Version 6 is crashing..

I'm gonna try version 5.5 also and see what it does.....will keep you posted. You using a 64bit or32bit computer?

[Prins_007]

I wouldn't do the "Erase all"
In some cases, somehow the box loses the wifi MAC address.

I would recommend doing the short NAND pin method.
I had a similar situation with a X96 Mini.
After installing the ROM from a W95, the only way I could install another ROM was through short NAND pin method.

I hope it helps
Cheers

Enviado do meu POCOPHONE F1 atrav?s do Tapatalk

Also tried today... The short nand or pin seems to do nothing specially. What i don't understand is why the only Rom who passed the aml_dtb is de XTM_ATV_4_4.img but with vendor issue. all other rom/firmware get stuck at aml_dtb....

Thank you for trying helping me :-) i appreciate.

[Prins_007]

Try 'Erase all' and check the 'Whether overwrite key'

Tried what you said today but the same as usual

Thank you for trying helping me :-) i appreciate.