Hi, I was trying to unload the bootloader with the program huawei multy tool, everything went ok until the restart and the smartphone was stuck to "you device has been unlocked and can not be trusted etc. you device is booting now. to fix? If I try some command from adb it goes out "waiting for devices"
ps. google translate XD
Related
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
You need a working phone with USB debug enabled, then " adb reboot edl" from cmd... Sorry but if you are in a boot loop there is no knows way to access the Qualcomm mode...
There is no way for you to go into EDL mode. You need to apply for unlock permission from Xiaomi if you want to fix your mi4c yourself.
I applied for permission on Feb 1, and I got it today (Feb 18) despite the Chinese New Year holidays. I haven't even received my mi4c from China yet, and am not even a diamond member at miui.com, either. Good luck!!
dsafro said:
Hi everyone,
I'm having this "locked bootloader" issue as probably hundreds other people do, since January update appeared. In my case the phone became unusable, stuck on MI logo, and also there is no recovery available.
I can only use fastboot.
I understand that some people managed to completely erase the eMMC and reflash the bootloader while the phone is connected to the computer in "Qualcomm HS-USB QDLoader 9008" or "QHS_USB Bulk" mode.
I can't figure out how to boot the phone in either of these modes! When connected through fastboot the MI4C is being recognized as "Marshall London Bootloader Interface". When I just turn it on and it's stuck on MI logo, it isn't recognized by device manager at all.
I'm on Windows 10 64 bit. Anyone has any idea what needs to be done to access these modes on Mi4C?
Many Thanks!
Click to expand...
Click to collapse
Did you try flashing it with Miflash? I got bricked yesterday, so I reflashed system this way, but via Qualcomm HS-USB QDLoader. Also, my phone did not react to anything except bootloader mode (holding buttons for a long long time), no charging, no lights - nothing.
Me too
Me too. :crying:
Hi,
I have the same problem of the bootloader locked. Not let me do anything. It is blocked. I've tried to give instructions by ADB, but will not let me load any file since it claims to be the phone locked.
I have applied the code unlock via SMS to Xiaomi, but they are very slow. Yesterday I wrote and asked you to unlock it. They asked me 2 days more waiting, at least.
This is still horrible, a shame.
I read the post of a colleague who manages to unlock it but has to be the phone working. For those who stayed with my at startup, there is no solution.
Regards.
Hi, I'm trying to unlock my phone so I can install Kali Linux on my A466BG. I've read a lot on the web but came to a problem. I've got Android SDK on my PC and installed platform-tools. My device shows up after entering "adb devices." I've enabled developer mode and usb debugging and OEM unlocking. My problem is...I can't unlock the bootloader and use fastboot. After pressing power and up volume I get into the menu (and I actually reset my phone to factory settings so I'll have more space) but I can't find bootloader. My phone shows up fine on my PC and under devices, but when I switch to the other menu (with reset options) it doesn't show up anymore. Not even under "adb devices." I tried entering "adb reboot-bootloader" but it just restarts and goes to the normal android phone screen. I tried "fastboot -i 0x1bbb oem device-info" and it says "waiting for device." I'm not sure how to boot into fastboot and unlock my bootloader. Or why my phone doesn't show up on my PC after pressing power and up volume. Please reply with instructions. Thank you
Hi, me again. I found a video on YouTube on how to install Kali Nethunter on Android phones. I got it and now I'm installing Metasploit. It's just the command line but that should work. Check You Tube on "Nethunter without root" if you want to know. Thanks
I'm back...Not satisfied with Nethunter on Termux. I would like to know how to root the phone and install Kali. Can anyone look at the above question and reply with how to root my Alcatel A466BG? I'll check back tomorrow. Thanks in advance!
when i install LKBoot Installer or fastboot etc, it suddenly stops it says "fastboot stop working" then my phone get bricked with the screen off it does vibrate but cant open and it cant search by an Windows Recovery Tool
But my PC can search it and the name is "Android Bootloader Interface"
How do I fix it? Any Help?
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
MugenG said:
Hi all,
sorry if there is plenty of these threads already floating around but wasnt able to find a relevant one to my problem. I'm hoping someone here might be able to help.
This is the primary XZ rooting guide i have been following, with other supplimentary guides 1 & 2
These have been my steps:
- Managed to successfully update fastboot driver with "android_winusb.inf-file" from 'Google USB Driver' within android studio.
- Unlocked bootloader
- Installed AndroPlus Kernel sucessfully "fastboot flash boot boot.img"
Now went to reboot device as stated by instructions (mistake) and now the device is not recognized in cmd "waiting for device". I've replugged the usb in multiple ports and the device shows up as "android" in devices and printers. I go to update the android "SOMC Flash Device" to the platform tools directory but makes no difference in cmd. Still "waiting for device". In Device Manager there is no sign of the device either.
When the phone is turned on it shows your device has been "unlocked and cant be trusted will reboot in 5 seconds" then proceeds to xperia logo and freezes. With no recoveries theres not much options.
Is there a way to continue from here or even return to a previous state? It seems like i hit a brick wall. Please help
Click to expand...
Click to collapse
Installed adb SystemWide?
adb drivers are Installed corrcetly? , better to reinstall them.
Hello, I am new here!
I have a problem with my P20. Yesterday I tried downgrading with HiSuite Proxy from Emui 9.1 to 8.1. The update went well, the emui loading circle with percentage appeared on the phone, then at 80 percent there appeared an error on the screen that the update has failed and I should either enter recovery or reboot. I clicked on reboot (I am dumb, I know) and since then the phone is showing a black screen and I cannot do anything. The phone is in Fastboot and it responds to fastboot commands from adb tools.
I think the problem is, that in Hisuite proxy I selected "normal update" instead of "rollback". That made Hisuite perform an update over a newer version of emui.
In the beginning, the phone was recognised by windows as "Andoid device" with a subname "HI3650". After switching drivers in device-manager, I got "ADB device" there.
What I tried so far:
- switching ADB drivers in device manager in windows
- system recovery in Hisuite. It fails, tried with several HiSuite versions so far.
- "fastboot flashing unlock" (most fastboot commands return errors like "FAILED (remote: check password failed!)" or "FAILED (remote: Command not allowed)"
I am not a pro with these things but understood that I could flash a recovery image with fastboot. Someone on this forum said something about .pac images which could be flashed even with a locked bootloader, mine is locked. Could somebody with good knowledge help me out? I did plenty of google searching before and also browsed through this forum, i did not find a solution, at least not with locked bootloader.
I would appreciate any help to save the phone before having to trash it!
Servus2403 said:
Hello, I am new here!
I have a problem with my P20. Yesterday I tried downgrading with HiSuite Proxy from Emui 9.1 to 8.1. The update went well, the emui loading circle with percentage appeared on the phone, then at 80 percent there appeared an error on the screen that the update has failed and I should either enter recovery or reboot. I clicked on reboot (I am dumb, I know) and since then the phone is showing a black screen and I cannot do anything. The phone is in Fastboot and it responds to fastboot commands from adb tools.
I think the problem is, that in Hisuite proxy I selected "normal update" instead of "rollback". That made Hisuite perform an update over a newer version of emui.
In the beginning, the phone was recognised by windows as "Andoid device" with a subname "HI3650". After switching drivers in device-manager, I got "ADB device" there.
What I tried so far:
- switching ADB drivers in device manager in windows
- system recovery in Hisuite. It fails, tried with several HiSuite versions so far.
- "fastboot flashing unlock" (most fastboot commands return errors like "FAILED (remote: check password failed!)" or "FAILED (remote: Command not allowed)"
I am not a pro with these things but understood that I could flash a recovery image with fastboot. Someone on this forum said something about .pac images which could be flashed even with a locked bootloader, mine is locked. Could somebody with good knowledge help me out? I did plenty of google searching before and also browsed through this forum, i did not find a solution, at least not with locked bootloader.
I would appreciate any help to save the phone before having to trash it!
Click to expand...
Click to collapse
Hello there! I can help you with this since I got exact same problem. Do you have any messaging app? add me on telegram t.me/dexxik or discord Dexxo#0295 if you want quicker response.
First of all, you f*cked up. I can help you recover your phone but you won't be able to use that phone for calling/messaging again.