Is there a way on this phone to do adb without needing to hook up from a PC or another phone?
drivel2787 said:
Is there a way on this phone to do adb without needing to hook up from a PC or another phone?
Click to expand...
Click to collapse
No
Yes use Shizuku.
SamsungKing10 said:
Yes use Shizuku.
Click to expand...
Click to collapse
Only works if you are rooted with Shizuku. If you are not then you have to do it over a pc to use adb
Jake.S said:
Only works if you are rooted with Shizuku. If you are not then you have to do it over a pc to use adb
I'm not rooted and shizuku works...I use it for my Hex Themes.
Click to expand...
Click to collapse
Well according to preview pic it says you need root to use shizuku
Fytdyh said:
No
Click to expand...
Click to collapse
You answered that with a definitive "No" when the answer, in fact, is "Yes." Shizuku.
Shizuku - Apps on Google Play
Shizuku is an open-source app for serving multiple apps that require root/adb.
play.google.com
Jake.S said:
Only works if you are rooted with Shizuku. If you are not then you have to do it over a pc to use adb
Click to expand...
Click to collapse
Thanks for tips this is wrong it actually does work and no PC required!!!!
Nope. You don't need root.
Shizuku no need root or adb! Test on my fold 3, great app work
Well then preview picture is lying since there it says it does need root
{
"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"
}
As you can see here it says for no root device you need to a computer to start adb. So apparently it needs root to start adb via phone in shizuku. Other option it has is starting wireless method but then it needs you to edit debug mode which isn't good for newbies to touch developers section.
Jake.S said:

As you can see here it says for no root device you need to a computer to start adb. So apparently it needs root to start adb via phone in shizuku. Other option it has is starting wireless method but then it needs you to edit debug mode which isn't good for newbies to touch developers section.
If you are using Android 11 or above you can use wireless debug
Click to expand...
Click to collapse
Like i said newbies shouldn't be touching developers section. It makes device more vulnerable if they are in there touching settings that aren't supposed to be on. So answer was I wasn't wrong about this app requires root. You guys where wrong about that part.
Jake.S said:
View attachment 5492501
As you can see here it says for no root device you need to a computer to start adb. So apparently it needs root to start adb via phone in shizuku. Other option it has is starting wireless method but then it needs you to edit debug mode which isn't good for newbies to touch developers section.
Click to expand...
Click to collapse
No. Once you run the command on your computer you're set. No need for root and you don't need the computer again. Just once.
There's also a tool called bugjaeger that can run adb on android devices, I use it to push apk's to my quest 2. Not sure if it can work locally.
Try to get the apk called LDAB, then connect to your own device wirelessly with the connect code and port.
Remember if you get the connect code or pin wrong, you'll need to go and reset data for LADB in order to re-enter code.
Shizuku works fine with adb wireless.
Sorry the app is called LADB. You need to do wireless pairing, use the dual screen feature to pair the code and port number.
I have tried it and it works without root
edmondt said:
Sorry the app is called LADB. You need to do wireless pairing, use the dual screen feature to pair the code and port number.
I have tried it and it works without root
Click to expand...
Click to collapse
Instructions to use LADB here.
Related
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
C:\Users\rikku>adb version
Android Debug Bridge version 1.0.32
Revision eac51f2bb6a8-android
C:\Users\rikku>adb devices
List of devices attached
1c576f70 sideload
C:\Users\rikku>adb usb
error: closed
Click to expand...
Click to collapse
mkioshi said:
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
Click to expand...
Click to collapse
Changing miui roms still require the bootloader to be unlocked.
mkioshi said:
After I flashed a ROM (a dev official rom since my device has a locked bootloader), now I cannot flash anything else.
I get the 'error:closed' message whenever I try to adb sideload, or adb tcp, or adb usb.
Since my phone is bootlooped I cannot unlock the bootloader or try other things outside adb.
Has anyone ever faced this kind of error?
Click to expand...
Click to collapse
Have you tried using Ubuntu and regular adb or something?
If you can't change anything on the phone start changing the way you try to fix it with the PC.
Maybe the linux adb will force it to work or something.
Sorry no specific answer but could be worth a try. If you have the determination there is a chance to fix it.
Your absolute last option is EDL with the test point on the inside of the phone. If you can't send it back to the seller its better to have a phone with a broken seal on the back (just repair it yourself after) than a fully assembled paper weight
Dobsgw said:
Have you tried using Ubuntu and regular adb or something?
If you can't change anything on the phone start changing the way you try to fix it with the PC.
Maybe the linux adb will force it to work or something.
Sorry no specific answer but could be worth a try. If you have the determination there is a chance to fix it.
Your absolute last option is EDL with the test point on the inside of the phone. If you can't send it back to the seller its better to have a phone with a broken seal on the back (just repair it yourself after) than a fully assembled paper weight
Click to expand...
Click to collapse
I tried both xiaomiadb and normal adb, all give the same error, on Mac OS X and Windows 10. Seems to me the problem is in the phone, I dunno.... Thanks a ton tho!
mkioshi said:
I tried both xiaomiadb and normal adb, all give the same error, on Mac OS X and Windows 10. Seems to me the problem is in the phone, I dunno.... Thanks a ton tho!
Click to expand...
Click to collapse
Seriously try Linux
Dobsgw said:
Seriously try Linux
Click to expand...
Click to collapse
I installed a virtual Ubuntu machine, did the passthrough but no dice
{
"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"
}
mkioshi said:
I installed a virtual Ubuntu machine, did the passthrough but no dice
Click to expand...
Click to collapse
good day please was this problem solved cause i have the same screen as above
Now that the Q7+ is out in mass can it be rooted? I know you can unlock it but can be rooted and if so what are
some of the ways it's been done? Removing bloatware is a big motivation for rooting for me.
Cheers!
95south said:
Now that the Q7+ is out in mass can it be rooted? I know you can unlock it but can be rooted and if so what are
some of the ways it's been done? Removing bloatware is a big motivation for rooting for me.
Cheers!
Click to expand...
Click to collapse
No root is possible with this device, Bootloader cannot be unlocked.
{
"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"
}
If I have Metro Pcs Q7+ LM-Q610MA, can it be unlocked. Because the option for OEM unlock is available in the dev. Options. Anyway I've never done it, and figure I use the twrp app and that's a wrap.
Paradox6996 said:
If I have Metro Pcs Q7+ LM-Q610MA, can it be unlocked. Because the option for OEM unlock is available in the dev. Options. Anyway I've never done it, and figure I use the twrp app and that's a wrap.
Click to expand...
Click to collapse
No it cannot be unlocked
Bootloader unlock and rooting are two different things.
And what about apps like KingRoot, Kingoo Root etc?
pawwaap said:
Bootloader unlock and rooting are two different things.
And what about apps like KingRoot, Kingoo Root etc?
Click to expand...
Click to collapse
I have tried every method out there, KingRoot, Kingoo Root etc do not work on this device.
And have you updated Android system on first run?
The ubdate process starts automatically, it needs disabling in settings.
From box yet the system version is dated as 1 may 2018, and very agressivelly wants to update itself
It's obvious the newer system update the less probability KingRoot manages it!
An another question, have you tried to root via KingRoot or KingooRoot, but NOT an apk run on Android - but exe run from PC and connecting through USB cable?
ivy.lally said:
And have you updated Android system on first run?
The ubdate process starts automatically, it needs disabling in settings.
From box yet the system version is dated as 1 may 2018, and very agressivelly wants to update itself
It's obvious the newer system update the less probability KingRoot manages it!
Click to expand...
Click to collapse
ivy.lally said:
An another question, have you tried to root via KingRoot or KingooRoot, but NOT an apk run on Android - but exe run from PC and connecting through USB cable?
Click to expand...
Click to collapse
Like I said, "I have tried every method out there". tried before and after updating no luck.
Maybe developers from KingRoot, KingoRoot etc. will find some exploit within this system, to enable obtaining root without touching bootloader
And indeed did you try with KingoRoot on PC? I tried to try, as KingoRoot didn't want to get installed on MS Win. As part of installation it downloads something from Internet, but it has been stuck exactly on 10% of progress bar.
Repeated on another komputer and the same: stuck on 10%! Have you experienced anything like this? So, how have you tried to root through KingoRoot from PC if the program can't install at all on a computer?
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.
Can anyone suggest some PC applications that can allow to manage the Phone's App, SMS, WhatsApp, ... from PCs??
I tried some of them but can't find one can work with the Redmi K40.
Thanks.
Sorry bud, no suggestions off hand, but curious... what exactly do you want to manage - backing up messages to PC etc, or sending messages from phone via PC, or what?
EDIT: are you using W10? could try this
or... one of these perhaps
KDE connect is a super app. There is a Windows version as well (however it's complicated to install)
reg66 said:
Sorry bud, no suggestions off hand, but curious... what exactly do you want to manage - backing up messages to PC etc, or sending messages from phone via PC, or what?
EDIT: are you using W10? could try this
or... one of these perhaps
Click to expand...
Click to collapse
I'm looking for some methods to remove the apps in the K40. There are too many useless apps!!!
Robert314 said:
KDE connect is a super app. There is a Windows version as well (however it's complicated to install)
Click to expand...
Click to collapse
It's TOO complicated to install!!!
hons9424 said:
I'm looking for some methods to remove the apps in the K40. There are too many useless apps!!!
Click to expand...
Click to collapse
Root or non-root?
Root: Debloater Magisk module, together with some apps to freeze/disable apps like SD maid.
Non-root: adb command or
XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools
The way to install that tool is written here until step 7.
{
"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"
}
Mark up the app you want to remove and press Uninstall.
You can re-install those removed apps if you need them back.
You cannot uninstall certain apps in non-root devices.
To manage Android applications, there is a wonderful tool - ADB AppControl. This is a new and convenient program. Very easy to use. No root needed.
Does not require installation. If you have Windows and Android device - this program will work for you ;-)
ADB AppControl XDA topic
T
pl1992aw said:
Root or non-root?
Root: Debloater Magisk module, together with some apps to freeze/disable apps like SD maid.
Non-root: adb command or
XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools
The way to install that tool is written here until step 7.
\
Click to expand...
Click to collapse
pl1992aw said:
Root or non-root?
Root: Debloater Magisk module, together with some apps to freeze/disable apps like SD maid.
Non-root: adb command or
XiaomiADBFastbootTools (Java)
https://github.com/Szaki/XiaomiADBFastbootTools
The way to install that tool is written here until step 7.
Mark up the app you want to remove and press Uninstall.
You can re-install those removed apps if you need them back.
You cannot uninstall certain apps in non-root devices.
Click to expand...
Click to collapse
Thanks!! I downloaded the files but didn't find the install instructions.
The link:
[MIUI12~13 A11~12.0/12.1][UNLOCK][ROOT] Picture guide unlock bootloader, flash custom ROMs & root Xiaomi Poco X3 Pro
Thanks for @urbanman2004 guide for Poco X3 Pro. Some sentences still needed, so keeping it similar. This guide provides photos & screenshots. Simulate all process and reduce misunderstanding. Section 1: Unlock bootloader (Works for most...
forum.xda-developers.com
seems not correct.
I use Anytrans for android. Works well
Cyber.Cat said:
To manage Android applications, there is a wonderful tool - ADB AppControl. This is a new and convenient program. Very easy to use. No root needed.
Does not require installation. If you have Windows and Android device - this program will work for you ;-)
ADB AppControl XDA topic
View attachment 5333519
Click to expand...
Click to collapse
This looks good. Will try it out.
Thanks.
hons9424 said:
T
Thanks!! I downloaded the files but didn't find the install instructions.
The link:
[MIUI12~13 A11~12.0/12.1][UNLOCK][ROOT] Picture guide unlock bootloader, flash custom ROMs & root Xiaomi Poco X3 Pro
Thanks for @urbanman2004 guide for Poco X3 Pro. Some sentences still needed, so keeping it similar. This guide provides photos & screenshots. Simulate all process and reduce misunderstanding. Section 1: Unlock bootloader (Works for most...
forum.xda-developers.com
seems not correct.
Click to expand...
Click to collapse
You have to click on the Spoiler tag under Clean Flash custom ROMs to open for more info on installation.
Pictures are long, so had made it hid.
ADB AppControl is also a good one. Cyber.Cat
is the author himself
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