• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Help Is there away?

Is there anyway to get a rooted Kyocera Rise with:
DSP Manager
Google Now
And Jellybean 4.2 keyboard
Back to 100% stock?
Not rooted. Like when you first take it out of the box?

Manually removing the parts, sure. There's no quick way such as dd'ing a clean system because the only way to get a copy of the system is to be rooted to have access to it. Unless someone has done that and then edited the resulting image manually of course.
 
Upvote 0
Manually removing the parts, sure. There's no quick way such as dd'ing a clean system because the only way to get a copy of the system is to be rooted to have access to it. Unless someone has done that and then edited the resulting image manually of course.

What are the adb commands to push /system/ dump to the phone because I just remembered DSP Manager screwd up the audio. I doesn't sound good like it used to.
Thank you.
 
Upvote 0
adb can't flash a phone, it can restore backups but those backups aren't a complete rom. You'd need fastboot to flash /system. It may be possible to do it with root using dd on the phone but I wouldn't try that as you'd be writing to the partition you're using to write to the partition with, the results of which could be... interesting.

Why do you need to do this? Is the phone in a nonfunctional state?
 
Upvote 0
adb can't flash a phone, it can restore backups but those backups aren't a complete rom. You'd need fastboot to flash /system. It may be possible to do it with root using dd on the phone but I wouldn't try that as you'd be writing to the partition you're using to write to the partition with, the results of which could be... interesting.

Why do you need to do this? Is the phone in a nonfunctional state?

No I put http://forum.xda-developers.com/showthread.php?t=1952154 on and it made my audio sound like crap. So I wanted to reverse that if I couldn't revers anything else.
 
Upvote 0
No I put http://forum.xda-developers.com/showthread.php?t=1952154 on and it made my audio sound like crap. So I wanted to reverse that if I couldn't revers anything else.

Looks straightforward enough. I cooked up a script for someone to remove the 4.2 camera/gallery and put back stock, I can whip something up for you for this if you'd like.

I assume you're rooted, how else would you have installed it in the first place. :)

edit: There may be an easier way than that, get a stock copy of /system/etc/audio_effects.conf and replace the one on your phone with it, and then delete DSPManager.apk from /system/app. You'll need to mount /system writable for it of course. The rest of the DSP Manager can be left on the phone, they won't do anything anymore when the .conf isn't loading them.

I'd attach the conf file but I'm getting complaints from the forum that I'm over an attachment quota.
 
Upvote 0
Yes please. I am rooted. Thank you SO much. :)

I updated that reply with alternate instructions. Since the forum won't let me upload a file I'll just put it in this reply hidden, copy it and save as audio_effects.conf

# List of effect libraries to load. Each library element must contain a "path" element
# giving the full path of the library .so file.
# libraries {
# <lib name> {
# path <lib path>
# }
# }
libraries {
bundle {
path /system/lib/soundfx/libbundlewrapper.so
}
reverb {
path /system/lib/soundfx/libreverbwrapper.so
}
visualizer {
path /system/lib/soundfx/libvisualizer.so
}
pre_processing {
path /system/lib/soundfx/libaudiopreprocessing.so
}
}

# list of effects to load. Each effect element must contain a "library" and a "uuid" element.
# The value of the "library" element must correspond to the name of one library element in the
# "libraries" element.
# The name of the effect element is indicative, only the value of the "uuid" element
# designates the effect.
# The uuid is the implementation specific UUID as specified by the effect vendor. This is not the
# generic effect type UUID.
# effects {
# <fx name> {
# library <lib name>
# uuid <effect uuid>
# }
# ...
# }

effects {
bassboost {
library bundle
uuid 8631f300-72e2-11df-b57e-0002a5d5c51b
}
virtualizer {
library bundle
uuid 1d4033c0-8557-11df-9f2d-0002a5d5c51b
}
equalizer {
library bundle
uuid ce772f20-847d-11df-bb17-0002a5d5c51b
}
volume {
library bundle
uuid 119341a0-8469-11df-81f9- 0002a5d5c51b
}
reverb_env_aux {
library reverb
uuid 4a387fc0-8ab3-11df-8bad- 0002a5d5c51b
}
reverb_env_ins {
library reverb
uuid c7a511a0-a3bb-11df-860e-0002a5d5c51b
}
reverb_pre_aux {
library reverb
uuid f29a1400-a3bb-11df-8ddc-0002a5d5c51b
}
reverb_pre_ins {
library reverb
uuid 172cdf00-a3bc-11df-a72f-0002a5d5c51b
}
visualizer {
library visualizer
uuid d069d9e0-8329-11df-9168-0002a5d5c51b
}
agc {
library pre_processing
uuid aa8130e0-66fc-11e0-bad0-0002a5d5c51b
}
aec {
library pre_processing
uuid bb392ec0-8d4d-11e0-a896-0002a5d5c51b
}
ns {
library pre_processing
uuid c06c8400-8e06-11e0-9cb6-0002a5d5c51b
}
}
# Audio preprocessor configurations.
# The pre processor configuration consists in a list of elements each describing
# pre processor settings for a given input source. Valid input source names are:
# "mic", "camcorder", "voice_recognition", "voice_communication"
# Each input source element contains a list of effects elements. The name of the effect
# element must be the name of one of the effects in the "effects" list of the file.
# Each effect element may optionally contain a list of parameters and their
# default value to apply when the pre processor effect is created.
# A parameter is defined by a "param" element and a "value" element. Each of these elements
# consists in one or more elements specifying a type followed by a value.
# The types defined are: "int", "short", "float", "bool" and "string"
# When both "param" and "value" are a single int, a simple form is allowed where just
# the param and value pair is present in the parameter description
# pre_processing {
# <input source name> {
# <fx name> {
# <param 1 name> {
# param {
# int|short|float|bool|string <value>
# [ int|short|float|bool|string <value> ]
# ...
# }
# value {
# int|short|float|bool|string <value>
# [ int|short|float|bool|string <value> ]
# ...
# }
# }
# <param 2 name > {<param> <value>}
# ...
# }
# ...
# }
# ...
# }

#
# TODO: add default audio pre processor configurations after debug and tuning phase
#

Let me know if it works, if it doesn't then I'll do it like I was going to before.
 
Upvote 0
adb can't flash a phone, it can restore backups but those backups aren't a complete rom. You'd need fastboot to flash /system. It may be possible to do it with root using dd on the phone but I wouldn't try that as you'd be writing to the partition you're using to write to the partition with, the results of which could be... interesting.

Why do you need to do this? Is the phone in a nonfunctional state?

Done it. It sets the phone into a bootloop with no way out.
 
Upvote 0
Do you know the ADB commands to push it to the phone?
And bassy songs weren't staticy before. Now the more bass the more static.

Before doing that, delete /system/vendor/etc/audio_effects.conf and reboot. Note that this is not the same file you replaced earlier.

Just for shits and giggles go ahead and delete /system/lib/soundfx/libcyanogen-dsp.so as well. After that, along with the earlier instruction to replace /etc/audio_effects.conf and nuke DSPManager.apk there won't be anything left of the CM DSP manager on the phone.
 
Upvote 0
Before doing that, delete /system/vendor/etc/audio_effects.conf and reboot. Note that this is not the same file you replaced earlier.

Just for shits and giggles go ahead and delete /system/lib/soundfx/libcyanogen-dsp.so as well. After that, along with the earlier instruction to replace /etc/audio_effects.conf and nuke DSPManager.apk there won't be anything left of the CM DSP manager on the phone.

I did it and it sound great.
Could I still get the adb commands because I still want to experiment with this phone.
 
Upvote 0
I did it and it sound great.
Could I still get the adb commands because I still want to experiment with this phone.

It kind of depends on the file you're wanting to push or pull. ADB stands for "Android Debug Bridge" and that's basically all it is, it's got some neat tricks but most of it could be done the same with some creative shell scripts and SSH access to the phone. It's kind of a glorified version of that, providing a conduit in to the built-in shell of the phone, same thing you see from a terminal app really. For instance I can tell you "adb reboot" reboots the phone, but if you type "reboot" in to a terminal on the phone itself it'll do the same thing.

Telling you the specific commands for what's already been done now won't be of much help, you'd be better served by playing with adb yourself and learning it that way.
 
Upvote 0
With ADB yu need to be on the computer and it always starts with adb then follows with the command. I know some people dont give a straigh answer, it was the same with me so here it is:

adb pull:

Open Command Prompt (windows)

Type adb connect(if it says device not connected or offline, etc then yu need to remount it)

Adb pull /"folder name"/"folder name"/"keep repeating til yu get to desired file destination"
I.e. adb pull for System UI: adb pull /system/app/systemui.apk


Adb push:

Open Command Prompt (windows)

Type adb connect(if it says device not connected or offline, etc then yu need to remount it)

Yu need to put the destination of the file yu are pushing into the command prompt,
I.e. trying to push systemui.apk thats on yur desktop to the phone yu would need to type:
cd C:/Users/"name of yur folder which yu are under"/Desktop

After that it should be mounted, so now yu can push the file by typing in the command prompt the destination of the on yur computer, add a space and the destination yu want to put it on yur phone. If yu are on the correct path, yu can type the first four letters of the name of the file then press tab, this should finish naming the file yu are trying to push.
i.e.
adb push systemui.apk ./system/app

hope this helps and can be understandable..
 
  • Like
Reactions: DMedina559
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones