Database Info

[Q] Frozen at bootloader, no adb or fastboot

Hello,
I was attempting to clean out (format) everything on my phone and start over with a fresh ROM, and it looks like I went a bit overboard. Now I'm stuck at the bootloader, but it appears to be frozen. When it loads, I get:
Code:
FASTBOOT MODE - NO BOOT OR RECOVERY IMG
PRODUCT NAME - HERRING
HW VERSION - REV 11
BOOTLOADER VERSION - 19020XXLC2
BASEBAND VERSION - 19020XXKI1
CARRIER INFO - TMB
SERIAL NUMBER - (REDACTED)
LOCK STATE - UNLOCKED
The menu appears as well, but I am unable to change the current selection, or perform a selection. (My power button stopped functioning a couple months ago).
Occasionally when I unplug the usb cable I'll see a quick message "USB Control Init USB Control Init End" and it restarts the bootloader. FASTBOOT MODE then just appears empty, and I still cannot access the menu items.
ADB was working before, but now 2 separate computers cannot detect it using "adb devices". I hadn't tried 'fastboot devices' beforehand, but it doesn't detect the phone now.
I tried installing a couple different drivers (Google's, PDANet), and using Wugfresh NRT, but could never connect.
So how's it look, doc? Will it live? Or should I bury it?
Thanks!

Lanik42 said:
So how's it look, doc? Will it live? Or should I bury it?
Click to expand...
Click to collapse
As long as the bootloader isn't deleted there's a good chance.
I think you have deleted the OS and the recovery :silly:
When you are in the bootloader, only fastboot commands work.
Type "fastboot devices" to check the connection
Or "fastboot help"
https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
I had to force the "Google Nexus BootLoader Interface" driver onto the system (win 8.1)
I know it says Acer, but it is my Nexus S
{
"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"
}
When fastboot.exe can see your device you can flash a recovery image.
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
You should now be able to start the recovery and use the adb commands.
Hope some of this can help

Thanks for the response! I wasn't sure if I would even get a reply, as the board appears to be rather quiet.
Lar5 said:
As long as the bootloader isn't deleted there's a good chance.
I think you have deleted the OS and the recovery :silly:
Click to expand...
Click to collapse
Yeah, I'm afraid I did. I got a little overly aggressive in my data purge
Lar5 said:
When you are in the bootloader, only fastboot commands work.
Type "fastboot devices" to check the connection
Or "fastboot help"
Click to expand...
Click to collapse
Sadly, therein lies my problem. I haven't been able to get fastboot to recognize my device, at all
Lar5 said:
I had to force the "Google Nexus BootLoader Interface" driver onto the system (win 8.1)
I know it says Acer, but it is my Nexus S
View attachment 2936108
When fastboot.exe can see your device you can flash a recovery image.
"fastboot flash recovery recovery.img"
"fastboot boot recovery.img"
You should now be able to start the recovery and use the adb commands.
Hope some of this can help
Click to expand...
Click to collapse
I tried the driver install listed, and I assume it successfuly installed, though I'm not sure how I'd check. but I'm still having the same problem. neither fastboot nor adb recognize the device (though as you said, adb wouldn't at this stage either way).
It doesn't appear that it's even showing up in the device manager (using Windows 7 x64). No search for drivers, no unrecognized device, nothing
I'm afraid it means that my phone is actually freezing during the bootloader loading, since the computer does not appear to recognize it and I can't navigate its menu.
Is there anything I'm forgetting? I may try booting into a Linux live image, to see if windows is just ignoring due to some driver issue. Will follow up with those results.
Thanks again!

I suggest removing all drivers. Each and every trace of it to be removed. Then install the Google USB drivers.
You can also get drivers from Windows Update...

Unable to flash TWRP

Yo
currently running newest official (12.1-YOG4PAS1N0).
I unlocked the bootloader-
{
"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"
}
then I put the recovery.img file at the adb path.
then I enter fastboot and typed <fastboot flash recovery recovery.img> and it flashed it.
I disconnected the USB, turned the device off and then immediately booted into recovery (Volume down + Power)... BUT- it takes me to CM stock recovery every time
was wondering if anyone knows what can be done.
CM Recovery update is disabledfrom Dev Options ofcourse.
thanks.

Lidor167 said:
Yo
currently running newest official (12.1-YOG4PAS1N0).
I unlocked the bootloader-
then I put the recovery.img file at the adb path.
then I enter fastboot and typed <fastboot flash recovery recovery.img> and it flashed it.
I disconnected the USB, turned the device off and then immediately booted into recovery (Volume down + Power)... BUT- it takes me to CM stock recovery every time
was wondering if anyone knows what can be done.
CM Recovery update is disabledfrom Dev Options ofcourse.
thanks.
Click to expand...
Click to collapse
Now since this is a straight forward thing you are going to get the basic questions which I suggest you put the exact route you took. was your recovery named recovery.img? Are you sure that its flashing?
Have you tried a toolkit although I agree to try it manually but just as another troubleshooting method.

playya said:
Now since this is a straight forward thing you are going to get the basic questions which I suggest you put the exact route you took. was your recovery named recovery.img? Are you sure that its flashing?
Have you tried a toolkit although I agree to try it manually but just as another troubleshooting method.
Click to expand...
Click to collapse
the recovery is named recovery.img
I tried a toolkit but its too bulky for me

Lidor167 said:
the recovery is named recovery.img
I tried a toolkit but its too bulky for me
Click to expand...
Click to collapse
what do you mean too bulky? did you try the toolkit prior to this or after
Edit: does it show the recovery flash working and being successful?

playya said:
what do you mean too bulky? did you try the toolkit prior to this or after
Edit: does it show the recovery flash working and being successful?
Click to expand...
Click to collapse
prior to this.. says something about not being able to find adb device. but when i open the command prompt and type <fastboot devices> it shows my One. so I gave up on the toolkit

Lidor167 said:
prior to this.. says something about not being able to find adb device. but when i open the command prompt and type <fastboot devices> it shows my One. so I gave up on the toolkit
Click to expand...
Click to collapse
Wugs makes a descent toolkit.. Did you get it fixed

playya said:
Wugs makes a descent toolkit.. Did you get it fixed
Click to expand...
Click to collapse
yeah, appreantly the file name was - recovery.img.img but it didn't show, I had it checked and now it's all good, thanks

Help Moto G stoping in "Warning BootLoader"

Hello guys! I'm on a G 2015 bike to find a way around it. Good tried the procedures without unlocking the bootloader, but without success! Then I went and I was able to unlock Bootloader and repeat the process to install Roo Stock. But to no avail as well. Does anyone have any tips for solving this problem?

I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.

Hi there! I had the same problem, but the solution was just wait. It took a full 5 minutes to boot since the warning appeared, but it worked fine. Give it a try, wait 5 minutes (literally) and see what happens. If it still stuck, then try the solution above.

KrisM22 said:
I would guess it stops in bootloader because it doesn't like the rom you've flashed.
Did you flash TWRP?
Boot to TWRP and clean flash something else.
Else flash TWRP and then do that.
Click to expand...
Click to collapse
Hi. I tried to do the way you said it, but it did not work. Take a look at the picture
I follow this GUIDE for install
https://forum.xda-developers.com/moto-g/general/guide-custom-recovery-moto-g-xt1033-t2972905
{
"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"
}

I don't think your bootloader is unlocked.
Have you unlocked your bootloader using the Motorola site? No other method will work.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
which recovery are you using - copy/paste full module name.

The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.

Jdoria said:
The bootloader has been unlocked by the motorola website! When I insert the cell phone, the message appears that the bootloader is unlocked.
Click to expand...
Click to collapse
"when you insert the cell phone" into what?
EDITED POST FOR WINDOWS:
for windows I think type cmd in search bar, right click on cmd.exe and choose administrative (you may have to enter a password) and do everything in that window.
fastboot flash recovery twrp.img
but first tell me exactly which twrp you are using - one is bad.
Better than that just grab the latest from squid and use that. I know it's good.
When it flashes successfully, DO IT AGAIN - don't ask why, just do it - same command.
THEN boot to TWRP and backup your stock if you still have one.
Then and only then, wipe and flash whatever your heart desires.

@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.

acejavelin said:
@Jdoria Please attach the output of "fastboot getvar all"
@KrisM22 "sudo" wont do anything, this is WINDOWS, not Linux.
Click to expand...
Click to collapse
Yeah I put a note at the bottom of that post for that. My bad.

Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?

Jdoria said:
Hi I ran cmd.exe in managed mode. Is there any method to format the data of the phone and install everything from scratch?
Click to expand...
Click to collapse
You need to run it in administrative mode.

[twrp] [v3. 3.1] [micromax infinity n12] [treble recovery] Micromax Infinity n12 TWRP

{
"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"
}
Long wait over! Finally working TWRP for Micromax Infinity N12
- Full Treble Support
-Capability to flash all GSI
-ADB fully working
- Latest version 3.1.1
- MTP
- Encryption ( can be fixed but causes problems like battery drain)
-This image didn't boot for some people. This is due to the some vendor patches from an OTA update. To install TWRP just install the stock firmware and follow the steps below. (just don't allow the phone to install the OTA update or else the vendor patches will come back)
- Install stock rom before flashing TWRP.
- Enable OEM Unlocking
- Type the following commands
fastboot oem unlock
fastboot flash recovery recovery.img
fastboot reboot
recovery.img
drive.google.com
https://androidfilehost.com/?fid=8889791610682881821 stock firmware
@lopestom for the base TWRP that I ported

Works well, just encryption needs to be done
Good job. There has been no development for this device. Thanks to you l could install Android 10 gsi!

Thanks for your reply
If you like the recovery that I ported please click the thanks button, this is my first post

SOLVED
JOSHUA....... said:
Good job. There has been no development for this device. Thanks to you l could install Android 10 gsi!
Click to expand...
Click to collapse
Encryption ploblem is solved please check out

After flashing twrp, phone not booting into twrp. What will be the reason?
Fixed

Voolyo said:
After flashing twrp, phone not booting into twrp. What will be the reason?
Fixed
Click to expand...
Click to collapse
Sorry for the late reply.
Which way did you use to flash twrp? Sp flash tool or fastboot mode? If you used fastboot use it in the exact same way
Fastboot oem unlock
Fastboot flash recovery recovery.img
Fastboot reboot
After that don't let the phone reboot. Immidialy after executing the command fastboot reboot, press the power and volume up, and select recovery.
If still not successful, first flash the stock recovery and then the twrp
Edit : oh sorry I didn't see that you fixed it

Tab E said:
Sorry for the late reply.
Which way did you use to flash twrp? Sp flash tool or fastboot mode? If you used fastboot use it in the exact same way
Fastboot oem unlock
Fastboot flash recovery recovery.img
Fastboot reboot
After that don't let the phone reboot. Immidialy after executing the command fastboot reboot, press the power and volume up, and select recovery.
If still not successful, first flash the stock recovery and then the twrp
Edit : oh sorry I didn't see that you fixed it
Click to expand...
Click to collapse
Thanks for the reply .

[solved + how i solved it] the current image(boot/recovery) have been destroyed

so, i was trying to install twrp, but i made a stupid mistake, instead of fastboot flash recovery i did fastboot flash boot, now it tells me: "the current image(boot/recovery) have been destroyed", when i go into bootloader, and attack the cable (both before and after) restarts itself.
things I tried: flash the original boot (it gave "FAILED (Write to device failed (no link))", obviously before the bootloader happened) change usb cable, flash the stock rom (obviously before the bootloader happened)), redownload adb /fastboot drivers, phone drivers, and google drivers. this is all i remember trying to do, i'm desperate, could someone help me please?

update: now i can use bootloader

update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!

Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
try going into the bootloader and re-unlocking it

{
"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"
}
That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo

Angel1104 said:
View attachment 5798249That happened to me when I wanted to block the boot, so I think the boot was blocked and only stayed in the realme recovery like the following photo
Click to expand...
Click to collapse
I don't understand if the recovery works or not, it's a bootloop with locked bootloader and you can go into recovery or locked bootloader without accessing recovery? you are confusing me, however, if you have access to recovery download the stock rom from the recovery, if not, try to unlock the bootloader again by doing fastboot flashing unlock, then flash the stock recovery and then download the stock rom from the recovery

And how do you enter that mode without the application?

enter bootloader and do fastboot reboot recovery, in bootloader you can't perform flashing actions and many other things (bootloader locked) but some things, like reboot should work

in case you get the same error for the recovery you have to unlock the bootloader again

Can I send you a private message?

yes

Did you solve it? I'm facing the same issue.

Gamer_Mida said:
update: I fixed it, in case this situation happened to you, I solved it like this: I had a windows update, while it was doing it, I connected the phone to the pc, in the end it no longer rebooted by itself (the phone) , then do fastboot flash boot (original boot), if it doesn't work, reboot the bootloader , from the bootloader, if it doesn't work, do the same thing downloading the drivers again, then do fastboot flash boot (original boot.img), if you want to download costum recovery, do fastboot flash recovery (costum recovery.img). I fixed it like this, now I have a costum recovery, costum rom and root!
Click to expand...
Click to collapse
I am having trouble understanding what you did exactly. I am getting this same error with a Xiaomi Mi 8 Lite.
Edit: got it working by disconnecting all usb ports and trying another port.

Angel1104 said:
Hello friend, I have a question. I closed the bootloader and when I closed it, the recovery image was destroyed.
Now I can't enter my cell phone and it stays in an infinite boot
any solution with locked bootloader
Click to expand...
Click to collapse
same as me i dont know what to do