This guide was not created by me but by a user who took my request to heart and is ante0 whoever had the phone in hand and wanted to try it would make a huge pleasure to the whole community! let the result know, of course![/SIZE]
Download and install Minimal ADB and Fastboot (if you have not already done so): https://www.androidfilehost.com/?fid=746010030569952951
Download and extract HwCallRecorder: https://mega.nz/#!QHwkCY4A!KDZhQmhqE ... Incmy_y06-c0O4
Download TWRP: https://mega.nz/#!RfhHhARK!UIFgF-ndi...CLxFTspAJAos5E
Start in fastboot mode (connect usb, hold down vol + power until the phone is restarted, keep holding down vol)
Flash TWRP: flash fastboot recovery_ramdisk P20_TWRP_PIEZ.img
Restarting for recovery (Remove the USB cable, press and hold up + power)
In TWRP, connect usb to computer for
open a command prompt and verify that ADB
functions: shell adb
If you get a ": / #", it works. If it says "error: no device / emulator found" does not work
If ADB works:
Open a new command prompt and type this command:
adb push HwCallRecorder / / system / app /
This assumes that the command prompt is open in the same folder as HwCallRecorder is (and HwCallRecorder is checked out), otherwise you will need to "cd" or place HwCallRecorder in the same folder as you have adb.
Switch to the command prompt with the adb shell in it.
Copy these commands one by one and paste the adb shell command prompt: (Ctrl + C then press the right mouse button to paste)
chmod -R 0755 / system / app / HwCallRecorder
chmod 0644 /system/app/HwCallRecorder/HwCallRecorder.apk
chmod 0644 /system/app/HwCallRecorder/oat/arm64/HwCallRecorder.odex
chmod 0644 /system/app/HwCallRecorder/oat/arm64/HwCallRecorder.vdex
At the end it is possible to restart the system.
If adb does not work, there is not much to do: /
OTG does not seem to work (yet) in this TWRP. It can once someone builds a better version
ITA VERSION:
Scarica e installa Minimal ADB e Fastboot (se non lo hai già fatto): https://www.androidfilehost.com/?fid=746010030569952951
Scarica ed estrai HwCallRecorder: https://mega.nz/#!QHwkCY4A!KDZhQmhqE ... Incmy_y06-c0O4
Scarica TWRP: https://mega.nz/#!RfhHhARK!UIFgF-ndi...CLxFTspAJAos5E
Avvio in modalità fastboot (Collega usb, tieni premuto vol down + power fino al riavvio del telefono, continua a tenere giù vol )
Flash TWRP: flash fastboot recovery_ramdisk P20_TWRP_PIEZ.img
Riavvio per il ripristino (Rimuovere il cavo USB, tenere premuto up + alimentazione)
In TWRP, collegare usb al computer per
aprire un prompt dei comandi e verificare che ADB
funzioni : shell adb
Se ottieni un ": / #", funziona. Se dice "errore: nessun dispositivo / emulatore trovato" non funziona
Se ADB funziona:
Apri un nuovo prompt dei comandi e digita questo comando:
adb push HwCallRecorder / / system / app /
Questo presuppone che il prompt dei comandi sia aperto nello stesso cartella come HwCallRecorder è (e HwCallRecorder è estratto), in caso contrario dovrai "cd" o posizionare HwCallRecorder nella stessa cartella che hai adb.
Passa al prompt dei comandi con la shell adb al suo interno.
Copia questi comandi uno per uno e incolla il prompt dei comandi di adb shell: (Ctrl + C quindi premi il tasto destro del mouse per incollare)
chmod -R 0755 / system / app / HwCallRecorder
chmod 0644 /system/app/HwCallRecorder/HwCallRecorder.apk
chmod 0644 /system/app/HwCallRecorder/oat/arm64/HwCallRecorder.odex
chmod 0644 /system/app/HwCallRecorder/oat/arm64/HwCallRecorder.vdex
Al termine è possibile riavviare il sistema.
Se adb non funziona, non c'è molto da fare: /
OTG non sembra funzionare (ancora) in questo TWRP. Può una volta che qualcuno ne costruisce una versione migliore.
This guide has not been tested on Mate 20. It's fine on Mate 10 Pro Pie, but the big question is if that TWRP works or not. So someone with a Mate 20 would have to test that first. Don't proceed with this guide if you don't know how to restore stock recovery (I haven't seen any firmware for Mate 20 yet, except for a early test version released as BLAOVS on FF).
Related
Hi everyone, I have a weird problem. Suddenly my phone turn of and when I turn on every app I have (included system apps) starts to FC and can't use any app.
I have TWRP but when I try to perform a factory reset the recovery dies and the only way to restart is perform a hard reset. Can't install any rom, any backup and when I do a wipe cache or dalvik or system has no effect on the system. Can't install anything via ADB or fastboot. Can't install a new recovery. Can't install nothing, is like the /data partition is read only.
Sorry for my poor english, hope understand me. Cheers.
Pongo el problema en castellano, tal vez alguien entienda mejor.
El telefono se me apago de repende, cuando lo volvi a encender todas las aplicaciones empezaron a tirar FC y no lo pude usar mas. No puedo hacer un factory reset desde recovery porque se reinicia y queda trabado en el recovery, haciendo wipe system, cache y dalvik no hace ningun efecto, no puedo instalar ninguna rom ni actualizacion ni backup ni nada. Intente volverlo de fabrica con los scripts que hay en la pagina y ninguno hace ningun efecto en absoluto, tampoco puedo instalar un recovery distinto, porque a pesar de que me dice que esta todo bien cuando reinicio sigue con el recovery que tenia. Intente montar /data desde recovery y me dice que la memoria es solo lectura.
Alguien tiene idea de lo que pueda ser?
Desde ya muchas gracias. Saludos.
Mmm I'll say dead nand but try e2fsck from adb.
fburgos said:
Mmm I'll say dead nand but try e2fsck from adb.
Click to expand...
Click to collapse
What is dead nand? Can you help me a little bit with e2fsck? I have read a couple of thing about it but I dont know exactly what to do-
Thanks.
Im not really shure how it goes, on this device I don´t own the device yet.... remember you could end in a worst brick.
Basically you setup correct adb and drivers on your computer, connect the phone, start adb and enter some commands.
adb devices <---- to check if device is recognize by the pc
adb shell <---- start command line for the phone
cat proc/partitions <-----this shows all the partitions in a format mmcblk0p##
umount /system
umount /data
e2fsck -fv dev/block/mmcblk0p## <--- I personally did this for all ## i had in my phone this ## is the number of the partition, data and system are commonly the biggest partitions
fburgos said:
Im not really shure how it goes, on this device I don´t own the device yet.... remember you could end in a worst brick.
Basically you setup correct adb and drivers on your computer, connect the phone, start adb and enter some commands.
adb devices <---- to check if device is recognize by the pc
adb shell <---- start command line for the phone
cat proc/partitions <-----this shows all the partitions in a format mmcblk0p##
umount /system
umount /data
e2fsck -fv dev/block/mmcblk0p## <--- I personally did this for all ## i had in my phone this ## is the number of the partition, data and system are commonly the biggest partitions
Click to expand...
Click to collapse
Thanks for your time man. I have use these commands and nothing, errors everywhere and nothing happens, Just 2 blocks are formatted and the phone stills in the same conditions.
Thanks.
That's bad news, I think its a bad nand, or wrong permissions as you said,
Can you upload the output for
cat proc/mounts
fburgos said:
That's bad news, I think its a bad nand, or wrong permissions as you said,
Can you upload the output for
cat proc/mounts
Click to expand...
Click to collapse
Hi, I have the same issues with my phone.... here the output. Hope someone can help!
~ # ←[6ncat proc/mounts
cat proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,size=428000k,nr_inodes=107000,mode=
755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime,size=428000k,nr_inodes=107000 0 0
/dev/block/mmcblk0p38 /data f2fs ro,seclabel,relatime,background_gc=off,user_xat
tr,inline_xattr,acl,errors=continue,active_logs=6 0 0
/dev/block/mmcblk0p38 /sdcard f2fs ro,seclabel,relatime,background_gc=off,user_x
attr,inline_xattr,acl,errors=continue,active_logs=6 0 0
/dev/block/mmcblk0p35 /cache ext4 ro,seclabel,relatime,data=ordered 0 0
/dev/block/mmcblk1p1 /sdcard1 vfat rw,relatime,fmask=0000,dmask=0000,allow_utime
=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
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 '-'
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
@alanduda65 Please use the English language!
XDA Forum Rules:
Spoiler: Rule No. 4
4. Use the English language.
We understand that with all the different nationalities, not everyone speaks English well, but please try. If you're really unable to post in English, use an online translator. You're free to include your original message in your own language, below the English translation. (This rule covers your posts, profile entries and signature). You could try :- https://translate.google.com/ or https://www.babelfish.com/ or use one of your choice.
alanduda65 said:
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
Click to expand...
Click to collapse
Hi!
Same thing here, Asus zenfone 5 ZE620KL, after trying to install twrp, phone got stuck in fastboot mode, can't get anywhere else, not recovery or boot to OS
Tried on AMD pc and Intel too, any ideas on how to get the phone working again?
You'll have to use QFIL to unbrick the phone. A quick google should show you how to do this
asusasus55 said:
You'll have to use QFIL to unbrick the phone. A quick google should show you how to do this
Click to expand...
Click to collapse
Do we really need to open the back?
alanduda65 said:
Mod edit - translated by https://www.deepl.com/translator:
Hello!
My device is stuck in Fastboot Mode, but I can't install recovery mode or access it.
Regardless of the keys I use to restart the device (Volume + / volume - / power) it always restarts in fastboot Mode.
When trying to install the recovery mode, and try to use the second command, it appears the following error:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
When trying to install a new rom, once it gave me the following information: Partition not found, but I don't know if it has much to do with it.
I've searched a lot of alternatives, but I always get back to Fastboot Mode.
Can anyone help?
*******************************
Olá!
Meu dispositivo esta preso em Fastboot Mode, mas não consigo instalar o modo recovery e nem acessa-lo.
Independente das teclas que utilizo para reiniciar o aparelho (Volume + / volume - / power) ele sempre reiniciar em fastboot Mode.
Ao tentar instalar o modo recovery, e tentar utilizar o segundo comando, ele aparece o seguinte erro:
C:\adb>fastboot oem reboot-recovery
...
FAILED (remote: unknown command)
finished. total time: 0.000s
Na tentativa de instalar uma nova rom, uma vez ele me deu a seguinte informação: Partition not found, mas nao sei se tem muito a ver.
Ja pesquisei inumeras alternativas, mas sempre retorno ao Fastboot Mode.
Algum pode ajudar?
Click to expand...
Click to collapse
Hey guy,
My phone was running the rom "UL-ASUS_X00QD-ASUS-AOSP-17.0615.2005.25-1.1.1-user.zip" (downloaded from Asus Web). I tried to install the TWRP ver 3.3.1 unofficial and my phone was stuck on the fastboot mode only.
After a lot of searching on how to fix the issue, I didn't change anything and almost gave up, until I've read this thread.
My Asus Zenfone 8 flip is STUCK in CSC FASTBOOT MODE PLZ HELP!, RAW FIRMWARE ANYONE???
These are what I did to get the phone into the recovery mode:
1. Extract the rom zip file that my phone was running on.
2. Copy the file boot.img to adb folder.
3. On PC, at adb folder enter CMD, connect the phone then type
fastboot -w
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot reboot recovery
4. After that, my phone can be booted into the recovery mode.
Hope you can solve the same problem as me.
Bye bye ...
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.
I'm going to give a solution for this problem (Note: I don't know if there is another solution, please if you know another fix post it here). I'm doing this post because i had this problem and there wasn't any guide on how to fix it, but wil too much patience and experimenting with my AGS2-W09 i could finally fix it . I'm going to post this on English and Spanish. I'm not a developer, I just want to share this with all that may have this problem, hope this work for you . / Voy a dar una solución para este problema (Nota: no sé si hay otra solución, por favor, si conoce otra solución, publíquela aquí). Estoy haciendo esta publicación porque tuve este problema y no había ninguna guía sobre cómo solucionarlo, pero con demasiada paciencia y experimentando con mi AGS2-W09, finalmente pude solucionarlo. Voy a publicar esto en inglés y español. No soy un desarrollador, solo quiero compartir esto con todos los que puedan tener este problema, espero que esto os funcione también
* First of all, we have to download some things:
- PotatoNV: https://github.com/mashed-potatoes/PotatoNV
- Hisuite Proxy v3.3.0: https://github.com/ProfessorJTJ/HISuite-Proxy/releases
- Huawei Update Extractor (v0.9.9.5): You can download it on this post on XDA
- Huawei test point drivers: https://androidfilehost.com/?fid=14943124697586361242
- Firmware files: Get them on Huawei Firm Finder
- Minimal ADB and Fastboot Tool (V1.4.3): https://forum.xda-developers.com/t/tool-minimal-adb-and-fastboot-2-9-18.2317790/
- 7-zip: https://7-zip.org/
* Process:
1.- Ok, first we have to download, extract and execute Hisuite Proxy, because you'll need it to be able to download the firmware (It's important to keep it open)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2.- Now, we have to download the firmware for our exact model. I will be using the firmware for the AGS2-W09 model but it work for AGS2-L09 too. We're going to get these files from the Huawei Firm Finder site. HERE, there is a list with all region codes
We have to type our exact model on "Phone Model" ( As I said, i'll be using the AGS2-W09 ). On region..., well our region XD, I'll be using the C432 region code.
Now, click on the three dots on the last firmware avaliable ( I'll be using AGS2-W09 8.0.0.328(OCEC432) ). Click on "Check Rom Status" and it should say "Approved for Installation", if it doen't say that, try another firmware.
If it said Approved, we can continue by clicking on "Download Rom" an downloading all files. It should say something like this:
3.- Extracting Process:
Now, I hardly reccomend to use 7-zip, because WinRAR sometimes cause problems at this step.
Extract update.zip on the folder with the same name and extract update_full_XXX-XXX_xx_xx.zip on a folder with same name. ( For example my update_full file is update_full_AGS2-W09_hw_eu)
Now, go into the update folder, right click on UPDATE.APP and extract the file: 7.oeminfo.img. Flash it onto the tablet using fastboot flash oeminfo (drag here that oeminfo.img file)
4.- Huawei Update Extractor:
Now open Huawei Update Extractor, go to settings and uncheck Verify header checksum and verify file checksum. It should look like this:
Now go back to Extract and on update file, select the UPDATE.APP from the update folder:
Right click on any of them and select "Extract All", then create a folder where you want and extract these files there. After extracting them, go back to Extract and select the UPDATE.APP on the update_full_XXX-XXX_xx_xx folder (In my case it's update_full_AGS2-W09_hw_eu) and choose the UPDATE.APP, then extract them the same way as you did with the other UPDATE.APP, but you have to extract this UPDATE.APP on the same folder you've extracted the other update.app.
5.- FASTBOOT
Now, we are ready to flash all IMG files we've extracted on the tablet. We have to do this one by one in order, I know there are a lot of files but I did that and worked for me. NOTE: There some files that it'll say that it couldn't be flashed but it's not a problem, just continue on flashing. FOR EXAMPLE: fastboot flash cache (drag and drop cache.img here) or fastboot flash recovery_ramdisk (drag and drop recovery_ramdis here)
6.- FINISHING PROCESS
When you finish flashing all files just do fastboot reboot and it should turn on. At this point I recommend you installing a custom rom like LineageOS, LeaOS or crdroid. List of compatible roms for this tablet
I hope it works for you as well, like I said earlier I'm not a developer, I'm just a person who likes technology and had this problem. I just share this because it helped me and because I didn't see any post here explaining something. As I said if you now another fix feel free to comment. / Espero que te funcione también a ti, como dije anteriormente no soy un desarrollador, soy solo una personal que le gusta la tecnología y tuve este problema. Comparto esto porque me ayudó y porque no vi ningún post explicando porqué pasa o como arreglarlo. Como dije si sabes de otra solución, por favor coméntalo.
I'll add the Spanish steps soon. / Añadiré los pasos en Español pronto.
(Reserved)
(Reserved)
Is there an order that these need to be flashed in? I have 33 files (ignoring the header files) and I don't know all of the partitions that the files need to be flashed to. This is the list I have so far, do I need other files and do I have the correct partitions?
Code:
fastboot flash cache CACHE.img
fastboot flash crc CRC.img
fastboot flash curver CURVER.img
fastboot flash cust CUST.img
fastboot flash dts DTS.img
fastboot flash erecovery_kernel ERECOVERY_KERNE.img
fastboot flash erecovery_ramdisk ERECOVERY_RAMDI.img
fastboot flash erecovery_vbmet ERECOVERY_VBMET.img
fastboot flash erecovery_vendor ERECOVERY_VENDO.img
fastboot flash fastboot FASTBOOT.img
fastboot flash fw_hifi FW_HIFI.img
fastboot flash fw_lpm3 FW_LPM3.img
fastboot flash ptable HISIUFS_GPT.img
fastboot flash kernel KERNEL.img
fastboot flash odm ODM.img
fastboot flash product PRODUCT.img
fastboot flash ramdisk RAMDISK.img
fastboot flash recovery_ramdisk RECOVERY_RAMDIS.img
fastboot flash recovery_vbmeta RECOVERY_VBMETA.img
fastboot flash recovery_vendor RECOVERY_VENDOR.img
fastboot flash sensorhub SENSORHUB.img
fastboot flash sha256rsa SHA256RSA.img
fastboot flash system SYSTEM.img
fastboot flash trustfirmware TRUSTFIRMWARE.img
fastboot flash vbmeta VBMETA.img
fastboot flash vendor VENDOR.img
fastboot flash version VERSION.img
fastboot flash verlist VERLIST.img
fastboot flash product PRODUCT.img
fastboot flash xloader XLOADER.img
You have to flash them on the same order they have extracted. Example: first cache, second CRC, etc. And the partition hace the same name as the IMG files. Example: fastboot flash xloader xloader
Thx bro very nice tuto . All works for me
woofer50 said:
Thx bro very nice tuto . All works for me
Click to expand...
Click to collapse
Glad it helps
The only part of all the steps that I don't understand is the part "5.- FASTBOOT"
Can you explain how this step has to be done and the programs that have to be used?
Kaparroz said:
The only part of all the steps that I don't understand is the part "5.- FASTBOOT"
Can you explain how this step has to be done and the programs that have to be used?
Click to expand...
Click to collapse
You have to use the minimal adb and fastboot tool to flash all the .img files.
Thank you very much, I'll try it.
I have other Huawei devices with locked Bootloader, I managed to update from download mode without any problem, with the first Firewall downloaded. But this AGS-L09 is burning me to excess and I have never achieved anything until now. There may be some version of Firewall with Android 7.0 that can be installed from download mode from MicroSd. I have two AGS-L09 one with Android 7.0 and one with Android 8.0 which includes a lot of unnecessary problems.