My new HD10 tablet will not power on after I tried to downgrade it to 5.1.2 from what I believed was 5.1.4, but after hours of reading and tinkering I think it might have OTA to 5.3.1.0 without me realizing it.
Right now I cannot get the display to show anything at all. When i attach it to Windows 7 or Windows 10 PCs I have a device show up called "MT65XX Preloader" with no recognized drivers. I have downloaded and installed drivers for this but they are not being recognized for this device (disabled driver signing, told windows to install anyways, says successful but device manager still shows unknown device).
It appears for about 5 second then disappears for 5 and comes back repeatedly.
ADB and fastboot shows no devices being detected.
Does anyone have any suggestions on how I can recover from this? I'm going to setup a Ubuntu VM to see if Linux is any better with recognizing the device.
nockam said:
My new HD10 tablet will not power on after I tried to downgrade it to 5.1.2 from what I believed was 5.1.4, but after hours of reading and tinkering I think it might have OTA to 5.3.1.0 without me realizing it.
Right now I cannot get the display to show anything at all. When i attach it to Windows 7 or Windows 10 PCs I have a device show up called "MT65XX Preloader" with no recognized drivers. I have downloaded and installed drivers for this but they are not being recognized for this device (disabled driver signing, told windows to install anyways, says successful but device manager still shows unknown device).
It appears for about 5 second then disappears for 5 and comes back repeatedly.
ADB and fastboot shows no devices being detected.
Does anyone have any suggestions on how I can recover from this? I'm going to setup a Ubuntu VM to see if Linux is any better with recognizing the device.
Click to expand...
Click to collapse
If you can't boot into stock recovery there's nothing you can do to recovery it at this point. How new is it? Amazon has a 30 day no questions asked replacement policy. You can actually set it all up without even speaking to them usually. Plus they'll send you the new one right away and you have 30 days to return the broken one.
Related
Evening/afternoon/morning depending on where you are.
I managed to successfully unlock the boot loader and then root my Nexus 7 using the Wugfresh Nexus toolkit and installed the latest TWRP recovery. All was going great, I decided to flash a ROM, it went well but never booted into it. I went back into recovery and stupidly deleted/wiped more than I should and long story short I have a tablet with no OS and the SD card has been wiped so I cannot flash the rom.
I have been for the past several hours trying to get the device to appear as mass storage so I could push out the rom but I am not able to that. I can see the nexus 7 appearing as a Android device in Windows Device Manager with the driver exclamation mark. I have tried to install the driver for it from the SDK folder and also downloaded the drivers from ASUS (both are the same?) but the Driver Wizard keeps saying the driver cannot be found.
I can still get into bootloader and recovery, when I do go into TWRP recovery, I go to mount option and see the USB-OTG option but I cannot check the box next to. I'm thinking I will need to get a appropriate cable and get the rom onto the device that way but will have to wait for morning when the shops are open.
I still have hope as I do have the recovery image but need the advice of the learned people of this forum to help. I am using Windows 8 in case it makes any difference, can use win 7 if anyone thinks that will make a difference? When its in bootloader the tablet then appears as a Android Phone in Device manager.
Thanks in advance to suggestions, please leave all cutting remarks at the door
Update: When I am in recovery mode on my Windows 7 machine, the tablet appears under the Android Phone section. Not sure if it helps but thought I would add that.
Can you get the device to show up in ADB? If so you can push the ROM through ADB.
mustbepbs said:
Can you get the device to show up in ADB? If so you can push the ROM through ADB.
Click to expand...
Click to collapse
Dude you were spot on, the nexus had ran out of juice so I had to painfully charge it to at least 10% before I could try it. Just to clarify, I got the device into recovery mode, in Device Manager it was appearing under Android Phone as ADB integ Port (something to that effect) and then pushed out the rom to the SDCARD using the ADB push command. Managed to install the SmoothRom and its loaded fully
My windows 8 laptop must not have a driver or something not compatible as opposed to my windows 7 PC. Although on the Win 8 laptop, when the device in Fastboot it does appear under Android Phone but when the device gets to recovery, it moves to the Unknown device. Anyway my ordeal is over and it has been nervy!
Hope this helps someone?
Hi all,
After a long time, I decided to play with my Nexus 7 again. About a year ago, I bricked itsomehow (don't remember how exactly).
As a result, only the bootloader is installed. So no (custom) recovery and/or ROM. Today, I tried to flash the stock rom with the Nexus Root Toolkit but it didn't work.
My computer (Win 8.1) was not able to recognize my Nexus 7 in fastboot mode.
The device manager in windows labels my nexus as an unknown device of which the device descriptor request has failed.
I already tried to install many different driver packages (while removing the device from the device manager) but it did not work for me. Everytime, the tablet is seen as an unknown device.
I also tried to update the driver manually by right clicking on the unknown device in device manager and clicking update driver software and then manually selecting this http://support.asus.com/Download.aspx?SLanguage=en&m=Nexus+7&p=28&s=2 driver but it does not recognize any driver.
So in short, my pc, which runs windows 8.1 is unable to see my Nexus 7 (which is bricked and has no rom nor custom recovery installed) when it is in fastboot mode. Therefore I am unable to install another rom.
Any thoughts on this problem? Thanks in advance.
I sent you a PM regarding this issue and a potential fix. If it works, i'll post the detailed info here later
I know what your thinking another newb not installing drivers properly or hasn't changed to file transfer mode.... This is not the case. I been installing adb and USB drivers since the og droid.
I have a real problem here....
I been on custom ROMs and wanted to fastboot back to stock however none of my computers are detecting my phone... Tried on 2 windows 10 x64 and one windows 7 x64 with same result. None even pop up a notification or ding a sound that the phone has been plugged into it. Nothing in device manager either. The phone charges at least I have also tried 4 different cables granted 3 came in a bundle pack that I do not trust but reviews state although not full speed they should do data....
Now here is the kicker:
If I turn off my phone and boot to the bootloader my 3 computers detect a device has been connected but the drivers fail and say something about the device signature can't be recognized. I have tried disabling the device signature validation in windows 10 with no luck and also windows 7....
Tried manually installing the drivers but says not compatible with device hardware
At this point I'm baffled luckily I'm rooted twrp and can download files to install directly but I rely heavily on fastboot as my goto if something goes wrong I'll be hosed!
I did factory reset and even flashed another custom rom to see if it was the ROM I was using.
Please help if you have any ideas to try. I have yet another cord coming Friday just in case the offchanse the main went bad and the other three from the bundle pack are ****
Sending back to google I hope they don't mind the custom rom, unlocked bootloader and twrp recovery lol
Hi guys,
I tried to move some files to my phone today, however when I plugged in the phone to my PC, it would only show the virtual drive with drivers. Installed those and reconnected, but to no avail. The phone just doesn't show up. In device manager it's shown as MTP device and when connecting with ADB enabled, "Marshall London ADB Android Device". I've done countless reinstalls of drivers but nothing has worked so far. Tried on a laptop running windows 8.1 but still nothing happens (PC runs windows 10 Education). Followed mutiple guides on installing the drivers, but never has the device type window (after manualy choosing a driver) shown an android device option. All help is appreciated.
Phone is rooted, bootloader unlocked and on 2.2.1 (5.1.1)
Model is ONE A2003.
It has worked before, when putting files on it a few months or even weeks ago.
I have windows 10, and am attempting to root and flash a custom recovery and ROM onto my nexus 7. Everything functions as intended until i have to enter bootloader. windows 10 is not able to recognize the device drivers when plugged in while in bootloader mode. It simply says that the device is not recognized. I read that the issue is needing to edit the .INF with updated hardware ID's for the device and reinstall the drivers using that INF file. However, trying to do that yields no results because when i uninstall the driver i cant find the device plugged in anywhere to be able to update its drivers in the device manager, and simply trying to override the devices currently installed drivers via device manager also does nothing. I even tried installing the driver update while the device was in bootloader via device manager (the device is recognized in device manager but has a yellow exclamation point and says device descriptor failed) with no results. What am i doing wrong? can anyone help? I've never had an issue this frustrating while trying to root an android device. Is it a windows 10 issue? I need a complete (and simple to understand) step-by-step please.
No help?