Related
Hi,
I'm trying to unlock my redmi note 5 with the latest version of miunlock but I keep getting this error message at 99%: "Request parameter error"
My account is correctly linked to the phone, I have no clue what to do...
Thank you!
take a pixel
same problem
Mi note 5 ai boot loader unlock
Same here ,every time i try the same error appear!
Redmi Note 5 Pro
same problem for me
still no solutions for these ?
Mi Unlock (windows) for Mi A3 Error: Couldn't unlock. Request parameter error
Hello, even I am facing the Same issue please asssist.
Thank you.
Same here: Redmi Note 5 Pro and the last global stable Miui 11 Rom.
I have enabled in dev options oem unlock, USB-Debugging and bind my phone to Mi Account (unlock status).
I saw the popup, that the phone is bind to my account.
Mi Cloud find my Phone.
The Phone is connected with USB 2.0 Port.
I have try the newest and older versions of the Mi unlock tool as admin.
Every time the same at 99%: Couldn't unlock => Request parameter error
In the Device Manager (Win10) I find Android Phone and ABD Bootloader Interface.
I think it looks good.
I have attached the mi unlock tool log file.
Where is the solution and sorry for my bad english.
It is not my native language.
Thank you for comments :good:
I had the same problem when I used my second phone as usb tethering network connection, but I fixed by using it as wifi hotspot. The adb thingie was not "locked" or if you have other devices connected via usb, it get the error, I believe.
Try downgrading mitools and miui
Today I could unlock the device by the first try, with my brothers pc (old amd apu/win7).
Thanks and have a Happy New Year!
If someone is still wondering, just connect your phone in fastboot and open Minimal ADB and Fastboot. type this "fastboot flashing unlock" and hit enter. This did the job for me.
httpdoge said:
If someone is still wondering, just connect your phone in fastboot and open Minimal ADB and Fastboot. type this "fastboot flashing unlock" and hit enter. This did the job for me.
Click to expand...
Click to collapse
Superb!
just had to modify as requested
fastboot flashing unlock
...
FAILED (remote: Need wipe userdata. Do 'fastboot oem unlock-go')
finished. total time: 0.045s
fastboot oem unlock-go
...
OKAY [ 0.034s]
finished. total time: 0.393s
how can i use this code
It Worked
httpdoge said:
If someone is still wondering, just connect your phone in fastboot and open Minimal ADB and Fastboot. type this "fastboot flashing unlock" and hit enter. This did the job for me.
Click to expand...
Click to collapse
Thanks Dude, It worked for me...
ramisamii said:
how can i use this code
Click to expand...
Click to collapse
very late reply but you should google how to open fastboot in your phone, then connect it to your pc and download platform tools, open cmd cd into the directory w that exe connect your phone and type the commands above
I solved this issue by simply rebooting my Poco F3 and then booting back into fastboot and clicking unlock
httpdoge said:
If someone is still wondering, just connect your phone in fastboot and open Minimal ADB and Fastboot. type this "fastboot flashing unlock" and hit enter. This did the job for me.
Click to expand...
Click to collapse
brother nothing is happening for me, i am still getting request parameter error, please help me
Robert314 said:
I solved this issue by simply rebooting my Poco F3 and then booting back into fastboot and clicking unlock
Click to expand...
Click to collapse
brother nothing is happening for me, i am still getting request parameter error, please help me
i solve it with changing usb port on pc. now have to wait 7 days
This solves the problem
Check out this video for more informations:
And yes, you have to wait for 7 days for some reason.... Thanks Xiaomi
Hi, I'm Loperaco. Maybe they remind me of threads like "Help Help help !!! Deep Cable / Flash Cable Moto Z2 Force" or "How modify a qcn file to enable AWS band". Today I come to you with a new challenge, to keep your mind entertained during the Coronavirus quarantine.
I have this Moto Z2 Force with which I have had many adventures, lucky and unfortunate (I have spoiled it a couple of times), and this time is no different.
For silly (I have no other reason) forget to check the 'OEM unlocking' in Android Settings after installing a new ROM on this cell phone that unlocked a long time ago, and then I got stuck in a loop in the bootloader, because when you try start shows the motorola message indicating "Your device is corrupt. It can't be trusted and will not boot" and when I go to the bootloader to try to flash because it is in "locked" state, so I cannot flash to recover the cel, and I can't start to unlock the OEM.
What I have tried to be able to unlock flashing:
- fastboot oem unlock: not working, I get it in "(bootloader) Check 'OEM unlocking' in Android Settings> Developer Options"
- fastboot flashing unlock: not working, I get it in "(bootloader) Check 'OEM unlocking' in Android Settings> Developer Options"
- fastboot flashing get_unlock_ability: Gives me instructions for initial unlocking via the Motorola website, which is a process that I went through a long time ago.
- fastboot oem unlock XXXXXXXXXXXXXXXXXXX: does not work, it results in "(bootloader) Check 'OEM unlocking' in Android Settings> Developer / (bootloader) Options / OKAY [0.003s] / Finished. Total time: 0.006s"
I also tried to take the phone to blackflash mode and boot from there with Qualcomm drivers:
- adb reboot edl: results in "error: no devices / emulators found", because I am clearly not in ADB state.
- fastboot oem blankflash: results in "(bootloader) Command Restricted / FAILED (remote: '') / fastboot: error: Command failed"
- fastboot -w: results in "Erasing 'userdata' / (bootloader) Permission denied / FAILED (remote: '') / fastboot: error: Command failed"
- fastboot oem edl: results in "(bootloader) 'edl' is not a supported oem command / (bootloader) See 'fastboot oem help' / FAILED (remote: '') / fastboot: error: Command failed"
- fastboot oem -edl: results in "D: \ Desktop \ 3. Moto Z2 Force \ 2. Platform-tools \ 1a. Platform-tools v.29.0.6 \ fastboot.exe: unknown option -e"
I also tried to install the custom recovery (fastboot boot twrp.img) and it turned out that if you let me install it (yeah!), But when you reboot to boot with TWRP I get the message "Your device is corrupt. It can't be trusted and will not boot ", so don't let TWRP (f.u.c.k!) start.
Lastly, and without giving up in the face of adversity, I tried to reinstall the same ROM that I had but it throws me denials of everything for having the "Flashing_locked". It turns out that that particular variation (XT1789-05_NASH_RETLA_SS_9.0_PPX29.159-23_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml) doesn't have a higher ROM available (or at least I didn't find it), so I tried to install a higher one from another variation and I didn't leaves the same Flashing topic blocked (NASH_RETAIL_9.0_PPX29.159-24_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml).
Any good Samaritan with an almighty idea?
looks like you're confused about where to post your 3 different question threads.
as a reminder https://forum.xda-developers.com/z2-force/development is for developers who are producing something to share with the community, and so the community can give feedback in those threads.
random questions about a device go in https://forum.xda-developers.com/z2-force/help
hope that clears things up for you, cheers.
jmichael2497 said:
looks like you're confused about where to post your 3 different question threads.
as a reminder https://forum.xda-developers.com/z2-force/development is for developers who are producing something to share with the community, and so the community can give feedback in those threads.
random questions about a device go in https://forum.xda-developers.com/z2-force/help
hope that clears things up for you, cheers.
Click to expand...
Click to collapse
Hello !
Wow, I didn't know, so I'm going to put this where it belongs.
Although I was checking and everyone asks and asks for help here according to the classification of the topic.
No one to help me?
Loperaco said:
No one to help me?
Click to expand...
Click to collapse
First, all questions threads belong in /help sections.
I would try LMSA'S Flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
You are able to boot TWRP, with the locked bootloader?
Sent from my ali using XDA Labs
sd_shadow said:
First, all questions threads belong in /help sections.
I would try LMSA'S Flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
You are able to boot TWRP, with the locked bootloader?
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hi sd_shadow !
Ok, so
First, all questions threads belong in /help sections.
I moved this thread from a ROM forum to the "Questions and Answers" forum, was I wrong again?
I would try LMSA'S Flash rescue option
Try this option, everything initially worked fine, in the "Flash / rescue" mode it recognized the model of my cell phone and then identified the appropriate firmware, I downloaded it without problem, but when I tried to flash (click the rescue button) I got an error, a Pop-up window indicating "Fastboot Flash Single Partition. Flash failed. Please try again". I tried again and got the same result.
You are able to boot TWRP, with the locked bootloader?
No I can not. Although the TWRP is allowed to install when I try to access the cell phone, it goes to the screen "Your device is corrupt. It can't be trusted and will not boot"
I continue to listen to suggestions, in the middle of this coronavirus it is not a good idea to spend money on a new cell phone.
Loperaco said:
Hi sd_shadow !
Ok, so
First, all questions threads belong in /help sections.
I moved this thread from a ROM forum to the "Questions and Answers" forum, was I wrong again?
Click to expand...
Click to collapse
Although this section title is Questions and Answer
It's url is
https://forum.xda-developers.com/z2-force/help
I would try LMSA'S Flash rescue option
Try this option, everything initially worked fine, in the "Flash / rescue" mode it recognized the model of my cell phone and then identified the appropriate firmware, I downloaded it without problem, but when I tried to flash (click the rescue button) I got an error, a Pop-up window indicating "Fastboot Flash Single Partition. Flash failed. Please try again". I tried again and got the same result.
Click to expand...
Click to collapse
Do you have access to a Windows PC that shipped with XP or 7?
It's ok if it was updated to 10.
If yes, try RSD Lite
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Other wise I don't think there's a solution.
Sent from my ali using XDA Labs
sd_shadow said:
Although this section title is Questions and Answer
It's url is
https://forum.xda-developers.com/z2-force/help
Do you have access to a Windows PC that shipped with XP or 7?
It's ok if it was updated to 10.
If yes, try RSD Lite
Motorola Flashing Guide
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039
Other wise I don't think there's a solution.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hi sd_shadow.
I was able to access a windows 7 with usb 2.0 and from there I tried the process according to the threads that it sends me as a guide, however, when I start flashing it generates the error "the phone failed to switch to fastboot mode", which is strange because if it's in fastboot, if not the RSD would not recognize it in first place.
what do you think?
Loperaco said:
Hi sd_shadow.
I was able to access a windows 7 with usb 2.0 and from there I tried the process according to the threads that it sends me as a guide, however, when I start flashing it generates the error "the phone failed to switch to fastboot mode", which is strange because if it's in fastboot, if not the RSD would not recognize it in first place.
what do you think?
Click to expand...
Click to collapse
Likely a USB driver issue
See my drivers post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ali using XDA Labs
sd_shadow said:
Likely a USB driver issue
See my drivers post in
Moto Drivers, Firmware, RSD Lite, and other Unbricking Tools
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hi SD.
I tried changing the cable and the drivers and I don't get it, somewhere I read that it helped somebody to do the process in a Windows 7 x32, however I don't have any equipment with OS in x32.
What do you think about bringing the cell phone to a state of blocking on purpose, that is, forcing it to go into a Qualcomm state? From there I could try to rescue with the blankflash. But I don't know how to do it, how to force it to get damaged, because the commands for that from fastboot do not lead me to the desired result.
Loperaco said:
Hi SD.
I tried changing the cable and the drivers and I don't get it, somewhere I read that it helped somebody to do the process in a Windows 7 x32, however I don't have any equipment with OS in x32.
Click to expand...
Click to collapse
How does it show up in device manager?
What do you think about bringing the cell phone to a state of blocking on purpose, that is, forcing it to go into a Qualcomm state? From there I could try to rescue with the blankflash. But I don't know how to do it, how to force it to get damaged, because the commands for that from fastboot do not lead me to the desired result.
Click to expand...
Click to collapse
Very unlikely that you can force EDM.
Code:
fastboot oem blankflash
And even if you get it in to emergency download mode there are probably more posts that the blankflash didn't work that reports that it did.
Sent from my ali using XDA Labs
sd_shadow said:
How does it show up in device manager?
Very unlikely that you can force EDM.
Code:
fastboot oem blankflash
And even if you get it in to emergency download mode there are probably more posts that the blankflash didn't work that reports that it did.
Sent from my ali using XDA Labs
Click to expand...
Click to collapse
Hi.
How does it show up in device manager?
Motorola ADB Interface
Very unlikely that you can force EDM.
Code:
fastboot oem blankflash
This is the resut "(bootloader) Command Restricted / FAILED (remote: '') / fastboot: error: Command failed"
And even if you get it in to emergency download mode there are probably more posts that the blankflash didn't work that reports that it did.
I understand, but right now I don't know what else I can do. I know it's a risk, but I ran out of ideas, because I read and read, try and try, and the "Flashing_locked" problem always blocks every attempt at every command.
Use Lenovo Moto Smart Assistant to recover it. I used it successfully.
hqureshi said:
Use Lenovo Moto Smart Assistant to recover it. I used it successfully.
Click to expand...
Click to collapse
Hi hqureshi.
I'm afraid this didn't work for me. The result for that was:
Try this option, everything initially worked fine, in the "Flash / rescue" mode it recognized the model of my cell phone and then identified the appropriate firmware, I downloaded it without problem, but when I tried to flash (click the rescue button) I got an error, a Pop-up window indicating "Fastboot Flash Single Partition. Flash failed. Please try again". I tried again and got the same result.
I try LMSA in pc with windows 10 x64 with USB 2.0, in a laptop with windows 10 x64 with USB 3.0, and in a laptop with windows 7 x64 with USB 2.0. Same results in all three.
The same thing happens to me, did you find a solution?
hi devs
i flashed accidentially Chinese recovery rom on my whyred now i m unable to switch from Chinese to global version as i tried every method fastboot,recovery,qfil,mi flash and edl mode i mean every possible way but all in vain as every method ended with error and my fastboot command is locked.
so what can i do please suggest me
it's Chinese miui 11
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
aliasgertaj said:
guys please help me i m frustrated tried every available method on internet downloaded tons of file.
Click to expand...
Click to collapse
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
SubwayChamp said:
What you are trying to do? Just switch from Chinese to Global? or your device is bricked now?
What did happen after that you flashed the Chinese recovery ROM?
What modes do you have available?
Did you unlock bootloader previously?
Click to expand...
Click to collapse
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
aliasgertaj said:
i m not bricked as my device is working fine
but now no fastboot command working i m not able to flash custom recovery
i tried fastboot method , used miflash method every miflash from old to newest , qfil edl mode method with miflash and qualcomm flash tool
i m just able to switch between china stable n developer rom
if i m able to unlock ma fastboot command then i can flash atleast custom recovery .
kindly help me as all method ended up every time with diffrent error.
Click to expand...
Click to collapse
Fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on Developer section, i.e. USB debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
subwaychamp said:
fastboot flashing commands won't work if you have bootloader locked.
Did you unlock bootloader previously and probably get locked again?
Did you enable all the proper options on developer section, i.e. Usb debugging and check if device is recogniced on adb commands?
What do you get with "fastboot getvar all"?
Click to expand...
Click to collapse
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
aliasgertaj said:
thanks a lot dude i m on unlock boot loader .
But bootloader some time works means sometimes it shows my device name after available device command it shows only ???????? Fastboot devices
i tried all way possible but none of them worked.
And i m unable to switch from china to global.
Only i can do is switch between china stable to developer.
Click to expand...
Click to collapse
aliasgertaj said:
i tried getvar command but it gave me this
PS C:\adb> adb reboot bootloader
error: device '(null)' not found
PS C:\adb> fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))
finished. total time: 5.007s
PS C:\adb>
Click to expand...
Click to collapse
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
SubwayChamp said:
I think you are not properly booted to the proper state while you're trying certain commands. Just to be clear; adb works while your device is power on and fastboot commands will work only while your device is in fastboot mode not while on adb mode. A way to be sure that you are doing properly is enabling USB debugging first but while connected device with PC, a prompt will appear from device screen and then tap on "always allow", then you have to type "adb devices" and follow step by step, if device is recognized you can go to the next step with "adb reboot bootloader" then in fastboot you have to see the bunny otherwise is not properly in fastboot mode, then you can follow with "fastboot devices" and so on, keep in mind that any command will work until device is properly recognized.
Click to expand...
Click to collapse
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
drnightshadow said:
And you said you enabled USB debuging?!? you didn't. First enable it under development tools.
MAKE SURE YOUR USING RIGHT ADB/FASTBOOT TOOLS AND DRIVERS.
After 'adb reboot bootloader' use 'fastboot devices'. You can change usb cable and if you still get errors try using usb hub.
If all above fails than try it on WIN7 PC.
Click to expand...
Click to collapse
thanks for response bro
i did it under developer option and trusted my computer connection also and install adb fastboot devices many time changed cable and port but nothing happen. i tried fastboot files of china stable rom but it also doesn't worked
aliasgertaj said:
thanks bro
yesterday i used xiaomitool v2 as it reboot automatically device in fastboot mode but as i said after in fastboot mode it doesn't boot in adb mode.
and what is proper method to open fastboot mode i m doing it by holding power and volume down button.
Click to expand...
Click to collapse
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
SubwayChamp said:
Just trying to determine what your words exactly mean when you say "after in fastboot mode it doesn't boot in adb mode." ... without entering in more technical insights adb works when device is on, no sense to boot to fastboot to try to boot to adb after that (?)
If you can boot to fastboot what you have to try firstly is unlock bootloader or be sure that is already unlocked using
Code:
fastboot oem device-info
if your device is or get unlocked then you can try to flash or just boot to a custom recovery but if you can't determine until now if your device is really unlocked then you couldn't go further.
The hardware method to enter to fastboot is from a device off; pressing both pwr and vol down buttons but if the bunny is not displayed probably you didn't really get fastboot mode.
Click to expand...
Click to collapse
i m frustrated now tried all the thing tried official flash tool official build but even official build by miflash official latest tool unable to flash image
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
aliasgertaj said:
i bought my device to official xiaomi service center they told it will be done in an hour but after couple of hour they returned my phone that it cant be updated.??????
shame on xiaomi that they implemented a method that they themselves also don't know how to revert it.
Click to expand...
Click to collapse
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
drnightshadow said:
Do yo use WIN10? Find PC with Win7... and install adb/fastboot app and drivers. Than try..
Is your system working now?
Just unlock your bootloader and install OrangeFox recovery than you can flash whatever you need.
Problem solved.
Click to expand...
Click to collapse
ok bro i will try today with another pc and update you
aliasgertaj said:
ok bro i will try today with another pc and update you
Click to expand...
Click to collapse
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
aliasgertaj said:
thanks installed twrp on other pc running on windows 7 but now internal storage goes 0mb unable to mount system
Click to expand...
Click to collapse
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
drnightshadow said:
Wtf .. what's wrong with you.. you did everything we said wrong... Where and when did I told you to install TWRP????
I'm done with you...
Good luck with china ROM.
Ignorance is a bliss.
Click to expand...
Click to collapse
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
aliasgertaj said:
thanks dude i installed twrp wipe my internal storage there is some error then some tricks goes perfect as i supposed and woohaa i installed masik port edition and now my phone works fine.
Click to expand...
Click to collapse
TWRP can't bypass encryption, when you have no access to read data (0mb) then you have to format it, to avoid that is always recommended use OrangeFox, just for future reference, if you understand that you can flash OrangeFox through TWRP for better experience.
Also you can use this tool to help you to automate some stuff https://github.com/Szaki/XiaomiADBFastbootTools
Bricked with a locked bootloader - "This MIUI version can't be installed on this device"
I can get to "adb sideload" and fastboot, but the bootloader is locked
Can I unlock the bootloader with EDL? Can I access EDL with an EDL-cable? Or do I need to open the phone and short the EDL pins?
Can I recover the phone from a Linux computer? Or do I need Windoze?
Is it even possible to un-screw this phone?
Any help appreciated.
go vegan said:
Bricked with a locked bootloader - "This MIUI version can't be installed on this device"
I can get to "adb sideload" and fastboot, but the bootloader is locked
Can I unlock the bootloader with EDL? Can I access EDL with an EDL-cable? Or do I need to open the phone and short the EDL pins?
Can I recover the phone from a Linux computer? Or do I need Windoze?
Is it even possible to un-screw this phone?
Any help appreciated.
Click to expand...
Click to collapse
how did you do this?
Redmi 4A abdal said:
how did you do this?
Click to expand...
Click to collapse
1- Checking if this problem is still a problem with custom ROMs; it is, and thus I believe it to be a hardware fault.
2- Done testing, re-install stock stock ROM, lock bootloader via adb; bricked phone.
go vegan said:
1- Checking if this problem is still a problem with custom ROMs; it is, and thus I believe it to be a hardware fault.
2- Done testing, re-install stock stock ROM, lock bootloader via adb; bricked phone.
Click to expand...
Click to collapse
ok, you can run edl mode but its no good for you, its already locked by xiaomi, ( go ing to fastboot mode and give commands something like this " fastboot boot edl")
* do you see padlock lock sign when you go to fastboot mode
* try to flash vbmeta in fastboot mode
* try again to flash correct version miui fastboot rom with mi flashing tool with out selecting lock bootloader
I can get to fastboot by holding power+vol-down. There's no lock icon.
On Ubuntu, I don't think fastboot is compiled to support rebooting into edl. I tried editing the source, and I'm not sure if I did it right, but the binary I built did not boot the phone into edl.
Using these commands:
Code:
fastboot flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta /tmp/platform-tools/vbmeta.img
They all give the same result:
Code:
target reported max download size of 804274176 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.006s]
writing 'vbmeta'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.007s
go vegan said:
I can get to fastboot by holding power+vol-down. There's no lock icon.
On Ubuntu, I don't think fastboot is compiled to support rebooting into edl. I tried editing the source, and I'm not sure if I did it right, but the binary I built did not boot the phone into edl.
Using these commands:
Code:
fastboot flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity flash vbmeta /tmp/platform-tools/vbmeta.img
Code:
fastboot --disable-verity --disable-verification flash vbmeta /tmp/platform-tools/vbmeta.img
They all give the same result:
Code:
target reported max download size of 804274176 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.006s]
writing 'vbmeta'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.007s
Click to expand...
Click to collapse
Try to unlock bootloader using cmd and then vbmeta
T.Y.M.SAI said:
Try to unlock bootloader using cmd and then vbmeta
Click to expand...
Click to collapse
I'm not sure what that means.
go vegan said:
I'm not sure what that means.
Click to expand...
Click to collapse
There are 2 ways to unlock bootloader
1. Official way using Mi flash tool
2. Unofficial way using cmd
There are lots of videos on how to unlock bootloader using cmd go and try them
Most important is to keep your phone charged
T.Y.M.SAI said:
1. Official way using Mi flash tool
2. Unofficial way using cmd
Click to expand...
Click to collapse
1- That requires access to a working phone.
2- All I'm finding is instructions for how to type "fastboot oem unlock" on a Windoze computer.
go vegan said:
1- That requires access to a working phone.
2- All I'm finding is instructions for how to type "fastboot oem unlock" on a Windoze computer.
Click to expand...
Click to collapse
Did you found a way to fix the phone or unlock bootloader?
You have 2 ways to get out of this situation.
1. Try to unlock the bootloader with the Mi account you used last time.
2. If couldn't unlock, then switch to EDL mode. Use a no auth programmer to flash the correct variant fastboot ROM and the device should boots up. Then add account again and wait for 168 hours for unlocking.
Since we've got no auth programmer for Sm6125 we could use EDL mode freely.
Hi there @go vegan , have you already fix your phone again? because i also got the same situation on my redmi 6. or is there anybody who can help? thanks
Hi all add me to the list with a k20pro.
The device was unlocked at the start, i got MIUI 12.5 global and flashed with miflashtool.
but wipe and lock was active.
now the phone comes up to the recovery menu and says the miui version is not for this device.
When I try to flash to another version, miflashtool says the device is locked,
when I try to unlock while using the account the device is registered in, miunlock says go to settings >developer options> mi unlock status.
Gave it to a repair shop for 1.5 months and nothing. I live in Iran so no authorized service centers here.
I have access to fast boot mode and recovery.
I tried xiaomitoll V2 which had a specific question asking if my device would show This MIUI version can't be installed on this device in phone is bricked option. It goes to get china official Rom but then errors.
I'm a noob here so any help would be great, tnx.
I have encountered the same problem a few hours ago with my beloved Redmi K20 Pro. My heart became gloomy thinking that I have no way left other than having to take to an authorized service centre where they will rip off the back cover. But then I stumbled upon this simple solution that took me a minute or two. This is how I solved it:
Entered the fastboot mode
Connected the phone to my laptop using the USB cable
Opened the official Mi Unlock Tool and logged in with my Mi account, and
Clicked on the beautiful UNLOCK button!
Boom! The phone is back to its vibrant life! I'm just happy again!
when I try to unlock while using the account the device is registered in, miunlock says go to settings >developer options> mi unlock status.
TECHtacian said:
I have encountered the same problem a few hours ago with my beloved Redmi K20 Pro. My heart became gloomy thinking that I have no way left other than having to take to an authorized service centre where they will rip off the back cover. But then I stumbled upon this simple solution that took me a minute or two. This is how I solved it:
Entered the fastboot mode
Connected the phone to my laptop using the USB cable
Opened the official Mi Unlock Tool and logged in with my Mi account, and
Clicked on the beautiful UNLOCK button!
Boom! The phone is back to its vibrant life! I'm just happy again!
Click to expand...
Click to collapse
Hi! Where can I download Mi Unlock Tool?
UnDevelopedDeveloper21 said:
Hi! Where can I download Mi Unlock Tool?
Click to expand...
Click to collapse
Apply for permissions to unlock Mi devices
en.miui.com
The solution to the problem is simple.
into fast boot mode,
Run unlock again!! Obviously it's locked. When unlocking is executed,
the same screen may appear again. Please do a reboot. You will definitely see the MIUI installation screen.
Device: Redmi note 7S
I found a solution and it worked for me:
1.Download the bat file and execute in your windows pc : https://drive.google.com/file/d/1NqPotx06yRuhPsOdEAdS4JNsk7qWWchF/view
2. After that use the MI unlocker tool to unlock the device.
3, Use mi flasher to flash the Rom.
After the hours of research in the internet i found the solution.
Thanks
Shiva5558 said:
Device: Redmi note 7S
I found a solution and it worked for me:
1.Download the bat file and execute in your windows pc : https://drive.google.com/file/d/1NqPotx06yRuhPsOdEAdS4JNsk7qWWchF/view
2. After that use the MI unlocker tool to unlock the device.
3, Use mi flasher to flash the Rom.
After the hours of research in the internet i found the solution.
Thanks
Click to expand...
Click to collapse
What do you mean by "execute in your windows pc"? Sorry for asking
I am trying to unlock the bootloader of the Poco F3 in order to root it.
I installed the platform tools present in the apt repositories (OS: Pop!_OS 20.10), this is the version I installed:
Bash:
$ fastboot --version
fastboot version 1:8.1.0+r23-8
Installed as /usr/lib/android-sdk/platform-tools/fastboot
Then I did this:
enabled developer options, USB debugging and OEM unlock in the device's settings
turned it off and then on again in fastboot mode (holding power and volume down buttons)
connected it to my PC through USB and then ran the following commands but when I run fastboot flashing unlock I get an unknown command error
Bash:
$ fastboot devices
████████ fastboot
$ fastboot flashing unlock
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Am I missing something here?
I read somewhere that I should install device specific drivers but I couldn't find any for Linux, what do I have to do?
You need to use mitools to unlock the bootloader. Search some videos of how to do it. You will need to wait 168 hours after finish the steps.
Is that actually the only way? According to this guide mi tools isn't required. I read that it only acts as a wrapper of fastboot so if I can I'd rather use fastboot directly and avoid setting up an account just for that.
QuazarOmega said:
Is that actually the only way? According to this guide mi tools isn't required. I read that it only acts as a wrapper of fastboot so if I can I'd rather use fastboot directly and avoid setting up an account just for that.
Click to expand...
Click to collapse
One Way : Mi Unlock Tool
No other way than Mi unlock tool......yet
Oh alright, Mi unlock tool it is then, thanks for the quick help!
It's purely so Xiaomi can limit people to unlock bootloader so that you don't get companies bulk buying devices falshing custom firmware and selling them as other phones for more
QuazarOmega said:
Is that actually the only way? According to this guide mi tools isn't required. I read that it only acts as a wrapper of fastboot so if I can I'd rather use fastboot directly and avoid setting up an account just for that.
Click to expand...
Click to collapse
that guide is wrong flashing unlock would work if the bootloader didnt need a special img file as part of the unlocking process.
the miunlock tool simply does the downloading of the img file in the background once you have waited the mandatory 168 hour wait period.