[Q] Sudden Brick - G 2014 Q&A, Help & Troubleshooting

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

Related

Modifying partition table

I'm trying to increase the size of internal storage (/data) on my TL at the expense of emulated external storage (/storage/sdcard0). I found that FTF files contain partition-image.sin, which describes all 15 partitions on the phone. Using the partition modification guide for 2011 Xperias, I made the necessary adjustments in the partition image and userdata .sins, compiled the FTF, and flashed it. However, the result was only a decrease in size of external storage while internal storage was still measured at 1.97GB despite fdisk -l showing the new partition table. Is there another place that controls partition sizes? Or is it possible only with unlocked bootloaders? Is there anything similar to Samsung's PIT configs?
I don't want to use Link2SD because the phone has sufficient onboard memory, and turning off emulated external storage isn't an option either because I want to use the physical SD card only for photos, music, and nandroid backups.
Hello,
some months ago I make a modified partition table with some command line programs
Finally I've got a unique internal memory of 7,36 GB at least. IT'S TRUE! IT'S POSSIBLE! (with locked bootloader, stock kernel, rooted phone e CWM installed).
Unfortunately, I make this in a lot of time and I don't rember the right order of the command.
There are the steps that I make certainly:
1 Restore the swap between internal and external memory (if you do it). ITA: ripristinare lo swap tra la sdcard falsa e la sdcard (se è stato fatto...)
2 Rooting. ITA: rootare il telefono
3 Installing CWM. ITA:installare cwm
4 Mount /system/ in RW. ITA:montare /system in scrittura (ad esempio con es file explorer (abilita root explorer, clicca su root explorer e poi ci sono le opzioni di montaggio di /system))
5 Copy the partition commands (parted, mk2fs, resize2fs and similar (I can't post the link, search it)) in /system/bin/. ITA: trasferire in /system/bin (o /sbin ??) comandi partizionamento
6 Mount /system/ in RO. ITA: montare /system in sola lettura
7 Reboot in CWM. ITA: riavviare il telefono in recovery (spegni, accendi tenendo premuto vol. giu)
8 With ADB do this. ITA: avere in una cartella i comandi adb e aprire il prompt dei comandi in quella cartella e dare i seguenti comandi
9 Erase the false SDcard partition. ITA: cancellare partizione sdcard falsa
adb devices
adb shell
parted /dev/block/mmcblk0
print
rm 15
Now we need to extend the partition 14 from these blocks: 1621 > 7818
and to extend the related filesystem.
Someone know how to extend partition and filesystem from command line?
Note:
Unforunately the command 'parted' doesn't support ext4 filesystem. So we can't do that with this command.
The command resize2fs seems doesn't work, infact when I execute that command it says always 'command not found'.
If somethings go wrong, you need to restore your phone with Sony Update Service. It's very very very simple.
you look into the repartion method we used on the xoom,
it finds when the partitions start and end and then patches it to somewhere else to make the partitions bigger:
the patch is here: https://github.com/Schischu/xoom-ElementalX/commit/859d63b5cd9bd12ed778192234b0a1f5242df94b
the thread full of info is here: http://forum.xda-developers.com/showthread.php?t=2506997
teidus said:
Hello,
some months ago I make a modified partition table with some command line programs like these
Finally I've got a unique internal memory of 7,36 GB at least. IT'S TRUE! IT'S POSSIBLE! (with locked bootloader and stock kernel).
Unfortunately, I make this in a lot of time and I don't rember the right order of the command.
There are the steps that I make certainly:
1 Restore the swap between internal and external memory (if you do it). ITA: ripristinare lo swap tra la sdcard falsa e la sdcard (se è stato fatto...)
2 Rooting. ITA: rootare il telefono
3 Installing CWM. ITA:installare cwm
4 Mount /system in RW. ITA:montare /system in scrittura (ad esempio con es file explorer (abilita root explorer, clicca su root explorer e poi ci sono le opzioni di montaggio di /system))
5 Copy the partition commands (parted, mk2fs, resize2fs and similar (I can't post the link, search it)) in /system/bin/. ITA: trasferire in /system/bin (o /sbin ??) comandi partizionamento
6 Mouynt /system in RO. ITA: montare /system in sola lettura
7 Reboot in CWM. ITA: riavviare il telefono in recovery (spegni, accendi tenendo premuto vol. giu)
8 With ADB do this. ITA: avere in una cartella i comandi adb e aprire il prompt dei comandi in quella cartella e dare i seguenti comandi
9 Erase the false SDcard partition. ITA: cancellare partizione sdcard falsa
adb devices
adb shell
parted /dev/block/mmcblk0
print
rm 15
Now we need to extend the partition 14 from these blocks: 1621 > 7818
and to extend the related filesystem.
Someone know how to extend partition and filesystem from command line?
Note:
Unforunately the command 'parted' doesn't support ext4 filesystem. So we can't do that with this command.
The command resize2fs seems doesn't work, infact when I execute that command it says always 'command not found'.
Click to expand...
Click to collapse
So I've searched all over the place before and I can't find parted and other disk utilities for Android. Can you share the link?
It would be awesome if your method works.
matt4321 said:
you look into the repartion method we used on the xoom,
it finds when the partitions start and end and then patches it to somewhere else to make the partitions bigger:
the patch is here: https://github.com/Schischu/xoom-ElementalX/commit/859d63b5cd9bd12ed778192234b0a1f5242df94b
the thread full of info is here: http://forum.xda-developers.com/showthread.php?t=2506997
Click to expand...
Click to collapse
I never see these threads.
It's an hardest work to apply this solution to Xperia... Do you think it's possible?
teidus said:
I never see these threads.
It's an hardest work to apply this solution to Xperia... Do you think it's possible?
Click to expand...
Click to collapse
I think it can be ported. It's in the kernel and not specific to any board/manufacturer
Sent from my LT30p using Tapatalk
Finally I do it! This is the result: (image in some time)
Here is the solution to unifing the two internal memory of the sony Xperia V and (?) related phones. Tested on Xperia V (LT25i) running Android 4.1.2
You need:
1 Rooted phone (link in some time)
2 CWM installed on phone (link in some time)
3 ADB installed on pc
4 Some partitioning commands files (link in some time)
5 4.1Swap.zip
Here is the solution:
1 Copy the partition commands in /external_sd/
2 Reboot in CWM (turn off, wait one minute, turn on while pressing a lot of time volume down button)
3 With ADB do this:
adb devices
adb shell
parted /dev/block/mmcblk0
print
rm 15
rm 14
mkpartfs logical ext2 1621 7818
name 14 UserData
quit
chmod 777 /external_sd/tune2fs
chmod 777 /external_sd/e2fsck
cd external_sd
tune2fs -j /dev/block/mmcblk0p14
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p14
e2fsck -fpDC0 /dev/block/mmcblk0p14
The first boot will require some minutes. Wait! (Now you have an internal memory of 5,68 GB)
Apply this zip through CWM
4.1Swap.zip (link in some time) (This will swap the internal memory with the external memory.) (Thanks to tangjun269)
In CWM wipe cache and Dalvik Cache.
Done!
If somethings goes wrong, simply download and install Sony Update Service and make a restore.
teidus said:
Finally I do it! This is the result: (image in some time)
Here is the solution to unifing the two internal memory of the sony Xperia V and (?) related phones. Tested on Xperia V (LT25i) running Android 4.1.2
You need:
1 Rooted phone (link in some time)
2 CWM installed on phone (link in some time)
3 ADB installed on pc
4 Some partitioning commands files (link in some time)
5 4.1Swap.zip
Here is the solution:
1 Copy the partition commands in /external_sd/
2 Reboot in CWM (turn off, wait one minute, turn on while pressing a lot of time volume down button)
3 With ADB do this:
adb devices
adb shell
parted /dev/block/mmcblk0
print
rm 15
rm 14
mkpartfs logical ext2 1621 7818
name 14 UserData
quit
chmod 777 /external_sd/tune2fs
chmod 777 /external_sd/e2fsck
cd external_sd
tune2fs -j /dev/block/mmcblk0p14
tune2fs -O extents,uninit_bg,dir_index /dev/block/mmcblk0p14
e2fsck -fpDC0 /dev/block/mmcblk0p14
The first boot will require some minutes. Wait! (Now you have an internal memory of 5,68 GB)
Apply this zip through CWM
4.1Swap.zip (link in some time) (This will swap the internal memory with the external memory.) (Thanks to tangjun269)
In CWM wipe cache and Dalvik Cache.
Done!
If somethings goes wrong, simply download and install Sony Update Service and make a restore.
Click to expand...
Click to collapse
Awesome! I found some issues with the current versions of recovery, which require a couple of additional steps (including using 2 different recoveries), but overall this works. I'll put this into a more comprehensive guide applicable to all models regardless of their storage capacity.
I would be glad to get rid of this nons-sense internal SD, or make it a lot smaller. All my apps are system apps, I don'r want to bother with maintaining two (or three) different places. I am reading here, but this certainly is far beyond me, resp. I am scared.
peter-k said:
I would be glad to get rid of this nons-sense internal SD, or make it a lot smaller. All my apps are system apps, I don'r want to bother with maintaining two (or three) different places. I am reading here, but this certainly is far beyond me, resp. I am scared.
Click to expand...
Click to collapse
I've created a thorough guide on how to resize the partitions. I did not test it with removal of the emulated SD card altogether but if you aren't afraid to experiment, please do try and let me know if it works.
Hey bsines, I think is usefull to include in the tutorial the swap of the internal memory with the external sd.
It's only a simple zip.
What do you think?
Search 4.1Swap.zip in the forum.
lost acces to internal sd
ok i have an issue, have a zte nx406e that is a version of zte nubia z5s mini, and its only for my country and this phone hasnt an offical dev. i made a mistake triying to format external sd to expand internal whit link2sd, i errase the sdcard0 wich is the internal. for (pics,vids etc) an i cant remount it. idk how to do this plz i need help.
PD sorry for my bad english. it is self learned.

Helpme OEM!

Instale TWRP. Por error desactive, despues OEM. Ahora no funciona..custom binary blocked. How to solve???

[GUIDE only for those who already have the 20 pro for CallRecorder Genuine]

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).

[harpia][8.x] Cache ext4 to f2fs

How about friends of XDA I encourage you to open this thread because I had the curiosity to change the cache partition of my team from ext4 to f2fs since the read that this has certain benefits on ext4, here in the forum I did not find much the truth always on the internet I read the same "edit the fstab to change from ext4 to f2fs" and "your kernel has to support f2fs" the kernel is not a problem, natively it already supports f2fs so there was only the fstab but they never said how to do it or they just said formatee with twrp and ready so playing a bit with the mount command and the qcom.fstab file gave me a little idea of ​​how this works.
The file fstab.qcom is located in "/ system / vendor / etc /" (Android 8) this is responsible for checking the partitions in the boot "system, data, cachr, boot etc" basically there are the variables that would occupy the kernel to mount the partitions (fs tipe, mount flags, mount point etc.
The only thing that needs to be done so that you can boot the computer with the partition in f2fs is to edit the file a bit
Original
"/ dev / block / bootdevice / by-name / cache / cache ext4 rw, nosuid, nodev, noatime, barrier = 1, data = ordered wait, check, formattable"
Edited
"/ dev / block / bootdevice / by-name / cache / cache f2fs rw, nosuid, nodev, wait noatime, check, formattable"
Note that only changed from ext4 to f2fs and removed barrier = 1, data = ordered, if you do not delete these 2 options the computer will not start, it will remain stuck in the bootlogo
Now you just have to restart in twrp and change the file system to f2fs restart and it should work.
And that would be all, quite easy truth xD I'm pretty green in this the truth but someone to serve this information.
Note: you can do the same with the system partition only if being honest ext4 is a much better option for a read-only partition.
That's all thanks for taking the trouble to read, I leave screenshot of what I raise, by the way I speak Spanish and I have to use the translator to publish this xd sorry.
Good job
Excellent Job
Question important
Hola amigo me podrías ayudar tengo mucho interés en hacerle esto a mi moto g4 play pero dime algo, esto funciona con la rom stock rooteada? o solo con una Custom Rom? y que ventajas tiene cambiar de EXT4 a F2fs?
por cierto no si se hablas español o inglés

Stuck in [Preso em] Fastboot Mode

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 ...

Categories

Resources