Hello,
First sorry for my English is so bad because I am Brazilian and I do not write well.
I have a Xperia SP and he had a ROM, I was changing the ROM and she was not installing for reasons that I'm trying to install a different version of my possible to XSP. Thus I uninstalled the old version and unwittingly I turned off my phone and now it is stuck in the logo of Sony.
Searching here and reading some many forums found some solutions put any work on my mobile.
Steps to follow:
1: I have installed FlashTool and tried to download the file * .ftf the original Xperia SP, however not sure gave the program is returning error in system.sin file and does not run the flash completely.
ERROR:
17/029/2015 23:29:58 - INFO - Flashing data
17/030/2015 23:30:00 - INFO - Closing TA partition
17/030/2015 23:30:00 - INFO - Opening TA partition 2
17/030/2015 23:30:00 - INFO - Processing system.sin
17/030/2015 23:30:00 - INFO - Checking header
17/030/2015 23:30:01 - ERROR - Processing of system.sin finished with errors.
17/030/2015 23:30:01 - INFO - Ending flash session
17/030/2015 23:30:01 - ERROR -
17/030/2015 23:30:01 - ERROR - Error flashing. Aborted
17/030/2015 23:30:01 - INFO - Flashing finished.
17/030/2015 23:30:01 - INFO - Please unplug and start your phone
17/030/2015 23:30:01 - INFO - For flashtool, Unknown Sources and Debugging must be checked in phone settings
2: researching a little more found something to extract the file * .tft zip in and try to flash but with FASTBOT only file system.sin however this step earlier returned mistake and now it does not load the file so any. If I try to give fastbot in kernel.sin it performs regular put in system.sin not run.
However after I run fastbot the kernel.sin the phone it tries to connect however he stands on the logo of Sony yet, but now it off and try to connect again, as if he had not found the systen.sin (which imagines that is the operational system)
3: I tried to correct the Sony PC Companion put it reports that there is a system installed on the phone and it is not possible to recover.
Another problem not appear that the phone is charging, it apparently is entering mod flash in and out even when connected to power .
Here is my problem, my cell phone does not come out of the Sony screen and I can not access the CWM in any way to try to install something for him.
I wonder if there is a solution to this problem.
Solved - resolvido
Hello everyone,
after a long break your head finally managed to solve the problem ( thank God !!!)
I discovered the fastboot and researched more about it and after many attempts almost breaking all here , figured out how to solve the problem.
First I realized I was only installing Kernels via fastboot so I basically looked for a way ta install something via Fastboo was then I found this turorial : http_://theunlockr.com/2014/03/04/install-custom-recovery-sony-xperia-sp-12-1-0-266/)
leading to an XDA link to download a file that reinstalava .elf CWM on your phone.
With so I reinstalled the CWM and insert the ROM again.
Well what was the mistake that I hope no one else comet.
PLEASE DO NOT TURN YOUR CELL AFTER ERASE A ROM BECAUSE THE PHONE WILL NOT FIND OPERATING SYSTEM AND NEITHER WILL ON.
If you make the same mistake you download this file and use the fastboot .
Thank you all
Obrigado pela ajuda pessoal.
olá a todos,
depois de muito quebrar a cabeça finalmente consegui resolver o problema (graças a Deus!!!)
Eu descobri o FastBoot e pesquisei mais sobre ele e apos muitas tentativas quase quebrando tudo aqui, descobri como resolver o problema.
Primeiro percebi que somente estava instalando Kernels via FastBoot então eu basicamente procurei uma forma ta instalar algo via Fastboo foi então que encontrei este turorial: http_://theunlockr.com/2014/03/04/install-custom-recovery-sony-xperia-sp-12-1-0-266
que levava a um link do XDA para download de um arquivo .elf que reinstalava o CWM no celular.
Com isso eu reinstalei o CWM e inseri a ROM novamente.
Bom qual foi o erro que espero que ninguem mais cometa.
POR FAVOR NÃO DESLIGUE SEU CELULAR APÓS APAGAR UMA ROM POIS O CELULAR NÃO VAI ENCONTRAR SISTEMA OPERACIONAL E NÃO VAI NEM LIGAR.
caso você cometa o mesmo erro que eu baixe este arquivo e use o fastboot.
Obrigado a todos
Ou com flash tools você podia fazer flash de um kernel e ligar o celular sem formatar '-'
Hello, to start my English is very bad so I'll try to explain what's going on with my device.
I bought the XT1068 defective, apparently in the photos would be simple the process, I would install the ROM stock and it would remove the message bootloader and ready. I've tried absolutely everything
It appears the error "Invalid boot image header!"
If I try for a ROM on it it gives some errors, for example "failed to validate ftm image that means its not fih mode load and validate boot image" other "version is downgraded primary_gtp" (this when I tried for the ROM 4.4.4 ).
When I try to install the ROM on mfastboot so it appears these errors "C: \ Users \ PEDRO \ Desktop \ adb> mfastboot flash partition gpt.bin
Reported target max download size of 536870912 bytes
sending 'partition' (32 KB) ...
OKAY [0.050s]
writing 'partition' ...
(Bootloader) Preflash validation failed.
What do I do ?? please help me
---------text in portuguese----------
Olá, pra começar meu ingles é péssimo então vou tentar explicar o que está acontecendo com meu aparelho.
Eu comprei o XT1068 com defeito, aparentemente nas fotos seria simples o processo, eu instalaria a ROM stock nele e tiraria a mensagem de bootloader e pronto. Já tentei absolutamente de tudo
Ele aparece o erro "Invalid boot image header !"
Se eu tento por uma ROM nele ele dá alguns erros, por exemplo "failed to validate ftm image that means its not fih mode load and validate boot image" outro "version downgraded for primary_gtp" ( isso quando eu tentei por a ROM 4.4.4 ).
Quando vou tentar instalar a ROM no modo mfastboot ele aparece esses erros "C:\Users\PEDRO\Desktop\adb>mfastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 0.050s]
writing 'partition'...
(bootloader) Preflash validation failed.
O que eu faço ?? por favor me ajudem
Queria uma ajuda, estou tentando desbloquear o bootloader do meu G5s plus xt1802, porém quando dígito. Fastboot oem get_unlock_data
(bootloader) Unlock data:
(bootloader) Unlock data unavailable
(bootloader) Failed
OKAY [ 0.125s]
finished. total time: 0.125s
Alguém poderia me ajudar, a oem está habilitada no desenvolvedor e depuração USB tambem.
Any command I try to put to flash the device it crashes and doesn't complete. I've tried recovery flash, boot, bootloader and none of them finish sending the file. I've already downloaded other files from other sites and it still doesn't send.
The device doesn't start recovery mode and I need to change roms.
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot devices
0047929849 fastboot
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot getvar max-sparse-size
getvar:max-sparse-size FAILED (remote: unknown command)
finished. total time: 0.004s
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot oem fb_mode_set
(bootloader) slot-count-size: not found
(bootloader) slot-suffi: not found
...
(bootloader) 'fb_mode_setfixes' is not a supported oem command
(bootloader) See 'fastboot oem help'
FAILED (remote failure)
finished. total time: 0.006s
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot flash partition gpt.bin
(bootloader) slot-countxes: not found
(bootloader) slot-suf: not found
(bootloader) slot-suffi: not found
(bootloader) partition-typ: not found
(bootloader) max-download-: not found
target didn't report max-download-size
sending 'partition' (37 KB)...
-----------------------------------------------------------------------------
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>adb devices
List of devices attached
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot devices
0047929849 fastboot
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.4.0-beckham-v2.img
target reported max download size of 536870912 bytes
sending 'recovery' (33308 KB)...
(bootloader) Requested download size is more than max allowed
FAILED (remote failure)
finished. total time: 0.004s
C:\Users\kauan\OneDrive\Área de Trabalho\minimal_adb_fastboot_1.4.3_portable>fastboot flash recovery twrp-3.4.0-beckham-v2.img
(bootloader) slot-countad-: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) partition-: not found
target didn't report max-download-size
sending 'recovery' (33308 KB)...
I had similar problem with old ROM, device fails to receive any file (for boot or flash); the solution was to update ROM using it's internal update.
MagusWRM said:
I had similar problem with old ROM, device fails to receive any file (for boot or flash); the solution was to update ROM using it's internal update.
Click to expand...
Click to collapse
could you tell me how i do this update?
kauankas said:
could you tell me how i do this update?
Click to expand...
Click to collapse
Configurations > System > Advanced > System update
But there are a chance that there is no update avaiable; in that case you can try ADB after boot: enable developer mod and then activate ADB from there, try the commands again.
Spoiler: Huehuehue
Configurações > Sistema > Avançado > Atualizações do sistema
Há grandes chances de não ter atualização disponível; nesse caso recomendo tentar ADB pelo sistema (depois do boot): ativar modo desenvolvedor e de lá ativar ADB; tentar os comandos novamente.
MagusWRM said:
Configurations > System > Advanced > System update
But there are a chance that there is no update avaiable; in that case you can try ADB after boot: enable developer mod and then activate ADB from there, try the commands again.
Spoiler: Huehuehue
Configurações > Sistema > Avançado > Atualizações do sistema
Há grandes chances de não ter atualização disponível; nesse caso recomendo tentar ADB pelo sistema (depois do boot): ativar modo desenvolvedor e de lá ativar ADB; tentar os comandos novamente.
Click to expand...
Click to collapse
There's only one problem, the device after the lineageOS update doesn't turn on anymore, it gets stuck in the boot animation. huehue
Do you have an AMD processor? Several devices do not like AMD processors for some reason. In my experience they have anything from Nextbit/Razer, Moto Z3 series, and Essential Phone PH-1. They all work fine for me on any Intel based processor.
christian.farmerf said:
Do you have an AMD processor? Several devices do not like AMD processors for some reason. In my experience they have anything from Nextbit/Razer, Moto Z3 series, and Essential Phone PH-1. They all work fine for me on any Intel based processor.
Click to expand...
Click to collapse
You have no idea what you're talking about. I've rooted/rom'd hundreds of devices, including a few dozen RP2's, PH-1's, Pixel's, and International Samsungs... all on an amd cpu. Root and Rom doesn't care AMD or Intel. Something was just wrong with your setup.
KaptinBoxxi said:
You have no idea what you're talking about. I've rooted/rom'd hundreds of devices, including a few dozen RP2's, PH-1's, Pixel's, and International Samsungs... all on an amd cpu. Root and Rom doesn't care AMD or Intel. Something was just wrong with your setup.
Click to expand...
Click to collapse
I have every idea what i'm talking about. Older bootloader versions on some phones don't work by default with an AMD CPU. There is a fix for Windows users that just adds a few registry keys but linux users like myself are more or less out of luck. I suggest the OP and yourself check out this thread: here
Boom roasted.
christian.farmerf said:
Do you have an AMD processor? Several devices do not like AMD processors for some reason. In my experience they have anything from Nextbit/Razer, Moto Z3 series, and Essential Phone PH-1. They all work fine for me on any Intel based processor.
Click to expand...
Click to collapse
por incrivel que seja acabei de fazer no meu celular, pelo meu desktop que é um amd não estava indo nem com reza, mudei para note com intel e deu certo
Buonasera ho riscontrato un grosso problema con il mio Samsung M31
In pratica il telefono rimane acceso in download mode e quando lo riavvio torna in download mode mostrandomi sempre lo stesso errore:
modalità odin (avb fail)
ripristino: errore durante la convalida del piè di pagina. (0)
ripristino: errore durante la verifica dell'immagine vbmeta: intestazione vbmeta non valida (6)
Sapreste darmi una soluzione?
Translated by GT:
Good evening I have encountered a big problem with my Samsung M31
In practice, the phone stays on in download mode and when I restart it it goes back to download mode, always showing me the same error:
odin mode (avb fail)
recovery: Error validating footer. (0)
recovery: error while verifying vbmeta image: invalid vbmeta header (6)
Could you give me a solution?
Seems you flashed something corrupt. I recommend a clean flash with the official firmware for your device.