I was trying to follow the advice here: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 but I must have missed a step, and now I can't even fastboot anything.
Previous Status:
I could run
Code:
adb devices
and
Code:
fastboot devices
fine. My computer was able to detect my OPO. When I
Code:
fastboot oem device-info
it says my phone is tampered with, and unlockedied.
What I did:
I rebooted my phone to fastboot mode by turning it off, then holding volume down + power button. It went into a menu, in which I selected reboot into fastboot mode.
Once in fastboot mode, and connected to my computer,
Code:
fastboot devices
shows my device. Then I ran
Code:
fastboot boot twrp-3.0.2-0-bacon.img
(the img was downloaded from https://dl.twrp.me/bacon/) which at this point I assumed was a mistake. My terminal said it was successful, but then running
Code:
fastboot devices
shows nothing.
Current Status:
Even in fastboot mode, my device is not detected. Booting up normally is successful, and I can access my files and apps. When booted up normally, running
Code:
adb devices
detects nothing. In fact, MTP and other USB connections has no affect on the OPO. The OPO would indicate that it is charging, but not indicating that it is actually connected to a computer.
My Conclusion:
Running
Code:
fastboot boot twrp-3.0.2-0-bacon.img
messed up my device in which it wouldn't communicate with my computer anymore. I don't know how to fix that though. In fact, I don't even know if that was the case, and I don't know how to fix this at all. Any help would be appreciate.
joeyism said:
I was trying to follow the advice here: http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 but I must have missed a step, and now I can't even fastboot anything.
Previous Status:
I could run
Code:
adb devices
and
Code:
fastboot devices
fine. My computer was able to detect my OPO. When I
Code:
fastboot oem device-info
it says my phone is tampered with, and unlockedied.
What I did:
I rebooted my phone to fastboot mode by turning it off, then holding volume down + power button. It went into a menu, in which I selected reboot into fastboot mode.
Once in fastboot mode, and connected to my computer,
Code:
fastboot devices
shows my device. Then I ran
Code:
fastboot boot twrp-3.0.2-0-bacon.img
(the img was downloaded from https://dl.twrp.me/bacon/) which at this point I assumed was a mistake. My terminal said it was successful, but then running
Code:
fastboot devices
shows nothing.
Current Status:
Even in fastboot mode, my device is not detected. Booting up normally is successful, and I can access my files and apps. When booted up normally, running
Code:
adb devices
detects nothing. In fact, MTP and other USB connections has no affect on the OPO. The OPO would indicate that it is charging, but not indicating that it is actually connected to a computer.
My Conclusion:
Running
Code:
fastboot boot twrp-3.0.2-0-bacon.img
messed up my device in which it wouldn't communicate with my computer anymore. I don't know how to fix that though. In fact, I don't even know if that was the case, and I don't know how to fix this at all. Any help would be appreciate.
Click to expand...
Click to collapse
Why were you booting TWRP? Were you trying to flash it? Normally its
fastboot flash recovery twrp-3.0.2-0-bacon.img
Sent from my A0001 using Tapatalk
Renosh said:
Why were you booting TWRP? Were you trying to flash it? Normally its
fastboot flash recovery twrp-3.0.2-0-bacon.img
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Yea I was trying to flash it, but I read from http://forum.xda-developers.com/oneplus-one/development/mod-reset-unlock-tamper-bit-t2820912 that another trick is to do
Code:
fastboot boot <path/name of the recovery twrp img>
So I thought I'd try it. But now my computer can't even detect my phone :/ Would there be a reason why my phone no longer communicates with my computer?
Related
I am trying to unroot and re-lock my xoom and everytime I try to use a fastboot command all I get at the command promt is "waiting for device". I have installed the moto drivers and adb is working fine, just no fastboot. Please help... Thanks in advance!
did you reboot your xoom into bootloader mode? (adb reboot bootloader)
does it show any devices when you type
adb devices
Yes,
adb devices returns the attached device with the serial number.
adb reboot bootloader reboots the device and it say starting fastboot protocol at the top. then when I try to use fastboot flash boot boot.img or any other fastboot command all it does is say waiting for device and that's it..
usb debugging is on? should be if you see the device with adb devices
try to flash another cwm - like rogue version
if you do that - same error?
./adb reboot bootloader
./fastboot flash recovery recoveryroguecwm.img (change real filename )
well, usb-debugging has no effect whatsoever on fastboot.
personally, I suspect a problem outside of the xoom. Have you installed the current motorola drivers using driverhelper? If not, please do so. Please make sure any firewall or anti-virus-software on your computer is disabled or uninstalled.
If you have the possibility, you should try fastboot with another computer.
btw: I'd try if fastboot works with the command fastboot devices. This should return a list of connected and detected devices.
Thanks! For some odd reason my driver needed to be re=installed. After I did that a restarted my computer everything works as it hasin the past!
Hello.
Earlier today I wanted to try a new JB rom to replace ICS so I transfered it into SD card and tried to reboot into recovery.
Instead of getting to recovery, I got stuck in fastboot mode, so I'm assuming recovery has been damaged.
After a whole afternoon of researching this forum I tried for several times this tutorial in order to install a recovery and afterwards a ROM (http://forum.xda-developers.com/showthread.php?t=1088046) and similar ones in both Mac OS X and Windows 7 (tried both USB 2.0 and USB 3.0 so its not a problem from USB) and I didn't succeed at all.
When I am using Windows 7, when I use "fastboot erase recovery", I keep receiving this message "waiting device". If I write "fastboot devices", I don't get results.
When using Mac OS X, I can get via command line to the folder "platform-tools" where fastboot is located but if I write "fastboot erase recovery" or something, it says "command not found". I've read it could be because I have to set fastboot as an environmental variable, but I having trouble setting it (Mac OS Lion).
Thank you so much for reading. Please help me!!! Any clues would be really appreciated!
-----
UPDATE: I finally managed to communicate with the device.
I used the following commands from this tutorial http://androidforums.com/optimus-m-all-things-root/382525-guide-get-out-fastboot-mode-2.html
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot flash recovery
The problem is, now I'm stuck at LG Logo, can't access fastboot... Please help, I think it's even worse now.
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
grigtm said:
boot rom, pull out battery and boot normal, it does or not? if it does use terminal emulator or adb push to install custom recovery, adb will work in fastboot if you had checked android debugging
http://forum.xda-developers.com/showthread.php?t=1007244
http://forum.xda-developers.com/showthread.php?t=1146566
Click to expand...
Click to collapse
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
techdani said:
I don't understand what you mean by boot rom. Every time I turn on the phone, (normal or as POWER+HOME+VOL DOWN) it goes into fastboot. When I pull out the battery, and power again it goes again into fastboot...
Click to expand...
Click to collapse
ok, read here http://forum.xda-developers.com/showthread.php?t=1088046 do exactly what says in this thread
Hey folks,
i have a problem with my shieldtablet. The fastboot doesn't work properly. I cannot load anything via "fastboot flash blablabla.img". Minimal ADB and Fastboot just shows "waiting for device" and if i check the devices via "fastboot devices" is just shows nothing but the normal command prompt.
Then i did a mistake and flashed the twrp 3 version with an older one, so i am unable to enter the recovery-mode. If i chose Recovery Mode via bootloader (or if i restart the tablet into recovery mode) it has a short bootloop and then after some trials it starts normal into Blisspop.
How could i flash this without the fastboot? Is there any trick i could use?
The tablet is unlocked. I had several custom-roms installed. Currently Blisspop 6.4 without playstore.
That looks like your PC is not seeing your tablet. Boot into fastboot mode, connect it to your PC and look in Windows device manager for the device.
Thanks a lot! ADB worked fine on Win10. Last time I flashed the recovery was on my old Win7-System. It seems, that the Upgrade deleted just the fastboot drivers.
One last question: is it normal, that if i chose the fastboot protocoll entry on the bootloader, that it restarts the bootloader?
Yes, that's normal. The menu entry is redundant because when you see it you are in fastboot mode already.
Hi,
I'm trying to boot a twrp image on my Motorola One Vision without flashing it or rooting the phone.
I've unlocked the boot loader and enabled developer options and set USB to debugging. When I connect the phone to the computer and use ./adb devices it is detected fine. When I disconnect, reboot and enable fastboot and when the menu is up connect it to the computer again it will not detect the phone. ./adb devices give no output and ./fastboot boot /PATH/TO/IMAGE.FILE just gives the output "waiting for device". I've tried from both my windows partition and Linux Debian with the same result. Cables are fine as I can use adb to pull files and such- It's basically in the fastboot menu that it doesn't seeem to respond.
The phone is running Android 10 Kane 4.14. I've tried twrp 3.4 but I don't think the image is the issue since it won't respond to commands in fastboot.
Does anyone have any suggestions for troubleshooting this? Any and all help is appreciated.
Kind regards
Magnus
Cardinal_Vice said:
Hi,
I'm trying to boot a twrp image on my Motorola One Vision without flashing it or rooting the phone.
I've unlocked the boot loader and enabled developer options and set USB to debugging. When I connect the phone to the computer and use ./adb devices it is detected fine. When I disconnect, reboot and enable fastboot and when the menu is up connect it to the computer again it will not detect the phone. ./adb devices give no output and ./fastboot boot /PATH/TO/IMAGE.FILE just gives the output "waiting for device". I've tried from both my windows partition and Linux Debian with the same result. Cables are fine as I can use adb to pull files and such- It's basically in the fastboot menu that it doesn't seeem to respond.
The phone is running Android 10 Kane 4.14. I've tried twrp 3.4 but I don't think the image is the issue since it won't respond to commands in fastboot.
Does anyone have any suggestions for troubleshooting this? Any and all help is appreciated.
Kind regards
Magnus
Click to expand...
Click to collapse
If ur phone is detected by adb don't disconnect and hit adb reboot bootloader, it worked for me than when ur in bootloader type:
fastboot flash vbmeta vbmeta_patch.img
fastboot erase userdata
fastboot erase cache (not necessary)
and boot to recovery
My phone is running perfectly fine. But after updating my phone last week officially, my PC doesn't recognize the phone in Fastboot. I'm trying to flash a custom recovery and root it, but in CMD, when I type fastboot devices, nothing comes up.
I am in the Fastboot mode when I try to do this. My phone was rooted earlier too with no issues. Also, in the Fastboot mode, The Bootloader version and the baseband version is blank. I tried different ports and a different cable along with a different PC, nothing seems to help.
Any suggestions?
Hi, did you ever get an answer?
I am having this exact same problem as well. Computer isn't recognizing the device as a fastboot device, I can't even run the fastboot boot recovery.img command to get into recovery.
I was able to get it to recognize my phone in fastboot mode by following the directions in this post: https://forum.xda-developers.com/t/...nize-device-but-adb-can.4040635/post-84052027
Though I never was able to root or install TWRP, this did allow my computer to recognize the phone in fastboot mode.