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
Related
I've got a Moto G4 Play and with LineageOS I can't make any calls. So I wanted to downgrade the firmware to the stock-firmware which I downloaded here: bit.ly/2lvXpgC. There are instructions how to downgrade the firmware here: bit.ly/2kPAuNS.
The first command - "fastboot oem fb_mode_set" - is accepted.
But the second command - "fastboot flash partition gpt.bin" - produces the following:
"target reported max download size of 268435456 bytes
sending 'partition' (32 KB)...
OKAY [ 0.008s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.442s"
Can anyone tell me what I'm doing wrong here?
[EDIT]:
I simply run the other commands and ignored those that failed. Now my Phone boots into the bootloader and if I press start, I get into an endless boot-loop. If I start the TWRP recovery-image with "fastboot boot twrpxyz.img", the device restarts and stops in the bootloader, i.e. the recovery-mode isn't started.
Can anyone help me from here?
[EDIT2]:
I've got the problem: I tried to boot the bootloader without a battery in the phone and just the USB-cable attached. So I suspected this was also the problem when flashing the stock-image and I run through tge commands to install it. I simply ignored that "fastboot flash partition gpt.bin" didn't work (according to someone who had the same problem here in this boadd) and every other command was successful. The phone booted the stock firmware and everything is fine now.
Thanks you so much
Work fine for me, only i found the solution here, seriously, thanks!!
GOD BLESS YOU
I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot.
I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD.
----------------------------------------------
D:\Download\platform-tools-Flash>fastboot flash bootloader bootloader-taimen-tmz12a.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 0.097s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed for Critical Partitions
)
finished. total time: 0.107s
D:\Download\platform-tools-Flash>
------------------------------------------------
I can not use the new phone anymore, please help to check my problem. Thanks.
Have you performed in fastboot Mode, at any time, this command: "fastboot flashing unlock_critical" ? (Without " ")
You can't flash factory image in recovery, it has to be done in bootloader mode, also can you boot in bootloader? Is your bootloader locked or unlocked?
Beast38 said:
I try to re-flash my Pixel 2 XL but failed. The status is it reboot and reboot and......non-stop reboot. I try to flash factory image on Recovery mode. it failed on bootloader. Below is the status on windows CMD. I can not use the new phone anymore, please help to check my problem. Thanks.
Click to expand...
Click to collapse
Apparently you have not unlocked your bootloader (critical) correctly. There are two separate commands needed to fully unlock it. That and you can't flash images from Recovery mode, you flash while in Bootloader mode. Read and follow the directions found on the same page you downloaded the image from HERE.
Thanks all. I re-check all procedure and re-do all process. It finally works fine for now.
I can not sure which step went wrong. All I know is "unlock done" "root failed or not complete".
So, I'm trying to get TWRP installed so I can root my phone, but whenever I go to try and do the fastboot flah recovery recovery.img command, I get this:
C:\Users\darks_000\Downloads\platform-tools-latest-windows\platform-tools>fastbo
ot flash recovery recovery.img.img
target reported max download size of 536870912 bytes
sending 'recovery' (26498 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.781s
I'm not sure what to do?
MedievalFreakShow said:
So, I'm trying to get TWRP installed so I can root my phone, but whenever I go to try and do the fastboot flah recovery recovery.img command, I get this:
C:\Users\darks_000\Downloads\platform-tools-latest-windows\platform-tools>fastbo
ot flash recovery recovery.img.img
target reported max download size of 536870912 bytes
sending 'recovery' (26498 KB)...
OKAY [ 0.766s]
writing 'recovery'...
(bootloader) Invalid partition name recovery
FAILED (remote failure)
finished. total time: 0.781s
I'm not sure what to do?
Click to expand...
Click to collapse
1. Make sure your device is unlocked.
2. Make sure fastboot is up to date.
3. That's not how you install twrp. It doesn't get flashed. You boot it temporarily and then use twrp to install itself into your current ramdisk.
4. You must also install a GSI afterwards or twrp will not work correctly. Twrp is not compatible with the stock OS because of some very hellish security Motorola has in place.
5. If you have a Verizon, Cricket, or At&t branded G7 Play, none of the above is possible. If you bought an unlocked or retail model and simply use one of them as a carrier though, it is possible.
Spaceminer said:
1. Make sure your device is unlocked.
2. Make sure fastboot is up to date.
3. That's not how you install twrp. It doesn't get flashed. You boot it temporarily and then use twrp to install itself into your current ramdisk.
4. You must also install a GSI afterwards or twrp will not work correctly. Twrp is not compatible with the stock OS because of some very hellish security Motorola has in place.
5. If you have a Verizon, Cricket, or At&t branded G7 Play, none of the above is possible. If you bought an unlocked or retail model and simply use one of them as a carrier though, it is possible.
Click to expand...
Click to collapse
Device is unlocked. Bootloader is also unlocked. As for fast boot im not sure how to update it. Unless it updates with the system updates. Ive not done them for fear of upgrading the software and then not being able to put twrp on or root it.
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
0sm1um said:
I did a very stupid thing.
I locked bootloader with fastboot, with LineageOS installed. Device was not binded to xiaomi account.
Now when I reboot, it shows "System destroyed" message.
Same message, when trying to boot to recovery. (Because I had TWRP installed)
When I do fastboot oem unlock I got FAILED (remote: Token Verify Failed, Reboot the device)
When I use MI unlock tool with newly created MI account, it says
Code:
Please, add your account in MIUI's settings
.
When I downloaded stock fastboot firmware, and tried to ./flash_all.sh, or ./flash_all_lock.sh I got
product: sagit
erasing 'boot'...
FAILED (remote: Erase is not allowed in Lock State)
finished. total time: 0.000s
Erase boot error
How do I recover?
Click to expand...
Click to collapse
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
demonntlxda said:
i think you can research about Mi 6 EDL / Test point. by open the back and connect the test point, you can flash in lock state. i have not use it for a long time so this hint is all i can give.
Click to expand...
Click to collapse
Well sadly Xiaomi locked down EDL mode and that needs people working for Xiaomi to fix it.
Sadly a service center will not fix it because they will convince you to dump your phone in a rubbish bin and buy a new mi 11 because Xiaomi could earn more.
So that is a bummer but your phone needs a new motherboard.
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