Database Info

Help can only access fastboot mode and locked bootloader and stuck

HELP CAN ONLY ACCESS FASTBOOT MODE AND LOCKED BOOTLOADER AND STUCK
Recovery not working, boot not working, only fastboot&rescue mode working but the problems is that i relocked the bootloader and now i cant unlock it and fastboot dont allow me to flash anything like recovery.img
also tried to flash update.zip but cmd says not enough space.? so anyone have i clue what to do? can i get rid of the out of space error? somehow flash something or an command in cmd fastboot to get my phone working?
PLease help

getvar:all FAILED (remote: Command not allowed) it says command not allowed even in that command. and its bootloader lock is on any workaround so i can install update.zip without cmd says not enought space? or some workaround or command in fastboot to bootloader unlock with fastboot or any other idees?

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery.img
target reported max download size of 471859200 bytes
sending 'recovery' (36998 KB)...
OKAY [ 0.786s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.786s
C:\Program Files (x86)\Minimal ADB and Fastboot>
ALWAYS GETTING FAILED (remote: Command not allowed)

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot update update.zip
archive does not contain 'android-info.txt'
error: update package 'update.zip' has no android-info.txt

i think YOU ARE DOOMED??
only thing you can do is getting it back to the service center..gud luck buddy...

goran85 said:
HELP CAN ONLY ACCESS FASTBOOT MODE AND LOCKED BOOTLOADER AND STUCK
Recovery not working, boot not working, only fastboot&rescue mode working but the problems is that i relocked the bootloader and now i cant unlock it and fastboot dont allow me to flash anything like recovery.img
also tried to flash update.zip but cmd says not enough space.? so anyone have i clue what to do? can i get rid of the out of space error? somehow flash something or an command in cmd fastboot to get my phone working?
PLease help
Click to expand...
Click to collapse
same problem,, how to solve it??

writing 'recovery'...
FAILED (remote: Command not allowed)
sometime happenned to me and when installed the correct drivers in windows installed ok

Getting ADB / fastboot working correctly (to reset radioband without flash)

Hi,
Yesterday my nephew wanted to show me a cool trick, getting to the settings menu. Although i had seen that already, i let him..
If only i hadn't, as he clicked on the radioband button with only "US" as a choice, and now i can't receive calls or call out myself.
As i can't risk losing data, i can't reflash, there is just too much i can't backup (Like Google Authenticator, i would have to disable it on 50+ accounts first)
So found the following link https://talk.sonymobile.com/t5/Xperia-Z1-Compact/WARNING-Never-Change-Radio-Band/td-p/905055/page/4, where all you need is ADB and your phone in fastboot / bootloader.. So, i have my Z5 in Developer mode, enabled USB Debugging (Also tried OEM unlocking as well), installed the latest ADB ( I tried both "Minimal ADB and Fastboot" and "platform-tools-latest-windows") and installed the "latest_usb_driver_windows". (After Phone started in fastboot, updated the S1.. Fastboot hardware drivers with the ones downloaded)
All seems OK, devices are found, but after i give the commands i get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
FAILED (command write failed (Unknown error))
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
FAILED (command write failed (Unknown error))
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 0.001s
All that works is: fastboot reboot..
It looks like the phone doesn't accept the commands, as even when i try a not existing one like "fastboot erase notexistingfolder, i get the same response..
Is it the software on my Xperia Z5, 7.1.1 (32.4.A.1.54)?
Is it my Windows version (W10 Pro x64, 1709)?
Do i need a special/other ADB+driver combo? I already installed the Sony Android .inf (disabled Driver Signing)
I used ADB before, never run in so much problem getting it going.. It doesn't need to have a unlocked bootloader for this, right?
As anything like that defeats the purpose of restoring calls without erasing the device..
Any help is appreciated. Willing to install W7/8 if needed to get it to work or use some sort of bootable W7/disk..
Thanks, allegro16

allegro16 said:
Hi,
Yesterday my nephew wanted to show me a cool trick, getting to the settings menu. Although i had seen that already, i let him..
If only i hadn't, as he clicked on the radioband button with only "US" as a choice, and now i can't receive calls or call out myself.
As i can't risk losing data, i can't reflash, there is just too much i can't backup (Like Google Authenticator, i would have to disable it on 50+ accounts first)
So found the following link https://talk.sonymobile.com/t5/Xperia-Z1-Compact/WARNING-Never-Change-Radio-Band/td-p/905055/page/4, where all you need is ADB and your phone in fastboot / bootloader.. So, i have my Z5 in Developer mode, enabled USB Debugging (Also tried OEM unlocking as well), installed the latest ADB ( I tried both "Minimal ADB and Fastboot" and "platform-tools-latest-windows") and installed the "latest_usb_driver_windows". (After Phone started in fastboot, updated the S1.. Fastboot hardware drivers with the ones downloaded)
All seems OK, devices are found, but after i give the commands i get:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb reboot bootloader
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst1
erasing 'modemst1'...
FAILED (command write failed (Unknown error))
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase modemst2
erasing 'modemst2'...
FAILED (command write failed (Unknown error))
finished. total time: 0.002s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
erasing 'cache'...
FAILED (command write failed (Unknown error))
finished. total time: 0.001s
All that works is: fastboot reboot..
It looks like the phone doesn't accept the commands, as even when i try a not existing one like "fastboot erase notexistingfolder, i get the same response..
Is it the software on my Xperia Z5, 7.1.1 (32.4.A.1.54)?
Is it my Windows version (W10 Pro x64, 1709)?
Do i need a special/other ADB+driver combo? I already installed the Sony Android .inf (disabled Driver Signing)
I used ADB before, never run in so much problem getting it going.. It doesn't need to have a unlocked bootloader for this, right?
As anything like that defeats the purpose of restoring calls without erasing the device..
Any help is appreciated. Willing to install W7/8 if needed to get it to work or use some sort of bootable W7/disk..
Thanks, allegro16
Click to expand...
Click to collapse
You are fu*ked up! To use fastboot commands you have to unlock phone bootloader first, so you will loose data (as boot unlock always factory reset phone)

EugenStanis said:
You are fu*ked up! To use fastboot commands you have to unlock phone bootloader first, so you will loose data (as boot unlock always factory reset phone)
Click to expand...
Click to collapse
That would indeed be the case then.. I'll wait for Sony Mobile support.. If it's THIS easy to set the band to US, it should be easy to reset for them as well, right?
If i'm forced to reset / erase the Z5 in any way, i might as well change brands again and get a new unit.. At least then i can copy everything over piece by piece in time..
Thanks anyway.

fastboot: FAILED (remote: image verification error) after DC Phoenix unbrick

Hello
after i succesfully used DC Phoenix to recover Huawei Mate 8 (NXT-L29C432) i cannot flash TWRP or anything on my phone , as im still getting the "FAILED (remote: image verification error)" from fastboot. So i also cannot root and use the device as before
Im sure im not alone with this issue, but i cannot find any clear solution for this. Can you please help or advice me further??
I spent 15€, recovered the phone, but with this, its still partial success.
I basicaly followed https://forum.xda-developers.com/mate-8/help/how-to-unbrick-l29-al10-stuck-fastboot-t3599775
Here some outputs:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery twrp-3.2.0-0-next.img
target reported max download size of 471859200 bytes
sending 'recovery' (22140 KB)...
OKAY [ 0.530s]
writing 'recovery'...
FAILED (remote: image verification error)
finished. total time: 0.562s
Before the use of DC Phoenix, i always get this number.
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
QHC0216327001941 fastboot
Now:
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
0123456789ABCDEF fastboot
In Fastboot mode, on phone screen i see:
PHONE Unlocked
FRP Lock
DC - Unlocker 2 Client 1.00.1308 reports:
FB LockState: UNLOCKED
USER LockState: LOCKED
unlocked
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-lockstate
...
(bootloader) locked
OKAY [ -0.000s]
finished. total time: -0.000s
c:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
In Developer menu i have the
"Allow OEM unlock" grayed & disabled, im unable to swich it on..
Can you please explain what happend and how to fix this?
Thank you for further help.

Solved with mighty HCU client, i was able to import the just the SN back without problems. Then as usual.. unlock the bootloader, TWRP, SU... and now the phone is back in shape

I hope I can recover my Mate 9 Pro.
Maybe 15€ is have to spend but FunkyHuawei is more expensive.

Hi. I have same problem., I unlocked Huawei WAS-AL00 bootloader via Miracle Huawei Tool, it unlocked successfully. But, I can't flash TWRP, it says-FAILED (remote: image verification error)
Whent type fastboot oem lock-state info in CMD, it shows:
FB LockState: UNLOCKED
USER LockState: LOCKED
There is not FRP or OEM lock option in settings, becuse this is China version model and doesn't support Google Play.
What is USER LOCK STATE? Please help me. Thanks.

Remote:image verification error.
When i try to flash Mate 8 nxt l29 twrp recovery its says remote:image verification error..the phone fastboot is unlocked .i tried many twrp images but still the same problem

Bootloop after installing an Factory Image for Android 9.0

Hi, i just bought a Google Pixel from Ebay an tried to install an factory image for Android 9 from the Google Website. After fastboot the flash-all.sh (ive got Ubuntu) it got stuck a on the bootscreen (The Google Logo flashes in an instance and the Screen goes black again). Unfortunally the device is locked again (bootloader ist locked), so adb is not working. fastboot works but when i install some other factory images from the google website the problem with the flashing bootscreen reappears.
Loading into bootloader works:
Product/Variant: sailfish-US-PVT
Serial Number FA72H0300560
CPU: MSM8996SG-AB 0x10001
UFS: 32 GB Samsung
DRAM:4096MB Hynix LPDDR4
Boot-slot: a
Console: DISABLED
Secure Boot: PRODUCTION
Device is LOCKED
Could anyone help?
Thanks in advance.

Not sure but I think U can try booting into TWRP using "fastboot flash recovery twrp" command in CMD and than switch boot slot to b, my pixel is in the same situation - I can't boot into slot a and switching to b works
oh sry, the command is "fastboot boot path/to/twrp.img"

Thanks for your help, but it didn't work.
When I try to fastboot with following commands, it says:
sudo ./fastboot boot twrp-3.2.3-1-sailfish.img
Code:
Downloading 'boot.img' OKAY [ 0.785s]
booting (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 0.963s
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...

Double-check the checksum of the downloaded file.
Open the flash-all.sh file in a text editor, and manually run each of the flash commands individually. See if any of them throw an error.
You might also try to install the OTA.

I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....

ArchArch said:
I tried the first command in the flash-all.sh with the same results:
sudo ./fastboot flash bootloader bootloader-sailfish-8996-012001-1808030001.img
Code:
Sending 'bootloader_a' (32384 KB) OKAY [ 0.951s]
Writing 'bootloader_a' (bootloader) Command is not supported.
(bootloader) Please unlock device to enable this command.
FAILED (remote: '')
Finished. Total time: 1.189s
I will try out the OTA tomorrow. Does anyone know how to handle the payload.bin in to OTA.zip under a Linux-System?
ADB seems not be working. SO adb sideload ota_file.zip, like its mentioned on the google website seems to be also no option....
Click to expand...
Click to collapse
You need to re-unlock your bootloader first, then. Try fastboot flashing unlock .

No luck.
sudo ./fastboot flashing unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.007s
sudo ./fastboot oem unlock
Code:
FAILED (remote: 'oem unlock is not allowed')
Finished. Total time: 0.038s

ArchArch said:
sudo ./fastboot flash recovery twrp
Code:
fastboot: error: cannot load 'twrp': No such file or directory
I have Ubuntu with local platform-tools, so the commands look a little bit different...
Click to expand...
Click to collapse
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.

Levan_i said:
Did U opened CMD from the folder in which the TWRP file is located? Just type in CMD: "fastboot boot", and after "boot" type "twr" and press TAB button, program will locate the file itself.
Click to expand...
Click to collapse
He's using linux. The reason his flashes have been unsuccessful is because the bootloader is locked.

Tanks for your efforts so far...
Just for clarification: The initial plan was to root my device, according to the XDA-Guide for rooting an Pixel XL Android 9.0 (with the Files for my "Sailfish"-Pixel) https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-9-0-pie-unlock-t3825866
First when I bought the Pixel the "OEM Unlock"-Option in the Developers-Menu was greyed out.
So i tried out, beneath some other guides, the XDA-Guide for unlocking a Verizon Pixel and it worked. https://forum.xda-developers.com/pixel-xl/how-to/how-to-unlock-bootloader-verizon-pixel-t3796030
So I thought its an VerizonPixel, installed an Verizon Image from the Google Website, got always the message at bootup that an unlocked bootloader is some sort of threat, closed the Bootloader and the flashing bootscreen-problem began…

Stuck on "fastboot mode" when try boot TWRP

So I have and running latest version of OnePlus 7 Pro Oxygen OS.
I try to run with ADB with commando "fastboot boot TWRP.img".
I get the following:
PS C:\adb> fastboot boot C:\adb\twrp-3.5.0_9-0-guacamole.img
downloading 'boot.img'...
OKAY [ 0.809s]
booting...
OKAY [ 0.132s]
finished. total time: 0.956s
But he freezes at "fastboot mode" the stock recovery works but I wanna install magisk with TWRP.

And yes I have ADB files:
adb devices (I see that everthing is OK).
adb fastboot (I see ID)

May I ask, are you using the correct TWRP for A11?
Nebrassy TWRP.img is the one to use.