[Redmi Note 8] Unlock the bootloader while bricked - General Questions and Answers

I was using my phone normally yesterday (Saturday) 12/06, I left it charging and when I looked at it again, it was restarting non-stop. It's a Redmi Note 8, I held the power button, but it wouldn't turn on, it just went back to the bootloader screen, I didn't try to format it as I'm trying to recover my files. So I thought about unlocking the bootloader to have access to my files, I used Mi Unlock Tool, but it doesn't work because it asks me to add my account to the device (It was already added before this happened). I still have access to my account phone number, and email. But I couldn't unlock by this fastboot method, so I tried using the "fastboot oem unlock" command, which didn't work either, it showed these two messages.
'Fastboot boot command is not available in locked device'
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
The versions of MiFlash Unlock I used were
"miflash_unlock-en-5.5.224.55" and "miflash_unlock-en-5.5.224.24".
The device is not recognized by the "Mi PC Suite".
The device still appears in fastboot devices, but not in adb devices

bump

When unlocking phone's bootloader automatically all user-data get lost.

Hint: Add Redmi Note 8 to this thread's title thus mainly owners of such phone get addressed.

jwoegerbauer said:
When unlocking phone's bootloader automatically all user-data get lost.
Click to expand...
Click to collapse
I was trying this and this [GUIDE]

jwoegerbauer said:
Hint: Add Redmi Note 8 to this thread's title thus mainly owners of such phone get addressed.
Click to expand...
Click to collapse
Ok!

When using "MiFlash Pro", I managed to reach 100% (?), but the device resets, gets stuck in the MIUI screen for 2 minutes and then resets again to the bootloader screen. I was flashing the same ROM i was using, the "V12.0.4.0.QCOMIXM".
Video flashing the ROM

Related

Fastboot oem unlock freezes phone

It's my first post on this forum, so I'm saying hello.
I've recently bought Nexus S which after turning on is stuck on Google logo, but I could enter fastboot and recovery. But it has locked bootloader. I tried unlocking it by "fastboot oem unlock" but it asks me if I'm sure and then i click yes it freezes (phone not fastboot). I tried it using different drivers, machines, operating systems, cables, but still nothing. Unbrick tool by AdamOutler says that "device not found". When trying to flash stock image by Odin on the phone there is message if I'm sure that I want to unlock bootloader but with nothing to choose, and after while it shows by red characters that system image was verified.
I don't know past of this phone. (I have no idea, which version of android was it running)
I'd be extremely helpful for any kind of advice.

Help - Bricked (accidentally locked bootloader with TWRP installed)

It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
try using search next time because its already been talked abput here https://forum.xda-developers.com/oneplus-6/help/relock-bootloader-t3798135
Actually, I DID read that. I didn't just roll off the cabbage truck. If you have time to post snippy replies (I also searched YOUR post history), then maybe you can point out where in that thread the answer to my question is. I could see if there was a thread where this specifically happened, or if it had been talked about over and over, but I couldn't find one. You do know this is a fairly new device, right? TBH, you're just being rude. To count on someone to hit the right search terms for a single thread where the info exists is just asinine.
1) I have not seen anyone with this situation on the OP6 yet
2) The OP5T had an unbrick tool
3) Most phones have a way to restore the OS to factory
If it can't be restored without calling OnePlus, then why not just say so? I'll answer for you, it's because you actually enjoy replying in such a manner. Grow up.
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Flapjack said:
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
Click to expand...
Click to collapse
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
[email protected] said:
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
I did, but I got the "software image does not exist" error. Does it matter whether I downloaded the 5.13 or 5.15 vesion?
mikex8593 said:
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
Click to expand...
Click to collapse
I tried several times. It throws the following error, which when searched for, always seemed to be someone forgetting to enable OEM unlocking in settings:
Code:
FAILED (remote: oem unlock is not allowed)
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Flapjack said:
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Click to expand...
Click to collapse
Hi buddy,
I tired to relock the bootloader and success in that but the phone stuck at fastboot mode, neither restarting to system nor to anything. Kindly help me if i can flash the stock rom in locked bootloader is so how.
THanks in adv
Did you try msm download tool ?
My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help

OnePlus 8 Hard bricked MSM tool will not work.

Hey everybody, Just curious I recently bought a OnePlus 8 on eBay however when it arrived it was stuck in the bootloader. I tried to use the MSM tool which did finish however once it completed I was greeted with an error on the phone saying "your device is corrupted and cannot be trusted and will not boot" which then placed me back into the bootloader brick, After more digging I found that the bootloader must have not been unlocked beforehand meaning I CAN access fastboot but CANNOT enter any commands such as fastboot OEM unlock without errors.
I am kindly asking if their is a solution for this or am I screwed, thanks in advance.
Try to use a fastboot rom from @mauronofrio
https://forum.xda-developers.com/oneplus-8/how-to/rom-stock-fastboot-roms-oneplus-8-t4084629
It always helped me, when i got stuck.
lauchiebeans said:
Hey everybody, Just curious I recently bought a OnePlus 8 on eBay however when it arrived it was stuck in the bootloader. I tried to use the MSM tool which did finish however once it completed I was greeted with an error on the phone saying "your device is corrupted and cannot be trusted and will not boot" which then placed me back into the bootloader brick, After more digging I found that the bootloader must have not been unlocked beforehand meaning I CAN access fastboot but CANNOT enter any commands such as fastboot OEM unlock without errors.
I am kindly asking if their is a solution for this or am I screwed, thanks in advance.
Click to expand...
Click to collapse
Oneplus 8 stuck
Unfortunately that doesn't work because bootloader is locked and cannot flash anything via fastboot with out error.
lauchiebeans said:
Hey everybody, Just curious I recently bought a OnePlus 8 on eBay however when it arrived it was stuck in the bootloader. I tried to use the MSM tool which did finish however once it completed I was greeted with an error on the phone saying "your device is corrupted and cannot be trusted and will not boot" which then placed me back into the bootloader brick, After more digging I found that the bootloader must have not been unlocked beforehand meaning I CAN access fastboot but CANNOT enter any commands such as fastboot OEM unlock without errors.
I am kindly asking if their is a solution for this or am I screwed, thanks in advance.
Click to expand...
Click to collapse
Are you sure you're flashing the right msm for your variant? IN2015, 2011, 2017?
Oneplus 8 stuck
sx10 said:
Are you sure you're flashing the right msm for your variant? IN2015, 2011, 2017?
Click to expand...
Click to collapse
Yeah I am 100% sure, the process does complete at 300 seconds, could it be that my bootloader was locked previously?
Oneplus 8 stuck
sx10 said:
Are you sure you're flashing the right msm for your variant? IN2015, 2011, 2017?
Click to expand...
Click to collapse
Yeah, tried all tools, for reference my device is in2010.
Just stays in your device is corrupted and will not boot.
Same problems on my oneplus 8?
But I have black screen after displaying the logo
And bootloader is locked
Fastboot oem unlock not work
I tried many version of sms tool but none of them fix my problems
Please help me
ONEPLUS 8
oliver802 said:
Same problems on my oneplus 8
But I have black screen after displaying the logo
And bootloader is locked
Fastboot oem unlock not work
I tried many version of sms tool but none of them fix my problems
Please help me
Click to expand...
Click to collapse
Same boat here, Ive contacted oneplus and they will remote my PC I will update you when that happens.

Device state locked.

This post is more like an explanation.
So my phone got bricked today, stuck at logo. I managed to access recovery and format data, but its stuck at formating data for more than 6 hour.
The only choice left is to unlock bootloader and flash firmware. Now here's the bull**** part.
When i try press fastboot oem unlock it says failed, device state locked. Device state can be set to unlock only through one method, by booting>going into settings>developer options>turning on oem unlocking. Doing this set your device in unlocked device state and thus allow it to unlock bootloader through fastboot. But, if your device got bricked and can't get into phone and your oem unlocking was off (average person will not set it to on) then you're ****ed, cuz without it you cannot unlock bootloader, thus you cannot install twrp or flash firmware.
This is so dumb, not even adb can set the device state to unlock. Read the last paragraph - (https://source.android.com/devices/bootloader/locking_unlocking)
There are so many post like these but no answer. so this post is for those guyz.
guess, i'll use feature phone for rest of my life
That an Android device's bootloader is locked by default isn't dumb, it has good reasons.
BTW: Flashing device's Stock ROM doesn't require device's bootloader got unlocked before.
tried flashing stock rom using adb sideload and fastboot. both failed. adb states that it cannot as it is a downgrade. fastboot says that device state is locked.
Yes, im aware that it is present for a good reason, but someone who's phone doesnt boot up has no way to unlock bootloader or do anything.
I'm not sure that I have the same problem but I have Samsung sm-t500 on the download mode says : device state lock and Im searching for FRP software but I think it won't happen because I tried too to connect via ADB and still can't connect.. But mine is still not bricked.. I will be very happy if you can give me some advice

Xiaomi Mi5 linageos 19.1 bricked after fastboot oem lock ?

Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Fytdyh said:
congrats, you succesfully hard bricked your phone. please take it for a walk to the xiaomi service and pay for gettting it fixed. who told you it is a good idea to relock the bootloader with a custom rom installed ?
Click to expand...
Click to collapse
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
jever2k said:
actually, i remember some banking apps complained about the locked bootloader. I thought i can lock/unlock it in fastboot mode, but looks like i was wrong.
I will give the MiFlash Tool a chance, but i have not much hope...
@Fytdyh: do you think, Xiaomi Service can fix it ?
Click to expand...
Click to collapse
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Tawsif999 said:
Make sure if your bootloader is really locked or not using fastboot command
fastboot oem device-info
OR,
fastboot getvar unlocked
If it's not locked, you can simply flash your stock rom using flash tool available for mi. Before downloading a rom from internet, take note of your device info using fastboot command ,
fastboot getvar all
And if bootloader is really locked, you have to flash stock rom from EDL mode. You may have to remove back cover to turn on EDL mode. Your device has snapdragon chipset (Plus point). Watch tutorials about xiaomi edl rom flash - snapdragon. You can go to service centre. If they tell you that you have to replace motherboard, don't be agree. Tell them to flash rom using EDL mode.
Click to expand...
Click to collapse
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
jever2k said:
looks like i am getting closer... located the two EDL points to short during PC connection, installed the Qualcomm serial driver. For a second i see the device appearing as COM6 but then it disappears again and is not availiable anymore.
Any hints ?
Thanks again, Jan
Click to expand...
Click to collapse
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
jever2k said:
Hello everybody,
i'm not new in custom roms, but i have a problem, i can't solve by myself:
I flashed an unlocked Mi5 to linageos 19.1 without problems.
I had the bad idea to relock the bootloader due to security reasons (fastboot oem lock).
Now the device is not booting anymore, i can just see the Mi-Logo flashing very shortly.
I can access fastboot, but can't boot into recovery.
I tried to unlock the device again, but the Mi Unlocker fails and prompts me to go to the developer options in Miui, which is clearly impossible.
Any chance to proceed from fastboot (fastboot oem unlock does not work...) ?
Thanks, Jan
Click to expand...
Click to collapse
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Droidriven said:
Flash stock recovery for your device via fastboot, then you should be able to boot into recovery or flash a stock system.img or your full stock firmware for your device, then unlock the bootloader(fastboot oem unlock) then flash TWRP and LineageOS again.
Click to expand...
Click to collapse
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing something from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Tawsif999 said:
Try this to solve the issue.
If it doesn’t help, read this to boot properly into edl
Click to expand...
Click to collapse
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole procedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
jever2k said:
OK, next level reached. The phone is connected to the com-port and the correct driver is displayed.
The whole prcedure is a bit unstable, i need to connect the phone several times, to get a stable EDL mode.
The Xiaomi Flasher recognizes the phone, but flashing does not succeed. Sometimes it's not able to receive a kind of Hello message, sometimes it displays "object reference not set to an instance of an object".
I also downloaded the QPST flasher, but have no plan, how to use it.
I'll keep on trying!
Thanks to all, who helped me to reach this point!
Click to expand...
Click to collapse
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Tawsif999 said:
But he mentioned, bootloader fails to unlock. Actually it's hard brick(Even though he can boot into fastboot,the bootloader is locked. So nothing to do with fastboot).Without unlocked bootloader, flashing psomething from fastboot will hard brick his device completely (Will not be able to boot into fastboot). Or flashing will be denied
Click to expand...
Click to collapse
Yeah, I jumped the gun and posted before seeing all the replies in the thread describing their whole scenario, should've known better.
They obviously need a hardware approach, i.e. JTAG/RIFF/Octoplus or replace motherboard.
Tawsif999 said:
I found something new by watching this video. Maybe you don't understand hindi(India is our relative country, so I do).
Lemme explain,
This guy's xiaomi k20 pro phone hard bricked with a locked bootloader. He tried a lot to repair it(by deep flash or something idk). But everything failed. At last he came to this step of EDL mode. But xiaomi Edl mode flash requires an "AUTHORIZED MI ACCOUNT" . Xiaomi people pay to get authorized account license that normal users don't have. So the guy contacted with them on a telegram page called "Mod Edit: Name Removed" . They told him that they will repair his phone via teamviewer. All he had to do is pay some $ & connect phone in edl mode. Rest of the things were done by them. And his phone repaired successfully! (Watch the video from 4:00)
So In his video, he is telling to go to that page & contact with "Mod Edit: Name Removed" there. They take 20-25$ (depends on device). If you tell them you're from Mod Edit: Name Removed's video, they will give some discount
Click to expand...
Click to collapse
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
jever2k said:
Thanks for research!
Meanwhile, i stopped using Windows due to all the caveats and switched to reliable Debian Linux on a different machine.
Again it takes 10 attempts to get into EDL Mode.
I used qdl (Qualcomm downloader for Linux) with all the firehose, raw and patch .xmls
Code:
sudo ./qdl --debug --storage ufs --include . prog_ufs_firehose_8996_ddr.elf partition.xml rawprogram0.xml rawprogram1.xml rawprogram2.xml rawprogram3.xml rawprogram4.xml rawprogram5.xml patch0.xml patch1.xml patch2.xml patch3.xml patch4.xml patch5.xml
Output looked like some stuff was written, at the end i receive:
Code:
qdl: failed to write: Connection timed out
However, the phone is now dead as can be without fastboot working any more.
Maybe i'll give it another try, or get a used Mainboard...
Best regards, Jan
Click to expand...
Click to collapse
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Tawsif999 said:
That's expensive. Anyway, it will be better if you don’t waste time on this. Just go for 3rd party help(From that official telegram channel or service centre). That will cost less
Click to expand...
Click to collapse
Thanks Tawsif for the good hints and links.
I don't really depend on the phone, so i will keep trying.
It's not wasted time, it's mainly learning new stuff and improving skills.
I believe, i'm not too far away and if it works, it's the best satisfaction.
If not, i bricked an old Mi 5.
All the best,
Jan

Categories

Resources