Hi, my phone is rooted, but still on stock rom with twrp recovery. My problem is that whenever I try adb commands or even check devices, it says it offline but when in fastloader and try fastboot devices, my device is seen and communicating well. Why is this so? What did I miss to do?
here is what shows when I try adb devices:
{
"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"
}
Pls advice what to do.. thanks!
P.S., after unlocking my bootloader and installing twrp, i locked it again. Is this the reason i cant connect via adb or this issue is not related at all?
Thanks!
Do you have the latest adb? With 4.2.2 a security feature was added to allow for white listing computers connected via adb. Older adb versions don't work with this.
See here: http://forum.xda-developers.com/showthread.php?p=37892511
Sent from my Nexus 10 using Tapatalk 4 Beta
ok, will check this thread.. thanks!
Related
Hello
I have a leeco s3 and i tried to install twrp and rooting them and i flollwed the link in the photo
{
"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"
}
the process stucks to process 8
{ 8. Next, install custom recovery by typing the following commands:
fastboot flash recovery recovery.img}
After this the phone stuck to fastboot mode and I press fastboot reboot to adb cmd.
After this the phone stops working doesnt turn on.
I think that have hard brick.
PLEASE PLEASE help me.
Is your computer detecting the device properly?
SasoGO said:
Is your computer detecting the device properly?
Click to expand...
Click to collapse
Yeah the computer makes the connect and disconnect sound.
after updating mi9 rom mobile complet dead
not connecting with adb .
all drivers is properly installed.
in cmd -adb devices- list is blank
in cmd - fastboot devices - 68fa8c907D22 SHOWING
IN DEVICE MANAGER-
{
"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"
}
please help me.
NAVEEN UDANIYA said:
after updating mi9 rom mobile complet dead
not connecting with adb .
all drivers is properly installed.
in cmd -adb devices- list is blank
in cmd - fastboot devices - 68fa8c907D22 SHOWING
IN DEVICE MANAGER-
please help me.
Click to expand...
Click to collapse
Can you boot to recovery?
After testing LineageOS over the weekend I wanted to go back to stock EMUI, so I downloaded the newest firmware from Team MT (FullOTA v167421) and flashed it via TWRP. That went through without any errors so I rebooted the phone and now I got nothing.
Basically whats described in this thread. (/huawei-p8/help/huawei-p8-black-screen-adb-recovery-t3663103 ;sorry, cant post links)I can't enter the bootloader, when connected to the PC neither adb devices, adb wait-for-device, nor fastboot-devices show anything. The only sign of life I have is in the device manager.
{
"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"
}
Any help would be appreciated.
For anyone with the same/similar problem: I didn't find a solution for this, gave up and sent it in.
As a newbie/noob, I am attemting getting the Mi A1 rooted. Thanks to this great forum I managed to get the bootloader unlocked, using ADB. After I have unlocked this bootloader the adb/fastboot cannot detect my phone anymore. I did check the USB debugging setting on the phone and after a few times I reinstalled ADB on my notebook. I found a lot of threats, but none to this particular problem. What am I missing?
{
"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"
}
Probably usefull info:
Xiaomi Mi A1, Android 9
Kernel: 3.18.120...
Notebook: Windows 10
Same.
You can get access to it in recovery mode, which is kinda disgusting because you have to reboot into twrp again again to transfer files. FML. Sad for us.
try it on other pc
try another cable
Hey guys, I want to revert my U Ultra to barebones stock Oreo ROM. Now the thing is, my installation doesn't seem to work, for whatever reason. I have attached a screenshot from the error message I get in the command prompt on Windows. I have USB Debugging enabled on my phone (running some version of Lineage OS with Android 10 at the moment), have the device drivers installed. I tried to lock my bootloader first with fastboot OEM lock but for whatever reason, it doesn't work either.
Any idea what I can try? I made sure, that the RUU is the correct one for my region as well, so it's not going to be the root of this problem I am having. Thanks in advance.
{
"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"
}
The message I get when trying to lock the bootloader via fastboot flashing lock or fastboot oem lock is "FAILED (remote: 'unknown command')" and I have not found a fix for it yet either.
Any help is greatly appreciated!