I'm working on Mac OS and an Stratos international version and was able after install the ads drivers to show the app List.
I wanted to unlock the boot loader, I'm able to get the watch in Fastboot mode with
MBP-de-Greglatform-tools greg$ ./adb devices
List of devices attached
4e570b25 device
MBP-de-Greglatform-tools greg$ adb shell reboot bootloader
But the next step is not working
MBP-de-Greglatform-tools greg$ ./fastboot getvar all
< waiting for any device >
nothing is happening after that ?
chocorem said:
I'm working on Mac OS and an Stratos international version and was able after install the ads drivers to show the app List.
I wanted to unlock the boot loader, I'm able to get the watch in Fastboot mode with
MBP-de-Greglatform-tools greg$ ./adb devices
List of devices attached
4e570b25 device
MBP-de-Greglatform-tools greg$ adb shell reboot bootloader
But the next step is not working
MBP-de-Greglatform-tools greg$ ./fastboot getvar all
< waiting for any device >
nothing is happening after that ?
Click to expand...
Click to collapse
Your fastboot driver is not working or it is not correctly installed.
I tried on a windows machine and it worked !
Related
I can use adb commands no problem, but with the phone being in fastboot, fastboot commands like
Code:
fastboot devices
don´t show anything.
I want to unlock the bootloader but I am stuck with
Code:
waiting for device
after the
Code:
fastboot flashing unlock
command.
Why is it that every time I try to follow a tutorial, I do the exact same things and it doesn´t work for me?
Anyways, I installed all drivers from here and Device Manager shows an Android ADB Interface with a yellow triangle when I connect my phone in fastboot mode.
I would like to install Android 11 or 10 on wiko wim lite, can you show me how to do it please?
notsmartphone said:
I would like to install Android 11 or 10 on wiko wim lite, can you show me how to do it please?
Click to expand...
Click to collapse
If
OEM unlock
Bootloader unlock
are sucessfully performed, then you flash an update/upgrade of Android OS via ADB
Code:
adb reboot recovery
adb sideload <FIRMWARE.ZIP>
jwoegerbauer said:
If
OEM unlock
Bootloader unlock
are sucessfully performed, then you flash an update/upgrade of Android OS via ADB
Code:
adb reboot recovery
adb sideload <FIRMWARE.ZIP>
Click to expand...
Click to collapse
KarlaPatton said:
I only prefer to use android 10 because of the great features it offers.
Click to expand...
Click to collapse
Thank you Karla and jwoegerbauer
now i can try upgrade to android 10 ,
then I'll try to update it tonight, because this phone need a change ,
if I understand correctly through the developer options I can unlock it , not software need , and then download adb for computer and connect the phone , but I don't have to download anything ? no rom ? does it update automatically ? if you have to upload some files, can you give me the link please there are too many files around the net ? thank you
@notsmartphone
Those are the steps
Find in Internet Android version that's suitable to your phone - FYI: I do NOT search for it - and download it onto PC
In phone's Developer options turn on OEM unlock and USB debugging and re-boot phone
On PC download and install ADB & Fastboot driver matching your phone from OEM's/Carrier's website.
Connect phone and computer by USB-cable what you got with phone.
Check connection
Code:
adb devices
Reboot phone into the bootloader
Code:
adb reboot bootloader
Check you can connect
Code:
fastboot devices
Unlock Android's bootloader
Code:
fastboot oem unlock
Reboot phone
Code:
fastboot reboot
Check unlock status
Code:
fastboot unlock-info
Reboot phone
Code:
fastboot reboot
Check connection
Code:
adb devices
Flash the downloaded Android firmware
Code:
adb sideload <FIRMWARE.ZIP>
Reboot phone
Code:
adb reboot
Happy flashing!
jwoegerbauer said:
If
OEM unlock
Bootloader unlock
are sucessfully performed, then you flash an update/upgrade of Android OS via ADB
Code:
adb reboot recovery
adb sideload <FIRMWARE.ZIP>
Click to expand...
Click to collapse
jwoegerbauer said:
@notsmartphone
Those are the steps
Find in Internet Android version that's suitable to your phone - FYI: I do NOT search for it - and download it onto PC
In phone's Developer options turn on OEM unlock and USB debugging and re-boot phone
On PC download and install ADB & Fastboot driver matching your phone from OEM's/Carrier's website.
Connect phone and computer by USB-cable what you got with phone.
Check connection
Code:
adb devices
Reboot phone into the bootloader
Code:
adb reboot bootloader
Check you can connect
Code:
fastboot devices
Unlock Android's bootloader
Code:
fastboot oem unlock
Reboot phone
Code:
fastboot reboot
Check unlock status
Code:
fastboot unlock-info
Reboot phone
Code:
fastboot reboot
Check connection
Code:
adb devices
Flash the downloaded Android firmware
Code:
adb sideload <FIRMWARE.ZIP>
Reboot phone
Code:
adb reboot
Happy flashing!
Click to expand...
Click to collapse
ok ) thanks
thanks for taking your time ,
the only thing guys, the reason why I contacted you is that I'm not in a position to find a version for the wiko wim lite, I don't really know which version to install and where to find it. I can't find anything, the only site that promised to download a version for this phone was fraudulent and installed dozens of programs on the computer, I had to do a system restore.
the alternative is to leave it as it is, but it doesn't work well with this software . android nougat 7.1
Non esiste rom per questo smartphone!
Just added some interesting device-related resources for this build request...
Hello Friends,
I have recently Purchased an Oppo F15, I have enabled developer mode, OEM Unlocked, and USB Debugging, with the latest adb drivers installed on my PC.
while I am running the command "adb devices" it returning with the device name I have connected i.e. Oppo F15 but when I am running the command "adb reboot fastboot", "adb reboot-bootloader", "adb reboot bootloader" the device reboots but not going to fastboot, it just reboots in normal mode.
Please help me if I am missing something in this. My device is running with Android version 9.
@Venomiest
Try this commands sequence
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
jwoegerbauer said:
@Venomiest
Try this commands sequence
Code:
adb reboot
adb devices
adb reboot bootloader
fastboot devices
Click to expand...
Click to collapse
Those are the proper commands
([emoji88]Havoc GSI[emoji88])
Venomiest said:
Hello Friends,
I have recently Purchased an Oppo F15, I have enabled developer mode, OEM Unlocked, and USB Debugging, with the latest adb drivers installed on my PC.
while I am running the command "adb devices" it returning with the device name I have connected i.e. Oppo F15 but when I am running the command "adb reboot fastboot", "adb reboot-bootloader", "adb reboot bootloader" the device reboots but not going to fastboot, it just reboots in normal mode.
Please help me if I am missing something in this. My device is running with Android version 9.
Click to expand...
Click to collapse
The bootloader is blocked by code combination. If you try to see more attentive you'll notice the tiny message on the black screen while rebooting.
Not Working
Alien object
Hey all, I just got a G90 Pro that I want to put a ROM on, but something is up with the fastboot. I have the drivers installed according to what I found online, but when I go to fastboot there is no response from the cmd inputs. Nothing even shows up when I check fastboot devices. Has anyone had luck with these phones? I can't even unlock the bootloader!
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
jwoegerbauer said:
If not already done yet, install the suitable BLUE USB Driver for Android:
Download BLU USB Driver for Windows (Latest Driver)
Download the latest and original BLU USB Driver to connect any BLU Smartphone and Tablets to the Windows Computer quickly.
androidmtk.com
Click to expand...
Click to collapse
I have done this, but did it again just to be sure, and device manager recognizes the G90 Pro under USB devices, and ADB finds it, but when I do the 'adb reboot bootloader' the fastboot mode text is on the bottom, yet fastboot commands don't do anything, not even 'fastboot devices'.
Edit: Fastboot devices is recognized in fastbootd, but not regular fastboot, yet the other commands don't work.
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
jwoegerbauer said:
In your case fastboot is located in Android's user-space, hence you run this command sequence
Code:
adb devices
adb reboot fastboot
fastboot reboot fastboot
fastboot <YOUR-COMMAND-HERE>
fastboot reboot
Click to expand...
Click to collapse
Fastboot reboot fastboot just brings up the fastboot command list. Assuming it's expecting me to try reboot bootloader.
That's really weird because your phone is running Android 10.
My info in settings definitely confirms that. Nothing seems to be working as expected though.
jwoegerbauer said:
That's really weird because your phone is running Android 10.
Click to expand...
Click to collapse
Is there any other possible solution? I still can't get fastboot commands to work after rebooting to fastboot mode from fastbootd.
I just got a new F(x)tec Pro-1X and I want to root it. I'm following the instructions to use Magisk from the F(x)tec team which involves 1) installing Magisk, 2) connecting adb and authorizing, 3) adb pushing the Pro-1X boot.img, 4) Running Magisk and patching the boot.img, and 5) downloading the patched .img.
Then I run "adb reboot bootloader" which leads me to a screen where I can choose Recovery mode and then I get to an Android screen that says "No command". I believe it's here that I'm supposed to run "fastboot flash boot magisk_patched-25200_HsxJg.img"; however, when I run "adb devices", I get unauthorized, and trying to run fastboot anyway fails:
$ adb devices
List of devices attached
8ce396c8 unauthorized
$ fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
I found elsewhere that from this screen, I can hold the power button and press the volume up key and then release both and I see the Android recovery screen. Then I scroll down to Enter fastboot and press power to enter that and I see fastbootd, but I get the same "waiting for any device" output if I try the fastboot flash command here.
If I go back to recovery mode, and instead go to Apply update from ADB, I then see the following from adb devices, but I still can't run fastboot flash:
$ adb devices
List of devices attached
8ce396c8 sideload
I'm running the latest Android Studio and platform-tools on a Lenovo X270 running Fedora 37 and Linux kernel 6.0.17. I'm connecting using a USB-2 port without a hub and tried multiple USBC cords.
A commenter on the F(x)tec forums said that he could never get his Lenovo X250 to work and he had to buy a Raspberry Pi 3 model B.
Are there any alternatives or diagnostics I can run to help solve this "unauthorized" error?
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
ze7zez said:
Did you enable usb debugging in the developer options and validate the box after connecting with a USB cable?
Click to expand...
Click to collapse
Yes. That was required for steps 2-4 for pushing and pulling the image. When I did that, I had to authorize my laptop on my phone. There's no such dialog during recovery mode. Is there some way to pre-authorize recovery mode with my laptop, or otherwise disable this authorization?
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
ze7zez said:
Option below USB debugging, which is: Revoke USB debugging authorizations.
or
read this:
ADB Android Device Unauthorized
Since I reinstalled Eclipse (simply deleted and downloaded it again) I can't debug my applications on Samsung Galaxy i9001 (with CyanogenMod - Android 4.4.2). It worked fine before reinstallation.
stackoverflow.com
Click to expand...
Click to collapse
Thanks, but none of that worked. My problem is authorizing during recovery mode, not during normal operations. It seems what I really need is to either modify /data/misc/adb/adb_keys on the device, or run adb disable-verity, or set ro.adb.secure=0, but I don't have permissions to do any of those.
It's interesting that another F(x)tec user says this works with a Raspberry Pi, and also says it does not work with his Lenovo X250 running Linux, which is similar to my laptop. This suggests there's some sort of limitation or additional security related to the Linux kernel 6.0.17 and/or Fedora, but I can't find what that is or how to diagnose it. I don't have SELinux running on my laptop.
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
MoHuToP said:
Good day,
I'm use adb tools from my fedora 37
Your issue is related to how you call adb.
Try this:
adb kill-server
sudo adb start-server
sudo adb devices
The same game with fastboot tools
Its works perfect with selinux on
Regards
Click to expand...
Click to collapse
Doesn't work:
$ adb kill-server
$ sudo -i
# adb start-server
* daemon not running; starting now at tcp:5037
* daemon started successfully
# adb devices
List of devices attached
8ce396c8 device
# adb reboot bootloader
... Wait for recovery mode "no command" screen ...
# adb devices
List of devices attached
8ce396c8 unauthorized
# fastboot flash boot magisk_patched-25200_HsxJg.img
< waiting for any device >
For reference, attached are pictures of all the places where I try the commands and they fail.
I bought a Raspberry Pi 3 B and microSD, installed Raspbian, installed adb and fastboot, connected to phone (normal boot), authorized the Pi, ran adb reboot bootloader, entered recovery mode, phone goes to "No command" screen, but then I get a popup on my Raspberry Pi desktop that says:
Unable to open MTP device "001,013"
Clicked OK and ran adb devices, and I'm back to the "unauthorized" status and adb and fastboot don't work. Tried this in the Raspberry Pi as both a normal user and root (with adb kill-server in between).
Tried with another USB C cable and got a similar error, although it ended with "001,016".
Any ideas?
Resolved by running fastboot on the START screen! (And worked through my X270)