Related
Hello,
I'm having the infamous Boot Loop issue but with an interesting twist...
I have gotten to the point with command prompt where it is < waiting for device > (I'm trying to use ADB)
And my device is in "FASTBOOT USB" mode
The only issue that is between me and sweet victory is my computer isn't recognizing my device.
When I plug my device into my computer a popup saying that "the connected USB device is not recognized" shows, I know that it isn't the USB or the cord because I was just using this setup about an hour ago to transfer the Rom (Android Revolution HD) to my device.
Any Ideas on a fix for this issue? Hope everything made sense, I tried to add pictures to help explain but the forum wouldn't allow me to.
[Edit]
I am willing to do a hard reset if need be, but I can't get to the options to do so because that is in recovery which I can't access...
Ixolus said:
I have gotten to the point with command prompt where it is < waiting for device > (I'm trying to use ADB)
And my device is in "FASTBOOT USB" mode
Click to expand...
Click to collapse
ADB commands only works from the OS or from custom recovery. In bootloader mode you can only use fastboot commands.
---------- Post added at 03:50 AM ---------- Previous post was at 03:48 AM ----------
Ixolus said:
Hello,
I'm having the infamous Boot Loop issue but with an interesting twist...
Click to expand...
Click to collapse
What recovery did you used to flash the rom? arhd require twrp 2.6.3.3 and up
---------- Post added at 03:52 AM ---------- Previous post was at 03:50 AM ----------
Ixolus said:
Hello,
The only issue that is between me and sweet victory is my computer isn't recognizing my device.
When I plug my device into my computer a popup saying that "the connected USB device is not recognized" shows, I know that it isn't the USB or the cord because I was just using this setup about an hour ago to transfer the Rom (Android Revolution HD) to my device.
Click to expand...
Click to collapse
Looks like you have drivers issues. If you go in windows device manager, when you connect the phone it should says ''My HTC''. If not you'll need to re-install the drivers.
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
2) Q: I'm using Windows 7 what should I worry about
A: when you issue the command "fastboot boot CWM.img" (now only in CWM/TWRP restore method) there's a high chance drivers won't correctly install
{
"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"
}
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
-------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
---------- Post added at 03:54 AM ---------- Previous post was at 03:52 AM ----------
Ixolus said:
Any Ideas on a fix for this issue?
Click to expand...
Click to collapse
fix drivers
flash twrp 2.6.3.3
fastboot erase cache
boot recovery
adb push or sideload the rom
flash the rom again
@alray
ADB commands only works from the OS or from custom recovery. In bootloader mode you can only use fastboot commands.
Click to expand...
Click to collapse
So what commands would I use to install the new recovery?
What recovery did you used to flash the rom? arhd require twrp 2.6.3.3 and up
Click to expand...
Click to collapse
I don't know and I dont know how to find out, but I did have an olderversion of ArHD
Looks like you have drivers issues. If you go in windows device manager, when you connect the phone it should says ''My HTC''. If not you'll need to re-install the drivers.
Click to expand...
Click to collapse
Ive tried a couple times now to re-install my drivers, In Device manager the phone is coming up as "Unknown USB Device (Device Failed Enumeration) I used the highest version with the link you provided and it didn't seem to work... (I have windows 8.1)
Also, sorry for the late reply, had had class.
Ixolus said:
So what commands would I use to install the new recovery?
Click to expand...
Click to collapse
as I said, from bootloader use fastboot commands not adb
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Ixolus said:
Ive tried a couple times now to re-install my drivers, In Device manager the phone is coming up as "Unknown USB Device (Device Failed Enumeration) I used the highest version with the link you provided and it didn't seem to work... (I have windows 8.1)
.
Click to expand...
Click to collapse
If your device is on hboot 1.44, it will not communicate with windows 8.1 in bootloader mode.
reboot in bootloader mode and confirm what is your hboot version. If you are on 1.44 you'll have to either use a windows 7 pc or use a live linux cd.
I had the same problem but I managed, but no way to put another rom, I tried to put the RUU, anyway problem solved thank you.
the solution was to use a PC with Windows 7 and not Windows 8.1, launched from my directory FlashBoot "FlashBoot flash recovery" nom_du_clockwork.img "
then "fastboot erase cache" then "fastboot reboot-bootloader"
recovery finally worked and I restore my backup!
< French >
j'ai eu le même problème mais j'ai réussis, mais pas moyen de mettre une autre rom, je vais essayé de remettre la RUU, en tout cas problème réglé merci.
la solution a été d'utiliser un pc avec Windows 7 et non Windows 8.1, de lancer depuis mon répertoire flashboot "flashboot flash recovery "nom_du_clockwork.img"
ensuite "fastboot erase cache" puis "fastboot reboot-bootloader"
enfin le recovery a marché et j'ai restore ma sauvegarde !
blipn said:
I had the same problem but I managed, but no way to put another rom, I tried to put the RUU, anyway problem solved thank you.
the solution was to use a PC with Windows 7 and not Windows 8.1, launched from my directory FlashBoot "FlashBoot flash recovery" nom_du_clockwork.img "
then "fastboot erase cache" then "fastboot reboot-bootloader"
recovery finally worked and I restore my backup!
< French >
j'ai eu le même problème mais j'ai réussis, mais pas moyen de mettre une autre rom, je vais essayé de remettre la RUU, en tout cas problème réglé merci.
la solution a été d'utiliser un pc avec Windows 7 et non Windows 8.1, de lancer depuis mon répertoire flashboot "flashboot flash recovery "nom_du_clockwork.img"
ensuite "fastboot erase cache" puis "fastboot reboot-bootloader"
enfin le recovery a marché et j'ai restore ma sauvegarde !
Click to expand...
Click to collapse
Yes its better and simpler to use a windows 7 pc. The OP want to flash arhd rom so he will need to flash twrp recovery not cwm.
Btw ''flashboot flash recovery'' or ''flashboot directory'' is incorrect. Its fastboot not flashboot
< French >
Oui c'est vrai que c'est mieuxe et moins compliqué d'utiliser windows 7. L'OP veut installer ARHD et CWM ne fonctionne pas avec les dernières rom ARHD, seulement TWRP 2.6.3.3 et plus récent. En passant, ''flashboot'' ca n'existe pas c'est ''fastboot'' attention de ne pas induire en erreur les autres avec des mauvaise commandes
Thanks guys! wedows 7 fixed it! Means a ton that yall took time out of your day to help out the stupid!
Hi,
today I received my Mi A2. I unlocked developer options and enabled OEM unlock.
Then I rebooted to fastboot via power + vol down and executed
fastboot flashing unlock_critical
as fastboot oem unlock didn't work (command unknown).
I got the bootloader unlock screen and commited by "unlock bootloader" + power button.
Until then the phone booted up. However I wasn't able to boot TWRP-3.2.3-jasmine-20180804.img or a magisk patched_boot.img, both attempts just hung without progress.
Now I'm stuck at the android one logo and nothing happens or at fastboot logo with no device detected.
I suspect it's bad RAM.
anyone else?
{
"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"
}
meltbanana said:
Hi,
today I received my Mi A2. I unlocked developer options and enabled OEM unlock.
Then I rebooted to fastboot via power + vol down and executed
fastboot flashing unlock_critical
as fastboot oem unlock didn't work (command unknown).
I got the bootloader unlock screen and commited by "unlock bootloader" + power button.
Until then the phone booted up. However I wasn't able to boot TWRP-3.2.3-jasmine-20180804.img or a magisk patched_boot.img, both attempts just hung without progress.
Now I'm stuck at the android one logo and nothing happens or at fastboot logo with no device detected.
I suspect it's bad RAM.
anyone else?
Click to expand...
Click to collapse
try with this
http://en.miui.com/download-353.html
https://rmtxpg.db.files.1drv.com/y4...ubZwX8fw6A?width=463&height=739&cropmode=none
tzadkiel2 said:
try with this
http://en.miui.com/download-353.html
https://rmtxpg.db.files.1drv.com/y4...ubZwX8fw6A?width=463&height=739&cropmode=none
Click to expand...
Click to collapse
fastboot doesn't work, it's stuck at "waiting for device" and fastboot devices shows a blank space, though I see the mi bot logo.
I'll return it.
for me every single attempt to flash a file failed though it showed the unlocked logo for the few times it booted.
it even showed random behaviour (fastboot returned unknown command, etc.), took several times for fastboot reboot or did nothing, it's defective.
meltbanana said:
fastboot doesn't work, it's stuck at "waiting for device" and fastboot devices shows a blank space, I'll return it.
for me every attempt to flash a file failed though it showed the unlocked logo for the few times it booted.
Click to expand...
Click to collapse
Change port USB, remove driver's and begin cero.
Si entiendes algo de expañol, elimina los drivers del pc y comienza como si estuvieras comenzando desde cero, cambia de puerto USB y conecta con el teléfono en fastboot se debería de instalar el driver.
Prueba también a Agregar hardware heredado, y ya sea por puertos COM o por otros lados Android Bootloader Interface.
Como yo lo desbloqueé fue con fastboot oem unlock.
Le he dejado en peores condiciones en varias ocasiones no he visto manera de pasar al Sistema después de instalar TWRP, así que me ha tocado recuperarlo en bastantes ocasiones.
tzadkiel2 said:
Change port USB, remove driver's and begin cero.
Si entiendes algo de expañol, elimina los drivers del pc y comienza como si estuvieras comenzando desde cero, cambia de puerto USB y conecta con el teléfono en fastboot se debería de instalar el driver.
Prueba también a Agregar hardware heredado, y ya sea por puertos COM o por otros lados Android Bootloader Interface.
Como yo lo desbloqueé fue con fastboot oem unlock.
Le he dejado en peores condiciones en varias ocasiones no he visto manera de pasar al Sistema después de instalar TWRP, así que me ha tocado recuperarlo en bastantes ocasiones.
Click to expand...
Click to collapse
cannot even reach it under ubuntu via fastboot
it's impossible that I broke it cause I wasn't able to flash a kernel (boot.img) or something else
and I wasn't able to switch a slot: "this device doesn't support slots". when I entered fastboot set_active a it returned
this device only support slots
a
b
it acted as if it was infected with an ART rootkit or had bad memory.
meltbanana said:
cannot even reach it under ubuntu via fastboot
it's impossible that I broke it cause I wasn't able to flash a kernel (boot.img) or something else
and I wasn't able to switch a slot: "this device doesn't support slots". when I entered fastboot set_active a it returned
this device only support slots
a
b
it acted as if it was infected with an ART rootkit or had bad memory.
Click to expand...
Click to collapse
In my case I was trying to flash MIUI 10 the third time then it fails I was using Android One rom September update and it was working flawlessly without any problem.
After miflash tool fails to flash my phone wont be detected either of my PC and Mac
I am thinking using deep flash cable to enter EDL but is it possible for MI A2 hopefully it is because I don't want my phone to be opened, ITS NEW :crying:
Am I still covered by warranty? If not I have to send my phone to repair shop to just enter EDL mode and to be able to flash stock or miui again
About me flashing MIUI I did follow instructions to avoid Anti Rollback (Never flashed MIUI 10 via twrp instead I flash custom roms)
johnsci911 said:
In my case I was trying to flash MIUI 10 the third time then it fails I was using Android One rom September update and it was working flawlessly without any problem.
After miflash tool fails to flash my phone wont be detected either of my PC and Mac
I am thinking using deep flash cable to enter EDL but is it possible for MI A2 hopefully it is because I don't want my phone to be opened, ITS NEW :crying:
Am I still covered by warranty? If not I have to send my phone to repair shop to just enter EDL mode and to be able to flash stock or miui again
About me flashing MIUI I did follow instructions to avoid Anti Rollback (Never flashed MIUI 10 via twrp instead I flash custom roms)
Click to expand...
Click to collapse
Same thing happened with me no fastboot no edl .
Then I flashed my phone using test points method.
And yes you need to open your phone for that.
ARNOB XENON said:
Same thing happened with me no fastboot no edl .
Then I flashed my phone using test points method.
And yes you need to open your phone for that.
Click to expand...
Click to collapse
Then I guess I need to open mine too
Is it guaranteed that the phone will work again?
Have you tried it yourself?
johnsci911 said:
Then I guess I need to open mine too
Is it guaranteed that the phone will work again?
Have you tried it yourself?
Click to expand...
Click to collapse
Yes It will work 100%....Best of luck ..Open it very carefully..Must watch some videos in YouTube how to open Mi A2.
Does it work with deep-cable? Or another option before open it? I prefer return to Amazon than open...
Fix it?
meltbanana said:
Hi,
today I received my Mi A2. I unlocked developer options and enabled OEM unlock.
Then I rebooted to fastboot via power + vol down and executed
fastboot flashing unlock_critical
as fastboot oem unlock didn't work (command unknown).
I got the bootloader unlock screen and commited by "unlock bootloader" + power button.
Until then the phone booted up. However I wasn't able to boot TWRP-3.2.3-jasmine-20180804.img or a magisk patched_boot.img, both attempts just hung without progress.
Now I'm stuck at the android one logo and nothing happens or at fastboot logo with no device detected.
I suspect it's bad RAM.
anyone else?
Click to expand...
Click to collapse
Did you fix ir?
I hace the same issue but Idk how to fix it, Any help?:c
---------- Post added at 03:16 PM ---------- Previous post was at 03:13 PM ----------
tzadkiel2 said:
Change port USB, remove driver's and begin cero.
Si entiendes algo de expañol, elimina los drivers del pc y comienza como si estuvieras comenzando desde cero, cambia de puerto USB y conecta con el teléfono en fastboot se debería de instalar el driver.
Prueba también a Agregar hardware heredado, y ya sea por puertos COM o por otros lados Android Bootloader Interface.
Como yo lo desbloqueé fue con fastboot oem unlock.
Le he dejado en peores condiciones en varias ocasiones no he visto manera de pasar al Sistema después de instalar TWRP, así que me ha tocado recuperarlo en bastantes ocasiones.
Click to expand...
Click to collapse
Yo intenté todo eso, el problema es que ningún PC reconoce el Xiaomi mi A2 aún cuando está en modo fastboot, lo único que sale es esperando dispositivo, no más no lo reconoce.
Did anyone solved this problem?
I've bricked my device and I can get on fastboot mode but the PC won't recognize the device.
I've tried several computers and systems, windows, ubuntu, debian...
Did the deep flash USB cable work?
I have a Moto E4 Plus xt1773, and it's in the infinite loop,
I try to enter into recovery mode and it does not enter,
Bootloader is locked, and the OEM also
I can only get into fastboot mode, can anyone help me?
sorry for the engfish of google
I gave flash in the Wood ROM of the Moto e4 and I just hear the sound of the motorola logo, but the screen turns black, but to hear that it starts,
but when I put my official ROM, it stays in Infinite Loop
Xt1773
My Cell's Rom is Nicklaus, and I tested a WOOD,
Instala la romstock de nicklaus
danyfenton said:
I have a Moto E4 Plus xt1773, and it's in the infinite loop,
I try to enter into recovery mode and it does not enter,
Bootloader is locked, and the OEM also
I can only get into fastboot mode, can anyone help me?
sorry for the engfish of google
Click to expand...
Click to collapse
Buenas noches amigo, instala la rom stock de este dispositivo, lo debes hacer con flastool es muy sencillo.
Saludos.
I need help because I can not get into fastboot mode on my LG Q6 (M700TV).
Preciso de ajuda, pois não consigo entrar no modo fastboot no meu LG Q6 (M700TV)
Alguém, por favor me ajude!!!
good luck bro.
Not available to boot to fastboot yet on lg q6. Even reboot to FFBM mode or shutdown to ship mode in QMMI hidden app doesn't work (just reboots device to system
bootloader
Ranypreto said:
I need help because I can not get into fastboot mode on my LG Q6 (M700TV).
Preciso de ajuda, pois não consigo entrar no modo fastboot no meu LG Q6 (M700TV)
Alguém, por favor me ajude!!!
Click to expand...
Click to collapse
You have to flash an older Firmware. for this you need to boot in Download mode (Volume up and power Key while connecting to the PC) LG disabled the service of some Lg Q6 phones.
hello, I recently flashed MIUI 12.0.1 QJQMIXM on my Redmi 9t with Miflash and it said « flash complete » but the phone boot loop when plugged and if I try to boot it when unplugged it boot once and shut down and if I keep pressing the power button it boot loop. When it’s « booting » it shows me a white screen with blue dots (zoom on the photo). The phone is not recognized by my computer. I need help please
noe.trbt said:
hello, I recently flashed MIUI 12.0.1 QJQMIXM on my Redmi 9t with Miflash and it said « flash complete » but the phone boot loop when plugged and if I try to boot it when unplugged it boot once and shut down and if I keep pressing the power button it boot loop. When it’s « booting » it shows me a white screen with blue dots (zoom on the photo). The phone is not recognized by my computer. I need help please
Click to expand...
Click to collapse
You flashed in fastboot mode with unlocked bootloader or.....
mvikrant97 said:
You flashed in fastboot mode with unlocked bootloader or.....
Click to expand...
Click to collapse
yes, I finally put it into edl mode and i can’t flash any rom it keeps saying « cannot receive hello packet »
noe.trbt said:
yes, I finally put it into edl mode and i can’t flash any rom it keeps saying « cannot receive hello packet »
Click to expand...
Click to collapse
It requires auth flashing in edl mode.
I have access to auth flash your phone using a paid software but don't worry I won't charge it for you.
mvikrant97 said:
It requires auth flashing in edl mode.
I have access to auth flash your phone using a paid software but don't worry I won't charge it for you.
View attachment 5937611
Click to expand...
Click to collapse
oh and I have to do what ?
noe.trbt said:
oh and I have to do what ?
Click to expand...
Click to collapse
Download Teamviewer or Anydesk so that I can remotely restore it.
mvikrant97 said:
Download Teamviewer or Anydesk so that I can remotely restore it.
Click to expand...
Click to collapse
okay I downloaded it
noe.trbt said:
okay I downloaded it
Click to expand...
Click to collapse
Hey please use this tool here to flash your device without auth
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing Modified by Zesuga Features: Free auth bypass (EDL Mobile) No need credit balance or activation Free unlock EDL Auth device and flash Only need to boot the device in EDL mode What's new...
forum.xda-developers.com
Same error....
mvikrant97 said:
Hé, veuillez utiliser cet outil ici pour flasher votre appareil sans autorisation
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing Modified by Zesuga Features: Free auth bypass (EDL Mobile) No need credit balance or activation Free unlock EDL Auth device and flash Only need to boot the device in EDL mode What's new...
forum.xda-developers.com
Click to expand...
Click to collapse
Same error.....
mvikrant97 said:
Hé, veuillez utiliser cet outil ici pour flasher votre appareil sans autorisation
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing
Xiaomi MiFlash Tool 2023.4.14.0 No Auth EDL Flashing Modified by Zesuga Features: Free auth bypass (EDL Mobile) No need credit balance or activation Free unlock EDL Auth device and flash Only need to boot the device in EDL mode What's new...
forum.xda-developers.com
Click to expand...
Click to collapse
It gives me this error now..
noe.trbt said:
View attachment 5938291
It gives me this error now..
Click to expand...
Click to collapse
I will help you out tomorrow using unlock tool as I have already used it up to unlock Samsung phones so I cannot use it on other computer for 12 hours from now.
mvikrant97 said:
Je vous aiderai demain en utilisant l'outil de déverrouillage car je l'ai déjà utilisé pour déverrouiller les téléphones Samsung, je ne peux donc pas l'utiliser sur un autre ordinateur pendant 12 heures à partir de mainte
mvikrant97 said:
Je vous aiderai demain en utilisant l'outil de déverrouillage car je l'ai déjà utilisé pour déverrouiller les téléphones Samsung, je ne peux donc pas l'utiliser sur un autre ordinateur pendant 12 heures à partir de maintenant.
Click to expand...
Click to collapse
ok thx tell me when you can
Click to expand...
Click to collapse
Start from here https://forum.xda-developers.com/t/...ote-9-4g-redmi-9t-redmi-9-power-lime.4263061/
- Can I flash an update of region X if I am using a version of region Y?
No, to switch regions you will have to unlock the bootloader and flash the fastboot ROM of the region you want to switch to.
Are you sure that bootloader is unlocked?
You have tried to flash MIUI firmware of all regions ....based on your pics!
diaconu.silviu said:
Start from here https://forum.xda-developers.com/t/...ote-9-4g-redmi-9t-redmi-9-power-lime.4263061/
- Can I flash an update of region X if I am using a version of region Y?
No, to switch regions you will have to unlock the bootloader and flash the fastboot ROM of the region you want to switch to.
Are you sure that bootloader is unlocked?
You have tried to flash MIUI firmware of all regions ....based on your pics!
Click to expand...
Click to collapse
yes the bootloader is unlocked and I tried to reflash international rom, chinese rom and EEA rom its not working it gives me the hello packets error
mvikrant97 said:
I will help you out tomorrow using unlock tool as I have already used it up to unlock Samsung phones so I cannot use it on other computer for 12 hours from now.
Click to expand...
Click to collapse
you can now ?
noe.trbt said:
you can now ?
Click to expand...
Click to collapse
My internet is not working to setup remote connection.
I would request you to wait for 5 more hours.