Hi, I have a Huawei Ascend P1 U9200 under contract from Vodafone which I am trying to upgrade to the official Huawei Jelly bean release (U9200-EM-UMTS-V100R00G411D00B315)
My phone has Build Number U9200-1V100R001C02B023 Custom version CUSTC02D023
I've downloaded it but it will not install because my phone is 'Operator Locked' I contacted Vodafone and they gave me an unlock code, and said that I have to put an invalid SIM in it and it will ask for the code - I have tried all of the UK SIMs and they are all valid!!! Vodafone will not help any more and have no plans to release updates.
I have managed to root the phone from stuff on here, but I still can't flash the update, I have ADB etc and have tried "fastboot oem unlock" but I get a fail message - if I do "fastboot devices" I get "? U9200" I was expecting some kind of #number...
Huawei offer a free 'Unlock bootloader' service, which I'm sure is what I need to do, but the online form does not offer the ascend P1 in the drop down menu - I have sent them about ten emails but they have not replied!
My PC is running Windows 8.1 maybe there are some issues with ADB/Fastboot in 8.1? I have installed Ubuntu onto an old laptop but don't really know what to do next. Please can someone help me?
Nearly there
Pompey0368 said:
Hi, I have a Huawei Ascend P1 U9200 under contract from Vodafone which I am trying to upgrade to the official Huawei Jelly bean release (U9200-EM-UMTS-V100R00G411D00B315)
My phone has Build Number U9200-1V100R001C02B023 Custom version CUSTC02D023
I've downloaded it but it will not install because my phone is 'Operator Locked' I contacted Vodafone and they gave me an unlock code, and said that I have to put an invalid SIM in it and it will ask for the code - I have tried all of the UK SIMs and they are all valid!!! Vodafone will not help any more and have no plans to release updates.
I have managed to root the phone from stuff on here, but I still can't flash the update, I have ADB etc and have tried "fastboot oem unlock" but I get a fail message - if I do "fastboot devices" I get "? U9200" I was expecting some kind of #number...
Huawei offer a free 'Unlock bootloader' service, which I'm sure is what I need to do, but the online form does not offer the ascend P1 in the drop down menu - I have sent them about ten emails but they have not replied!
My PC is running Windows 8.1 maybe there are some issues with ADB/Fastboot in 8.1? I have installed Ubuntu onto an old laptop but don't really know what to do next. Please can someone help me?
Click to expand...
Click to collapse
I have managed to get the Bootloader unlock code from Huawei and the NUC code from Vodadfone.
I've downloaded the latest ADT bundle and I can use adb to reboot the phone into fastboot but when I do 'fastboot devices' it lists '? fastboot'
see below
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
2BD2002200000001 device
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
? fastboot
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock 9868234643128978
...
FAILED (remote failure)
finished. total time: 0.000s
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
I'm guessing it's a driver issue or something, could someone please help me?
Pompey0368 said:
I have managed to get the Bootloader unlock code from Huawei and the NUC code from Vodadfone.
I've downloaded the latest ADT bundle and I can use adb to reboot the phone into fastboot but when I do 'fastboot devices' it lists '? fastboot'
see below
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
2BD2002200000001 device
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
? fastboot
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock 9868234643128978
...
FAILED (remote failure)
finished. total time: 0.000s
L:\Downloads\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
I'm guessing it's a driver issue or something, could someone please help me?
Click to expand...
Click to collapse
it just shows as ? because of the 'blaze' ADB drivers, just flash as normal. (fastboot flash [ROM])
OEM unlock doesn't work also because of locked boot loader. [Not unlockable]
Sent from my U9200 using Tapatalk
Related
Hi everyone,
It seems I was stupid enough to choose a wrong model (MediaPad M1) in TWRP Manager (downloaded from Google Play) while attempting to install TWRP recovery.
This resulted in an infinite bootloop where the "Huawei MediaPad" logo keeps appearing, the tablet restarts and again the same.
I do have access in Recovery and Bootloader mode, but all my attempts did not yield any results. Things I have tried so far:
- Download the Stock ROM from needrom.com (versions B009 and B019), extracted them and loaded the "dload" folder onto an SD card and executed recovery (by pressing both Vol UP/DOWN and starting the tablet). Even though the procedure seems to be perfoming normally, indicator reached successfully 100%, when the tablet restarts after the supposed successful recovery I am still left with the same bootloop.
My SD is a 64GB one, formatted with exFAT if this makes any difference.
- I have tried extracting UPDATE.APP using Huawei Update Extractor (http://forum.xda-developers.com/showthread.php?t=2433454) and tried to push via fastboot all necessary parts (i.e. BOOT.img, RECOVERY.img, SYSTEM.img, etc) but I get the "FAILED (remote: Command not allowed)" error message.
My bootloader was unlocked from the beginning (at least that's what showing when I enter bootleader/rescue mode with red letters - "PHONE UNLOCKED").
Any suggestions would be greatly appreciated! Thanks!
What commands are you using? It is peculiar that fastboot mode fails to flash. It may be that your bootloader is not properly unlocked even though it shows that it is.
If you have a bootloader unlock code for your device, I would suggest that you try explicitly unlocking the bootloader when in fastboot mode (it won't hurt to do this even if your bootloader is already unlocked):
Code:
fastboot oem unlock <YOUR_BOOTLOADER_UNLOCK_CODE>
Then you can verify that the bootloader is actually unlocked by issuing the following command:
Code:
fastboot oem get-bootinfo
If your bootloader is properly unlocked, then the previous command should return output similar to the following:
Code:
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.002s
At this point, let's try to restore your original BOOT partition and RECOVERY partition.
Now, gather the following partition images from your OEM firmware package:
BOOT.img
RECOVERY.img
SYSTEM.img
USERDATA.img
Only BOOT.img and RECOVERY.img should be needed to solve your issue, but we'll have SYSTEM.img and USERDATA.img ready and available here just in case our efforts fail with just boot and recovery alone.
Now erase and flash boot and recovery as follows (replace /path/to/oem/ in the commands below with the full path to the files you extracted from your OEM firmware):
Code:
fastboot erase recovery
fastboot erase boot
fastboot flash recovery </path/to/oem/RECOVERY.img>
fastboot flash boot </path/to/oem/BOOT.IMG>
fastboot erase cache
fastboot reboot
Hopefully, at this point your bootloop issue is resolved and your ROM boots normally. If not, then read on.
Uh oh, time to flash SYSTEM.img and USERDATA.img too and see if that makes a difference. While we're at it, let's also reflash BOOT.img and RECOVERY.img. Use the following commands (replace /path/to/oem/ in the commands below with the full path to the files you extracted from your OEM firmware):
Code:
fastboot erase recovery
fastboot erase boot
fastboot erase system -w
fastboot flash recovery </path/to/oem/RECOVERY.img>
fastboot flash boot </path/to/oem/BOOT.IMG>
fastboot flash userdata </path/to/oem/USERDATA.IMG>
fastboot flash system </path/to/oem/SYSTEM.IMG>
fastboot erase cache
fastboot reboot
...and hopefully now you're back up and running.
Good luck!
In case you don't have a unlock code and *already* bricked it, you can get the imei from fastboot as well. Simply send the following command from fastboot:
fastboot oem get-psid
Using the imei you can then request an unlock code from huawei on their web site.
Thank you both for replying!
Unfortunately, I don’t have an unlock code. I have contacted Huawei through https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail months ago asking them for an unlock code for the bootloader but I never got a reply. I have even tried again a couple of months ago but they didn’t answer back. It seems there is a limitation on the time entitled to ask for an unlock code – I believe 3 or 6 months if I remember correctly.
I have just tried contacting them again through an e-mail form, let’s hope this time they’ll reply.
Now please allow me to fill you up in some more test/trials I did today:
I issued the “fastboot oem get-bootinfo command” and the result is this:
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
(Not even a milisecond in replying. This looks a bit suspicious, right?)
But when I try to continue as per your instructions (i.e. issue the command “fastboot erase recovery”) this is what I get:
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
So I cannot go on using your suggestions
I have also tried to use DC-Unlocker to unlock the bootloader (perhaps wasted money since the bootloader is already unlocked but I just wanted to try). When I bought the credits and opened DC Unlocker Client, the option for Unlock was grayed out, but the option for Factory Reset Protection was selectable. Based on this, I am now suspecting that the tablet has got FRP protection enabled, since I did have a PIN set-up before choosing the wrong model in TWRP manager and brick it. So I tried DC Unlocker’s Factory Reset Protection (paid 15 wasted euros!) but again no luck. This is the log from that attempt:
===================================================================
Before detection Huawei Android phones, enable 'Manufacture' mode:
in dial pad type *#*#2846579#*#* for Qualcomm and Kirin based models, or *#*#14789632#*#* for MTK, then select
'ProjectMenu',
'Background settings',
'USB ports settings',
'Manufacture mode'.
Step by step guide for other Huawei phone unlock:
https://www.dc-unlocker.com/huawei_phones_detect_unlock_tutorials
===================================================================
DC - Unlocker 2 Client 1.00.1322
Detecting phone :
selection :
manufacturer - Huawei phones
model - Auto detect (recommended)
Found Phone : HUAWEI M2-803L
Model : Huawei phone in fastboot mode
Serial NR. : YVF4C15928000296
Firmware : V100R001C00B000
unlocked
Battery state: 3648mv
===================================================================
Factory reset protection Erase start
unknown error (398)
===================================================================
Since I already paid the €15 at DC Unlocker I decided to give a go using their other piece of software, DC Phoenix. This one allowed me to flash pieces of the UPDATE.app package while in fastboot mode, without complaining about locks. It seemed to be flasing normally (I tried flashing all contents of the latest UPDATE.app package) and then (as per DC’s instructions) I tried re-flashing everything using the second option (Upgrade Mode) while in Repair mode (i.e. Vol +/- pressed while powering the tablet).
No success either – Tried various combination of DC Phoenix – even only the files you suggested (BOOT & RECOVERY, BOOT & RECOVERY & USERDATA & SYSTEM).
Is there a way to find out if FRP has been activated through fastboot? Tried Googling it but no usable results came up.
Any other suggestions would really, really be appreciated!
manowar666 said:
Thank you both for replying!
Unfortunately, I don’t have an unlock code. I have contacted Huawei through https://emui.huawei.com/en/plugin.php?id=unlock&mod=detail months ago asking them for an unlock code for the bootloader but I never got a reply. I have even tried again a couple of months ago but they didn’t answer back. It seems there is a limitation on the time entitled to ask for an unlock code – I believe 3 or 6 months if I remember correctly.
I have just tried contacting them again through an e-mail form, let’s hope this time they’ll reply.
Click to expand...
Click to collapse
I did contact Huawei for an unlock code, myself - I sent emails to [email protected] and [email protected] and received a reply back from them the next day. Here is what they said:
Dear User,
Huawei Customer Service is pleased to be at your service.
Apology for any inconvenience.
If you would want to unlock your phone, you should meet the following conditions:
1.Please register your Huawei ID in our official website http://emui.huawei.com/en/ on your phone.
2.Log in your Huawei ID continuously for 14 days.
3.Each Huawei ID should not apply for the unlock code more than twice within 6 months.If you meet the criteria,please go to http://emui.huawei.com/en/ and click the 'download'button to login your Huawei ID other than any other third party ID to apply for the unlock code.Please contact us by mail or local service hotline as following if error message appears.
TEL: http://consumer.huawei.com/en/contact-us/index.htm?tag=hotline
Mail: http://consumer.huawei.com/en/contact-us/index.htm?tag=email
Please submit your mobile model, SN, IMEI/MEID and erro message in your e-mail.We also need to know that your phone is rooted, it can be out of the best working state and some of the functions may not be able to work normally. In additon, the system is vulnerable to be invaded by viruses once your phone is permitted to unlock. For the lack of testing,third party software may not be compatible with your phone. Unlocking will bring unexpected negative impacts and the device will be not normal, and can not be restored, Huawei after-sales service office will not provide warranty service for your rooted phone, and you may bear the cost. So we strongly advise you to think twice.
If you have any other problems, please send your feedback to us. We will be at your service to help you to solve your problems.
Once again thank you for contacting Huawei device.
Best Regards.
Huawei Device Customer Care Team
Click to expand...
Click to collapse
I didn't want to faff around with all that logging in nonsense for two weeks, and also the Huawei bootloader code site seemed to be offline (kept getting "Page not found" errors with the error page in Chinese characters and what was ostensibly an HTTP 600 error, which was why I contacted Huawei support over email), so I just ponied up about $4.25 for 4 dc-unlocker credits (4 euros) and got my bootloader unlock code from the dc-unlocker software. Neat, clean, easy and non-messy.
manowar666 said:
Now please allow me to fill you up in some more test/trials I did today:
I issued the “fastboot oem get-bootinfo command” and the result is this:
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
(Not even a milisecond in replying. This looks a bit suspicious, right?)
Click to expand...
Click to collapse
Yes, that does seem very odd. I would expect it to take at least some time in userspace (the "total time" field).
manowar666 said:
But when I try to continue as per your instructions (i.e. issue the command “fastboot erase recovery”) this is what I get:
erasing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: -0.000s
So I cannot go on using your suggestions
I have also tried to use DC-Unlocker to unlock the bootloader (perhaps wasted money since the bootloader is already unlocked but I just wanted to try). When I bought the credits and opened DC Unlocker Client, the option for Unlock was grayed out, but the option for Factory Reset Protection was selectable. Based on this, I am now suspecting that the tablet has got FRP protection enabled, since I did have a PIN set-up before choosing the wrong model in TWRP manager and brick it. So I tried DC Unlocker’s Factory Reset Protection (paid 15 wasted euros!) but again no luck.
Click to expand...
Click to collapse
I find it very peculiar that your bootloader is unlocked but FRP is activated. I think that dc-unlocker does not give you the option to unlock the bootloader because FRP protection is still active - according to all guides, FRP must first be deactivated if you want to unlock the bootloader.
What does your phone say in the bootloader screen for the FRP? You'll find it directly under the "Phone Unlocked" text. It should say either "FRP Locked" in green or "FRP Unlock" in red.
manowar666 said:
Is there a way to find out if FRP has been activated through fastboot? Tried Googling it but no usable results came up.
Any other suggestions would really, really be appreciated!
Click to expand...
Click to collapse
There isn't, directly, but you can try to issue the fastboot command
Code:
fastboot oem frp-erase
although at this point I am not very hopeful that it will work.
FRP is nothing but the developer option to allow an OEM unlock of the phone - it is the option mentioned in this image in the Huawei "Unlock bootloader" guide thread.
Like I said, I find it very peculiar that FRP is enabled but the bootloader is "unlocked". Did you at any point reset the developer options or reflash the stock ROM before you soft-bricked the device? Did you pick up this phone second-hand/used or something?
I think that the root (excuse me, I couldn't resist) of all your problems is that FRP is still enabled, and this is what is causing your flash attempts to fail.
Here is the dc-unlocker guide to repair a bricked Huawei phone even if the bootloader and FRP are locked. If you follow this guide very carefully, maybe it can save you. Since you already seem to have tried "Method 1" of the guide, maybe you can try "Method 2".
Another suggestion I have is that you can contact the dc-unlocker guys for online chat support (when you see that the chat is online). They are very helpful, and since you've thrown so much money at them (be sure to mention that, just in case they don't know), they should be able to do something to help you out. Good luck, and I hope that you can get your phone back online...
I've been faced with all the same issues as the OP for the last 24 hours and thought all was lost. I had been through all the same stuff - every fastboot command and every key combination possible. I'd tried different tools and apps to get some life out of the device but no luck. I had even downloaded the ROM from beast.in.black's thread and extracted it to the SD card but it didn't do anything for me.
Worse still, the tablet was now out of juice. And as soon as I plugged it into the mains, the screen lit up and the all too familiar fastboot screen would stay on, meaning the tablet was barely charging long enough for me to try anything new with adb / fastboot or whatever.
So in trying to get the screen off and charge the tablet, while it was plugged in I held vol up / vol down / power together for 10 seconds. I was hoping this would leave the screen off (I had managed this earlier while plugged into USB) but instead it booted again. So I walked away for a minute, then came back expected to see the fastboot screen but no, it was in the middle of an EMUI software install. Huzzah! I left it to do its thing but at the end, it came up and said install failed and my only option was to press power to reboot. Sigh. So I pressed power and then got another surprise. The Huawei boot logo. The tablet was booting. A few seconds later I'm at the "Choose your regional settings & language" screen in the setup wizard. After trying everything under the sun, it turns out all I needed was the ROM on the SD card and to give the tablet the three-finger-salute while plugged into mains.
Happy days!
I found the Official M2-803L ROM!
For anyone who needs it, I've found an official download (direct from the Huawei China support site) for the M2-803L.
I've posted the ROM details here for anyone who needs this ROM.
Status update for anyone that might be interested: I was able to restore the tablet with the help of DC-Unlocker. I highly recommend them for any unlocking/restoring needs.
More specifically, I contected them via email and they were kind enough to give me credits (since I already paid them) in order to try again with Method 2 as per https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Step 2 of this method did not work for me (i.e. flashing in upgrade mode) but I was able to replace this step simply by re-flashing with DC Phoenix in fastboot mode.
After this, my IMEI was zeroed-out (that was a problem since this tablet is 4G-enabled thus I couldn't register on my provider's network) but I was also to fix that by using HCU-Client (had to purchase 8 more credits from DC-Unlocker).
All are working fine now.
Special thanks to @beast.in.black for pointing me towards the right direction!
hello
got the new version of Android (oreo).
I did the installation using adb. Once installed, the phone did not boot. Rebooted on the Google logo.
Now I can not do anything, Because it is not oem unlock and then I can not unlock the device, to flash again.
When using adb, I use adb devices, the device does not show me, but the fastboot devices I use show the serial device.
I searched and searched all the necessary possibilities in this case and did not know the driver, and apparently there was no problem.
Anything I want to do is require oem unlock and when I put this command in adb. It looks like:
FAILED (remote: oem unlock is not allowed).
And I can not do anything.
Hi!
I´m not new into flashing mobile phones, but with my new Mi Max 3 I´m not sure to do the right things.
I bought the 6Gb/128Gb Variant (so Chinese or international Version) and the Seller (from Gearvita) sent me the Phone with unlocked Bootloader and GlobalRom. It seems to be the official Global Rom, because there are normal OTA Updates from Xiaomi and they work.
I tried to flash TWRP via fastboot mostly for enabling Camer2Api and for changing the DPI with root-access, but there is no responding from the phone while Fastboot Mode
ADB Driver are installed, Developer Options and USB-Debugging are enabled. If I start the CMD or PowerShell it recognized "adb devices" as normal and with the command "fastboot bootloader" the phone goes into Fastbootmode, but then there is no reaction anymore to any command. "fastboot devices" says "no device found" , "flash recovery .img" says nothing or sometimes it says image "size too large"
So what is the best way to get a save unlocked bootloader official from Xiaomi? Mi Unlock Tool don´t recognize my phone, too :crying:
I know I should go back to normal Chinese Rom and locked bootloader, than unlock the bootloader official way and then flash GlobalRom and install TWRP, but how to get back to CN Rom without doing any mistakes?
I´m on latest 10.3.5.0 since yesterday - I hope there is no problem with ARB in that case.
Thanks in Advance
In the meantime I checked the fastboot behavior with an older Notebook (Windows 7) and now everything is working correctly.
I had to use adb sideload in TWRP and was able to install Magisk and Camera 2 API Enabler.
But I tried soooo many Driver Setups with Windows 10 and nothing was workling as it should
I´m not sure if I have still a fake unlocked bootloader, but everything is working for me now
Chainz007 said:
Hi!
I´m not new into flashing mobile phones, but with my new Mi Max 3 I´m not sure to do the right things.
I bought the 6Gb/128Gb Variant (so Chinese or international Version) and the Seller (from Gearvita) sent me the Phone with unlocked Bootloader and GlobalRom. It seems to be the official Global Rom, because there are normal OTA Updates from Xiaomi and they work.
I tried to flash TWRP via fastboot mostly for enabling Camer2Api and for changing the DPI with root-access, but there is no responding from the phone while Fastboot Mode
ADB Driver are installed, Developer Options and USB-Debugging are enabled. If I start the CMD or PowerShell it recognized "adb devices" as normal and with the command "fastboot bootloader" the phone goes into Fastbootmode, but then there is no reaction anymore to any command. "fastboot devices" says "no device found" , "flash recovery .img" says nothing or sometimes it says image "size too large"
So what is the best way to get a save unlocked bootloader official from Xiaomi? Mi Unlock Tool don´t recognize my phone, too :crying:
I know I should go back to normal Chinese Rom and locked bootloader, than unlock the bootloader official way and then flash GlobalRom and install TWRP, but how to get back to CN Rom without doing any mistakes?
I´m on latest 10.3.5.0 since yesterday - I hope there is no problem with ARB in that case.
Thanks in Advance
Click to expand...
Click to collapse
Interesting. I have a somewhat similar experience. Got a China phone with global rom (4/64GB variant.) The phone updated to 10.3.5.
I immediately rooted it (using TWRP boot; did not flash TWRP - with a magisk Zip) an all seemed fine.
After your post I tried to test the process again - and to my greatest surprise
1. I see the phone with fastboot devices but
2. The same TWRP I booted in before (with the same software version) does not boot any more
I get an error message with adb and the phone reboots.
Not sure where to go from here...
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
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