How can I force install an apk? I just started running JellyBam 5.2 on my sprint s3 and really want ALL of the stock apps. I have S voice, paper artist, and the file manager. But it will not let me install video player nor music hub. I have the apks, can I force install them.
Sent from my SPH-L710 using xda app-developers app
Try installing through your computer.
Connect the phone, turn on usb debugging, and run the following, replacing "app.apk" with the name of each app
Code:
adb install -r app.apk
Sent from my PG06100
Tutorial?
Sent from my SPH-L710 using xda app-developers app
Download adb from my dev-host right here. Grab the "adb_windows.zip" and extract it somewhere
Now take the app you wanna install and copy it into the folder where you extracted the contents of "adb_windows". The app will be referred to as "app.apk"
Then go to the extracted folder and Shift+RightClick > Open command window here
Type the following into the terminal and press enter
Code:
adb install -r app.apk
Make sure "usb debugging" is enabled on your phone (Settings > Developer options)
Some you have to move to system/app and reboot
Sent from my SPH-L710 using xda premium
gtuansdiamm said:
Some you have to move to system/app and reboot
Sent from my SPH-L710 using xda premium
Click to expand...
Click to collapse
This installs as a user app
Code:
adb install -r app.apk
This installs as a system app
Code:
adb push app.apk /system/app
Alternate version that pushes to sd, and then uses a superuser command to copy to /system/app
Code:
adb push app.apk /sdcard/app.apk
adb shell "su -c 'mount -o rw,remount system; cp /sdcard/app.apk /system/app/app.apk'"
adb shell "su -c 'mount -o ro,remount system"
EDIT: Changed push code. It was just pushing to sdcard before, sorry
Correct me if the internal sd is not called "sdcard" as I do not have this phone yet
EDIT2: Thanks whiplashh
Sent from my PG06100
Correct me if the internal sd is not called "sdcard" as I do not have this phone yet
Sent from my PG06100
Click to expand...
Click to collapse
You are correct. It is sdcard unless its an aosp ROM then it is sdcard0
Sent From My Rooted, S-OFF'd Blackberry Curve using the iOS XDA Application for Android.
Hey just googled this question and this thread came up. Thank you all for this method. Worked for me on 4.2 :beer:
Sent from my E4GT using Tapatalk 2
Gazzuk said:
Hey just googled this question and this thread came up. Thank you all for this method. Worked for me on 4.2 :beer:
Sent from my E4GT using Tapatalk 2
Click to expand...
Click to collapse
No problem
Just an FYI, but this works for all android versions :beer:
Sent from my PG06100
I get the following when using ADB to install
[email protected]:~/Copy/HTC_One/TV$ adb install -r com.htc.videoCenter.apk
adb server is out of date. killing...
* daemon started successfully *
4381 KB/s (1989867 bytes in 0.443s)
pkg: /data/local/tmp/com.htc.videoCenter.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
CNexus said:
Try installing through your computer.
Connect the phone, turn on usb debugging, and run the following, replacing "app.apk" with the name of each app
Code:
adb install -r app.apk
Sent from my PG06100
Click to expand...
Click to collapse
Floyd_Flivercod said:
I get the following when using ADB to install
[email protected]:~/Copy/HTC_One/TV$ adb install -r com.htc.videoCenter.apk
adb server is out of date. killing...
* daemon started successfully *
4381 KB/s (1989867 bytes in 0.443s)
pkg: /data/local/tmp/com.htc.videoCenter.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
Click to expand...
Click to collapse
Try this
Code:
adb push app.apk /sdcard
adb shell su -c "pm install /sdcard/app.apk"
Either way, that app looks like a system app, so you should push it to /system/app.
Use my code from a couple posts above to do that.
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
CNexus said:
Download adb from my dev-host right here. Grab the "adb_windows.zip" and extract it somewhere
Now take the app you wanna install and copy it into the folder where you extracted the contents of "adb_windows". The app will be referred to as "app.apk"
Then go to the extracted folder and Shift+RightClick > Open command window here
Type the following into the terminal and press enter
Code:
adb install -r app.apk
Make sure "usb debugging" is enabled on your phone (Settings > Developer options)
Click to expand...
Click to collapse
Could you reupload adb?
Schwabie64 said:
Could you reupload adb?
Click to expand...
Click to collapse
Ah, out looks like dev-host mixed up my links
It's still there, but here's the right link: http://d-h.st/users/CNexus/?fld_id=7741#files
The Thanks button is just to avoid "THANKS" posts in threads. Nothing more. Don't defeat the purpose of why it was introduced.
trevonc91 said:
How can I force install an apk? I just started running JellyBam 5.2 on my sprint s3 and really want ALL of the stock apps. I have S voice, paper artist, and the file manager. But it will not let me install video player nor music hub. I have the apks, can I force install them.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
any Help ?
Attempting to install ROMToolboxPr.apk...
adb server is out of date. killing...
* daemon started successfully *
3772 KB/s (7900663 bytes in 2.045s)
pkg: /data/local/tmp/ROMToolboxPr.apk
Failure [INSTALL_FAILED_UID_CHANGED] :crying:
Welp please
Welp:
C:\Users\kuba\Desktop\Desktop Stuff\adb_windows\adb_windows>adb install -r app.apk
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
3346 KB/s (911481 bytes in 0.266s)
pkg: /data/local/tmp/app.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
I renamed the app to app.apk (didn't enter the extension, was already there) and it didn't work. I did open it with WinRAR but I didn't change anything in the META-INF folder.
Phone: Samsung Galaxy Y GT-S5360
LanCeeXD said:
Welp:
C:\Users\kuba\Desktop\Desktop Stuff\adb_windows\adb_windows>adb install -r app.apk
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
3346 KB/s (911481 bytes in 0.266s)
pkg: /data/local/tmp/app.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
I renamed the app to app.apk (didn't enter the extension, was already there) and it didn't work. I did open it with WinRAR but I didn't change anything in the META-INF folder.
Phone: Samsung Galaxy Y GT-S5360
Click to expand...
Click to collapse
No, you replace app.apk with the name of the app you are trying to install in the command. ex- Facebook.apk
And depending on what it is you may have to push it to system/app instead of data/app
{
"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"
}
CNexus said:
This installs as a user app
Code:
adb install -r app.apk
This installs as a system app
Code:
adb push app.apk /system/app
Alternate version that pushes to sd, and then uses a superuser command to copy to /system/app
Code:
adb push app.apk /sdcard/app.apk
adb shell "su -c 'mount -o rw,remount system; cp /sdcard/app.apk /system/app/app.apk'"
adb shell "su -c 'mount -o ro,remount system"
EDIT: Changed push code. It was just pushing to sdcard before, sorry
Correct me if the internal sd is not called "sdcard" as I do not have this phone yet
EDIT2: Thanks whiplashh
Sent from my PG06100
Click to expand...
Click to collapse
I tried that, but I get this error:
xBeNx69 said:
I tried that, but I get this error:
Click to expand...
Click to collapse
It looks like the apk is bad (not compiled correctly)
My ROM: WICKED X
bilgerryan said:
It looks like the apk is bad (not compiled correctly)
My ROM: WICKED X
Click to expand...
Click to collapse
I took this APK from a samsung stock rom apps, is there anyway i can resign it to work on my device?
Sent from my XT1063 using Tapatalk 2
xBeNx69 said:
I took this APK from a samsung stock rom apps, is there anyway i can resign it to work on my device?
Sent from my XT1063 using Tapatalk 2
Click to expand...
Click to collapse
I'm guessing it you took it from an odexed stock ROM and you're trying to use it on a deodexed ROM.
My ROM: WICKED X
Related
can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!
betterment66 said:
can someone please post DETAILED isntructions to put froyo or gingerbread youtube app thing on samsung epic 4g. ive tried so many time and cant do it. and i delted the stock youtube app with titanium but cant install the other app and i dont wanna pay for root explorer cuz idk if its gonna help at all. i tried using the cmd promt but it says permission denied everytime and it also says adb is not recognized as an internal storage.. PLEASE SOMEONE HELP MEEE I DONT HAVE A YOUTUBE AP AT ALL NOW!!!!!
Click to expand...
Click to collapse
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.
gremlyn1 said:
The new YouTube.apk just needs to be placed in '/system/app'. What I did was remove the original YouTube.apk and put the new one in its place and voila. Here is the method adapted for Windows (I think it's all right for Windows). This is also assuming you rooted with a one click root that included the remount script and that you have adb on your computer (the one click rooter should have adb included with it).
1. in the cmd prompt, go to the folder where you have adb and type:
Code:
adb.exe shell
2. inside shell:
Code:
$ su
# remount rw
# mkdir /sdcard/backup
# cp /system/app/YouTube.apk /sdcard/backup
# rm /system/app/YouTube.apk
# exit
$ exit
3. now in the cmd prompt again:
Code:
adb.exe push \path\to\YouTube.apk /system/app
4. Reboot the phone.
Click to expand...
Click to collapse
ok i get to remount rw but the when i type in the nect code it says
mkdir falied for /sdcard/backup read-only filesystem
I install it using terminal emulator.
All I do is type
Su
#rm /system/app/YouTube.apk
#cp /sdcard/DirectoryWithTheYoutubeApp/YouTube.apk /
system/app
Or after you rm, just use the "My Files" app and go on your sdcard and click YouTube.apk and it'll install and work fine. But remember to sign out of youtube before you close it by going to your page and clicking sign out or else it'll keep force closing after you start it up.
I hope I helped...
Sent from my SPH-D700 using XDA App
you guys are gonna freaking kill me. ALL THE TROUBLE I WAS HAVING WAS BECAUSE I HAD MY SDCARD MOUNTED THE WHOLE TIME I WAS TRYING TO DO THIS THE MINUTE I TRIED IT WITHOUT IT BEING MOUNTED IT WORKED...IM SO DUMB!!!!! LOL BUT THANKS FOR THE HELP ALL OF U!!!!!! U GUYS ROCK!!!! N SO DOES THE NEW UTUBE APP .....BTW I UNDERSTAND UR NOT SUPPOSED TO SIGN IN TO IT RIGHT???
I just uninstalled the original, put the modded youtube.apk in the SDX backup folder and installed (restored) it with SDX stock app remover. Simple, fast and no typing required.
Glad you got it worked out though.
me 2!!! this app rocks
Glad it's working! Having the SD card mounted while trying to adb is a common mistake and always a good first troubleshooting check.
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/
Has anyone been able to update the binaries using the latest version of Superuser (v3)? The application successfully updated via the Market for me, but I cannot get the binaries to update properly.
{
"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"
}
Looking for a workaround to Superuser not being able to write to /sbin/su
ROM: SRF 1.2
Kernel: Twilight Zone 1.1.1
We're trying to figure it out. I'm getting the same thing. Not all users are. Very odd error. Not even the install assister is helping for me. You should try it from the Market if you haven't already.
The Root said:
We're trying to figure it out. I'm getting the same thing. Not all users are. Very odd error. Not even the install assister is helping for me. You should try it from the Market if you haven't already.
Click to expand...
Click to collapse
I should have mentioned that I already did that and no dice. That update assist application is more for signature mismatches, as per the app description in the Market.
Basicly, it says if you reboot the binary will be downgraded so why try. Get a new kernel
Sent from my SPH-D700 using Tapatalk
ugothakd said:
Basicly, it says if you reboot the binary will be downgraded so why try. Get a new kernel
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Well I've tried out Genocide v2 and it kept causing the black screen of death on my phone. I had to go back to Twilight in order to get stable again. (Stock speeds and voltage when using Genocide too.)
I've come to realize my phone is finicky.
Sent from my SPH-D700 using Tapatalk
nikon120 said:
Well I've tried out Genocide v2 and it kept causing the black screen of death on my phone. I had to go back to Twilight in order to get stable again. (Stock speeds and voltage when using Genocide too.)
I've come to realize my phone is finicky.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
Did you try Genocide 1.1 Final? At first Genocide 2.0 wasn't playing nice with my phone either but now its working fine. We are looking into updating Twilight to have 1.4 frequency and updated binaries
Sent from my SPH-D710 using xda premium
JohnCorleone said:
Did you try Genocide 1.1 Final? At first Genocide 2.0 wasn't playing nice with my phone either but now its working fine. We are looking into updating Twilight to have 1.4 frequency and updated binaries
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
I did not try Genocide 1.1 final. I will give that one a go after vacation.
Edit: on 4G for like the 3rd time ever. I hate you Sprint for sucking so hardcore with you infrastructure.
Sent from my SPH-D700 using Tapatalk
I'll post chain's solution in a bit. I have to test it.
Sent from my SPH-D700 using XDA App
Pretty sure my issue is exactly the same...
http://forum.xda-developers.com/showthread.php?t=1280641
Running SRF 1.2 with Genocide 2.0..
How to from DDChains
If you have adb, run:
adb remount
adb shell rm /system/app/Superuser.apk
adb shell pm uninstall com.noshufou.android.su
adb reboot
Or from a terminal app on your phone, run:
$ su
# (your phone's remount command, on the Nexus One it's 'mount -o remount,rw /dev/block/mtdblock3 /system'. Other pones follow the same pattern, but may vary on the '/dev...' block)
# rm /system/app/Superuser.apk
# pm uninstall com.noshufou.android.su
# (same remount command as above, but use 'remount,ro' instead of 'remount,rw')
Then reboot your phone as normal.
This is of course on an Epic running SRF 1.2..
Don't have access to ADB at the moment so tried using terminal on the phone.
After running the su command, typed:
Code:
'mount -o remount,rw /dev/block/mtdblock3 /system'
And received
Code:
mount -o remount,rw /dev/block/mtdblock3 /system: not found
Did I type something wrong or should I be using a different command?
Thanks for the help & time..
Coucher said:
This is of course on an Epic running SRF 1.2..
Don't have access to ADB at the moment so tried using terminal on the phone.
After running the su command, typed:
Code:
'mount -o remount,rw /dev/block/mtdblock3 /system'
And received
Code:
mount -o remount,rw /dev/block/mtdblock3 /system: not found
Did I type something wrong or should I be using a different command?
Thanks for the help & time..
Click to expand...
Click to collapse
same, i'm trying to find the proper mount codes for the epic. as he said, that's the nexus mount code
This may help..
http://wiki.sdx-developers.com/index.php/Commands
Problem with ADB command
The Root said:
If you have adb, run:
adb remount
adb shell rm /system/app/Superuser.apk
adb shell pm uninstall com.noshufou.android.su
adb reboot
Or from a terminal app on your phone, run:
$ su
# (your phone's remount command, on the Nexus One it's 'mount -o remount,rw /dev/block/mtdblock3 /system'. Other pones follow the same pattern, but may vary on the '/dev...' block)
# rm /system/app/Superuser.apk
# pm uninstall com.noshufou.android.su
# (same remount command as above, but use 'remount,ro' instead of 'remount,rw')
Then reboot your phone as normal.
Click to expand...
Click to collapse
I tried using the ADB method you outlined above, but when I got to this line: adb shell pm uninstall com.noshufou.android.su
I got this error message below:
/sbin/sh: pm: not found
Any ideas why?
**EDIT** I just tried using the Terminal Emulator method and was successful
The following command worked for me for some reason:
mount -o remount,rw /dev/block/mtdblock3 /system
But I'm still curious to see why I got that error in ADB.
Terminal method didn't work.
Sent from my SPH-D700 using XDA App
I'm using the most recent AOSP ROM which has Genocide 2.0 as the built-in kernel. I had this and it updated fine. I was coming from the ERA Revolt ROM before that. Did a wipe of everything before, of course.
To be honest, I didn't even know what was all going on, I just kept clicking through and the binaries updated just fine.
If I can be of help somehow, please let me know.
GRK4G63 said:
I
**EDIT** I just tried using the Terminal Emulator method and was successful
The following command worked for me for some reason:
mount -o remount,rw /dev/block/mtdblock3 /system
But I'm still curious to see why I got that error in ADB.
Click to expand...
Click to collapse
Ok, it was user error for me. I was putting ' in front of and after the command.
The terminal process worked for me and got me back to a fully working (older. 2.3.1 -ef) SuperUser.
Guess the 3.0 just isn't ready for primetime yet?
My tab updated fine.
Sent from my SPH-D700 using XDA App
Coucher said:
Ok, it was user error for me. I was putting ' in front of and after the command.
The terminal process worked for me and got me back to a fully working (older. 2.3.1 -ef) SuperUser.
Guess the 3.0 just isn't ready for primetime yet?
Click to expand...
Click to collapse
Kernel developers build superuser and su into the kernel...this is what "root" is...so 9/8 times there going to be using the superuser everyone knows about, 2.3.x. (Fraction mess up on person) The only way to get around this is ask the dev of your kernel to make a non-rooted version, or use a stock kernel.
ugothakd said:
Kernel developers build superuser and su into the kernel...this is what "root" is...so 9/8 times there going to be using the superuser everyone knows about, 2.3.x. (Fraction mess up on person) The only way to get around this is ask the dev of your kernel to make a non-rooted version, or use a stock kernel.
Click to expand...
Click to collapse
Yeah tanimn's still busy, we're hunting someone down.
Sent from my SPH-D700 using XDA App
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
Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.
broodplank1337 said:
Now next to the i9500 Quick Flasher there also is the i9505 Quick Flasher, just slight changes to make partitions match
Download:
www.broodplank.net/I9505-Quick-Flasher-1.0.zip
Created for a fail-safe flash operation of boot.img and recovery.img, all other partitions (currently only system) are experimental.
Click to expand...
Click to collapse
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.
Snakefood said:
Tried this, it cannot connect to my S4. Yes, I have debugging enabled, and yes my device is in mtp mode.
I get:
Running checks, please wait...
<<< I9505 USB Connection >>>
[ ] I9505 USB Connection
Your I9505 is not connected or unreachable! Please read the instructions for reference.
Click to expand...
Click to collapse
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.
broodplank1337 said:
I had some issues with usb as well when I was testing the tool out, but It was fixed after a while, its actually not the tool but the way of mounting usb on the i9505. I fixed it by replacing the adb.exe file with the latest one (which is also included in the zip tho). Can you please test for me if your able to get a normal adb shell? (open cmd window in the quickflasher dir and type "adb shell"), if it says device not found there is an issue with debugging mode. if not then you should test this and pls give me the info:
adb get-state (should return "device")
adb devices (should return a connected device)
If you get negative results here you should kill adb.exe (taskkill /f /im adb.exe for group kill) and try again.
If it does work pls enter:
adb root
adb remount
adb shell
and tel me what you see.
The usb mode is a struggle on the i9505.. I thought hey lets upgrade to CM so I will have mass storage mode.. but no way, only MTP and PTP... (I added the Mass storage option and forced it to be available on my private build, but it still doesn't work..)
Currently trying to find out how to permanently enable oldskool mass storage + adb.
Click to expand...
Click to collapse
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>
Snakefood said:
My results:
C:\Windows\system32>cd \
C:\>cd s4 root
C:\S4 root>cd qflash
C:\S4 root\qflash>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: more than one device and emulator
C:\S4 root\qflash>adb get-state
unknown
C:\S4 root\qflash>adb devices
List of devices attached
12138fc0 device
emulator-5554 offline
C:\S4 root\qflash>adb root
error: more than one device and emulator
C:\S4 root\qflash>
Click to expand...
Click to collapse
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Edit: I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?
Snakefood said:
What emulator do I have, I've only used the files in your download, as far as I know. Any way to check / remove?
Click to expand...
Click to collapse
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )
broodplank1337 said:
Hmm the emulator that comes with android sdk, is afaik the only one who can correspond with adb, but it would be odd if you ran it all the time.
check taskmgr, and look for emulator.exe/java.exe, to be sure also kill adb.
You can check if there is an existing emulator if you start AVD manager (if you don't have android sdk at all then its really strange )
Click to expand...
Click to collapse
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $
Snakefood said:
I didn't have sdk installed; I installed it and ran avd manager, doesn't show any installed.
when I run adb -d shell I get [email protected]:/ $
Click to expand...
Click to collapse
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot
broodplank1337 said:
Ok the output is good. ill add a function to the tool to force adb usb connection
for the meanwhile you can use:
(put boot.img in adb dir)
adb -d push boot.img /sdcard/boot.img
adb -d shell su -c 'dd if=/sdcard/boot.img of=/dev/block/mmcblk0p20'
adb -d shell reboot
Click to expand...
Click to collapse
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?
Snakefood said:
Do I rename my recovery.img from cwm to boot.img for the above, or is this for a different process?
Click to expand...
Click to collapse
boot.img = mmcblk0p20
recovery.img = mmcblk0p21
the name of the .img doesn't matter but the partition is important.
Ahh, looking at your image, this now makes sense, I can see the destination partition names as you describe..
Well have a go at this later, unless you plan to release an update later today?
Sent from my Nexus 7 using xda app-developers app
Edit: couldn't get this working, so I just flashed using odin. Thanks for trying to get resolved tho.
Odin is the tool for me, no need more than that.
broodplank1337 said:
ah so you have the emulator in there as well.. thats the problem. to bypass the emulator use:
adb -d
for example adb -d shell or adb -d get-state
do you have an AVD emulator running currently?
Click to expand...
Click to collapse
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.
skywalker01 said:
Hi brood,
just stumbled upon this thread and read about Snakefood's problem.
Although he worked around the error by using Odin I want to give you a hint regarding this specific problem:
he obviously has an adb device installed called emulator-5554 but which is offline. He already gave himself the correct answer:
"I had bluestacks installed a while back, but uninstalled it, could this have left some crap behind after it?"
My diagnose is: yes, BlueStacks definitely leaves a lot of crap behind and does NOT uninstall cleanly. I tested it once and I saw myself compelled to restore an older windows image which I made BEFORE I installed BlueStacks on my windows machine.
BTW: BlueStacks is an Android emulator for Windows but a piece of *%$~#!!! crap, but that's just my humble opinion.
And BlueStacks uses such an adb emulator device entry although I'm not sure if it was called like that. But BlueStacks is not the only Android emulator and most probably other programs of this kind create such an adb entry as well.
Click to expand...
Click to collapse
Hi Skywalker.
Long time no see . Anyways, OT. I have installed BlueStacks once (in the alpha or beta phase I believe) and I don't remember much of it but I do remember that it was crap idd. Also that it leaves "traces" (if you call adb a trace xd, more like a fail uninstall ) is very lame.. and causing problems for people who are not 100% familiar with adb and its daemon.
The AVD Emulator from the SDK may lag a bit but atleast it doesn't interfere with adb :silly:
Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes
dublinz said:
Great tool broodplank1337, well done mate this will save ppl from making stupid mistakes
Click to expand...
Click to collapse
Thanks ^^, I think that is true hehe, using 'dd' to flash images isn't for the absolute beginner idd ;p
Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app
Snakefood said:
Hi guys,
If you need me to assist more with ahh testing just let me know. Is there an uninstaller to remove what bluestacks left behind, or is the Windows disc the only definite uninstaller
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
You should first look in msconfig (start > run > msconfig) at the startup tab and look if there is any startup item from bluestacks.
If there is nothing there look in services.msc (start > run > services.msc) and check for any blue stacks service, and if there is any, disable it.
Next to that you can also use HijackThis (http://sourceforge.net/projects/hjt/) to find startup items. hope it helps
Hey Brood,
See you're doing great work here on the S4 section.:good:
I'm missing your input in the S+ section unfortunatly:crying: