-All credit for this method belongs to @xdabbeb from this thread: http://forum.xda-developers.com/showthread.php?t=2467302 All I did was gather the necessary elements and test to see if this would work on the G3 as it did on the G2.
-Please thank him for the great work he has done for finding and executing this method originally for the Verizon G2.
-Another shout out to @rickleasa for extracting and providing the hiddenmenu.apk from the AT&T G3 rom.
So Verizon as usual has hidden some features from the stock lg rom that other variants have access to, in this case the hidden menu that is typically accessed via a code entered into the dialer. This method will unlock this option for us - though you will not be able to access it via the dialer (well, not that I know of...yet), its accessed through adb or terminal.
Step 1: Download the hiddenmenu.apk at the link at the bottom of the post. The apk is unaltered (not deodexed) from the AT&T build. The Odex file is not needed.
Step 2: Manually past the apk into system/app and set permissions to rw-r-r- using your preferred root file manager, then reboot.
Step 3: From adb: (assuming you have adb set up and operational) type adb shell (then enter), su (then enter), and enter the command, or from terminal: type su (then hit enter) to gain root, then enter the command (press enter after entering or pasting the command). Command here:
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
-The hidden menu will then open up and your good to start breaking your phone as you see fit!!
-The most common use for this is to fix Knock-on if you ever break it (Flashing international ports has a tendency to break hardware functions). This is done by accessing the hidden menu and going to HW Device Test/Touch Test/Touch Firmware Upgrade. Wait 10 seconds after updating to see if the fix worked.
-You can do lots of damage in there so be careful!! There's also many other fun things to do as well.
If someone finds a dial code that will execute this menu after the apk is installed, please post it :good:
Updated Codes: Verizon Hidden Enable/Disable menu: ##3328873 + send + 000000
Here's what you'll get:
{
"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"
}
##PROGRAM985, Call, Enter "000000" for code opens vzw field test. Still poking around for LG menu.
OG RAZR XT912 got 4.4 before S4!
anyway to tell band 4 from this menu?
This can also be run from Android Terminal Emulator on the phone. I stuffed the "am..." line into a file called "hiddenmenu", put that in /system/bin/
-Launch Terminal Emulator
-su
-hiddenmenu
Hidden Menu will launch
Back in Terminal Emulator:
-exit
-exit
The above may also need busybox -- not sure, as I had already installed that app.
markfm said:
This can also be run from Android Terminal Emulator on the phone. I stuffed the "am..." line into a file called "hiddenmenu", put that in /system/bin/
-Launch Terminal Emulator
-su
-hiddenmenu
Hidden Menu will launch
Back in Terminal Emulator:
-exit
-exit
The above may also need busybox -- not sure, as I had already installed that app.
Click to expand...
Click to collapse
Cool shortcut... Still hoping someone cracks the dialer entry.
Is there any other way to block OTA's other then this menu?
Anyone figure out how to turn off OTA using HiddenMenu on VZW?
There is a "Wi-Fi setting -LG" section, however when I select "OTA Setting" it throws an error, resets to the main menu page.
Alternately, I'm thinking perhaps use Titanium Backup to freeze "System updates 1_13_10_0"?
(Edit: I also froze keychain, as I've seen doing that mentioned several times. This could be good, bad, or indifferent, but i's what I've tried.)
markfm said:
Anyone figure out how to turn off OTA using HiddenMenu on VZW?
There is a "Wi-Fi setting -LG" section, however when I select "OTA Setting" it throws an error, resets to the main menu page.
Alternately, I'm thinking perhaps use Titanium Backup to freeze "System updates 1_13_10_0"?
Click to expand...
Click to collapse
I was thinking TiBu myself. Haven't tried it yet. Froze all the other bloat
LG G3 flies faster than a G6
OG RAZR XT912 got 4.4 before S4
If ##LGSERVICEMENU doesn't work, then it's possible they changed it...Or more likely it's blocked again and will require a framework mod. If that's the case let me know.
xdabbeb said:
If ##LGSERVICEMENU doesn't work, then it's possible they changed it...Or more likely it's blocked again and will require a framework mod. If that's the case let me know.
Click to expand...
Click to collapse
It does not, neither do any variations of the newly found sprint codes, or the standard other varients codes.
The HiddenMenu apk works for some items that appear, others crash the app. For example, on my phone BT_TEST says that Settings has stopped, then returns to the main menu, while Device_Test kills HiddenMenu, though doesn't do anything bad. Progress
So with this, is it possible to stop OTAs yet? Or people are still poking around to find the right combo?
HiddenMenu would likely be a "No" for stopping VZW OTA, since you can't actually get to that setting.
Freezing System updates (and maybe keychain?) will likely work, though I'm waiting for someone more experienced to chime in.
markfm said:
HiddenMenu would likely be a "No" for stopping VZW OTA, since you can't actually get to that setting.
Freezing System updates (and maybe keychain?) will likely work, though I'm waiting for someone more experienced to chime in.
Click to expand...
Click to collapse
Yes, freezing system updates will stop any ota from auto installing, but will also stop any ota notification (you won't know if one is available). LG handles OTA's differently from other manufacturers where you can disable the action of installing an ota separately from being notified of one. Also, on the g2 (and I assume the g3), you had to manually allow the ota to install, it wouldn't do it on its own, but why risk it? Freeze it, and I'm sure you'll still know when there's an ota here on xda immediately.
Doesnt uninstalling bloat also break ota? Could have swore that was the case with one of my older phones
Annoyingduck -- is freezing keychain also good/needed, or is freezing "system updates" probably enough? Thanks!
(Having fun poking at HiddenMenu, interesting things in there.)
markfm said:
Annoyingduck -- is freezing keychain also good/needed, or is freezing "system updates" probably enough? Thanks!
(Having fun poking at HiddenMenu, interesting things in there.)
Click to expand...
Click to collapse
It shouldn't be needed, but all bets are still off because of the many changes Verizon made. I'm comparing the international build and soon one of the other us carrier builds to find out what else big red has pulled. I can tell you with certainty that we are missing some "stock" apks and possibly some sync items that may or may have not been removed to allow some of verizons new cr-apps! That new Verizon messaging app may be the scariest thing I've seen from Verizon in a while... Who knows who's on the other end of that!
I still can't figure out what is hiding the weather app even though it's technically installed. Using a nova shortcut gives you access to it as a temp fix.
annoyingduck said:
-All credit for this method belongs to @xdabbeb from this thread: http://forum.xda-developers.com/showthread.php?t=2467302 All I did was gather the necessary elements and test to see if this would work on the G3 as it did on the G2.
-Please thank him for the great work he has done for finding and executing this method originally for the Verizon G2.
-Another shout out to @rickleasa for extracting and providing the hiddenmenu.apk from the AT&T G3 rom.
So Verizon as usual has hidden some features from the stock lg rom that other variants have access to, in this case the hidden menu that is typically accessed via a code entered into the dialer. This method will unlock this option for us - though you will not be able to access it via the dialer (well, not that I know of...yet), its accessed through adb or terminal.
Step 1: Download the hiddenmenu.apk here: https://mega.co.nz/#!yUgmBRZK!Fy3Iq5_vvdTVpsY9dNXz00Yxv9qH1k8Q-LrTKFVFcGM or at the link at the bottom of the post. The apk is unaltered (not deodexed) from the AT&T build. The Odex file is not needed.
Step 2: Manually past the apk into system/app and set permissions to rw-r-r- using your preferred root file manager, then reboot.
Step 3: From adb: (assuming you have adb set up and operational) type adb shell (then enter), su (then enter), and enter the command, or from terminal: type su (then hit enter) to gain root, then enter the command (press enter after entering or pasting the command). Command here:
am start -a android.intent.action.MAIN -n com.lge.hiddenmenu/com.lge.hiddenmenu.HiddenMenu
-The hidden menu will then open up and your good to start breaking your phone as you see fit!!
-The most common use for this is to fix Knock-on if you ever break it (Flashing international ports has a tendency to break hardware functions). This is done by accessing the hidden menu and going to HW Device Test/Touch Test/Touch Firmware Upgrade. Wait 10 seconds after updating to see if the fix worked.
-You can do lots of damage in there so be careful!! There's also many other fun things to do as well.
If someone finds a dial code that will execute this menu after the apk is installed, please post it :good:
Click to expand...
Click to collapse
Hey Duck- will I be able to access the LG built in Call Reject with this method? So annoying that Verizon has removed it!
Thank you for the reply
Scoob
scooby-snack said:
Hey Duck- will I be able to access the LG built in Call Reject with this method? So annoying that Verizon has removed it!
Thank you for the reply
Scoob
Click to expand...
Click to collapse
Not that I've found. Seems to have been removed from the framework from what I can tell - unless again, it's hidden
Related
Note from developer: If you want to block OTA updates, just use the adb hijack app once (click the button on it once) and then you can run the OTA block part of this script and every other mod for it. The hijacker is right below this V
If you already ran this script but want to apply the mods from an update to the script: Just use this method to be able to rerun the script
NOTE: Anyone who is having problems with drivers, http://forum.xda-developers.com/showthread.php?t=1363652 <-- That explains the two most common problems.
Step by step video from my friend Albert to gain root access:
http://www.youtube.com/watch?v=1zbT1Fj38nE
This also includes a gApps install section in it incase you decide you want to run that.
You may NOT use the included script in your work without atleast asking me as of now, this may change in the future but I dont want to have to hop from thread to thread just to offer support when I can keep the answers organized for all to find. So please just ask first.
Thanks.
Information:
I have gotten zergRush to work on the nook tablet as well as created a batch script for you to run to allow you to root your tablet. This does NOT unlock the bootloader software/hardware checks this is just so you can remove whatever unnecessary crap you wish to get the **** off your device.
Features:
Root (obviously)
Gapps install
De-bloat menu
System mods (New gallery, email, keyboard, and live wallpaper support)
Launcher install (Choice of 3!)
Homecatcher installer (if you install a launcher in the previously mentioned feature)
Root check
USB Vendor ID check.
Needed files for root:
You need drivers first:
http://dl.dropbox.com/u/15069134/usbdrivers.zip
here is an app to pull up usb debugging menu
http://li362-167.members.linode.com/gapps/non_google/tgps_launcher.apk
Code:
<robertely> Also note, that while that box will remain checked, the setting is not persistant.
<robertely> So you have to flick the top 'Usb Development' box twice to get it working.
Download Link for rooting script:
http://dl.dropbox.com/u/15069134/Nook&Zergy.zip
Code:
MD5sum
5df962260797ec4e3d80e107bca1fdb2
How to get adb debugging enabled:
Download the apk provided in the second download link to be able to access the menu *if you're just installing an app the first time, it will pull up the menu anyway but this is more for AFTER you have root as a convienance to access usb debugging and whatnot. Just try to install the apk *or open it if you already set unknown sources* and you will get a prompt to allow non-market apps. Click settings then you should be able to see "Unknown sources" check that followed by going into "Development" and check the 2 "Usb Debugging" boxes and uncheck "auto mount" then your nook tablet is ready to be used in debugging mode.
Instructions to root:
1. Download the "usbdrivers" zip
2. Download the "Nook&Zergy.zip"
3. Extract both to a folder C:\ntroot\
4. Now you should see the following files and folders inside c:\ntroot:
5. Run "runmefirst.bat" and follow the instructions.
6a. When the batch file opens the device manager, If you don't see a broken device icon next to "NOOK Tablet" then you may have some other generic drivers taking over. Not sure how to remove them so you will have to move to another PC that has never had a tablet hooked up and start over.
6b. If you do see NOOK Tablet with a broken device icon.. then right click and choose "update driver". Choose "Let me specify where the driver is" and browse to the c:\ntroot\usbdriver folder and hit ok. It should install and you can click "OK" to the warning about unsigned drivers.
7. Run "NookandZergy.bat" and follow the instructions
7a. If you see a long string of numbers/letters it's your device
Now you should have root.
How to Unroot and Undo system mods: Check out this thread:
Code:
Changelog:
7.5: Added file to block OTA's directly instead of needing titanium backup and did a few script fixes as well as added brianf21's hiddensettings app.
7.0.1: Fixed minor bug where systemui mod was not being properly installed (wrong command was used) NOTE: You will get force closes from the systemui until the script finishes and reboots your tablet.
7.0: Allowed recognition of users that used ADB Hijacker app to allow for system mods to occur even if you didnt choose them with the script originally
6.0: Added ricochet1k's SystemUI mod to have perm back / menu button on status bar + have N automatically redirect to home on first click
6.0: (continued) fixed the sdcard check for users since Zerg causes auto unmount of the sdcard
5.2: Added check for sdcard to install files
5.0.1: Added option for access to the titanium backup and push them to sdcard even if you are already rooted
5.0: Added Titanium backup as well as files needed to block OTA's
4.7: New Market added (3.4.4)
4.6: Added permissions fix.
4.5.5: (Debloater): Added Extreme Debloater option
4.5: Debloated updated to be a customized menu (Has a menu included now) [URL="http://forum.xda-developers.com/showpost.php?p=20229004&postcount=625"]found here[/URL]
4.1: Removed bugs
4.0: Included de-bloater and launcher install (you get to choose!)
3.5: Updated to check for proper USB Vendor ID as well as check for root.
3.0: Updated to include system app replacements (Keyboard, Email, Gallery) As well as adding live wallpapers for other launchers. You need to choose to run this part of the script same as gApps.
2.7: Updated Gapps to latest [9/30/2011]
2.5: Fixed a few minor typo's/bugs with the script
v2.1: Added usb vendor id addition to adb_usb.ini
v2.0: Rewritten script to allow for more user choices; added Gapps installer (thanks anlog); Added busybox installer apk and debug menu puller (allows you to access debugging menu)
v1.1 Updated superuser apk
v1.0: Official release
v.75: Updated to install SU and superuser.apk
v.5: Initial release
Code:
Credits:
Gojimi for his HomeCatcher.apk
Developers of ADW launcher for their APK
Developers of Go launcher for their APK
Syndicate Apps for their Honeycomb Launcher
anlog for finding out how to get nook color drivers to work and general testing
Team Revolutionary for their exploit
B&N for using android like good little sheep
suicideclown for bearing with me while I tried to get it to work on his computer until anlog found the driver fix.
Dsstrainer for the simplified instructions.
How to do it manually instead of running the Nook&Zergy.bat file (for linux or mac users or someone who wants to do it all manually)
Install drivers and follow instructions up until running the batch file then do the following commands in order:
Code:
adb push zergrush /data/local/zergy
adb shell "chmod 755 /data/local/zergy;cd /data/local/;./zergy"
adb wait-for-device install Superuser.apk
adb remount
adb push su /data/local/tmp/
adb shell cd /data/local/tmp;chmod 777 su;cd /;mount -o remount,rw -t rootfs rootfs /;
adb push su /system/bin/su
adb shell chmod 4755 /system/bin/su
Wanna buy me a coffee or something pretty for christmas?
Unroot method can be found here
Rooted nook tablet using my method
Taken from inside of barnes and noble;
{
"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"
}
Indirect said:
Alright, I know you all are going to say "We cant find usb debugging" but allow me to assist you. I found that it's in the development menu of where you enable side-loading of applications so just check that then get the zergrush exploit ran using this.
*I do not own a nook tablet so I cannot check, I just learned alot about it tonight while at a barnes and noble store and the guy who worked there was cool enough to try and help root it with me but since you need adb permissions to run the exploit, I couldn't do anything.
Download Link:
http://dl.dropbox.com/u/15069134/Nook&Zergy.zip
Click to expand...
Click to collapse
Wouldn't still need adb drivers to work in order to do this exploit? If both are possible, I'll gladly buy a nook tablet in order to see if it works (because I intended to buy one anyway if it got root).
I think it might use the nook color drivers but again, I can't test so if anyone has the specific drivers, post them.
Very interesting. I hope someone tries this soon.
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
I am willing to give this a try tonight. want to get in touch? If it works I will record video.
suicideclown said:
I am willing to give this a try tonight. want to get in touch? If it works I will record video.
Click to expand...
Click to collapse
Thanks. Let us know how it goes!
Sent from my Nook Tablet using Tapatalk
Yeah, add me on Gtalk.
[email protected]
Indirect said:
Yeah, add me on Gtalk.
[email protected]
Click to expand...
Click to collapse
I'll help out as well.
gtalk: [email protected]
I tried this quickly and cannot get it working, i have usb debug enabled however the first problem is that the device does not show up in ADB Devices. Second problem or at least i think it might be is that it defaults in to usb storage mode and while plugged in it cannot be altered from that mode. If someone could create a toggle app to change the default i believe this might help. As for the drivers i am looking and will report back later.
ITFloater said:
I tried this quickly and cannot get it working, i have usb debug enabled however the first problem is that the device does not show up in ADB Devices. Second problem or at least i think it might be is that it defaults in to usb storage mode and while plugged in it cannot be altered from that mode. If someone could create a toggle app to change the default i believe this might help. As for the drivers i am looking and will report back later.
Click to expand...
Click to collapse
People hit a wall here last night on irc, May want to hop in #nookcolor to chat about it.
*cough* http://dl.dropbox.com/u/15069134/add-ons.zip *cough* Put that into your android sdk directory and you have the drivers.
Very nice
Sent from my BNTV250 using Tapatalk
905 views, someone must've tried this by now
Sent from my Samsung Legendary 4G, a Universe UTES phone, running "two.three.five"
You need to add the Nook Tablet USB vendor-id to adb_usb.ini, otherwise adb will not see the device. Do not know what the Nook Tablet vendor-id is, but you can find it with serveral utilities.
I just added a zip that I found to add usb vendor ID and gives you the drivers.
Crap...
I got into the application settings menu and was able to allow sideloading, but the window closed before i could turn on usb debugging. I can't figure out how to get back into the menu, since when I try to install an APK it actually does it now instead of spitting out an error.
Looks like I'm going to have to factory reset. I'll try the root right after that and report results here...
BTW, are those drivers 32-bit or 64-bit?
WAIT here is an app to pull up usb debugging menu
http://dl.dropbox.com/u/15069134/me.tennkia.apr-1.apk
Indirect said:
I just added a zip that I found to add usb vendor ID and gives you the drivers.
Click to expand...
Click to collapse
i got USB debugging enabled (i sideloaded AnyCut and put a shortcut to Development on my home screen)
but i cant get adb to recognize my NT... already edited adb_usb.ini with 0x2080 as vendor id.
http://legacyschool.us.to/nookdev/nookcolor-easyADB.exe
^ use that
Indirect said:
http://legacyschool.us.to/nookdev/nookcolor-easyADB.exe
^ use that
Click to expand...
Click to collapse
no dice, still not recognizing NT
This is my first attempt at creating something for users on xda, so be gentle .
Eternityproject has released a fine script for rooting our Motorola RAZR phones on the 4.0.4 update. As a windows-user that used to use batch scripts for everything I could not help but want some more output than just the [rebooting] echo's that the script print on the screen. As a bonus I thought it would be nice to see how long the script will take before my phone is rooted. I have made these wishes into an application, and pedrotorresfilho kindly allowed me to use their script in my application.
So what does it do?
It roots your Motorola RAZR and shows you what the script originally did. It also calculates how long your phone takes to reboot, and shows you how much time you have to get a nice cup of [insert drink here]. Or soda if you prefer that. In theory it is possible to root multiple phones at the same time, which saves time if you have to root 10 RAZRs at once (LOL... as if).
How does one use it?
- Install the program using Microsoft's Awesome ClickOnce distibution system
- Install the Motorola Drivers (Download MotoHelper from here)
- Enable 'Unknown Sources' (on your phone: go to settings, go to security, tick the box next to 'Unknown Sources') (needed to install supersu.apk)
- Enable 'USB Debugging' (on your phone: go to settings, go to developer options, tick the box next to USB Debugging) (needed to communicate with your phone over USB)
- When connecting your phone, please set the USB Mode to 'Media Sync - MTP', to be sure that mounting points won't interfere with the rooting process.
When the application is opened all the connected Android devices will be selected. This means that as soon as you press the 'Root' button, they will be rooted.
In principle the application does nothing more or less than the script. You don't have to have extensive knowledge of adb or android internals, it's just an app that shows the connected devices and a root button . If you are already rooted, it's easy to unroot using SuperSU.
{
"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 links:
Open ClickOnce Application (works only if you have .NET 4.0 installed!)
Download page (use this if the above link does not work/you do not have .NET 4.0)
You can update by opening the application. If there is an update, you will be prompted to download the latest version.
Required:
Windows (with .NET Framework 4.0 Client Profile installed)
Motorola RAZR running ICS (other phones might work, but you will get a warning)
I ask all of you kindly NOT to mirror or reshare the application without my permission. Please share the ClickOnce Application link. Is assures that you are running the latest version!
Credits:
Eternityproject (pedrotorresfilho & kholk) - for writing the script
miloj - For finding the exploit binary to root the phone
Dan Wager - For creating AndroidLib, a .NET wrapper for ADB on Windows
Chainfire - For creating and providing SuperSu and his su binary - http://forum.xda-developers.com/showthread.php?t=1538053
Changelog:
1.0.0.6:
Added more strings to the logging output
Fixed the blocking of the root button if there are no devices selected
Added a splash screen to indicate that the application is actually loading
Changed the location where the splash as well as the credits/welcome screen appear
1.0.0.5:
added credits for Chainfires SuperSU and su
Removed the message that rooting was not successful
Added a few more messages about the script itself (in the script output)
Updated SuperSU and binary to 0.94 (su binary still says it needs to be updated )
1.0.0.4:
The application now properly disposes of the AndroidLib instance, disabled the CheckedItem event on the DeviceList because it was a tad buggy. This won't harm anyone.
1.0.0.3:
Enabled Microsoft ClickOnce Update deployment. If I fix a bug, you are able to update to a less buggy version
DJFliX said:
This is my first attempt at creating something for users on xda, so be gentle .
Credits:
Eternityproject (pedrotorresfilho & kholk) - for writing the script
minoj - For finding/creating the exploit binary to root the phone (please correct me if this is not correct)
Dan Wager - For creating AndroidLib, a .NET wrapper for ADB on Windows
Click to expand...
Click to collapse
+1 congratulations for this work
thanks
My Razr is already rooted, but I can test.
nespresso33 said:
My Razr is already rooted, but I can test.
Click to expand...
Click to collapse
I have sent you a dm .
Can you try with this root method. It's simpler.
http://dev.crackflasher.com/ROOT_TOOLS/razrs_edge_windows.zip
For guys already rooted that wanna test it, first unroot your phone:
Run SuperSU app and press 'full unroot'. If you have superuser app also installed remove it first.
Cheers
whirleyes said:
Can you try with this root method. It's simpler.
http://dev.crackflasher.com/ROOT_TOOLS/razrs_edge_windows.zip
Click to expand...
Click to collapse
Hmm... I will have a look at this. What are your reasons for using this except that it's simple? It's just a matter of preference, right?
pedrotorresfilho said:
For guys already rooted that wanna test it, first unroot your phone:
Run SuperSU app and press 'full unroot'. If you have superuser app also installed remove it first.
Cheers
Click to expand...
Click to collapse
Thanks man! Much appreciated!
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
nespresso33 said:
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
Click to expand...
Click to collapse
Yeah, the installer should be extra user friendly. I should probably just advice users to use the .application link. But the link will only work if .NET client profile is already installed. I'll adjust the message about root, It seems that the library that I use does not query root status from the phone, but rather from it's cache. Maybe I have to update the phone data before querying for root. Thanks for your feedback!
Edit: I am now uploading version 1.0.0.5, I added credits for Chainfires SuperSU, removed the message about the rooting. Too bad my connection is bad (3G in the mountains in La Palma) so bear with me while the updated version is uploaded. Should be up within about 10 minutes, users that already have the application installed will asked to update to the latest version.
nespresso33 said:
Well, I tested the 2 versions ( I got a notification to update your tool ).
It is working great but the installer is strange, ( I had all requirements but for people which don't, it's not great ).
SuperSu and binary are not latest version. And I get at the end a message who say " the phone does not seem to have root" but I had root
Click to expand...
Click to collapse
1. Installed and executed (had to confirm the download since google chrome didn't allow setup.exe files to be directly donwloaded)
2. Upon start it updated.
3. First run the app didn't recognized my connected Razr after changing USB to Media Device - MTP and enable USB debug.
3. Closed and reopened the app and it recognized and root went fine.
Notes: Application said to 'Refresh' when ADB has being enable, but theresn't a Refresh button.
Really nice!
pedrotorresfilho said:
1. Installed and executed (had to confirm the download since google chrome didn't allow setup.exe files to be directly donwloaded)
2. Upon start it updated.
3. First run the app didn't recognized my connected Razr after changing USB to Media Device - MTP and enable USB debug.
3. Closed and reopened the app and it recognized and root went fine.
Notes: Application said to 'Refresh' when ADB has being enable, but theresn't a Refresh button.
Really nice!
Click to expand...
Click to collapse
The refresh button is the button next to root . I'll put a tooltip on that button. Glad to hear all is fine. I'm uploading 1.0.0.5 to polish out the small annoyances and update SuperSU. Thank you so much for testing .
Edit: 1.0.0.5 is out . The download link is now public. Please leave suggestions and improvements in this topic or send me a DM. Thanks!
First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Alternative To Greenify, Native Feature
ggrant3876 said:
First and foremost I am not the developer of this App! I just discovered it and thought those of you missing Greenify might find this useful.
[What's Brevent]
There are a lot of apps which claim to prevent apps from running. However, most of them requires ROOT, or do a system modification via Xposed or patching or unlocked bootloader.
Brevent can app-standby or force-stop apps, prevent apps from running in long time. It doesn't require ROOT, nor modify system. Furthermore, it may doesn't work well on ROOT or modified system. There is an experimental feature to start Brevent Server without adb, please read guide - permissions.
Brevent supports Android 5.0 to Android O DP3, requires "USB debugging" in "developer options". I mainly used it on Google Pixel with Android 7.1.2.
[Simple Guide]
0. (Device) open Brevent, read "Guide"
1. (Device) open Brevent, navigate to "Developer Options", turn on "USB debugging"
2. (PC) Download ADB: https://developer.android.com/studio/releases/platform-tools.html
(If you live in China, you can download it here too: https://developer.android.google.cn/studio/releases/platform-tools.html)
3. (PC) Uncompress, navigate to "platform-tools" directory in Command Line, refer to "Guide - ADB"
4. (PC and Device) connect device and PC with usb cable, type "adb devices" in PC Command Line, and confirm the authorized dialog on Devices if needed
5. (PC) type "adb -d shell sh /data/data/me.piebridge.brevent/brevent.sh" in PC Command Line
[FeedBack]
For any issues, please open an issue at github with logs: https://github.com/brevent/Brevent/issues
1. crash log (in PC's command line): adb -d logcat -d -b crash
2. brevent server log (in PC's command line): adb -d logcat -d -b main -s BreventServer BreventLoader
2.1. enable debug for Brevent Server, type in PC's command line: adb -d shell setprop log.tag.BreventServer DEBUG, then get brevent server log
2.2. disable debug for BreventServer, type in PC's command line: adb -d shell setprop log.tag.BreventServer "" (Note for the back slash)
https://play.google.com/store/apps/details?id=me.piebridge.brevent&hl=en
Click to expand...
Click to collapse
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
kxdaorbit said:
One of the reasons I rate this phone so highly is that there are plenty of 'native' features present that make rooting less necessary.
My phone is a UK Sky Mobile Exynos model, and under 'Maintenance', 'Battery' there is an option to put 'non running' apps to sleep, just like 'Greenify'. I don't know if this is true for other regions or carrier's. Maybe other people can check this to see if it's so for their region and carrier.
Click to expand...
Click to collapse
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
ggrant3876 said:
I agree with you on the phone but there are two features that I miss with root.
1. Titanium Backup - they ability to back up your apps and data. I know there is Samsung Cloud but I'm not a big fan of cloud based services.
2. TWRP - the ability to back up your whole phone and restore it if needed.
Click to expand...
Click to collapse
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
kxdaorbit said:
I get your apprehension about cloud based services, but this is 2017, you'll have to bite the bullet sooner rather than later.
Also don't forget, if you have really super sensitive or personal data that you can't trust to cloud based services, we have 'Smart Switch'. Enables you to make as close to a 'nandroid' backup as is possible, and to store it locally. You can then restore single elements or the whole phone. Thank you Samsung.
Click to expand...
Click to collapse
Yes I read a thread yesterday that said you can use Smart Switch and back it up to your sdcard. It's getting better, I started with the T-Mobile G-1 and the only way to root and even do screenshots was with adb. I learned adb and it has served me well on android, even on the S8+ to get rid of the battery icon I had to run a few commands to get SystenTuner UI to work.
Why don't you just use Samsung built in always sleeping option for apps? Works great
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have rooted, it's not problem.
And if you don't have rooted, no other alternative third-party apps can app-standby other apps or force-stop apps quickly.
I am rooted, but the app doesnt seem to see that I am rooted.
MrPhilo said:
Why don't you just use Samsung built in always sleeping option for apps? Works great
Click to expand...
Click to collapse
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
{
"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"
}
Sent from my SM-G955F using Tapatalk
BratPAQ said:
I agree, s8 already have functions to put your apps to sleep immediately without waiting 3 days.
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
how do you get here ?
crayonyes said:
how do you get here ?
Click to expand...
Click to collapse
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
BratPAQ said:
Settings - Device Maintenance - Battery
Then at the very bottom is "always sleeping apps"
Sent from my SM-G955F using Tapatalk
Click to expand...
Click to collapse
got it, Thanks
Where is the experimental feature to start server without adb?
mrQQ said:
Where is the experimental feature to start server without adb?
Click to expand...
Click to collapse
suku_patel_22 said:
I am rooted, but the app doesnt seem to see that I am rooted.
Click to expand...
Click to collapse
]
Compusmurf said:
according to the info, you have to regrant permissions thru ADB every darn reboot or it's useless.
Click to expand...
Click to collapse
If you have Root
Just press "back" about 6 times
And then a new menu appears
There you press on "ROOT"....
Tab A7 stock rootless setup
model used: Tab A7 Lite SM-T220
Just a quick article for this nicely sized 8.7" tablet. It's a baby tablet, not wasting time with rooting We want:
* debloating
* better battery
* better privacy
* call recording
* disk encryption
* tweaks
RootingNo rooting. No logins, not even Google login, that's the plan. FDroid, Aurora, Vanced manager to deploy all you need. No contacts, no SMS, no location, nothing to protect.
ModulesMagisk-
XPosed-
Apps* AdGuard -> supreme adblocker and firewall. Set VPN approach (rootless friendly, assuming device will stay at home), turn on HTTPS and turn off internet for all apps. Then enable few (browser, youtube, aurora) specifically.
* YouTube Vanced -> YouTube without ads and sponsor blocks.. install in non root mode, and remove the existing originals
* (optional) MiXplorer -> best file manager, replaces spyware ES File explorer you had before
* F-Droid -> open source apps
* Aurora -> all apps
DebloatingWhat the script does:
* choose 8 categories of app removal, in the beginning of the file
for each say 0=skip 1=remove 2=revert back
* use more switch to disable some questionable/helpful stuff
* disable up to 70 apps with possibility to revert back
I usually cook these files carefully, here i just removed non existing packages, added existing vendor packages. Vendor garbage gets uninstalled straight away, majority of packages is disabled in non-root mode (per user) so it can be reenabled later. You can edit the file.
unzip the file to some folder
adb shell as it's plugged to PC and authorized (and usb debugging in developer otions on)
go to the folder with script
cp TabA7_cleanup.sh /data/local/tmp
chmod +x /data/local/tmp/TabA7_cleanup.sh
/data/local/tmp/TabA7_cleanup.sh;
Tested ok on August Android 11 EU firmware. It produced no errors (=packages relevant), but there could be regional differences, producing exceptions in your case. See other comments below if the instructions are unclear.
Download: (file attached)
BatteryBattery saving:
turn off location
turn off permissions and app usage for usual snitches
in Adguard turn off WIFI/mobile for each app (will be the default), then reenable few - advantage: no ads in games, no stupid accidental payments. Also set WIFI/mobile off when screen off -> tablet won't do anything, just keep idle for days hopefully
don't even enable GMS, this device can be a good throwawy tablet with no login to ANY service, without encryption, just pure gamepad.... likely no password/PIN to unlock. It's with slow CPU but games work nicely. It's not even slower than S4 flagship tablet honestly.
hi, thanks for the guide, very insightful with me transitioning from iOS.
My only question is the script, I’ve downloaded ABD and can shell into my device. However I’m having issues when copying the script, it keeps coming up saying invalid path, I’ve looked everywhere for a tutorial but with me having limited knowledge I’m at a dead end
any help greatly appreciated
Herb291 said:
hi, thanks for the guide, very insightful with me transitioning from iOS.
My only question is the script, I’ve downloaded ABD and can shell into my device. However I’m having issues when copying the script, it keeps coming up saying invalid path, I’ve looked everywhere for a tutorial but with me having limited knowledge I’m at a dead end
any help greatly appreciated
Click to expand...
Click to collapse
i just flashed the new firmware and did it again, no problem. First i copied the script from Windows to somewhere on Android (/storage/emulated/0 or similar "noexec" quasi-sd card location), and then moved it to a location from where it can be executed. The location should work and is generally recommended. You can find another one /data/local, /tmp or whatever is there. Or use adb push <PC_file> <target_directory>. Or post the screenshot. This should be a trivial issue and can't stop you.
{
"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"
}
getting this error
raxahasan0077 said:
View attachment 5456865getting this error
Click to expand...
Click to collapse
Place the script on the tablet in an easy to remember location.
Open Powershell:
“adb shell” or “./abd shell” (whichever works)
“Cp /storage/emulated/0/FILELOCATION/TabA7_cleanup.sh /data/local/tmp”
then follow the rest of the instructions
now getting this error
raxahasan0077 said:
now getting this errorView attachment 5456963
Click to expand...
Click to collapse
Is your USB debugging turned on in the dev settings, did you hit authorise on your device when you first plugged it in?
you can check if you’re device is authorised with “adb devices”
edit: not sure if it matters but try a lowercase cp
Herb291 said:
Is your USB debugging turned on in the dev settings, did you hit authorise on your device when you first plugged it in?
you can check if you’re device is authorised with “adb devices”
edit: not sure if it matters but try a lowercase cp
Click to expand...
Click to collapse
yeah lowercase cp works
Working with LADB ( no computer needed)
https://www.xda-developers.com/debloat-your-phone-run-adb-shell-commands-no-root-no-pc/
Download: https://disk.yandex.com/d/H02YifGGtrErbw
////////////Run an .sh file to install ///////////
cd /sdcard
cp cleanup.sh /data/local/tmp
cd /data/local/tmp
ls -l
chmod +x /data/local/tmp/cleanup.sh
ls -l
./cleanup.sh
/////////
Download: https://disk.yandex.com/d/NcQMhFp73OpwXw
( and run .sh script with LADB)
Tips howto install LADB:
important! Always use "Open in split screen view” for pairing devices. (only first connection, next time don't need)
View attachment 5457089
@tom.android have you removed all theese 41 apps and the tablet functions ok, without any problems ? Is there any real benefit in performance and especially in lagging ?
Reply: @nikoum
Just removed (switch off) my unused app, sorry not help for good performance but no trouble.
Note: LADB
https://forum.xda-developers.com/attachments/ladb_v1-7_test-zip.5457295/
How dose this work without rooting? When I try to run the script from ADB i get Can't execute: permission denied?
I run "cmd", then "adb shell" and then "pm uninstall --user 0 <package name>". Make sure in developer options to check USB debugging to on and when connecting device with usb cable, authorize the conneftion, when asked by the phone.
doggydog2 said:
Tab A7 stock rootless setup
model used: Tab A7 Lite SM-T220
Just a quick article for this nicely sized 8.7" tablet. It's a baby tablet, not wasting time with rooting We want:
* debloating
* better battery
* better privacy
* call recording
* disk encryption
* tweaks
RootingNo rooting. No logins, not even Google login, that's the plan. FDroid, Aurora, Vanced manager to deploy all you need. No contacts, no SMS, no location, nothing to protect.
ModulesMagisk-
XPosed-
Apps* AdGuard -> supreme adblocker and firewall. Set VPN approach (rootless friendly, assuming device will stay at home), turn on HTTPS and turn off internet for all apps. Then enable few (browser, youtube, aurora) specifically.
* YouTube Vanced -> YouTube without ads and sponsor blocks.. install in non root mode, and remove the existing originals
* (optional) MiXplorer -> best file manager, replaces spyware ES File explorer you had before
* F-Droid -> open source apps
* Aurora -> all apps
DebloatingWhat the script does:
* choose 8 categories of app removal, in the beginning of the file
for each say 0=skip 1=remove 2=revert back
* use more switch to disable some questionable/helpful stuff
* disable up to 70 apps with possibility to revert back
I usually cook these files carefully, here i just removed non existing packages, added existing vendor packages. Vendor garbage gets uninstalled straight away, majority of packages is disabled in non-root mode (per user) so it can be reenabled later. You can edit the file.
unzip the file to some folder
adb shell as it's plugged to PC and authorized
go to the folder with script
cp TabA7_cleanup.sh /data/local/tmp
chmod +x /data/local/tmp/TabA7_cleanup.sh
/data/local/tmp/TabA7_cleanup.sh;
Tested ok on August Android 11 EU firmware. It produced no errors (=packages relevant), but there could be regional differences.
Download: (file attached)
BatteryBattery saving:
turn off location
turn off permissions and app usage for usual snitches
in Adguard turn off WIFI/mobile for each app (will be the default), then reenable few - advantage: no ads in games, no stupid accidental payments. Also set WIFI/mobile off when screen off -> tablet won't do anything, just keep idle for days hopefully
don't even enable GMS, this device can be a good throwawy tablet with no login to ANY service, without encryption, just pure gamepad.... likely no password/PIN to unlock. It's with slow CPU but games work nicely. It's not even slower than S4 flagship tablet honestly.
Click to expand...
Click to collapse
How do I get the script file to.run from ADB? I get permission denied
TheDroidKid said:
How do I get the script file to.run from ADB? I get permission denied
Click to expand...
Click to collapse
that's literally discussed above incl all common mistakes, if you think it's unique, please post a screenshot.
Your right got it working. Didn't releaize it was a big deal not to have it in /tmp
I keep trying to do the cp step but it keeps saying no such file or directory.
I checked my tablet with MiX and there's no local folder on data... What am I doing wrong here?
Is better privacy only possible with rooting? I want to disable the radio entirely and remove all of the Google apps.
Elzbach said:
Is better privacy only possible with rooting? I want to disable the radio entirely and remove all of the Google apps.
Click to expand...
Click to collapse
i disabled google, and using Aurora without root. With no logins, no PIM data, no location tracking, there's almost no data to steal. But if I was using it as a mobile phone, with logins, contacts etc, i'd have to root.
doggydog2 said:
i disabled google, and using Aurora without root. With no logins, no PIM data, no location tracking, there's almost no data to steal. But if I was using it as a mobile phone, with logins, contacts etc, i'd have to root.
Click to expand...
Click to collapse
I'm not using it as a phone and there is still no data to steal, but I still want to get rid of those things. I want to completely remove the tracking apps regardless of how little there is to track because they are bloat. I want to completely disable the radio, the microphone, gps, and blu tooth. I don't even want wireless internet connections to remain.
How to use?
1. Enable ADB Debugging from Fire TV settings
2. In this app, add the adb commands that you want to execute on every boot
3. Set whether you want to display a Toast message on completion of command execution
4. Test the script if you want by pressing "Test Script" button.
5. Apply the configs by pressing the apply button.
Support the work by purchasing it from here
Note: when you run this app for the first time, you should press the test script button, so that app can acquire adb permission. If you don't do this, then the adb permission prompt would appear when you boot the stick for the first time, after installing and opening this app.
That's all
Also note that, the commands you'll write here should be without "adb shell" prefix.
For example,
you have to write
echo "Hello World"
and not
adb shell echo "Hello World"
{
"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"
}
(or multiple commands separated by semi-colon ' ; ' )
Awesome thanks!
Is it possible to combine commands with ; or add a delay?
Spamm00r said:
Awesome thanks!
Is it possible to combine commands with ; or add a delay?
Click to expand...
Click to collapse
Yes you can add multiple commands with ; and add a delay using sleep command.
Example,
sleep 3; echo "I'm here after 3 seconds";
Shaikh Amaan FM said:
Yes you can add multiple commands with ; and add a delay using sleep command.
Example,
sleep 3; echo "I'm here after 3 seconds";
Click to expand...
Click to collapse
Perfect!
Did you test wether you can use this app to issue "adb tcpip 5555" command at bot so that the adb wifi tasker function can do the rest? Thatway we would have adb shell on a non rooted device all the time.
Spamm00r said:
Perfect!
Click to expand...
Click to collapse
let me know if you are able to get your work done
Spamm00r said:
Perfect!
Did you test wether you can use this app to issue "adb tcpip 5555" command at bot so that the adb wifi tasker function can do the rest? Thatway we would have adb shell on a non rooted device all the time.
Click to expand...
Click to collapse
The issue with Tasker is something else as far as I can see. May be because Tasker have subscription checking thing in it and it needs Google Libraries which are not available in fire os.
So I finally was able to test this. The app does work ok.
I'd like to be able to execute these scripts not only at boot. For example like when you press test script, I'd like to be able to run the app anytime I want the script to execute.
Can you please also add an setting that allows the scripts to be executed by just opening the app, so that you are not limited to run these scripts only at boot or when you manually press " test script". So we could use these scripts anytime we run this app for example via Tasker.
Why does the shell execution work with this app but not with taskers adb shell?
Spamm00r said:
So I finally was able to test this. The app does work ok.
I'd like to be able to execute these scripts not only at boot. For example like when you press test script, I'd like to be able to run the app anytime I want the script to execute.
Can you please also add an setting that allows the scripts to be executed by just opening the app, so that you are not limited to run these scripts only at boot or when you manually press " test script". So we could use these scripts anytime we run this app for example via Tasker.
Why does the shell execution work with this app but not with taskers adb shell?
Click to expand...
Click to collapse
Are you able to use Tasker in the stick?
I tried in my device and it won't even show a simple Toast and possible reason as I said is that Tasker have subscription checking thing in it and that requires Play services which are missing in Fire OS. So unless you have direct purchased version of Tasker or unless you install Play services in it, I don't see any good way of running Tasker in it.
Shaikh Amaan FM said:
Are you able to use Tasker in the stick?
I tried in my device and it won't even show a simple Toast and possible reason as I said is that Tasker have subscription checking thing in it and that requires Play services which are missing in Fire OS. So unless you have direct purchased version of Tasker or unless you install Play services in it, I don't see any good way of running Tasker in it.
Click to expand...
Click to collapse
Yes I have Tasker running on FireTV 4K without play service. You can download an apk with 7 day trial directly from the tasker website and it works without playstore. If it has issues with subscription or trial expired, it will tell so and refuse to execute some advanced features.
I can run intents and stuff with tasker just fine, but as Fire TV has no Accessibility service installed, you can not use most of the nice features and plugins of Tasker. Issuing shell commands for example does not work. so I can not issue any keyinput with tasker. That's why I have to rely on your app.
With your app however I was able to completely avoid tasker for now.
I used Tasker to run an intent that opens a youtube link. Now I run this intent from your app. Also i can now issue keyinput with your app. With Tasker that was not possible due to missing accessibility service, which Tasker relies on.
How is your app able to issue keyinput via shell, while tasker can not due to mssing accessibility services? Maybe you can make your app more advanced and allow it to be used as a proxy for issuing shell keyinput on devices without accessibility service. This is the one single reason why I wish i had root on this device. Just to have accessibility service back, which Amazon removed in the recent firmware versions.
I use input to press home key, which makes Fire TV switch the HDMI input of the TV to itself. Now Whenever I start the tv, Fire TV automatically switches input to itself and starts playing youtube.
What I now also want is to be able to use your app also after boot, as I need to switch input and issue keyinput after boot while running several times. Thats why I asked you to add an option to runn it also after boot.
Because if I press "test script" keyinput also works with your app. But not with Tasker.
Will it work, if I open your app with intent "android.intent.action.MAIN"? Will it execute the shell script like when at boot? if yes, then I will try to run this intent from Tasker.
Also It would be good if it was possible to have multiple scripts that you can execute so that you are not stuck with one single script. For example allow to save script a, b, c etc, and then have an intent to be ebale to run a specific script a, b or c. etc..
Your script is very helpful and solves a big problems that amazon has introduced by cutting accesisbility service. Without your app, fire tv would be so useless for me. Thanks for releasing it.
Spamm00r said:
What I now also want is to be able to use your app also after boot, as I need to switch input and issue keyinput after boot while running several times. Thats why I asked you to add an option to runn it also after boot.
Because if I press "test script" keyinput also works with your app. But not with Tasker.
Click to expand...
Click to collapse
Yes this can be done, but i'm busy in something else, so it might take a while
Spamm00r said:
Also It would be good if it was possible to have multiple scripts that you can execute so that you are not stuck with one single script.
Click to expand...
Click to collapse
For having multiple scripts, currently I think you can do it by creating different bash files containing scripts and store them somewhere in Fire Device's storage and then execute them (but probably you'll face problem in giving execute permission to those bash files), this process can be made easier but as I said would take time.
Shaikh Amaan FM said:
Yes this can be done, but i'm busy in something else, so it might take a while
For having multiple scripts, currently I think you can do it by creating different bash files containing scripts and store them somewhere in Fire Device's storage and then execute them (but probably you'll face problem in giving execute permission to those bash files), this process can be made easier but as I said would take time.
Click to expand...
Click to collapse
OK no problem. Take your time.
I don't think that you can execute scripts without root. How does your app execute these scripts without root permissions?
Also sometimes the script is not executed, not at boot and not when I press "test script". I think maybe adb is being blocked by some other app? I have to look into why this happens.
Spamm00r said:
OK no problem. Take your time.
I don't think that you can execute scripts without root. How does your app execute these scripts without root permissions?
Also sometimes the script is not executed, not at boot and not when I press "test script". I think maybe adb is being blocked by some other app? I have to look into why this happens.
Click to expand...
Click to collapse
Which fire device do you have and what's the Fire OS version in it. App doesn't works in Fire OS 5, in Fire OS 6, you have to make sure that no other device/service is connected to ADB, In Fire OS 7, I didn't saw any issue
Shaikh Amaan FM said:
Which fire device do you have and what's the Fire OS version in it. App doesn't works in Fire OS 5, in Fire OS 6, you have to make sure that no other device/service is connected to ADB, In Fire OS 7, I didn't saw any issue
Click to expand...
Click to collapse
I have Fire TV Stick 4k and OS is 6. I figured out why it sometimes doe snot work. it is because ADB is occupied by another app. If I disable and enable adb debugging and thatway break any exisiting connections, it works fine. I just have to make sure that no other app blocks adb, as apparently only 1 app can be connected to adb at a time.
That might be another point of improvement, to make sure that adb is not left occupied.
Spamm00r said:
I have Fire TV Stick 4k and OS is 6. I figured out why it sometimes doe snot work. it is because ADB is occupied by another app. If I disable and enable adb debugging and thatway break any exisiting connections, it works fine. I just have to make sure that no other app blocks adb, as apparently only 1 app can be connected to adb at a time.
That might be another point of improvement, to make sure that adb is not left occupied.
Click to expand...
Click to collapse
In fire os 7, there's no such issue. But yeah in fire os 6 I have tested, only one service or device can connect to adb at a time, and I don't think there's anything I can do about it
Shaikh Amaan FM said:
In fire os 7, there's no such issue. But yeah in fire os 6 I have tested, only one service or device can connect to adb at a time, and I don't think there's anything I can do about it
Click to expand...
Click to collapse
My exact Fire OS is: Fire OS 6.2.8.1
WHich Fire TV Stick has OS 7?
Being able to connect multiple clients to adb is a big step forward. Right now I have to manually toggle adb access to allow other tools to connect to adb. This is a big problem.
Spamm00r said:
My exact Fire OS is: Fire OS 6.2.8.1
WHich Fire TV Stick has OS 7?
Being able to connect multiple clients to adb is a big step forward. Right now I have to manually toggle adb access to allow other tools to connect to adb. This is a big problem.
Click to expand...
Click to collapse
I have Fire Stick 3rd gen.
New devices including Fire Stick Lite are running Fire OS 7.x and I can connect multiple different devices/services to adb at the same time without any issue.
Curious that the Lite has newer Fire OS Version than man other devices. In this case it would be desirable to update, but until then how can make sure that your app or any other app disconnects form adb and gives it free to use for other applications.
Right now I have to manually go to developer settings and toggle ADB off and on to make it available to other apps. Otherwise, adb will be occupied by the last app that used it.
Is it possible to automate this? Adding "disconnect" to the shell command didn't help.
Spamm00r said:
Curious that the Lite has newer Fire OS Version than man other devices. In this case it would be desirable to update, but until then how can make sure that your app or any other app disconnects form adb and gives it free to use for other applications.
Right now I have to manually go to developer settings and toggle ADB off and on to make it available to other apps. Otherwise, adb will be occupied by the last app that used it.
Is it possible to automate this? Adding "disconnect" to the shell command didn't help.
Click to expand...
Click to collapse
Look for force stopping the application through adb commands.
I have managed to make the app start also after boot via Taskers app action. But the script is only executed after manually pressing the "test Script" button.
What exact intent action is executed by pressing the "Test Script" button? From the xml file I can only see "com.asfmapps.firetv_adbonboot.MainActivity".
I have also tried to send android.intent.action.BOOT_COMPLETED to your app to make it think it just started up but that also does not make your app to execute the script automatically.
What intent is your app listening for to execute the script? And ho do I issue it via shell or tasker?
Hi,
I'm trying to echo to sys/class/display/mode so I can change the resolution on boot.
When I test the script it shows 'permission denied'. It's an android box so it won't work?