Same on my u5x+s.
I tested that image with bootloader of v2ff. Atvx logo displayed but that's all.
Tanix TX9 Pro
-
- Expert Member
- Posts: 125
- Joined: Wed Oct 03, 2018 9:43 pm
- Has thanked: 15 times
- Been thanked: 4 times
Hi at this time the V2g DDR4LPDDR doesn't work on my TX9 pro.
it burn with out error but don't boot. like the trouble with [mention]onexzero[/mention] 's device mentionned at the adam's personnal rom post.
I think some one moved my post on this section.
- ricklar
- Moderator
- Posts: 889
- Joined: Fri Nov 30, 2018 10:30 pm
- Has thanked: 139 times
- Been thanked: 249 times
Try the v2g_A1_final.img - that device is suppose to be LPDDR3 also.
Only need to "Short the Pins" IF Boot Logo never shows ever, if you unplug and plug-in and at least the Boot Logo shows for several seconds then you are ok, even if screen then goes black, device Bootloader or DDR read file is incorrect; So you can just Burn again a different firmware image.papla83 wrote: ...and i think i will short cut the pin the burn it...
BE KIND, BE NICE, BE RESPECTFUL TO OTHERS, RESPECT THE MODERATORS,
*IMPORTANT NOTE* ONLY PM MODERATORS OR DEVELOPERS AS A LAST RESORT!!!
My test device: H96 Pro+ 3gb/32gb DDR4 Plus own Tanix, Beelink, Alfawise, X96S, Odroid-N2, Khadas VIM3L, X3, ADT-3, X96-Air
GEARBEST.com
PLEASE ENJOY ATVX!
*IMPORTANT NOTE* ONLY PM MODERATORS OR DEVELOPERS AS A LAST RESORT!!!
My test device: H96 Pro+ 3gb/32gb DDR4 Plus own Tanix, Beelink, Alfawise, X96S, Odroid-N2, Khadas VIM3L, X3, ADT-3, X96-Air
GEARBEST.com
PLEASE ENJOY ATVX!
-
- Expert Member
- Posts: 125
- Joined: Wed Oct 03, 2018 9:43 pm
- Has thanked: 15 times
- Been thanked: 4 times
Hi and thanks, unfortunally the A1 version doesn't burn correctly...ricklar wrote: ↑Fri Jan 11, 2019 2:55 amTry the v2g_A1_final.img - that device is suppose to be LPDDR3 also.
Only need to "Short the Pins" IF Boot Logo never shows ever, if you unplug and plug-in and at least the Boot Logo shows for several seconds then you are ok, even if screen then goes black, device Bootloader or DDR read file is incorrect; So you can just Burn again a different firmware image.papla83 wrote: ...and i think i will short cut the pin the burn it...
- ricklar
- Moderator
- Posts: 889
- Joined: Fri Nov 30, 2018 10:30 pm
- Has thanked: 139 times
- Been thanked: 249 times
[mention]papla83[/mention] sorry to hear. Only solution is to repackage the firmware with different UBOOT files to your specific ram MHz device, a standard AtvX img most likely wont work for you.
To unpack stock firmware and pull out the files you need Amlogic CustomizationTool. The Ram and Bootloader need to match for firmware to be usable. The stock files to pull from stock firmware:
Most Simple solution I could recommend is to Flash stock firmware,
Check both Erase All and Erase Bootloader on stock install,
Then plug into TV make sure box is working with stock img then unplug,
Load AtvX LPDDR into Burning Tool,
Only check Erase All,
Not check erase bootloader, that will keep stock Bootloader in place.
Burn img and see if it works.
Erasing stock bootloader causes issues for boxes not tested by developers of ROM, so a full Burning will use built-in AtvX firmware files "UBOOT" and "bootloader" which may change the RAM MHz speed value too high or too low which will cause box not to boot.
To unpack stock firmware and pull out the files you need Amlogic CustomizationTool. The Ram and Bootloader need to match for firmware to be usable. The stock files to pull from stock firmware:
Code: Select all
aml_sdc_burn.UBOOT
UBOOT.USB
bootloader.PARTITION
DDR.USB
Check both Erase All and Erase Bootloader on stock install,
Then plug into TV make sure box is working with stock img then unplug,
Load AtvX LPDDR into Burning Tool,
Only check Erase All,
Not check erase bootloader, that will keep stock Bootloader in place.
Burn img and see if it works.
Erasing stock bootloader causes issues for boxes not tested by developers of ROM, so a full Burning will use built-in AtvX firmware files "UBOOT" and "bootloader" which may change the RAM MHz speed value too high or too low which will cause box not to boot.
BE KIND, BE NICE, BE RESPECTFUL TO OTHERS, RESPECT THE MODERATORS,
*IMPORTANT NOTE* ONLY PM MODERATORS OR DEVELOPERS AS A LAST RESORT!!!
My test device: H96 Pro+ 3gb/32gb DDR4 Plus own Tanix, Beelink, Alfawise, X96S, Odroid-N2, Khadas VIM3L, X3, ADT-3, X96-Air
GEARBEST.com
PLEASE ENJOY ATVX!
*IMPORTANT NOTE* ONLY PM MODERATORS OR DEVELOPERS AS A LAST RESORT!!!
My test device: H96 Pro+ 3gb/32gb DDR4 Plus own Tanix, Beelink, Alfawise, X96S, Odroid-N2, Khadas VIM3L, X3, ADT-3, X96-Air
GEARBEST.com
PLEASE ENJOY ATVX!
-
- Expert Member
- Posts: 125
- Joined: Wed Oct 03, 2018 9:43 pm
- Has thanked: 15 times
- Been thanked: 4 times
i have ATVX logo but stuck on it ... it's a great news lol.ricklar wrote: ↑Sun Jan 13, 2019 8:27 am [mention]papla83[/mention] sorry to hear. Only solution is to repackage the firmware with different UBOOT files to your specific ram MHz device, AtvX most likely wont work for you.
To unpack stock firmware and pull out the files you need Amlogic CustomizationTool. The Ram and Bootloader need to match for firmware to be usable. The stock files to pull from stock firmware:Most Simple solution I could recommend is to Flash stock firmware,Code: Select all
aml_sdc_burn.UBOOT UBOOT.USB bootloader.PARTITION
Check both Erase All and Erase Bootloader on stock install,
Then plug in TV make sure box is working then unplug,
Load AtvX LPDDR into Burning Tool,
Only check Erase All,
Not check erase bootloader, that will keep stock Bootloader in place.
Burn img and see if it works.
Erasing stock bootloader causes issues for boxes not tested by developers of ROM, so Burning will use built-in AtvX firmware files "UBOOT" and "bootloader" which may change the RAM MHz speed value too high or too low which will cause box not to boot.
I burned first a non nexus rom in 7.1.2 for Tx9 pro and after try to burned ATVX V2G then i stuck on ATVxperience logo.
-
- Expert Member
- Posts: 125
- Joined: Wed Oct 03, 2018 9:43 pm
- Has thanked: 15 times
- Been thanked: 4 times
the difference betwen the full install and the install with only erase all checked is :
it's displaying something on screen ( great )
i can burn it after by the reset button.
common with V2g full install is nothing on the front panel ( no boot , no hours, )
it's displaying something on screen ( great )
i can burn it after by the reset button.
common with V2g full install is nothing on the front panel ( no boot , no hours, )