I am currently using a ROOTED "Huawei MediaPad 7 Lite" tablet and am having issues entering the bootloader. When powered on and connected to a Windows PC, the device is seen in adb using the command "adb devices" (driver is working). However, when I try to enter the bootloader, "adb reboot bootloader", the device malfunctions in windows.
(View attachment 1)
Click to expand...
Click to collapse
The same occurs when the tablet is powered off, and the power and volume up keys are held down (entering bootloader manually). In 'Device Manager', there are NO 'Unknown Devices' missing drivers. Instead, there is an issue with the USB controller, with an error saying "Unknown USB Device".
(View attachment 2)
Click to expand...
Click to collapse
Due to this malfunction, I cannot install a driver for the tablet when in bootloader mode. To clarify, the tablet works OK when powered on and connected to a PC, but malfunctions when in bootloader mode. I have tried this on 3 different computers with 4 different MicroUSB cables with no success.
I also have a second identical MediaPad 7 Lite, and in trying the above steps also has the same problems. It seems Huawei have done this as a preventative measure (meaning it is a device specific issue), but does anyone know how to make the PC recognise this device properly when in bootloader?
The bootloader screen is unusual. Without the cable connected, when the bootloader is entered (by pressing power with volume up & down), the following options exist:
- continuing to hold volume up brings up a screen which is used to update the tablet software from a file on the external MicroSD card
- continuing to hold volume down initiates an automatic recovery process
- releasing all buttons reboots the tablet automatically after a few seconds
With all of the above options, I tried plugging the tablet into my PC. However, Windows does not recognize the tablet at all (nothing pops up).
same applies MediaPad s8-701w
Thanks for this information.
Was good to get confirmation of what I experienced - same applies to recently purchased MediaPad s8-701w.
Searching widely fails to raise any other observations of this to date.
handaxe said:
Thanks for this information.
Was good to get confirmation of what I experienced - same applies to recently purchased MediaPad s8-701w.
Searching widely fails to raise any other observations of this to date.
Click to expand...
Click to collapse
Sigh! This is wrong. See this where I give the details.
Related
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
JNiels1980 said:
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
Click to expand...
Click to collapse
When you press up on the USB icon and it freezes that it normal.. This is fastboot mode.
You now must access it over a PC after installing the naked drivers.. If it is not showing on your PC then either try a different PC or your cable is faulty.
Thanks for the quick reply.
I tried once more to enter fastboot. Same result.
But when I disconnected my usb cable to connect it to an other computer, suddenly I got this message on my tablet:
"Starting Fastboot USB download protocol"
This message didn't show up before.
I plugged the tablet back to my pc, but still no device detection in device manager, even when refreshing (So I can't install naked drivers, as it is not recognized).
My computer is a Windows 8.1 system.
I restarted my tablet again, (after disconnecting it from my pc) and followed the procedure to enter Fastboot again.
I waited for the message "Starting Fastboot ..." and then I connected the cable to my other pc (Windows 7 system)
Same result as on the Windows 8.1 machine, not recognized
You say it could be that my cable is broken. Maybe, but it's a strange coincidence that this happened when switching from ICS to JB.
I know JB for the tf201 is been out a long time, and I updated since I could. So over time, maybe my cable could be broken now. But I'm sure I had this problem (not recognizing) since then, because right after updating I wanted to do some things with ADB and so I found out I had this problem.
Hello everyone,
I'm writing in the hopes of receiving some guidance re: a small "challenge" a friend issued to me. As you can probably guess, the half of the story that involves my friend's actions on the tablet are word-of-mouth, seeing as the device was given to me in a totally bricked state. Hope you'll be able to assist me somehow!
After using his Galaxy Tab P7500R for some time, the battery stopped charging. He supposedly tried a complete wipe and system restore (for which he was unable to guarantee a successful conclusion), and then the machine ran out of whatever juice had been left behind during the last successful charging cycle, and turned off completely, showing no signs of life whatsoever.
This is where I come in - I was given the "expensive ornament", accompanied by the words "have fun, I've already bought another one".
Symptoms are the following:
1) Powering the device on doesn't work. While the device is connected to the house power grid, there are no indicators of the device doing anything.
2) Connecting the device to a USB port on my laptop, and holding the power button, after 15 seconds my PC signals a device being disconnected via sound, and that disconnection sound is almost immediately followed by a couple, rapid, "halved" 'device connected' sounds. On the other hand, while the device is connected to a USB port on the laptop, if I hold the power button together with volume+, all I hear every 15 or so seconds is the "Device disconnected" sound.
3) After using USBDeview to remove a driver named APX, and after reconnecting the device to the computer via USB (sometimes this requires holding the power button, sometimes all it takes is a reconnection), I will hear a full "device connected" sound; then, an "installing driver" window will open, for the APX driver, which, after looking for the appropriate driver via Windows Update, will give me an error message ("no driver found") on the "unable to install device drivers" window.
4) Opening the device (out of warranty for over a year), and utilizing some testing tools have shown that power does reach as far as the motherboard, and that the batteries are somewhat charged at the moment.
Any ideas?
Thanks in advance for your help!
Lightside
[UPDATE 1]: I successfully installed the NVIDIA USB Boot-Recovery drivers for mobile devices. The tablet is now detected as being connected to my laptop, sounds and everything.
Following some instructions I was able to find on these forums, I tried installing NVFlash, and running the --bl bootloader.bin --go, receiving a "Rcm version 0X4 - Command send failed (usb write failed)" message.
From what I gathered, this is evidence of a locked bootloader. I wasn't able to find any posts dealing specifically with a bricked device that is only recognized in APX mode, and how to unlock the bootloader in such cases. Is there a guide available by any chance?
Update 2 :
I've extracted the battery, but I seem to be unable to remove the residual charge, as the device shows up (APX) as connected, as soon as I plug in my USB cable.
Anyone? :/
Up?
As the title says, I have an Ariel Fire HD 7 stuck at the Amazon logo. At this point, I suspect I have no bootable OS because after using powerpoint45's Linux Unbricking ISO successfully, I downgraded to 4.5.3 to root, then tried to upgrade to Lollipop, probably flashing an incompatible bootloader. It is not detected by ADB, ./handshake.py in the Unbrick ISO fails after about half an hour of waiting, and Windows 7 Device Manager detects it as an "MTP USB Device" with error 10 "The device cannot start". If this is recoverable, please post a thread URL in this thread, and I will try the method detailed in it, then post the result here. Thanks in advance!
Not sure if this would help, but you can get the MTP USB Device to change to Fire ADB by watching device manager. In Win10, I have Device manager open, wait for the MTP to opo into it and quickly right click on it and clicking update driver.
When mine did that it would pop up and dissappear pretty quickly. Does yours do that? If so after clicking on update driver, click on browse for driver. Should bring up a list of devices it could be. Click on all devices and go down to Amazon and use those adb driver. A pop up asked if I really wanted to do that, and I clicked yes when I heard the device pop into device manager again. It was always there since you were working on it, but really it wasn't. I had to wait for the sound it makes when popping up.
As for ./handshake.py what I did was take the cover off the kindle and unplug the battery. Plugged the cable into the usb port, used the handshake command and after it said waiting, I plugged the battery back in. may have to hold the power button for a while if it's in a bootloop to turn it off totally.
So this is a budget phone , spent hours obsessing over rooting it, did the whole process several different times several different ways,
the funny thing is , i can't event brick this device . this runs OREO 8.1 which a chopped down version of the full OREO 8.0 , basically it's designed for budget "entry level phones" . So i'm wondering
why they would make it so unbrickable? is it possible that this device doesn't even have a bootloader? if not why is it so hard to get to it?
Can't access fastboot mode nor the bootloader
One year later and this is still an issue. Here is my situation:
I bought an OTG (on-the-go) cord that allows me to connect a USB stick to my phone in order to extend my storage capabilities, but my phone doesn't natively support OTG (it basically doesn't have the drivers for it). In order to add support for it I need to root my phone, which I am having serious trouble with.
After hours of researching, installing, uninstalling, and factory resetting I've narrowed everything down to not being able to access the bootloader to select the fastboot mode. Here are my phone details:
Device Name: LG K20 (boot screen says "LG k20 Plus" however)
Model: LM-X120WM
Android Version: 9
Build Number: PKQ1.180904.001
Software Version: X120WM11c
As far as configurations go, I have:
- Enabled Developer Support
- Enabled OEM Unlocking
- Enabled USB Debugging
- Made my computer a Trusted Device on the phone
- There are no special "adb" options or configurations within my phone (I saw one website mentioned something about "adb" some options, but I only saw this once, and my phone doesn't have it anyway).
So far I have tried:
1) Holding the Power + Volume Down button for 10 seconds, then releasing the Power button when I see the LG logo, then repress the Power button until I see the "Factory Reset" menu. All this does it give me options to Factory Reset unfortunately (which I've done).
2) Holding Power + Volume Down button for 10 seconds. This simply reboots the phone and does nothing else.
3) I've downloaded, installed (on both my phone and my computer when needed), and tried rooting using the following programs: Dr.Fone, KingoRoot, RootGenius, iRoot, SuperSU Pro, and Superuser. There were some others I tried as well, but I determined I couldn't get anywhere with them specifically because I could not access fastboot mode (one example is "Magisk Manager").
4) Using ADB tools within command prompt (the most commonly recommended method) I tried rebooting the device into fastboot mode using the command "adb fastboot bootloader". The phone simply reboots and that's it, it has not switched into fastboot mode. You can confirm if you are by using the command "fastboot devices", which my device never shows.
5) I have gone to the LG website in order to download the drivers for this phone, however, while I am able to locate my specific device on the LG website, it directs me to download the "LG Mobile Support Tool", rather than download the drivers specifically for this device. I downloaded and installed the LG Mobile Support Tool but when the tool loads it does not recognize my device and tells me I need to install the drivers, which it gives me an option to do. Naturally I start the process to install the drivers but when it gives me the list of phone models mine is not in there *and you cannot proceed without selecting a model*. So, I tried using the closest model to mine (the LMX510WM), but it still didn't work.
6) Because LG does not have a direct download of the drivers for this device specifically I have tried downloading a variety of different drivers for this device. None have resolved the issue, but at this time *I believe* I have the most recent version of the LG drivers available "LGMobileDriver_WHQL_Ver_4.5.0".
7) I've tried adding the USB drivers through any install tools that came with them, and I've tried installing them manually via "Device Manager -> Add Legacy Hardware" and choosing the driver files specifically. This has not resolved the issue.
8) Installed the "wpdmtp.inf" file found within "c:\windows\INF" as recommended for Windows 10 users on one forum or another. Did not resolve the issue.
9) Installed the full Android Studio suite hoping something I was missing would be available, I also tried using the "adb" tools they provided: no love.
10) I also tried powering off the phone, holding the Volume Down button while plugging in the USB cord. This is supposed to do *something*, the instructions says I should enter "download mode", but on my phone does nothing.
11) the XDA-Developers forum suggested installed LGBridge_Setup.exe if I was having problems with drivers, which I have. When I ran the program it wasn't able to connect to my phone.
At this time I've uninstalled almost all software and all extra drivers from my computer (I left only the "LGMobileDriver_WHQL_Ver_4.5.0" drivers), as well as having factory reset the phone.
Everything is ready for another attempt, I've just run out of ideas. Thoughts?
Hi, I have also been trying to root this phone for the last year, but failed.
Everything is exactly the same as your phone regarding Build#, model # etc except i have software version X120WM10c .
The phone always wants to update but then it fails every single time.
I am hoping to root the phone so i can debloat it, and remove the restrictions preventing me from using it the way I want.
Anyone have any advice/info please post here. I will do the same.
Anyone? No response in almost a year.
ckeays said:
Anyone? No response in almost a year.
Click to expand...
Click to collapse
first of all you guys, are talking about two diferent very disimilar phones.. mediatek v20,qualcomm on the k9.....
myself i have a x210wm k9 im trying to find compatable firmware for.
The phone is working fine without root. Seems very fast for $99 CAD phone!
I seem to have gotten my N200 in a state where it will not power on. No screen display, no vibrations, and unresponsive to volume and power buttons (standalone or combination). It's a DE2118, T-Mobile variant, network locked and not rooted.
Here are the conditions leading up to it:
The phone was plugged in to my PC via USB, (through a USB hub).
My Sim/SD tray was ejected.
I had been using an ADB shell to disable-user some apps and check out some various PM commands.
I did not terminate the ADB shell before powering down from the phone.
Once powered off, I held the volume up+volume down+power buttons to attempt to check out the recovery mode. I've never entered recovery mode before on this device.
The USB cable was still plugged in and I could hear the USB new device sounds on my PC a few times while I did this but didn't think anything of it.
Nothing ever appeared on the screen and pushing any of the buttons seem to provide no response.
Battery usage was at least 80%, if not closer to 90% before this happened.
It almost seems like the device is powered on and running as there feels like there's some very slight warmth on the back panel, near the center just under the camera area but I might just be imagining the warmth.
I'm aware that it needs to be network unlocked before it can be rooted as per other threads and I have not tried any root methods.
I still have my ADB shell dialog up but there really isn't much interesting in it besides a lot of the command help dialog.
What are my options?
Note: I recently installed the Jan 6th android 11 security update maybe a day before.
Edit: For anyone looking at this later, the phone came back after a complete battery drain and partial recharge and I was able to replicate the bricked state performing the same thing, usb debugging on, plugged in to usb hub on pc, shut down phone, then holding all 3 buttons down for a while.
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
mthous01 said:
Windows or Linux pc?
Does your device show up in device manager if windows?
If Linux, do you see the device if you run
adb devices or fastboot devices?
Click to expand...
Click to collapse
I'm using Windows 7 mainly.
It shows up in device manager when I plug in the USB but with error code 28, unknown driver.
In Win7, "adb devices" lists a blank line for devices.
In Linux, "adb devices" lists a blank line for devices.
In Linux, "fastboot devices" has no output at all.
If your phone is showed in device manager you should be able to give him his life back...had the same situation long time ago with my oppo find 7..
Try this, and see if it'll recognize you for MSM download.
mthous01 said:
Try this, and see if it'll recognize you for MSM download.
Click to expand...
Click to collapse
Will give it a try. Going to be a few hours to DL the file as I'm on an extremely slow connection atm.
Well, I think that made it worse. Couldn't get the Qualcomm CAB drivers working on Windows 7, but got it through Windows Update. The MSM tool went through the process fully but afterward I unplugged the device and tried to boot, still no response, nothing on screen, no vibration. Now when I plug my device back in to the USB, I have an endless new usb device noise and windows says "Unknown Device". Device manager refreshes constantly while its plugged in. Looking back I should have probably tried ADB first before running the MSM tool.
After almost 24 hours of being unplugged, I tried plugging it in again and it finally had some signs of life with the low battery warning and then TMobile splash screen+vibration+sound after about 5 minutes. Still waiting on it to charge up for now. Probably just needed to be power cycled in the end instead of attempting to flash anything. I sure do miss the days of removable batteries.
Mtrlns said:
Probably just needed to be power cycled in the end instead of attempting to flash anything.
Click to expand...
Click to collapse
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
lzgmc said:
In the future, you can power cycle the device by holding all three buttons on the phone for 30 seconds while it isn't plugged into a PC.
Click to expand...
Click to collapse
I had tried that yesterday to no avail. Was very strange. Everything seems to be working as normal now, though factory reset from running the MSM tool. I'm wondering if I'd be able to duplicate the issue again.
Could not replicate with USB debugging off and plugged directly in to my PC's USB port, but turning on USB debugging and plugging in to my USB hub, shutting down the phone, and then power cycling with all three buttons brought the same bricked state.
Don't know for sure if the USB port matters but while bricked plugging in to the USB hub always gives a USB device error sound. Going directly on PC it connects fine as a new device (as QUSB_BULK without drivers or Qualcomm HS USB QDLoader 9008 with drivers). ADB/Fastboot commands from PC's command line don't seem to do anything.
I did notice the fastboot menu show up on screen for a second when power cycling this time and I don't recall it appearing the first time. I think i may have had "advanced reboot" turned on the first time, while it was off this time.
Powercycling actually reset it this time.
Possible solution
It would seem that you can force MSM to write both a and b slots, which might fix your issue. Might be worth a shot
Note: If this swaps you to the Tmobile software, there's no guarantee you'll have anything but a phone that cannot be bootloader unlocked again. Since unlocked have no unlock token, trying to do so with a phone that isn't technically Tmobile may be an issue.
Just had the same problem. Holding all buttons for 30 seconds worked.
if you bricked it and you have tmobile variant you can restore it weather you have a locked or unlocked bootloader.
you have to get your phone in EDL mode, once in EDL mode you will see the "QUSB_BULK_CID" in device manager. you will then need to install qualcomm drivers (if done manually you will have to endable windows test mode, if you use the qualcomm USB driver installer then it will do it for you and you will be in test mode upon next windows reboot.) Reboot windows in TEST MODE. NOTE: i said WINDOWS TEST MODE... Once in windows test mode the driver should function and look normal in device manager. From there just open the MSM tool for your version of Nord N200 and flash and wait about 3-5 minutes. Reboot the phone and you are back in Oxygen OS.
Tips and extra Files needed below:
for the tmobile NORD N200 MSM tool
Index of /list/Unbrick_Tools/OnePlus_Nord_N200
The installer for the QUALCOM USB drivers can be found here at this website (ONLY use the QUALCOMM drivers from here, do not use any other file as it is for a different phone):
droidwin.com/unbrick-oneplus-7-pro/
once done unbricking and restoring your phone you can then exit windows test mode by running
bcdedit -set TESTSIGNING OFF
at the windows command prompt as ADMINISTRATOR.