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?
Related
This might be a dumb question, but I recently bought a Jiayu G4 and I've been trying to install the drivers on my laptop. Formerly when I connected the phone with the battery in and power on I'd have "JY-G4" show up in my device manager, and when I connected it with the battery out and vol+ pressed I'd get mtk6589 or something along those lines (contrary to everything I read that said I could let go of the volume button after the phone got picked up, I had to keep it pressed or it would disconnect... this is important). Anyway I managed to start installing the driver but I must have accidentally let go because I got a message saying the installation failed because the device was disconnected. Now neither of these devices shows up in the device manager, Windows doesn't try to install the drivers when I connect the phone, etc... how can I retry to install the drivers when the devices don't show up on the list? Did they install correctly after all? I haven't modified the phone at all so I'm pretty sure this is all Windows.
I have a (supposed) MT6589 iPhone i5s clone which I managed to brick. I tried to use the instructions here to use the SP Flash Tool to unbrick it, but the first problem I have is with getting my Windows 7 (32 bit) computer to recognize the phone. I installed the MediaTek MT65xx Preloader VCOM driver and it connects for a second. I can see the device connected as a COM device, but it only stays connected for a second and then disconnects. (This is independent of whether I am running the SP Flash Tool or not.)
Is this a symptom of a bad driver? The other problem with trying to follow the instructions is that it says to remove the battery, but this copy is a 1:1 of the iPhone so it is not intended to be opened up. I tried to discharge the battery completely, but when I plug the device in, there seems to be no response (ie, Windows doesn't do anything). At some point, there seems to be some charge in the battery because of constantly plugging in the USB cable, and at that point, is when the device is recognized but is quickly disconnected.
Anyone happen to know what I am doing wrong?
So in general, I am first interested in:
Why is the device connecting properly (I assume) being recognized as MediaTek Preloader VCOM, then disconnecting in about a second?
Is it related to not being able to disconnect the battery?
In theory, wouldn't a dead battery be the same as disconnecting the battery?
When battery is dead, nothing happens when I connect the phone to my PC. This seems odd since I am supposed to be able to connect to the PC without any battery... What is the difference?
Per instructions, I've been pressing the + volume button when connecting, but I seem to get similar results no matter if I press + or not.
Should I be loading any other drivers besides the MediaTek Preloader drivers?
Thanks.
PS. I've decided to open up the phone using a video found on YouTube, and found that the battery is soldered, so I am not so motivated in trying to disconnect the battery if possible.
Update: OK, the problem I likely had with the phone is that since the phone was in a type of "boot loop", I couldn't actually tell it was on or not... And plugging in the cable only worked if the phone is off. Once I made sure the phone was dead due to battery dying and made sure I did not turn the phone on, I could connect, let the battery charge long enough for the phone to respond to the PC, and then it was recognized by SP Flash Tool. However, seems I may have tried flashing something incompatible as the phone is not responding. I'll likely need to write another post once I can find the symptoms of what is going on.
Try hardware preloader MOD which means test point on the phone board; by soldering one to GND and another point on the board (connecting points are clear on the board), this will stop connecting and disconnecting phenomenon
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.
Hi, so I have encountered a rather big issue with my xiaomi redmi 3 pro.
I believe I have flashed wrong (corrupted ? ) ROM, now I have a really annoying situation.
So, I flashed " ido_xhdpi_images_V7.2.6.0.LHPCNDB_20160129.0000.14_5.1_cn " in MiFlash, took a bit long time (nearly 15 minutes), afterwards it was completed, I disconnected my phone, and *BOOM* since then, black.
Current situation is this: When I connect my phone via USB, my phone gets recognized in device manager as
"Qualcomm HS-USB QDLoader 9008 (COM#)", also it gets recognized in MiFlash, but can't get it to work in fastboot, and it is not recognized as adb device. So, throughout 3 days now, I tried nearly EVERYTHING I have found on forums. The only thing I have not done is to take the back cover off and disconnect battery ( as I have seen on forums), tried with deep flash cable, all possible combinations of buttons and all. If the phone is connected to PC, when I press whatever combination of buttons on phone I just get Windows sound for connecting an USB device.
So today, when I connected it, red LED light was blinking, I have no idea what that was, so I plugged it into the wall to charge for 10mins, and now when I connect it, it's gone again, all black, no response whatsoever.
So, when I connect it to MiFlash and try to flash any ROM, tried nearly everyone I found, I get the same message; "Unspecified error 0x80004005; End Transfer packet id0, status 9" if I refresh MiFlash without disconnecting, and press flash again I get "Reached the end of the file. (0x80070026; Receiving hello packet) "
Things maybe to mention: I am running a 64 bit Windows 10, and my bootlocker is locked.
So I am wondering, if there is any possible way to solve this or it's time for a new phone?
alchzor said:
Hi, so I have encountered a rather big issue with my xiaomi redmi 3 pro.
I believe I have flashed wrong (corrupted ? ) ROM, now I have a really annoying situation.
So, I flashed " ido_xhdpi_images_V7.2.6.0.LHPCNDB_20160129.0000.14_5.1_cn " in MiFlash, took a bit long time (nearly 15 minutes), afterwards it was completed, I disconnected my phone, and *BOOM* since then, black.
Current situation is this: When I connect my phone via USB, my phone gets recognized in device manager as
"Qualcomm HS-USB QDLoader 9008 (COM#)", also it gets recognized in MiFlash, but can't get it to work in fastboot, and it is not recognized as adb device. So, throughout 3 days now, I tried nearly EVERYTHING I have found on forums. The only thing I have not done is to take the back cover off and disconnect battery ( as I have seen on forums), tried with deep flash cable, all possible combinations of buttons and all. If the phone is connected to PC, when I press whatever combination of buttons on phone I just get Windows sound for connecting an USB device.
So today, when I connected it, red LED light was blinking, I have no idea what that was, so I plugged it into the wall to charge for 10mins, and now when I connect it, it's gone again, all black, no response whatsoever.
So, when I connect it to MiFlash and try to flash any ROM, tried nearly everyone I found, I get the same message; "Unspecified error 0x80004005; End Transfer packet id0, status 9" if I refresh MiFlash without disconnecting, and press flash again I get "Reached the end of the file. (0x80070026; Receiving hello packet) "
Things maybe to mention: I am running a 64 bit Windows 10, and my bootlocker is locked.
So I am wondering, if there is any possible way to solve this or it's time for a new phone?
Click to expand...
Click to collapse
Hello,
I will move your thread to the correct section so that the experts there maybe able to assist you.
Regards
Vatsal,
Forum Moderator.
Hi, sorry to hear that happened to you. I suggest you to post this on Xiaomi reddit page, so more people can help you. Here is the link:
https://www.reddit.com/r/Xiaomi/
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.