Develop Bugs

[Q] Trouble Unlocking Bootloader

Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.

Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.

abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.

abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app

I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967

Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.

Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults

UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.

Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/

Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.

Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).

It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it

I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?

razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.

Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve

Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app

@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices

I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...

Bootloader or oem unlock not working

HELLO
I want to unlock my lenovo p2 and install twrp in it but in oem unlock option if i was pressing it was showing LENOVO ID WITHOUT PERMISSION and not going forward.help me to root my phone

yasaswi2509 said:
HELLO
I want to unlock my lenovo p2 and install twrp in it but in oem unlock option if i was pressing it was showing LENOVO ID WITHOUT PERMISSION and not going forward.help me to root my phone
Click to expand...
Click to collapse
You will need to verify you Lenovo account, an e-mail will be sent to the address you used to set up your account. Once verified go back to OEM/Bootloader unlock to start the 14day wait.
Hope that helps.

I have verified the link that i got and it states success but iam not able to unlock its saying network unavailable even if i was connected to net

I have the same issue. Did you fix this already?

If you aren't on global release over the world version you can't unlock BL. Send a screenshot of about phone or build number.
Sent from my Lenovo P2a42 using Tapatalk

yasaswi2509 said:
HELLO
I want to unlock my lenovo p2 and install twrp in it but in oem unlock option if i was pressing it was showing LENOVO ID WITHOUT PERMISSION and not going forward.help me to root my phone
Click to expand...
Click to collapse
Did you find any solution for this. I am also facing the same issue.

Same issue here.
I thinks it started after the july security update for nogat!

QUAD_FOXX said:
I thinks it started after the july security update for nogat!
Click to expand...
Click to collapse
No. The July security update came on August. The first post on this thread came in July. So, this has nothing to with the new security patch. I checked two days ago and it synced correctly. It was only yesterday that I started experiencing this issue. I just hope it's a temporary problem.

medwatt said:
No. The July security update came on August. The first post on this thread came in July. So, this has nothing to with the new security patch. I checked two days ago and it synced correctly. It was only yesterday that I started experiencing this issue. I just hope it's a temporary problem.
Click to expand...
Click to collapse
oh.. i hope the same

QUAD_FOXX said:
oh.. i hope the same
Click to expand...
Click to collapse
1. When did you start observing the issue ?
2. Do you have the 32 GB model out of 64GB model?

Ive EU version. What I did was to log out from the Lenovo account when I tried to check how many days it was left of the 14 days "saftey".
edit: lol, tried it now and nope same error as you guys.

Same problem here and I have no clue what I could do so far now.
Is there no solution out there? Probaply not a good choice of smartphone?

maggy2011 said:
Same problem here and I have no clue what I could do so far now.
Is there no solution out there? Probaply not a good choice of smartphone?
Click to expand...
Click to collapse
I think we have proof now that is not an isolated issue. A lot of us are experiencing it at the same time. There was a similar issue last week for OTA updates, but after some pressure in the Lenovo forum, the servers were back online. I don't know if this is a temporary problem and the servers will be online soon, or OEM unlock service is down for good.

medwatt said:
1. When did you start observing the issue ?
2. Do you have the 32 GB model out of 64GB model?
Click to expand...
Click to collapse
yesterday. it was the first time checking after the update.
---------- Post added at 02:06 AM ---------- Previous post was at 02:06 AM ----------
QUAD_FOXX said:
yesterday. it was the first time checking after the update.
Click to expand...
Click to collapse
yea 32gb model

medwatt said:
I think we have proof now that is not an isolated issue. A lot of us are experiencing it at the same time. There was a similar issue last week for OTA updates, but after some pressure in the Lenovo forum, the servers were back online. I don't know if this is a temporary problem and the servers will be online soon, or OEM unlock service is down for good.
Click to expand...
Click to collapse
After have tried Lenovos "support" before I will not send a bug report to them. Hopefully someone else will do it thou

Does a factory reset help (do I need to wait another 14days?) ?

I could run the oem unlock command in fastboot
No reset needed, just ignore the message ( LENOVO ID WITHOUT PERMISSION)

robuser007 said:
I could run the oem unlock command in fastboot
No reset needed, just ignore the message ( LENOVO ID WITHOUT PERMISSION)
Click to expand...
Click to collapse
Could you be kimd to post the command you used?

robuser007 said:
I could run the oem unlock command in fastboot
No reset needed, just ignore the message ( LENOVO ID WITHOUT PERMISSION)
Click to expand...
Click to collapse
I am having the LenovoID without permission issue but this is happening when trying to turn on allow OEM bootloader unlocking in the developer options and I believe this has to be turned on before the fastboot command will work.
When I try the fastboot command of fastboot OEM get_unlock_data to get the code I need to convert for the unlock code, it returns Not Found for all values.
I contacted sorry about this but they want talk about it because they don't 'support it', I sent them the link for getting the code converted (https://motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-b) and said if you don't support it why do you offer the service? And they said yes we provide the service but don't support it. . Asked who could give support on this and they said they don't know...
---------- Post added at 08:22 PM ---------- Previous post was at 07:47 PM ----------
I've just seen in another thread that the OTA servers are down because there is a new update coming so maybe these are on the same server and it will be up again soon.

AGAWhitty said:
I contacted sorry about this but they want talk about it because they don't 'support it', I sent them the link for getting the code converted (https://motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-b) and said if you don't support it why do you offer the service? And they said yes we provide the service but don't support it. . Asked who could give support on this and they said they don't know...
Click to expand...
Click to collapse
Sorry, but this is so funny. Because its sooo typical Lenovo service

Help 20days and still unable to unlock

Hi, i send many email to emui support and no matter I wrote they say create an account and wait 10-15 days.
They doesn't seem to want to help.
So now what can I do !! I buy an Honor 7X and just 1 week after redmi note 5 to be able to use root, custom rom, etc...
Two phone buy for nothing, why but why I sale my Nexus 5X....
I do all I must do, create account, OEM unlock, bind, debug USB.....
I have 4 miflash_unlock tools and I use all of them.
Every time I try I have many things appear :
Error -1, Chinese word !?!, Unable to unlock to try this account, 27 hours unlock phone, cannot connected, etc.
I have like 20 message different.
Every time the process is not the same.
So PLEASE someone help me. The MIUI support doesn't care, they repeat the same thing in here email every time.
I'm tired.
HELP

Vink67 said:
I do all I must do, create account, OEM unlock, bind, debug USB.....
I have 4 miflash_unlock tools and I use all of them.
I have like 20 message different.
I'm tired.
HELP
Click to expand...
Click to collapse
Sorry to hear that but you must have made a mistake somewhere as everybody get unlocked after 360hours.
Just redo everything from scratch, yeah again 15days but better than nothing hun.
You need one account / one miflash tool.
Check again thread here or miui forum or telegram.
I use method of old miflashtool.
Create account email.
Login in phone not in developing mode.
Go in developing mode
Enable oem unlock
...
You will manage like the others

rodolphe06 said:
Sorry to hear that but you must have made a mistake somewhere as everybody get unlocked after 360hours.
Just redo everything from scratch, yeah again 15days but better than nothing hun.
You need one account / one miflash tool.
Check again thread here or miui forum or telegram.
I use method of old miflashtool.
Create account email.
Login in phone not in developing mode.
Go in developing mode
Enable oem unlock
...
You will manage like the others
Click to expand...
Click to collapse
Where I must go to create new account?
Must I use another phone number?
Can you tell me more about step by step.
Thanks

Vink67 said:
Where I must go to create new account?
Must I use another phone number?
Can you tell me more about step by step.
Thanks
Click to expand...
Click to collapse
Follow this thread
https://forum.xda-developers.com/re.../solution-unlocking-bootloader-redmi-t3800161
Create account with email not phone number.
You shall delete all your accounts may be or at least ask on miui en forum to see if a dumb solution exists for usecase where you have waited more than 360 hours.
Otherwise start from scratch.

[Solved] Xiaomi Redmi Note 8 Pro hard brick

I tried unsuccessfully to install TWRP on a Xiaomi Redmi Note 8 Pro.
These are the steps I took:
Unlock the bootloader with MiUnlock.
Downloaded Fastboot.
Copied this CFW TWRP inside the Fastboot folder.
Downloaded these two files and copied inside the Fastboot folder.
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash recovery twrp-3.3.1-0-begonia_UNOFFICIAL.img
fastboot reboot
And the result is that it no longer turns on. It also fails neither to enter the Fastboot screen, nor in that of recovery.
Windows no longer sees the device, so I can't interact in any way even with the folders inside the phone memory. Finally it is not even seen by Xiaomi Flash Tool (wanting to try to reinstall the official ROM).
The phone, immediately after unlocking it with the Xiaomi tool, had MIUI 12. I don't know which Android mounted (my fault), but I proceeded the same, without doing a downgrade, since in a discussion here on the forum it seemed that it could work same, even without downgrading to Android 9.
Is there any way to fix?
Maybe using Linux, you might be able to interact with the phone memory even if it is turned off / bricked?

Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!

Only if you have flashed it with a CFW
Angry Unlocker said:
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.

I had the same problem
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)

Thanks for your answers!
kingsemperor said:
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.
Click to expand...
Click to collapse
I am not quite clear what you mean exactly, but I, before proceeding with trying to flash a custom ROM, I had connected my original Xiaomi account to the device in question and also had requested the unlocking of the bootloader through the appropriate Xiaomi software (and I finally waited the time indicated by them, before proceeding). So on my Note 8 Pro there was actually the original / official MIUI updated to the latest version and I didn't need to proceed with a payment of any kind following that tutorial.
chumpokemon said:
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)
Click to expand...
Click to collapse
Thanks for your suggestion, but I have already solved it by following precisely that video.

How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?

Perike said:
How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?
Click to expand...
Click to collapse
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg

chumpokemon said:
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg
Click to expand...
Click to collapse
Flashed successfully, but the result is a reboot and This Miui version cant be installed on this device...

Angry Unlocker said:
Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Why does it say "this video is private" ?

Question Help please, Poco f3, black screen after failed rom install, no fastboot

Soo, I was installing eu rom via fastboot when accidentally close the terminal windows that was running the sh file (I was doing some other thing with homebrew, thought that was the one I was closing, yes I was careless) decided to relaunch the .sh file but it got stuck on waiting for the device, decided to try and restart my phone, only problem is that after exiting fastboot cant seem to get out of blackscreen, Im completely lost, any help is appreciated

That's not good. You now likely have to use EDL Mode to flash a ROM.
Problem is, Xiaomi locked the EDL Mode to Xiaomi Authorised Service Centers, who have an Authorized Account to initiate the Flash.
They did this to stop people from importing the Chinese Variants to EU/USA, flashing ROM and selling them for Cheap.
<Moderator Edit>: @cyanGalaxy, I'll let you know just as soon as I can about what I removed from this post and why.
I have experience with that because I've gone through it. <Moderator Edit>

cyanGalaxy said:
That's not good. You now likely have to use EDL Mode to flash a ROM.
Problem is, Xiaomi locked the EDL Mode to Xiaomi Authorised Service Centers, who have an Authorized Account to initiate the Flash.
They did this to stop people from importing the Chinese Variants to EU/USA, flashing ROM and selling them for Cheap.
You probably have to pay someone $35 on Telegram. They'll help you unbrick your phone. They'll do this by remote-controlling your PC.
I used this group https://t.me/miauthofficial_d
I had to do this once and it worked.
It may be possible for cheaper, maybe elsewhere ^^ I did it using the Telegram Group I linked above for ~24€ ($35).
I have experience with that because I've gone through it. If you want I can leave you my Discord if you need more help... cyanGalaxy#3161
Click to expand...
Click to collapse
Isn’t there any other way? I mean letting someone tunnel to my pc sounds fishy to say the least, isn’t there maybe a modified version of the program or something that I could use?

<Moderator Edit>
Edit: I just saw my previous reply got edited by a moderator. I think it's not allowed here to mention these kinds of services, but it's not an advertisement at all. I'm just saying what helped me when I hardbricked my phone. :S
I mean other than such a service, you could go to a Xiaomi Store and perhaps use Warranty-Claim?

cyanGalaxy said:
I saw a program some time ago here on XDA that was just 1€/$1 to unbrick your phone over EDL, but I don't remember the name..
Yes, it does sound hella sketchy but it is a real service.
View attachment 5664369
Edit: I just saw my previous reply got edited by a moderator. I think it's not allowed here to mention these kinds of services, but it's not an advertisement at all. I'm just saying what helped me when I hardbricked my phone. :S
I mean other than such a service, you could go to a Xiaomi Store and perhaps use Warranty-Claim?
Click to expand...
Click to collapse
Sadly, its a few weeks out of warranty and the closes Xiaomi store is about two hours from here, will try to go, but who knows if they will even consider repairing it

Bruh124 said:
Sadly, its a few weeks out of warranty and the closes Xiaomi store is about two hours from here, will try to go, but who knows if they will even consider repairing it
Click to expand...
Click to collapse
Ok, yeah that sucks. <Moderator Edit> I can explain the other choice in more detail, since I've gone a hardbrick and so know a bit about it.
But if the Xiaomi Store would do it, that's also good.
<Moderator Edit>
I don't know if flashing Custom ROMs invalidates Warranty-Claims. ^^ (i know yours is out of it already, but maybe they have mercy)