Hi,
I'm using moto g4 plus xt1643 with RR Custom ROM.
When i restart/Power ON/OFF my device it automatically goes into fast boot mode every time. at that time i have to press start for booting my device. Every time doing this task is getting irritation. Kindly anyone help me to fix this
Except this issue my device is working smoothly.
Thanks in advance.
Kind Regards
Kranthi Kanapala.
What happens if you connect your phone to your PC whilst in fastboot mode, open ADB (and use the command 'fastboot devices' to check if your device is detected), and in ADB run the command 'fastboot oem fb_mode_clear' (without quotation marks)? This command, as I understand it, should clear fastboot mode and permit you to boot properly.
echo92 said:
What happens if you connect your phone to your PC whilst in fastboot mode, open ADB (and use the command 'fastboot devices' to check if your device is detected), and in ADB run the command 'fastboot oem fb_mode_clear' (without quotation marks)? This command, as I understand it, should clear fastboot mode and permit you to boot properly.
Click to expand...
Click to collapse
Thanks you friend.... Its working
Related
I tried to root my kindle through, http://forum.xda-developers.com/showthread.php?p=24128777 , but I got half way and got stuck at the fastboot mode. I don't have recovery or anything because it was a stock 6.3 kindle fire. Does anybody know how to get out of this? The adb isn't recognizing my device right now and I've tried hard resetting.
Any help would be appreciated!
Edit: Is the only way out of this is through a factory cable?
what means got half way ?
you switch to fastboot at a point - then adb commands are not recognized
only fastboot commands are recognized in fastboot mode
would try to issue:
fastboot -i 0x1949 getvar product - it should return "kindle"
if not check your drivers
if you got the drivers working resume with the above manual
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Oh. Is that it? . So is it normal for the cmd command "adb devices" to not show the kindle device?
If so, that's a pretty big relief! And all I need to do is type that cmd?
you have a great manual here explaining how the kf works:
http://forum.xda-developers.com/showthread.php?t=1552547
furthermore this one could help you to understand how drivers/bootmode/commands correlate:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
I'm having a similar problem. I can boot into fastmode but when I try to reboot, it just seems to hang with a <waiting for device> message. I get the same <waiting for device> message if I do the fastboot -i 0x1949 getvar product command.
I am stuck in TWRP and if I hit reboot, the command prompt does return the info.
OK, it appears that the KF didn't update. It was just stuck in some weird boot loop or something. Maybe it was trying to update and couldn't for some reason? I am keeping all this info bookmarked in case something does happen though.
hi,
trying to flash the breadcrust recovery using my linux pc, but the Z1 doesn't appear in the list of devices when running adb devices. Image attached. Normally I would get a request to accept the RSA key for a trusted pc when enabling usb debug. But I don't get this option.
- Adb tools are loaded and working on my linux laptop
- My nexus 7 responds to ADB devices and shows up ok
- tried on wifes windows laptop with adb/sdk tools loaded and no joy there too
- i have developer USB debug options enabled, i've tripple checked this
could it be the cable? I'm using the one which came with the phone, so that should be ok?!!
cheers
SOLUTION - I ran this One Plus Two script modified with the Z1 device ID and now I can see my device in adb devices and interact with it. I get the SHA screen to allow access and can run commands from linux terminal. YAY!
See the attachments for script.
I think it´s a driver fault. Did u install them in windows?
im using linux, i dont get any rsa pop up confirmation either!
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
and that was the reason, why i installed windows last night. as long you dont get rsa pop up, the device will not listed (i think so)
EggZenBeanz said:
im using linux, i dont get any rsa pop up confirmation either!
Click to expand...
Click to collapse
But u said, that u tried ur wifes Windows notebook. Did u install the drivers there?
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
MKKLR21 said:
ADB doesn't work for me, too. I work around this problem by booting into recovery (simultaneously press Vol+ and Vol- and Power until phone vibrates) and choose "Boot to bootloader" from there. After rooting I installed "Power Toggles" from Play Store and use the toggle to reboot to recovery or bootloader.
By the way, when I boot into recovery, I'm able to ADB sideload. So I don't think there's a driver issue.
Click to expand...
Click to collapse
Good tip - I'll give it a go.
My nexus 7 works as expected on all PCs and laptops Linux/windows so it must be the phone
Sent from my Nexus 7 using Tapatalk
Maybe sudo or check this:
http://1.bp.blogspot.com/-rDdBnJTh870/U-hxVzxMf3I/AAAAAAAAKwQ/WrZkaMjaReo/s1600/Unlock-Bootloader-linux-terminal-xperia-z.png[img/]
Source: [url]http://linuxwelt.blogspot.de/2014/08/cyanogenmod-unter-linux-installieren.html[/url]
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader, but the device doesn't boot into fastboot, just reboots as normal!
I could also hold down up/down volume buttons and get into the bootloader, but again the device isn't picked by any fastboot oem checks for unlocking!!
arrrgh!!!
You'll have to add -i switch followed by the device ID to your fastboot command. I don't have it at hand, so just read the TWRP thread.
ok! Some progress...ish.
running "adb reboot bootloader"command in windows worked when I switched Cyanogen recovery updates off in developer options. The Z1 reboots into bootloader.
Running "fastboot -i 0x2b4c oem get-device-info" returns nothing just "....."
So I tried "fastboot -i 0x2b4c oem unlock" an error returns cannot unlock use command "fastboot -i 0x2b4c oem unlock-go" which works. The phone wipes data and reboots back into OS.
I re-enable the developer options and adb debug. and reboot into bootloader
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
weird!
Your commands are simply wrong, thats why they don´t work.
It is:
fastboot -i 0x2b4c oem device-info
fastboot -i 0x2b4c oem unlock-go
Run "fastboot -i 0x2b4c flash recovery z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img" - some time stats are retunred and OKAY message. But when I boot into recovery it's still the cyanogen stock recovery. not TWRP.
Click to expand...
Click to collapse
Flashing does NOT work on the international version, you have to boot into it directly from fastboot.
fastboot -i 0x2b4c boot z1.twrp.2.8.7.0.By.Breadcrust-UPDATE3.img
Should be correct instead of the flash command.
EggZenBeanz said:
ok some progress.....
got the trusted device RSA screen to appear on my wifes windows pc. i could then run adb devices and see the device.
I could run adb reboot bootloader...
...
Click to expand...
Click to collapse
What made the change? I was able to see the RSA screen only once, but after device restored to defaults I can't get it back. same drivers installed, and it appears in the device manager.
I honestly don't know, it just worked after many attempts. I read somewhere about USB 3 ports with Linux so might be the same for windows?
Sent from my Z1 using Tapatalk
It's an USB 3.0 issue. Plug the phone into an USB 2.0 port, or an USB 2.0 hub plugged into an USB 3.0 port and it will magically start working. God knows why this is the case...
Ironically, fastboot works fine even on USB 3.0...
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Planet X said:
For to be able to boot (not flash) the TWRP recovery you shouldn't need to unlock bootloader. Am I right?
Click to expand...
Click to collapse
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
MrColdbird said:
Booting should work.
At least it worked fine on other fastboot capable devices I've had in the past.
Click to expand...
Click to collapse
Okay, I have found out that it is impossible to boot from TWRP as log as the bootloader is locked. It just took me 2 hours to setup my phone again after unlock.
Have a look at this thread, I am going to give it a try later.
http://forum.xda-developers.com/showthread.php?t=2408802
This did the trick on Linux (Ubuntu):
- run on terminal "sudo gedit ~/.android/adb_usb.ini"
- put "0x2b4c" in
- run on terminal "adb kill-server" and "adb start-server"
And run the fastboot commands with "sudo".
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
It sounds like you may not have the latest drivers for the Android SDK or ADB toolkit.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
When you are in bootloader, you can use fastboot commands.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
JustPlayingHard said:
When you are in bootloader, you can use fastboot commands.
Click to expand...
Click to collapse
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
RonaldusMagnus said:
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
Click to expand...
Click to collapse
It's not adb fastboot.. It's just fastboot.
teh roxxorz said:
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
Click to expand...
Click to collapse
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
RonaldusMagnus said:
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
JustPlayingHard said:
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
Click to expand...
Click to collapse
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
No worries, it's probably me that's being dense.
That should work fine
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
or plug your phone in (while its booted normally, into its OS)
type: adb reboot bootloader
once phone reboots to bootloader, type: fastboot devices
He must have came from a HTC bc he's looking for the option Fastboot in Bootloader.
Sent from my Nexus 6P using Tapatalk
Thanks for your help everyone. I'm back up and running now. My problems stemmed from a misunderstanding that once in the bootloader I'm already able to execute fastboot commands and didn't need to select a fastboot option from the bootloader. And I had a misunderstood how to execute the fastboot commands from the command prompt.
Many thanks to everyone setting me straight!
I can't get into fast boot mode on my US996. Adb connects just fine and shows the device with "adb devices" command.
However, fastboot command just sits there with a "waiting for device" message, until I CTRL-C out of it.
What can I be doing wrong??
boowho said:
I can't get into fast boot mode on my US996. Adb connects just fine and shows the device with "adb devices" command.
However, fastboot command just sits there with a "waiting for device" message, until I CTRL-C out of it.
What can I be doing wrong??
Click to expand...
Click to collapse
Boot to download mode
https://www.google.com/search?clien...131j0i20i263j46j0i10j5j0i22i10i30.fLpw7AGOyvs
Sent from my PH-1 using Tapatalk
thanks that worked!!
Post moved to another forum and was told it really belongs here; so I'm putting it back:
I've read a ton of threads on the problem of TWRP failing flash, but no help. Maybe I've missed something??
Enter FB mode on the phone and then on PC I Issue "fastboot flash twrp.img", the DOS window reports everything OK; I pull the battery but in no way can I get into TWRP it just boots regularly no matter what buttons I hold down in any sequence.
studied the thread attached intently, but no help. My phone is a US996 (unbranded) and I unlocked it (successfully) via LG's procedure.
Ideas, anyone??
https://forum.xda-developers.com/v20...overy-t3603760
Boowho??
P.S. Anyone have the stock boot image for this phone? Magisk needs it to patch and then flash. I've been unable to find it and yes, I have searched this forum
Last week i received a notification the 8.1 Oreo update was available for my Moto g4 Plus.
Downloaded the package and hit the install button. My moto restarted in order to perform the installation.
However, since i had TWRP installed and thus bootloader unlocked, the phone restarted in recovery mode.
Downloaded a TWRP 8.1 rom and installed it without a problem.
Unfotunately everytime I restart my Moto it starts up in fastboot mode.
Bootloader log shows: Fastboot Reason: reboot mode set to fastboot
From bootloader I can start the Android OS, but i wan't to get rid of this reboot mode
I tried tools like "Android Multi Tool" and "Free ReiBoot for Android" but this reboot mode can not be cleared.
Anyone encountered this problem and how did you fix it.
Thanks in advance
Try this:
Reboot your device to the bootloader.
Connect your device to your computer and open an ADB terminal on your computer.
In the ADB terminal, type 'fastboot devices' without quotes. Press Enter - your device should respond with its serial number.
If so, then type 'fastboot oem fb_mode_clear' without quotes. Press Enter, then reboot your device.
That fb_mode_clear command seems to clear a flag that keeps your device booting into fastboot (usually for OTA updates).
I have Tried that option as i found it as one of the possible solutions for this issue.
the clear_fb unfortunately does not remove the fastboot mode on my moto.
mbodewes said:
I have Tried that option as i found it as one of the possible solutions for this issue.
the clear_fb unfortunately does not remove the fastboot mode on my moto.
Click to expand...
Click to collapse
Alright, though this is for solving TWRP bootloops, might be useful for you https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
echo92 said:
Alright, though this is for solving TWRP bootloops, might be useful for you https://forum.xda-developers.com/moto-g4/help/troubleshooting-twrp-boot-loop-ota-t3714325
Click to expand...
Click to collapse
echo92. Thanks. Works like a charm. Issue fixed.