Hello,
I got a Sony Xperia M C1905 with CyanogenMod 14.1 installed.
Failling to install Gapps, I have decided to reinstall all OS from scratch following official procedure.
I have downloaded the last LineageOS build from this link: download.lineageos.org/nicki
I try to install it, following this link steps: wiki.lineageos.org/devices/nicki/install
I push the zip file with this command (despite that I don't have SD card):
Code:
adb push ./Downloads/lineage-14.1-20170427-nightly-nicki-signed.zip /sdcard/
I reboot my phone on TWRP recovery interface.
I try to apply update from emulated /data/media/0/lineage-14.1-20170427-nightly-nicki-signed.zip
I encountered following errors messages:
Code:
-- Install /data/media/0/lineage-14.1-20170427-nightly-nicki-signed.zip
E:failed to find /misc partition
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
Update package verification took 12.4 s (result 1).
E:Signature verification failed
E:error: 21
Now my phone can't boot (except on recovery interface).
I have not found how to disable signature verification and I don't known what to do next...
Any suggestion is welcome!
EDIT:
I try to run following fastboot commands without success (problem still occurs):
Code:
sudo fastboot erase system
sudo fastboot flash system ./Downloads/lineage-14.1-20170427-nightly-nicki-signed.zip
Strangely I don't have install menu on TWRP recovery interface. Do I need to store the build on a SD card to that?
EDIT 2:
I downloaded last TWRP image from this link: eu.dl.twrp.me/nicki/twrp-3.0.2-0-nicki.img.html
And try to flash it but it raised an error:
Code:
sudo fastboot flash recovery ./Downloads/twrp-3.0.2-0-nicki.img
target didn't report max-download-size
sending 'recovery' (11208 KB)...
OKAY [ 0.703s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.706s
Related
Hi, XDA community.
I got this phone today and user reported that suddenly is boot looping until battery dies.
When trying to wipe, stock recovery prompted:
Code:
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument)
I tried the following so far:
============================================================================
(#1)
If I wipe data or cache I get a big FAIL message and then
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
cust copying files...
copy cust files system error!ret = -1
I have no info if it's running JB or KK, nor B116 or whatever (I assumed it might be running JB).
============================================================================
(#2)
I can ADB and FASTBOOT to it, but device cannot be recognized properly.
Code:
C:\huawei>adb.exe devices
List of devices attached
? recovery
C:\huawei>adb.exe reboot bootloader
C:\huawei>fastboot.exe devices
????????(?(???O?(???????(?(? fastboot
I think that the bootloader is locked.
Code:
C:\huawei>fastboot.exe oem get-bootinfo
...
(bootloader) locked
OKAY [ 2.201s]
finished. total time: 2.201s
I tried to unlock it with something I found somewhere and apparently it worked:
Code:
C:\huawei>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\huawei>fastboot.exe oem get-bootinfo
...
(bootloader) unlocked
OKAY [ -0.000s]
finished. total time: -0.000s
I tried to delete the stock recovery and install TWRP, some other Open Recovery, and it prompted OKAY.
However after rebooting to recovery, is gone, I faced the exact same stock recovery with the same E:failed to mount /cache (Invalid argument) and the big FAIL when trying to wipe.
When going back to ADB and FASTBOOT, the bootloader is back to locked status. I can unlocked again (somehow) with the UUUUUUU thing but I'm not sure if this is actually flashing something.
============================================================================
(#3)
I tried to download Ascend P6 Software (P6-U06,Android 4.4.2,Emotion UI 2.3,V100R001C00B520,Latin_North_America-Channel,05011SYH).zip from the main portal (I am located in LATAM).
http://consumer.huawei.com/ve/support/products/manuals/ascend-p6-ve.htm
I got a UPDATE.APP file of 1.61GB. I copied the file on a 4GB microSD leaving it on the root under dload folder, inserted on the phone and rebooted using VOL+ VOL- combination, not plugged on the USB.
It didn't work. I ended in the same stock recovery with the E:failed to mount /cache (Invalid argument) error and the big FAIL again if tried to wipe.
I am running out of ideas. I will try to get in touch with Huawei later to see if I can get a bootloader unlock code for this phone since I cannot get the Product ID with the *#*#whatever, of course because is bricked.
Does anyone have anything that I might be missing here?
Should I tried with a 4.2.2 stock update.app instead of this 4.4.2?
Thank you so much for your time.
Hope to hear back from anybody.
UPDATE:
============================================================================
(#4)
I tried to extract and flash the boot, recovery, efi, system, cust, userdata, cache images from the 4.4.2 UPDATE.APP with the latest HuaweiUpdateExtractor_0.9.9.3 I found here. I used the fastboot flash for that (I had to unlock the bootloader again with the UUUUUUU command).
It took all of them with OKAY messages, excepted for the system one which prompted.
Code:
target reported max download size of 838860800 bytes
Invalid sparse file format at header magi
And when rebooting, it came back to the boot loop in the ASCEND logo, and when VOL+ VOL- same thing, back to stock recovery with mount /cache error and the BIG FAIL message when trying to wipe.
I am not sure if the thing that I keep getting the bootloader back to locked status everytime and reboot the phone is a bad sign.
Still no progress... will continue tomorrow.
Try wiping all infastboot and then reflashing clean. Files to make the prio list are boot.img recovery.img and cust.img Dont reboot untill you reflashed the files or you will get to a hard brick. So make a wipe and right after that flash. No reboots inbetween.
Sent from my SM-G850F
I'm on 7.1.2 (patch level July 2017, N2G48B). I would like to boot TWRP to make a backup before updating to the August patch. The device is unlocked. Fastboot fails to boot or flash TWRP:
Code:
fastboot flashing unlock
FAILED (remote: Device already unlocked)
fastboot boot twrp-3.1.1-0-dragon.img
creating boot image...
creating boot image - 13035520 bytes
downloading 'boot.img'...
OKAY [ 0.324s]
booting...
FAILED (remote: image verification failed)
fastboot flash recovery twrp-3.1.1-0-dragon.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
Somebody got an idea?
[Solved] Can't start TWRP any more
Solved, see here: https://forum.xda-developers.com/showpost.php?p=73361170&postcount=426 and the following posts.
Hi, yesterday I tried to flash a factory image to start fresh and the power went out mid flashing. Now the phone is stuck at bootloader.
I already tried multiple computers and cables, also have lastest platform tools and the phone is unlocked using fastboot flashing unlock and fastboot flashing unlock_critical.
Trying to flash factory image outputs this:
Code:
Sending 'bootloader' (36356 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'radio' (60388 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Invalid argument))
getvar:serialno FAILED (Write to device failed (Invalid argument))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Invalid argument))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Invalid argument))
fastboot: error: requirements not met!
Press any key to exit...
Trying to flash bootloader using
Code:
fastboot --slot a --force flash bootloader bootloader-taimen-tmz30m.img
outputs
Code:
fastboot: error: Device does not support slots
.
Also recovery doesn't work, not even booting the .img using fastboot boot twrp.img
fjgato said:
Hi, yesterday I tried to flash a factory image to start fresh and the power went out mid flashing. Now the phone is stuck at bootloader.
I already tried multiple computers and cables, also have lastest platform tools and the phone is unlocked using fastboot flashing unlock and fastboot flashing unlock_critical.
Trying to flash factory image outputs this:
Code:
Sending 'bootloader' (36356 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'radio' (60388 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Invalid argument))
getvar:serialno FAILED (Write to device failed (Invalid argument))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Invalid argument))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Invalid argument))
fastboot: error: requirements not met!
Press any key to exit...
Trying to flash bootloader using
Code:
fastboot --slot a --force flash bootloader bootloader-taimen-tmz30m.img
outputs
Code:
fastboot: error: Device does not support slots
.
Also recovery doesn't work, not even booting the .img using fastboot boot twrp.img
Click to expand...
Click to collapse
Nevermind, just tried another cable I found and it worked . I don't know how to change the title thought.
fjgato said:
Nevermind, just tried another cable I found and it worked . I don't know how to change the title thought.
Click to expand...
Click to collapse
Just report your thread to the moderator team designated to your area, which I am not, and have them change the thread title to what you want. Glad you figured out your problem :good::laugh:
fjgato said:
Hi, yesterday I tried to flash a factory image to start fresh and the power went out mid flashing. Now the phone is stuck at bootloader.
I already tried multiple computers and cables, also have lastest platform tools and the phone is unlocked using fastboot flashing unlock and fastboot flashing unlock_critical.
Trying to flash factory image outputs this:
Code:
Sending 'bootloader' (36356 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Sending 'radio' (60388 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
Rebooting into bootloader FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
< waiting for any device >
--------------------------------------------
getvar:version-bootloader FAILED (Write to device failed (Unknown error))
getvar:version-baseband FAILED (Write to device failed (Invalid argument))
getvar:serialno FAILED (Write to device failed (Invalid argument))
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
getvar:product FAILED (Write to device failed (Invalid argument))
Checking 'product' FAILED
Could not getvar for 'product' (Write to device failed (Invalid argument))
fastboot: error: requirements not met!
Press any key to exit...
Trying to flash bootloader using
Code:
fastboot --slot a --force flash bootloader bootloader-taimen-tmz30m.img
outputs
Code:
fastboot: error: Device does not support slots
.
Also recovery doesn't work, not even booting the .img using fastboot boot twrp.img
Click to expand...
Click to collapse
I'm having the same trouble that you did got the same stuff to pull up and everything all you did was switch out your data cable
PRODUCT NAME: GOOGLE Smaug
HW VERSION: 5
BOOTLOADER VERSION: Google_Snaug.7900.139.0
LOCK STATE: Unlocked
Hello. After doing the wipe of System, Data , Cache and Davlik..., I tried to install another PixelExperience ROM and it has given me an error of format as soon as start the installation on the TWRP and when the tablet restarting again at FastBoot I try to enter in TWRP again but give me the following error.
C:\ADB>fastboot boot twrp.img
creating boot image...
creating boot image - 16893952 bytes
Sending 'boot.img' (16498 KB) OKAY [ 0.419s]
Booting FAILED (remote: 'image verification failed')
fastboot: error: Command failed
So I can not enter the TWRP to install another ROM and the previous one does not boot, so when the tablet boot in normal mode, return again to wait for a FastBoot command.
Can you please help me?. I do not know what else to do
Thank you
Nobody can helpme with this error please?
I need to use TWRP again.
I have been trying and failing to get TWRP installed on my Pixel 3a XL running Android 9 stock image
Trying the recommended install instructions from the TWRP website, I keep getting the following error;
Code:
C:\platform-tools>fastboot boot twrp.img
Sending 'boot.img' (65536 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
C:\platform-tools>fastboot recovery twrp.img
fastboot: usage: unknown command recovery
C:\platform-tools>fastboot flash recovery twrp.img
Sending 'recovery' (65536 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
I have ensured the bootloader is unlocked, I have updated drivers from the OEM package, I can see devices properly with fastboot and adb, and I've even flashed stock images with fastboot. I've tried looking up this error, but all results point to solutions that don't work, or deleted posts. If anyone has some insight, I'd very much appreciate it.
Update to the latest version of Android or try an older version of TWRP. The latest version of TWRP doesn't like Android 9 (possibly other versions as well).
I believe this was the last update for twrp on android 9
Download twrp-installer-3.5.2_9-0-bonito.zip
Download page for twrp-installer-3.5.2_9-0-bonito.zip
dl.twrp.me