I wanted to upgrade from android 9 to android 10.
Adb and fastboot were installed. The phone was enabled with USB Developermode and OEM change mode.
I entered the following commands;
# adb devices (then I saw my phone)
# fastboot devices
and then
# fastboot flash boot twrp-3.4.0-0-twrp.img
After that, "something" was left on the screen in small print that could not be read .... then I pressed the power button until the image disappeared and nothing happened.
After that, the phone can no longer be connected to the computer. The computer will no longer see the phone when im enter the command
# adb devices
My phone is CUBOT P30 ...Is it possible to restore or throw it straight in the trash!
SORRY my bad english.
@IFFI76
As long as you can interact with phone's bootloader you should be able to re-flash phone's Stock ROM.
The related command sequence would be
Code:
fastboot devices
fastboot flash-all <PATH_TO_STOCK_ROM_IMAGE>
fastboot reboot
Thank you for answering!
I don't understand exactly what you mean now!?
I personally believe I can't communicate with the bootloader...
I use debian distro and this is the output of my terminal;
[email protected]:/home/iffi/Downloads/ADB-fastboot/platform-tools# adb devices
List of devices attached
* daemon not running; starting now at tcp:5037
* daemon started successfully
[email protected]:/home/iffi/Downloads/ADB-fastboot/platform-tools# adb devices
List of devices attached
[email protected]:/home/iffi/Downloads/ADB-fastboot/platform-tools#
indicates that the device list is empty!
@IFFI76
Wondering why you stubbornly want to make an ADB connection, what in your case is absolutely pointless? Check whether you can establish a Fastboot connection.
Okay, I tried to do that now
I connected the mobile phone to the computer via usb and then below is the output of my terminal.
[email protected]:~
$ cd /home/iffi/Downloads/ADB-fastboot/platform-tools/
[email protected]:~/Downloads/ADB-fastboot/platform-tools
$ fastboot devices
[email protected]:~/Downloads/ADB-fastboot/platform-tools
$ sudo su
[sudo] password for iffi:
[email protected]:/home/iffi/Downloads/ADB-fastboot/platform-tools# fastboot devices
[email protected]:/home/iffi/Downloads/ADB-fastboot/platform-tools#
Looks like I can't connect to my phone and the bootloader is DELETED!
PLATFORM-TOOLS the contents of the directory are as follows
{
"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 suppose your phone became e-waste.
Related
Hello everybody,
want to ask your advice in re: following issue
I am going to use nextbook NX868QW8G tablet as an embedded advertisement solution ie it should start when external power gets plugged in. I can find a normal tech desc of this model in the internet even on the official site.
It have almost the same look&hardware as NX785QC8G availabe at wallmart but have slightly another cpu mtk8382 and embedded 3g modem which was the decisive factor since we need tablets to be updated remotely.
Here are system settings:
{
"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 have done the following:
1) rooted device via cydia impactor - root check apps from gplay are saying its rooted now + it has auto instaled chainfire SU to the tablet. For some reasons cydia impactor thinks its HTC ONE X. I have installed a PdaNetA4150 and it also considers it as HTC phone. I have tried to install drivers for nextbook8 I have found in internet but window doesnt recognize them as appropriate. At the moment device is recognized as unknown MT65XX Android phone
2) run adb reboot-bootloader
3) run fastboot oem unlock
4) run fastboot oem off-mode-charge 0
I have tried doing it manually and through cydia impactor but in both cases the command thread for #3 and #4 seems to be in an infinite sleep - just displays "..." in command line shell and cydia impactor simply gets frozen for a couple of minutes then throws timeout exception.
I think its waiting my input after #3 however the screen remains black and it does nothing when I press on vol up/down/power buttons. Fastboot prints "OK [X sec]" when I call fastboot reboot from another shell window.
In regards to the adb drivers and etc - device is visible through both 'adb devices' and 'fastboot devices' commands. For some reasons
Please advice in which direction to seach and digg.
Any help will be highly appreciated,
Max
Hello,
I am trying to install the PACEField ROM on my Amazfit A1609 (Chinese version) but I can't list the watch in fastboot in order to boot on the temp root boot image.
Commands:
Code:
$ ./adb devices
List of devices attached
2b9e2c22 device
Code:
$./adb shell reboot bootloader
The watch reboot and displays the Fastboot screen
Code:
$./fastboot devices
Nothing listed and
Code:
$ ./fastboot getvar all
< waiting for any device >
Stays on "waiting for any device" (with and without sudo).
Details
ADB/Fastboot version:
I use ADB and fastboot from the Android SDK :
Code:
./adb --version
Android Debug Bridge version 1.0.40
Version 4986621
Code:
./fastboot --version
fastboot version 28.0.1-4986621
Android file transfer displays an error message (can't access device storage)
{
"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 use the original USB cable
I am on a the last MBP with USB C port so the watch is connected through a dongle (the HooToo's one).
I have seen that windows users have to install some drivers in order to get fastboot access. Is there any drivers available for OS X ?
What are the others possible problems ? Is there any other way to install the ROM without fastboot getting full access ?
Fastboot is broken on macOS since High Sierra and it doesn't seem that Google is bothered enough to fix it... The last version that works somehow for me is version 1.0.36 from this repo:
https://android.izzysoft.de/downloads
Somehow because it may hang after 1 or 2 commands, so you must restart the watch manually and start again.
Hi,
my Pixel 4 got stuck booting on the G logo. I tried rebooting from recovery, but no luck.
I sidloaded Android 11 hoping that would fix it, but no luck.
So my option I guess it's to factory reset. But in order to avoid losing data, can anyone give me pointers to backup the phone?
The bootloader is unlocked, but not rooted. Developer settings were enabled and usb debugging should on by default.
From recovery adb devices sees an unknown device I cannot successful run backup commands on as the device is unauthorized.
Any help is appreciated
andreadoli96 said:
The bootloader is unlocked, but not rooted. Developer settings were enabled and usb debugging should on by default.
From recovery adb devices sees an unknown device I cannot successful run backup commands on as the device is unauthorized.
Click to expand...
Click to collapse
You can't establish a valid ADB connection because on phone the ADB RSA keys didn't get confirmed
{
"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's what the "unauthorized" ADB-message means.
FYI: When you click to always allow, Android appends the public key from ADB on the computer into a specific file ( /data/misc/adb/adb_keys ) on the phone.
jwoegerbauer said:
You can't establish a valid ADB connection because on phone the ADB RSA keys didn't get confirmed
That's what the "unauthorized" ADB-message means.
FYI: When you click to always allow, Android appends the public key from ADB on the computer into a specific file ( /data/misc/adb/adb_keys ) on the phone.
Click to expand...
Click to collapse
So considering that I can't turn the phone on to confirm that is there a workaround?
@andreadoli96
Don't know whether this will work or not
Code:
adb devices
adb push %USERPROFILE%\.android\adbkey.pub /data/misc/adb/adb_keys
adb reboot
adb devices
Good luck.
BTW:
Take note that if your Android version has encryption enabled out of the box ( there’s no way to remove encryption !!! ) then trying to backup the user-data ( will say pulling them out by means of ADB ) may work, but is senseless because you can't decrypt them.
Rase to wake not working.
Phone waking up even Rase to wake in off position
{
"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"
}
It may be a bug. You can try to upgrade the system
红豆生南瓜 said:
It may be a bug. You can try to upgrade the system
Click to expand...
Click to collapse
Hi
It is up to date
Fixed.
Follow these steps:
1- Activate developers options on your phone.
For this you have to open Settings>About phone and tap on MIUI Version for about 7-10 time.
Now you go back to settings>adittional settings > Developer Options. Make sure you have USB Debugging and
USB Debugging(Security settings) are activated. For this last one i think you have to be logged in your MI account.
2- Install ADB(Android Debug Bridge) on your computer.
If you are on Windows, install ADB Universal drivers first.
Then download the ADB files.
3- Excecute commands.
Open a Command prompt (or shell) on the directory where you have the adb files.
Connect your phone with a USB cable. Change the USB mode to “file transfer".
In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices.
You should get a prompt on your phone to allow (or deny) USB Debugging. Allow it and re enter on command prompt the "adb devices" command.
Now you should see your phone serial number. And you just have to enter the mentioned commands.
adb shell
settings put secure wake_gesture_enabled 0
exit (to exit adb shell)
And that`s all.
Screen turning on by itself.
When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving. Someone can help me please? When the winds of change blow, some build walls, others build...
forum.xda-developers.com
Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"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"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).