Amlogic S905x stuck on flashing logo screen - Android TV General

Hi there all, I have an old Android TV box which when powered up gets to the logo screen but doesn't load/boot, I have tried the reset button but it doesn't take me to the options menu or reboot the system..I have the correct .img file with firmware of the the device and I have tried unsuccessfully to flash it using Amlogic USB Burner via double male USB cable connecting the box and pc..I have also burnt the .Img file with firmware onto and SD card which was then plugged directly into the box..neither method has worked..I have faithfully followed the instructions for both methods and the software for USB burning and SD card burning are Amlogic tools...so fully compatible as the Android Box is Amlogic also...any help would be appreciated.

Related

[Q] opad p10 cant boot

hello i have opad p10 oem version of advent vega after some market application install first my desktop window gone then i tried to restart in recovery mode but tablet is no screen cant inter in cwm only white circle with andriod robot with in upear micro second and gone pleas help i cant connect with my pc because usb problem any method to boot or flash with sdcard i have some knowledg about linux and lablet install 3.2 9n1 thanks sorry for my bad english
As far as i am aware the only way out is to reflash the stock firmware, without usb your a bit stuck. what is the problem with the usb connection?
i am trying 3 systems xp w7-64 w7-32 all are device not recognized error in device maneger is yellow mark unknown device
You need to install the usb recovery drivers. They are on the advent/pov websites. I assume there the same as your tab.
i cant access my tablet because i have usb not recognized error i want any alternat method to flash my tablet rom like sd card or usb drive thanks
no one solved my problem any idea if i use usb to serial cable or usb to lpt cable
You need to sort the usb driver issue. That will solve your problem. As far as i am aware flashing the stock rom with any other cable is not possible.
finaly i found a pc i install a nvidia driver audi sign green but run moddedstock its showing error nvflash uid read failed what this error and some time nvflash runing but blank screen nothing hapen
every time connect to pc masseg appear this device perform faster but connect to usb 1.1 and every time flash hang betwen system.img copying last file why is connect slow speed not full usb 2 speed there is cable problem or some thing else or driver problem ihave tried vega flash and modded stock v2 any help to try with linux ubuntu pleas help me thanks
any help to flash only system.img or only flash cwm to boot into cwm and then install modded rom in to opad
Can you boot in recovery mode?
SGS2-i9100; SGS3-i9300; Archos 101 Turbo (G9/250gb/512mb)

RK3188 9 inch with touch and usb and without cardreader soft brick

Suddenly hangs at Android logo, if i try to get it in recovery mode, its just flashing recovery 7.1.1 in the corner.
Got the firmware from the aliexpress seller and extracted the IMG file to a usb stick and put it in the usb cable of the headunit but i Will NOT read it. And there is not a sd card reader in this unit.
Can i connect it to my pc and Update or What Can i Do ?

Z17 Lite won't boot after v1.05 ROM update

Hello,
After rooting the system I tried to upgrade the stock firmware.
I probably did something wrong because now the device won't boot.
At startup it shows the "Nubia... Powered by android" screen and does not continue with the boot process.
I still have access to TWRP so I tried to wipe everything and to install the ROM from TWRP.
It looks as if the ROM is installed correctly, but it requires reboot and after reboot the same "Nubia... Powered by android" screen comes up.
I also tried the emergency recovery but that installs only from external sd card (that the Z17 lite does not have), or from OTG device. I connected a USB thumb drive with OTG cable but it doesn't recognize it
At this point I have no idea what else to do.
I'd be happy for any assistance.
TIA
yaccri said:
Hello,
After rooting the system I tried to upgrade the stock firmware.
I probably did something wrong because now the device won't boot.
At startup it shows the "Nubia... Powered by android" screen and does not continue with the boot process.
I still have access to TWRP so I tried to wipe everything and to install the ROM from TWRP.
It looks as if the ROM is installed correctly, but it requires reboot and after reboot the same "Nubia... Powered by android" screen comes up.
I also tried the emergency recovery but that installs only from external sd card (that the Z17 lite does not have), or from OTG device. I connected a USB thumb drive with OTG cable but it doesn't recognize it
At this point I have no idea what else to do.
I'd be happy for any assistance.
TIA
Click to expand...
Click to collapse
UPDATE: I tried different USB drives. One of them mounted. I found that this one was formatted in FAT. Since this is a small 2Gb drive that cannot hold the ROM, I found another drive that was formatted in ExFAT that also loaded correctly.
I loaded the ROM as suggested and now the phone is working again.
My guess is that the phone can't read NTFS file format in emergency recovery mode.

Nvidia Shield 2017 Issues

HEllo, the screen on tv saz data can not be checked i shall loock the bootloader, iv done this but it does not help, when i boot into recovery, i then put the usb cable to the pc, but there is no reaction from the pc, the pc does not see any new device, what i can do

Unbrick Vontar V6 TV Box – Help needed

Hello! I was wondering if someone could give me a hand. I have researched and tried several things to unbrick my TV box but no luck so far. I was using PhoenixSuit to flash a firmware to my Vontar V6 (H616) box and during the process Windows crashed. After the PC reboot, I noticed Windows 10 recognize the TV box (Device Manager) as Universal Serial Bus controllers -> USB Device (VID_1f3a_PID_efe8) but PhoenixSuit is unable to recognize it again as a device. I tried also flashing the firmware via PhoenixCard as well as accessing the box via adb and fastboot but no luck at all. Based on what I have researched, I believe the bootloader of the box is damaged. So any help or guidance to fix it would be mega appreciated. Thanks in advance, Marcello.

Categories

Resources