Develop Bugs

[Q] "Installation unsuccessful" for Google Voice Search

I've been trying to download Google Voice Search on my Evo running Cyanogenmod 6 8-10. Every time I try to download it though, I get "Installation unsuccessful". Is anyone else having the same problem? This is the only app I've had problems downloading.

Hairongreenfire said:
I've been trying to download Google Voice Search on my Evo running Cyanogenmod 6 8-10. Every time I try to download it though, I get "Installation unsuccessful". Is anyone else having the same problem? This is the only app I've had problems downloading.
Click to expand...
Click to collapse
I'm not sure of the cause, but I am having the same problem as well.

I'm having the same issue as well.
Going into Settings -> Force Stop on the Voice Search app already installed didn't resolve the issue.
I will keep looking for a solution personally ...

my solution was
download and install titanium backup
uninstall voice search via that,
reboot
install new one
worked for me

Jsimon9633 said:
my solution was
download and install titanium backup
uninstall voice search via that,
reboot
install new one
worked for me
Click to expand...
Click to collapse
Will try and report back -- thank you!!
Edit: This worked! Thanks!!

aikeru said:
Will try and report back -- thank you!!
Click to expand...
Click to collapse
I removed it using adb shell, and rebooted and it worked.
The google search widget won't install so I'm going to try the same thing. Also, I need to find the clock app to be able to do "Set Alarm" with it.

Jsimon9633 said:
my solution was
download and install titanium backup
uninstall voice search via that,
reboot
install new one
worked for me
Click to expand...
Click to collapse
Tried this, it hasn't worked for me. I get 'download unsuccessful.'
EDIT: Rebooted again, it worked this time.

Thanks for the quick reply, Jsimon, it worked perfect!

i had the same issue also. possibly because voice search was an existing embedded application in the system folder. I also had to remove via root explorer, reboot and re download. thank god for root

Uninstall version 1.6 with Titanium Backup first...
I had to do the same thing.
I was getting the "manual update required" error. Used TB to uninstall version 1.6. ADB reboot and then I installed version 2.1 from the market.
Works like a champ. This is true useful functionality!

Whats the adb command that I type into terminal to delete this? It won't let me delete in TB or Root Explorer or anything. Says I don't have permissions.
NEVERMIND, GOT THIS TO WORK!

I used Root Explorer to remove Voice Search and then rebooted Evo. Hit up the Market and DL'd Voice Search with a perfect install. Good Luck.

I was having the same problem and the TB work-around worked well for me. So thank you for that. This may or may not be related, but does anyone have any issues purchasing applications from the market? I have been trying to buy, "Tasker," for the better part of the last week and every time I go to enter my card information it fails.

How to get this trick work with Google Search from the Market?
{
"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"
}

Fixed
This worked for me running Cyanogenmod 6-RC2 on US MT3G:
from http://forum.cyanogenmod.com/topic/4231-installing-updated-voice-search/
Anyway, if you have adb, plug into usb and run:
Code:
adb pull /system/app/ ~/Desktop/app/
adb remount
adb shell rm -f /system/app/VoiceSearch.apk
adb shell pm uninstall com.google.android.voicesearch
adb shell rm -f /system/app/GoogleQuickSearchBox.apk
adb shell pm uninstall com.google.android.googlequicksearchbox
If you don't, open Terminal Emulator on your phone (This does NOT backup the .apk's, so proceed at your own risk!) and run:
Code:
su
mount -o rw,remount /system
rm -f /system/app/VoiceSearch.apk
pm uninstall com.google.android.voicesearch
rm -f /system/app/GoogleQuickSearchBox.apk
pm uninstall com.google.android.googlequicksearchbox
Your old out of date versions are now removed. Now go to the Market and install "Voice Search" and "Google Search".

WORKING!
Thanks ryanclemson!

Thanks Jsimon9633! It worked perfectly!

Im running CM's nightlys. I am trying to get this working also. Just a question, when I go to adb shell, I get "#" not "$". Shouldnt I have $?

RichTJ99 said:
Im running CM's nightlys. I am trying to get this working also. Just a question, when I go to adb shell, I get "#" not "$". Shouldnt I have $?
Click to expand...
Click to collapse
# means root access
$ means no root

ryanclemson said:
This worked for me running Cyanogenmod 6-RC2 on US MT3G:
from http://forum.cyanogenmod.com/topic/4231-installing-updated-voice-search/
Anyway, if you have adb, plug into usb and run:
Code:
adb pull /system/app/ ~/Desktop/app/
adb remount
adb shell rm -f /system/app/VoiceSearch.apk
adb shell pm uninstall com.google.android.voicesearch
adb shell rm -f /system/app/GoogleQuickSearchBox.apk
adb shell pm uninstall com.google.android.googlequicksearchbox
If you don't, open Terminal Emulator on your phone (This does NOT backup the .apk's, so proceed at your own risk!) and run:
Code:
su
mount -o rw,remount /system
rm -f /system/app/VoiceSearch.apk
pm uninstall com.google.android.voicesearch
rm -f /system/app/GoogleQuickSearchBox.apk
pm uninstall com.google.android.googlequicksearchbox
Your old out of date versions are now removed. Now go to the Market and install "Voice Search" and "Google Search".
Click to expand...
Click to collapse
get the following error when attempting:
rm failed for -f. read only file system
any ideas??

[RECOVERY][ClockWorkMod 3.0.2.8][BETA]

Disclaimer:
Proceed at your own risk. I am not responsible if your device gets bricked or damaged during the process.
recovery-CW3028-OP-thunderc_002.zip
Port to Optimus V
This version is using a beta kernel I am working on. (driver updates from new Optimus-S source, NOOP set default)
Backup and restore tested.
Camera button == Action
Code:
In an ADB shell:
> mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system
> cat /sdcard/flash_image > /system/bin/flash_image
> chmod 755 /system/bin/flash_image
> mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
> mount -o remount,ro -t yaffs2 /dev/block/mtdblock5 /system
> flash_image recovery /sdcard/recovery.img
> exit
reboot into recovery (I use QuickBoot, but "adb reboot" works fine as well)
Enjoy!

I'll update more after work.
[hold]

Badass, thank you!
Sent from my VM670 using XDA App

What's the difference between this and the one posted on romrepo?
Sent from my LG-VM670 using Tapatalk

vegetajin8 said:
What's the difference between this and the one posted on romrepo?
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
Cant say 100% as I only used the recovery-thunderc-v-1.2.0-GNM.img recovery (Amon_RA based) once since I've had the OptV.
This is based on CWM source and the stock recovery kernel (for now)
which allows advanced restores etc.
The only other Recovery I see is CWMA which looks like a Xionia kernel and a Amon_Ra/ClockWorkMod hybrid recovery. I know nothing about that recovery, so be sure to try it out and see which you like best.

opcode1300 said:
Cant say 100% as I only used the recovery-thunderc-v-1.2.0-GNM.img recovery (Amon_RA based) once since I've had the OptV.
This is based on CWM source and the stock recovery kernel (for now)
which allows advanced restores etc.
The only other Recovery I see is CWMA which looks like a Xionia kernel and a Amon_Ra/ClockWorkMod hybrid recovery. I know nothing about that recovery, so be sure to try it out and see which you like best.
Click to expand...
Click to collapse
I've tried xionia I like it to a point that almost all roms will only work with it. I'm currently using 3.0.2.8 from rom repo for the v and like it better. Just wish everyone would use one recovery to develop their roms with.
Sent from my LG-VM670 using Tapatalk

I'm sorry, but I am having some trouble using the ADB. Where does the .zip file need to be when I type in all of these commands?
Whenever I try to type in the first command (mount -o remount,rw -t yaffs2 /dev/block/mtdblock5 /system) in the ADB shell it says Operation not permitted. Anyone know how to get around it?

When in adb type su then the command see if that works.
Sent from my LG-VM670 using XDA Premium App

Why not just add terminal directions? much simpler
$ su
# cat /proc/mtd
identify recovery -mines mtd2 - & backup...
# cat /dev/mtd/mtd2 > /sdcard/recovery.img
place the recovery to be flashed on sdcard root (example.img)
# flash_image recovery /sdcard/example.img

I saw a clockwork recovery avalibale threw rom manager for the optimus v and would like to know if that's a stable recovery ?
Sent from my T-Mobile G2 using XDA App

arsonist63086 said:
I saw a clockwork recovery avalibale threw rom manager for the optimus v and would like to know if that's a stable recovery ?
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
Depending on how new the OV is.
The newer OVs have a different screen and that recovery is not compatible
Sent via LG VM670 IHO

Someone explain recovery for me, is it basically a rom?
BOB DOLE

Recovery
omgpk said:
Someone explain recovery for me, is it basically a rom?
BOB DOLE
Click to expand...
Click to collapse
No its not a rom but what can be used to flash roms
Sent from my LG-P500 using XDA

Here is a dictionary link
omgpk said:
Someone explain recovery for me, is it basically a rom?
BOB DOLE
Click to expand...
Click to collapse
Here is some info on it.
http://forum.xda-developers.com/showthread.php?p=10377391#post10377391
Once you are on the page you can scroll up to the top to see the other information that is there.

Root samsung gem sch-i100

Can anyone tell me how to root a samsung gem (sch-i100) I posted this in 2 other sections already about month ago but I've had no respnoses at all. Can anyone tell me anything????
Sent from my SPH-D700 using Tapatalk

One click Root?
Google it, and that device might not be supported by a dev who's rooted it yet.

justen7723 said:
Can anyone tell me how to root a samsung gem (sch-i100) I posted this in 2 other sections already about month ago but I've had no respnoses at all. Can anyone tell me anything????
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I found this through Google:
Download and Install Samsung Drivers
64bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
Download and Install ADB
Android SDK | Android Developers
http://developer.android.com/sdk/index.html
Download the attached files
Setup ADB to work in your PATH
Windows: Go to System Properties > Advanced Tab > Environment Variables
Click on the Path variable under System Variables and hit edit
Add a colon: and the location of your android-sdk tools folder
In example :C:\Android\SDK\android-sdk-windows\tools
connect your phone with the usb cable and go to settings > applications > enable debugging
run cmd
cd to the directory of the unzipped files included and follow these commands to a tee
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt follow these commands
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Thats it, I hope this helps you. Its a complete rooting process.
Once you have Root, simply download ROMManager from the Market, do a "Backup" from the app, and download whichever ROM you want from the list of available ROMs inside the app, enjoy!
Read more: how to root android 2.1 on Samsung Gem - JustAnswer http://www.justanswer.com/cell-phones/4ztjq-root-android-2-1-samsung-gem.html#ixzz1VhiYTWP4

Thanks haven't tried it yet but I will, (its for a friend)
Sent from my SPH-D700 using Tapatalk

kennyglass123 said:
I found this through Google:
[/url]
Click to expand...
Click to collapse
Impressive, most impressive.
{
"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"
}

I tried this method and got it to work but it still didnt root im running 2.2.1 though i dont know how to get this going

I'm missing something here.. where does rage.bin come from? For that matter, where are the superuser and busybox binaries coming from?

jimnutt said:
I'm missing something here.. where does rage.bin come from? For that matter, where are the superuser and busybox binaries coming from?
Click to expand...
Click to collapse
Why necro this thread? Let it die in peace.
Sent from my SPH-D700 using Tapatalk

kennyglass123 said:
I found this through Google:
Download and Install Samsung Drivers
64bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x64.shtml
32bit:
http://drivers.softpedia.com/get/MOBILES/Samsung/Samsung-Galaxy-S-USB-Driver-for-Windows-x86.shtml
Download and Install ADB
Android SDK | Android Developers
http://developer.android.com/sdk/index.html
Download the attached files
Setup ADB to work in your PATH
Windows: Go to System Properties > Advanced Tab > Environment Variables
Click on the Path variable under System Variables and hit edit
Add a colon: and the location of your android-sdk tools folder
In example :C:\Android\SDK\android-sdk-windows\tools
connect your phone with the usb cable and go to settings > applications > enable debugging
run cmd
cd to the directory of the unzipped files included and follow these commands to a tee
adb push su /sdcard/su
adb push rage.bin /data/local/tmp/rage.bin
adb push busybox /sdcard/busybox
adb shell
cd /data/local/tmp
chmod 0755 rage.bin
./rage.bin
wait....
when it brings you back to your original shell or windows cmd promt follow these commands
adb shell
mount -t rfs -o remount,rw /dev/block/stl9 /system
cd /system/xbin
cat /sdcard/su > su
cat /sdcard/busybox > busybox
chmod 4755 su
chmod 4755 busybox
exit
adb install Superuser.apk
Thats it, I hope this helps you. Its a complete rooting process.
Once you have Root, simply download ROMManager from the Market, do a "Backup" from the app, and download whichever ROM you want from the list of available ROMs inside the app, enjoy!
Read more: how to root android 2.1 on Samsung Gem - JustAnswer http://www.justanswer.com/cell-phones/4ztjq-root-android-2-1-samsung-gem.html#ixzz1VhiYTWP4
Click to expand...
Click to collapse
Wow, that's extraordinarily similar to the process I had to use to root my Epic4G WAY back in Nov of 2010. Those were scary times.
I remember that while I was doing this my Epic went black and unresponsive, and it took me several hours to get it working again. I felt faint and was shaking the whole time.
From that point on I always told friends who wanted to root- it's not really any fun until you think that you've bricked your phone a couple of times.
sent from my secret underground bunker

Samsung gem i100
I recently got a samsung gem i100. Biggest problem with it was it didn't have the new version of google play (market) on it. I like installing programs from the website, not typing away looking for the right app on my phone. So I installed APK installer, and upgraded the os from 2.1 to 2.2. Which did kill google market.. However I have a different phone and on that phone I have an app called APK extractor(the phone is rooted) I extracted he newest version of google play and uploaded it to the Gem. Google play works fine so far... The 3g data isn't working but the phone is for my kid and Verizon charges for data now. It works ok, but would like the 3g data to work again.any ideas? (The only data it has is wifi. I wonder if it is a setting somewhere, I wouldn't mind throwing on a new os if there was one I could find so long as it was compatible.)

Samsung gem i100
I was hoping someone on here had a unmodified Samsung gem i100 from Verizon so they could use super one click on it and root it then back up the rom, and share it because I broke mine by updating it to 2.2... (the rom for Verizon is 2.1, but 2.2 is for US cellular and Alltel) I downloaded the source code from Samsung in a long shot attempt to repackage it so it will make the data work on the gem again. I think the problem with 2.2 lies in the drivers for the board. If I can fix that then 2.2 should work for Verizon. Although I have no idea what I'm doing I have downloaded Oracle VM VirtualBox, and setup what I need for Android kitchen so I can run the current rom from there and hopefully make the changes...
The other project I'm working on is to find out why the game Temple Run 2 will run on a Droid 4 but not a Droid 1, and if there is a way to modify the Droid 1 so it can run it. My kids like the game, but I don't want them using my phone to play it all the time...
Any pointers would be great. I don't look forward to teaching myself how to write programs but it seems that is my only option...

Are you aware that this is the Epic 4G (with keyboard) forum?
Sent from my Nexus 7 using Tapatalk 2

norcalnub said:
I was hoping someone on here had a unmodified Samsung gem i100 from Verizon so they could use super one click on it and root it then back up the rom, and share it because I broke mine by updating it to 2.2... (the rom for Verizon is 2.1, but 2.2 is for US cellular and Alltel) I downloaded the source code from Samsung in a long shot attempt to repackage it so it will make the data work on the gem again. I think the problem with 2.2 lies in the drivers for the board. If I can fix that then 2.2 should work for Verizon. Although I have no idea what I'm doing I have downloaded Oracle VM VirtualBox, and setup what I need for Android kitchen so I can run the current rom from there and hopefully make the changes...
The other project I'm working on is to find out why the game Temple Run 2 will run on a Droid 4 but not a Droid 1, and if there is a way to modify the Droid 1 so it can run it. My kids like the game, but I don't want them using my phone to play it all the time...
Any pointers would be great. I don't look forward to teaching myself how to write programs but it seems that is my only option...
Click to expand...
Click to collapse
Also. The Droid 1 has an armv6 processor and the Droid 4 has an armv7 processor. So in order for the game to play on the Droid 1, you'd need to find someone who knows how to port games from armv7 to armv6.
Sent from my SPH-D700 using Tapatalk 2

nikon120 said:
Are you aware that this is the Epic 4G (with keyboard) forum?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Apparently they are not aware -_____-

silly necroers.
---------- Post added at 04:50 PM ---------- Previous post was at 04:41 PM ----------
https://code.google.com/p/intercept-root/

[ROOT][Silence_Camera][Deodexed] Silence: for simplifying the silencing of the camera

{
"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"
}
Silence is a compilation of tools (based on sfhub's RUNFIRST) that has been tested on the EK02 and EL29 kernel, made for use on Windows OS(not Linux or OSX). This application has only 5 distinct purposes:
-Install Manufacturer's Android Samsung USB Drivers
-Install Root
-Uninstall Root
-Install Silent Camera.
-Uninstall Silent Camera (restore stock Camera application).
It would be wise to backup any data on your E4GT before downloading Silence, make sure your kernel version is either EK02/EL29/EG30/EG31.
1 - It is required that you enable USB Debugging Mode by going to Menu (Home Button)>>Settings>>Applications>>Development>>Check 'USB debugging'.
Make sure that you do this while the USB is NOT connected, then reconnect the USB adapter. If you are currently in USB Storage Mode *orange android*, hit the disconnect button.
2 - Download silencev4.zip here | mirror and unzip to your local drive [default value is C:\].
3 - Run Command Prompt (if you can't find it in the Start Menu, open up Task Manager and click 'File'>>New Task>>type in 'cmd')
Under Windows 7, the prompt should say:
Code:
C:\Users\%USERNAME%>
4 - Run Silence, use the following commands in consecutive order:
Code:
C:\Users\%USERNAME%>_
C:\Users\%USERNAME%>cd C:\root\
C:\root\>_
C:\root\>index
5 - Install the Android Samsung USB Drivers.
6 - Install Root. *only after Step 5*
7 - Install Silent Camera *only after Step 5/6*, unless you've already rooted your E4GT.
(Note: Your Camera application icon might disappear from Menu (Home Button), but it can still be found under the Applications Menu.).
Finally:
Option 0: Uninstall the Silent Camera.
Option 1: Uninstall Root.
Option 2: Leave root on your E4GT.
The folder "000root" can be deleted at anytime and it will not affect any future operations.
Credits to sfhub (RUNFIRST) and kcbedo (Silent Camera EK02/EL29).
Credits to locoboi for pointing out a flaw in the code.

change log
8/14/12
Stock FF18 odexed silent Camera.apk (here)
[MD5: 716be9c8377f2772346fdd62cdb6ef6b]
ADB w/ E4GT Android Drivers (here)
[MD5: 58b9094400895ca8320963fb4d4a520d]
8/11/12
Integrated deodexed silent camera application into stock FF18 ROM (here).
7/20/12
Stock FF18 deodexed silent Camera.apk (here)
[MD5: AbkuDU8LiaMoQ+IdbOf44w==]
Replace these .ogg files found in /system/media/audio/ui/ (here).
[MD5: 5f208003f3ee8b35c103954e90e3cbfd]
1/10/12 silencev4
+decreased overall size *credits go to sfhub*
1/9/12 silencev3
+fixed a flaw that prevented the success of installing the silent camera
Original screenshot can be found here.
1/9/12 silencev2
+ Ability to uninstall silent camera.
1/9/12 silence
+/- Posted initial package.
Original screenshot can be found here

Thank you.
Sent from my SPH-D710 using Tapatalk

This wouldn't happen to work with EL29, would it?

locoboi187 said:
This wouldn't happen to work with EL29, would it?
Click to expand...
Click to collapse
I'm not sure if it would work, the Camera application was tested under EK02; I would recommend that you pm kcdedo.
His original thread is here.

Nice mod.
Thank you..

taufunc said:
I'm not sure if it would work, the Camera application was tested under EK02; I would recommend that you pm kcdedo.
His original thread is here.
Click to expand...
Click to collapse
Didnt fully work. Still makes the focus sounds

locoboi187 said:
Didnt fully work. Still makes the focus sounds
Click to expand...
Click to collapse
Was your kernel version EK02, different kernels might work differently? I've also updated Silence to version 2, it can now restore the deleted sound files as an option.

taufunc said:
Was your kernel version EK02, different kernels might work differently? I've also updated Silence to version 2, it can now restore the deleted sound files as an option.
Click to expand...
Click to collapse
Nah I was reporting back on EL29. Lol. But idt much has changed as far as camera goes
Sent from my SPH-D710 using xda premium

locoboi187 said:
Nah I was reporting back on EL29. Lol. But idt much has changed as far as camera goes
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
It is possible to create a seperate version of the Silent Camera application; I would need a EL29, which I don't have and understand a lot about other than its another kernel. The original steps of how I tried to make the Silent Camera application begins with how I found the refocusing sound files within the original .apk file. After editing the file personally, but I failed to deodex the Camera.odex successfully after countless tries. However, I found kcdedo's copy and it worked quite well.

taufunc said:
It is possible to create a seperate version of the Silent Camera application; I would need a EL29, which I don't have and understand a lot about other than its another kernel. The original steps of how I tried to make the Silent Camera application begins with how I found the refocusing sound files within the original .apk file. After editing the file personally, but I failed to deodex the Camera.odex successfully after countless tries. However, I found kcdedo's copy and it worked quite well.
Click to expand...
Click to collapse
On your program it said Camera and Camera odex directories were failed to be found. I believe they are always in system/app. so idk why it couldnt find it

locoboi187 said:
Didnt fully work. Still makes the focus sounds
Click to expand...
Click to collapse
The autofocus sounds are in Camera.apk, not in the /system/media folder. You either need to modify the apk or make a change in the initramfs of the kernel to get rid of that sound. The Camera.apk is odexed, so you can't just take one version and put it on another ROM release, expecting it to work. You actually need to make the change for each release's Camera.apk.

locoboi187 said:
On your program it said Camera and Camera odex directories were failed to be found. I believe they are always in system/app. so idk why it couldnt find it
Click to expand...
Click to collapse
Woah, I typed the wrong directory. Thanks, I'll temporarily upload the 2 important files that must be replaced.
sfhub said:
The autofocus sounds are in Camera.apk, not in the /system/media folder. You either need to modify the apk or make a change in the initramfs of the kernel to get rid of that sound. The Camera.apk is odexed, so you can't just take one version and put it on another ROM release, expecting it to work.
Click to expand...
Click to collapse
I never stated that I had any expectations or implied that the autofocus sounds wheren't in the Camera.apk; however, if it works then it works.

taufunc said:
Woah, I typed the wrong directory. Thanks, I'll temporarily upload the 2 important files that must be replaced.
I never stated that I had any expectations or implied that the autofocus sounds wheren't in the Camera.apk; however, if it works then it works.
Click to expand...
Click to collapse
Worked flawlessly Thanks dude!

taufunc said:
I never stated that I had any expectations; however, if it works then it works.
Click to expand...
Click to collapse
There is a good chance the EK02 Camera.apk will FC using a different ROMs Camera.odex
You probably should put in BIG letters at the beginning that this is only for EK02 since you aren't backing up the Camera.apk, or at least back up Camera.apk before you overwrite it.
I know you wrote that it is tested on EK02 but trust me, there will be people who don't read, or will read that as it might work on a different release so they will go ahead and try.
---------- Post added at 04:43 AM ---------- Previous post was at 04:39 AM ----------
BTW the filesystem type for /system is ext4, not yaffs2. Also there is no /dev/block/mtdblock3 on Samsung. It is actually /dev/block/mmcblk0p9
The reason your remount works is because on the remount it ignores those parameters and uses the ones it was originally mounted with.
My intention is to help make your modifications work better, not to sound harsh. Apologize if came off that way.

sfhub said:
There is a good chance the EK02 Camera.apk will FC using a different ROMs Camera.odex
You probably should put in BIG letters at the beginning that this is only for EK02 since you aren't backing up the Camera.apk, or at least back up Camera.apk before you overwrite it.
I know you wrote that it is tested on EK02 but trust me, there will be people who don't read, or will read that as it might work on a different release.
---------- Post added at 04:43 AM ---------- Previous post was at 04:39 AM ----------
BTW the filesystem type for /system is ext4, not yaffs2. Also there is no /dev/block/mtdblock3 on Samsung. It is actually /dev/block/mmcblk0p9
The reason your remount works is because on the remount it ignores those parameters and uses the ones it was originally mounted with.
My intention is to help make your modifications work better, not to sound harsh. Apologize if came off that way.
Click to expand...
Click to collapse
I think it worked out for me because i was on stock, even though its EL29. He just had a tiny issue with the system apps directory. All worked well for me, idk about anyone else though haha

Thinking it over, if you aren't going to backup the existing files, it would be quicker if, after remounting /system rw, you just adb pushed the files directly into /system/media rather than copying them to a /sdcard then copying them to /system, the removing the ones from /sdcard.
I would suggest backing up the existing files though.
Also cp -r and rm -r are probably overkill for single file copies.
You can get rid of the copy2sd-img directory. It will make your update MUCH smaller. You aren't installing CWM, so it isn't necessary.
The remount,rw only needs to be done once prior to the first write. Also it is good practice to remount it ro, when you are done.

sfhub said:
Thinking it over, if you aren't going to backup the existing files, it would be quicker if, after remounting /system rw, you just adb pushed the files directly into /system/media rather than copying them to a /sdcard then copying them to /system, the removing the ones from /sdcard.
I would suggest backing up the existing files though.
Also cp -r and rm -r are probably overkill for single file copies.
Click to expand...
Click to collapse
I told the application to push the original sound files from the folder (backupsounds) when anyone chooses to uninstall the silent camera application; the user might delete the files by accidental reason, therefore it'd be better to have a backup folder on your computer.

Sorry, I was wrong about your Camera.apk. I didn't realize the version from kcdedo was deodex'd. It will work on any ROM since it is deodex'd. And I did notice you backed it up, initially I just looked at the .ogg commands which didn't back up the files and didn't look at the entire Camera.apk line to see that it was backed up.
---------- Post added at 05:11 AM ---------- Previous post was at 05:00 AM ----------
locoboi187 said:
I think it worked out for me because i was on stock, even though its EL29. He just had a tiny issue with the system apps directory. All worked well for me, idk about anyone else though haha
Click to expand...
Click to collapse
I was wrong about it not working. The Camera.apk kcdedo is deodexed and self-contained, so it should work with any ROM.
---------- Post added at 05:54 AM ---------- Previous post was at 05:11 AM ----------
taufunc said:
I told the application to push the original sound files from the folder (backupsounds) when anyone chooses to uninstall the silent camera application; the user might delete the files by accidental reason, therefore it'd be better to have a backup folder on your computer.
Click to expand...
Click to collapse
I am not sure if you are understanding my comment.
Instead of writing:
adb push Cam_Start.ogg /mnt/sdcard
adb push Cam_Stop.ogg /mnt/sdcard
adb push camera_click.ogg /mnt/sdcard
adb push camera_click_short.ogg /mnt/sdcard
adb push Shutter_01.ogg /mnt/sdcard
adb push VideoRecord.ogg /mnt/sdcard
adb push Camera.apk /mnt/sdcard
adb shell su -c "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system;rm -r /system/media/audio/ui/Cam_Start.ogg;cp -r /mnt/sdcard/Cam_Start.ogg /system/media/audio/ui;rm -r /mnt/sdcard/Cam_Start.ogg"
adb shell su -c "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system;rm -r /system/media/audio/ui/Cam_Stop.ogg;cp -r /mnt/sdcard/Cam_Stop.ogg /system/media/audio/ui;rm -r /mnt/sdcard/Cam_Stop.ogg"
adb shell su -c "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system;rm -r /system/media/audio/ui/camera_click.ogg;cp -r /mnt/sdcard/camera_click.ogg /system/media/audio/ui;rm -r /mnt/sdcard/camera_click.ogg"
adb shell su -c "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system;rm -r /system/media/audio/ui/camera_click_short.ogg;cp -r /mnt/sdcard/camera_click_short.ogg /system/media/audio/ui;rm -r /mnt/sdcard/camera_click_short.ogg"
adb shell su -c "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system;rm -r /system/media/audio/ui/Shutter_01.ogg;cp -r /mnt/sdcard/Shutter_01.ogg /system/media/audio/ui;rm -r /mnt/sdcard/Shutter_01.ogg"
adb shell su -c "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system;rm -r /system/media/audio/ui/VideoRecord.ogg;cp -r /mnt/sdcard/VideoRecord.ogg /system/media/audio/ui;rm -r /mnt/sdcard/VideoRecord.ogg"
adb shell su -c "mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system;cd /system/app; mv Camera.apk Camera.apk.bak; mv Camera.odex Camera.odex.bak; cp -r /mnt/sdcard/Camera.apk /data/app;rm -r /mnt/sdcard/Camera.apk"
Click to expand...
Click to collapse
you can place all the silence files in a folder, let's say Silent\000silent:
Silent\Camera.apk
Silent\000silent\Cam_Start.ogg
Silent\000silent\Cam_Stop.ogg
Silent\000silent\camera_click.ogg
Silent\000silent\camera_click_short.ogg
Silent\000silent\Shutter_01.ogg
Silent\000silent\VideoRecord.ogg
adb shell su -c "mount -o remount,rw /system /system"
adb push Silent /sdcard/
adb shell su -c "cp /sdcard/000silent/* /system/media/audio/ui"
adb shell su -c "cd /system/app; mv Camera.odex Camera.odex.bak; mv Camera.apk Camera.apk.bak; cp /sdcard/Camera.apk ."
adb shell "cd /sdcard; rm -r Camera.apk 000silent"
adb shell su -c "mount -o remount,ro /system /system"
Click to expand...
Click to collapse
---------- Post added at 06:06 AM ---------- Previous post was at 05:54 AM ----------
sfhub said:
You can get rid of the copy2sd-img directory. It will make your update MUCH smaller. You aren't installing CWM, so it isn't necessary.
Click to expand...
Click to collapse
You might have missed it in the previous post, but you can get rid of the copy2sd-img directory. That will make your update much smaller.

Fixed the dead link.

[Q&A][Help] So you want to be a dev?

This is a thread that will allow you to ask specific questions and get some help with any dev work you may be attempting.
This will be a community effort between enewman17, loserskater, stratatak7, and myself. It would be great if other devs want to join in.
Acceptable questions
"I am trying to recompile X using APK Tool and I get this error. What am I doing wrong?".
"I am trying to flash the ROM I just built and I keep getting a status 0 error. Any thoughts?".
Unacceptable questions
"How do I compile/decompile apks?"
"How do I mod a kernel"
Theming questions go here.
Thread Rules
Do not post unless you have searched the thread.
Only post specific questions.
Only post long sections of code using the code or hide tags.
Your question may not be answered immediately. Be patient.
Use the thanks button (even if you don't get the answer you want).
Many thanks to kennyglass123 for the sticky!

Re: So you want to be a dev?
Just wanted to comment about questions.
The more info the better!
Bad comment: "I can't get X mod to work."
Better: "I'm trying to get X mod to work, and settings keeps FCing. Here's my modified files and a logcat."
Sent from my SAMSUNG-SGH-I747

Anyone feel free to PM me and I'll help you get the ball rolling if you feel your question does not meet thread criteria and you're looking to start development. I realize everyone has to start somewhere. Just be prepared for work.

mine

Now that we have thoroughly thanked each other, maybe someone will stop by with some questions. :silly:

upndwn4par said:
Now that we have thoroughly thanked each other, maybe someone will stop by with some questions. :silly:
Click to expand...
Click to collapse
LOL. I sure hope so.
For those of you reading this, feel free to ask any questions you have about Android development-related modification. I'm sure between the four of us and anyone else who wants to help out that knows what they are doing will know. I'm happy to help out with anything I can.

How do you double the hours in a day so you have enough time to actually do this stuff
Seriously though, this is a great thread and nice to see 4 of the top devs working together and willing to help.
If I ever do find the time I'm sure I'll be back.
Sent from my SGH-I747 using xda premium

jde984 said:
How do you double the hours in a day so you have enough time to actually do this stuff
Click to expand...
Click to collapse
A (somewhat) valid question: For me, it requires a very understanding wife and sleep deprivation.
______________
OK, now let's keep this thread clean and on topic. Thanks!

See in my sig a guide how to decompile apks, edit, and recompile apks! link: http://forum.xda-developers.com/showthread.php?t=2147425
My question: I'm attempting to edit smali for the first time. However, it's pretty foreign. Any guides or tutorials out there? I've searched, but nothing substantive (just some pages on the nomenclature for the dalvik bytecode). My issue is that the instructions for the mod have different registers than me and I can't figure out how to adjust the changes.

It's difficult to answer generic questions like that.
Post up what you are trying to do and maybe we can all work it our together.

headsest control for AOSP
Ok... Team LiquidSmooth is stumped as am I, and I've spent about 8-10 hours searching all in all, through Google, CM threads, Android General/q&a and githubs... I'm still looking but wondering if I could get some help before their team or I pull any more hair out. Basically just what my title says, need the code for controlling music and phone calls from headset controls. The capacitive keys light up when the buttons are pressed but no actions are performed. It's as if the rom is just missing the path for them or something. Any help on where to search or anything, I'm game. Thanks guys.
SOLVED, thanks anyways guys :good:

upndwn4par said:
It's difficult to answer generic questions like that.
Post up what you are trying to do and maybe we can all work it our together.
Click to expand...
Click to collapse
Got it. I'll write up my issues...but, I've been having some trouble with adb and think that might be a bigger issue, haha:
I'm trying to allow adb to run as root. I decompiled boot.img, changed ro.secure to 0, recompiled boot.img, and pushed. Default.prop now shows ro.secure=0. But, I tried running adb remount and I still get permission denied? Someone said there may be other edits required, but I can't seem to find any.
Here's what I changed it to:
{
"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"
}
Here's what ADB is telling me:
Code:
[email protected]:/ $ getprop ro.secure
getprop ro.secure
0
[email protected]:/ $ exit
exit
adb remount
[B]remount failed: Operation not permitted[/B]

ikjadoon said:
Got it. I'll write up my issues...but, I've been having some trouble with adb and think that might be a bigger issue, haha:
I'm trying to allow adb to run as root. I decompiled boot.img, changed ro.secure to 0, recompiled boot.img, and pushed. Default.prop now shows ro.secure=0. But, I tried running adb remount and I still get permission denied? Someone said there may be other edits required, but I can't seem to find any.
Here's what I changed it to:
Here's what ADB is telling me:
Code:
[email protected]:/ $ getprop ro.secure
getprop ro.secure
0
[email protected]:/ $ exit
exit
adb remount
[B]remount failed: Operation not permitted[/B]
Click to expand...
Click to collapse
Try this in terminal...
adb root
Then
adb remount
That should do it for ya.

task650 said:
Try this in terminal...
adb root
Then
adb remount
That should do it for ya.
Click to expand...
Click to collapse
Thanks for the reply! Right: I should probably be root before I try that command. Unfortunately, I tried "adb root" and it said: "adbd cannot run as root in production builds." I did some Google'ing and a few threads said that I should have changed ro.debuggable to 1 as well in default.prop.
So, I changed ro.debuggable=1 and, right, ro.secure=0 still. Then the oddest thing happened: I typed "adb root" into terminal and it went to a new line, no message. And then it disconnected my phone from ADB (I heard the little "ding ding" noise of disconnection). Unfettered, I typed in "adb remount," but of course then it complained that no devices were attached! I thought it was a fluke, so I tried it a few more times. It happened again and again.
In an ostensibly unrelated problem, I couldn't get SecSettings.apk to push back (even though android.policy.jar pushed fine), so I tried a Nandroid. TWRP seemingly did not like my changes to default.prop, as it went crazy (froze a few times) saying "cannot unmount /system" every time I tried a restore and then "Restore failed." Hmm...I pushed back my backed up boot.img and it restored fine.
I'm messing up somehow. So, I'm using VTS to unpack and repack the image. I saw that the output boot.img's are about 6MB, while the default ones I pulled are 10.1MB. Dev said it was probably just compression? Also, I'm pulling the boot.img via adb dd if=/dev/mnt/mmcblk0p7 of=/sdcard/boot.img. Are either of these too weird/wrong?

ikjadoon said:
Thanks for the reply! Right: I should probably be root before I try that command. Unfortunately, I tried "adb root" and it said: "adbd cannot run as root in production builds." I did some Google'ing and a few threads said that I should have changed ro.debuggable to 1 as well in default.prop.
So, I changed ro.debuggable=1 and, right, ro.secure=0 still. Then the oddest thing happened: I typed "adb root" into terminal and it went to a new line, no message. And then it disconnected my phone from ADB (I heard the little "ding ding" noise of disconnection). Unfettered, I typed in "adb remount," but of course then it complained that no devices were attached! I thought it was a fluke, so I tried it a few more times. It happened again and again.
In an ostensibly unrelated problem, I couldn't get SecSettings.apk to push back (even though android.policy.jar pushed fine), so I tried a Nandroid. TWRP seemingly did not like my changes to default.prop, as it went crazy (froze a few times) saying "cannot unmount /system" every time I tried a restore and then "Restore failed." Hmm...I pushed back my backed up boot.img and it restored fine.
I'm messing up somehow. So, I'm using VTS to unpack and repack the image. I saw that the output boot.img's are about 6MB, while the default ones I pulled are 10.1MB. Dev said it was probably just compression? Also, I'm pulling the boot.img via adb dd if=/dev/mnt/mmcblk0p7 of=/sdcard/boot.img. Are either of these too weird/wrong?
Click to expand...
Click to collapse
Are you running adb shell as superuser?
Try:
adb shell
su
adb remount
After typing su you will need to grant superuser permission on your device.
Things to check when pushing with adb:
System, app, and framework folders are mounted r/w in root explorer.
USB debugging is enabled.
I am lazy so I use Eclipse for pushing and pulling files.
Repacked boot images are almost always smaller than the original (sometimes a lot smaller).

upndwn4par said:
Are you running adb shell as superuser?
Try:
adb shell
su
adb remount
After typing su you will need to grant superuser permission on your device.
Things to check when pushing with adb:
System, app, and framework folders are mounted r/w in root explorer.
USB debugging is enabled.
I am lazy so I use Eclipse for pushing and pulling files.
Repacked boot images are almost always smaller than the original (sometimes a lot smaller).
Click to expand...
Click to collapse
EDIT: I gave up, haha. Thank you guys, though. I just copied and pasted both files onto /sdcard and then used the good 'ole adb shell mount -o remount,rw /system and then busybox cp of the files over. Copy worked. And the mod worked. And, honestly, I don't flash enough to make adb root worth it. It's a few extra seconds of my life to type the extra commands instead of taking 2 days to figure out this boot.img....
----
I re-did the ro.secure=0 edit in the boot.img through dsixda's kitchen, just to be sure it wasn't VTS. I also "flashed" it via adb dd in recovery this time instead of in Android. I also left ro.debuggable=0 as that does not seem pertinent to allowing adb to run as root, but simply to debug system apps, etc. Does anyone know any actual information on whether ro.debuggable=0 is required to allow adbd to run as root?
1) ADB shell as superuser: um, I didn't think about that! I thought adb root and adb remount were ADB commands, not shell commands? But, I tried it anyways, but it simply said "error: device not found". See http://prntscr.com/wvjmq
2) Right, ADB shell has SU rights as "always grant" per the SuperSU app.
3) Pushing with ADB: oh, huh! So, adb remount or mount -o remount,rw /system are not recursive? Meaning they only apply to the top-level directory? I think that's what you're saying, but that has never been a problem in the past...I think. And, technically, that doesn't explain why when I didn't mount /system/framework specifically android.policy.jar pushed fine. Pushing SecSettings.apk to /system/app causes a "Permission denied" error. Can Android reject apks? I did a few minor edits to SecSettings.apk, from this mod: http://forum.xda-developers.com/showthread.php?t=2002620
4) Thanks for the boot.img size clarification; got a little worried after having "lost" 40% of the image, haha!
tl;dr:
1) Using either VTS or dsixda's kitchen to modify boot.img to ro.secure=0 and running "adb root" = "adbd cannot run as root in production builds." Pulled and flashed boot.img via adb dd.
2) Unrelated to issue 1 (I think): after mounting system via adb shell (mount -o remount,rw /system), I cannot push SecSettings.apk into /system/app ("Permission denied"), while android.policy.jar pushes just fine /system/framework.
I appreciate everyone's help here. I think it's something really little that I've missed and I just can't figure it out.

ikjadoon said:
EDIT: I gave up, haha. Thank you guys, though. I just copied and pasted both files onto /sdcard and then used the good 'ole adb shell mount -o remount,rw /system and then busybox cp of the files over. Copy worked. And the mod worked. And, honestly, I don't flash enough to make adb root worth it. It's a few extra seconds of my life to type the extra commands instead of taking 2 days to figure out this boot.img....
----
I re-did the ro.secure=0 edit in the boot.img through dsixda's kitchen, just to be sure it wasn't VTS. I also "flashed" it via adb dd in recovery this time instead of in Android. I also left ro.debuggable=0 as that does not seem pertinent to allowing adb to run as root, but simply to debug system apps, etc. Does anyone know any actual information on whether ro.debuggable=0 is required to allow adbd to run as root?
1) ADB shell as superuser: um, I didn't think about that! I thought adb root and adb remount were ADB commands, not shell commands? But, I tried it anyways, but it simply said "error: device not found". See http://prntscr.com/wvjmq
2) Right, ADB shell has SU rights as "always grant" per the SuperSU app.
3) Pushing with ADB: oh, huh! So, adb remount or mount -o remount,rw /system are not recursive? Meaning they only apply to the top-level directory? I think that's what you're saying, but that has never been a problem in the past...I think. And, technically, that doesn't explain why when I didn't mount /system/framework specifically android.policy.jar pushed fine. Pushing SecSettings.apk to /system/app causes a "Permission denied" error. Can Android reject apks? I did a few minor edits to SecSettings.apk, from this mod: http://forum.xda-developers.com/showthread.php?t=2002620
4) Thanks for the boot.img size clarification; got a little worried after having "lost" 40% of the image, haha!
tl;dr:
1) Using either VTS or dsixda's kitchen to modify boot.img to ro.secure=0 and running "adb root" = "adbd cannot run as root in production builds." Pulled and flashed boot.img via adb dd.
2) Unrelated to issue 1 (I think): after mounting system via adb shell (mount -o remount,rw /system), I cannot push SecSettings.apk into /system/app ("Permission denied"), while android.policy.jar pushes just fine /system/framework.
I appreciate everyone's help here. I think it's something really little that I've missed and I just can't figure it out.
Click to expand...
Click to collapse
If you post the kernel (untouched) for me. I will go through the process myself. That when when/if it works I can tell you my exact steps so that you can try it out for yourself. Let me know exactly what you are trying to accomplish also.

task650 said:
If you post the kernel (untouched) for me. I will go through the process myself. That when when/if it works I can tell you my exact steps so that you can try it out for yourself. Let me know exactly what you are trying to accomplish also.
Click to expand...
Click to collapse
You guys are too kind. I feel like you have more important things to do than help a sucker like me. If you're very bored, go ahead.
Attached is my stock, unadulterated boot.img inside a zip. What I am trying to accomplish: push system files from ADB (without going into the shell). I think you need adbd to run as root to do that, right? So, an "insecure" kernel. Thus, I should be able to type "adb root" and then "adb remount" to make /system rw instead of ro and then type "adb push SystemUI.apk /system/app/SystemUI.apk" and it work. I thought I just needed to make ro.secure=0 in the boot.img's default.prop, but it looks like that is not enough.
But, honestly, if it looks like it takes too much time (I'm serious; I honestly think Samsung sent me a borked phone), it's all good. ADB shell and Busybox cp will suffice. I'm just more curious of what I am doing wrong here.
~Ibrahim~

Interesting. I am getting the same error (yes, ro.secure=0 and ro.debuggable=1).
As soon as I am finished with the update I am working on I will look in to this - unless Task figures it out first. If for no other reason, just because I want to know.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Me>cd c:\android
c:\Android>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
041b9c2b device
c:\Android>adb shell
[email protected]:/ $ adb root
adb root
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ su
su
[email protected]:/ # adb remount
adb remount
error: device not found
1|[email protected]:/ # adb root
adb root
error: device not found
1|[email protected]:/ #WTF?

upndwn4par said:
Interesting. I am getting the same error (yes, ro.secure=0 and ro.debuggable=1).
As soon as I am finished with the update I am working on I will look in to this - unless Task figures it out first. If for no other reason, just because I want to know.
Code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Me>cd c:\android
c:\Android>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
041b9c2b device
c:\Android>adb shell
[email protected]:/ $ adb root
adb root
* daemon not running. starting it now on port 5038 *
* daemon started successfully *
error: device not found
1|[email protected]:/ $ su
su
[email protected]:/ # adb remount
adb remount
error: device not found
1|[email protected]:/ # adb root
adb root
error: device not found
1|[email protected]:/ #WTF?
Click to expand...
Click to collapse
You shouldn't be running adb root inside of a shell. You're running two instances of adb and only need the first connection. The reason you're getting device not found is because you're running an instance of adb on the device and it's looking for other devices. Try it again without running adb shell.
Sent from my SAMSUNG-SGH-I747