Hello,
I have a Redmi Note 4 SD MIDO, since the 8.2.10.0 update, I had several problems (battery, usb).
Firstly, I was unable to charge my phone, it makes a connecting/disconnecting loop, making the charge very slow (video: streamable[.]com/4k23i).
I managed to fully charge it, caliber it and fully discharge it, the charge worked like it used to. It happened to other people, it's really weird.
Now, I'm able to charge it but if I connect it to my computer, it makes this connecting/disconnecting loop again! (On Android, TWRP, adb). If I start my phone in fastboot mode, it doesn't disconnect, I type "fastboot devices" and it works. With TWRP using ADB, "adb devices" loose it in loop.
I think it's a software issue, but I'm not sure, I don't know if it comes from the update because it doesn't work well with TWRP.
Does anybody had this kind of issue? I would like to avoid to send it to the service center, I live in Europe and it's in China.
Thank you!
Related
I thought I would share this. I am kind of answering my own question but I am not really sure how I got into the state that I did.
Today I realized that I could no longer connect via USB to my PC. My phone has DietICS ROM. I tried the following:
New Cable
New USB port
Cache wipe
Dalvik wipe
Factory Reset
Rolling back to a previous nandroid that I knew worked
Reinstalling USB drivers
I still couldn't connect the phone as a media device and nothing was reported in Device Manager.
I ended up trying to put the phone in download mode and firing up Odin (to see if it would show as connected) and whalla. It saw the phone. I shut the phone down and rebooted it again and everything was working as it should.
If anyone has any insight on this, it would be appreciated. I am still not sure if it was the PC or the phone that had the hiccup.
Did you try rebooting the PC? I don't see that on your list.
Occasionally I have issues with Windows 7 (and 8) where it doesn't see that a USB device was unplugged, and if I try to use that same USB port for something else it just never detects anything.
It's rare in my case, but maybe something similar happened on your end and just having a different device ID show up (download mode shows up as a different device) kicked Windows in the pants and got your USB drivers working properly again?
dstruct2k said:
Did you try rebooting the PC? I don't see that on your list.
Occasionally I have issues with Windows 7 (and 8) where it doesn't see that a USB device was unplugged, and if I try to use that same USB port for something else it just never detects anything.
It's rare in my case, but maybe something similar happened on your end and just having a different device ID show up (download mode shows up as a different device) kicked Windows in the pants and got your USB drivers working properly again?
Click to expand...
Click to collapse
bah, yes. Rebooting the PC was one of the first things. I missed that on my list.
Weird... happened again.
1.) connected device to USB. Got the double beep and charging but no "MTP" connection message on phone and nothing detected in windows.
2.) Booted phone into download mode. Connected phone and windows saw it.
3.) Rebooted phone again and everything works fine
Happened again (updating this thread for no apparent reason).
Fully powering down the phone and then booting it back up (cold boot) seems to be fixing it.
camoto said:
Happened again (updating this thread for no apparent reason).
Fully powering down the phone and then booting it back up (cold boot) seems to be fixing it.
Click to expand...
Click to collapse
I have the gnex and although different phone i just have plain out usb issues. Does your phone and/or battery have nfc chip?
*Android is upgrading...*
JediNinjafication said:
I have the gnex and although different phone i just have plain out usb issues. Does your phone and/or battery have nfc chip?
*Android is upgrading...*
Click to expand...
Click to collapse
Yes it does
camoto said:
Yes it does
Click to expand...
Click to collapse
Ok, I download all roms and mods directly from phone browser so don't usually have it plugged into computer but have been having issue when trying to charge it with the factory plug. If phone is hot i have to reboot or it says "not charging" in stats. Might not even be related but i found out the battery also has an nfc inside it. Maybe it's something in the connection or the chip in battery between the port and battery..? Because when hooked to computer it also tries to charge right?
*Android is upgrading...*
Hi everyone,
My dad's friend has a problem with his phone and dad asked me if I can help him. Right now I only know that he had "LG Security Error". However when I got the phone it didn't react on anything, so I'm unable to turn it on or charge a battery (I have also a second battery, neither of them works). When I plugged it to a PC it showed "OMAP4430". I've never had experience with LG before (only Xperia phones), but after searching I found this (2n option), which didn't work with my device, but this (1st option) worked flawlessly. I managed to get into FASTBOOT mode (phone is listed with "fastboot devices", ADB not) - OMAP FASTBOOT DEVICE. I noticed that it disconnects itself after 1-2 minutes and the proccess needs to be repeated. The phone still isn't showing anything on screen. After few hours of searching I didn't find anything, except that after doing procedure with Vol+ button entered, Windows recognized my phone (I could get only twice and the screen was still blank):
Code:
LGE Mobile Composite USB Device
LGE Mobile USB Serial Port (COM9)
LGE Mobile USB Modem
LGMobile Support Tool was doing something, but in the end it didn't detect anything, also I checked out LG Flash Tool 2014, phone information showed that it was in emergency mode. Screenshots
At this point I'm guessing that the phone is hard bricked as it couldn't go to S/W mode, download mode or show anything on screen etc. I haven't found any tut about unbricking in fastboot. Is there anything I can to at this stage?
Thank you in advance!
The com port driver is the only one needed for unbricking. Provided, that the phone is already in D/L mode, otherwise communication will first be done with the ADB driver.
I had the situation, that the phone wasn't recognized by the ADB and Fastboot drivers(with a custom rom installed), and under Win8.1 and Ten Fastboot generally doesn't work. But only the L9 is affected by this.
But if someone managed to clear the whole internal flash, with bootloader and baseband, the phone is economical junk now. Though re-flashing via JTAG is possible. While some geeks may own one of these Octopus adapters privately, even if you know such a person, he should be an LG user, too, as support for each brand or individual model has to be bought separately. Or simply invest around 100€ or $100. That is the price of a brand new phone with the L9s capabilities and a stable(!) Lollipop or Marshmallow installed.
hi. so my problem is that my phone does not turn on, i cant go to recovery or do hard reset. the phone react when i plug it in PC without battery, but its always connect and disconnect over and over again. i have downloaded the omap drivers and instaled it. now i have in the device manager a OMAP4430 FastBoot USB device. by the drivers was a fastboot emulator. but when i will flash rom, kernel or recovery a just get partition does not exist. can someone help me please? srry for english.
Does your phone not turn on at all when holding down the power button? If it boots up, and gets stuck on a loop or has an error message, that is different. But if it doesn't turn on at all, then your battery is dead or something is wrong with your phone's hardware. If you connect your phone to the PC (with the battery on), does it at least show a light? Or does it boot up at all when you hold the power button? If it doesn't show a light or boot up, it is not your battery, but your phone's hardware. Your phone might have been dropped or water inside it or it was microwaved? I know it sounds silly, but something happened to the phone physically. Now if you connect it to the PC and you see a light but it never boots, your device is bricked. Not accusing you, but you might have tried rooting it or writing over a partition on your phone which caused to brick. Also, try typing in fastboot devices. If it shows up a device, that means it is connected. Cheers!
No the phone does not turn on and it shows nothing, even when i put it on charger. If i connect to pc with battery after i installed the omap driver it just connect and disconnect over and over again, windows make this sound when you connect and disconnect something. I have flashed a new rom. It has worked but after some time its stoped. So i have try flashed it again but i could not get in recovery. A files was missing and after i try flashing thhe recovery its just dead. I can connect it just with the fastboot emulator because it's don't connect when i just put it on pc. I must connect it without battery wait 4 sec and then put the battery back. Than i can see in the emu my phone but not able flash anything because of partition does not exist
Just want to make sure that I'm dealing with a hardware and not a software problem....
Device: OOS 3.1.4, TWRP, Magisk 18.1, Xposed, Arsenic kernel. Battery replaced just a month ago.
Friday, I noticed my phone reporitng a battery level of 100% after using it for most of the day. Plugged it in to charge and it wouldn't charge. After reboot it showed the correct level, and would accept a charge.
Saturday morning, on unplugging the phone I noticed that the notification LED flickered a few times, as if the phone though it was still being charged. After a few flickers it stops.
Since then, the phone charges fine. However, I noticed that my car's Android Auto no longer recognized the phone as being plugged in. After a bit more snooping, I realized the phone's lost data transfer capabilities over the USB. Here's what I've tried (and failed)
Plugging into computer with multiple different cables and different ports.
USB Debug + ADB -- no new devices detected in device manager
Fastboot -- throws a "device descriptor request failed"
Repeated the above after re-installing the 15 second ADB drivers -- no luck.
Boot into TWRP and attempt to ADB via side-load -- nothing
Wiped everything except boot and EFS in TWRP, re-flash stock ROM -- nothing
At this point, is there any possibility that it's still software? Can a kernel error do this? Or is it purely hardware and I should look for a new phone?
You can try to clean the connector.
Did clean it. No luck
I had also faced almost same kind of problem. When i plugged it for charge LED won't blink but it charged. After some days that stopped too. So i changed charging port from a repairing shop. After some days data transfer stopped with original charging cable and my PC recognized it as unknown broken device. So i bought another charging cable and now everything works.
TL;DR -- it works
Just an update...since my last post, I had an episode where it boot-loops. I suspect this was because I had used the "advanced mounting" on Apps2SD that warns that it can boot loop. The fix requires ADB which I couldn't do, but somehow re-flashing the stock ROM breaks the bootloop (but USB still doesn't work).
Reinstalled Arsenic, Apps2SD, Magisk. Have had the occasional freeze (usually while on the phone, and once when trying to transfer something to the SD card). Dialed down the undervolting (which has been rock solid until now) and maybe it helped a bit? I still froze once while on completely stock settings though.
HOWEVER...had my phone plugged into a Linux-based thin-client for charging...and after around 15 minutes, it spontaneous went into debug mode. Data transfer works now, as does ADB. With all of my cables that I know are good.
What happened? no clue.
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.