Hello guys, last week I bought a redmi 7. But this i check this cell phone and the MIUI LOCK was unlocked.
I had a brilliant idea to block using adb. And i destroy the system.
I tryed MI PC Suite, I Tryed mi flash is faild (remoite: Update sparse crc list failed), I Tryed in adb fastboot oem unlock, i tryed mi flash unlock, I tryed change the firehose but i won't have a success. I tryed use old versions of miflahs and i was unsuccessful too.
*I tryed install TWRP but have a error:
fastboot flash recovery recovery.img
target reported max download size of 534773760 bytes
erasing 'recovery' ...
FAILED (remote: device is locked. Cannot erase)
finished. total time: 0.006s
Did i throw my money in the trash?
Guys, this cell phone have a solution ?
Related
Dear All,
i'm new in the Android world and purchased a Xiaomi MI 6 for the very begining.
Installed TWRP and tried to:
HTML:
sudo fastboot flash recovery SR5-SuperSU-v2.82-SR5-20171001224502.zip
target reported max download size of 536870912 bytes
sending 'recovery' (6721 KB)...
OKAY [ 0.221s]
writing 'recovery'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.223s
[email protected]:~/Android Xiaomi MI 6$ sudo fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.000s
[email protected]:~/Android Xiaomi MI 6$ sudo fastboot devices
8e6471bb fastboot
[email protected]:~/Android Xiaomi MI 6$ sudo fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.000s
[email protected]:~/Android Xiaomi MI 6$
Tried some how to's but didn't succeed well.
Is there a straightforward way to open root access to the device, so i can plug it on my linux box and have total access to the files (all)?
Thx in advance.
pw44 said:
Dear All,
i'm new in the Android world and purchased a Xiaomi MI 6 for the very begining.
Installed TWRP and tried to:
HTML:
sudo fastboot flash recovery SR5-SuperSU-v2.82-SR5-20171001224502.zip target reported max download size of 536870912 bytessending 'recovery' (6721 KB)...OKAY [ 0.221s]writing 'recovery'...FAILED (remote: Flashing is not allowed in Lock State)finished. total time: [email protected]:~/Android Xiaomi MI 6$ sudo fastboot oem unlock...FAILED (remote: Token Verify Failed, Reboot the device)finished. total time: [email protected]:~/Android Xiaomi MI 6$ sudo fastboot devices8e6471bb [email protected]:~/Android Xiaomi MI 6$ sudo fastboot oem unlock...FAILED (remote: Token Verify Failed, Reboot the device)finished. total time: [email protected]:~/Android Xiaomi MI 6$
Tried some how to's but didn't succeed well.
Is there a straightforward way to open root access to the device, so i can plug it on my linux box and have total access to the files (all)?
Thx in advance.
Click to expand...
Click to collapse
I'm curious too abot how to root paintless.
txh
Sent from my MI 6 using Tapatalk
pw44 said:
Dear All,
i'm new in the Android world and purchased a Xiaomi MI 6 for the very begining.
Installed TWRP and tried to:
HTML:
sudo fastboot flash recovery SR5-SuperSU-v2.82-SR5-20171001224502.zip
target reported max download size of 536870912 bytes
sending 'recovery' (6721 KB)...
OKAY [ 0.221s]
writing 'recovery'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.223s
[email protected]:~/Android Xiaomi MI 6$ sudo fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.000s
[email protected]:~/Android Xiaomi MI 6$ sudo fastboot devices
8e6471bb fastboot
[email protected]:~/Android Xiaomi MI 6$ sudo fastboot oem unlock
...
FAILED (remote: Token Verify Failed, Reboot the device
)
finished. total time: 0.000s
[email protected]:~/Android Xiaomi MI 6$
Tried some how to's but didn't succeed well.
Is there a straightforward way to open root access to the device, so i can plug it on my linux box and have total access to the files (all)?
Thx in advance.
Click to expand...
Click to collapse
you will have to enable "oem unlock" on developer settings, "usb debugging" too, and click on the "mi unlock status" and click on the button down there to pair your mi account with your device, after that you will go on the official miui page and select the unlock option on the page (on pc it is on the top right hand corner if i remember correctly) and proceed to unlock your phone through mi unlock utility.
~Edit~
And btw i dont think you should tinker with your device cause are likely going to brick it by flashing .zip files through fastboot...
AWESOME1092387456 said:
you will have to enable "oem unlock" on developer settings, "usb debugging" too, and click on the "mi unlock status" and click on the button down there to pair your mi account with your device, after that you will go on the official miui page and select the unlock option on the page (on pc it is on the top right hand corner if i remember correctly) and proceed to unlock your phone through mi unlock utility.
~Edit~
And btw i dont think you should tinker with your device cause are likely going to brick it by flashing .zip files through fastboot...
Click to expand...
Click to collapse
The only goal (for now) i want to achieve is to disable ipv6 from the device, because of dns errors... any way other than having root access?
when i tried to unlock bootloader it says:
target reported max download size of 1610612736 bytes
sending 'unlock' (5 KB)...
OKAY [ 0.032s]
writing 'unlock'...
FAILED (remote: Invalid data)
finished. total time: 0.095s
why always like that , i've tried to get new img but still remote invalid data
Z2 Plus doesn't actually lock the bootloader. With locked bootloader, the phone can still boot with unofficial ROMs, there's merely a warning message before the phone continue to boot - even if you unlock the bootloader, such warning still won't go away.
You may use QPST/QFIL's partition manager (with the firehose flasher program extracted from stock ROM package) to flash TWRP into the recovery partition.
Unlocking bootloader merely provides convenience in fastboot mode. However it's not hard for Z2 to enter EDL (9008) mode, the so-called "deep flash USB cable" works. There're test points on the mainboard as well.
Hi! If you're trying (and failing) to flash the sn.img file received via email, check on my answer Here.
Good luck!
Yea please someone help tried everything but it still shows unlocking failed remote invalid data
So, here I was thinking things couldn't hurt to do some customisation.
This evening, I flashed a custom logo... using fastboot. (fastboot flash logo logo.bin)
That was the last thing I saw on my device, it won't show anything anymore.
Any advice on how to get any connection to my device again?
Right... So as before I found the solution myself.
I used the BROM to reflash the logo with the proper image.
For whoever wants to know. I used the MTK bypass utility to bypass the authentication stuff, and the SP Flash tool to flash.
I did have to use libusb-win32 for the python part, took me some hours to figure that one out. All sources told me UsbDK would work for that.
Kind of relieved I actually managed to unbrick my phone.
Did you get solution?
As mentioned in the post right before you; yes.
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl_a xbl.elf
Sending 'xbl_a' (3449 KB) OKAY [ 0.105s]
Writing 'xbl_a' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone?
I would be very, very grateful for help
You could try this: fastboot --set-active=b
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Try this
https://www.getdroidtips.com/twrp-recovery-redmi-note-8-2021-root/
I guess you have used a wrong recovery file, maybe one for another device
The problem is that the command 'flash recovery' does not work, because it says th partition does not exist....
Norah1838 said:
I am using a Redmi Note 8 (2021)
Click to expand...
Click to collapse
wrong forum ! , see Biloba forum
on some devices, boot+recovery are on the same partition, but not for Biloba
boot partition (+dtbo on some cases) is the kernel
i think you should look for official install of miui rom since it has IMG of most partitions ...
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
I am using a Redmi Note 8 (2021) and wanted to flash lineageOS. So I unlocked the bootloader via my mi account, booted into fastboot mode (usb-debugging was of course enabled) and tried to flash twrp to recovery using the cmd-window via platform-tools.
This didn't work because when I typed:
./fastboot flash recovery twrp.img
I got the reply:
Sending 'recovery' (65536 KB) OKAY [ 1.743s]
Writing 'recovery' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
I therefore started googling and found a threat on xda where someone had solved the problem by replacing 'recovery' with 'boot':
./fastboot flash boot twrp.img
What I got was:
Sending 'boot_a' (65536 KB) OKAY [ 1.818s]
Writing 'boot_a' OKAY [ 0.827s]
Finished. Total time: 2.681s
After that my phone was bricked. I cannot enter recovery mode anymore and even fastboot mode appears a bit different (I don't see the bunny anymore, all I see is the word 'fastboot' in orange letters on a black screen). When I enter fastboot mode, the device is detected by my computer - the only sign that still gives me an inch of hope. When I'm not in fastboot mode my phone keeps vibrating and then turning of, then suddenly it vibrates again and turns on, the logo 'redmi' appears and then it suddenly turns off again - and it just keeps repeating this procedure.
I downloaded the mi flash tool and tried to flash the Xiaomi ROM, but that didn't work either - after about five minutes of waiting I get an error. I tried different versions of MIUI but keep getting errors. When I try to flash the Xiaomi ROM via cmd-window, as suggested here ( https://www.droidwin.com/unbrick-redmi-note-8-fastboot-commands/ ) I get this:
fastboot flash xbl xbl.elf
Sending 'xbl' (3449 KB) OKAY [ 0.105s]
Writing 'xbl' FAILED (remote: 'This partition doesn't exist')
fastboot: error: Command failed
Is there anything left for me to do or should I give up and save money for a new phone? I am also wondering why the command-window keeps talking about 'boot_a'. Is there a 'boot-b' also? And should I write something onto it? When I try to boot the twrp.img by typing:
fastboot boot twrp.img
I get:
Sending 'boot.img' (65536 KB) OKAY [ 1.592s]
Booting FAILED (Status read failed (Too many links))
fastboot: error: Command failed
I would be very, very grateful for help
Norah1838 said:
Hello,
I'm a beginner in the field of flasing custom roms but I would really like to abandon using google on my phone and find your work here really awesome. So yeah, I hope my question doesn't sound stupid but I'm seriously stuck and hope I didn't completely break my phone.
Click to expand...
Click to collapse
Use this tool:
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/
First off: don't go punching in commands you don't understand.
You literally flashed an incompatible image to your boot_a.
You could try and set the active partition to b using: fastboot --set-active=b.
Other option, if you have the firmware image for your boot partition, flash that image to boot_a.
you only need to flash the original boot.img from firmware lol it's so easy