Greetings. When I was installing a custom rom on my device, I did a data format (the picture was said so), then loaded twrp from the rom, but it remains in the fastboot section. Reload is required to enter twrp. I tried 2 roms with twrp with orange fox, I didn't flash + mi and it stays on fastboot. I say let's do etc, I get an error like the following. twrp connection to device, computer also looks like about 10gb free space, but 128gb space.
: \ Users \ Samet Artuç \ Desktop \ Minimal ADB and Fastbootfastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
target reported maximum download size of 536870912 bytes
Sending 'vbmeta' (4KB) ...
OK [0.002sec]
Selamlar. Cihazıma özel bir rom yüklerken, bir veri formatı yaptım (resim öyle söylendi), ardından twrp'yi rom'dan yükledim, ancak fastboot bölümünde kalıyor. Twrp'ye girmek için yeniden yükleme gerekiyor. Turuncu tilki ile twrp ile 2 rom denedim, + mi flash yapmadım ve fastboot üzerinde kalıyor. Vbmeta yapalım diyorum, aşağıdaki gibi bir hata alıyorum. cihaza twrp bağlantısı, bilgisayar da yaklaşık 10 gb boş alan gibi görünüyor, ancak 128 gb alan var.
: \ Kullanıcılar \ Samet Artuç \ Masaüstü \ Minimal ADB ve Fastbootfastboot --disable-verity --disable-doğrulama flash vbmeta vbmeta.img
hedef, 536870912 baytlık maksimum indirme boyutunu bildirdi
'vbmeta' (4 KB) gönderiliyor ...
TAMAM [0,002sn]
'vbmeta' yazılıyor ...
BAŞARISIZ (uzak: Böyle bir bölüm yok.)
bitti. toplam süre: 0.008s
Related
Hello,
a friend gave me hier "bricked" fon. I could get it booting again, system is up and running - but with any sdcard. Not the external and neither the internal one.
That means I cant put a SAPIMG.nph or anything else to the sdcard.
I cant download an apk or modify anything.
adb shell is working, but certainly su not.
adb push hboot_2010_signed.img /sdcard
certainly doesnt work either, there is no sdcard!
ok, I tried now different fastboot operations.
to come closer:
./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... FAILED (remote: not allow)
... etc... all the normal stuff.. nothing wortks, I usualy get "Not allowed on a production phone"
What to do now, I have no clue anymore!
here my data:
./fastboot oem boot
... INFOsetup_tag addr=0xA0000100 cmdline add=0x880705C0
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 64
INFOTAG:hwid 0x1
INFOTAG:skuid 0x1E300
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x2
INFODevice CID is not super CID
INFOCID is VODAP102
INFOsetting.cid::VODAP102
INFOserial number: HT93YKF06262
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =346
INFOactive commandline: board_sapphire.disable_uart3=1 board_sap
INFOphire.usb_h2w_sw=1 board_sapphire.disable_sdcard=1 smisize=6
INFO4 androidboot.baseband=2.22.19.26I androidboot.cid=VODAP102
INFO androidboot.carrier=VODA-Germany androidboot.keycaps=qwerty
INFO androidboot.mode=normal androidboot.serialno=HT93YKF06262 a
INFOndroidboot.bootloader=1.33.0007 no_console_suspend=1 console
INFO=null
INFOPARTITIOM_NUM_MAX =6 Valid partition num=6
Do you see? There is the kernel option board_sapphire.disable_sdcard=1 set !!! But I cant disable it with a fastboot -c option.
./fastboot getvar version-main
version-main: 1.89.162.1
./fastboot getvar cid
cid: VODAP102C??a
#########
Any help is appreciated, thanks!
Code:
fastboot oem enableqxdm 0
Regarding root... follow my guide found in my signature..
./fastboot oem enableqxdm 0
... INFO[ERR] Command error !!!
OKAY
./fastboot devices
HT93YKF06262 fastboot
[[email protected] HTC]# ./fastboot flash recovery recovery-RA-sapphire-v1.7.0G-cyan.img
sending 'recovery' (4528 KB)... OKAY
writing 'recovery'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
this seemed to get me a little further:
./fastboot oem rebootRUU
... OKAY
[[email protected] HTC]# ./fastboot -c "board_sapphire.disable_sdcard=0 board_sapphire.disable_uart3=0" reboot
rebooting...
YEAH!"
but then..... still no sdcard when the OS was up :-(
any ideas?
Type
Code:
fastboot oem h
and post here the result.
Root and recovery = follow my guide found in my signature...
Just replace all "/sdcard" paths with "/data/local/tmp"
I use custom Rom in my game Moto G4 play, and at some point in time I try to get back to the rom stock, but I always get this error:
FAIL (Command write failed (argument invalid))
Or
Preflash validation failed
Another error is also (Data tranfer failure <Too many links>)
I already tried Rsd lite and it also did not work, and also clear by adbfastboot
This may have happened because in Twrp I deleted the system, internal memory, it was kind of a layman, and I was too curious, only able to use custom rom.
Nougat coming to G4 play and I with this problem.
Can anybody help me, thank you very much? :chorando:
I'm having this problem to go back to Stock ROM, my cell phone is a Moto G4 play xt1603, I use a custom ROM, have any tips, I already tried Rsd lite and nothing ...
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot oem fb_mode_set
...
OKAY [-0.000s]
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash partition gpt.bin
Target reported max download size of 268435456 bytes
Sending 'partition' (32 KB) ...
OKAY [0.078s]
Writing 'partition' ...
(Bootloader) Preflash validation failed
FAILED (remote failure)
Finished. Total time: 0
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Freeboot flash bootloader bootloader.img
Target reported max download size of 268435456 bytes
Sending 'bootloader' (2546 KB) ...
OKAY [0.219s]
Writing 'bootloader' ...
(Bootloader) flashing sbl1 ...
(Bootloader) flashing aboot ...
(Bootloader) flashing tz ...
(Bootloader) flashing hyp ...
(Bootloader) flashing rpm ...
OKAY [1.722s]
Finished. Total time: 2
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
S)> fastboot flash logo logo.bin
Target reported max download size of 268435456 bytes
Sending 'logo' (751 KB) ...
FAILED (data transfer failure (Too many links))
Finished. Total time: 0.187s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
S)> fastboot flash boot boot.img
Sending 'boot' (16384 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
S)> fastboot flash recovery recovery.img
Sending 'recovery' (16484 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sblocked)> fastboot flash dsp adspso.bin
Error: can not open 'adspso.bin'
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
> Fastboot flash oem oem.img
Sending 'oem' (13464 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
> Fastboot flash system system.img_sparsechunk.0
Sending 'system' (262141 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.1
Sending 'system' (262142 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.2
Sending 'system' (262140 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.3
Sending 'system' (259676 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
> Fastboot flash system system.img_sparsechunk.4
Sending 'system' (262140 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: 0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.5
Sending 'system' (262141 KB) ...
FAILED (command write failed (Invalid argument))
Finished. Total time: -0.000s
C: \ Users \ Vin \ ius \ Downloads \ Roms \ Rom3 \ ADB tool (No bootloader warning from
Sb)> fastboot flash system system.img_sparsechunk.6
Sending 'system' (262142 KB) ...
FAILED (command write failed (Invalid argument))
Finished.
Try flashing from a shorter path and remove spaces, Windows (and even Linux) are kinda stupid on handling these types of path, mainly Windows.
I'm almost sure it's handling it like: C:\Users\Vin\ius\Downloads\Roms\Rom3\ADB at every command not matter what you write.
Eu apaguei o celular pelo twrp e fui instalar o twrp atualizado nisso meu leeco le 2 x522, fico sem twrp porquê deu bug.
Ai eu fui volta com o twrp antigo não deu certo, da false para o desbloqueio do bootloader.
Vou deixa os comandos pra vocês verem e me ajudarem só agradeço pela atenção de vocês.
COMO EU DESBLOQUEIO O BOOTLOADER??
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot devices
7e60b741 fastboot
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.004s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot oem device-info
...
(bootloader) Device product name: [s2_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.010s]
finished. total time: 0.010s
C:\Program Files (x86)\Minimal ADB and Fastboot>
COMO EU DESBLOQUEIO O BOOTLOADER??
Click to expand...
Click to collapse
1. Enable developer options:
In Settings go to 'About Device' and click 7 x on 'Build Number'. New settings menu 'Developer Options' appears in Settings.
2. Allow OEM Unlock:
Go to 'Developer Options' and check 'Enable OEM Unlock' and 'Enable USB Debugging'
Zenfone ZE552KL stuck at ASUS boot logo and can only access fastboot. I tried using asus flash tool and whenever I flash stock oreo raw image it fails and status says FAILED(remote: writing partition failed)
I tried extracting the raw zip and run cmd command flashall_AFT.cmd WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw and this is the result
Code:
##################################################################
####################### FLASH RAW FILE ########################
##################################################################
## RAW: WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
## ERASE DATA: 0
## SSN:
===================================================================
[command] : fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android N 7.1.1)
// Version V1.4 (2017/05/20)
// Support_AB : 0
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 534773760 bytes
sending 'partition' CRC (0x3016d48d)...
OKAY [ 0.029s]
writing 'CRC'...
OKAY [ 0.022s]
sending 'partition' (33 KB)...
OKAY [ 0.062s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.227s
"FAILED, fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw failure, EXIT!"
The phone is not mine, a friend asked me to fix his phone and I hit a wall here. I cannot flash nor boot twrp.img. Whenever I try to flash twrp it fails and the error is remote: too many links. Any insights?
rexendz said:
Zenfone ZE552KL stuck at ASUS boot logo and can only access fastboot. I tried using asus flash tool and whenever I flash stock oreo raw image it fails and status says FAILED(remote: writing partition failed)
I tried extracting the raw zip and run cmd command flashall_AFT.cmd WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw and this is the result
Code:
##################################################################
####################### FLASH RAW FILE ########################
##################################################################
## RAW: WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
## ERASE DATA: 0
## SSN:
===================================================================
[command] : fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw
/////////////////////////////////////////////////
// ASUS Fastboot Tool (Android N 7.1.1)
// Version V1.4 (2017/05/20)
// Support_AB : 0
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_PROJECT_NAME = ZE552KL
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// CPU ID = 046
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// RE-PARTITION ENABLE
/////////////////////////////////////////////////
/////////////////////////////////////////////////
// ASUS_RAW_VERSION = V1
/////////////////////////////////////////////////
target reported max download size of 534773760 bytes
sending 'partition' CRC (0x3016d48d)...
OKAY [ 0.029s]
writing 'CRC'...
OKAY [ 0.022s]
sending 'partition' (33 KB)...
OKAY [ 0.062s]
writing 'partition'...
FAILED (remote: failed to write partition)
finished. total time: 0.227s
"FAILED, fastboot.exe flash all WW_ZE552KL_15.0410.1807.75_M3.10.47.19_Phone-user.raw failure, EXIT!"
The phone is not mine, a friend asked me to fix his phone and I hit a wall here. I cannot flash nor boot twrp.img. Whenever I try to flash twrp it fails and the error is remote: too many links. Any insights?
Click to expand...
Click to collapse
Hello friends, I came here to ask a question, I updated my device with a stock rom (bootloader unlocked), I was using normal, so I accidentally installed an OTA update,
after that it is in an infinite loop, goes into fastboot mode (recognizes the device serial but cannot flash anything, also tried ROMs via flash (unsuccessful), tried also via qfil and also unsuccessfully said that I wanted to know if anyone you can give me some instructions or I killed my phone.
Thank you very much in advance
willamy.lemos said:
Hello friends, I came here to ask a question, I updated my device with a stock rom (bootloader unlocked), I was using normal, so I accidentally installed an OTA update,
after that it is in an infinite loop, goes into fastboot mode (recognizes the device serial but
cannot flash anything
, also tried ROMs via flash (unsuccessful), tried also via qfil and also unsuccessfully said that I wanted to know if anyone you can give me some instructions or I killed my phone.
Thank you very much in advance
Click to expand...
Click to collapse
Mod edit - translated by https://www.deepl.com/translator:
Hello friend, this problem of yours I believe you can solve with ADB Flash Tools. I am having a similar problem. recently my device turned off and didn't turn on again. It connects as Qualcomm 9008. But it shows the following error in QFIL:
21:32:36: {ERROR: Unable to write to 'COM4. \ COM4', Windows API WriteFile Failed! Your device is probably *not* on this port, tried 100 times}
Write record to 'C: \ Users \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt' may take a minute
The log is 'C: \ Users \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt'
Download failed: FireHose failed: FHLoader failed: Process failed
Could someone please help me?
Thank you for your attention.
******************************************************
Olá amigo, esse seu problema acredito que consiga resolver com o ADB Flash Tools. Eu estou com um problema parecido. recentemente meu aparelho desligou e não ligou mais. ELE Conecta Como Qualcomm 9008. Porem apresenta o Seguinte Erro no QFIL:
21:32:36: {ERRO: Não foi possível gravar em '\\. \ COM4', Falha de WriteFile da API do Windows! Seu dispositivo provavelmente * não * está nesta porta, tentadas 100 vezes}
Gravar o registro em 'C: \ Users \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt' pode demorar um minuto
O log é 'C: \ Usuários \ Nizack \ AppData \ Roaming \ Qualcomm \ QFIL \ COMPORT_4 \ port_trace.txt'
Falha no download: Falha no FireHose: Falha no FHLoader: Falha no processo
Alguém poderia me ajudar?
Obrigado pela atenção.