"failed (remote: unlock failed - err: 0x7001)", - Android Apps and Games

Hi guys I have a problem I want to unlock bootloader huawei CRO L03, but when I follow all the steps I get an error
"failed (remote: unlock failed - err: 0x7001)",
I searched and can not find the solution, who can help me

Related

Unlock Token Check Failed!

I get this error when trying to unllock my Bootloader
writing 'unlocktoken'... FAILED (remote: unlock token check failed).
hboot-1.06.0000
RADIO-0.15.3501S.19
oPENdsp-V21.1.0.32.8314
EDIT::: Sorry its ok now must have been a corrupt token. sorry again please delete

Unable to flash with fastboot

Hello there,
I just got a Nokia 6.2 to use for my app reverse-engineering/development needs, but I would need to root it.
Recovery is just saying "no command" and fastboot does not want to flash recovery.
Code:
C:\Users\<user>\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot flash recovery twrp-3.3.1-PL2.img
Sending 'recovery' (38736 KB) FAILED (remote: 'unknown command')
fastboot: error: Command failed
Apperently the device's flashing functionality appears to be encrypted.
per the how-to at https://www.androidweblog.com/nokia-6-2-ta-1198-root-install-twrp-recovery/:
Code:
C:\Users\<username>\Downloads\platform-tools_r29.0.5-windows\platform-tools>fastboot oem unlock-go
FAILED (remote: 'Failed to unlock, decrypt failed!')
fastboot: error: Command failed
Device state is listed as unlocked.
Try
HTML:
fastboot flashing unlock

[FIXED] Factory Image Bricked My Device?

I'll start this off with the fact that my Pixel 4a is a Google Store variant and the bootloader is unlocked.
So basically I downloaded the October factory image off of Google's website with the intent of wiping my phone completely and starting fresh.
I flashed it using the flash-all script however during the install for some reason an error occurred and my 4a rebooted.
Now it apparently no longer has an OS installed and boots straight into fastboot, so all I have access to is fastboot and recovery mode.
Attempting to reflash the factory image with flash-all while in fastboot gives me the following which I have never seen before:
Code:
Sending 'bootloader' (8341 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (no link))
fastboot: error: Command failed
Sending 'radio' (72372 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
Rebooting into bootloader FAILED (Write to device failed (no link))
fastboot: error: Command failed
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (no link))
getvar:version-baseband FAILED (Write to device failed (no link))
getvar:serialno FAILED (Write to device failed (no link))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (no link))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (no link))
fastboot: error: requirements not met!
Attempted to run "Wipe data/factory reset" in recovery mode and get the following:
Code:
-- Wiping data...
E:eek:pen failed: /metadata/ota: No such file or directory
Formatting /data...
Formatting /metadata...
Wiping Titan M...
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
E:can't send spi message: Try again
Data wipe complete.
I've done this plenty of times before with other devices and have never ran into something like this, so I really am lost on what to do.
Edit: Just tried downloading the standalone OTA file from Google and flashing that. It went smoothly until it hit 94% and then there was an error. Even with the error that was enough for it to be able to boot into the OS though and everything seems to be working fine.
Hey there. Did you ever figure out a fix for this? I had a similar thing happen to me last night. Everything is working fine but I'm worried it will eventually have consequences.

Question help with the xt2215-4

just got this device from google fi and got the bootloader unlocked. not too bad of a device but i'm having issues flashing a gsi to it!
fastboot keeps telling me
Erasing 'system_a' (bootloader) Permission denied
FAILED (remote: '')
fastboot: error: Command failed
this is happening when trying to erase the system and it tell me this when trying to flash the gsi
Invalid sparse file format at header magic
Resizing 'system_a' FAILED (remote: '')
fastboot: error: Command failed
im stuck on what to do next
device is already rooted, the version of twrp in this forum dont boot so its out of the question
any advice is appreciated and if more info is need to help solve this issue feel free to ask!
thanks in advance!

Huawei Mediapad T5 stuck in eRecovery

Hi everyone,
i have a Mediapad T5 that it's unable to boot into OS. if i try to turn it on the tablet goes directly into the huawei eRecovery, and trying all the factory solutions (download and update, factory reset or anything else), just won't help and the tablet just goes back to the recovery.
I tried to use the HiSuite from huawei but once i got it in fastboot&rescue mode i receive the messagge that the device it's not supported.
Also while i'm here i also tried to unlock the bootloader but both PHONE and FRP are locked, so i just get errors.
I tried
fastboot flashing unlock
(bootloader) Necessary to unlock FRP!
(bootloader) Navigate to Developer options, and enable "OEM unlock"!
FAILED (remote: 'Command not allowed')
fastboot: error: Command failed
fastboot oem frp-unlock
FAILED (remote: 'oem_frp_check_password failed! Error = -1')
fastboot: error: Command failed
fastboot oem frp-erase
FAILED (remote: 'Command not allowed!')
fastboot: error: Command failed
PS C:\platform-tools>
Obviously i can't get into the system and enable the OEM unlock since the tablet doesn't boot into it.
Is there anything else i can try?

Categories

Resources