i have already unlock my bootloader and i download a ROM (RROS 8.1).
Use "fastboot flashing unlock" and it says :failed ,already fastboot unlock. I think its really unlocked.
I boot to bootloader and use command "fastboot flash system X:/system.img" and it failed
the OUT-POST is :
target reported max download size of 471859200 bytes.
sending sparse 'system'(460796 KB)
OKAY [11.152s]
writing 'system'
FAILED(remote: sparse flash write failure)
finished. total time: 11.502s .
im frome china so i cant use Gapps and i think its no necesessry to unlock frp and of course i checked SETTING and found nothing like 'OEM UNLOCK' .
What should i do to countine write System ? i think it trasfer system.img correctly and the problem is the Writing operation.
Related
I made a bootlogo with Moto Boot Logo Maker (http://forum.xda-developers.com/moto-g/themes-apps/app-motorola-boot-logo-maker-source-t2848667).
But when I tried to install the bootlogo via fastboot, I did the mistake of try to flash 'boot' instead of 'logo'.
I tried to flash bootlogo in 'boot' partition 3 times, and now I don't know what to do.
Please help, what to do now?
I don't know if I can turn off my phone or try to restart, I don't know if it'll start again or if it'll hard brick because I tried to flash 'boot' partition.
What can I do? Will I need to download original firmware and flash boot with its correct image?
Computer Logs
Code:
fastboot flash boot bootlogotest.bin
target reported max download size of 299892736
sending 'boot' (597 KB)...
OKAY [0.047s]
writing 'boot'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.094s
fastboot flash boot bootlogotest.bin
target reported max download size of 299892736
sending 'boot' (597 KB)...
OKAY [0.062s]
writing 'boot'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.094s
fastboot flash boot logo.bin
target reported max download size of 299892736
sending 'boot' (421 KB)...
OKAY [0.078s]
writing 'boot'...
(bootloader) Invalid boot image
FAILED (remote failure)
finished. total time: 0.094s
Phone Logs
Code:
Fastboot Reason: Reboot mode set to fastboot
USB connected
cmd: getvar:partition-type:boot
cmd: getvar: max-download-size
cmd: download:000954e8
cmd: flash:boot
Mismatched partition size (boot)
cmd: getvar:partition-type:boot
cmd: getvar: max-download-size
cmd: download:000954e8
cmd: flash:boot
Mismatched partition size (boot)
cmd: getvar:partition-type:boot
cmd: getvar: max-download-size
cmd: download:000696e8
cmd: flash:boot
Mismatched partition size (boot)
Phone Info
Code:
Model: XT1025 Dual Sim w/ TV - Brazillian Retail
Updated to first 5.1 Official OTA on July 23rd
Then installed Resurrection Remix
So is your phone booting now?
It wouldn't have done any harm imo.
I haven't came across it before so nothing can be said for sure.
Chances are, fastboot formatted your boot partition and when tried to flash the IMG, throws that error. In that case, your boot partition is empty and system is without a kernel. You will need to flash stock IMG in that case.
However, it might be the case that fastboot performed the check before formatting partition and your kernel might be residing there safely.. But no way of knowing that without booting.
So if you want to be on safe side, flash the stock img.
If you want to try and check , try rebooting once. You might be able to boot into bootlaoder mode after.
Tapped from my Moto X
neo.ank said:
I haven't came across it before so nothing can be said for sure.
Chances are, fastboot formatted your boot partition and when tried to flash the IMG, throws that error. In that case, your boot partition is empty and system is without a kernel. You will need to flash stock IMG in that case.
However, it might be the case that fastboot performed the check before formatting partition and your kernel might be residing there safely.. But no way of knowing that without booting.
So if you want to be on safe side, flash the stock img.
If you want to try and check , try rebooting once. You might be able to boot into bootlaoder mode after.
Tapped from my Moto X
Click to expand...
Click to collapse
I thought boot partition was important as motoboot's bootloader partition or gpt, forgot 'boot' is kernel.
fastboot formatted my boot partition, phone was stuck at bootlogo.
Downloaded official XT1025 firmware and flashed only boot partition.
Went to TWRP, installed my old custom kernel and now the phone is fine.
Thanks
Glad u solved it..
Tapped from my Moto X
The custom logo's doesn't flash on the boot partition, flash on the logo partition
Example: mfastboot flash logo nameoflogo.bin
So straight to it, when I am trying to flash twrp recovery img with adb I keep getting failed (remote:unknown command) .
Process I have done;
Turned on oem unlock and debugging in developer otions
Unlocked boot loader via adb with fastboot oem unlock
Rebooted and got corruption msg but thats due to bootloader unlock
Put twrp in adb folder
Rebooted into fastboot
attempted to flash twrp recovery img via fastboot flash recovery twrp.img
Then thats when I get my error as follows;
target reported max download size of 536870912 bytes
sending 'recovery' (19412 kb) ...
okay [0.443s]
writing 'recovery' ...
failed (remote: unkown command)
finished. total time: 0.469s
Did I miss a step? I was reading something about a "fake" bootloader unlock besides h850?? I did achieve root with a tot file and lg up that did have already twrp baked in, but I need to get a stock rom so I can go ahead and switch between root and non root, cause I use an application for work that doesn't like root
i know this is an old post but i'm having the same issue. is it not possible to flash recovery with latest firmware?
same
Hello. Today i tried to flash the phone to the stock ROM twice but it didnt work probably cause unlocked bootloader and custom recovery (TWRP).
So i brick the phone and now i cant access the rom or the recovery. All i can do is access the fastboot mode. I tried to install the new recovery through fastboot but it doesnt work.
I tried the twrp 3.0.2.0 and 3.0.1.0 for yuga.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot flash recovery recovery.img
target didn't report max-download-size
sending 'recovery' (10704 KB)...
OKAY [ 0.342s]
writing 'recovery'...
FAILED (remote: Command not allowed)
finished. total time: 0.347s
Tried various of commands that i found on google and this forum but nothing worked. I unlocked the bootloader before when i was installing various of custom roms. Could somehow stock rom affect the bootloader when i was flashing through flashtool ? I tried to only boot the recovery from the img, the command worked but the recovery did not boot.
Code:
C:\Users\Kubo\Downloads\platform-tools>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.341s]
booting...
OKAY [ 0.033s]
finished. total time: 0.378s
Tried to check the status of bootloader but the command is just showing ... and nothing happend. Tried to get the IMEI through fastboot getvar command but no output is given. Im desperate. Sorry for english not my native language. I'll appreciate all the help.
this is a message of the error that I have
my device is a tablet xperia z sgp311
C:\Users\4lph4\Appdata\Local\android\android-sdk\platform-tools>
fastboot devices
CB5A1U3D5J fastboot
fastbot flash recovery twrp-3.0.2-0-pollux_windy.img
Target didn't report max-download-size
sending 'recovery' (10688)
OKAY [ 0,343]
writing 'recovery'
FAILED (remote: Commnand not allowed)
finished, total time : 0.347
I want to use flashtool to do a relock and unlock again but I do not know if that would cause hard brick
novatosuper said:
this is a message of the error that I have
my device is a tablet xperia z sgp311
C:\Users\4lph4\Appdata\Local\android\android-sdk\platform-tools>
fastboot devices
CB5A1U3D5J fastboot
fastbot flash recovery twrp-3.0.2-0-pollux_windy.img
Target didn't report max-download-size
sending 'recovery' (10688)
OKAY [ 0,343]
writing 'recovery'
FAILED (remote: Commnand not allowed)
finished, total time : 0.347
I want to use flashtool to do a relock and unlock again but I do not know if that would cause hard brick
Click to expand...
Click to collapse
I got that problem too with an Experia tablet Z. I used the Xperia Companion's "repair" function (from sonys product support page) to restore my device that was unable to boot.
novatosuper said:
this is a message of the error that I have
my device is a tablet xperia z sgp311
C:\Users\4lph4\Appdata\Local\android\android-sdk\platform-tools>
fastboot devices
CB5A1U3D5J fastboot
fastbot flash recovery twrp-3.0.2-0-pollux_windy.img
Target didn't report max-download-size
sending 'recovery' (10688)
OKAY [ 0,343]
writing 'recovery'
FAILED (remote: Command not allowed)
finished, total time : 0.347
I want to use flashtool to do a relock and unlock again but I do not know if that would cause hard brick
Click to expand...
Click to collapse
tablet z doesn't have separate recovery partititon, so you have to use kernel with built-in recovery (fastboot flash boot twrp-3.0.2-0-pollux_windy.img)
or you can try to install it permanently to FOTA partition.
by typing: dd if=/sdcard/twrp-3.0.2-0-pollux_windy.img of=/dev/block/platform/msm_sdcc.1/by-name/FOTAKernel
is resolved thank you
is resolved thank you
Before:
I just unlocked the bootloader and installed a custom ROM (LineageOS 15.1: https://forum.xda-developers.com/huawei-y6/development/lineageos-15-1-huawei-y6-2018-t3832278) on my Huawei but it won't let me flash the TWRP from adb. I tried before flashing the custom ROM and also after but no progress. I tried with 'fastboot flash recovery recovery.img' as well as 'fastboot flash boot recovery.img' because I knew some smartphones include the recovery in the boot.img but I am always getting the same error:
Code:
fastboot flash recovery recovery.img
target reported max download size of 535822336 bytes
sending 'recovery' (16544 KB)...
OKAY [ 0.522s]
writing 'recovery'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.553s
I am not an expert but I understood that 'recovery' partition doesn't exist. I found some possible solutions online such as writing 'fastboot flash RECOVERY recovery.img' or 'fastboot flash erecovery recovery.img' (because Huawei calls the stock one 'erecovery') but they both gave me another error:
Code:
fastboot flash RECOVERY recovery.img
target reported max download size of 535822336 bytes
sending 'RECOVERY' (16544 KB)...
OKAY [ 0.522s]
writing 'RECOVERY'...
FAILED (remote: Command not allowed)
finished. total time: 0.528s
UPDATE: I found, maybe, the correct name of the recovery partition and it seems to work:
Code:
fastboot flash recovery_ramdisk twrp.img
< waiting for device >
target reported max download size of 535822336 bytes
sending 'recovery_ramdisk' (14026 KB)...
OKAY [ 0.443s]
writing 'recovery_ramdisk'...
OKAY [ 0.323s]
finished. total time: 0.767s
BUT it actually doesn't work properly because when I boot into recovery it boots the stock one. I tried other solutions found on the net like instantly unplug the phone after the flash and reboot it into recovery immediately but again it boots into stock one...
OTHER UPDATE: I managed to find and flash a TWRP that can boot up but it shows the internal storage 0MB not allowing me to install any .zip file. Because of that, I cannot install SuperSU to get root access.
I tried installing TWRP also with stock ROM but still showing 0MB because the phone is encrypted. To disable encryption I need to install the bluspark TWRP (As I found online), the problem is that bluspark won't boot and gets immediately overwritten by the stock ROM as it happened with the one I mentioned in the first update of the post.
Now I will try buying a microSD card and see if it shows right so that I can still flash .zip from the microSD card.
Now:
LATEST UPDATE: The SD card is working properly and I see it as around 60 GB instead of 64 but that's not the problem. I can see the .zip files I'd want to flash but when I try to do it it says me that it failed to mount every single partition and after some research I discovered that my Huawei has all the data encrypted. After other research I found that there are some TWRPs like blu_spark that could decrypt the data but every version I tried doesn't work and gets immediately overwritten by the stock recovery.
Does anyone know other methods to decrypt all the data on Huawei? Otherwise it's impossible to flash any .zip. Actually it flashes it but it fails to update the partitions state so the system doesn't recognize the changes.
Rooting Huawei is so difficult.. I will buy an OP5t as soon as I have the money XD.
Y6 2018 twrp
Any progress? I'm also looking for a version of TWRP that works with the Y6 2018.