Database Users

[Q] Unable to unlock bootloader. RMA my only option?

As title suggests, my bootloader is locked and my N7 will not boot past the Google logo. If i try Recovery, it says "booting failed" so I can only assume that it was lost/erased. Is an RMA through Asus my only choice at this point?

If you can boot into bootloader mode (which you can) you can use fastboot to flash a stock image. Here is a fine guide. It seems like something on your data and/or recovery partition got corrupted. If you still have a warranty, you should send it to RMA. But it's your choice.

Erovia said:
If you can boot into bootloader mode (which you can) you can use fastboot to flash a stock image. Here is a fine guide. It seems like something on your data and/or recovery partition got corrupted. If you still have a warranty, you should send it to RMA. But it's your choice.
Click to expand...
Click to collapse
I can get to bootloader but I am unable to unlock it. When I try to unlock it, it gives me the prompt, I click YES and then it just goes back to bootloader but still locked.

Well, that's interesting. I don't know what could it be. I guess, RMA is your best option.

engagedtosmile said:
I can get to bootloader but I am unable to unlock it. When I try to unlock it, it gives me the prompt, I click YES and then it just goes back to bootloader but still locked.
Click to expand...
Click to collapse
Hi, engagedtosmile...
This seems to be a common problem... inability to unlock the bootloader... I've come across it a few times, both here on XDA and on other forums.
As I suggested a while ago with this guy who had a similar problem... it could potentially be an eMMC chip gone bad, a corrupted partition structure (very unlikely though, since both his and your Nexus 7 boots and works fine otherwise) or a corrupted bootloader (extremely unlikely, as the Nexus 7 wouldn't boot at all).
As a bit of a last ditch 'clutching-at-straws' suggestion, I advised him to try a different USB port on his PC and/or a different USB cable... my experiences of using fastboot, is that it can be remarkably fussy about such things at times.
Anyway, it appears to have worked for him.
So, it might be worth a shot... change to a different USB port, and/or maybe try a different USB cable.
Good luck... and hope you have as much success as the guy whose post I referenced above.
Rgrds,
Ged.

Report Your Problems with the Official ASUS Bootloader Unlock Tool Here

There's a bunch of threads about the bootloader unlock tool existing, not any real place to aggregate reports of problems with it. So, if you've attempted to unlock your bootloader using the official ASUS tool and are having problems, please post your situation.
Reported instances:
myself
DeathStolas
ASUS_Khang
Rattraps123
m3t4lw01f
creison
both are experiencing bootloader unlock limbo. The tool seems to have worked, but going into fastboot shows two progressive screens:
1) Unlock Successfully reboot in 5 seconds
2) FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Clearing the cache goes through the loop again. Mind you, this loop only happens when you're trying to get to the bootloader. If you go to recovery or normally boot, you won't have any issues.
However, any commands sent via fastboot fail, so the bootloader is still locked. Attached is an image of the second bootloader screen.
ASUS_Khang is already getting in touch with technical folks to investigate as well, but I figure it best to see if anyone else is having issues with the official tool.

Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...

I have to laugh at the fact that someone on XDA unlocked the bootloader successfully with none of these problems and then ASUS give an "Official Unlock Tool" that screws up the phone of any who uses it... In the words of Alanis Morrisett - "Isn't it Ironic"...

m3t4lw01f said:
Having your device encrypted prevents the unlock tool from working it seems...had to factory reset then I could run it and it "worked".
I, too, have the Unlock Successfully reboot in 5 seconds message though, so at this point I'm hoping ASUS comes through.
EDIT: Now I am getting the:
FASTBOOT CMD WAITING...
RESULT: FAIL(can not mount the necessary partition)
Error when I reboot to the bootloader (I did nothing else, just used the phone for a bit and decided to try rebooting again).
If it matters, I did NOT have a PIN set on my phone when I ran the tool and it complained at me when running it, but allowed me to continue. Shot in the dark here that maybe that's related. Wondering if other people had a PIN or not when they ran and are having the same errors...
Click to expand...
Click to collapse
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.

Same problem here. I used the official unlocker tool and it did what it said it was going to do, but... I got the mythical "Bootloader 5 sec reboot".

asus is working on a fix.

playingmax said:
asus is working on a fix.
Click to expand...
Click to collapse
I'm sure that they are, but it would be interesting to see a source for that claim.

darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.

m3t4lw01f said:
There's an official ASUS rep in another threads keeping us in the loop on what's happening.
He even sacrificed his own device and ended up with the same problem.
Going to need a little patience here while we wait for some more info.
Click to expand...
Click to collapse
Sounds good. Can't wait till this is all sorted out and I can continue on with installing Cyanogenmod for my SO. She is really excited since it's her first Android phone.

darkdragon505 said:
I'm sure that they are, but it would be interesting to see a source for that claim.
Click to expand...
Click to collapse
here you go
http://myzen.asus.com/2015/10/13/official-bootloader-unlock-for-zenfone-2-is-now-available/
look at Khang Thai (ASUS REP) reply. they are working on a fix.

Kona67 said:
Same problem. I unlocked without pin. Bootloader is unlock with withe spash screen but always ...unlock successfully... reboot after 5 sec.
Click to expand...
Click to collapse
Same issue ... I tried without a pin .. now added a pin and it asked me for it when trying to run the app again ... but that didn't help !
Help Ausus!!!

Mine says unlock failed rebooting in 5,4,3,2,1.

any way to relock bootloader as zenfone 6,5,and 4 have

When the 5 second bootloader issue is fixed you should hear about it here first, we have an Asus employee helping us: http://forum.xda-developers.com/zenfone2/general/official-asus-ze551ml-bootloader-unlock-t3224747

https://fsfe.org/news/2012/news-20121106-01.en.html
Enviado do meu iPhone usando o Tapatalk

Looks like a user has solved the 5 second reboot issue. Check out the rather convoluted method here: http://forum.xda-developers.com/showthread.php?p=63498472

[Q] Bricked Nexus 4

Hello Guys,
yesterday I restarted my Nexus 4, running the cm-13.0-20160520-NIGHTLY-mako. It stuck at the bootlogo, so I tried to reflash it in the twrp 2.8.7.0 recovery. But I got the error message "E:/ unable to mount /cache".
After that I was trying to solve this issue by wiping the cache, but I got the same error message -> The phone wasn't booting
From now on I did several things to solve my problem. I don't know the exact order.
- I've downloaded the Nexus Root Toolkit from WugFresh -> Tried to use the Flash Stock + Unroot Option with Soft-Bricked/Bootloop status enabled -> I choosed the 5.1.1 Factory Image -> In the cmd window, I get in every point the same error message "Falied (remote: flash write failure) -> I get the same message when I'm trying to manually flash each part of the factory image via fastboot
- Within the Toolkit I also tried to format cache, system and Userdata, but afther this I get the same error when trying to do the step before
- I think also used the Fastboot Flash options, but I'm not sure.
- After that I attempted to flash the cm13.zip via adb-sideload in TWRP. Here is a part from the error message I get:
"(...) could not detect filesystem for /dev/block/platform/msm_sdcc.1/by-name/system, assuming ext4
mount: failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system: Invalid argument
unmount of /system failed: no such volume (...)
E: Error executing updater binary in zip 'sideload/package.zip'
E: Unable to mount '/data'
- In TWRP the Internal Storage is shown with 0mb
- Currently only the bootloader is working fine and I also can get a fastboot and adb connection to the phone
-> Loading the recovery is only possible by booting a recovery image in fastboot
Can somebody tell me if it is possible to restore my Nexus 4 and how to do it?
Thank you in advance :fingers-crossed:
PS: I hope I mentioned all the important points. If some information is missing, feel free to ask me.

Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?

audit13 said:
Did you try to manually flash the latest rom?
Did you try to flash a stock 4.2 rom?
Tried different USB cables and USB ports?
Click to expand...
Click to collapse
Thank you for your answer.
I tried to flash the newest cm13 in TWRP and with adb Sideload. I get the same error.
Also the 4.2 Stock rom doesn't work. Same problem as with the 5.1.1 factory image.
I also switched the cable and the USB ports, but it leads to the same error messages.

Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.

From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.

audit13 said:
Try flashing the userdata.img file in fastboot. As soon as userdata finishes flashing, use the buttons to boot into recovery and perform a factory wipe. User the usedata.img file included with the stock ROM you flashed.
Click to expand...
Click to collapse
I get the same error message as always: Falied (remote: flash write failure)
nerotNS said:
From what I see, your partitions got completely messed up. I reckon if it's fixable at all (assuming your chip ain't dead), the only thing that can fix it is fully reflashing everything via emergency mode. Now I can't seem to find the exact link, but I do know there was a thread on xda with instructions and everything. I'll keep digging around to see if I can find anything and then I'll link it here.
Click to expand...
Click to collapse
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:

Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.

audit13 said:
Does the bootloader remain unlocked after rebooting? The emmc chip could be messed up and need replacement.
Click to expand...
Click to collapse
Unfortunately yes. After locking the bootloader via fastboot, the bootloader is marked as unlocked after rebooting.
Do I have to change the mainboard?

This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.

audit13 said:
This confirms that the emmc chip is damaged and can only be fixed via a motherboard swap.
I had similar problems with two nexus 5 phones where I would unlock the bootloader but would always relock on reboot.
Click to expand...
Click to collapse
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.

tobi.king said:
I get the same error message as always: Falied (remote: flash write failure)
In Meanwhile I also think that my partitions are messed up. I saw one thread that could help me (http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060), but some of the links are down.
Thank you for your help. :good:
Click to expand...
Click to collapse
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
tobi.king said:
Ok. Doesn't sound very good.
Nevertheless I will try the method of nerotNS, if he finds the thread.
Click to expand...
Click to collapse
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.

nerotNS said:
Aye that's the thread I've been talking about. And yeah, the links are down for quite a while, I reckon the OP doesn't maintain it anymore. Anyways I used the tool once, I found all the files by Googling for like 4 hours or so - the most difficult one being the .dll file and getting the program itself to run. I'd upload them to you but there were on my C disk on my main rig and that got wiped when I reinstalled Windows :S I'm sure the files are on the net even now tho, I remember getting the .dll file from some Chinese website, Chrome's translator gave me enough info to actually download the file. Once I got it up and running the flash was OK, I've tested the method from that thread myself, the only problem is getting the files from the links that are down. I wish you good luck in your search for them, I know what an awful feeling it is for your nexus to die, my mako is still my daily driver, still kickin' ass
I did however have to change the motherboard out, since, while the flash was ok, the chip was not, so it didn't help much. I had an issue with my /data partition where it was completely gone, and the while filesystem got messed up, the only thing I could boot to was bootloader and even that only while on charger. Eventually I swapped my motherboard with a friends who didn't need her nexus 4 anymore and now it's ok. I suggest you first attempt the method from that link and if that fails, then you should resort to getting a new motherboard, but imo only if you can get it either dirt cheap or in a way like I did. Caching out around 100$ for a new nexus 4 mb, with phones like nexus 5X 32Gb costing 300$ is not a good investment if you ask me.
Click to expand...
Click to collapse
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.

tobi.king said:
I found all the necessary files for doing the method subscribed in the thread, but afther flashing the firmware nothing changed. Only thing that worked was the bootloader, everthing else still wasn't working.
Fortunately I had a broken Nexus 4 from a friend. So I switched both mainboards and my Phone is working again
Thank you for your help.
Click to expand...
Click to collapse
Awesome, glad to be of service

Encryption unsuccessful

Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.

laofan said:
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
Click to expand...
Click to collapse
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...

Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
5.1 said:
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Click to expand...
Click to collapse

laofan said:
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
Click to expand...
Click to collapse
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...

I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
5.1 said:
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
Click to expand...
Click to collapse

laofan said:
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
Click to expand...
Click to collapse
You might have to RMA. I believe "no command" means the emmc has died.

dieselbuddeh said:
You might have to RMA. I believe "no command" means the emmc has died.
Click to expand...
Click to collapse
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
If you bought the phone direct from Google, you will likely get a one time exception.

v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.

5.1 said:
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
Click to expand...
Click to collapse
I almost tried all the major OTA, none of them could pass 46%... oh well......
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
tommyg562000 said:
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
Click to expand...
Click to collapse
It is not from google. And the warranty ended in January... I am fxxked.....

Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.

v12xke said:
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
Click to expand...
Click to collapse
posted it on craigslist now.
( I noticed that you are in the Woodlands area. I missed the time when I am in Houston. One of the best memories)

just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.

laofan said:
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
Click to expand...
Click to collapse
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...

5.1 said:
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
Click to expand...
Click to collapse
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)

laofan said:
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
Click to expand...
Click to collapse
Hello,
I see nothing different than hmm an OTA here. I thought that was a "special" OTA, but no.
Not sure why it's called rescue OTA, lol.
Thanks for the links, but i know exactly what an OTA and a factory image are. :good:
Thanks...

Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!

fredmoro said:
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
Click to expand...
Click to collapse
Same. The data decryption being unsuccessful happened to me as well on stock oreo 8.1.0. not rooted
Anyone know how to fix it and doesn't happen again?
Thanks

Is my Mi 9t bricked?

Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.

yurtal said:
Hello. I recently tried to flash the latest fastboot global rom which included locking the bootloader. I used the latest miflash unlock program and everything went well and displayed the green "successful' when it was done. But when I rebooted to the system it loaded directly into stock recovery and boot loops by itself, restart>recovery>restart>recovery etc. It also displays at the bottom of the recovery screen "This MIUI version can't be installed this devise' but I'm sure I flashed the right one.
Now I don't know what to do. If I try to reunlock the bootloader it doesn't go through because I haven't linked my account to the phone (and cant do that because it wont boot up properly). I've tried wiping data in recovery but that doesn't change anything. I can however boot the phone into fastboot and also ADB but I don't know what to do from there. If I try to erase the data via fastboot I get an error saying it can't do that on a locked devise.
So I'm really stuck here and if someone knows what I can do (if anything) I would really appreciate your help.
Click to expand...
Click to collapse
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly

zgfg said:
Unfortunately, classical case to seek a paid EDL support
Btw, I don't know did the ROM really forced relocking BL or you didn't pay attention - there was an option in MiFlash to avoid relocking BL (unfortunately, by default it is enabled and many users then come to the same situation and have to seek for and pay EDL support, if anything goes wrong while flashing the ROM - one must disable relocking BL to stay on the safe side)
You should look around XDA if you can find somebody (it's not allowed to advertise, hence most posts would be deleted) or ask on Telegram or similarly
Click to expand...
Click to collapse
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?

yurtal said:
Hi thank you for your reply. I wanted to lock the bootloader as I was going to sell the phone and wanted it all back to stock standard. What does EDL do exactly?
Click to expand...
Click to collapse
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything

zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Oh ok. Yes I'll read up on it. Thanks for your help.

zgfg said:
Please google about
It's very deep flashing. Something like how they flash the phones when they are assembled - they have to flash Bootloader and everything
Click to expand...
Click to collapse
Hey, just to follow up. I managed to get it back up and running from someone with EDL support.