Both Ubuntu and Windows recognize my mi10 phone on normal startup, but when I've enter fastboot (Power+Vol Down) to burn a new rom, it is undetected by either adb\fastboot, I've enabled usb-debugging and OEM Unlocking of course.
After wasting good couple of hours, It turns out you need to go the mobile device "Developer options" --> "Mi Unlock status" Grant permission to "Mi Unlock" a utility by xiaomi that can be downloaded from here (works on Windows).
this app will unlock your xiaomi device, making it possible to burn a new rom.
For me I had to wait 168 hours (1 week) before the app unlocked my phone (An excessive security measure?)
Related
I have a google pixel (sailfish) where the Operating system was damaged beyond repair.
It won't start into recovery mode.
I tried to use fastboot to unlock the bootloader (fastboot flashing unlock),
but it won't do that because OEM is not allowed.
I can't start up the device on Android to allow OEM unlock in developer options...
What can I do?
My power button died on my phone. Or got less and less responsive. Last time I was lucky that trying a long time I managed to start up my phone. Since then I kept my phone on perpetually or restarting it if that was required. However, now my phone just suddenly turned off out of nowhere. I tried to turn it on again but had no luck. I had previously turned on USB debugging since I thought that was enough to turn it on from the pc if it ever got turned off. Now it seems that was not enough as it shows up as unauthorized in adb (I never tried actually connecting, very stupid on my part). Is there any hope for turning my device on through adb.
Phone: Nokia 7.1
There are some questions on problems with unauthorized devices (ADB Android Device Unauthorized) but those seem to assume I can still turn on my phone to change settings. Is it impossible otherwise?
tldr; Here is a detailed list of instructions if you want to try your luck with fastboot. Your touchscreen and volume buttons must be functional for this to work.
Make sure the phone is turned off.
Press and hold the Volume Down button. Don't release it.
Plug in a USB charging cable
When the screen turns on and shows a message saying "Download" or "Fastboot" mode, release the Volume Down button.
Charge your phone like this for 2 minutes, to make sure it has enough charge.
Move your phone's USB cable and connect it to a PC.
Download the binary for fastboot.
Run fastboot continue.
Consider the below case:
A mobile phone is booted. At this moment it can be said that it is in run mode where the power consumption is more.
If no activity is done, after sometime the screen goes dim.
After further inactivity, the screen completely goes off.
Now my question is: can we say that the mobile phone was in standby mode and sleep mode in above steps 2 and 3 respectively?
Another question is, suppose we are playing some music and we leave the mobile like that for sometime. In this case also the mobile phone goes through 2 and 3 steps mentioned above. But the only difference to earlier scenario is that music is being played in the second scenario. In this case, can we say that mobile phone was in standby and sleep mode respectively in 2 & 3 steps when the music is being played.
If no activity is there for Linux, CPUIDLE threads gets scheduled by scheduler as it is the least priority process and it brings the CPU to various low power states, where as other peripheral are governed by various other concepts of OS.
If screen goes dim it can lead to two possibilities :
Partial wake load is help and system is down (some power save)
Linux suspend called (echo mem > /sys/power/stae) and full device is suspended, (huge power saves, as only ddr is active that to in self refreshing mode along with ALWAYS ON module)
So just by seeing you cant say its in sleep or suspend mode, but if say your touch or some activity other then register WAKE UP event brings the screen up, your device was in sleep mode not suspend mode.
WAKE UP events usually are "power on key", alarm, network packet (ie a call or message etc)
And for your second part of question, it belongs to low power audio concept, it varies alot with your device architecture.
Most common in android phones are putting the cpu in 'Low power state' and periodically waking them up to copy the music data to DMA, which can be played.
There are so many concepts used in the scenario you have used varies with OS and architecture and application, I have tried my best to give you a bird's eye view.
Very strange issue, no results that I could find from google searches.
I am running Windows 7 64 bit. Everything Windows related is up to date, and so are all USB drivers. My computer is a laptop from Puget Systems.
My computer has three USB inputs; one USB 2.0, and two USB 3.0s. 2.0 versus 3.0 doesn't really matter though, because this issue happens with all three drives.
Heres the issue: When connected, USB devices are found, and recognized. 5-30 sec later, they disconnect, only to reconnect in a couple seconds. The cycle of disconnecting/reconnecting continues indefinitely. I have not been successful with keeping USB devices connected for more than ~30 seconds.
At this point, it could be any number of things causing this issue. But this is where it gets weird. This issue ONLY happens with mobile devices, and it happens with ALL mobile devices. By mobile devices I mean phones and iPods. I have tested my Samsung Galaxy S4, an iPod Classic, an iPod touch, an iPod nano, a Droid Turbo, and an iPhone 5. This issue occurred with all of these devices. The issue did NOT occur at all with my 2TB Seagate backup harddrive, my 1TB WD harddrive, several USB pen drives, my external keyboard, or my wireless mouse USB receiver that is plugged in nearly 24/7 in my USB 2.0 drive. My Xbox One controller disconnected 3 times in a row once, but that only happened once so it might have been a fluke...?
Anyways, what could be the reason for this strangely specific issue? Does anyone have any answers or has anyone experienced something similar?
Improper drive installation? Make sure your drivers are installed correctly. Try uninstalling and reinstalling them. If this does not work try to see if it is your USB cable or mobile device's port. (Test by altering to charge the device from a wall adapter) It could also be your computers port but you said in the title that it is only happening for mobile devices.
Reinstall the drivers to the devices you are having problems with. (Oh someone beat me too it.)
I am having a problem with adb not finding my evo 4g lte. I have USB debugging selected. The phone is updated to 3.17, so some of the options, like charge only/disk drive have changed (now i think my only options are HTC Sync and disk drive). I am using the most updated version of the Android SDK. I'm running a fully updated windows 7 box. I have tried all of my USB ports, adb kill-server/adb start-server. I even created an .ini file with the hex version of the device USB/VID id (based on the HTC Sync setting, the phone shows only as Android Phone in my windows device manager. I have not yet tried switching it to disk drive), and nothing has worked. The phone's bootloader is unlocked via htcdev, but is otherwise stock. And, oddly enough, my old evo 4g which is rooted and running CM9 can be found, so I think it's got to be something with the new phone, I am just not sure what. I've been researching this over the last few days and have tried everything I have found, all to no avail. Any advice would be greatly appreciated!
Internal port is faulty. Two terminals for charging ,two for data, the data one(s) may have fractured from.the board.