Develop Bugs

[Q] [HELP]I cant turn on my kindle fire.

Hello everyone, Kindle fire is my first android device(i'm noob).
I rooted it(not sure it sucess or not) and downloaded go launcher ex.apk from my computer then threw to my kindle. When I choosed to use the launcher, my device was hang. And I cant open my kindle fire until now.
How can I bring my kindle back ? please help me.
sorry for my bad english.
bict
=================================================================================================================
Now,my problem was solved. Thank you every one especally "b63" for the great advice.

a better description would be needed to help you
what exactly have you done ?
what is the status of your kf ? black/kindle fire logo/animated or not
a first shot would be to hold the power button for ~20sec till it turns off and power on again

bicture said:
Hello everyone, Kindle fire is my first android device(i'm noob).
I rooted it(not sure it sucess or not) and downloaded go launcher ex.apk from my computer then threw to my kindle. When I choosed to use the launcher, my device was hang. And I cant open my kindle fire until now.
How can I bring my kindle back ? please help me.
sorry for my bad english.
bict
Click to expand...
Click to collapse
In my first days of own the kindle I did that too XD
if you cheked the box that said use as default then you have to use KFU
(http://forum.xda-developers.com/showthread.php?t=1399889)
select option 1
1. bootmode menu
and then option 3
3. recovery
(español)
utiliza KFU v0.9.2
selecciona la opcion 1 la que dice bootmode menu
presiona enter
luego selecciona la opcion 3 recovery
presiona enter
con esto deberia de poner en modo recovery tu kf, y listo, ahora si solo la instalaste y no le diste el chequesito, presiona el boton de encendido de la kf por 15 seg y debería de funcionar bien, desinstala la aplicacion (go launcher ex)

b63 said:
a better description would be needed to help you
what exactly have you done ?
what is the status of your kf ? black/kindle fire logo/animated or not
a first shot would be to hold the power button for ~20sec till it turns off and power on again
Click to expand...
Click to collapse
Actually,that is
1.root with buritto.
2.try to go on TWRP recovery mode but not sucess(didnt see yellow fire logo) then I'm stop.
3.Try Go launcher ex.When I see it Lag for a long time,i press power off button.Then, I cant open my kindle again. *I see kindle fire logo in my display*
4.I checked on cmd that my device was connecting or not. and it was not.
Thanks for your advice I'll try the first one.

wcastillosalva said:
In my first days of own the kindle I did that too XD
if you cheked the box that said use as default then you have to use KFU
(http://forum.xda-developers.com/showthread.php?t=1399889)
select option 1
1. bootmode menu
and then option 3
3. recovery
(español)
utiliza KFU v0.9.2
selecciona la opcion 1 la que dice bootmode menu
presiona enter
luego selecciona la opcion 3 recovery
presiona enter
con esto deberia de poner en modo recovery tu kf, y listo, ahora si solo la instalaste y no le diste el chequesito, presiona el boton de encendido de la kf por 15 seg y debería de funcionar bien, desinstala la aplicacion (go launcher ex)
Click to expand...
Click to collapse
Thanks for your solution.It makes me belive must have a way to bring my kindle back.
I had done your solution.When I unlocked the sceen ,its in hanging time same as i saw in the first time.It 's a black screen, upper bar have a notification said it have unexpected error. I try to press home and back button but it didnt respond.
What I should do next.
thanks
bict

Factory reset
Sent from my HTC ThunderBolt using XDA App

RevosFTS said:
Factory reset
Sent from my HTC ThunderBolt using XDA App
Click to expand...
Click to collapse
My kindle was hang.I cant do anything on it such as press any button.
Do it have another way to command my kindle to factory reset ?

bicture said:
My kindle was hang.I cant do anything on it such as press any button.
Do it have another way to command my kindle to factory reset ?
Click to expand...
Click to collapse
yes - you could try to communicate with the kf per command line
what do you have available ? kfu or sdk ?
would recommend to download kfu - extract to c:\ and rename to something like "kfu" that it looks c:\kfu - now you can open an (elevated) command prompt
and cd to "c:\kfu\tools" - here you can issue "adb devices" - get a response ?
if yes then you are able to repair or flash a new rom
tell us about and we'll try help further ...

Did you use Kindle Fire Utility?
what said when you try the option 0 Recheck Device Status?

b63 said:
yes - you could try to communicate with the kf per command line
what do you have available ? kfu or sdk ?
would recommend to download kfu - extract to c:\ and rename to something like "kfu" that it looks c:\kfu - now you can open an (elevated) command prompt
and cd to "c:\kfu\tools" - here you can issue "adb devices" - get a response ?
if yes then you are able to repair or flash a new rom
tell us about and we'll try help further ...
Click to expand...
Click to collapse
yes,i used kindle fire utility and my status is online.I'm going to use TWRP to flash the stock rom in it.
Do you have anyway easier ?

please try to answer my questions from post #8 that i can try to help you further
there will be no easier way as flashing a new rom but please use one of the prerooted stock roms
http://forum.xda-developers.com/showthread.php?t=1451747

b63 said:
yes - you could try to communicate with the kf per command line
what do you have available ? kfu or sdk ?
would recommend to download kfu - extract to c:\ and rename to something like "kfu" that it looks c:\kfu - now you can open an (elevated) command prompt
and cd to "c:\kfu\tools" - here you can issue "adb devices" - get a response ?
if yes then you are able to repair or flash a new rom
tell us about and we'll try help further ...
Click to expand...
Click to collapse
Thank you for your advice.
Now,I did follow you and "adb devices" got response.What I should do next ?

given that you don't have fff and twrp availabe (hangs at "kindle fire" logo)
i would recommend to use the following post (i have done it today with him):
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
if your situation is an other one please tell us ...

b63 said:
given that you don't have fff and twrp availabe (hangs at "kindle fire" logo)
i would recommend to use the following post (i have done it today with him):
http://forum.xda-developers.com/showpost.php?p=21803658&postcount=29
if your situation is an other one please tell us ...
Click to expand...
Click to collapse
Thanks for the solution.But I've done something wrong,I done step 4,5 before step 2,3(my confusing).
now when I used "adb devices" it said "List of devices attached 3Axxxxxxxxx device"
and when I used command in step3 it said "<waiting for the device>".
How can I solve it ?
Thx for take care a newbie like me.I'm very appreciate that.

nothing could be happened
point 4 - if you downloaded the file first ->ok
point 5 - the command could not work cause you'r still not in fastboot - right ?
just start from beginning and skip point 4 cause you allready downloaded the file
good luck !

b63 said:
nothing could be happened
point 4 - if you downloaded the file first ->ok
point 5 - the command could not work cause you'r still not in fastboot - right ?
just start from beginning and skip point 4 cause you allready downloaded the file
good luck !
Click to expand...
Click to collapse
now,I finish at 8 step.
I've seen the yellow triangle logo and computer cant find my device.
what I should do next.I dont understand a 9step "click the mount button from the recovery mode".
Where is mount button and where is the recovery mode?
Now,my computer cant connect to the device. Is that ok ?

i assume you are at the yellow triangle and your computer dont recognise the kf - right ?
now you have to update the drivers - the right one is "android adb interface"
then you can resume with point 7 - this will switch the kf to recovery mode (into twrp) - there you will see the mount button

b63 said:
i assume you are at the yellow triangle and your computer dont recognise the kf - right ?
now you have to update the drivers - the right one is "android adb interface"
then you can resume with point 7 - this will switch the kf to recovery mode (into twrp) - there you will see the mount button
Click to expand...
Click to collapse
I went to Device Manager and uninstall the old driver and try to install it again.
I did Update Driver Software>Browse My Computer for the software>Let me pick form the list > Browse >I type "C:\kfu\drivers\kindle" ... and it said "The folder you specified doesnt contain a compatible software,make sure it decided to work with 32 bit system."
I never seen this problem before. : (

would mean you selected the wrong driver file - it's android_winusb.inf

b63 said:
would mean you selected the wrong driver file - it's android_winusb.inf
Click to expand...
Click to collapse
I think I choose right file.And now, my computer see kf as "Unknown Device" in the "Universal serial Bus Controller".

Install Magisk on PX6 (Working on Xtrons)

Hello, I have successfully installed Magisk on my Xtrons PQ80UNV. All you need is a smartphone or tablet with Magisk, a PC and a USB A-A cable
- extract the boot.img from the update.zip
- on the smartphone patch the boot.img with magisk ( you find the patched file in the download folder )
- connect the radio on usb 1 with your pc over the USB A-A cable
- Reboot to recovery
- select bootloader
- on pc write "fastboot reboot"
- write "fastboot flash boot magisk_patched.img"
- write "fastboot reboot"
- install magisk manager on the radio
and if all correct, you have working magisk
good luck ^^

Hello! Where do I find downloads to do all this? You can be a little bit more detailed in the steps? ?I want to perform this procedure for my PQ80UNV
Ciao! Dove trovo download per fare tutto cio? Puoi essere un pochino più dettagliato nei passaggi? ?Voglio eseguire questa procedura per il mio PQ80UNV

This worked on my Dasaita Vivid 11. The first time I tried it, I ended up in a boot loop after I restarted from within Magisk. However, following the steps on page 7 got me to a rooted head unit.

my adb-fastboot doesn't recognize my smartphone

Hey guys, I was trying to root my smartphone using magisk, so I downloaded the stock rom and got the boot.img file for magisk to modify, passed the modified file to the computer and put my device in fastboot mode, but adb-fastboot didn't recognize my device even though I installed the google drivers, so I decided to install the manufacturer's own drivers, but it didn't work, I went to several forums and nothing, so please help!

Filkiro said:
Hey guys, I was trying to root my smartphone using magisk, so I downloaded the stock rom and got the boot.img file for magisk to modify, passed the modified file to the computer and put my device in fastboot mode, but adb-fastboot didn't recognize my device even though I installed the google drivers, so I decided to install the manufacturer's own drivers, but it didn't work, I went to several forums and nothing, so please help!
Click to expand...
Click to collapse
Does it show in Device Manager?
Install Moto USB Drivers

sd_shadow said:
Does it show in Device Manager?
Click to expand...
Click to collapse
Yes, when i go into fastboot mode, it pops up "Android adb interface"

Filkiro said:
Yes, when i go into fastboot mode, it pops up "Android adb interface"
Click to expand...
Click to collapse
seems to be a reoccuring problem to us. steps as show:​​1. press the windows key + r at the same time to open the "run" window.​
2. type "devmgmt.msc" and press enter. it should give a device management window in a few seconds.​
3. if the phone is in mtp mode, it will appear under portable devices/mobile devices. right click that and select "update drivers." click on "search drivers in my computer" and then select "allow me to choose from a available drivers list from my computer." scroll down until you see "mtp device" and double click on it. just click on "proceed". if it fails, try it again but with different drivers.​
make sure to have usb depuration on and reboot to fastboot yadda yada badlaldaaa
then update fastboot drivers "device may be on android phone "'''make sure to install motorola drivers or built in fastboot drivers''''' and then proceed

no matter how much you manage to install drivers you will not be able to root your moto e6 play, (BOOTLOADER IMPOSSIBLE TO UNLOCK UNTIL THE MOMENT)
and do not come to say that it is due to drivers or because we are using an incorrect method, etc.
fastboot oem get_unlock_data not working
fastboot oem unlock does not work
fatboot flashing unlock and unlock_critical either
and it does not appear as waiting for device
appears as remote: unknown command
so it is a problem of the bootloader and not the user

G.Kart said:
não importa o quanto você consiga instalar os drivers, você não conseguirá fazer o root no seu moto e6 play, (BOOTLOADER IMPOSSÍVEL DE DESBLOQUEAR ATÉ O MOMENTO)
e não quero dizer que é devido aos drivers ou porque estamos usando um método incorreto, etc.
fastboot oem get_unlock_data não funciona
fastboot oem unlock não funciona
fatboot piscando desbloqueio e desbloqueio_crítico também
e não aparece como aguardando dispositivo
aparece como remoto: comando desconhecido
então é um problema do bootloader e não do usuário
Click to expand...
Click to collapse
Yes, I searched many forums and it really is practically impossible to unlock the bootloader, but I have a question, is it possible to root using the sp flash tool?

Filkiro said:
Yes, I searched many forums and it really is practically impossible to unlock the bootloader, but I have a question, is it possible to root using the sp flash tool?
Click to expand...
Click to collapse
no, AVB2.0 doesn't allow it, unless I manage to get motorola's private key (.pem) to be able to sign a patched boot.img and even GSIs

Question Bricked device?

I tried to flash Evolution X 5.9. I came from the latest Xiaomi.eu stable (12.5.4). Followed the installing instructions (flash via twrp/ format data), but after reboot, i got a "no command" error message. I then tried to flash the original F3 EEA Fastboot Rom downloaded here: https://c.mi.com/oc/miuidownload/detail?guide=2 , unzipped it twice, but when i tried to flash the rom, i got the error message "can not find file flash_all.bat. I can only enter fastboot now. I have no idea what i did wrong. I would be grateful for any help!
Edit: I'm getting another error now: "error:Writing 'crclist'"

sycomantis said:
I tried to flash Evolution X 5.9. I came from the latest Xiaomi.eu stable (12.5.4). Followed the installing instructions (flash via twrp/ format data), but after reboot, i got a "no command" error message. I then tried to flash the original F3 EEA Fastboot Rom downloaded here: https://c.mi.com/oc/miuidownload/detail?guide=2 , unzipped it twice, but when i tried to flash the rom, i got the error message "can not find file flash_all.bat. I can only enter fastboot now. I have no idea what i did wrong. I would be grateful for any help!
Edit: I'm getting another error now: "error:Writing 'crclist'"
Click to expand...
Click to collapse
Don't go any further, it's really easy to fix, I had the same issue yesterday.
Just try this:
- Download the latest TWRP image
- Launch it from RAM: fastboot boot twrp.img
- Now, try to flash whatever you need to!
- Reboot, and the motherboard will be put out of fastboot.
Good luck!

facuarmo said:
Don't go any further, it's really simple to fix, I had the same issue yesterday.
Just try this:
- Download the latest TWRP image
- Launch it from RAM: fastboot boot twrp.img
- Now, try to flash whatever you need to!
- Reboot, and the motherboard will be put out of fastboot.
Good luck!
Click to expand...
Click to collapse
what do you mean by "Launch it from RAM" ? and which TWRP version should I downlaod? I have the "RUN_TWRP Toolkit" which lets me enter TWRP via fastboot and windows10, is that sufficient? Thx!
The thing is, that I cant copy files to the internal storage, thats why i cannot flash a rom via that RUN TWRP Toolkit.

I downloaded the latest [unofficial] TWRP Version 3.5.2_11-0, entered TWRP via cmd, but i do not know how to flash a ROW now, since i can not copy a rom.zip to the internal storage.

I'm in a similar situation. Tried out a few roms and wanted flash back to stock. Something went wrong and now TWRP is gone and I can only boot into fastboot and stock recovery. I can fastboot TWRP, but don't know how to get a rom accessible. I tried MiFlash but that just tells me "flash done" after 5 seconds without actually doing anything. Tried just executing flash_all.bat, but it comes down to this error message:
$fastboot -s devicename getvar product 2>&1 | findstr /r /c:"^product: *alioth" || echo Missmatching image and device
Click to expand...
Click to collapse
I'm trying to flash MiUI 12.5.1 on a POCO F3, so I don't really understand. Any help would be appreciated.

I was in similar situation. Twice.
Solution: fastboot rom.
I successed with Syberia.
FASTBOOT Roms of Syberia are here:
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
Syberia Project (aka Syberia OS) is a custom ROM for many devices that implements various features. This project was designed by our "Syberia Team"…
sourceforge.net
Unpack it.
Enter fastboot mode on phone.
Run install.bat. Wait. Device reboots to system.

That worked, thank you very much! The only other option I found was to remove part of the flash_all.bat, but I didn't really feel comfortable removing something I don't quite unterstand.

ptr21 said:
I was in similar situation. Twice.
Solution: fastboot rom.
I successed with Syberia.
FASTBOOT Roms of Syberia are here:
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
Syberia Project (aka Syberia OS) is a custom ROM for many devices that implements various features. This project was designed by our "Syberia Team"…
sourceforge.net
Unpack it.
Enter fastboot mode on phone.
Run install.bat. Wait. Device reboots to system.
Click to expand...
Click to collapse
Thank you so much!! It worked

ptr21 said:
I was in similar situation. Twice.
Solution: fastboot rom.
I successed with Syberia.
FASTBOOT Roms of Syberia are here:
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
SyberiaOS - Browse /alioth/fastboot at SourceForge.net
Syberia Project (aka Syberia OS) is a custom ROM for many devices that implements various features. This project was designed by our "Syberia Team"…
sourceforge.net
Unpack it.
Enter fastboot mode on phone.
Run install.bat. Wait. Device reboots to system.
Click to expand...
Click to collapse
Hi,
excuse me but I don't know English.
My Poco F3 crashes on MIUI, can I get into Fastboot or start TWRP from Windows powershell.
I downloaded the syberia_alioth-v4.7-20210715-1557-OFFICIAL-fastboot but I didn't understand how to proceed.
Could you please explain me step by step what to do?
Thank you.

pegasoc said:
Hi,
excuse me but I don't know English.
My Poco F3 crashes on MIUI, can I get into Fastboot or start TWRP from Windows powershell.
I downloaded the syberia_alioth-v4.7-20210715-1557-OFFICIAL-fastboot but I didn't understand how to proceed.
Could you please explain me step by step what to do?
Thank you.
Click to expand...
Click to collapse
Unzip syberia fastboot rom to your computer.
Enter fastboot mode on your phone (power+ volume down buttons)
Connect your phone to computer via USB
In unzipped folder of Syberia fastboot rom you find windows command : install ...... .bat
Run it. It will install Syberia rom.
Dont worry if the errors are shown, iust wait, it will reboot to Syberia rom.

ptr21 said:
Decomprimi la rom di syberia fastboot sul tuo computer.
Accedi alla modalità di avvio rapido sul telefono (pulsanti di accensione e riduzione del volume)
Collega il telefono al computer tramite USB
Nella cartella decompressa della rom Syberia fastboot trovi il comando di Windows: install ...... .bat
Eseguirlo. Installerà la rom Syberia.
Non preoccuparti se vengono mostrati gli errori, aspetta, si riavvierà su Syberia rom.
Click to expand...
Click to collapse
WOW WOW WOW WOW!!! Sei un salvavita. Grazie molte!!!
Ciò che è ancora meglio è che dopo aver bloccato POCO F3 stavo solo cercando di installare syberia_alioth-v4.7-20210723-1108-OFFICIAL.
Presumo che Syberia fastboot non sia aggiornato come syberia_alioth-v4.7-20210723-1108-OFFICIAL, per aggiornare devo installare TWRP e poi
Riavvia in TWRP
Vai su "Installa" -> scegli ROM.zipper (assicurati di aver selezionato "Inietta TWRP dopo l'installazione")
Riavvia -> ripristino
Vai su "Installa" -> scegli Gapps.zipper (Magisk, Gapps-Addons opzionali ecc.) (assicurati che NON SELEZIONATO "Inietta TWRP dopo l'installazione")
Riavvia -> Sistema
Destra?

Question Dm-Verity corruption

Hi everyone, i have the dm verity corruption on my xiaomi 11 t, it is my main phone so i need to fix it, i wanted to unlock the bootloader, but i have family link that blocks that option, so i booted it into fastboot and typed:fastboot reboot fastboot, as said from the guide, but then the phone rebooted in fastbootd, i didnt know what that was and i typed fastboot reboot and it showed the DM verity error. Is there any way to fix it?

Nixk 2 said:
Hola a todos, tengo la corrupción de dm verity en mi xiaomi 11 t, es mi teléfono principal, así que necesito arreglarlo, quería desbloquear el gestor de arranque, pero tengo un vínculo familiar que bloquea esa opción, así que lo inicié en fastboot y escribí: fastboot reboot fastboot, como se dice en la guía, pero luego el teléfono se reinició en fastbootd, no sabía qué era eso y escribí fastboot reboot y mostró el error de verdad de DM. Hay alguna manera de arreglarlo?
Click to expand...
Click to collapse
I know how to fix it, it happened to me recently too
se como arreglarlo me paso hace poco tambien

I found the solution, at this point I assume you have abd and fastboot drivers installed so:
1.- fastboot devices
2.- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.-fastboot reboot

felixpaz1992 said:
I found the solution, at this point I assume you have abd and fastboot drivers installed so:
1.- fastboot devices
2.- fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
3.-fastboot reboot
Click to expand...
Click to collapse
i tried it but the phone got into bootloop
i have to do one more step

Extract the IMG file and in the last part of the fastboot command drag the extracted file in place of the vbmeta.img

felixpaz1992 said:
Extract the IMG file and in the last part of the fastboot command drag the extracted file in place of the vbmeta.img
Click to expand...
Click to collapse
Is this the nulled vbmeta.img?

felixpaz1992 said:
Extract the IMG file and in the last part of the fastboot command drag the extracted file in place of the vbmeta.img
Click to expand...
Click to collapse
do i have to wipe data or no
i still have the same issue can anyone help me still bootloop
but i want to try nippon gsi but can't because of stupid vbmeta man :-'(
can't even acsess recovery only fastboot man please help

Look with these 2 programs I instantly recovered my bricked cell phone, it even allows you to downgrade if you wish, both are free
The one that says TFT allows me to flash the complete ROM, but the bootloader will block you again, the second one that says MTK Meta Utility is used to unlock the bootloader without having to go through xiaomi

Nixk 2 said:
so i booted it into fastboot and typed:fastboot reboot fastboot, as said from the guide
Click to expand...
Click to collapse
What guide? And yes, this command boots into fastbootd mode. That's not more than a binary in your recovery and won't brick your device when it gets executed. Also a reboot from fastbootd won't brick it.
To avoid serious damage on your OS and your device, you shuld try to flash a complete firmware.

BTW: your device is in "Red state".
Boot Flow | Android Open Source Project
source.android.com

WoKoschekk said:
What guide? And yes, this command boots into fastbootd mode. That's not more than a binary in your recovery and won't brick your device when it gets executed. Also a reboot from fastbootd won't brick it.
To avoid serious damage on your OS and your device, you shuld try to flash a complete firmware.
Click to expand...
Click to collapse
I dont know, maybe i flashed something? because the device said not allowed in locked state, but i couldnt do fastboot oem unlock, i needed to enter the os, btw thanks yall for the collaboration, the phone is booting, but it is in unlocked state, i gived the phone in a repair centre to lock the bootloader. Thanks again.

your device is locked in family link. it's a brick. service center can help flashing ROM. MTK - Auth Bypass (SLA/DAA) could maybe work too (at least chipset is supported)
It's now easy to bypass MediaTek's SP Flash Tool authentication
A group of developers has created a Python utility to bypass the authentication routine of MediaTek SP Flash Tool. Check it out now!
www.xda-developers.com