Hi guys,
so after I got my xiaomi with a global ROM and wanted to update and that is when I accidentally relocked the bootloader. The version of ROM was invalid apparently and wouldn't let me boot and now I'm stuck in fastboot mode.
My problem is as follows:
-can't enter recovery, stuck at fastboot no matter how many times I try and reboot
-adb not working since I didn't enable it
-bootloader locked (miflash says so and it can't unlock it since I didn't check 'oem unlock enable' and I cannot boot ROM so I can't enable it)
-fastboot flashing says 'not allowed in lock state'
-edl mode not available
I've seen tutorials where people opened their phones to force the phone into edl mode via the testing points but is that the only way`?
Any suggestions on how I could unbrick it?
Much appreciated
yes, it is the only way.
koniv90 said:
Hi guys,
Any suggestions on how I could unbrick it?
Much appreciated
Click to expand...
Click to collapse
you can use this tool to flash the phone on fastboot mode
Xiaomi King Tool - Home.
xiaomikingtool.com
its cost you only 5 credit
Can you flash files by fastboot? if so, flash the global rom images one by one, then reboot
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
I need help please my phone redmi k50 gaming is no recovery and . bootloader is locked
eclipsek20 said:
I know this is a late reply, but I was in a similar situation with my phone and here is how I dealt with it: You need to access EDL mode, it doesn't require disassembling the device like the other user here suggested. Here is a thread you can find several variations of fixes here: https://forum.xda-developers.com/t/xiaomi-12-pro-completely-bricked-dead.4422997/
If anyone needs help with a locked bootloader bootlooped phone and doesn't know what to do I can help for a fee.
Click to expand...
Click to collapse
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
This what I'm facing
Dims_Camper said:
yes, it is the only way.
Click to expand...
Click to collapse
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
kskksks said:
So even with a locked bootloader and disabled developer options, I can still flash stock rom in edl mode, regardless?
Click to expand...
Click to collapse
Nope, only very old devices.
NOSS8 said:
Nope, only very old devices.
Click to expand...
Click to collapse
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
kskksks said:
So that's why I get the error "operation not allowed for write" in QFIL... What do i do then? Is there a way to unlock bootloader in edl mode? I can't access recovery mode because of the bootloop... Only EDL mode
Click to expand...
Click to collapse
Have you tried to flash stock rom?
I mean, if you have Chinese rom before, just flash with latest Chinese rom.
Ghanaba said:
Please I have pocophone f1 which says system has been destroyed I have downloaded the firmware xiaomi_poco_f1_V12.0.2.0.QEJRUXM_20200907.0000.00_Gobal_10_XFT (by xiaomistockrom.com) and Qualcom Driver V1.0 and MiFlash tool 20210226 and ADB drive R13 and MiFlash unlock tool en-3.5.1128.45 and platform tool r33.0.3-windows after installing all this drives the phone doesn't want to flash when I use MIFLASH TOOL to flash it say ERROR FLASH IS NOT ALLOWED IN LOCK STATE MODE. when I use windows powershell it says the same thing it looks like the bootloader is lock and I don't know the xiaomi e-mail, number and password on the phone pls help me
Click to expand...
Click to collapse
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
jholfran3 said:
Try to flash the .img files of the fastboot rom, unzip the rom and find all the .img files and flash them with CMD from fastboot, one by one
Click to expand...
Click to collapse
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
flashing is possible with modified firehose programmer (no auth factory loader) or with authorized xiaomi account. both solutions are paid service and cannot advertised here.
please -as always- read the thread you posted in. I can see useful information shared already. wait for other replies.
letsgofly said:
Hello, My Poco X3 System destroyed itself while I was using it, it showed a glitch screen and turned off. Now I went to flash my mobile through Miflash but it showed the bootloader is locked and now I can't unlock it as the system itself is destroyed and can't do anything. So i wanted to know if i can flash my mobile with cmd as you said above flashing img files one by one or let me know if there is any method to flash my mobile or unlock the bootloader? Please me help bro
Click to expand...
Click to collapse
Hi, try to flash the .img files from the fastboot stock rom whit cdm in fastboot, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
example:
fastboot flash boot boot.img
fastboot flash cust cust.img
etc.
jholfran3 said:
Hi, try to flash the .img files from the fastboot stock rom, one by one, some files will give error but skip that, then reboot the phone as normal, it should work.
Click to expand...
Click to collapse
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
NOSS8 said:
If it were that simple, it would have been known for a long time.
You have already posted about this (post#14).
Click to expand...
Click to collapse
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
jholfran3 said:
I had a Mi 9T and by mistake I installed a recovery that didn't correspond to it, the phone got bricked, and the only way to save it was like this, I searched and read everywhere but I couldn't find a solution, flashing the .img files was my idea, I didn't know if it would work but it did.
:V
Click to expand...
Click to collapse
To install a recovery, the bootloader must be unlocked.
Related
Hi,
someone has been able to unlock the locked bootloader?
I have the phone locked in the boot screen (Mi) and I can only get to the fastboot.
It will not let me load any .img file from ADB. He says that the terminal is blocked.
All this I go to load (without being aware) a Miui version from the official website.
Thanks and regards.
hey, try to use Mi Flash then flash the stable ROM into your phone. You can use updater to flash too. AFAIK, your bootloader will be opened in stable roms.
tuanhung303 said:
hey, try to use Mi Flash then flash the stable ROM into your phone. You can use updater to flash too. AFAIK, your bootloader will be opened in stable roms.
Click to expand...
Click to collapse
When I do that, I get the following code... ERROR NO ESPECIFICADO (0x80004005:FAILED (remote device is locked. Cannot flash images))
really? you can't use miflash?
try to use updater app in your phone to flash back to any stable roms
tuanhung303 said:
really? you can't use miflash?
try to use updater app in your phone to flash back to any stable roms
Click to expand...
Click to collapse
Yes, I can't use miflash!!!!
I've been trying, but I get the same failure. (device is locked. Cannot flash images)
I cannot enter in the phone, stays on the main screen, with the logo Mi.
ah so the reason is you can't boot into the UI. You have to ask for unlock request from MI website. after 10 days, they will approve and give your unlock code...
tuanhung303 said:
ah so the reason is you can't boot into the UI. You have to ask for unlock request from MI website. after 10 days, they will approve and give your unlock code...
Click to expand...
Click to collapse
Yes, I ordered it and am waiting to send me the code.
Even so, I wanted to know if you have been able to unlock it somehow.
I don't understand why Xiaomi does not have a release such as Motorola or others.
Thanks!
garaje said:
Yes, I can't use miflash!!!!
I've been trying, but I get the same failure. (device is locked. Cannot flash images)
I cannot enter in the phone, stays on the main screen, with the logo Mi.
Click to expand...
Click to collapse
I have the same problem... I' waiting for sms...
I think this was my first and last smartphone xiaomi.......
azzochetifrega said:
I have the same problem... I' waiting for sms...
I think this was my first and last smartphone xiaomi.......
Click to expand...
Click to collapse
I agree with you and I think the same thing. But for my, the problem is the service so slow Xiaomi. If they knew that it could happen to them, because they did not think in another way to solve this.
Is there also, somehow skip the Boot Manager or change the bootloader of the Mi4c? has anyone tried it?
Regards
garaje said:
Is there also, somehow skip the Boot Manager or change the bootloader of the Mi4c? has anyone tried it?
Regards
Click to expand...
Click to collapse
Hi guys,
Someone has tried it or has obtained it?
I have the same problem, i've received the sms from xiaomi to unlock bootloader, but when i use the miflash unlock tool the operation stops at 50% and says 'couldn't verify device' , probably because i'm not connected with the mi account into the phone....oh and my phone, obviously, is in bootloop and i can go to fastboot mode and nothing else
Someone have any ideas to help me?
I just happened to me today, I wanted to prove Version: 2.6.25 (MIUI7) on Xiaomi's website for mi4c and entered the TWRP recovery and I wiped the system, and i wanted to install Version: 6.2.25 (MIUI7), was installed but stuck to miui.com when i restart . What to do ??????
i still stuck at 50 %
garaje said:
Yes, I can't use miflash!!!!
I've been trying, but I get the same failure. (device is locked. Cannot flash images)
I cannot enter in the phone, stays on the main screen, with the logo Mi.
Click to expand...
Click to collapse
1. Enter to fastboot mode (with rabbit).
2. On the drive "C" must be a folder ADB with the necessary files.
3. Need to download the firmware for fastboot (e.g. 7.1.6.0) and copy it into any folder on the drive, folder name without spaces.
4. Enter to ADB command promt.
5. Commands:
5.1 fastboot devices
5.2 fastboot oem edl
6. Use MiFlash to flash you firmware.
7. Reboot )
What if i root and install twrp and then custom rom without unlocking bootloader?
Sent from my A0001 using Tapatalk
Go there, it works !
Max B. said:
I have the same problem, i've received the sms from xiaomi to unlock bootloader, but when i use the miflash unlock tool the operation stops at 50% and says 'couldn't verify device' , probably because i'm not connected with the mi account into the phone....oh and my phone, obviously, is in bootloop and i can go to fastboot mode and nothing else
Someone have any ideas to help me?
Click to expand...
Click to collapse
Check it out
lukyy81 said:
I just happened to me today, I wanted to prove Version: 2.6.25 (MIUI7) on Xiaomi's website for mi4c and entered the TWRP recovery and I wiped the system, and i wanted to install Version: 6.2.25 (MIUI7), was installed but stuck to miui.com when i restart . What to do ??????
Click to expand...
Click to collapse
Check it out
https://youtu.be/ZkBLrn0Dzt4
Enviado desde mi Mi-4c mediante Tapatalk
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
Give the all required information like Brand, model number in your post first.
Huawei honor 5x kiwi L24, I can't really acces the phone so finding some information is impossible. My main issue is when I boot it's failing to verify the Boot.img , recovery.img and system.img . I don't exactly know what all information I can give you
Nixonkai417 said:
So i did a stupid thing and flashed the wrong image when i was installing a new rom, I managed to lock myself out of ADB, TWRP and download mode. I'm in a bit of a pickle right now I've been trying everything I can to fix it, but I managed to do nothing. Is there anyone that can walk me through the steeps to get unbricked.
I've tried recovery through hisuite, but it says my device is not supported. My phone showed up via CMD command (fastboot devices) but not (adb devices). I have no idea what to do?
PLEASE HELP ME!!!
Click to expand...
Click to collapse
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
-Hope- said:
First open the tool
Select the update.app file
Then press Ctrl and select the imgs you want
And then right click and click extract selected
Like in here
https://up.harajgulf.com/imagef-149893652739431-png.html
Click to expand...
Click to collapse
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Nixonkai417 said:
I have already done that, I've tried flashing it via SP flash tool but nothing, it won't show up. I've downloaded correct drivers and done what I could but my phone shows up as Lemobile android adb interface. It sometimes shows as a disk drive as well.
When I run CMD command (fastboot flash oem info) it shows everything but the recovery.img system.img and boot.img need verification how can I verify them without the debugging bridge active on the phone.
Click to expand...
Click to collapse
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
-Hope- said:
What do you mean sir
Imgs are already verified cause they are official
And you don't need USB debug in fastboot mode
Your device is not has mtk processor so it won't work
Click to expand...
Click to collapse
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Nixonkai417 said:
I rooted my phone and was running xenon HD on my Huawei honor 5x, in the midst of switching ROMs I accidently targeted a TWRP recovery.img with the ROM and Gapps.
So what my phone dose now is when it powers on it an all green screen with a red box and a blue box. After a second it come up with " recovery image verify failed, please update to verified images." I can enter fastboot&rescue mode and a Huawei erecovery, but when i do try to download the recovery via WIFI it says package failure.
Click to expand...
Click to collapse
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
-Hope- said:
What happens when you try flashing through fastboot
Assuming that your bootloader is unlocked have you tried reflashing twrp?
Click to expand...
Click to collapse
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Nixonkai417 said:
I had unlocked my bootloader but some research I was doing says, when you accidently flash wrong images it can relock the bootloader. I lost the original bootloader code and i don't exactly have the box anymore, so getting a new code will be difficult.
Click to expand...
Click to collapse
As long as the bootloader says 'phone is unlocked' then its ok
-Hope- said:
As long as the bootloader says 'phone is unlocked' then its ok
Click to expand...
Click to collapse
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Nixonkai417 said:
I'm my case the bootloader has relocked, so in green it say phone status: locked.
Click to expand...
Click to collapse
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
-Hope- said:
I've reread your previous post and you didn't mentioned what happens in the cmd window when trying to flash the files?
Click to expand...
Click to collapse
(REMOTE: command not allowed)
I have already sent an email to Huawei support, just waiting on a response to see if they can give me another unlock code. If I'm unable to unlock the boot loader again with the codes, what's my options for unlocling the boot loader without Huawei's help.
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs
hackermssharma said:
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
Thank you for taking time to reply to my query. I did what you suggested and got into EDL mode. Xiaomi Mi Flash picked up the device as COM10 but when I tried to flash it shows "sahara read end error with status:40" and nothing happens.
Any further idea?
TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
I suggest you use the older variant of the MiFlash tool.
How did you flash Peter's? Did you use "fastboot flash recovery recovery.img"? That's the only right command.
Also are you sure you have the Indian variant of the phone? Another way to bypass anti roll back would be to clear all partitions, and then flash the required ROM.
Sorry if I'm not able to help you, I'll try having a look later on.
Thank you for your support. I had to go to the service center as no solution could be found.
Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.
dnyaneshmoh said:
Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.
Click to expand...
Click to collapse
Thank you for your feedback but the phone bootloader remained unlocked as when the phone starts there is "unlocked" written in bottom.
I got the phone back from Service Center. It's working fine but strangely still the bootloader is shown as unlocked in the start animation.
I have unlocked oneplus 8 (china global) boot loader. But i cannot flash my phone because of critical partition. I wan to know how to unlock critical partition. When i am trying to flash by fastboot ...Shows (Flashing is not allowed for Critical Partitions)
I have tried code: fastboot flashing unlock_critical
. But its not working... My phone is bricked ..please help me.
What are you trying to flash and how are you doing it? To get that warning.
Sent from my IN2010 using Tapatalk
Bro i'm trying to flash oneplus 8 stock rom by fastboot. My bootloader is unlocked. But it isn't working for system files....I have to unlock critical partiton.
sadatkabir55 said:
Bro i'm trying to flash oneplus 8 stock rom by fastboot. My bootloader is unlocked. But it isn't working for system files....I have to unlock critical partiton.
Click to expand...
Click to collapse
Please post screenshot of error. I had this too and it was because of drivers. I tried to manually force bootloader to fastboot. This caused issues with the critical partition.
To fix, when the phone rebooted I let it sit while windows installed drivers. After that no problem. This is assuming you are using the fastboot ROMS posted.
Bro i have also installed twrp....can it help me to open my set..its not booting
sadatkabir55 said:
Bro i'm trying to flash oneplus 8 stock rom by fastboot. My bootloader is unlocked. But it isn't working for system files....I have to unlock critical partiton.
Click to expand...
Click to collapse
When I did that, I just ran the (flash-all.bat) file and it installed all fine. It sounds to me like you are trying to flash one file at a time!
AndyBury said:
When I did that, I just ran the (flash-all.bat) file and it installed all fine. It sounds to me like you are trying to flash one file at a time!
Click to expand...
Click to collapse
Hay I have the same problem and no one can help me.....I have the right drivers installed iv tryed 10 different msm tools and two different laptops and can't fastboot a Rom or By all the tools available on line and nothing!... Thanks in advance
I have similar error message of not allowed for critical partition. My situation is caused by outdated fastboot software. I downloaded the newest one from Google website and problem solved. Not sure if this fits your problem.
Same problem here, everything up to date, but stock rom jus don't go, can flash any custom but not the stock, wtf
Solution: I hardbricked my device because of my dumbness. This device is not veux... It s viva. Be cautious my friends...
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies
turbotales said:
I unlocked my bootloader and wanted to install TWRP to flash a custom ROM to the device. Unfortunately, right after I tried, device got stuck in a bootloop (Mi logo showing, then closing.)
I tried flashing multiple TWRP files after that. Since there is no official file for this device, I tried the ones given in the forum and a youtube video.
Holding power+up does not open anything. Holding power+down I can go to fastboot. ADB does not see the device (adb devices does not show anything). But fastboot devices does show. (MiFlash tool also sees the device but can't flash the ROM.)
MiFlash first gives the classic crc error, I delete the lines, it passes this error and finally gives another error ("Command failed"). I tried flashing 2 versions (my local version and eu version) of the stock rom in both windows and ubuntu based linux. What am I doing wrong?
Am I doomed? What can be done? Why isn't ADB working? Thank you for replies
Click to expand...
Click to collapse
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
NOSS8 said:
ABD works only if you have enabled USB debugging.
Eventually check here that everything is correct:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
Or try to install a Xiaomi Eu rom (Fastboot).
Extract the zip then run the scrip in the corresponding extracted folder to your O.S.
Fastboot_first install.
xiaomi.eu_multi_VEUX_V13.0.3.0.SKCCNXM_v13-12-fastboot.zip
https://sourceforge.net/projects/xi...files/xiaomi.eu/MIUI-STABLE-RELEASES/MIUIv13/
Click to expand...
Click to collapse
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?
turbotales said:
Hello, I do have my bootloader unlocked and USB debugger is also on.
I tried flashing twrp again, says it worked but does not boot into it. Goes back to boot loop
Then I tried flashing with MiFlash again. Same error
fastboot error remote: command failed
When I google it everyone says my bootloader should be locked. But it is not.
Can I use the hard brick solution with bypass for this problem?
Click to expand...
Click to collapse
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).
NOSS8 said:
All these procedures, Miflash, Twrp, Xiaomi Eu rom are done in Fastboot mode not ADB and obviously the bootloader must be unlocked.
Try the Xiaomi Eu rom.(TWRP included).
Click to expand...
Click to collapse
Tried doing this.. now it s hard bricked.
turbotales said:
Tried doing this.. now it s hard bricked.
Click to expand...
Click to collapse
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?
NOSS8 said:
You have flashed a Xiaomi Eu rom and it does not work?
And with Miflash?
Click to expand...
Click to collapse
I tried flashing with Miflash didnt work,
Tried flashing with linux and said it is done, but now device does not open in any way. What should I do?
These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.
NOSS8 said:
These are the screenshots of the Xiaomi Eu rom?
What is the version of your phone? (11 pro/Poco).
What rom were you on?
post the Miflash log.
Click to expand...
Click to collapse
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?
turbotales said:
Downloaded the rom from the link you sent me earlier. My device is veux and had MIUI13 before getting bricked.
Again the device got bricked from the last think i did. Do you know what wen wrong?
Click to expand...
Click to collapse
If you tried with Miflash post the log otherwise try and post the log.
Solved, I'm dumber than I thought. This phone is not veux. It's viva. If I were to re-check it I d not be in this position... Let this be a lesson to me. Going to have to take it to the service now.