I have adb 1.0.31. It works when I boot system.
If I try use it in recovery mode got:
error: device offline
Any way to fix?
PC Ubuntu trusty
Android 4.4.2 CWM
svs57 said:
I have adb 1.0.31. It works when I boot system.
If I try use it in recovery mode got:
error: device offline
Any way to fix?
PC Ubuntu trusty
Android 4.4.2 CWM
Click to expand...
Click to collapse
Whats your device and which recovery version / rom is installed?
LS.xD said:
Whats your device and which recovery version / rom is installed?
Click to expand...
Click to collapse
I am getting this too on the Galaxy Nexus. I'll try and run .adb and it won't connect. I will then get a message from Windows saying that the USB is not recognizable. X.x
LS.xD said:
Whats your device and which recovery version / rom is installed?
Click to expand...
Click to collapse
SGS4 SGH-I337 LOKI, Omega 28 (XXUFNC9), Kernel: KT-SGS4-KK4.4-TW-ATT-04.02.2014, Modem: I337UCUAMDL, Recovery OUDHS (CWM),
ADB
Try to access ADB in root. I have never used Windows for connecting ADB but for linux, its the code:
Code:
adb root
adb devices
If still it shows device as offline, remove the plug, reconnect and start adb as root again.
You can also use commands like adb kill-server and adb start-server.
If still you get the problem, try to plug the cable on another USB port and try again.
Hope it works.
#Su said:
Try to access ADB in root. I have never used Windows for connecting ADB but for linux, its the code:
Code:
adb root
adb devices
If still it shows device as offline, remove the plug, reconnect and start adb as root again.
You can also use commands like adb kill-server and adb start-server.
If still you get the problem, try to plug the cable on another USB port and try again.
Hope it works.
Click to expand...
Click to collapse
Thank you! Works. I also never use Windows Brother?
It's strange. Long time I use adb including in revovery.
I can't remember what I did but suddenly got "offline" message.
I plug, unplug, remove ~/.android and /data/misc/adb, start adb from root, reboot phone and PC, even rebuild adb from latest sources.
Nothing help
adb devices offline
Can anyone help me??
{
"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"
}
Philips9 said:
Can anyone help me??View attachment 3120299
Click to expand...
Click to collapse
Same is happening with me. Don't know what to do. :/
Related
While in the Sony Tablet Bootloader Discussion I have created a R5A ADB Recovery Driver.
This will overwrite your Sony Tablet S ADB driver.
This does support x86 and x64.
Please note that the recovery is going to disallow most if not some adb commands, I created this so people can access the recovery with the new recovery address via ADB, hopefully someone would be able to bypass and hack the recovery using this.
This uses the ADB from the system so it is ok to install.
EDIT: I was really suppose to use adb install to install an application.
EDIT 2: Sideload just throws back an error, I have not tested ADB install and I doubt that would work.
Screeny of the commands that would work if I had a flashable zip file and also if the recovery allowed such thing:
{
"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"
}
Download and Installation instructions here: http://caftp.pcsat.tv/drivers/puredriver_sts_r5a_adb
andyabc said:
While in the Sony Tablet Bootloader Discussion I have created a R5A ADB Recovery Driver.
This will overwrite your Sony Tablet S ADB driver.
This does support x86 and x64.
Please note that the recovery is going to disallow most if not some adb commands, I created this so people can access the recovery with the new recovery address via ADB, hopefully someone would be able to bypass and hack the recovery using this.
This uses the ADB from the system so it is ok to install.
EDIT: I was really suppose to use adb install to install an application.
EDIT 2: Sideload just throws back an error, I have not tested ADB install and I doubt that would work.
Screeny of the commands that would work if I had a flashable zip file and also if the recovery allowed such thing:
Download and Installation instructions here: http://caftp.3owl.com/Drivers/PureDriver_STS_R5A_ADB/
Click to expand...
Click to collapse
says install method not supported for this type of file. I was hoping to use this to allow flashing on my soft brick tab that I just can't seem to get going again.
jamminjon82 said:
says install method not supported for this type of file. I was hoping to use this to allow flashing on my soft brick tab that I just can't seem to get going again.
Click to expand...
Click to collapse
Yeah the install command is just for installing applications...
Sent from my Nexus 4 using Tapatalk 4
Can we run adb shell and “ dump_image boot /sdcard/boot.img “ to port CWM
Plays2 said:
Can we run adb shell and “ dump_image boot /sdcard/boot.img “ to port CWM
Click to expand...
Click to collapse
Nope, unfortunately Sony did block most of the ADB commands and I assume it is blocked with either ADB unlock code or some file which is required to unlock the commands.
Sent from my Nexus 4 using Tapatalk 4
So I tried to flash CyanogenMod 12 to my phone, however, because this was my first time doing this sort of thing, I missed turning off the security on my phone before I wiped the phone. Obviously, at this point it was bricked, and after searching around, I discovered ADB Sideload. So I went through the process to get ADB, downloaded Android SDK and installed the platform tools, and I thought I was going to be able to save my phone. However, when I ran the TWRP ADB sideload, this happens when trying to input my file View attachment 3306335
I tried to check the drivers and found the HTC One X+ drivers, however when I try to install the drivers, this happens
{
"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"
}
When it does sometimes work, it gets to around 40% then just stops, or does "Total transfer 0.01" or something like that
There's also the problem that I couldn't actually flash a recovery without using the tool built for it by somebody on here, and that wouldn't let me get ClockworkMod Recovery for some reason
Please help me here, I'm incredibly stuck and even trying a RUU doesn't do anything
By the way it seems to connect just fine outside of ADB Sideload, it even gets detected by ADB when the server actually works and doesn't fail to start "ACK"
(EDIT) I do hear the phone disconnect and reconnect when I enter Sideload
TezzaBP said:
So I tried to flash CyanogenMod 12 to my phone, however, because this was my first time doing this sort of thing, I missed turning off the security on my phone before I wiped the phone. Obviously, at this point it was bricked, and after searching around, I discovered ADB Sideload. So I went through the process to get ADB, downloaded Android SDK and installed the platform tools, and I thought I was going to be able to save my phone. However, when I ran the TWRP ADB sideload, this happens when trying to input my file View attachment 3306335
I tried to check the drivers and found the HTC One X+ drivers, however when I try to install the drivers, this happens View attachment 3306350
When it does sometimes work, it gets to around 40% then just stops, or does "Total transfer 0.01" or something like that
There's also the problem that I couldn't actually flash a recovery without using the tool built for it by somebody on here, and that wouldn't let me get ClockworkMod Recovery for some reason
Please help me here, I'm incredibly stuck and even trying a RUU doesn't do anything
By the way it seems to connect just fine outside of ADB Sideload, it even gets detected by ADB when the server actually works and doesn't fail to start "ACK"
(EDIT) I do hear the phone disconnect and reconnect when I enter Sideload
Click to expand...
Click to collapse
Uninstall HTC sync and leave drivers. If that is indeed installed.
Lloir said:
Uninstall HTC sync and leave drivers. If that is indeed installed.
Click to expand...
Click to collapse
I'll try that
Unfortunately that didn't do anything
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.
Hello,
I am new to this forum but maybe I have an interesting thing.
I found a Samsung A3 (SM-310F 16GB) wich was going to trash. It seems it acts as a medical device for monitoring heart diseases. It has a custom launcher loaded on wich you can only load the monitoring program. It has the Android top bar with time bluetooth-status battery and so on, but you can´t swipe down to access preferences or else. You also can´t take screenshot due to security guidelines and you can´t connect to it with a PC.
So my question, is it possible to do a root on this device. Or to flash it with a stock firmware to use it as anormal phone?
I´m wondering if anyone has an idea about this.
Thanks
Dirk
The door to any Android device is ADB ( read: Android Debug Bridge ). If device isn't accessable by means of ADB then you can NOTHING do with it, IMHO.
jwoegerbauer said:
The door to any Android device is ADB ( read: Android Debug Bridge ). If device isn't accessable by means of ADB then you can NOTHING do with it, IMHO.
Click to expand...
Click to collapse
Ok, so how do I know if it is accessable with ADB?
And just for understanding, how do you customize a normal android device (smartphone), that it won´t act like a phone anymore? Just custom firmware, or custom chips?
igel81 said:
Ok, so how do I know if it is accessable with ADB?
Click to expand...
Click to collapse
You on Windows computer
install the Android USB driver suitable to this phone
install ADB
Then you connect Windows computer and phone via USB-cable, power on phone, and run this ADB command
Code:
adb devices
Look also inside here.
jwoegerbauer said:
You on Windows computer
install the Android USB driver suitable to this phone
install ADB
Then you connect Windows computer and phone via USB-cable, power on phone, and run this ADB command
Code:
adb devices
Look also inside here.
Click to expand...
Click to collapse
Thanks. I tried this, but unfortunately it shows no device. By holding up and home at start, it boots into a firmware update mode. From here I can connect with adb in sideload mode. Don´t know if this is helpfull...
@igel81
If you can boot phone into ADB Sideload mode
{
"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"
}
then you can flash a ROM as a whole.
jwoegerbauer said:
@igel81
If you can boot phone into ADB Sideload mode
then you can flash a ROM as a whole.
Click to expand...
Click to collapse
Too bad, it doesn´t work. It says "footer is wrong" and "signature verification failed". It seems you can only install roms signed by that medical company.
Hello,
Can we root the Android tablet YC-83T?
Specs: https://portworld-solu.com/portfolio-item/yc-83t-portable-8-inch-android-10-wifi-tablet/
Runs Android 10 (go)
Ram: 1GB
Storage: 32gb
It's not locked down, as in it has google services and it can install APK files
I don't think so, I can't seem to find a custom recovery, you might be able to use adb sideload to install magisk or superuser though, good luck though
running adb reboot bootloader gets stuck on the boot logo, nice
17lifers said:
running adb reboot bootloader gets stuck on the boot logo, nice
Click to expand...
Click to collapse
could you send a picture of what it's stuck on?
{
"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"
}
OEM Logo, not bricked as it can boot fine without usb cable (yes tablet was given away for free lol)
17lifers said:
OEM Logo, not bricked as it can boot fine without usb cable (yes tablet was given away for free lol)
Click to expand...
Click to collapse
lucky you, what you planning on rooting a tablet for?
oh and what model does it say you have in your settings?
YC-38T
might have an idea, does the tablet bootloop whilst adb is on? or does it just not turn off at all?
only with adb on, i can disconnect cable, force off the device, and boot it back up then it'll turn on fine
so it doesn't turn off at all?
no
17lifers said:
no
Click to expand...
Click to collapse
whilst it's stuck, could you run the fastboot devices command?
will try again, currently charging it (18:54 in the netherlands )
nope, no response
17lifers said:
nope, no response
Click to expand...
Click to collapse
It could have a non-standard VID/PID on the bootloader.
Is it even detected as anything?
What does DeviceManager say?
hm, if possible, can you go to recovery and use adb sideload? you should probably do the devicemanager thing first though
shows up as usb download gadget
17lifers said:
View attachment 5856319
shows up as usb download gadget
Click to expand...
Click to collapse
that's odd, what about entering recovery?
no command ¯\_(ツ)_/¯
we need usb drivers thats why, gonna install them