Hello, recently just got a pocophone and wanted to root it but no matter how many guides i consult(Probably over 20 guides at this point) i just can't get my phone to be detected in miflash unlock.
I have tried:
Enabling USB Debugging
Enabling OEM unlock
Installing USB Drivers
Booted in fastboot mode(duh)
Moving Miunlock file to C: directory
Running Miunlock as administrator
Disabling Driver Signature Enforcement
Trying to start over afresh still isn't working as i am very sure i have followed every step but my phone is just not detected.
Interesting Notes:
My phone was actually detected ONLY ONCE in which i tried unlocking but it stopped on 50% with an error message.
Driver Installed:
Android Phone: Android Bootloader Interface (Sorry cant post pic as i'm a new user)
This is just one of the many drivers i have installed, the rest are deleted by me during a fit of rage after researching for 8 hours but still not being able to unlock the bootloader.
Does the PC you're using have a USB2 port and are you using that? Does the PC you're using have an AMD Ryzen processor?
Yes,my PC(desktop) runs on a 2600x and I use usb 3.0(unfortunately no 2.0) I have tried switching to a Intel laptop but it is still not working, I have yet to use the 2.0 port on my laptop.
Edit: I have tried using usb 2.0 on my intel laptop and it is still not working.
idkman1234 said:
Yes,my PC(desktop) runs on a 2600x and I use usb 3.0(unfortunately no 2.0) I have tried switching to a Intel laptop but it is still not working, I have yet to use the 2.0 port on my laptop.
Edit: I have tried using usb 2.0 on my intel laptop and it is still not working.
Click to expand...
Click to collapse
Try different cables.
USB 2.0, Intel PC, Win 10, Disabling driver signing, different cables. Any one of them can be the culprit.
unlock boot loader
try creating new account with new sim. add account. to in android developer options then try again in fastboot might work download software again to pc
Still doesn't work for me. I was able to connect with my phone just a while ago but now I can't.
When my phone magically connected through my desktop(ryzen). I clicked on unlock and after reaching 50%,it showed that it couldn't verify my device with unknown error(-1).
I then closed down mi unlock again and reconnected my phone to the desktop and this time the phone was not detected. I suspect this is because the phone immediately displays 'Press any key to shutdown' after showing the fastboot logo for a split second.
Any way to fix this? I heard that some people used a USB hub and it works while some say it works on Windows 7 but I really do not want to waste money buying a hub and I'm not really sure how to get my PC downgraded to Win 7.
I've read online that registering a mi account and applying for unlock takes a few days. Is it true? If so how can i check my status? Is there a wait time for my phone to be able to be able to get unlocked?
I am not talking about the 72 hours or X hours wait time. I am talking about whether there is a wait time when you first apply for unlock.
I also read online that people have to input their reason for unlocking their phone. I did not get such questions when registering.
make sure you got driver in pc work ok on windows 10 with driver and internet here link to your fix
https://forum.xda-developers.com/android/general/guide-complete-solution-one-to-unlock-t3629512
idkman1234 said:
Still doesn't work for me. I was able to connect with my phone just a while ago but now I can't.
When my phone magically connected through my desktop(ryzen). I clicked on unlock and after reaching 50%,it showed that it couldn't verify my device with unknown error(-1).
I then closed down mi unlock again and reconnected my phone to the desktop and this time the phone was not detected. I suspect this is because the phone immediately displays 'Press any key to shutdown' after showing the fastboot logo for a split second.
Any way to fix this? I heard that some people used a USB hub and it works while some say it works on Windows 7 but I really do not want to waste money buying a hub and I'm not really sure how to get my PC downgraded to Win 7.
Click to expand...
Click to collapse
AMD Ryzen will not work. That is why another member and I specifically told you to use an Intel PC.
---------- Post added at 07:04 PM ---------- Previous post was at 06:59 PM ----------
idkman1234 said:
I've read online that registering a mi account and applying for unlock takes a few days. Is it true? If so how can i check my status? Is there a wait time for my phone to be able to be able to get unlocked?
I am not talking about the 72 hours or X hours wait time. I am talking about whether there is a wait time when you first apply for unlock.
I also read online that people have to input their reason for unlocking their phone. I did not get such questions when registering.
Click to expand...
Click to collapse
When you apply for unlocking the bootloader, there is a 72 hours wait (you apply only once). No reasons are asked for. Apart from this there is no other wait time. No status check.
tnsmani said:
AMD Ryzen will not work. That is why another member and I specifically told you to use an Intel PC.
---------- Post added at 07:04 PM ---------- Previous post was at 06:59 PM ----------
When you apply for unlocking the bootloader, there is a 72 hours wait (you apply only once). No reasons are asked for. Apart from this there is no other wait time. No status check.
Click to expand...
Click to collapse
I did exactly just that on my intel laptop. I connected it to USB 2.0 port but the phone is not detected and it always displays 'Press Any key to shut down' after showing the fastboot logo for a split second.
idkman1234 said:
I did exactly just that on my intel laptop. I connected it to USB 2.0 port but the phone is not detected and it always displays 'Press Any key to shut down' after showing the fastboot logo for a split second.
Click to expand...
Click to collapse
See post #4 above. Should be an issue with drivers, cable or USB port. Use different ports and cables. Disable driver signing also before installing the drivers and install correct drivers.
I have finally managed to unlock my bootloader. All i did was i dug up my old alienware laptop(intel) and did a fresh install of drivers and it actually managed to unlock it. No disabling driver enforcement, no switching usb ports(i only used 3.0), no switching cables. What i did was right click and install android_winusb in the 'drivers' folder of the mi unlock file. For some odd reason, this did not work on my local brand intel laptop and my ryzen desktop. Thank you to those who have offered me help even though non of it worked(at least for me). I appreciate you stepping out of your way to help me.
Glad to read you've unlocked your fone. The world is out there, enjoy...
How to unlock poco f1 bootloader without mobile data connection ?
I had to root poco f1 but i was unable to unlock the bootloader because in my state mobile internet is banned and i am not able to add account in (developer options>mi unlock status>add account and device). I had added the mi account in phone with wifi connection. But while clicking the option of "add account and device" in mi unlock status, there shows that mobile data is required.
Howsoever, i added the mi account via wifi and turned on sync and all the necessary things that had to be done. But as i clicked on unlock phone in mi flash tool in pc, after 99% it failed and there showed me" add account or device in mi unlock status".
I want to get rid of this problem.
Related
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hello Everyone
I am putting my problem in this general section with the hope to ask for help to more people compared to the Mate 8 section where not a lot of people go these days.
Since a while I am not able to connect my phone to a laptop. If I connect it to a laptop it just starts charging but nothing else. I have tried everything like:
Changing Cables (tried more than 5. I dont have the original anymore)
Changing Laptops
Changing the USB port of the phone itself
Updating Drivers
Installing Hisuite (current version 5.0.3.300)
Restore phone to factory settings
Complete formatting
Updating to the latest version (Current version Nxt-L29C185B582)
Changing the USB debugging/ Connection (MTP/PTP/etc)
And what not
The problem is, it doesnt get detected on the computer and cant connect to adb as well. All I want is to unlock bootloader and Install TWRP and Magisk. I have the unlock bootloader code but no way to unlock it since I cant connect.
Can anyone help me in fixing this stupid problem ? It is getting frustrating. If there is a hardware issue, what part needs to be replaced? Any help would be appreciated.
USB connection icon on top of the phone when connecting laptop
gandotratushar said:
Hello Everyone
I am putting my problem in this general section with the hope to ask for help to more people compared to the Mate 8 section where not a lot of people go these days.
Since a while I am not able to connect my phone to a laptop. If I connect it to a laptop it just starts charging but nothing else. I have tried everything like:
Changing Cables (tried more than 5. I dont have the original anymore)
Changing Laptops
Changing the USB port of the phone itself
Updating Drivers
Installing Hisuite (current version 5.0.3.300)
Restore phone to factory settings
Complete formatting
Updating to the latest version (Current version Nxt-L29C185B582)
Changing the USB debugging/ Connection (MTP/PTP/etc)
And what not
The problem is, it doesnt get detected on the computer and cant connect to adb as well. All I want is to unlock bootloader and Install TWRP and Magisk. I have the unlock bootloader code but no way to unlock it since I cant connect.
Can anyone help me in fixing this stupid problem ? It is getting frustrating. If there is a hardware issue, what part needs to be replaced? Any help would be appreciated.
Click to expand...
Click to collapse
Go to the Settings of your phone---> About phone----> Build number tap this 7 to 8 times-----> Developers option is enabled----> back to settings ----> go to developers option ----> enable USB debugging.
When you connect to the phone to the laptop you will find an icon on top of the screen of your phone with a USB mark "like a trident", pull down the top menu and find the USB connection tab, (like changing the sim card if you intend to call through a specific card) e.g quoted, double tap the USB tab to obtain options ---> 3 options 1) MTP 2)PTP 3) USB charging only----> select the first option MTP (Media transfer protocol).
Now connect to the laptop you will find exclamation marks in the device manager of your laptop. Load the appropriate drivers on your computer and viola! this will establish connection with the device you are having. if you find difficulty in installing USB drivers, search the thread "Attempt to load USB drivers for Micromax E484 on win XP is a fiasco" in this forum. You will find the solution for USB drivers
http://forum.xda-developers.com/android/help/attempt-to-load-usb-drivers-micromax-t3696432
Regards,
689alza
Thanks for your reply
Go to the Settings of your phone---> About phone----> Build number tap this 7 to 8 times-----> Developers option is enabled----> back to settings ----> go to developers option ----> enable USB debugging.
Already Tried
When you connect to the phone to the laptop you will find an icon on top of the screen of your phone with a USB mark "like a trident", pull down the top menu and find the USB connection tab, (like changing the sim card if you intend to call through a specific card) e.g quoted, double tap the USB tab to obtain options ---> 3 options 1) MTP 2)PTP 3) USB charging only----> select the first option MTP (Media transfer protocol).
Already tried too
Now connect to the laptop you will find exclamation marks in the device manager of your laptop. Load the appropriate drivers on your computer and viola! this will establish connection with the device you are having. if you find difficulty in installing USB drivers, search the thread "Loading USB drivers in Win XP turned to be a fiasco"
Nope. Doesnt happen
When i connect with the laptop, my laptop doesnt even make that sound for the connection.
What is the model and OS version of the device and the model and OS version of the computer? According to your symptoms your phone appears to be in option 3) USB charging only. The phone will not be detected by your laptop or the like(Computer) in this mode. Merely remains in a charging state. Are you certain the option 1) is picked MTP? If the phone is not detected there appears to be some hardware failure, try another USB port to connect to the laptop. if all else fail a service technician will pinpoint the fault. It may perhaps be a data transmission failure of the devices port to the interior of the phone. This is merely an assumption.
best remedy would be a service technician.
Hope this helps
689alza
alza689 said:
What is the model and OS version of the device and the model and OS version of the computer? According to your symptoms your phone appears to be in option 3) USB charging only. The phone will not be detected by your laptop or the like(Computer) in this mode. Merely remains in a charging state. Are you certain the option 1) is picked MTP? If the phone is not detected there appears to be some hardware failure, try another USB port to connect to the laptop. if all else fail a service technician will pinpoint the fault. It may perhaps be a data transmission failure of the devices port to the interior of the phone. This is merely an assumption.
best remedy would be a service technician.
Hope this helps
689alza
Click to expand...
Click to collapse
I have tried changing the usb charging only to all possible options but it still is the same. I tested in Linux and when I connect the phone nothing shows up in the logs. It's like it's not being connected . I have tried changing the usb port itself from the phone but it remained the same.. can the flex cable be a problem ? Mate series was never launched in India so I don't have any help from the service centre. I have to order the spare from eBay.com so there is no qualified technician who can help.. that's why I have to fix it myself somehow..
Thank you for your help
gandotratushar said:
I have tried changing the usb charging only to all possible options but it still is the same. I tested in Linux and when I connect the phone nothing shows up in the logs. It's like it's not being connected . I have tried changing the usb port itself from the phone but it remained the same.. can the flex cable be a problem ? Mate series was never launched in India so I don't have any help from the service centre. I have to order the spare from eBay.com so there is no qualified technician who can help.. that's why I have to fix it myself somehow..
Thank you for your help
Click to expand...
Click to collapse
I quite doubt the cable will be the culprit as your device charges the battery while in an established connection with the laptop. As you state the phone USB port was replaced, it could be a some glitch before the USB port in the device where there is an interruption in the data transmission signal that cannot be detected by your laptop.
Could you boot your device, computer and connect the two and take a snapshot of your device (whilst connected to the laptop) and paste the same in the forum?
Perhaps visual cue could be better at dealing such mishaps.
alza689 said:
I quite doubt the cable will be the culprit as your device charges the battery while in an established connection with the laptop. As you state the phone USB port was replaced, it could be a some glitch before the USB port in the device where there is an interruption in the data transmission signal that cannot be detected by your laptop.
Could you boot your device, computer and connect the two and take a snapshot of your device (whilst connected to the laptop) and paste the same in the forum?
Perhaps visual cue could be better at dealing such mishaps.
Click to expand...
Click to collapse
Yes of course. It is connected to a computer now. You can see it getting charged but that's about it
alza689 said:
I quite doubt the cable will be the culprit as your device charges the battery while in an established connection with the laptop. As you state the phone USB port was replaced, it could be a some glitch before the USB port in the device where there is an interruption in the data transmission signal that cannot be detected by your laptop.
Could you boot your device, computer and connect the two and take a snapshot of your device (whilst connected to the laptop) and paste the same in the forum?
Perhaps visual cue could be better at dealing such mishaps.
Click to expand...
Click to collapse
Can it be something because of some wrong flash ? This problem has survived through 2 versions and 1 system upgrade through firmware finder .. and a complete format
USB trident is not seen on the device
gandotratushar said:
Yes of course. It is connected to a computer now. You can see it getting charged but that's about it
Click to expand...
Click to collapse
Your USB trident icon is not indicated on the device, If you were to receive power from the laptop the trident would be displayed on top of the screen, even for charging the battery. The power source for your device appears to from other than the laptop.
I have pasted my device after connecting to the computer and the second icon from the top left is the USB Trident icon indicating connection with my laptop. Have taken the snapshot of the menu that I was describing .
I strongly feel you have a hardware failure rather than a simple fix and would require the help of a technician (ordinary if professional is unavailable). Am skeptic you could mend that on your own unless you are proficient in electronics. This mishap is not due to flashing wrongly too, unless you have changed the stock ROM with some custom ROM which has some bug that affect the USB alone.
Take the assistance of a technician whether professional or less is my counsel
Thank you
alza689 said:
Your USB trident icon is not indicated on the device, If you were to receive power from the laptop the trident would be displayed on top of the screen, even for charging the battery. The power source for your device appears to from other than the laptop.
I have pasted my device after connecting to the computer and the second icon from the top left is the USB Trident icon indicating connection with my laptop. Have taken the snapshot of the menu that I was describing .
I strongly feel you have a hardware failure rather than a simple fix and would require the help of a technician (ordinary if professional is unavailable). Am skeptic you could mend that on your own unless you are proficient in electronics. This mishap is not due to flashing wrongly too, unless you have changed the stock ROM with some custom ROM which has some bug that affect the USB alone.
Take the assistance of a technician whether professional or less is my counsel
Thank you
Click to expand...
Click to collapse
I did flash a different rom .. but then back to stock recently.
I can do basic electronics but the if the problem lies in Mobo .. then nothing can be done .. as I don't have the spares available in India. But I would hate to lose this phone as it was a perfect fit for my needs
gandotratushar said:
I did flash a different rom .. but then back to stock recently.
Then the question of wrong flash or ROM issue does not arise
I can do basic electronics but the if the problem lies in Mobo .. then nothing can be done .. as I don't have the spares available in India.
If you do not have spares is best left alone rather than tampering with it and rendering the device useless if any untoward incidents tends to occur.
But I would hate to lose this phone as it was a perfect fit for my needs
Send to the vendor directly if you have warranty for the device stating its complaints or request your relative or friends who live in the area where you bought your phone to hand it to the vendor or service technician and bear its expenses
Click to expand...
Click to collapse
Thank you
alza689 said:
Thank you
Click to expand...
Click to collapse
Is there a way to unlock bootloader somehow without connecting to usb ? That would also solve the purpose.. I want to root it for some of the things to work and with the latest upgrade to latest version I lost the unlocked bootloader and root.. if somehow I can unlock and root .. I should be fine without the usb connection to computer.. but I have ran out of ways
Does Kingroot work for you?
I mean did u try it or u just want magisk?
If u didn't, kingroot may be able to root ur device and unlock ur bootloader, then u can flash TWRP using rasher.. & make a backup BTW...
After that, try using the adb sideload in TWRP to test ur connection with ur computer.
TWRP for ur device : (q.gs/DxuAH)
There is a way to unlock bootloader without USB via developers option.
Go to settings-----> About phone-----> Build number ( Tap this option around 7 or 8 times) till developers option is enabled------> go back to settings-----> developers option-----> OEM unlock option (Enable this option) to unlock the bootloader.
Xeedius said:
Does Kingroot work for you?
I mean did u try it or u just want magisk?
If u didn't, kingroot may be able to root ur device and unlock ur bootloader, then u can flash TWRP using rasher.. & make a backup BTW...
After that, try using the adb sideload in TWRP to test ur connection with ur computer.
TWRP for ur device : (q.gs/DxuAH)
Click to expand...
Click to collapse
Thank you for the advice.. I hadn't tried it earlier but after your suggestion I did.. kingroot says I need to unlock my bootloader to root it.. so I am back to square one..
alza689 said:
There is a way to unlock bootloader without USB via developers option.
Go to settings-----> About phone-----> Build number ( Tap this option around 7 or 8 times) till developers option is enabled------> go back to settings-----> developers option-----> OEM unlock option (Enable this option) to unlock the bootloader.
Click to expand...
Click to collapse
This gives me an frp unlock and not a phone unlock.. still not able to root
There is no FRP unlock.
gandotratushar said:
This gives me an frp unlock and not a phone unlock.. still not able to root
Click to expand...
Click to collapse
There is no FRP unlock, to circumvent FRP you need to factory reset or flash your firmware. The above quotation was to unlock the boot loader as you cannot access through your computer. Your sole option to unlock boot loader was through the above directions.
Moreover, King root application never ask for boot loader to be unlocked. Although a little unstable this is the initial program to root any device. Once you have the TWRP setup then you could switch to Super Su etc. according to your preference.
Could you paste your developers option snapshot here...
Regards,
689alza
gays
me too have this problem ( only usb port for charge and other option's not work)
and i want back to orignal system
and i want know how download orignal system (from Huawei web site) to my phone
can any one help me how
or how can fixed this problem
and i have other problem
when i try to boot to TWRP phone stay on " your device is booting now..."
so any one can help me how reinstall TWRP without PC or why this problem ??
TWRP is not installed duly on your phone
Hello! Omar Dahy,
OmarDahy said:
gays
me too have this problem ( only usb port for charge and other option's not work)
Connect your phone to your computer or laptop, a trident icon appears on your phone notification area, pull down the notifications and identify the notice as USB connection, tap twice you willk be provided with options.
and i want back to orignal system
and i want know how download orignal system (from Huawei web site) to my phone
My phone was Micromax and I am not aware of your phone's firmware, try and google or search the Xda developers forum under your phones model number for the original firmware.
can any one help me how
or how can fixed this problem
and i have other problem
when i try to boot to TWRP phone stay on " your device is booting now..."
Your phone has not installed TWRP duly, therefore it boots straight to the system. Search again in this XDA forum, with your pnone name and model number to obtain instructions
so any one can help me how reinstall TWRP without PC or why this problem ??
Click to expand...
Click to collapse
Undetected by PC. Unable to access fastboot, flashtool. "USB devices disabled"
Note 1: I purchased this device second hand in a third world country, so please don't suggest "warranty" or return or service options.
Note 2: Both my computers work perfectly fine with other devices, so please don't waste time asking questions about them. They are fine. My adb configuration is fine. Yes I've tried many, many different cables. This problem is definitely 100% with the phone. The only thing that COULD be computer-side is drivers, but once again, it was connecting normally without any drivers before the "USB devices disabled" warning. I have the latest version of everything with the latest updates. I have followed all the info in all other guides all over the internet.
When I first got this phone, I did what I always do: Enable dev options, enable OEM unlock and ADB debugging. Connected it to PC and was detected normally in My Computer like any other phone. I had no particular Sony drivers installed and no Xperia Companion, only ADB drivers.
I started looking up how to install TWRP, which is the first thing I do on any phone. For some reason, I wasn't able to access fastboot or flashmode on this phone. I tried to access them in adb, but adb wouldn't show the device, even though it appeared in My Computer, had ADB debugging enabled and USB connection type set as MTP File Transfer.
Odd. I installed Xperia Companion, which detected the phone normally, but that didn't make adb work. ̶I̶ ̶t̶r̶i̶e̶d̶ ̶i̶n̶s̶t̶a̶l̶l̶i̶n̶g̶ ̶t̶h̶e̶ ̶o̶f̶f̶i̶c̶i̶a̶l̶ ̶d̶r̶i̶v̶e̶r̶ ̶a̶s̶ ̶s̶u̶g̶g̶e̶s̶t̶e̶d̶ ̶e̶v̶e̶r̶y̶w̶h̶e̶r̶e̶,̶ ̶b̶u̶t̶ ̶f̶o̶r̶ ̶s̶o̶m̶e̶ ̶r̶e̶a̶s̶o̶n̶ ̶W̶i̶n̶d̶o̶w̶s̶ ̶w̶o̶n̶'̶t̶ ̶l̶e̶t̶ ̶m̶e̶ ̶i̶n̶s̶t̶a̶l̶l̶ ̶i̶t̶.̶ ̶I̶n̶ ̶o̶n̶e̶ ̶m̶e̶t̶h̶o̶d̶,̶ ̶i̶t̶ ̶t̶e̶l̶l̶s̶ ̶m̶e̶ ̶t̶h̶a̶t̶ ̶"̶T̶h̶i̶s̶ ̶d̶e̶v̶i̶c̶e̶ ̶i̶s̶ ̶a̶l̶r̶e̶a̶d̶y̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶b̶e̶s̶t̶ ̶d̶r̶i̶v̶e̶r̶"̶,̶ ̶a̶n̶d̶ ̶t̶h̶e̶ ̶H̶a̶v̶e̶ ̶D̶i̶s̶k̶ ̶m̶e̶t̶h̶o̶d̶ ̶t̶e̶l̶l̶s̶ ̶m̶e̶ ̶t̶h̶a̶t̶ ̶"̶T̶h̶i̶s̶ ̶d̶r̶i̶v̶e̶r̶ ̶i̶s̶n̶'̶t̶ ̶c̶o̶m̶p̶a̶t̶i̶b̶l̶e̶ ̶w̶i̶t̶h̶ ̶t̶h̶i̶s̶ ̶d̶e̶v̶i̶c̶e̶"̶,̶ ̶a̶n̶d̶ ̶i̶n̶ ̶b̶o̶t̶h̶ ̶c̶a̶s̶e̶s̶ ̶t̶h̶e̶ ̶i̶n̶s̶t̶a̶l̶l̶a̶t̶i̶o̶n̶ ̶f̶a̶i̶l̶s̶.̶
Edit: I successfully installed flashtool drivers as well as the official Sony driver. Still unsuccessful.
I kept reconnecting to different ports and different cables to see if it helps, but I started getting a strange warning on my phone that I've never seen before: "USB devices disabled for using too much power". I ignored it and clicked ok. This showed up twice or 3 times. After that, the phone stopped being detected by My Computer and also Xperia Companion. Windows started warning me upon connecting that "USB Device not recognized".
A̶l̶l̶ ̶o̶f̶ ̶t̶h̶i̶s̶ ̶w̶a̶s̶ ̶y̶e̶s̶t̶e̶r̶d̶a̶y̶.̶ ̶I̶ ̶f̶o̶r̶g̶o̶t̶ ̶a̶b̶o̶u̶t̶ ̶i̶t̶ ̶a̶n̶d̶ ̶k̶e̶p̶t̶ ̶u̶s̶i̶n̶g̶ ̶t̶h̶e̶ ̶p̶h̶o̶n̶e̶ ̶n̶o̶r̶m̶a̶l̶l̶y̶.̶ T̶o̶d̶a̶y̶,̶ ̶I̶ ̶d̶e̶c̶i̶d̶e̶d̶ ̶t̶o̶ ̶t̶r̶y̶ ̶a̶g̶a̶i̶n̶,̶ ̶b̶u̶t̶ ̶e̶v̶e̶r̶y̶t̶h̶i̶n̶g̶ ̶s̶e̶e̶m̶e̶d̶ ̶t̶o̶ ̶b̶e̶ ̶t̶h̶e̶ ̶s̶a̶m̶e̶ ̶s̶t̶i̶l̶l̶.̶ ̶I̶ ̶d̶e̶c̶i̶d̶e̶d̶ ̶t̶o̶ ̶t̶r̶y̶ ̶o̶n̶e̶ ̶m̶e̶t̶h̶o̶d̶ ̶t̶h̶a̶t̶ ̶I̶ ̶t̶h̶o̶u̶g̶h̶t̶ ̶w̶a̶s̶ ̶p̶r̶e̶t̶t̶y̶ ̶s̶t̶u̶p̶i̶d̶ ̶w̶h̶e̶n̶ ̶I̶ ̶f̶i̶r̶s̶t̶ ̶c̶a̶m̶e̶ ̶a̶c̶r̶o̶s̶s̶ ̶i̶t̶,̶ ̶b̶u̶t̶ ̶a̶t̶ ̶t̶h̶i̶s̶ ̶p̶o̶i̶n̶t̶ ̶I̶ ̶w̶a̶s̶ ̶o̶u̶t̶ ̶o̶f̶ ̶o̶p̶t̶i̶o̶n̶s̶ ̶s̶o̶ ̶I̶ ̶f̶i̶g̶u̶r̶e̶d̶ ̶w̶h̶a̶t̶ ̶t̶h̶e̶ ̶h̶e̶c̶k̶.̶ ̶I̶ ̶d̶i̶s̶a̶b̶l̶e̶d̶ ̶A̶D̶B̶ ̶d̶e̶b̶u̶g̶g̶i̶n̶g̶,̶ ̶O̶E̶M̶ ̶u̶n̶l̶o̶c̶k̶ ̶a̶n̶d̶ ̶d̶e̶v̶e̶l̶o̶p̶e̶r̶ ̶o̶p̶t̶i̶o̶n̶s̶.̶ ̶ ̶T̶h̶e̶ ̶p̶h̶o̶n̶e̶ ̶c̶o̶n̶t̶i̶n̶u̶e̶d̶ ̶t̶o̶ ̶b̶e̶ ̶u̶n̶d̶e̶t̶e̶c̶t̶e̶d̶,̶ ̶s̶o̶ ̶I̶ ̶d̶e̶c̶i̶d̶e̶d̶ ̶t̶o̶ ̶r̶e̶s̶t̶a̶r̶t̶ ̶t̶h̶e̶ ̶p̶h̶o̶n̶e̶.̶ ̶I̶t̶ ̶b̶o̶o̶t̶s̶ ̶c̶o̶m̶p̶l̶e̶t̶e̶l̶y̶ ̶a̶n̶d̶ ̶n̶o̶r̶m̶a̶l̶l̶y̶,̶ ̶b̶u̶t̶ ̶u̶p̶o̶n̶ ̶e̶n̶t̶e̶r̶i̶n̶g̶ ̶m̶y̶ ̶p̶i̶n̶ ̶c̶o̶d̶e̶,̶ ̶i̶t̶ ̶c̶r̶a̶s̶h̶e̶s̶ ̶a̶n̶d̶ ̶r̶e̶b̶o̶o̶t̶s̶.̶ ̶T̶h̶e̶ ̶f̶u̶r̶t̶h̶e̶s̶t̶ ̶I̶'̶v̶e̶ ̶b̶e̶e̶n̶ ̶a̶b̶l̶e̶ ̶t̶o̶ ̶g̶e̶t̶ ̶i̶t̶ ̶w̶a̶s̶ ̶t̶o̶ ̶r̶e̶a̶c̶h̶ ̶m̶y̶ ̶h̶o̶m̶e̶ ̶s̶c̶r̶e̶e̶n̶ ̶(̶b̶y̶ ̶d̶i̶s̶a̶b̶l̶i̶n̶g̶ ̶W̶i̶-̶F̶i̶ ̶a̶n̶d̶ ̶m̶o̶b̶i̶l̶e̶ ̶d̶a̶t̶a̶,̶ ̶n̶o̶t̶ ̶s̶u̶r̶e̶ ̶i̶f̶ ̶t̶h̶a̶t̶ ̶m̶a̶d̶e̶ ̶a̶ ̶d̶i̶f̶f̶e̶r̶e̶n̶c̶e̶)̶,̶ ̶b̶u̶t̶ ̶t̶h̶e̶n̶ ̶i̶t̶ ̶c̶r̶a̶s̶h̶e̶s̶ ̶a̶g̶a̶i̶n̶.̶ ̶A̶n̶y̶ ̶a̶t̶t̶e̶m̶p̶t̶ ̶t̶o̶ ̶a̶c̶c̶e̶s̶s̶ ̶S̶e̶t̶t̶i̶n̶g̶s̶ ̶i̶n̶s̶t̶a̶n̶t̶l̶y̶ ̶m̶a̶k̶e̶s̶ ̶i̶t̶ ̶c̶r̶a̶s̶h̶,̶ ̶a̶l̶t̶h̶o̶u̶g̶h̶ ̶a̶c̶c̶e̶s̶s̶i̶n̶g̶ ̶s̶p̶e̶c̶i̶f̶i̶c̶ ̶s̶e̶t̶t̶i̶n̶g̶s̶ ̶m̶e̶n̶u̶s̶ ̶t̶h̶r̶o̶u̶g̶h̶ ̶Q̶S̶ ̶(̶l̶i̶k̶e̶ ̶m̶o̶b̶i̶l̶e̶ ̶d̶a̶t̶a̶)̶ ̶o̶p̶e̶n̶ ̶f̶i̶n̶e̶,̶ ̶b̶u̶t̶ ̶i̶t̶ ̶s̶t̶i̶l̶l̶ ̶c̶r̶a̶s̶h̶e̶s̶ ̶a̶f̶t̶e̶r̶ ̶a̶ ̶c̶o̶u̶p̶l̶e̶ ̶o̶f̶ ̶s̶e̶c̶o̶n̶d̶s̶.̶
Edit: Reboot has been fixed with a factory reset via Support > System > Factory reset during the short uptime of the device before it reboots.
This phone is 100% stock, Oreo, latest updates. Zero root exploit attempts have been made. I activated Substratum's Andromeda via PC but Substratum still told me that it didn't work, so I stopped trying. I also side-loaded some APKs (all trusted, none of which on the system partition), but that's about it.
I've also tried connecting it to my laptop with no difference. The exact same behavior, so it's clearly the phone itself.
Clearly, the key to all of this is finding a way to access fastboot and flashmode, but for the life of me I can't get either to work. I follow the instructions and get a red LED that gets stronger if I keep holding down the VOLdwn button and the Sony splash screen followed by the charging animation. VOLup never does anything, it boots normally, unless the power button is also pressed which makes it vibrate 3 times, apparently signaling that the device was powered off.
Also, figuring out why the charging port ("USB Devices") seems to have been disabled (as per the warning message) and how to re-enable it. From what I've read, this typically happens when moisture is detected in the charging port and is done to protect the phone from over-voltage. However I have not used this phone anywhere near water since I've gotten it. And it was initially being detected normally.
I saw some great guides made by @FoxTheLegend and @YasuHamed for this phone and I was hoping they'd be able to lend their experience to help me figure this out. I've never been completely locked out of a device like this in a way that I was completely unable to solve, and I've dealt with Samsung devices with FRP and the 7 day thing.
Update: I installed flashtool drivers, but still not having any luck getting into fastboot or flash mode. The device still shows up as not recognized even when just charging. Same behavior is exhibited in safe mode.
Good morning sir, @Ace2213
thank you for the detailed Recital of your observation but frankly the KEY info which is required for me to make any observation is missing
1. Windows Version ? Win7 x64/32x ?? , w10 ?
2. firewall status? which antivirus/internet security running? or in win10, security essentials were disabled or not?
3. if win10 , has digital driver signatures were put to sleep? or not?
4. flasthtool versions?, drivers installation? , google usb drivers? xperiax Motherboard driver from developer.sonymobile.com ?
5. google adb & minimal fastboot version?
6. Xperia X running on which Stock Version? (Oreo/Nougat) ???
7. in xperia X under services menu > configuration, Unlocking status is allowed or not? but ...
8. as you said you bought it second hand, is the device is already UNLOCKED? & when you boot do u see "THIS DEVICE is UNLOCKED and CANNOT BE TRUSTED" warning from sony for 5 seconds before xperia splash screen?"
my guess is if the device is already unlocked by the time you made purchase, alot have had might happend to it by previous user(s) which ofcourse something mystry now!
so now if the device is totally bricked and non responsive try ..
1. press volume up and power keys for 15 seconds, you should feel 3 jerks (after 1 jerk at 5th second) and this will force device to force shutdown.
2. try installing fresh drivers (for everything) and flash the stock firmware) via flashtool ( read guide thoroughly, as there are many details)
but
if device is totally dead and doing nothing! then do the #RUBBER #BAND trick
1. tie rubber band across Xperia X, in a way that Volume DOWN key is pressed 100% and keep it overnight,, this will force battery drain, & Motherboard to reset
2. after 36 hours , plug mobile to wall charger and leave it for a 24hrs,,,, later see if red led blinks! or appears ,,
3. keep charging , once red led goes off, NOW is the time to connect xperia x to flashmode and flash stock firmware via flashtool!!!
U
YasuHamed said:
1. Windows Version ? Win7 x64/32x ?? , w10 ?
Click to expand...
Click to collapse
Win10 x64 with latest updates, both computers.
YasuHamed said:
2. firewall status? which antivirus/internet security running? or in win10, security essentials were disabled or not?
Click to expand...
Click to collapse
Windows Firewall and I'm guessing Security Essentials are enabled (Should I disable?). No AV or 3rd party security on either computer.
YasuHamed said:
3. if win10 , has digital driver signatures were put to sleep? or not?
Click to expand...
Click to collapse
Admittedly, I only figured out this part after I made the post, so now flashtool drivers have successfully been installed.
YasuHamed said:
4. flasthtool versions?, drivers installation? , google usb drivers? xperiax Motherboard driver from developer.sonymobile.com ?
Click to expand...
Click to collapse
Latest version of flashtool from the website. I installed the first 2 "common" drivers and all Z device drivers (like you suggested on another post). I tried to search for Google drivers, but for Sony, they sent me back to the Sony website for the official driver, which I have "installed", appearing constantly as "Sony sa0114 ADB Interface Driver" with Error Code 10. I'm guessing "motherboard" is the official Sony driver?
YasuHamed said:
5. google adb & minimal fastboot version?
Click to expand...
Click to collapse
Latest, from xda thread.
YasuHamed said:
6. Xperia X running on which Stock Version? (Oreo/Nougat) ???
Click to expand...
Click to collapse
Oreo. I know I need to downgrade to MM.
YasuHamed said:
7. in xperia X under services menu > configuration, Unlocking status is allowed or not?
Click to expand...
Click to collapse
BL Unlocking allowed, yes.
YasuHamed said:
8. as you said you bought it second hand, is the device is already UNLOCKED? & when you boot do u see "THIS DEVICE is UNLOCKED and CANNOT BE TRUSTED" warning from sony for 5 seconds before xperia splash screen?"
Click to expand...
Click to collapse
No. People are not very tech savvy here and are scared of root.
I cannot use fastboot or flashmode. The result of connecting the cable while pressing down ANY button is the same result as connecting the cable without any button. It almost seems like it doesn't recognize the button presses at all. But PWR+VLUP does work and vibrates 3 times.
Are you familiar with the "USB devices disabled for using too much power" message? I feel like this is a key to understanding the problem.
The other breakthrough would be figuring out why I cannot enter fastboot or flashmode.
Another big question is why my phone is restarting by itself now after I disabled developer options. Did I trip dm-verity or some security thing?
- on win10 when digital signature verification is off along with firewall and security essentials, win10 allows adb/fastboot connections. if you have any other droid, try making connection. if windows fails then its not xperia X you whould be focusing on.
- since you selected on first two of xperia z drivers from flasthool given setup, i would suggest you to rerun it and install all of them! just incase
- also see this https://developer.sony.com/file/download/xperia-x-driver/
- for random reboots issue, reset your device (factory reset) (wipe all data)
- since boot it locked you can repair the device from Xperia companion
- try different usb cable ( ironically / comically, sony's own give cable usually don't connect with flashtool, ) i always use xaiomi or samsung cable to make test connection!
- if device jerks that amazing sign! device is not hard bricked! it might be soft bricked due to some software error! or attempts to root etc
- downgrading to MM to save DRM KEYS is HIGHLY RECOMENDED
but since
- the device is now almost 4 years old and have all of the possible updates! if you don't have drmkeys saved! it doesnt matter! but then if you wana give/sell this device in your country tommorow , for better deal you must relock the bootloader and you need drmkeys to relock the bootloader!
YasuHamed said:
- if you have any other droid, try making connection. if windows fails then its not xperia X you whould be focusing on.
Click to expand...
Click to collapse
My old Samsung J5 Prime worked fine with adb on both devices with all the same settings. The problem is the phone, for sure.
YasuHamed said:
- since you selected on first two of xperia z drivers from flasthool given setup, i would suggest you to rerun it and install all of them! just incase
Click to expand...
Click to collapse
I installed the first two common ones, and ALL the Z ones.
YasuHamed said:
- also see this https://developer.sony.com/file/download/xperia-x-driver/
Click to expand...
Click to collapse
That's the official driver that I'm talking about.
YasuHamed said:
- for random reboots issue, reset your device (factory reset) (wipe all data)
Click to expand...
Click to collapse
I can't, without access to Settings (the phone doesn't stay on long enough) and no adb, fastboot or flashtool or Xperia Companion.
YasuHamed said:
- since boot it locked you can repair the device from Xperia companion
Click to expand...
Click to collapse
Xperia Companion doesn't detect it. That's the whole point.
YasuHamed said:
- try different usb cable ( ironically / comically, sony's own give cable usually don't connect with flashtool, ) i always use xaiomi or samsung cable to make test connection!
Click to expand...
Click to collapse
I've tried almost 20 cables so far, including Samsung and Motorola cables.
YasuHamed said:
- if device jerks that amazing sign! device is not hard bricked! it might be soft bricked due to some software error! or attempts to root etc
Click to expand...
Click to collapse
Ok but how to fix it?
YasuHamed said:
- downgrading to MM to save DRM KEYS is HIGHLY RECOMENDED
Click to expand...
Click to collapse
I don't really care about DRM keys, I just want TWRP.
So no idea about the USB port being disabled? Or why I'm unable to access fastboot and flash mode?
Ace2213 said:
My old Samsung J5 Prime worked fine with adb on both devices with all the same settings. The problem is the phone, for sure.
I installed the first two common ones, and ALL the Z ones.
That's the official driver that I'm talking about.
I can't, without access to Settings (the phone doesn't stay on long enough) and no adb, fastboot or flashtool or Xperia Companion.
Xperia Companion doesn't detect it. That's the whole point.
I've tried almost 20 cables so far, including Samsung and Motorola cables.
Ok but how to fix it?
I don't really care about DRM keys, I just want TWRP.
So no idea about the USB port being disabled? Or why I'm unable to access fastboot and flash mode?
Click to expand...
Click to collapse
sounds like i should get hold of your device to do RND ....
it will be challanging!
at this point i think, (assuming) that the usb port is faulty! it charges for sure but data transfer is not happening.
this happens when local shops repairs usb port if user has damaged it (damage can be usb wire head hard bent while it was plugged it! something that has made port faulty)
can you transfer files to/from device? if no then this might be the case
i am running out of options
YasuHamed said:
can you transfer files to/from device?
Click to expand...
Click to collapse
At the beginning, when the device was detected over USB, I transfered files to\from it. Now, I'm not sure
Like I said, it gave me warning about "USB devices disabled" RIGHT BEFORE it stopped being recognized
Anyone else? I really need my phone back asap since I use it for work
Is there another way to factory reset? In my 2-5 seconds I have inside my phone, I put the Xperia Support app on the home screen and keep restarting to see if I can factory reset within the time limit. Support > System > Factory Reset > Factory Reset > Reset. Powering off the device between boots makes it last a bit longer, but still not enough. The farthest I can get is to entering my pin to confirm factory reset. I enter it, click enter and everything freezes again.
Could this be hardware related? The top right corner gets a bit warm and this whole situation is starting to remind me of the Nexus 5X. This is also a hot country. Maybe if I try using it inside a freezer I'll be able to factory reset.
If not, is there another way to factory reset that would be faster to access through the system? Or an easy key combination or hardware action (like disconnecting a component)? This phone doesn't look easy to disassemble though
If I can factory reset I should at least (hopefully) fix the bootloop and be able to re-enable dev options, OEM unlock and ADB debugging.
UPDATE: I INITIATED THE FACTORY RESET! I was fast enough using the above steps and triggered it. The phone reset and the reboots finally stopped. The OEM unlock option is disabled, which means I was right. I did trip a security feature. In Samsung devices, when this happens, you need to wait 7 days for the option to reappear. Is there a workaround for Xperia devices?
Update: I was able to enable OEM unlocking by long pressing on the option.
I tried to access fastbood and flashmode, same as before. I connected it to the PC in normal mode and the PC recognized it, configured it then showed "Xperia X". The phone prompted me to install Xperia Companion. I clicked install and it opened the Xperia Companion on my PC which was already installed, but it didn't detect the phone. Windows still saying "device not recognized". Still no "USB Connection Type" notification. USB Connection still disabled under Settings > Connectivity > USB, saying "Not Connected".
I noticed the tip of the charger getting very warm while charging (maybe because it's loose and keeps coming off?) and the bottom of the phone near the charging port sort of seems warm on the inside.
I'm using Motorola's Turbo Wall charger. Is it possible that the current is too high? My device charged to 94% over USB while I was trying to fix it yesterday, so it clearly has no issue with low-watt charging.
The reason I'm mentioning it is because I've read that Sony can disable "USB devices" if moisture is detected to protect from over-voltage. Is it possible that this happened in my case even without moisture, but simply because a too-powerful charger was used?
Did you get any solvings for ur Xperia X issue?
Ace2213 said:
I noticed the tip of the charger getting very warm while charging (maybe because it's loose and keeps coming off?) and the bottom of the phone near the charging port sort of seems warm on the inside.
I'm using Motorola's Turbo Wall charger. Is it possible that the current is too high? My device charged to 94% over USB while I was trying to fix it yesterday, so it clearly has no issue with low-watt charging.
The reason I'm mentioning it is because I've read that Sony can disable "USB devices" if moisture is detected to protect from over-voltage. Is it possible that this happened in my case even without moisture, but simply because a too-powerful charger was used?
Click to expand...
Click to collapse
Greeting dude,
My friend have Sony Xperia X Dual (F5122) phone, and about 2 months ago he got problems with sound (phone doesn't play any sound and record voices, sometimes restarting phone helps, but only for a couple hours ) i guessed that problem with OS because he was step by step upgrading Android from 6.0 till 8.0 and then got this problem. By problem with sound he got "Warranty Time Service" message in top of phone. Then i suggested him to fully reinstall OS, i have read instruction how to flashh phone, but i got same issue as you. I couldn't put phone to fastboot, it just charging, that's all. Computer doesn't recognize him like any new device. I used almost 5 different cables that i use for my Samsung Galaxy phone. All cable are workable and many times i flash and tranfer datas with them. I don't know really how to fix this issue.
I was able to get a screenshot of this error. Happened while using a Motorola 2.1A quick charger. Also came up a couple of times before it stops, but the phone was undetected before and after.
I'm honestly disappointed in the lack of community support for this device. I'm going to sell it and get an XZ1. Hopefully that one is better supported. If not, at the very least it runs Pie and will run Q.
I purchased a Pixel 6 advertised as unlocked, but the OEM unlock option was greyed out in Developer Tools. I read somewhere that giving it the OTA update for at least June 2022 would unlock it, so I set out to do that.
After many issues trying to get the computer and phone to communicate, I found I should just use the ADB 1.0.32 binary (Linux), then try a combination of killing ADB, unplugging the phone, plugging it back in, starting ADB, etc., etc. until there is no longer "offline", "no device", or "unauthorized" shown. Eventually, I got it to communicate once it recognized the phone as being in "sideload" status.
So, after running `./adb_Linux sideload oriole-ota-sq3a.220705.003-17fec7eb.zip`, it finally did something. Except, it was stuck at, "Verifying update package..." No matter how many times I reach this point, no matter how many minutes or hours I wait, nothing happens.
Any ideas? I couldn't find any solutions or similar problems posted anywhere.
Since you're mucking around with ota's, it sounds like you are deliberately keeping it disconnected from the network, otherwise it would prompt you with an update almost immediately and there would be no need for this.
In order for the unlocking switch to be enabled, the phone MUST be connected to the network.
Also be CERTAIN that your device is a Pixel 6 and not a Pixel 6a. The 6a is the one that needs a particular update version in order for unlocking to work due to a bug. The 6 will unlock just fine on factory firmware. Assuming that you have a 6a, this would explain why trying to install "oriole" firmware would fail for you since it is a DIFFERENT PHONE.
So I take it no one has found a solution for not connecting it to the network in order to unlock it? There have been some workarounds for other devices, so I'm just asking.
Zakku said:
So I take it no one has found a solution for not connecting it to the network in order to unlock it? There have been some workarounds for other devices, so I'm just asking.
Click to expand...
Click to collapse
I don't see it as a huge issue in need of a resolution. Google does NOT blacklist you in any way for unlocking the bootloader, and they already know all of the identifying codes on every phone anyway so its not like you're keeping any information from them. Just don't put a sim card in it before unlocking it, and if you're worried they will connect the phone with your IP address, use a VPN or public AP.
USB C to USB 2.0 will work. USB C to C will not, ADB does not have the proper protocols to work with USB C. I have tried with myself. My computer has Gen2 3.1 USB C. Transferring files between are fast. But when sideload mode, it doesn't work. After investigating this issue, it was ADB not the computer nor the phone. Finally got it work once I put it in a 2.0 USB.
nerdsquadmember1 said:
USB C to USB 2.0 will work. USB C to C will not, ADB does not have the proper protocols to work with USB C. I have tried with myself. My computer has Gen2 3.1 USB C. Transferring files between are fast. But when sideload mode, it doesn't work. After investigating this issue, it was ADB not the computer nor the phone. Finally got it work once I put it in a 2.0 USB.
Click to expand...
Click to collapse
What are you talking about? And what does this have to do with this thread? And where are you coming up with this nonsense?
96carboard said:
What are you talking about? And what does this have to do with this thread? And where are you coming up with this nonsense?
Click to expand...
Click to collapse
His comments seem to have a lot to do with this thread. Clearly, at least to me, he tried sideloading and had a problem. He was simply relaying what he tried to fix it.
nerdsquadmember1 said:
USB C to USB 2.0 will work. USB C to C will not, ADB does not have the proper protocols to work with USB C. I have tried with myself. My computer has Gen2 3.1 USB C. Transferring files between are fast. But when sideload mode, it doesn't work. After investigating this issue, it was ADB not the computer nor the phone. Finally got it work once I put it in a 2.0 USB.
Click to expand...
Click to collapse
Clearly there is something to that... I had my Pixel 6 Pro sit at verifying (on phone screen) and 0% (in cmd window) for over an hour before i found this helpful comment. Killed the process (CTRL+C), then force rebooted into recovery (Power + VolUP) without trying to start the device because there was already an "install failed dont reboot" warning and then plugged it into the last remaining USB 2.0 port. There, the verification was done in 101 seconds and the flashing started when the cmd window hit about 50%.
The Pixel 6 Pro is just rebooting into Android 13 while typing this message.
Thank you for pointing this problem out.
[EDIT]
I might want to add that this happened on a Gigabyte Z390 board that has mostly USB 3 and one USB C plus just one USB 2.0 port out front. I could imagine this not applying to all USB C ports on PCs. Maybe its just because of the older Intel platform or the active (with its own controller chip inside) USB-PD cable i was using.
Yep same thing on my XPS 9710 which only has TB4 ports: using a TB4 to USB A adapter and then an A to C cable worked, stupid of Google to not include native C support since they have been using C as the standard since 2016 with the Nexus 6P lol.
I think the USB issue might be more of a combination of thighs, since when I tried to sideload through classic C to A cable it was really slow and basically got stuck at like 5%, then I used "higher quality" C to C cable and the update was done in minute.
Sneakyghost said:
Clearly there is something to that... I had my Pixel 6 Pro sit at verifying (on phone screen) and 0% (in cmd window) for over an hour before i found this helpful comment. Killed the process (CTRL+C), then force rebooted into recovery (Power + VolUP) without trying to start the device because there was already an "install failed dont reboot" warning and then plugged it into the last remaining USB 2.0 port. There, the verification was done in 101 seconds and the flashing started when the cmd window hit about 50%.
The Pixel 6 Pro is just rebooting into Android 13 while typing this message.
Thank you for pointing this problem out.
[EDIT]
I might want to add that this happened on a Gigabyte Z390 board that has mostly USB 3 and one USB C plus just one USB 2.0 port out front. I could imagine this not applying to all USB C ports on PCs. Maybe its just because of the older Intel platform or the active (with its own controller chip inside) USB-PD cable i was using.
Click to expand...
Click to collapse
Yep. This the bloody fix! Exact same problem. Stuck at verifying at 2% for the September patch. I switched USB ports from my new laptop to the dock itself and finally, sideloaded it. Does ADB need to be updated to work with USB 3.0?
So I have been trying to root my Moto G Power 2021 all day. I have been following the guide to using Magisk the non-twrp way, and I keep hitting the same snag over and over again. So far, I have successfully unlocked the bootloader, downloaded and installed the latest Magisk apk (Magisk25.2.apk) form the github page, and downloaded and installed the official Rescue and Smart Assistance (LMSA) on my computer. The problem that I am having is that whenever I plug my phone into my computer while I have RSA open, it asks me to authorize the computer to use it, but nothing opens on my phone to give me that option.
Before I am asked, yes I have Developer tools unlocked, the OEM is unlocked already (As I said above), and I have made sure that USB Debugging was allowed.
Please, tell me where I'm going wrong with this if anywhere?
The only other information I can think to add is that my phone IS running Android 11, but I'm unsure if that matters as I have seen other guides that explain how to root on Android 11.
Thanks in advance for any information that can be given!
First thing: Have you installed the specific Motorola USB Drivers on your PC?
Link: https://motorola-global-portal.cust...can-i-download-the-usb-drivers-for-my-device?
sdembiske said:
First thing: Have you installed the specific Motorola USB Drivers on your PC?
Link: https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481/~/where-can-i-download-the-usb-drivers-for-my-device?
Click to expand...
Click to collapse
Yes I did. I also tried uninstalling and reinstalling it when you linked it in case I didn't have it installed correctly, and that still did not work.
The below image is what I keep getting when I attempt to connect to RSA with my phone, and nothing at all like that shows up on my phone to verify.
Had you previously authorized the phone on that PC, i.e., using adb, etc? If so, you may not have to authorize it again. Have you actually tried to do anything with RSA or just wondered why the authorization notification doesn't show on your phone? Does the USB debugging pop-up show in the status bar on your phone when you're connected? If so, you're connected and were already authorized.
Other than that, your antivirus/firewall software may be blocking the connection and you'll have to allow the app to connect to the phone there. May also want to check that your USB cord isn't the issue by trying another one with data capabilities.
Please see the N.B. in my signature below.
Thanks! I'll give that a shot and update when I've got a chance. I don't believe it's the USB cable since it's the cable that came with the phone, so I'll try the antivirus/firewall software side of things first.
Small edit:
I forgot to actually answer your question before. No, I hadn't already authorized this computer, as this is actually a pretty new computer (Only a few months old at this point). The USB debugging shows up at the top of my phone yes, but RSA won't do anything unless I authorize it, which gives me conflicting impressions that the phone seems to think it's verified the computer, but the computer and program don't see the verification.
sdembiske said:
Had you previously authorized the phone on that PC, i.e., using adb, etc? If so, you may not have to authorize it again. Have you actually tried to do anything with RSA or just wondered why the authorization notification doesn't show on your phone? Does the USB debugging pop-up show in the status bar on your phone when you're connected? If so, you're connected and were already authorized.
Other than that, your antivirus/firewall software may be blocking the connection and you'll have to allow the app to connect to the phone there. May also want to check that your USB cord isn't the issue by trying another one with data capabilities.
Please see the N.B. in my signature below.
Click to expand...
Click to collapse
Thank you! That worked! I was able to get it sorted out, AND following the root guide, I was able to get my phone rooted too! Thank you very much again!
@Cloud557 How did you unlock bootloader? I have cricket moto g power 2021 but I checked with Motorola and apparently this model cannot be unlocked? Thanks