i have just flashed a new recovery, and everything is just fine until i typed this:
fastboot reboot
and it does not reboot fastboot,stucks on first screen but!
pull out battery and entering by hardware key works, all fastboot, bootloader, my ROM, the new recovery.
so that confuses me, i can enter manually, but by adb i cant?
ADB works at the Bootloader and Recovery.
Fastboot works at the Fastboot mode.
Fastboot != ADB
Different commands, different purpose.
If you need reboot to fastboot command is:
"fastboot reboot-bootloader"
"fastboot reboot" just reboots your phone.
Related
Ok I can use commands VIA fastboot when the phone is on. The problem is using commands when the phone is in bootloader. It says "fastboot usb" But when i am trying to use commands like :adb reboot" i get a " device not found " error
The device is Eng s off and ship s off
Tryed this with 3 computers with no luck
I have all the needed drivers.
And using commands in bootloader worked before.
you cannot use adb commads while in fastboot, not will your device show up with the "adb devices" command, you can only issue fastboot commands. so to reboot you must use the command "fastboot reboot" and to show your device you can use the command "fastboot devices"
AndroHero said:
you cannot use adb commads while in fastboot, not will your device show up with the "adb devices" command, you can only issue fastboot commands. so to reboot you must use the command "fastboot reboot" and to show your device you can use the command "fastboot devices"
Click to expand...
Click to collapse
K thnx .
One more thing
I have SU on (#) and i cant even use commands in terminal .. tried reboot command : not permited
primpower said:
K thnx .
One more thing
I have SU on (#) and i cant even use commands in terminal .. tried reboot command : not permited
Click to expand...
Click to collapse
are you using leedroid's rom? i had the same problem, when i used his rom, some of the permissions in /system/bin/ are wrong on his rom, they are rwsr-xr-x and they should be set to rwxr-xr-x, try using adb
AndroHero said:
are you using leedroid's rom? i had the same problem, when i used his rom, some of the permissions in /system/bin/ are wrong on his rom, they are rwsr-xr-x and they should be set to rwxr-xr-x, try using adb
Click to expand...
Click to collapse
I was using Leedroid, i f**** up and installed multiple .zip at once.... first "leedroidRom.zip" and then "theme" without rebooting between.
After that it stopped working ( I think )
I then wiped everything and installed Android Revolution 2.0.12..
"Terminal"
# Reboot
not permited!
About the question i asked earlier. So its not possible to use adb commands trough fastboot. only fastboot commands.
so i have to use : "fastboot flash" and "fastboot push" to execute commands ?
you cannot use the push command while in fastboot for the same reason you cannot use ADB commands, because at that moment android is not booted, you can use adb commands from recovery though
here are the fastboot commands i know of:
fastboot devices - fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - Dont think this works with the DHD
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image
Hi, I am trying to Re-Lock my Galaxy Nexus GSM version, I've downloaded the SDK files (adb-mac and fastboot-mac) and all the image files and I am trying to execute the following commands:
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
fastboot reboot-bootloader
fastboot oem lock
With the phone in normal mode I connect the USB cable to the computer, start Terminal windows and run the first command, "./adb-mac reboot bootloader" and the phone will boot into the "Fastboot Mode", then I try to execute "./fastboot-mac devices" to make sure the phone is connected and properly detected and I get nothing.
If I try to execute "./fastboot-mac flash bootloader bootloader-toro-primekk15.img" I get the message <waiting for device> and it will stay there forever.
Do you know what might be the problem ?, is there other method to do this ?, go back to Stock ROM and Re-Lock the device ?, thanks
You must also install the Samsung usb drivers. I have no idea how to do this in mac. A simple search will help you tho.
Been an incredibly bad week for me as far as technology is concerned. Everything around me seems to be breaking apart form my new One X. That is of course.. until now..
I'm trying to flash TripNDroid's CM10 Rom to my phone by following my self written instructions that have worked like a charm for me so far.
Enter Fastboot on phone. Open the command line window in the relevant place in windows and check it's connected using 'fastboot devices' command. Then:
fastboot erase boot
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase webtop
fastboot erase preinstall
fastboot erase recovery
fastboot flash recovery-clockwork-touch-5.8.4.0-endeavoru.img
fastboot flash boot boot.img
Enter recovery and flash the ROM.
However, I'm getting mixed responses in the command line. Very occasionally I will type a command in and it will accept it. and say 'Done' but 90% of the time it will say 'FAILED (remote: 0000004)' or occasionally 'remote: not allowed'
I have checked that the usb is connected (it is the original cable) and used the fastboot devices command to confirm this. I have tried rebooting the bootloader and redownloading fastboot and the files to be flashed. Completely stuck D:
So I've been working on trying to flash CM on my Fire 2 (I'm fairly experienced with flashing). I managed to get 10.5.1 rooted with SuperSU installed, and then I followed the directions here (https://wiki.cyanogenmod.org/w/Install_CM_for_otter2) to install CM. I made sure to verify the MD5 checksums on the files, and executed the fastboot commands successfully (I don't have a factory cable, I used the ADB commands after gaining root to get into fastboot).
When I executed "fastboot -i 0x1949 oem recovery", it gave me the blue Kindle Fire boot screen, and booted normally into the OS. I loaded the CM/Gapps zips into the storage partition, and then did "adb reboot recovery". It rebooted, showed the orange stock Kindle Fire screen, then this grey triangle screen and proceeds no further. I tried rebooting multiple times, nothing. Device doesn't show up in my device manager, nothing in fastboot or ADB.
View attachment 3621153
So what can I do? I read that as long as something shows up, it's not irreversibly bricked....Or do I need that dang factory cable....
Thanks!
Turn off the kindle completely (hold the power button for about 10 seconds). Open up a command prompt, type fastboot -i 0x1949 getvar product, and plug in the kindle when you see <waiting for device>. If your device boots into fastboot, and you get a string like "otter2-xxx-xx", then you should reflash the files like told to in the CM guide. However, before you type the "fastboot -i 0x1949 oem recovery" command, issue fastboot -i 0x1949 erase system, fastboot -i 0x1949 erase cache, and fastboot -i 0x1949 erase userdata. After that, I think you shouldn't have any issue flashing.
Hi there,
I've got a problem with my Moto Z Play. It is unlocked with lastest unofficial TWRP, bootloader unlocked and running lastest Lineage OS ROM.
I already checked these type of threads:
https://forum.xda-developers.com/moto-z-play/help/booting-recovery-automatically-t3654698$
which gives a solution (doing some fastboot commands) but it doesn't work for me.
So I tried to do this in fastboot mode
" adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot "
But it didn't change anything. I need to boot on fastboot mode and then push power button while selecting start to get it runs on ROM.
Is anyone has a solution?
paknex said:
Hi there,
I've got a problem with my Moto Z Play. It is unlocked with lastest unofficial TWRP, bootloader unlocked and running lastest Lineage OS ROM.
I already checked these type of threads:
https://forum.xda-developers.com/moto-z-play/help/booting-recovery-automatically-t3654698$
which gives a solution (doing some fastboot commands) but it doesn't work for me.
So I tried to do this in fastboot mode
" adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot "
But it didn't change anything. I need to boot on fastboot mode and then push power button while selecting start to get it runs on ROM.
Is anyone has a solution?
Click to expand...
Click to collapse
I faced the same issue ... Tried many things but simple solution worked like a charm
Flash twrp ... Re boot phone ... Don't boot to system instead boot to recovery ..then shutdown from recovery ... That's it twrp is permeant and phone boots to system normally
Tried this but still boots to recovery. Thanks for the idea.