/system/bin Commands & Root Availability??? - Android General

Okay so here's the story guys, I am simply baffled at the fact I am holding a ZTE Majesty Pro Android MM 6.0 handset.
I look through my /system/bin for cmd interface type programs & to my surprise I see a lot of friendly & functional tools I would even see a few on a device with BusyBox installed, so here is where my confusion starts,
I can call the 'am' command from terminal,
I can call the 'pm' one from ADB with permissions over any user app (not sure about system apps my guess is probably since I got AppOps running with ADB & the pm command)
I can chroot and the 'toolbox' command spits out a majority of BusyBox, + the 'cat' command is in there, along with the weirdest command thusfar
the 'ss' command (Im assuming safestrap?) it asked me for 64-bit ELF files.
I'd be happy to provide any other specs for my device if needed, would appreciate anyone willing to help me use p0six to root this internally encrypted pile of crap.

LilAnt530 said:
Okay so here's the story guys, I am simply baffled at the fact I am holding a ZTE Majesty Pro Android MM 6.0 handset.
I look through my /system/bin for cmd interface type programs & to my surprise I see a lot of friendly & functional tools I would even see a few on a device with BusyBox installed, so here is where my confusion starts,
I can call the 'am' command from terminal,
I can call the 'pm' one from ADB with permissions over any user app (not sure about system apps my guess is probably since I got AppOps running with ADB & the pm command)
I can chroot and the 'toolbox' command spits out a majority of BusyBox, + the 'cat' command is in there, along with the weirdest command thusfar
the 'ss' command (Im assuming safestrap?) it asked me for 64-bit ELF files.
I'd be happy to provide any other specs for my device if needed, would appreciate anyone willing to help me use p0six to root this internally encrypted pile of crap.
Click to expand...
Click to collapse
I would love to. However i have the majesty pro on 7.1.1. What is p0six

ATACELITE said:
I would love to. However i have the majesty pro on 7.1.1. What is p0six
Click to expand...
Click to collapse
https://en.m.wikipedia.org/wiki/POSIX
Did you purchase your majesty pro with 7.1.1 on it already?

Did you purchase your majesty pro with 7.1.1 on it already?[/QUOTE said:
Yes siree
Click to expand...
Click to collapse

ATACELITE said:
Did you purchase your majesty pro with 7.1.1 on it already?[/QUOTE said:
Yes siree
Click to expand...
Click to collapse
Awh man, i wonder if there's an update
Click to expand...
Click to collapse

Related

One Click Root & Recovery for the Epic 4G! v2.5.5 Now has ClockworkMod Redirector!

One Click Root & Recovery for the Epic 4G! v2.5.5 Now has ClockworkMod Redirector!
Here's a new one click root. 2.4.0 now flashes clockworkmod recovery for you. It's also a little less likely to fail, and is tested to work on Froyo.
It will also work correctly if you are on a pre-rooted kernel. It will install superuser, busybox, and clockworkmod.
http://firon.net/xda/one.click.root.exploitv2.5.5.zip
Here's 2.5.0 of the one click root, now with the clockwork redirector integrated.
I cleaned up noobnl's script a little bit and ensured that adbd would run as root when booted into recovery. Also made sure we symlinked every single applet that recovery's busybox provides.
Now the one click also avoids pushing playlogo unless it detects that you have the old joeykrim root installed, to avoid any potential issues with future froyo releases.
Linux and Mac users users chmod +x run.sh and run it
THANKS FIRON
Here's 2.2.7, that simplifies the root process thanks to the discoveries here: http://forum.xda-developers.com/showthread.php?t=800483
I also increased the timeout after running the root (fails less), moved more things to /system/xbin to reduce the risk of breaking things, and removes all the old files leftover from joeykrim's root (including his modified playlogo that runs at boot every time).
It also means your system will no longer be mounted as read-only every time you reboot and there's no more problems with jk-su overwriting your existing su binary.
1. you need samsung galaxy s drivers
32-bit drivers: http://firon.net/xda/Samsung_Mobile_Driver_V1.3.800_For_SPH-d700_Epic_4G.zip
64-bit drivers: http://firon.net/xda/usb_drivers_GalaxyS_x64.zip
2. push MENU, select Applications > Development, then enable USB debugging.
3. extract and run run.bat
4. enjoy!
v2.2.4 added busybox and the remount script and fixes sprint animation not showing
2.2.5 superuser.apk & su added!
v2.2.6 installs busybox to xbin
uninstaller http://firon.net/xda/one.click.stock.flasher.&.root.uninstaller-di18.zip
Any word on whether the OTA update (Hotspot/4G/AmazonMP3) breaks or makes this method not work?
lordcyrus said:
Any word on whether the OTA update (Hotspot/4G/AmazonMP3) breaks or makes this method not work?
Click to expand...
Click to collapse
no it doesn't break it
Gonna test this right now!
Sweet!!! Thanks!!! Going to do this after i get my epic after work.
Longest day ever!!!
OP. There is a really big step missing here. Guess what it is?
Hint: You need to have set the path in the command prompt for adb in order to work.
Fixter said:
Gonna test this right now!
Click to expand...
Click to collapse
You first Boriqua.
Fixter said:
OP. There is a really big step missing here. Guess what it is?
Hint: You need to have set the path in the command prompt for adb in order to work.
Click to expand...
Click to collapse
updated the post and dl link!
NOOB question, how do you know if your 32-bit, or 64-bit? Running Windows 7 basic on a net book.
Will this nand unlock?
vazquezcmp said:
NOOB question, how do you know if your 32-bit, or 64-bit? Running Windows 7 basic on a net book.
Click to expand...
Click to collapse
Odds are its 32 but heres how to check:
Click Start
Right Click Computer
Click Properties
Then look where it says System Type
32. Thanks man. I'm next.
Hmm.. Still not working.
Bring on the custom ROM's
Alright, well you needed to copy the folder to the Tools folder of the SDK.
I'm typically not brain dead but I'm lost
Working on Windows XP....
A) Installed the 32 bit drivers (strange that when I plug the phone into the USB cord the computer doesn't ever seem to acknowledge that I did so as it did with my BB?)
B) Tried to run the RUN and RUN 2 but I keep getting messages that no device is detected.
Obviously I'm missing something somewhere???????
jfenton57 said:
I'm typically not brain dead but I'm lost
Working on Windows XP....
A) Installed the 32 bit drivers (strange that when I plug the phone into the USB cord the computer doesn't ever seem to acknowledge that I did so as it did with my BB?)
B) Tried to run the RUN and RUN 2 but I keep getting messages that no device is detected.
Obviously I'm missing something somewhere???????
Click to expand...
Click to collapse
I'm not even seeing RUN2.
My phone went completely black. Not responding to anything.
I can see the device with adb devices and ran run.bat and then run2.bat and it rebooted the phone but I don't think I have root. How can I test it? I downloaded wireless tether and it doesn't broadcast.
GrandMstrBud said:
I can see the device with adb devices and ran run.bat and then run2.bat and it rebooted the phone but I don't think I have root. How can I test it? I downloaded wireless tether and it doesn't broadcast.
Click to expand...
Click to collapse
Download Titanium Backup.

Battery Status on computer

IGNORE THIS, NEWER VERSION(S) ARE HERE: http://forum.xda-developers.com/android/development/phone-s-battery-status-computer-screen-t3070549
I have made a program to display the percentage of your phone on your computer. Requirements:
Computer that can run bash
USB-to-phone cable
ADB enabled on phone
Has been tested on the following:
LG P716 Jelly bean stock- One Works the other doesn't
LG P716 KitKat - Works
LG P500 with CM11 and rooted- Works
Samsung S3 stock - Doesn't work
Your help is greatly appreciated to porting it to Windows/Mac and adding new devices.
wilk.gr76 said:
I have made a program to display the percentage of your phone on your computer. Requirements:
Computer that can run bash
USB-to-phone cable
ADB enabled on phone
Has been tested on the following:
LG P716 Jelly bean stock- One Works the other doesn't
LG P716 KitKat - Works
LG P500 with CM11 and rooted- Works
Samsung S3 stock - Doesn't work
Your help is greatly appreciated to porting it to Windows/Mac and adding new devices.
Click to expand...
Click to collapse
Don't get me wrong but do you really have a use for it or is it just about improving your development skills ?
LS.xD said:
Don't get me wrong but do you really have a use for it or is it just about improving your development skills ?
Click to expand...
Click to collapse
I do. If I plug my phone in, and then turn on the display to see how far it has charged, the battery percentage is DROPPING! So, I created this. If you want faster charging than your USB port, use ADB over WiFi. But this did help me hone my skills.
wilk.gr76 said:
I do. If I plug my phone in, and then turn on the display to see how far it has charged, the battery percentage is DROPPING! So, I created this. If you want faster charging than your USB port, use ADB over WiFi. But this did help me hone my skills.
Click to expand...
Click to collapse
Pretty cool for that specific purpose I just downloaded the zip and was just about starting my laptop to test it BUT the archive is damaged and i can't extract it May you please check the archive's integrity and upload it again?!
Sure!
LS.xD said:
Pretty cool for that specific purpose I just downloaded the zip and was just about starting my laptop to test it BUT the archive is damaged and i can't extract it May you please check the archive's integrity and upload it again?!
Click to expand...
Click to collapse
Did that! Just make sure you can run bash. Your computer'll need linux or mac os x (not sure about mac)
If it helps, please press thanks.
wilk.gr76 said:
Did that! Just make sure you can run bash. Your computer'll need linux or mac os x (not sure about mac)
Click to expand...
Click to collapse
BASH?! Never heard about it...
Manjaro Linux should be fine for it
LS.xD said:
Pretty cool for that specific purpose I just downloaded the zip and was just about starting my laptop to test it BUT the archive is damaged and i can't extract it May you please check the archive's integrity and upload it again?!
Click to expand...
Click to collapse
It is nice to get feedback so quicly! I expected to have no replies by Sunday, yet I get one in the first 5 mins! "Vielen Dank!" (I saw the german flag by your name...)
LS.xD said:
BASH?! Never heard about it...
Manjaro Linux should be fine for it
Click to expand...
Click to collapse
Open the terminal, and its most likely your using bash. Bourne-Again SHell.
Just wondering, what is the orange "OP" rectangle next to "Junior Member", to the left of my post?
wilk.gr76 said:
Open the terminal, and its most likely your using bash. Bourne-Again SHell.
Just wondering, what is the orange "OP" rectangle next to "Junior Member", to the left of my post?
Click to expand...
Click to collapse
OP = overpowered or may be "Original Poster"
Is it possible that your tool only runs on 32Bit systems? I use 64Bit OS with multilib and no chance to make it fly / run or whatever you like
LS.xD said:
OP = overpowered or may be "Original Poster"
Is it possible that your tool only runs on 32Bit systems? I use 64Bit OS with multilib and no chance to make it fly / run or whatever you like
Click to expand...
Click to collapse
Yes it is built for 32bit systems but you should be able to run it on 64 bit as well. You need to unzip everything of course and make adb and dialog (in the same folder as the script) executable. The command is chmod +x adb && chmod +x dialog
To change it to 64-bit, you'll need to replace the adb and dialog files with the 64-bit versions.
You might need ia32-libs or somthing like that.
Also, OP I think it overpowering. You shall port it to Windows. You shall thank me. LOL, don't have to do it.
wilk.gr76 said:
Yes it is built for 32bit systems but you should be able to run it on 64 bit as well. You need to unzip everything of course and make adb and dialog (in the same folder as the script) executable. The command is chmod +x adb && chmod +x dialog
To change it to 64-bit, you'll need to replace the adb and dialog files with the 64-bit versions.
You might need ia32-libs or somthing like that.
Also, OP I think it overpowering. You shall port it to Windows. You shall thank me. LOL, don't have to do it.
Click to expand...
Click to collapse
Im familiar with chmod Commandline version works well (see signature for phone's setups) while the guy version causes a never ending error output:
libgtk-3.so.0 shared libraries can't be found . All files are present in my Linux so I really have no clue, why i can't open it.
LS.xD said:
Im familiar with chmod Commandline version works well (see signature for phone's setups) while the guy version causes a never ending error output:
libgtk-3.so.0 shared libraries can't be found . All files are present in my Linux so I really have no clue, why i can't open it.
Click to expand...
Click to collapse
Are you using GNOME? You might need to install libgtk. But, like the readme file says, this is bit is still alpha (it's more beta than beta.. If that makes sense).
But if it helped, please press the " Thanks" button
wilk.gr76 said:
Are you using GNOME? You might need to install libgtk. But, like the readme file says, this is bit is still alpha (it's more beta than beta.. If that makes sense).
But if it helped, please press the " Thanks" button
Click to expand...
Click to collapse
Its really weird as the libs "missing" are all installed. I use KDE.
LS.xD said:
Its really weird as the libs "missing" are all installed. I use KDE.
Click to expand...
Click to collapse
It's pretty strange that it used "can't" instead of "cannot". Maybe try using gnome. I dunno, it works on mine.
I'm moving this to a DevDB now.
Has been moved to http://forum.xda-developers.com/and...ter-screen-t3070549/post59841376#post59841376

[SOLVED] Android Trojan.Gorilla.AM or Guerrilla.AM on my device OEM launcher...

(NOTE: this post is a duplicate of a similar thread I started on the Android Central user forum)
Hello everyone,
In the continuing saga of the Leagoo T5C i bought before the holidays from GearBest, I've seen the good (the price and overall build quality, along with a reasonably good user experience), the bad (some notifications that I just can't get rid of, among other things), and I now present you the ugly: after watching a review video on YouTube about my device, I learned that it came loaded with a Trojan called "Gorilla.AM"...
***EDIT: apparently, the Trojan's name could actually be "Guerrilla.AM", I'm not sure.***
Needless to say, I did as the tester had, and installed Malwarebytes, which, sure enough, found the exact same Trojan on my device.
You can watch the video here: https://www.youtube.com/watch?v=R5l3z7BvBtk
It so happens that it's embedded in Leagoo's own application launcher, called Sujet (in French; maybe it's called "Subject" in English, I don't know). I can force quit the application, since I use another launcher called Apex (good pick, by the way), but Malwarebytes can't seem to shake the Trojan off my device nonetheless.
A quick search on Google gives very little in the way of information about this malware, but I'd like to be on the safe side, so I came here.
Any contribution would be welcome at this stage.
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Lannig said:
Hi. I've seen your post on a french-speaking forum but for my own reasons I don't want to help there, too many morons.
Leagoo is well-known for smartphones with built-in spyware/adware. I've had both a Z5 and a M5 and both had such crap in the stock firmware.
This one is new to me but you'll probably have to follow the same steps to get rid of it.
Try
Code:
adb shell pm disable <internal name of that launcher>
first (from a PC connected to the device with ADB - zillions of tutorials available for this)
The internal name can be found by guessing or by using one of the many apps that will show you the information. One is https://play.google.com/store/apps/details?id=com.csdroid.pkg
If that fails, try adding "-k -user 0" to the command line.
If it fails again (denied) then you have no choice but to root your device first, then use this pm command from a root shell or directly delete the folder for "Sujet/Subject" from /system/app or /system/priv-app where you'll find it.
Click to expand...
Click to collapse
Hi,
OK, first off, thanks for the reply. Secondly, as I've stated before, I'm new to Android, and though I know my way around the command line in both Windows, Linux et OS X (not so much macOS: my MacBook Pro is 12-years old...), I suppose there are some things to set up first, before you can actually do what you suggest.
I understand that ADB stands for Android Debug Bridge, so is it an existing functionality in, say, Windows, that you can trigger from the command line, or a third-party software you have to install first?
On the Android side, what action should I take? Any Developer command to enable/disable to let ADB interact with my device the way it's supposed to?
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Lannig said:
Yes, you need to enable debug mode on your phone too. I could refer you to one of the zillion tutorials available on the net, but here's a summary.
Go to settings > about... (à propos)
Make at least 7 rapid touches on the line that says "build number" or its french translation.
This will make a new settings menu available from the main settings page: developer options
In this new menu, enable USB debugging.
Then you need to install ADB on your Mac and I'm at loss to help you there because I'm totally foreign to Macs. Never used one.
This seems like a good start: https://www.xda-developers.com/install-adb-windows-macos-linux/
Note: you may also try issuing the commands mentioned above from a terminal emulator running directly on your Android device, although I'm told that it's not exactly the same thing protection-wise.
Install this: https://play.google.com/store/apps/details?id=jackpal.androidterm and try typing the commands from the emulator window. If it works, no need for ADB (although having ADB will probably prove useful sooner or later and I encourage you to take the step).
EDIT: forget the guys from Phonandroid, they're brain-damaged beyond help
Click to expand...
Click to collapse
OK, thanks for the heads-up; I've already installed a Terminal emulator on the phone, so I'm gonna give it a go in a moment. I concur about Phoneandroid, alas: I've just received flak from one of the moderators because I'd double-posted on the same subject, whereas I'd just posted one thread, in the wrong part of the forum, according to him. Go figure...
OK, please feed back on your attempts, both from terminal emulator and through ADB.
Alas, I suspect that root will be required. It was for me on my Z5 and M5 to get rid of Leagoo's crapware.
Phonandroid is a bunch of losers with bloated egos posing as experts when 2/3 of the replies given are total BS.
"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...
"Er, Houston, we've had a problem..."
On Windows: "ADB is not a recognized name for a command applet..."
On OS X: "adb: command not found"
Stumped, I am...
(Additional question, not quite related: Aida64 indicates that my device runs a 4.4.49 version of the Android kernel, when the current version for Android 7.x is supposed to be 4.4.1; how does that compute--no pun intended--with my issue?)
Missing adb command is because the adb.exe (Windows) or adb (Mac) file is not in the command path. Either make the folder that contains the adb[.exe] file the current folder using the cd command or use whatever context menu for opening a command line window within the currently selected folder works, or even add that folder to the PATH variable. Google "add directory to path" for Windows and MacOS.
No idea about the kernel version. Minor kernel versions may vary within an Android release. Not surprising and most definitely unrelated to your problem. The crapware certainly isn't part of the kernel. It's most likely a system app i.e. a folder within either /system/app or /system/priv-app folders. You can't delete it without root, but you might be able to disable (freeze) it with the commands I gave you.
OK, thanks. I did "cd" to the folder where I had unzipped ADB on Windows (on the Mac, when I tried to open the ADB executable, I got a "cpu not supported" error message in the Terminal, as I feared, since my MBP is 32-bit-only, and most Mac applications nowadays only support 64-bit CPUs), and still got the "adb unrecognized command" error in PowerShell.
The phone was plugged in, and the right USB mode, so I'm still a bit baffled here. Gonna try it again with a different approach. Will keep you posted.
Over and out...
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
UglyStuff said:
OK, here's what I got: "Error: java.lang.SecurityException: Shell cannot change component state for com.leagoo.launcher3/null to 2"
Basically, from my poor understanding of how Android works, it's root or die, right?
Click to expand...
Click to collapse
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
---------- Post added at 01:23 PM ---------- Previous post was at 01:20 PM ----------
rhn19 said:
I see that this phone has 7.x android. So, a Magisk Systemless flash might work. After rooting your device, get a good launcher integrate it to /system. Then delete your stock launcher all together.
Tell me if this works.
Click to expand...
Click to collapse
If you are new to this, use an app from play store for uninstalling and integrating apps.
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
UglyStuff said:
Hi,
Yes, like I said, I'm a newbie when it comes to Android, so I'll abstain from rooting my device for now, but I'll keep your suggestions under advisement, because I suppose there'll be no other option in the long run. I'm gathering info on how to safely root a device.
I've done countless jailbreaks on iPhones, and it was always absolutely painless, but then, I had better understanding of how iOS works than I have Android, so until I know more about the OS, I'll keep my phone as it is.
Thanks again!
Click to expand...
Click to collapse
Jailbreaking vs Rooting is like 5-1 on difficulty level. Because Android is Open source while IOS is not. I would highly suggest you Root it if your phone does not have warranty. After all something that is on /system partition like your launcher will need superuser access to modify it. I cannot think of a way that wont void your warranty.
You can flash TWRP and then boot into aroma-fm but that will void your warranty. Rooting is the preferred option here.
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
UglyStuff said:
Yeah, well, the phone is brand-new, and still under warranty, but that's not what's holding me back: I'd rather not brick it, most of all, because I need it, if not as my main phone, at least for connectivity.
I've read tutorials on this very website about using TWRP to flash a new baseband, but I'm curious about what firmware to choose, where to download it from to be sure it's not laden with bad stuff, and how sure I'll be to have an operable phone afterwards.
Click to expand...
Click to collapse
Why do you want a new firmware? I don't get you man, do you want to clear out the malware or try a new ROM? Because i think you would have to build a new ROM, there is not one available i guess.
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
UglyStuff said:
That's the thing: the malware on my phone is part of the application launcher installed by the OEM. In other words, it's embedded inside the ROM. If I root my phone and somehow manage to get rid of this launcher, what's to tell me that Leagoo won't push it silently back onto my device under the disguise of an update?
I don't know what to do here. I understand that based on stock Android, each OEM applies a certain number of modifications to accommodate the hardware it used to build the phone, and since the SoC is brand-new, I gather there aren't many drivers available, unless I leave the current baseline in place.
I'm kinda caught between a rock and a hard place here...
Click to expand...
Click to collapse
If you use malwarebytes after root that thing wont happen. And almost all of the OEMs have a trigger which voids when rooting or flashing firmware. After that the OEM wont give you updates unless you use the A/B partitioning system.
OK, I understand how rooting my phone would void the warranty: after all, it's a substantial change in the phone software, and the OEM can't be made responsible for any mishap that occurs after I've rooted the phone.
What's the A/B partitioning system (I suppose it helps partition your storage space)? I don't have a microSD card installed (I use the slot for my second SIM), but I do have 32 Gb of storage space, minus what's already used up.
Do you know KingRoot? Is it as good and (reasonably) safe a rooting tool as they say it is?

Call recording

Can anyone confirm that this 9.0 pie update breaks all call recording app from the play store. Thanks for your feedback.
Updated to Android 9 today and boldbeast no longer works, it will record my voice but not that of the call )-: I am considering root now to get the feature back as i did find it useful.
Update: found this on the play store https://play.google.com/store/apps/details?id=net.jroot3d.joneplustools&hl=en_GB
Its all working fine now as it enables the oneplus6 built in recorder.
Thanks
But that also means that it wouldn't work without root like myself. Right?
Guess I gotta stick with my 8.1 until someone figures this one out. This one feature is like super important to me atm.
Thanks again for your kind reply.
Hi,
No root required, my phone is standard no unlocked bootloader and no root.
You just need to install the software, then enable developer options on your phone, enable usb debbugging and send the following command to your phone. adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
Then you will have the option in the software (joneplustool) to enable call recording and also restore calling recorder at boot.
Then on the phone dialler , go into settings and enable call record.
xtruss said:
restore calling recorder at boot.
Click to expand...
Click to collapse
That's a bummer...
But hey, thanks a lot for your kind reply. And as for myself, I've been using Cherinbo, pretty decent I would say.
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
vibo2013 said:
Well, I can confirm the paid verision of CallRecorder from skvalex still works on my Oneplus 6 with 9.0 Pie (not rooted, yet)
Click to expand...
Click to collapse
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
You seem as though you just want to promote a product to me, and one that doesn't work.
Darkest shades said:
Thanks for your feedback, and I'd like you ask a favor from you guys who is on 9.0.
Try that Cherinbo app and confirm that it's working good. I'll buy you a coffee if I could.
Click to expand...
Click to collapse
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
xtruss said:
You seem as though you just want to promote a product to me, and one that doesn't work.
Click to expand...
Click to collapse
Lol, not my intention. But the one thing that I like about this one is that all saved, recorded files doesn't appear into my music player, where as for others, they always does. Thanks for confirming that it doesn't work.
vibo2013 said:
I wanted to give it a try, but I can't use it unless I give permission to access my contacts. A call recording app should work without that. So: sorry, won't test it any longer.
Click to expand...
Click to collapse
It's ok, you help a lot already.
Thanks for your help guys.
I am very happy with the built in call recorder. What is the benefit of having a third party app to record calls?
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Void
---------- Post added at 02:57 AM ---------- Previous post was at 02:49 AM ----------
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
dgunn said:
Void
Does this allow recording apps to work or just the default recorder on the dialer? Also has anyone tried ACR? People are reporting that it does still work with and without rooting.
Click to expand...
Click to collapse
"adb shell settings put global op_voice_recording_supported_by_mcc 1"
It enables the default, native Call Recorder found on op6 and op5 and I really like it. It recorded all my today's calls ranging from 625KB to 2.29MB all good quality(aac files)
eliaspizarro said:
Requeriments:
root
terminal with su permisions
Manual steps
Method 1 (works until reboot):
Create a file ex. incall.sh:
Code:
#!system/bin/sh
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
execute from terminal: $ sh incall.sh
Method 2 (works until reboot):
with adb: > adb shell "settings put global op_voice_recording_supported_by_mcc 1"
My steps (permanent):
Install termux (add su permisions)
in termux: $ termux-setup-storage
Install termux boot
create folder un termux home path (default) named: .termux
in termux: $ ln -s /storage/emulated/0/<your boot script folder> ~/.termux/boot
create script in /storage/emulated/0/<your boot script folder>
Code:
su -c 'settings put global op_voice_recording_supported_by_mcc 1'
exit
reboot
Click to expand...
Click to collapse
..
This is what I'm getting
sh: $: not found
Just by telling us to install this and add home path here..... We need instructions
---------- Post added at 06:26 PM ---------- Previous post was at 06:04 PM ----------
and again
sh: adb: not found
mzsquared said:
xtruss said:
Hi,
adb shell pm grant net.joneplustools android.permission.WRITE_SECURE_SETTINGS
this adb command(below) worked on oreo and I just used it on pie, no root, works great. (you just have to run it again anytime you reboot your phone, if you're rooted, then it's permanent)
so, copy and paste in adb:
adb shell settings put global op_voice_recording_supported_by_mcc 1
>>>>then go to your phone dialer settings to see that is there.
Click to expand...
Click to collapse
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
You can also use Tasker to enable native call recording (provided you've granted WRITE_SECURE_SETTINGS permission to Tasker).
It seems the system deactivates jOnePlus from activating call recorder after 8 hours. Anyway to make it a permanent activation?
Even after removing jOnePlus from the battery optimize list, the call recorder still gets deactivated after a couple of hours.
obislu said:
mzsquared said:
When you say you used it on Pie, do you mean the beta or final version?
Click to expand...
Click to collapse
I took the official OTA Pie upgrade and enabled the recorder with adb command after that. I'm not planning to root my phone, at least not yet. I'm enjoying the Pie Rom as is. It's all good, actually great with the night mode, there is no bloat. I disabled few apps, mainly from google and that's that. I remember times when rooting was an important necessity, I've had a Motorola Defy XT, long time ago, with 1GB RAM and no space for any extra apps, rooting was mainly used for getting the bloat out and moving apps to SD card by way of creating ext4 partition.
My OP6 has 256GB storage space, 8GB RAM and I just don't feel like constantly reloading the system, chasing newest twrps and Magisk versions, softbricking etc,etc.. and having my phone 'off line' for hours while I'm fixing it.
Click to expand...
Click to collapse

Rooting Android TV with /system partition ro

Hey, I have a smart android TV running on some cvte board from china and running android 7.1.1 from 2020.
The /system partition is mounted ro [remount allowed] and /data rw but trying to edit that gives access denied error.
The adb reboot fastboot and adb reboot recovery just reboots the tv.
I have enabled adb by going into the service menu and enabling in debug.
I have seen modified scripts in /system/bin that refer to su scripts.
One of them being cvte_su_service and sys_control. These scripts do not work without adb root shell.
I cannot find any exploit for this tv and it is a 32bit hislicion cpu with mali 450 gpu.
I use adb with the termux terminal emulator.
I cannot find any way to elevate permissions on the tv and i cannot find any type of help on this.
P.S i also saw many hotkeys like the service menu but i cant understand what they are for since they are in Chinese..
At least your device has the ability of installing apps freely
I can help you to translate the hotkeys to English in 3 days if necessary.
Well thanks!
yeah idfk what those keys mean or do, only the factory menu one.
Mark Zhang said:
At least your device has the ability of installing apps freely
I can help you to translate the hotkeys to English in 3 days if necessary.
Click to expand...
Click to collapse
I can help you with installing termux and adb on that so you can run adb on your tv itself and install through it like that.
Great! Thanks too!
How about continue on Chat apps such as Telegram?
The forum is not a convenient place for long conversations.
Mark Zhang said:
Great! Thanks too!
How about continue on Chat apps such as Telegram?
The forum is not a convenient place for long conversations.
Click to expand...
Click to collapse
I'm not on telegram but you can contact me on Twitter! @Kenora_I
Could you please check a tweet from you? I'm under it ~ (。・ω・。)
Mark Zhang said:
Could you please check a tweet from you? I'm under it ~ (。・ω・。)
Click to expand...
Click to collapse
Kay.
Kenora_I said:
Hey, I have a smart android TV running on some cvte board from china and running android 7.1.1 from 2020.
The /system partition is mounted ro [remount allowed] and /data rw but trying to edit that gives access denied error.
The adb reboot fastboot and adb reboot recovery just reboots the tv.
I have enabled adb by going into the service menu and enabling in debug.
I have seen modified scripts in /system/bin that refer to su scripts.
One of them being cvte_su_service and sys_control. These scripts do not work without adb root shell.
I cannot find any exploit for this tv and it is a 32bit hislicion cpu with mali 450 gpu.
I use adb with the termux terminal emulator.
I cannot find any way to elevate permissions on the tv and i cannot find any type of help on this.
P.S i also saw many hotkeys like the service menu but i cant understand what they are for since they are in Chinese..
Click to expand...
Click to collapse
@jwoegerbauer sorry for the mention but do you have any amazing ideas on how to accomplish root on this. Sorry for the mention, I know you must be busy and you don't need to reply.
Just kinda at my wits end with this.
No problems.
I think the answer I gave here:
Fully Rooting Onyx Boox Poke3 e-reader
UPDATE: Changed the Topic as we are getting away from the original question in post 1 to the actual problem: figuring out how to fully root an Onyx Boox Poke3 e-reader running Android 10. "Fully" meaning including full r/w access to /system and...
forum.xda-developers.com
Do you know how to open an app with IR Remote? Editing keylayouts?

Categories

Resources