Develop Bugs

[Q] Device recognized by adb, but always offline

Recently got my new N7. First thing I wanted to do was to edit hosts file on it, but currently after fixing the issue with no visible devices in
Code:
adb devices
now I see my device, but it is always offline.

{
"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"
}

NetJunky88 said:
Recently got my new N7. First thing I wanted to do was to edit hosts file on it, but currently after fixing the issue with no visible devices in
Code:
adb devices
now I see my device, but it is always offline.
Click to expand...
Click to collapse
Is your adb version 1.0.31 or greater? Use "adb version" to see what version you are running.
device offline is usually wrong adb version
device not authorized is usually because you didn't accept the RSA prompt for the whitelist

sfhub said:
Is your adb version 1.0.31 or greater? Use "adb version" to see what version you are running.
device offline is usually wrong adb version
device not authorized is usually because you didn't accept the RSA prompt for the whitelist
Click to expand...
Click to collapse
First of all sorry for such delay in reply and my adb version is Android Debug Bridge version 1.0.29
UPDATE:
Updating tools through Android SDK Manager did help and now device is visible, but I have one more, what seems to me, easy question. Is it possible to edit one rooted file without rerooting whole main directory? I need to edit /system/etc/hosts file.

NetJunky88 said:
First of all sorry for such delay in reply and my adb version is Android Debug Bridge version 1.0.29
Click to expand...
Click to collapse
Upgrade your adb and you should see the RSA prompt and after accepting the prompt on the tablet, everything will work as you expect.

sfhub said:
Upgrade your adb and you should see the RSA prompt and after accepting the prompt on the tablet, everything will work as you expect.
Click to expand...
Click to collapse
As I wrote in update, that adb was successfully updated and it did help.

Just go to storage settings and untick mtp and ptp and try again. Sorry for muy english it's not muy native language
Enviado desde mi Galaxy Nexus usando Tapatalk 2
---------- Post added at 01:10 PM ---------- Previous post was at 01:06 PM ----------
I have the same problem and that solve it
Enviado desde mi Galaxy Nexus usando Tapatalk 2

Any way to mark question as solved?

Problem solved
Seems That 4.3 Jellybeen you need ADB newest drivers follow this guide http://www.droidextra.org/2013/12/24/solved-fix-adb-devices-offline-100-working.html

NetJunky88 said:
Any way to mark question as solved?
Click to expand...
Click to collapse
OP can edit title and include solved. That does help people too.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

Lg L Manager [Win] [Unix] [L3] [L3 II] [L5] [L7]

{
"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"
}
LG L Manager​
With Crazy Mode too​
Lg L Manager is your new Pc suite for your Lg L3, L3 II, L5 and L7!!​
Features
Code:
#Supported Os:
--> Windows (Xp, Vista, 7, 8.x)
--> Unix based os (Os X too)
--> Linux distros (Ubuntu, Debian, Suse, Fedora, Linux Mint, etc..)
#Common Fetures:
-->Backup & Restore
-->Adb Shell
-->Install roms (Not fully automatized due to wipe /data)
-->Install Gapps or any mod (automatizated)
-->Install apk
-->Import Camera photos
-->Push and Pull files
-->Crazy mode
#Device Specific
-->Full Unlock (Bootloader+Recovery+Root) [L5] [L7] [L3II -> WIP]
-->Full Unlock (Recovery+Root)

Sources
Sources: https://github.com/ionolinuxnoparty/Lg-L-Manager
Branches :
Master > Windows
Master-unix > Unix and Linux
Click to expand...
Click to collapse
Download
Windows
Unix / Linux
Click to expand...
Click to collapse
Bugs
-Windows > dunno what's working and what not cuz I own no windows PCs and I wrote it with no test
-Unix > Crazy mode will make you crazy [cannot fix this]
Check commits to see if I've fixed something
Click to expand...
Click to collapse
How to run
Unix / Linux : browse into the folder where you have to place files ( ~/Lg-LManager), and run
./Start.sh 0 [Select device manually]
./Start.sh 1 [Lg L3]
./Start.sh 2 [Lg L5]
./Start.sh 3 [Lg L7]
./Start.sh 4 [Lg L3 2]
Click to expand...
Click to collapse
Windows: execute start.bat

Dev notes
Full Unlock,
it was pretty easy, everyone used stupids toolkit that may work or not. Adb and fastboot are the most useful and powerful tools.
I've changed the order to unlock device that everyone used. Why first root, then recovery and then bootloader?? Do you need the keys to change a car engine? Nope, so it's the same thing for an android device. Fist I boot a recovery to get adb root (stock kernel doesn't allow it, but a recovery automatically give adb root acces even if phone is not rooted), then I'll push file to unlock bootloader to sdcard and then unlock it. After this I flash recovery, then flash any root package. Done! And it works with any rom.
Click to expand...
Click to collapse
About Lg L3 II,
apparently this device has no bootloader to imput fastboot commands needed for the full unlock, read notes inside bat file
Click to expand...
Click to collapse
About Lg L3,
this is the only device I own of the four I support... Now there's no recovery that allow both adb shell and sideload so I've to push every file to sdcard. When there will be a recovery where both adb shell and sideload are working I'll change a few lines of code and it will be OK.
Click to expand...
Click to collapse
About Crazy Mode,
it's made for crazy users that may brik their devices and make strange things with their pc. When crazy mode is enabled there's no way to quit it and it may lag your pc like hell (until reboot) so you won't be able to do anything because you're crazy and you may destroy something.
Click to expand...
Click to collapse

Seems so good!
Well I guess I need to run su before i execute it on unix because of the permission errors I get , it will work fine I guess
If you need any help or testing for Unix , message me on Hangouts

Help Mounting Remote Samba/CIFS Shares (persistent)

So basically I'm rooted and Busybox installed trying to use XBMCTORRENT and getting the unmounted shares error
So trying to mount my remote shares using this command while adb shell and su:
mount -o noperm,unc=\\\\192.168.0.21\\putsharenamehere,username=putusernamehere,password=putpasswordhere -t cifs none /mnt/obb/nas
I get this error ermission denied
Also tried a lot of apps like CifsManager and Mount Manager but none of those worked either.
Any help would be greatly appreciated.

username, not user name
/mnt/obb/nas exist? with which permission?

Kramar111 said:
username, not user name
/mnt/obb/nas exist? with which permission?
Click to expand...
Click to collapse
Oh yeah sorry about user_name that was just me posting the thread
/mnt/obb/nas was created previously for this purpose with 777
thanks for the quick reply btw

Just checked
Code:
adb shell su -c mount -o noperm,unc=\\\\192.168.1.1\\Media,username=123,password=12345 -t cifs none /mnt/obb/nas
All Ok

Kramar111 said:
Just checked
Code:
adb shell su -c mount -o noperm,unc=\\\\192.168.1.1\\Media,username=123,password=12345 -t cifs none /mnt/obb/nas
All Ok
Click to expand...
Click to collapse
OK so stupid question under username is my NAS user and password right???
THat username has access and rights for my nas folder so idk what's going on here really
I still get permission denied error
I double checked the folder inside the firetv for the permissions dont know what else to do damn

LastDeuS said:
OK so stupid question under username is my NAS user and password right???
Click to expand...
Click to collapse
Yes.
Can you make screenshot?

Kramar111 said:
Yes.
Can you make screenshot?
Click to expand...
Click to collapse
Suere here it goes
{
"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"
}

Can you change (for testing purposes) username and password to something like 123?

Kramar111 said:
Can you change (for testing purposes) username and password to something like 123?
Click to expand...
Click to collapse
Man I was away for vacations so I couldn't test anymore but thanks that did the trick
I must be honest I'm so lazy I was waiting for someone to tell me to test a simpler user and pass so I would go ahead and create another user on my NAS
I like to think all systems now are beyond those simple problems but hey it's working now thanks again man!!!

Kramar111 said:
Can you change (for testing purposes) username and password to something like 123?
Click to expand...
Click to collapse
Now that we got that working
How can I make this script run each time I reboot the device

LastDeuS said:
Now that we got that working
How can I make this script run each time I reboot the device
Click to expand...
Click to collapse
Don't know
For now my device is bricked (hope temporary) (bueller-51.1.4.1_514013920-rooted + reinstall Xposed framework)

Kramar111 said:
Don't know
For now my device is bricked (hope temporary) (bueller-51.1.4.1_514013920-rooted + reinstall Xposed framework)
Click to expand...
Click to collapse
Oh man sorry to hear that I'm thinking I can use some sort of script app to run this command each time I turn on the FireTV

LastDeuS said:
Oh man sorry to hear that I'm thinking I can use some sort of script app to run this command each time I turn on the FireTV
Click to expand...
Click to collapse
My Fire TV is restored now!
Thanks to rbox
But no time to try with script

Can't find my device in fastboot mode

Hi, i want to unlock the bootloader of my old Redmi note 5, but there's a problem, when I go into fastboot mode, the Xiaomi's software can't find it, even using ADB the device is impossible to find. If I turn it on normally i can find it. Why it happens?

Hey u may give this a try as based on my understanding Xiomi devices will require u to install mi flashtool on PC as it has driver installation option. Remember some times you are required to disable driver signature verification.

I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.

plusminus_ said:
I recently had trouble with fastboot as well. I eventually sorted it by installing the correct drivers, from here: http://bigota.d.miui.com/tools/xiaomi_usb_driver.rar
I don't remember having to disable driver signature enforcement (usually to do this you have to use an advanced boot option as shown in Option 2 here) but maybe it happened automatically.
Click to expand...
Click to collapse
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
{
"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"
}

Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
Weird.
Maybe try a different cable?

Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
U might be using an Amd based system. Usb 2.0 hub is ur solution

Fruso01 said:
I installed the driver but nothing changed. I post a screenshot of the situation , as soon as i go into fastboot mode the adb can recognize the device, but after few seconds not.
View attachment 5260567
Click to expand...
Click to collapse
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.

drnightshadow said:
lool win10 sh1t... use usb 3 reg patch or usb 2.0 hub. Search it on xda forum.
Btw. There is no problems on w7 and linux lool.
Click to expand...
Click to collapse
Can you tell me about this usb 3 reg patch?
Actually i am outstation and don't have my usb hub and i want to do faatboot commands

Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me

Banty448 said:
Why my note 5 pro not connecting with pc after installing any custom rom.i have proper usb driver and everything like adb fastboot..but not showing any device in my computer ...can anyone help me
Click to expand...
Click to collapse
Read the thread and don't be troll. You didn't even read post before you post it your own. Ignorance is a bliss.
Good luck and stay safe.

Question MIUI 12.5.6 killed gestures for third party launchers

MIUI 12.5.6 killed gestures for third party launchers, I have been using Fluid.N.G to bypass full screen gestures erlier problems, but now system doesn`t allow to switch to gestures when third party launcher is selected. Does anyone know how to get it work?

Yeah purchase LADB and run the command after any reboots, it is on sales now cause I requested for. Hurry up.

italodance said:
Yeah purchase LADB and run the command after any reboots, it is on sales now cause I requested for. Hurry up.
Click to expand...
Click to collapse
What command should I enter? I've enabled USB debugging and granted rights for FNG, but despite this, the option to remove control keys doesn't work. How to do it with a manual command? I'd love to see if it works via PC, and then possibly buy a LADB to do it from phone. BTW I have a ABD Shell for Tasker already

malykazio said:
What command should I enter? I've enabled USB debugging and granted rights for FNG, but despite this, the option to remove control keys doesn't work. How to do it with a manual command? I'd love to see if it works via PC, and then possibly buy a LADB to do it from phone. BTW I have a ABD Shell for Tasker already
Click to expand...
Click to collapse
settings put global force_fgs_nav_bar 1

@italodance Thank you good man! Not without some probems with the configuration, but it worked!

malykazio said:
@italodance Thank you good man! Not without some probems with the configuration, but it worked!
Click to expand...
Click to collapse
What problem? If it is statusbar theme, just switch between gestures once then back to homescreen menu and run the command again. you won't lose your theme.

italodance said:
What problem? If it is statusbar theme, just switch between gestures once then back to homescreen menu and run the command again. you won't lose your theme.
Click to expand...
Click to collapse
I was referring to the LADB configuration, I couldn't get the pairing to work properly at first, but I used the hint about two windows and then it worked. It would be nice to force Tasker to work this way, so that using its ADB plugin it automatically enters this command after a reboot. When I find time I might look into it, for now I'm happy. Thanks again.

.

.

malykazio said:
I was referring to the LADB configuration, I couldn't get the pairing to work properly at first, but I used the hint about two windows and then it worked. It would be nice to force Tasker to work this way, so that using its ADB plugin it automatically enters this command after a reboot. When I find time I might look into it, for now I'm happy. Thanks again.
Click to expand...
Click to collapse
LADB is really painful to use...
Tasker allows you to set this global var after each boot via a Custom Setting (no need for ADB plugin)
Create a Profile > Event > System > Device Boot
Add a new Task
Add a new Action > Settings > Custom Setting
{
"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"
}

Mellow971 said:
Tasker allows you to set this global var after each boot via a Custom Setting (no need for ADB plugin)
Click to expand...
Click to collapse
Interesting option - is it working without root?

Yes, you just need to grant Tasker WRITE_SECURE_SETTINGS permission via ADB