Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

X96 Air Amlogic S905X3 Android 9.0 Media Player

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • gatos814
    replied
    99,99999999% of the difficulty is to find the proper pins for shorting them...!
    Especially in these pcb with no ''optical'' pins of the eMMC !
    After that , with one way or the other , in 1 minute , 1 hour , 1 day or one week you will have your device again ... functional !


    Leave a comment:


  • ath156
    replied
    Originally posted by RiCkLaR_atvX View Post
    Your Logic is wrong, it doesn't matter what the device is doing, it doesn't matter at what state of boot the device is bricked in, it doesn't matter if the device is booting-up/loading, because you are not faster than a bootloader operation to try to physically time an interruption of the boot sequence, that is just not possible. Even if the device is currently running android perfectly when you engage MaskROM mode, it will happen with your Amlogic device if it is getting steady power over USB-cable/OTG-port When you Short-The-Pins and the key is you have to short the Correct Pins then it will Reset the device to be in the Proper state to communicate to a PC to install a firmware.
    Don't you understand that it is your "Logic" that kept gatos814 from reviving his box ??
    If he was still following your way (as the only correct procedure) probably he was going to still be trying to bring back his box to life. Please read carefully his last 2 posts.
    Also what are you meaning by "you are not faster than a bootloader operation to try to physically time an interruption of the boot sequence"???? But that's exactly the point of 1st shorting the pins and only then connecting the Cable to the box (which must be previously completely out of power for some time -no "residual" current). You don't have to be fast at all !!! You do not give it a chance at all as you immediately lead it to "reset state" asking for the proper parameters and therefore loading your rom from UBT.
    Also from the beginning I said that what I suggest is for me the primary/main method (not the only one). At the end it doesn't matter what you say or what I say but what actually revives our box. So if I have such a case I will try my method, your method or any other sequence/combination (without power adapter, with the additional help of power adapter etc).
    Best regards.

    Leave a comment:


  • RiCkLaR_atvX
    replied
    Originally posted by ath156 View Post
    Allow me to insist that at step 6 usually it is best practice to first short pins and only then connect USB cable. This way the relevant NAND chip instead of loading the usual parameters (and probably enganging in a loop - when it is bricked or semi-bricked) it is forced to look for new parameters immediately so as to be able to function. The whole purpous is to "initialize"/"reset" it before being able to load anything else.
    Your Logic is wrong, it doesn't matter what the device is doing, it doesn't matter at what state of boot the device is bricked in, it doesn't matter if the device is booting-up/loading, because you are not faster than a bootloader operation to try to physically time an interruption of the boot sequence, that is just not possible. Even if the device is currently running android perfectly when you engage MaskROM mode, it will happen with your Amlogic device if it is getting steady power over USB-cable/OTG-port When you Short-The-Pins and the key is you have to short the Correct Pins then it will Reset the device to be in the Proper state to communicate to a PC to install a firmware.

    Leave a comment:


  • gatos814
    replied
    The thing that i was missing here as i said was that the tv box was not full bricked ...
    And what that means...
    Means that it wanted other approaching than the standard way ...
    The standard way on a full bricked device is first the cable and after the pins ...
    But in my case for opening the reset ''portal'' i should have done this first (as and i finally did this !)
    And that's because i should have intervened before the pcb gets power from the usb cable!
    Of course and you must do all the things you both mentioned but the critical here ALWAYS is to use a multimeter to make an approach AND FIND the right pins to short !
    Or of course to search and find if and others have found the solution...!
    Regards

    Leave a comment:


  • ath156
    replied
    Originally posted by RiCkLaR_atvX View Post
    No, incorrect. The correct way to short the pins is have USB-OTG-port connected to computer well shorting the pins. This way you know when you have reset the NAND chip immediately on shorting-the-pins. Problems usually arrives because the user is not using the correct USB-port which is not the OTG-port of their device. For this X96air the OTG-port is the USB3.0-port, most other devices use a USB2.0-port, this is why it is important to research your exact device specifications before trying anything.

    Example:
    1) Know your device before starting, know which port is USB-OTG, if not marked do research or contact Manufacturer/Vendor
    2) Start Windows PC
    3) Start USB Burning Tool (hopefully you have the latest version installed in PC, if not search for update)
    4) Load correct firmware into Tool, if device is bricked then use an original factory firmware to restore before trying a custom ROM
    5) Click Start in Tool
    6) Attach USB-to-USB cable betweeen PC and Amlogic device
    7) Short the Pins, if device has Red/Blue LED usually will switch Red to Blue(generally signals standby to operational mode); if no LED then watch and listen to PC to signal Connected Device chyme, because Tool is already engaged "Start" it will Start the Burning Process immediately after correct Pin-Short, if it stalls click "Refresh" in Tool to continue. If Tool+Firmware continues to fail the install then you probably have incorrect firmware. Or, possible your device needs DC-Power supply connected to install firmware fully during burn process, not the case for X96air.
    I obviously agree with you that in some boxes you have to use USB 2.0 and in others USB 3.0.
    I also agree for the steps 1 to 5. Allow me to insist that at step 6 usually it is best practice to first short pins and only then connect USB cable. This way the relevant NAND chip instead of loading the usual parameters (and probably enganging in a loop - when it is bricked or semi-bricked) it is forced to look for new parameters immediately so as to be able to function. The whole purpous is to "initialize"/"reset" it before being able to load anything else.
    Anyway as you can see this is the problem gatos814 faced and you can clearly see that he solved it the way I am supporting as primary/usual method.
    On the other hand it may be that certain boxes/chips require a different approach OR most probably that at some cases you can achieve the same purpous in either way!!!

    Leave a comment:


  • RiCkLaR_atvX
    replied
    Originally posted by ath156 View Post
    Shorting first the pins and only then connecting USB cable is the standard procedure.
    No, incorrect. The correct way to short the pins is have USB-OTG-port connected to computer well shorting the pins. This way you know when you have reset the NAND chip immediately on shorting-the-pins. Problems usually arrives because the user is not using the correct USB-port which is not the OTG-port of their device. For this X96air the OTG-port is the USB3.0-port, most other devices use a USB2.0-port, this is why it is important to research your exact device specifications before trying anything.

    Example:
    1) Know your device before starting, know which port is USB-OTG, if not marked do research or contact Manufacturer/Vendor
    2) Start Windows PC
    3) Start USB Burning Tool (hopefully you have the latest version installed in PC, if not search for update)
    4) Load correct firmware into Tool, if device is bricked then use an original factory firmware to restore before trying a custom ROM
    5) Click Start in Tool
    6) Attach USB-to-USB cable betweeen PC and Amlogic device
    7) Short the Pins, if device has Red/Blue LED usually will switch Red to Blue(generally signals standby to operational mode); if no LED then watch and listen to PC to signal Connected Device chyme, because Tool is already engaged "Start" it will Start the Burning Process immediately after correct Pin-Short, if it stalls click "Refresh" in Tool to continue. If Tool+Firmware continues to fail the install then you probably have incorrect firmware. Or, possible your device needs DC-Power supply connected to install firmware fully during burn process, not the case for X96air.

    Leave a comment:


  • ath156
    replied
    Originally posted by gatos814 View Post

    Finally i figured out what was going on and bring my tv box again in life...!
    My tv box was not entirely ''dead''...
    It was on a boot loop and without recovery ...
    So every time i was putting first the usb to blue port the tv box was starting without getting anywhere ....!
    So , i first shorted the 2 pins and after i pluged the usb cable ....
    And ... boom!
    The tv box detected from my pc and everything went as it should!
    This might help and others with similar issues!
    In the photo below these are the 2 pins that worked in my case...
    This is not my board it's from 4pda and from a p1 board but these 2 pins did the job and in mine!
    Shorting first the pins and only then connecting USB cable is the standard procedure. Look also to a similar case here https://forum.freaktab.com/forum/tv-...ard-xyx_s905x3

    Leave a comment:


  • gatos814
    replied
    Originally posted by gatos814 View Post
    I have a p2 version x96 air with 100mb ethernet and i want someone to show me the short pins to bring that box in life again ...!
    What ever i found so far didn't worked!
    Thank you!
    Finally i figured out what was going on and bring my tv box again in life...!
    My tv box was not entirely ''dead''...
    It was on a boot loop and without recovery ...
    So every time i was putting first the usb to blue port the tv box was starting without getting anywhere ....!
    So , i first shorted the 2 pins and after i pluged the usb cable ....
    And ... boom!
    The tv box detected from my pc and everything went as it should!
    This might help and others with similar issues!
    In the photo below these are the 2 pins that worked in my case...
    This is not my board it's from 4pda and from a p1 board but these 2 pins did the job and in mine!
    Last edited by gatos814; 23 July 2020, 11:53.

    Leave a comment:


  • Satbeginner
    replied
    Originally posted by digitgr View Post
    ok now it's work.i will install the rom later .i forgot to ask you after install rom must install and the patch?thanks for your help
    Yes, the order of things is:

    Factory reset old ROM;
    reboot into TWRP;
    Install new ROM ;
    Reboot and let fully finish;
    Reboot into TWRP;
    Install patch for your box;
    Reboot and let finish;

    Enjoy.

    Leave a comment:


  • digitgr
    replied
    ok now it's work.i will install the rom later .i forgot to ask you after install rom must install and the patch?thanks for your help

    Leave a comment:


  • digitgr
    replied
    Originally posted by Satbeginner View Post

    Hi, I found the old link at 4PDA does not work anymore, probably something changed there.
    Use this one, it's from my Google Drive:

    https://drive.google.com/file/d/1BEM...ew?usp=sharing


    Leo
    thank you. i will try with this later thanks

    Leave a comment:


  • Satbeginner
    replied
    Originally posted by digitgr View Post

    where can i find this.the link above in post 137 is dead.only this TWRP-9.0-3.3.1-for-N5MAX-X3 .zip exist and not work for me.any way thanks for the answer
    Hi, I found the old link at 4PDA does not work anymore, probably something changed there.
    Use this one, it's from my Google Drive:

    https://drive.google.com/file/d/1BEM...ew?usp=sharing


    Leo
    Last edited by Satbeginner; 10 May 2020, 15:58. Reason: Typos

    Leave a comment:


  • digitgr
    replied
    Originally posted by Satbeginner View Post

    You must put the TWRP and ROM both as .zip files on the SD-card.
    SD card must be formatted as Fat32, works for me every time.

    I use TWRP331_AML_ViT.zip size is 14.084kB

    Good luck,

    Leo
    where can i find this.the link above in post 137 is dead.only this TWRP-9.0-3.3.1-for-N5MAX-X3 .zip exist and not work for me.any way thanks for the answer

    Leave a comment:


  • Satbeginner
    replied
    Originally posted by digitgr View Post
    I have installed the rom from post 103 and I want to try the rom from 4pda but I can't.I put the recovery and the rom zip on the sd card I enter the stock recovery I choose update from ext choose recovery img but nothing.error. what i am doing wrong?
    You must put the TWRP and ROM both as .zip files on the SD-card.
    SD card must be formatted as Fat32, works for me every time.

    I use TWRP331_AML_ViT.zip size is 14.084kB

    Good luck,

    Leo

    Leave a comment:


  • mrwislr
    replied
    Originally posted by digitgr View Post
    I have installed the rom from post 103 and I want to try the rom from 4pda but I can't.I put the recovery and the rom zip on the sd card I enter the stock recovery I choose update from ext choose recovery img but nothing.error. what i am doing wrong?
    I couldn't get any of the slimbox roms working but the images from lekha7777 work fine... using the usb burning tool

    There are ATV versions for all boxes



    Or Vanilla Android versions for P1, P2, V2



    Leave a comment:

Working...
X