writing 'system' 1/4...
**FAILED (remote: flash write failure)**
finished. total time: 9.167s
Any solution...I have unlocked bootloader.
Related
So I downloaded this Archive.zip from http://forum.xda-developers.com/showthread.php?t=2064868
and I boot my device to fastboot...
now on my pc when i type:
fastboot flash recovery adsp.img
I get:
sending 'recovery' (6345 KB)...
OKAY [ 0.950s]
writing 'recovery'...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 0.998s
--------------------------------------------------------
or if i try:
>fastboot flash adsp adsp.img
sending 'adsp' (6345 KB)...
OKAY [ 0.949s]
writing 'adsp'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.485s
What am I doing wrong? I have HBOOT-1.13 and viperones rom on my HTC One S
Im pretty sure you cant flash it through fastboot.
You need hboot 1.09 or lower and flash through recovery.
I was given a droid razr hd (xt926). Guy said he took an update and when the phone rebooted, it wouldn't go past the M boot screen. I don't know what build he was on and I don't know the previous status of the phone (root, rom, unlock, etc)
I can access AP Fastboot but I can't access anything else (Recovery, BP Tools, Factory).
I am using a Team Black Hat Cable, the most recent Motorola_End_User_Driver_Installation_6.4.0_32bit Driver, and a Windows 7 computer (my best computer is at ASUS getting fixed).
AP Fastboot Reads:
Code:
AP Fastboot Flash Mode (S)
10.9B(*) (sha-61146a2, 2014-05-02 03:15:48)
eMMC Info: Size 16GB
Device is LOCKED, Status Code: 0
Battery OK
Transfer Mode:
USB Connected
Fastboot Reason: Boot menu selected
usb connected
______________________________________________________________________________
I first tried RSD Lite (using both 6.1.4 and 6.2.4 to flash VZW_XT926_4.4.2-KDA20.62-15.1_1FF.xml
I got:
Code:
Failed flashing process. 1/17 flash partition "gpt.bin" -> phone return FAIL
Trying VZW_XT926_4.4.2-KDA20.62-10.1_CFC_1FF.xml I had to delete the "getvar" line for it to begin BUT I also get the "gpt.bin" failed message here. If I delete steps in XML (get.bin, sbl1, sbl2, sbl3, etc) the process just gets hung up and fails on the next step
______________________________________________________________________________
Trying the most recent Matt's Utility, Mr.Parkinson's Utility, and SamuriHL's House of Moto (trying each build listed above) I get significant failed messages which I will post below.
Code:
Ready to flash...
Press any key to continue . . .
Flashing: UNIVERSAL.bat
sending 'sbl1' (101 KB)...
OKAY [ 0.031s]
writing 'sbl1'...
Failed to erase partition
Failed to flash partition sbl1
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl2' (127 KB)...
OKAY [ 0.031s]
writing 'sbl2'...
Failed to erase partition
Failed to flash partition sbl2
FAILED (remote failure)
finished. total time: 0.078s
sending 'sbl3' (512 KB)...
OKAY [ 0.062s]
writing 'sbl3'...
Failed to erase partition
Failed to flash partition sbl3
FAILED (remote failure)
finished. total time: 0.250s
sending 'rpm' (140 KB)...
OKAY [ 0.031s]
writing 'rpm'...
Failed to erase partition
Failed to flash partition rpm
FAILED (remote failure)
finished. total time: 0.218s
sending 'aboot' (256 KB)...
OKAY [ 0.031s]
writing 'aboot'...
Failed to erase partition
Failed to flash partition aboot
FAILED (remote failure)
finished. total time: 0.218s
sending 'modem' (30720 KB)...
OKAY [ 2.371s]
writing 'modem'...
Failed to erase partition
Failed to erase partition
Failed to write mmc
FAILED (remote failure)
finished. total time: 2.434s
sending 'fsg' (165 KB)...
OKAY [ 0.031s]
writing 'fsg'...
Failed to erase partition
Failed to flash partition fsg
FAILED (remote failure)
finished. total time: 0.094s
erasing 'modemst1'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
erasing 'modemst2'...
Failed to erase partition
FAILED (remote failure)
finished. total time: 0.047s
sending 'logo' (854 KB)...
OKAY [ 0.078s]
writing 'logo'...
Failed to erase partition
Failed to flash partition logo
FAILED (remote failure)
finished. total time: 0.140s
sending 'boot' (10240 KB)...
OKAY [ 0.796s]
writing 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED (remote failure)
finished. total time: 1.451s
______________________________________________________________________________
Trying to manually mfastboot in cmd, I get similar errors. I tried boot.img first and got this error
Code:
mfastboot.exe flash boot boot.img
sending 'boot'...
Failed to erase partition
Failed to flash partition boot
FAILED <remote failure>
finished. total time: 1.451s
Flashing gpt.bin partition
Code:
mfastboot flash partition gpt.bin
< waiting for device >
sending 'partition' (32 KB)...
OKAY [ 0.031s]
writing 'partition'...
This may take a few seconds, if a
different partition table is being
flashed since we need to backup
and restore a few partitions
Failed to program partition table
FAILED (remote failure)
finished. total time: 0.250s
Is the phone FUBAR or does anyone have a suggestion how I could fix this?
Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.
eckdawg5 said:
Spoke with the guy that gave me the phone. The update that bricked the device was 4-5 months ago. I'm guessing it was May for the kitkat update. He's not sure if it was running kitkat or jelly bean. It wasn't rooted and never was unlocked.
Click to expand...
Click to collapse
Sorry to be the bearer of bad news, just by looking at your screen shots, I can tell you it's hard bricked.
Sent from my VS985 4G
HI
i am facing the issue in my moto g xt1033
i cant move from here i have struck in bootloader v41.1a* and device is locked, if i try to unlock this but it shows bootloader unlock is disabled and also trying to flash bootloader with same bootloader v41.1a and other v41.18 it always shows the same error i.e bootloader unknown partition here are the error msg i attest down
Installing the new bootloader
target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [ 0.093s]
writing 'motoboot'...
(bootloader) Motoboot: Unknown partition name
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.132s
applying the changes...
rebooting into bootloader...
OKAY [ 0.002s]
finished. total time: 0.003s
checking...
getvar:version-bootloader FAILED (command write failed (Too many links))
finished. total time: 0.085s
hi,
I tried to use the unlock.cmd in command promt via fastboot, half of it worked it only unlocked my frp but it said "failed: Unknown Command !". Please help, is there any other way I can unlock my bootloader? My max pro m1 won't boot and doesn't have access to recovery mode. Thanks
C:\adb>C:\adb\unlock.bat.cmd
------------------------
Begin fastboot flashall
------------------------
Earse Data: Yes
Support All device
current-slot is current-slot
buildtype is user
target reported max download size of 536870912 bytes
sending 'IMAUOvZqcpug' (0 KB)...
OKAY [ 0.002s]
writing 'IMAUOvZqcpug'...
(bootloader) Begin to do frp unlock ...
(bootloader) FRP unlock successful !!!
OKAY [ 0.005s]
finished. total time: 0.009s
...
FAILED (remote: unknown command !)
finished. total time: 0.002s
...
FAILED (remote: unknown command !)
finished. total time: 0.002s
...
OKAY [ 0.002s]
finished. total time: 0.003s
All is download
Maybe update your adb/fastboot
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
FkReMy said:
using cmd
when trying to unlock oem; giving:
FAILED (remote: OEM unlock is not allowed)
finished. total time: 0.011s
-----------------------------------------------------------------
when trying to flash boot or recovery; giving:
boot:
sending 'boot' (29069 KB)...
OKAY [ 0.765s]
writing 'boot'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.787s
recovery:
sending 'recovery' (42204 KB)...
OKAY [ 1.103s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 1.121s
-----------------------------------------------------------------
when trying to change the partition giving:
C:\Users\Rfastboot --set-active=b
fastboot: unknown option -- set-active=b
-----------------------------------------------------------------
please help!!!
Click to expand...
Click to collapse
From what I found on the internet, I guess you didn't turn on the setting `oem allow unlock' in developer settings.
But isn't there `rescue party' (a subsystem of androids recovery which shows two options: 1) Try again 2) Factory data reset)?
If it is, just press that Try again button, wait until it boots into rescue party again and then press the Try again button again. Do that 5-7 times in a row (depending on the phone). Your phone should detect that your current slot is unbootable and should boot into the unupdated slot.
You could also try to find the stock image (or whatever image you have currently installed) and flash it within recovery (there should be a button labeled like `update...' or `sideload...' or something). That should also work.
If nothing helps, you could also factory data reset and hope that it works now...
If that also doesn't work, you could research abit about edl (emergency donwload mode) and how to use it to reflash your device.