Wrong ROM and now now touch support - Android Q&A, Help & Troubleshooting

My YeahPad A13 tablet was hanging in boot process. That's why I flushed a ROM (with LifeSuite).
Now the tablet starts normally and the android screen is shown, but no touch action
If I connect with the PC the device is always connected as mass storage and ADB/Fastboot do not work.
This makes another flushing difficult... I also cannot boot in recovery mode as no key combnation works...
Any advice? Please

help
noone an idea or some suggestions? :crying:

Related

[Q] Can anyone help me to boot into DFU mode? [ZTE V817]

Hello. I'm new here. and not native speaker.
I'll try my best for English.
My device got soft bricked after I'm trying to install the new ROM.
Actually I had installed the ROM but It didn't appear anything.
Then I'd try to restore my backup to Its place.
It made my phone brick.
I can't boot into recovery mode, ROM and also FTM mode.
I must have an access to adb, If I want to boot into bootloader.
But I don't have any access to it at all!!.
I had read some post and I hope that DFU can help me.
But I don't know how can I boot into that mode.
And I had try hold volume + and - with and without power button but it still the same.
I had read that the DFU mode will display nothing but have the briefly red led.
I had accident plug the USB to device without battery.
And I got it, The briefly red led light with nothing change in the display (still nothing).
My computer recognizes it as a ZTE technology device. But It's in an unspecified device zone.
I had installed the ZTE USB device (My computer is MS Windows 8.1) and I had also installed it with unsigned driver mode too.
What could I do for getting it to work again?
Have I found the correct DFU mode?
My device is ZTE V817.
With MSM8225Q CPU and MSM7627A board platform specified in default.prop.

(android 4.0) wintouch q74 tablet bricked

i update my tablet with a liquid rom using default android recoverymode. the installation was succesful but when i reboot my tablet, logo appears as usual and get stack in blackscreen. i could still enter android recovery mode but it only reads internal storage so i cant update anymore, usb debugging was not turned on. how could i get it back to life/unbrick my tablet. (it is not rooted anyway.)
so i tried livesuit v1.09 and connect my tablet while in recovery mode, (the computer detects it as softwiner761) still livesuit doesnt start even if i already selected an img file. system upgrade says "no available device". then i just nomally boot my tab and the computer detects it as an unspecified android, still livesuit doesnt start any progress. turned off tablet doesnt do anything so what should i do?
from wintouch site ive downloaded the the img and downloaded the latest livesuit.
fastboot devices doesnt work too. i have no more idea how could i unbrick this tablet. please help me how could i repair this.:crying:
please help me :crying: :crying: :crying:

[Q] Flashed Pi****u on Android device, now its in bootloop

Hello,
Edit: First off sorry about the title it Pic Untu without the space I didn't realize it until I posted the question.
I have an android tv box. Model name is cs968 and it has RockChip rk3188, its rooted and i had cwm as recovery.
The device is also mentioned in this thread : http://forum.xda-developers.com/showthread.php?t=2457778
I wanted to use a linux distro on it and came across a distro named Pic Untu ; (its not written separately but its getting censored otherwise same with the link below you have to delete the space between 'pic' and 'untu' sorry about that )
http://ubuntu.g8.net/index.php/14-sample-data-articles/86-pic untu-4-5-nand-released
Now I have successfully flashed it without having any problems. But it had no support for built-in wifi or bluetooth so i turned it off as you would a desktop computer ("shut down" from the start menu) and moved it close to a place where i can connect it to ethernet to see if ethernet works. But when I started the device again it stuck in boot loop.
The device is not recognized from windows or linux from adb (but it used to, I've flashed a custom ROM with rkbatchtool from windows, and could connect the device from ubuntu with adb). Also i cant flash it again from a flash drive or sdcard ( although it says it recognizes a usb device or an sd card when booting up).
The only other response i get from the device is that when i press and hold the reset button, it resets and stops booting with an empty screen( this would go to CWM when android was installed)
Last thing is, I have 2 of these devices one of them is untouched so if that helps i can maybe do a nandroid backup and flash it once the adb is working or something similar maybe.
I'm not sure what I can do at this point so any help/pointers is appreciated.
Thank You.

[help] Lenovo S6000L bricked (?)

Some wanker had posted wrong images for boot and recovery for S6000L. And since I'm a moron, i didn't take the files apart to check them.
Installing them bricked my tablet. So essentially I have no boot or recovery images on the device and was wondering if there's any way to revive it.
Tablet freezes if i start it in normal, fastboot or recovery modes, so that's out of the picture.
However, i think that "meta mode" still works (if indication of it working is displaying lenovo logo and having "meta mode" written on the bottom of the screen)
It's getting detected on "mediatek preloader usb vcom port" for a couple of seconds when connected to the PC, which means that i might be able to use adb to push a backup into the tablet (?)
Been scouring the internet for a while with no results. Is there, by any chance, anyone who can help me out?

[Help] x96Air v2 stuck on logo

Hi , my x96Air v2, 4/32 is stuck on logo and i cant access recovery mode to do a hard reset , is there any solution ?
and can anyone help me please.
PS i can flash roms using the sd card or Amlogic usb burning tool.
I also have an X96Air, 4/32....
After flasching my Image nothing happens on startup.
It takes a while until the logo appears. This is when the device comes to the emergency upload mode. This is the moment where the device becomes recognized by the usb burning tool from amlogic. (when drivers are correctly installed)
Be patient... after fail boots my device always comes back to an emergency upload mode after some time.
Stil searching the Backup of the Device with AM7256 Wifi chip. Have you this Backup?
rogi1 said:
I also have an X96Air, 4/32....
After flasching my Image nothing happens on startup.
It takes a while until the logo appears. This is when the device comes to the emergency upload mode. This is the moment where the device becomes recognized by the usb burning tool from amlogic. (when drivers are correctly installed)
Be patient... after fail boots my device always comes back to an emergency upload mode after some time.
Stil searching the Backup of the Device with AM7256 Wifi chip. Have you this Backup?
Click to expand...
Click to collapse
no i don't have it sorry

Categories

Resources