Hi.
I have searched for a solution but I couldn't find anything.
I was trying to install GCam and download the file here and when I selected Magisk Module in Magisk app my phone rebooted and didn't boot it was stuck in the screen after Android One logo.
I manually rebooted my phone and it showed me this message.
I can't take a pic of my phone because I don't have a camera or another phone right now but the error is the same in the I uploaded.
Has anyone had the same problem?
I can't flash the stock rom using the MiFlash 'cause it returns an erro: error: "Flash bluetooth_a error"
I solved the problem by unlocking the bootloader again.
gsilva92 said:
I solved the problem by unlocking the bootloader again.
Click to expand...
Click to collapse
I am sorry of course. But how did you unlock the bootlaoder? I just have a mistake
"remote: 'Flashing Unlock is not allowed"
Damir51 said:
I am sorry of course. But how did you unlock the bootlaoder? I just have a mistake
"remote: 'Flashing Unlock is not allowed"
Click to expand...
Click to collapse
Sorry for taking too long to answer.
You can unlock your bootloader by following this guide.
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
Related
I had unlocked bootoader for more than 1 year and didn't have any problem with it. But now for some reason I can't flash anything.
When I try to flash using TWRP i get ERROR 1. From recovery log:
Code:
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
and when i try adb (not only flash but other commands like fastboot oem device-info aswell)
Code:
FAILED <Remote: command not allowed>
Any idea how to fix this?
woooz said:
I had unlocked bootoader for more than 1 year and didn't have any problem with it. But now for some reason I can't flash anything.
When I try to flash using TWRP i get ERROR 1. From recovery log:
Code:
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
and when i try adb (not only flash but other commands like fastboot oem device-info aswell)
Code:
FAILED <Remote: command not allowed>
Any idea how to fix this?
Click to expand...
Click to collapse
Try to unlock again!
Bootloader say locked in green or unlocked in red?
.
persona78 said:
Try to unlock again!
Bootloader say locked in green or unlocked in red?
.
Click to expand...
Click to collapse
Unlocked red.
woooz said:
Unlocked red.
Click to expand...
Click to collapse
try to unlock again, and check what it say will you try to unlock.
.
Note: The only file system that works with fastboot is the file system that you extract from update.app, only!
But doesn´t work if you flash with twrp, for twrp is the file system that you pull from the phone.
.
persona78 said:
try to unlock again, and check what it say will you try to unlock.
Click to expand...
Click to collapse
FAILED (remote: already fastboot unlocked)
persona78 said:
Note: The only file system that works with fastboot is the file system that you extract from update.app, only!
But doesn´t work if you flash with twrp, for twrp is the file system that you pull from the phone.
Click to expand...
Click to collapse
I know. Tried to flash stock boot img with fastboot and zip with magisk in twrp.
EDIT: I was able to flash boot.img after this, I guess it worked. Thanks!
I have the same problem again... But now unlocking bootloader again doesn't help.
Also reflashed twrp.
Anyone?
woooz said:
Anyone?
Click to expand...
Click to collapse
If you only want to flash boot.img you can do that in TWRP.
keikari said:
If you only want to flash boot.img you can do that in TWRP.
Click to expand...
Click to collapse
Not only and I can't.
When I try flash anything in twrp i get this error:
Code:
Updater process ended with ERROR: 1
I:Legacy property environment disabled.
woooz said:
Not only and I can't.
When I try flash anything in twrp i get this error:
Click to expand...
Click to collapse
You still didn't fixed since then?
D1stRU3T0R said:
You still didn't fixed since then?
Click to expand...
Click to collapse
When I created this topic all I had to do to fix this problem was unlocking bootloader again.
But few days ago this problem occured again and unlocking bootloader doesn't help.
It's a bug. REINSTALL default firmware it 3 buttons, let it turn on. Unlock boot again and flash twrp. If that does not work either your phone is damaged or you did something wrong in the middle.
I was trying to install stock rom after installing RR rom. MiFlash said "flashing is not allowed for critical partitions" and when i did "fastboot flashing unlock_critical" from cmd i got "remote: Flashing Unlock is not allowed". I then used the allinone tool from xda and pressed "lock loader" to unlock it again and ended up bricking the device as it now shows "your device is corrupt. it can't e trusted and will not boot" I can't enter recovery either only fastoot and nothing works. PLEASE HELP FAST
have you tried flaashing via edl mode ?
medkim said:
have you tried flaashing via edl mode ?
Click to expand...
Click to collapse
how to do that
Hammad1029 said:
how to do that
Click to expand...
Click to collapse
reboot into edl mode and flash stock rom by mifilash tool
medkim said:
reboot into edl mode and flash stock rom by mifilash tool
Click to expand...
Click to collapse
how do I reboot into edl mode without dissembling the phone
Hammad1029 said:
how do I reboot into edl mode without dissembling the phone
Click to expand...
Click to collapse
reboot into bootloader then issue this command via adb
fastboot oem edl
medkim said:
reboot into bootloader then issue this command via adb
fastboot oem edl
Click to expand...
Click to collapse
it gives "FAILED (remote: 'Device is already locked!')"
@__harmeet reply here please
Hammad1029 said:
it gives "FAILED (remote: 'Device is already locked!')"
Click to expand...
Click to collapse
friend
first of all, you shoud unlock the bootloader
try with this guide
medkim said:
friend
first of all, you shoud unlock the bootloader
try with this guide
Click to expand...
Click to collapse
@Hammad1029 He Is Right, Firstly Unlock The Bootloader, Then Unlock Its Critical Partition And Boot Up Into EDL Mode By Typing "fastboot oem edl#
medkim said:
friend
first of all, you shoud unlock the bootloader
try with this guide
Click to expand...
Click to collapse
have tried already it says "FAILED (remote: Flashing Unlock is not allowed"
bump...
Dude, how many threads do you need to create, it won't make it any more likely that anyone will help you
Your problem is caused by that you only unlocked the bootloader and not critical partitions
Which stock rom were you on before flashing a custom one?
Nebrassy said:
Dude, how many threads do you need to create, it won't make it any more likely that anyone will help you
Your problem is caused by that you only unlocked the bootloader and not critical partitions
Which stock rom were you on before flashing a custom one?
Click to expand...
Click to collapse
I created the 2nd thread in desperation of restoring my only phone so sorry. How do I unlock the ootloader it shows the error I mentioned above
Hammad1029 said:
I created the 2nd thread in desperation of restoring my only phone so sorry. How do I unlock the ootloader it shows the error I mentioned above
Click to expand...
Click to collapse
I asked you what stock rom you were on
Nebrassy said:
I asked you what stock rom you were on
Click to expand...
Click to collapse
10.0.2
Hammad1029 said:
10.0.2
Click to expand...
Click to collapse
Are you sure?, if so, manually flash boot, system and vendor using fastboot to your current slot
Fastboot flash boot_a boot.img
Or boot_b if active slot is B etc...
Then go to developer options and enable oem unlocking, if you can't enable that option, lock the bootloader, enable the option then unlock bootloader and critical flashing
Nebrassy said:
Are you sure?, if so, manually flash boot, system and vendor using fastboot to your current slot
Fastboot flash boot_a boot.img
Or boot_b if active slot is B etc...
Then go to developer options and enable oem unlocking, if you can't enable that option, lock the bootloader, enable the option then unlock bootloader and critical flashing
Click to expand...
Click to collapse
can I claim warranty on this issue
Hammad1029 said:
can I claim warranty on this issue
Click to expand...
Click to collapse
Hi , sorry for my bad English , if you can open you phone and enter to EDL MODE and flash the stock rom of your device may be solve your problem ,
(I get the same problem trying to install a custom rom)
If you can't acces to EDL via ABD i think that you only can enter to EDL disasembly your phone .. Suertee xd
Yo también me desesperé
same problem
i got the same problem, won't start normally, hangs in boot screen so can't enter the phone to put it in usb debugging, only responce is through fastboot mode. Every attempt is failing due to locked state and unlocking is not allowed.
I was trying to install stock rom after installing RR rom. MiFlash said "flashing is not allowed for critical partitions" and when i did "fastboot flashing unlock_critical" from cmd i got "remote: Flashing Unlock is not allowed". I then used the allinone tool from xda and pressed "lock loader" to unlock it again and ended up bricking the device as it now shows "your device is corrupt. it can't e trusted and will not boot" I can't enter recovery either only fastoot and nothing works. PLEASE HELP FAST
Hammad1029 said:
I was trying to install stock rom after installing RR rom. MiFlash said "flashing is not allowed for critical partitions" and when i did "fastboot flashing unlock_critical" from cmd i got "remote: Flashing Unlock is not allowed". I then used the allinone tool from xda and pressed "lock loader" to unlock it again and ended up bricking the device as it now shows "your device is corrupt. it can't e trusted and will not boot" I can't enter recovery either only fastoot and nothing works. PLEASE HELP FAST
Click to expand...
Click to collapse
Try Using EDL Mode And Then Flash Stock Firmware
__harmeet said:
Try Using EDL Mode And Then Flash Stock Firmware
Click to expand...
Click to collapse
how do i reboot into edl without disassembling the phony
Hammad1029 said:
how do i reboot into edl without disassembling the phony
Click to expand...
Click to collapse
Type In Fastboot "fastboot oem edl"
Duplicate thread closed
I can't relock my bootloader. Haven't rooted or anything. I unlocked it, couldnt flash the kernel for root so gave up on it and wanted to relock my bootloader. Getting these errors:
c:\adb>fastboot flashing lock_critical
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
Any ideas?
wschamps42 said:
I can't relock my bootloader. Haven't rooted or anything. I unlocked it, couldnt flash the kernel for root so gave up on it and wanted to relock my bootloader. Getting these errors:
c:\adb>fastboot flashing lock_critical
FAILED (Write to device failed (No such file or directory))
fastboot: error: Command failed
Any ideas?
Click to expand...
Click to collapse
Are you sure the kernel didn't flash at all?
I'd recommend flashing a factory image and then trying to lock it just in case something went wrong.
If it still doesn't work is your device showing on CMD using "fastboot devices"?
I'm getting the error device already locked even though my bootloader clearly states that the bootloader is in unlocked. I just flashed the factory image for the phone and still same error. Any ideas?
Rox598 said:
Are you sure the kernel didn't flash at all?
I'd recommend flashing a factory image and then trying to lock it just in case something went wrong.
If it still doesn't work is your device showing on CMD using "fastboot devices"?
Click to expand...
Click to collapse
hello i was able to get it to show up in fastboot devices but i am unable to relock...when i try to get it to relock it goes and says waiting for device even though its in fast boot mode.
Hey Everyone recently my device got stuck at android one logo and so after analyzing it I understood that it was in a hard brick condition. so I tried the Xiaomi Flash Tool to flash the original firmware but every time it had some kind issues such as
1. cannot Flash Bluetooth_a error
2. FAILED (remote: Error flashing partition : Write Protected)
Can anyone suggest me how can I remove this Write Protection.
earlier build - HavacOS ,bootloader unlocked.
PS- Also tried the oem edl mode but it showed an error programmer file not found using the MiFlashTool (Beta) and with the latest build
3. error cannot read from com3 (read hello packet)
Any suggestions would be appreciated.
How did you brick the phone?
Anyway, can you boot into fastboot?
If yes, try booting into TWRP (fastboot boot twrp.img) and use the fix boot loop command.
Exxdeea said:
How did you brick the phone?
Anyway, can you boot into fastboot?
If yes, try booting into TWRP (fastboot boot twrp.img) and use the fix boot loop command.
Click to expand...
Click to collapse
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
This looks like the solution:
https://forum.xda-developers.com/mi-a2/how-to/fix-twrp-freeze-splash-logo-t4065173
Exxdeea said:
This looks like the solution:
https://forum.xda-developers.com/mi-a2/how-to/fix-twrp-freeze-splash-logo-t4065173
Click to expand...
Click to collapse
Thanks for replying but still no hope.
here is another error.
Allocating group tables: done
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'cache' (56 KB) FAILED (remote: 'Error: Last flash failed : Write Protected')
fastboot: error: Command failed
Write protected. How can I remove This?
Same Problem
Try using 4pda version which is X.X.X.X-5. That worked for me. Also, try switch slot a/b from fastboot
Pandu Ahbar said:
Same Problem
Click to expand...
Click to collapse
What does "fastboot getvar unlocked" say?
If you are sure that you have previously unlocked phone:
1. maybe try to lock and then unlock again with
fastboot flashing unlock
and
fastboot flashing unlock_critical
2. try to flash stock, forget about miflash, use fastboot from latest platform tools
If you have not unlocked phone before, and have not set "OEM unlock" in Settings -> Developer, and rebooting 7+ times does not switch A/B slots into working ROM, then look into TestPoint/EDL guide.
Death_17 said:
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
Click to expand...
Click to collapse
Same problam bro how can i solve i don't know and i also use last time havoc os
have you tried test point method?
Death_17 said:
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
Click to expand...
Click to collapse
Aerobatic said:
What does "fastboot getvar unlocked" say?
If you are sure that you have previously unlocked phone:
1. maybe try to lock and then unlock again with
fastboot flashing unlock
and
fastboot flashing unlock_critical
2. try to flash stock, forget about miflash, use fastboot from latest platform tools
If you have not unlocked phone before, and have not set "OEM unlock" in Settings -> Developer, and rebooting 7+ times does not switch A/B slots into working ROM, then look into TestPoint/EDL guide.
Click to expand...
Click to collapse
Vishal656 said:
Same problam bro how can i solve i don't know and i also use last time havoc os
Click to expand...
Click to collapse
have you tried test point method?
Same problem for me write protected error
How to fix it
Death_17 said:
Yes, I can boot into fastboot! but every time it got stuck at the TWRP splash screen/Logo. tried with different versions too.
Also using ( fastboot flash boot_a twrp.img ) and ( fastboot flash boot_b twrp.img) gives an error of write protected .
And as far as how I bricked- I don't have any idea , it was working fine but then suddenly it stooped responding.
(As things usually happen suddenly. )
Click to expand...
Click to collapse
Same problem any suggestions how to fix this
same problem someone give solution
try flashing "super_empty.img" file then install your current ROM through pixel experience recovery
blacksrj531 said:
try flashing "super_empty.img" file then install your current ROM through pixel experience recovery
Click to expand...
Click to collapse
Bro you don,t understand it's write protected