Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
There does seem to be a known problem with the Mi Unlock tool not being able to communicate properly with the system drivers. There are some tips for getting it working on this thread:
https://forum.xda-developers.com/t/...ol-cannot-detect-phone.3663139/#post-73566526
If that post doesn't solve the problem then try reading through the later posts in that thread.
Sorry for the late reply, I did the suggestion and it worked! Thank you for the help.
My goal was to flash the indonsian rom of the device onto and I had a bit of a problem last night I ended up sending it into a bootloop because the connection wasn't stable from the computer to the phone, I just woke up today and tried it again on a different computer and a brand new cable and the connection wasn't cutting out at all. I put it in fastboot and succesfulyl flashed it. I can't thank you enough for the help.
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
The Spike Man said:
I just need to know if I need to close this thread or something now that my issue is complete. I'm new around here so I don't know if I shoudl do that.
Click to expand...
Click to collapse
No need, your experience may be shared by others in which case it will be useful to have somewhere to talk about it
The Spike Man said:
Hi,
I am experiencing issues with my Poco M4 Pro 4G and trying to unlock the bootloader. What I am currently doing is the following;
I enabled developer options, enabled usb debugging and OEM unlocking. I went to unlock status hit agree and hit pair and have waited 7 days for the timer to run out
I shut down the phone and then enter fastboot by holding the volume down button and the power button at the same time.
I downloaded the mi flash unlock tool from here and I logged in using the same account as on the phone, and got up to this screen.
View attachment 5681651
I then connect the phone which currently has the fastboot logo on to the computer but the button stays grey.
The following is what I have done;
I have installed adb tools. When the phone is booted and is connected to my computer I can see it via "adb devices" in CMD as admin. I can even send it to fastboot mode by "adb reboot fastboot"
I have installed the qualcomm drivers but I am unsure if they are the correct ones.
I have tried with different cables.
I have tried with different PCs.
The computer that I am using mainly to try and unlock the bootloader is a laptop and the specs are as follows;
Model: GP72 2QE Leopard Pro
Intel Core i7 5700HQ
16GB RAM
The other systems that I have tried are almost identifically specced both are AMD based on X570 Mobo and a Ryzen 7 3700X
Click to expand...
Click to collapse
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
aariss said:
Are u sure m4 pro 4g is qualcom ?
Thought is mediatek
Click to expand...
Click to collapse
It is mediatek.
Related
Hi all,
think i bricked/ defected my Pace today. The idea was a mod with german language so i began to read here at xda for info. I'm on iOS now but modding on Android is nothing new for me, i modded some mobiles before, everthing workedtill today. I unlocked the bootloader and installed the mod, something went wrong i think, maybe i tried an incorrect image or something else, i don't know. After installing the watch wanted to update via OTA an after that it was shown as a Stratos in the Huami Amazfit Tool, sn was NULL an so on. The watch booted to os but the app was not able to read the QS Code for connection, touch doesn't work...
I can't say which ways i tried the last 6 to 8 hours to repair it and now i'm sure there is no bootloader/ software anymore on the watch. It starts with Amazfit Logo and stops with "No Command" & and the triangle. The only way to connect is in Fastboot, which shows chinese signs at the bottom of the display. There is no connection possible on ADB or otherwise.
Is there any way to get back the software on my watch? Maybe download mode which starts from my pc or something else? I'm on win 10 here, there is no linux machine or something else.
Thanks for reading
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Quinny899 said:
If you can get to fastboot and recovery, you have not deleted the bootloader.
Follow this guide: https://forum.xda-developers.com/smartwatch/amazfit/tutorial-unbrick-huami-amazfit-t3547300
Click to expand...
Click to collapse
Hi,
i tried this yesterday for about 10 to 15 attempts, but after step 4 there is no adb connection for step 5 and adb commands doesn't work. Getting the watch in fastboot is no problem anymore for me after last night
You have flashed Stratos firmware on your Pace, that's why touch didn't work. If the unbrick tutorial didn't work for you, then you should check your drivers: both drivers for adb and fastboot (they are different) should be installed and working properly. Sometimes you must re-connect the watch for the computer to detect it when the mode change, I usually keep Device Manager when I am using Windows to check this.
Or try AmazeROM installer, it has an option to start flashing from fastboot and it will guide you through the process.
Hi all,
sorry for my later post but under week i have no time for doing things like this here.
I checked adb and fastboot on the pc, installed system wide and works, fastboot drivers seems to be ok, but i have no idea how to check adb drivers. It's all the same, if i try this guide https://forum.xda-developers.com/sma...azfit-t3547300 or if i install amazeos with installer. The watch is recognized in fastboot but afterwards switching to adb there is no new connection, it's still in fastboot and does not switch to anything, i can restart it when amazeos installer script runs but nothing happens and if i let it run for about three hours the watch is still in fastboot and nothing happens there. In the device manager i see only an ADB Testing Device when in fastboot connected, on adb nothing happens there.
I tried everything on a clean win 7 machine, in this case the watch won't even recognize, so i could't run an installer or try to use the unbrick guide.
Just for information, it was Stratosfied which killed my watch in my mistake, but after that i think i deleted all with Amazfit Tools for doing the worst case for me here an unplugged it before reinstalling something else.
I attached some pics of the watch, first is after starting and directly after Amazfit logo, second is in fastboot with this method https://forum.xda-developers.com/sm...tches/amazfit-boot-fastboot-directly-t3546829, Point two there is not reachable, only point one fastboot, but in it i can't do anything though.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And for information, every fastboot command will be determind with "The command is not allowed"
Heyo
Following situation:
I tried to root and flash my old Sony Xperia Z3 compact which I have been using as an mp3 player. I successfully did so (I think), however when I wiped my data to flash to linage os, it gave me error 7. I assumed it was because my TWRP version was way out of date so I updated that, and hit "reboot into recovery" to activate the new twrp version.
Unfortunately the phone didn't boot into recovery and just wound up stuck at the sony screen without anything else since no OS is installed.
I can't boot into recovery manually either, it just boots into the sony logo and gets stuck there.
I do have a backup in twrp but I can't install that since I can't get into recovery, and I can't manually access the storage since usb debugging is not active while on the sony startup screen.
Is there anything I can do or is my z3c rip?
I can connect the phone in fastboot and flashmode and flashtool does recognize it, however I can't really seem to do anything while in flashmode and fastboot mode doesn't work since flashtool tells me I don't have the right drivers for the device, however when I try to install the driveres it hands out an error message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
StanYz said:
Heyo
Following situation:
I tried to root and flash my old Sony Xperia Z3 compact which I have been using as an mp3 player. I successfully did so (I think), however when I wiped my data to flash to linage os, it gave me error 7. I assumed it was because my TWRP version was way out of date so I updated that, and hit "reboot into recovery" to activate the new twrp version.
Unfortunately the phone didn't boot into recovery and just wound up stuck at the sony screen without anything else since no OS is installed.
I can't boot into recovery manually either, it just boots into the sony logo and gets stuck there.
I do have a backup in twrp but I can't install that since I can't get into recovery, and I can't manually access the storage since usb debugging is not active while on the sony startup screen.
Is there anything I can do or is my z3c rip?
I can connect the phone in fastboot and flashmode and flashtool does recognize it, however I can't really seem to do anything while in flashmode and fastboot mode doesn't work since flashtool tells me I don't have the right drivers for the device, however when I try to install the driveres it hands out an error message
Click to expand...
Click to collapse
If your using Windows 10 you'll probably need a Windows 7 virtual machine if you don't have a physical PC with Windows 7 already installed. That or you'll need to turn on test mode for Windows
But if I may ask what fhe error(s) output whwn trying to install said drivers?
TheExploitedOne said:
If your using Windows 10 you'll probably need a Windows 7 virtual machine if you don't have a physical PC with Windows 7 already installed. That or you'll need to turn on test mode for Windows
But if I may ask what fhe error(s) output whwn trying to install said drivers?
Click to expand...
Click to collapse
I've attatched 4 screenshots in my OP, thats all I see, it doesn't actually state what the error is, just that it didn't finish.
Will it go through with win7? Actually that aside, is there a way to force a new os onto the phone via the flashtool to begin with?
Since your Windows computer needs to recognize the Xperia z3 based on Qualcomm chipset once connected, the PC should have installed proper USB drivers. which in no case depends on Windows version or Windows edition. You have to obtain the USB drivers and also the ADB / Fastboot drivers from OEM's / Carrier's website. It's never a good idea to install the ADB / Fastboot drivers elsewhere offered on WEB.
And once installed, restart the PC.
If successful then use
jwoegerbauer said:
Since your Windows computer needs to recognize the Xperia z3 based on Qualcomm chipset once connected, the PC should have installed proper USB drivers. which in no case depends on Windows version or Windows edition. You have to obtain the USB drivers and also the ADB / Fastboot drivers from OEM's / Carrier's website. It's never a good idea to install the ADB / Fastboot drivers elsewhere offered on WEB.
And once installed, restart the PC.
If successful then use
Click to expand...
Click to collapse
---
My carrier doesn't offer any drivers whatsoever.
But all of that aside, even if I do get fastboot running, is there even a way to force a new OS onto the phone via some tool?
I have an Oppo A51w (Oppo Mirror 5) that I just reset to factory settings, out of nowhere when I restared the phone after that it shows encryption unsuccessful, and a reset phone button, which I couldn't press.
Going into ColorOS recovery mode, I tried wiping data and cache, but wiping data doesn't work because it says I have no space it needs at least 250mb, but I remember the phone does have plenty of space, more than 7gbs, so I don't get why it shows that.
As for fastboot mode it doesn't really do anything other than show its starting logo and text and it turns off? Is there anything else I'm supposed to do I'm not sure?
Anything I could do to get past the encryption screen? I don't mind having to fully reset the phone or flash it but I might need a guide.
There is also an install from sd option in the recovery mode, if somehow it can be fixed from there then please help me with that.
The android version is 5.1.1 and ColorOS 2.1.0i
The version that shows on the ColorOS recovery is 1.2
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
NextGenMagisk said:
Android 5.1 is too old. I am not sure which fastboot commands are supported for this version but you can try this even if Fastboot works for few seconds.
fastboot -w
fastboot erase userdata
If the fastboot method does not work then you need to find a MSM Download tool and correct firmware for your device model and flash it.
Click to expand...
Click to collapse
Does this need USB debugging? I don't have it enabled and can't enable it because I can't get past the encryption screen.
I tried using MSM download tool but for some reason it won't detect my phone and I'm not sure which usb driver to use and how to install it.
The phone also isn't rooted.
Update:
The phone is now stuck on boot loop. I tried to flash it from sd card using stock rom from the official website, without wiping data first because it wasn't possible (needs 250mb of storage space even though there IS enough free space). It said it was successful, but after rebooting it just gets stuck on boot loop.
- for adb I'd need usb debugging? Which can't be enabled
- the phone isn't rooted, so no cwm
- msm download tool I tried, v4 and v5 doesn't work it says "Packed image not exist" but v1.6.7 does? except even it won't detect the phone, and the rom that i downloaded for that from a different source had different phone model options which i do not recognize (oppo15008.bin etc and rawprogram0_MSM_15070.xml) so I'm not sure which one to choose. Maybe I haven't installed the driver but I don't know which to install and how to.
I really have no experience with this and just tried different guides on the internet to get the phone working. For now I don't know what to do. Any help is appreciated.
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
NextGenMagisk said:
Your device seems to have Qualcomm chipset so it can be repaired in the EDL mode (9008). Search google "unbrick oppo a51w". It will give you all info you need to fix this.
If your device is not detected even after installing correct drivers, then you need to use Test Point method (shorting JTAG pins) to access EDL mode. This step needs expertise to short correct pins, if your attempts fail then your best option is the Oppo service center.
Click to expand...
Click to collapse
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
southeeast said:
I searched and I seem to have tried following steps like this before and it didn't detect my phone even with Qualcomm driver installed, also didn't know which phone model mine is and I'm supposed to choose between these, how do I know?
Click to expand...
Click to collapse
Sorry, I cannot help with selection of firmware.
Is there any reason why you can't get this repaired in the Oppo service center?
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?
Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Solved without using EDL test points. see The Solution below.
BIG Thanks goes to @NOSS8 for his help.
ramiro2016 said:
Hi,
I need to put my device in Emergency Download Mode (EDL) in order to recover the boot and fix the bootloop (fastboot not working).
Where is the test points, or how to figure them out?
See the phone schemas below:
Redmi Note 10 Pro 5G (chopin)
Click to expand...
Click to collapse
this phone did not need edl or test point.
https://forum.xda-developers.com/t/...-after-flashing-gsi-rom.4448229/post-86995731
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
ramiro2016 said:
@NOSS8 I've tested this method out. The USB serial device drive shows for about 3 seconds and MTK META UTILITY only detects it when I uninstall the driver for the USB serial device. Then it didn't succeed due to the driver I guess. Look at the result in the following image.
Note:
I'm using Windows 11. For this, I will install Windows 7. I will redo the process. When I finish, I will provide you with the results.
Click to expand...
Click to collapse
https://xiaomitools.com/sp-flash-tool-en/
there is also this tool (new not tested).
https://forum.xda-developers.com/t/tool-rom2box-all-in-one-frp-flashing-unlocking-tool.4477349/
https://gearupwindows.com/how-to-disable-driver-signature-enforcement-on-windows-11-10/
check for program update
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
ramiro2016 said:
@NOSS8 Not working neither in windozs 11 nor in windows 7, I've tested a lot of MediaTek drivers with no luck. Even the new app (Rom2Box) is not detecting the USB serial at all.
Look at the attached images of test I've done.
Click to expand...
Click to collapse
This is not the latest version(V52).
https://mega.nz/file/H0MW3BST#PfzzmSwbncT5aV7A1ZhWztQonLj4CgJLDHbXoRtCu54
Maybe useful
https://www.bypassfrpfiles.com/2021...h_Secure_Boot_Disable_Tool_V52_Latest_Version
BTW: I don't have and would never have a xiaomi Mediatek and therefore never use these tools for Mediatek, that's why I can help you for the links but not for the use of these tools.
If it still doesn't work post the latest log.
Unfortunately, even the latest version v52 doesn't work, but this tool helped me solve the problem.
https://github.com/bkerler/mtkclient (You need to follow the readme document).
I've used the mtk_gui, and after it got connected, I sent my original firmware boot.img that is currently installed on my mobile after renaming it to boot.bin to the device partitions boot_a and boot_b
Rebooting the device got me the original recovery mode and the fastboot mode.
Then I used the MiFlash tool to flash my phone using flash_all.bat
Every thing is working fine know.
BIIIIIIIIIIIG Thanks goes to @NOSS8 for helping me all the way to the solution .