[Q] Failed flashing - stuck at USB Logo - Android Q&A, Help & Troubleshooting

Hi,
I have an ASUS Fonepad 7 K012 (FE7010CG) and I mistakenly flashed an official ASUS firmware for the FE170CG
After this, the tablet won't boot and is only showing the USB logo with a red / white bar below it. If I try to connect it to my (Windows 8.1) computer, it tries to connect (keep hearing the connecting/disconnecting) sounds all the time) and only recognizes a "CLOVERVIEW" device for which no drivers are found, but it also does not remain connected, it just keeps appearing and disappearing from the device manager...
I have found some posts about getting out of this, but none for this device and only when the device actually remains connected... On top of this, I now looked in ASUS for a correct firmware, and none is available for this model
Is there any hope of doing something myself or will I have to send it for a (costly?) repair?
Thanks,
José

same problem here bro, i downloaded firmware from asus site, but found out that the problem was the firmware itself coz i tried to extract rar file and it has many errors upon extracting the firmware, hope somebody will find a solution....

Related

[Q] MK808B don't boot

Hi
I have a problem with my google tv , MK808B
It doesn't boot
I have black screen after "android"
It seem to be a real one, not a fake, I open it and see it on another site, with pictures from the real and the fake
I try to flash another firmware, but I can't put it in flash mode, when I press reste button and connect to usb from otg to my pc, my pc doesn't detect mk800b
I try on differents pc
Sorry for my english, I prefer try by myself, I think it is better than google tradcution (perhaps not ?)
Up
Hi there, I got that problem as well when I first got it. Mine just stucks at the "android" logo screen forever. I panic and look up online. Apparently if you be able to flash different rom then the stock one, it should work fine like in my case. First connect your device to the computer under flash mode. So when you download the firmware zip file, unzip and you file the driver for your device "\Rockchip_Batch_Tool_v1.5\Rockchip_Batch_Tool_v1.5\RockusbDrive" it will depend on your computer to be 32 or 64bit to choose the right driver. Next go to your device manager, scan one more time for new device and update the driver from the directory above. If you install the driver properly the computer will recognize your device with no hiccup. Hope this help cause I solve my problem through this step as well.
Old threat but......
There is something around google with the nandchip pin 8 & 9. I rote something after search for mk808b firmware. Sorry for the bad help.
Kis Plus Ersatzhandy

Q Tab 850: Dead/Not Recognized By windows 7

My q Tab 850 is dead and is not recognized by windows 7
Hi Experts,
I have QTab 850 (qmobile) and it is dead now.
from few days it was giving me Phone service stopped, the I decide to update its firmware and I read on internet to use SP_FLASH_TOOL. Form some site I have downloaded it firmware and tried to update its firmware using SP_FLASH_TOOL. After an hour with out no response then I removed the device but the result was its dead.
Now when I connect to USB , my PC shows notification USB Device Not Recognize and when I check in device manager it shows details as :This device is disabled because the firmware of the device did not give it the required resources. (Code 29).
I dont know what to do, is there any solution to recover my device

Ematic EGS-102 stuck on logo screen; computer doesn't see it when connected with USB

Hello,
I have a rooted Ematic EGS-102. Following some instructions to swap my internal sd with the external one (as the memory where the apps' data get downloaded to was only 500MBs), I believe I have typed something incorrectly inside the vold.fstab file, because after rebooting my tablet it's forever stuck on the logo screen. This is my first android tablet so please bear with me. The solution that comes to mind is to open the root files by some program on my PC and edit the vold.fstab file back (I even have a backed up version of it from a few weeks earlier), or even flash a new ROM. Now, the problem is, my computer cannot see my tablet when I connect it through USB. At all. Back before when the tablet was fine, I could use the USB to transfer files to and from my computer, but after I killed my tablet, my computer doesn't even make the sound which indicates that a USB device has been connected.
I have tried changing the USB cable and the port where I connect it to (never mind that the same cable and port work with other devices), to no avail. Having given up on the USB method working, I decided to follow some instructions on installing a custom ROM that has worked on EGS-004, and according to the one who posted that, would work on other variants such as EGS-102. Basically It was steps to installing the ROM from the external card through Recovery mode, which I followed thoroughly to no avail. The tablet still gets stuck on the "ematic" logo start screen.
I've noticed that in the Device Manager my tablet is displayed as "USB Device(VID_1f3a_PID_efe8)" with a yellow triangle mark indicating that it's not working properly (code 10). I tried searching that error code and trying all the solutions I found to no avail, including updating the driver (just refuses to update and keeps telling me that my driver is up to date.)
Sadly all the other methods that would have a decent shot at working (Root explorer on PC, android recovery program, even a flash EGS-004 firmware method on ematic's website) requires USB. I'm out of solutions, and unless I can get the USB to work somehow, or find out why the ROM method didn't work, my tablet would officially be dead. I'm utterly miserable that such a stupid mistake on my part ruined my tablet, and I have no way of buying another (broke student here) or returning it (out of warranty and I'm pretty sure I voided it anyway). I would absolutely appreciate any help, and thanks in advance.
Edit: It's stuck on logo screen, not a bootloop. I'm terribly sorry for this confusion, my head isn't straight right now.
Still haven't found a solution :/

Lossing usb connectivity after firmware update in fe170cg

Hi
my fe170cg(k012) was soft bricked..so i downgraded it to v4.3,then I download update files from asus website and updated firmware to 4.4 manuelli In the following
I kept update it to v.5 with ota this time after downloading completed My tab restart to install firmware but it takes much time & i was scared so i turned of tab during installing new firmware & then turned it on & firmware was installed,,
but problem start here,I cant connet my tab to pc via usb(MTP OR SYNC)..i tried pc link also installing usb drivers & adbs manuelli but pc cant even recognize it also i tried 2 other pc but the same.
Its a problem for many users but not solved...please help me I'M FROM IRAN and the asus official service center is weak alitle HERE SO i got to sent it to capital about 2000km away
please help me

Need help with a truly bricked Galaxy S ii

Hi everyone,
I have an SII GT- I9100 that I installed a custom ROM on a while back (probably 2 years ago). After a while it got badly bricked I don't remember what happened, and not only that
the charging port was also messed up so I couldn't connect it to my pc (pc wouldn't recognize it unless I held the cable in with force, but even that didn't work after some time).
It's been sitting on a shelf for about a year and I decided to buy a new charging port, replace it, unbrick it and give it to my mom.
I did replace it and I can connect it to my pc now but there's still issues. On my main windows 10 pc it gives me an error "USB device not recognized, the last USB device you connected to this computer malfunctioned, and Windows does not recognize it". (I've reinstalled usb drivers and troubleshooted with Kies).
I keep the phone in download mode while I am trying to connect it to my pc since I can't boot into anything (I have a yellow triangle and Samsung logo if I don't go into download mode).
On my laptop (win 7) I've managed to get windows to install all the drivers(even though it failed a couple times ?), I've also troubleshooted with Kies, still Kies can't connect to it.
I want to restore it to stock ROM but I haven't been successful. First Odin gave me "setup connection" error but then I rebooted the pc and it "worked".
Now it just says complete (write) operation failed.
I've tried 3 different Odin versions, nothing.
What bothers me is that Odin says "Added !" but everyone online to the people with similar issue says that they should reinstall drivers or talks about USB Debugging (which I can't turn on or off since it's bricked).
Sorry for the long post but what's the move here? Am I using a bad ROM ? I've tried one for the country I live in but not the country from which the phone is ( I don't know the country, might be Austria), could this be the issue ?
Thanks in advance!
Update, I may have found the right ROM, now it's stuck at boot.bin
EDIT: Found a youtube "solution" to that, then it got stuck at cache.img
EDIT: Getting Driver issues again, Unknown Device :/

Categories

Resources