Related
Some of you are familiar with the adb install command.
Is there an equivalent of it in the terminal emulator?
Hi,
Adb is used from the computer and terminal emulator is used from the phone.
What are you trying to do?
I'm trying to install an app without using astro.
your best choise would be
cd to the location of the apk file and use
adb install appname.apk
or adb install C:\folder\appname.apk
think thats the correct way im not sure how you can install it in the terminal i knwowho to remove it.. but not install :/
Install .apk via Terminal EMulator
1) Place the .apk on the root of your SD card (for simplicity)
2) Type "su"
3) cd into the destination of your .apk (in this case it will be cd /sdcard)
4) Use "install "name of .apk" /"destination"/"name of .apk"
su
cd /sdcard
install com.makemobile.coursepro.apk /system/app/com.makemobile.coursepro.apk
further example:
install "space" com.makemobile.coursepro.apk "space" /system/app/com.makemobile.coursepro.apk
This will install the app on your phone using the Terminal Emulator. The destination location can change as well.
Additional help: http://www.busybox.net/downloads/BusyBox.html
On the flip side, could you uninstall from the ext2 partition this way?
install on/from ext2
not sure...I'll looks into this. I had my apps and data on my sd however, it seemed a little buggy and inconsistant. It may have been due to using original G1 1gb class 2 card.
-let me know if you find out first.
a1t said:
1) Place the .apk on the root of your SD card (for simplicity)
2) Type "su"
3) cd into the destination of your .apk (in this case it will be cd /sdcard)
4) Use "install "name of .apk" /"destination"/"name of .apk"
su
cd /sdcard
install com.makemobile.coursepro.apk /system/app/com.makemobile.coursepro.apk
further example:
install "space" com.makemobile.coursepro.apk "space" /system/app/com.makemobile.coursepro.apk
This will install the app on your phone using the Terminal Emulator. The destination location can change as well.
Additional help: http://www.busybox.net/downloads/BusyBox.html
Click to expand...
Click to collapse
nevermind..........used astro file manager and it worked fine
help
what's 'cd' ? the emulator is already installed on the phone ?
i'm trying to install an app but i don't understand the adb method. someone can help me ?
thanks
MikeMadden said:
what's 'cd' ? the emulator is already installed on the phone ?
i'm trying to install an app but i don't understand the adb method. someone can help me ?
thanks
Click to expand...
Click to collapse
cd is a command, meaning "change directory". Which is used to move your location on the system.
MikeMadden said:
what's 'cd' ? the emulator is already installed on the phone ?
Click to expand...
Click to collapse
cd is a *nix command , it is short for 'change directory' and it... changes directory
MikeMadden said:
i'm trying to install an app but i don't understand the adb method. someone can help me ?
thanks
Click to expand...
Click to collapse
it depends on what the app is
your best bet would be to get an app called 'Astro file manager' from the market
Its quite easy, so I won't go into further detail
Which to be honest is a fair trade
APrinceAmongMen said:
Some of you are familiar with the adb install command.
Is there an equivalent of it in the terminal emulator?
Click to expand...
Click to collapse
Some people have mentioned the `install' command from BusyBox, but this won't quite do what you probably want. To invoke the full Android package installation experience--the complete equivalent of `adb install'--you're looking for `pm install'. It takes the same arguments that `adb install' does, checks signatures, creates the appropriate user accounts, etc. so the package is installed the Android way. You can also use `pm uninstall' to remove a package (and as with `adb install', the "-k" option keeps its data around).
The `am' and `pm' commands are both underdocumented, but can be terribly useful. `am' can issue arbitrary Intents, including some Extra values. `pm' has other features not mentioned here, but which are shown in the help text.
olearyp said:
Some people have mentioned the `install' command from BusyBox, but this won't quite do what you probably want. To invoke the full Android package installation experience--the complete equivalent of `adb install'--you're looking for `pm install'. It takes the same arguments that `adb install' does, checks signatures, creates the appropriate user accounts, etc. so the package is installed the Android way. You can also use `pm uninstall' to remove a package (and as with `adb install', the "-k" option keeps its data around).
The `am' and `pm' commands are both underdocumented, but can be terribly useful. `am' can issue arbitrary Intents, including some Extra values. `pm' has other features not mentioned here, but which are shown in the help text.
Click to expand...
Click to collapse
'pm install' often fails with [INSTALL_FAILED_INSUFFICIENT_STORAGE]
which used to frustrate me no end ..
simple shell script
Code:
am start -a android.intent.action.VIEW -t application/vnd.android.package-archive -d file://$1
just pass the full path e.g
sh /sdcard/installapk.sh /sdcard/theapp.apk
and it pops up the Android Package installer
Firerat said:
'pm install' often fails with [INSTALL_FAILED_INSUFFICIENT_STORAGE]
which used to frustrate me no end ..
Click to expand...
Click to collapse
Interesting. I wonder if that's related to A2SD or a particular implementation, and pm getting confused as a result? Still, I like the idea of sending the VIEW intent to bring up the package installer. Good snippet.
I just cp the files to /system/sd/app/
from Windows Command prompt, and after switching to the folder containing the .apk file, type:
adb install filename.apk
if it is a reinstall:
adb install -r filename.apk
you could also push the file to the app folder. I use this method to push system apk:
adb remount <<<< you have to remount since you're going to mess with a sys folder
adb push filename.apk /system/app
seriously useful thread... especially after for some weird reason certain apps fail to install using the default Android installer. *cough* Radiant *cough*
Thanks for the help guys. Btw install command doesn't work. To clear things out for some clueless person like I am :
1. Open Terminal Emulator
2. Type -
su
cd /dir
pm install appname.apk
3. Done!
Example -
su
cd /sdcard
pm install AstroFileManager.apk
Hope that can help!
rajasyaitan said:
Thanks for the help guys. Btw install command doesn't work. To clear things out for some clueless person like I am :
1. Open Terminal Emulator
2. Type -
su
cd /dir
pm install appname.apk
3. Done!
Hope that can help!
Click to expand...
Click to collapse
This is very helpful, thanks!
rajasyaitan said:
Thanks for the help guys. Btw install command doesn't work. To clear things out for some clueless person like I am :
1. Open Terminal Emulator
2. Type -
su
cd /dir
pm install appname.apk
3. Done!
Example -
su
cd /sdcard
pm install AstroFileManager.apk
Hope that can help!
Click to expand...
Click to collapse
Thanks big time. Installed perfectly although apk won't open...just got to find one that will.
I'm having trouble with step 4 of the rooting guide. The command prompt says:
data/local/gingerbreakBB: not found
Where should I place the files from the zip? Inside the platform-tools folder? Or inside a different folder?
Thanks in advance for helping a noob.
You need to put all of those files in the platform-tools folder or wherever advanced is located
Sent from my HTC Eva 4G using Tapatalk
Jocelyn said:
You need to put all of those files in the platform-tools folder or wherever advanced is located
Sent from my HTC Eva 4G using Tapatalk
Click to expand...
Click to collapse
All the files were in the platform-tools folder originally. Just making sure because it isn't working.
Cory1234 said:
All the files were in the platform-tools folder originally. Just making sure because it isn't working.
Click to expand...
Click to collapse
Did you change directories in Cprompt/terminal?
PS advanced above = adb silly spellchecker
Sent from my HTC Eva 4G using Tapatalk
Jocelyn said:
Did you change directories in Cprompt/terminal?
PS advanced above = adb silly spellchecker
Sent from my HTC Eva 4G using Tapatalk
Click to expand...
Click to collapse
Do you mean like to: C:\program files (x86)\android\android-sdk\platform-tools
??
I'm going to reinstall everything one more time.
Ok I got step 4 to go through, but I didn't get a number. When I try to redo step 4 it gives me this error: "cannot copy boomsh.: Permission denied.
What should I be looking for after step 4?
Cory1234 said:
Ok I got step 4 to go through, but I didn't get a number. When I try to redo step 4 it gives me this error: "cannot copy boomsh.: Permission denied.
What should I be looking for after step 4?
Click to expand...
Click to collapse
You need to remove them and start over
run these two lines then start from step 1
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
after step 4 if it successfully install you'll see a
[!] dance forever my only one
#
Also remember step 4 is actually a two lines process
run adb shell {Enter}
/data/local/gingerbreakBB {Enter}
Don't forget to open a DIFFERENT terminal window for steps 7-9
baseballfanz said:
You need to remove them and start over
run these two lines then start from step 1
adb shell rm /data/local/tmp/boomsh
adb shell rm /data/local/tmp/sh
after step 4 if it successfully install you'll see a
[!] dance forever my only one
#
Also remember step 4 is actually a two lines process
run adb shell {Enter}
/data/local/gingerbreakBB {Enter}
Don't forget to open a DIFFERENT terminal window for steps 7-9
Click to expand...
Click to collapse
Thanks. I got that info earlier by using google . Now I'm stuck on step 9. I am in a new terminal window. The output I receive after entering "md5sum cwm_blob_retransfer" is "md5sum is not recognized as an internal or external command, etc.
I also tried md5sums as another member commented on. Still no go.
This is starting to get frustrating..Jailbreaking was simple compared to this.
Anyone have any ideas?
Edit: Dur, Finally got it. Apparently, some of the files had write protection on them for some reason, which was causing all the problems. Thanks everyone for the help.
First off, all credit goes to nubecoder. Original post:
[Bash] android_bash: Bash, cross-compiled and modified for the android platform.
Introduction...
Most (All) modern Linux distributions utilize bash (Bourne Again SHell) rather than sh (Bourne SHell). Android, by default uses sh. Bash has numerous advantages over sh, sush as tab completion and history support.
Some ROM developers include bash in their ROMs by default. It makes adb, terminal, and scripted commands much easier and more powerful/flexible. I noticed that Sidekick 4G ROMs don't come with bash, hence this thread.
How to Install BASH...
Simpy flash this zip through Clockworkmod recovery: (if ORANGE, check mounts. Not sure if neccessary, but it doesn't hurt)
android_bash-4.1.11(2)_installer-SK4G.zip
Then load your preffered terminal emulator application, type bash, press enter, and there you go.
What's the difference between the SK4G version, and the original Epic 4G version?
- Modified device/product check in updater-script to "SGH-T839"
- Modified $PATH variable in /data/local/.profile to "/sbin:/system/bin:/system/xbin:/data/local/tmp:/bin"
- Modified $PATH variable in /system/etc/bash.bashrc to "/sbin:/system/bin:/system/xbin:/data/local/tmp:/bin"
- [Personal preference] Add alias su='su -c bash' to /data/local/.bash_aliases
- [Personal preference] Modified $PS1 to PS1="\[$txtgrn\]\w $ \[\e[m\]"
- [Personal preference] Modified root $PS1 to PS1="\[$txtred\]\w # \[\e[m\]"
- [Personal preference] Modified location of .bash_history from /sdcard/.bash_history to /data/local/.bash_history
Click to expand...
Click to collapse
As any experienced bash user should know, if you want to revert/modify my personal preferences, just modify "/data/local/.bashrc", "/data/local/.bash_aliases", or "/system/etc/bash.bashrc" to your liking.
Extras...
mntsystem Make /system partition read-only or read-write. Usage:
# mntsystem [ro|rw|status]
Unzip mntsystem.zip, copy mntsystem to /system/bin, chmod 744 /system/bin/mntsystem
Click to expand...
Click to collapse
defaultshell Replace sh with bash, or revert. Usage:
# defaultshell [bash|sh|current]
Unzip defaultshell.zip, copy defaultshell to /system/bin, chmod 744 /system/bin/defaultshell
Click to expand...
Click to collapse
More extras (bash scripts) to come! Please post you own as well!!
PS: I was confused on where I should post this (General vs. Development), figured it isn't "technically" ROM related, so I posted in General. Please move if necessary. Thanks.
mntsystem extra added!
Awesome
Oh man, I have been missing BASH so much, thank you! Now I will finally have a fully-functioning terminal on my phone. I can't wait to tab-complete (seriously).
One question about installation, though. I'm supposed to "install zip from sdcard" in CWM, correct? Will this replace anything I already have, or just copy over the files for BASH? Does it leave sh as the default shell?
nteleky said:
I'm supposed to "install zip from sdcard" in CWM, correct? Will this replace anything I already have, or just copy over the files for BASH? Does it leave sh as the default shell?
Click to expand...
Click to collapse
Yes, flash through Clockworkmod. And, no it will not replace any files already on your phone (unless you already have bash, or some bash configuration files on your phone). Yes, it will leave sh as the default shell.
I can make a bash script to "replace" sh with bash, and post in the Extras if you want. When I say "replace", I mean backup /system/bin/sh, then symlink bash to /system/bin/sh. Therefore any time you try to execute a script through sh, it actually is executed by bash.
Although, for your information bash is/should-be fully backwards compatible with any sh script. I say should be, because:
Bash (Unix shell) - Wikipedia said:
The vast majority of Bourne shell scripts can be executed by Bash without modification, with the exception of Bourne shell scripts stumbling into fringe syntax behavior interpreted differently in Bash or attempting to run a system command matching a newer Bash builtin, etc.
Click to expand...
Click to collapse
Very rare chance though.
I personally keep sh as the default though, android system level scripts are designed for sh (its works), I just use bash for any script that I decide run (through a shell, or adb). So, I start connectbot with a profile that runs "/system/bin/bash" automatically at start.
New extra!
defaultshell Replace sh with bash, or revert. Usage:
# defaultshell [bash|sh|current]
Unzip defaultshell.zip, copy defaultshell to /system/bin, chmod 744 /system/bin/defaultshell
Click to expand...
Click to collapse
Hey
I'm a noob and I'm curious if this could run on my galaxy s 2 running stock?
The bash binary (with supporting files) should work on any rooted android device, however the flashable zip file I posted WILL ONLY WORK on the sidekick 4g.
If you want to install bash, you can download the flashable zip, extract it and copy the the files to their correct location (Quick, easy solution), or you can modify the update-script to work with your phone. Be sure the mounts are the same! Then alter the device check. (More difficult at first, but results in easily reuseable and distributable, flashable zip)
Sent from my SGH-T839 using XDA App
hey after I go to the emulator and type bash.. what should it read?
Sent from my SGH-T839 using XDA App
Should be a green prompt that reads:
/ #
If you cd to, for example, to /sdcard, then the prompt will read:
/sdcard #
If you enter su, then the prompt will become red and use a $ instead of #.
If your prompt says sh-4.1 # then you invoked bash as sh, ie you symlinked (or renamed) bash to sh (usually /system/bin/sh).
Sent from my SGH-T839 using XDA App
well when i enter bash this comes up... 0localhost:// $
and the last two are green ..
What terminal emulator are you using?
Sent from my SGH-T839 using XDA App
The free one.. lol. Idle I just typed emulator and that's the first one in the list ..
Sent from my SGH-T839 using XDA App
I'm not sure why its doing that. Although, all it means is that bash is being accessed from localhost, aka from the phone itself (not an outside source). It doesn't mean anything is wrong.
If it bothers you, you can use connectbot (free on the market, also includes an ssh client) instead. Just create a profile and make sure its local. Then it will work as expected.
Sent from my SGH-T839 using XDA App
Ok. Thanks .. ill let u know if it works
Sent from my SGH-T839 using XDA App
Well it work. Lol.. thank you
Sent from my SGH-T839 using XDA App
bc54 said:
The bash binary (with supporting files) should work on any rooted android device, however the flashable zip file I posted WILL ONLY WORK on the sidekick 4g.
If you want to install bash, you can download the flashable zip, extract it and copy the the files to their correct location (Quick, easy solution), or you can modify the update-script to work with your phone. Be sure the mounts are the same! Then alter the device check. (More difficult at first, but results in easily reuseable and distributable, flashable zip)
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
I tried doing this for my Droid 3, by changing updater-script file to the values I get from my terminal emulator, like so:
Code:
assert(getprop("ro.product.device") == "cdma_solana" || getprop("ro.build.product") == "solana_vzw");
But CWM tells me it fails because "(bad)". Do you have to somehow change the update-binary file as well?
no i didnt change the update-binary file.
however i think the source of you problem is the "/dev/" names the sidekick uses for its partitions.
for example the sidekick "/dev/" name for the partition mounted to "/system" is "/dev/block/stl9"
the droid 3 most likely uses a different "/dev" naming scheme.
find out the "/dev/" name for "/system" on the droid 3.
in the update-script file, replace "/dev/blocl/stl9" with the corresponding name for the droid 3.
find out the "/dev/" name for the "/data" partition on the droid 3.
in the update-script file, replace "/dev/blocl/stl10" with the corresponding name for the droid 3.
then rezip it, and flash. if that fails, then you could just manually copy the files to their respective location using adb, a terminal emulator app, or even a file manager.
The official CWM has problems in mounting SD-EXT, thus, Jaggyrom and other custom roms (except stock) won't work properly and your phone will reboot everytime you install apps. You'll also get a lot of app crashes because Dalvik cache can't move properly. Now here's how to flash back to Yannou90's recovery using only Android Terminal Emulator.
__________
THINGS YOU NEED:
1. Your HTC Explorer must be rooted
2. Flash_image and Recovery (You can download it here on this thread)
3. Root File Explorers (Like Root Explorer and ES File Manager, at play store)
STEPS:
1. Download the zip file, read the readme inside the zip, and extract flash_image and recovery.img to the root of your SD Card
2. Download Root Explorer from play store, you can use ES file explorer if you want a root file explorer for free
3. Using your root explorer, copy flash_image to /system/bin/ but before you do that, make sure you mount /system/bin/ as R/W.
4. After copying flash_image, set flash_image permissions to rwxrwxrwx
5.Download Android Terminal Emulator on Play store
6. Run Terminal Emulator and open up preferences.
7. at the initial command, put this:
export PATH=/system/bin:$path
7. Go back to Terminal and Type su
8. Superuser should prompt. Accept it.
9. If you saw # it means you are running it as root, which is that we really needed. If you saw $ , it's not running as root and do type su again.
10. now type this:
flash_image recovery /sdcard/recovery.img
11. Wait for it and if it's done, boot your phone to recovery.
12. CONGRATULATIONS AND YOU ARE BACK TO YANNOU90's RECOVERY
DOWNLOAD LINK:
Flash_Image and Recovery.zip
mrchezco1995 said:
......
2. Flash_image and Recovery (You can download it here on this thread)
......
Click to expand...
Click to collapse
Sorry, on trying to download the following message shows up.
"The page you have requested does not exist. Please check your spelling and try again."
Can you please re-upload the Flash_image and Recovery.zip ?
Download link 404..
Sent from my HTC desire_HD using xda app-developers app
beegeevee said:
Sorry, on trying to download the following message shows up.
"The page you have requested does not exist. Please check your spelling and try again."
Can you please re-upload the Flash_image and Recovery.zip ?
Click to expand...
Click to collapse
Deivi_Z said:
Download link 404..
Sent from my HTC desire_HD using xda app-developers app
Click to expand...
Click to collapse
Download link fixed. Uploaded it to mediafire instead. Thanks for reminding guys.
permission denied
followed all the steps....still got the "Permission Denied" message
followed all the steps....still got the "Permission Denied" message
Click to expand...
Click to collapse
Check superuser and make sure Terminal is allowed. And type su in all lowercase, not uppercase like SU. That wont work
Sent from my HTC Explorer using XDA
mrchezco1995 said:
The official CWM has problems in mounting SD-EXT, thus, Jaggyrom and other custom roms (except stock) won't work properly and your phone will reboot everytime you install apps. You'll also get a lot of app crashes because Dalvik cache can't move properly. Now here's how to flash back to Yannou90's recovery using only Android Terminal Emulator.
__________
THINGS YOU NEED:
1. Your HTC Explorer must be rooted
2. Flash_image and Recovery (You can download it here on this thread)
3. Root File Explorers (Like Root Explorer and ES File Manager, at play store)
STEPS:
1. Download the zip file, read the readme inside the zip, and extract flash_image and recovery.img to the root of your SD Card
2. Download Root Explorer from play store, you can use ES file explorer if you want a root file explorer for free
3. Using your root explorer, copy flash_image to /system/bin/ but before you do that, make sure you mount /system/bin/ as R/W.
4. After copying flash_image, download Android Terminal Emulator on Play store
5. Run Terminal Emulator and open up preferences.
6. at the initial command, put this:
export PATH=/system/bin:$path
7. Go back to Terminal and Type su
8. Superuser should prompt. Accept it.
9. If you saw # it means you are running it as root, which is that we really needed. If you saw $ , it's not running as root and do type su again.
10. now type this:
flash_image recovery /sdcard/recovery.img
...
After this step what I get is as follows
usage: flash_image partition file.img
sh-3.2#
Click to expand...
Click to collapse
Superuser worked fine on terminal. But also got permission denied on last command in terminal.. should I push it via ADB?
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
[BTW, if you're wondering, the first command identifies as root, the second remounts /system as RW, the last copies the file]
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
SifJar said:
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
Click to expand...
Click to collapse
Thank You. U completed this thread. Decided to use fastboot (faster) instead of terminal emulator way.
SifJar said:
You can simply flash the recovery using fastboot. Download this ZIP: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100 (courtesy of jaggyjags), start your phone in fastboot mode (ROM Manager might be able to reboot your phone into this mode, otherwise just turn it off, pull out the battery and replace it, then turn on while holding volume down and choose "FASTBOOT" from the menu that appears), then run "recovery.bat" from inside the ZIP. It's simpler than having to mess with adding files to /system/bin.
FYI, you need to set permissions on flash_image to allow it to be executed. I think typing this in the terminal emulator should work:
Code:
chmod 777 /system/bin/flash_image
(otherwise use your file manager to change the permissions to give read, write and execute permissions to all users i.e. tick all the boxes). This is the missing step from your guide to make it work from terminal emulator.
Also, you don't need multiple apps, you can just use terminal emulator for it all by using the "cp" command e.g. if flash_image is on the root of your SD card, use the following commands:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
then use the chmod command above and then the original command from the first post.
So the full process for terminal emulator ONLY, would be this:
Code:
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cp /sdcard/flash_image /system/bin/flash_image
chmod 777 /system/bin/flash_image
flash_image recovery /sdcard/recovery.img
{rm /sdcard/flash_image
rm /sdcard/recovery.img}
The commands in the {} are optional and just delete the two files from your SD card. The 2nd and 3rd commands can be excluded if you copy flash_image with a root capable file manager, as can the 4th if you change permissions with the file manager.
(This post ended up being much longer than I originally intended. I was just going to post the first paragraph, but figured I may as well post how to make it work the way the OP described as well - or at least what I think should make it work, I haven't actually tested the full process [I have tested the exact same process with other binaries {viewmem, tcpdump} and it works perfectly. Provided the usage of flash_image as in the OP is correct and works, this method will work])
EDIT: You also shouldn't have to change the initial command, /system/bin is already specified in $PATH. If it wasn't, pretty much nothing on the phone will work.
Click to expand...
Click to collapse
Mine worked for me on terminal without any problems, but thanks for filling up what I just missrf for others. Hehe
Sent from my HTC Explorer using XDA
mrchezco1995 said:
10. now type this:
flash_image recovery /sdcard/recovery.img
11. Wait for it and if it's done, boot your phone to recovery.
]
Click to expand...
Click to collapse
I did upto this point when I write and enter this string nothing happens it gives me another sh-3.2# to write in. How would I know that the Yannou90 recovery has completed??? I'm stuck
SherazHashmi said:
I did upto this point when I write and enter this string nothing happens it gives me another sh-3.2# to write in. How would I know that the Yannou90 recovery has completed??? I'm stuck
Click to expand...
Click to collapse
Why don't you try step 3 from jaggyjag's rooting tutorial....
Sent from my HTC Explorer A310e using xda app-developers app
My HTC Explorer's recovery was stuck green logo, but what thing that helped to get back my clockword recovery
is just downloading you recovery file and renamed it recovery.img
And...
I used Android SDK tool, and used the below command in command prompt and then I reboot the mobile, and I got back:
fastboot flash recovery recovery.img
Thanks for this valuable thread
SU not found !
after changing the INITIAL COMMAND
i restarted d terminal and now the initial command just gets printed and after that i typed 'su'...d output was 'su not found'..
wats d problem ???
I even tried d fastboot method...dats epic, whenever i try to install any .zip from it dis is wat i see
"Installing update...
Installation aborted."
Plz suggest nythng else other than REFLASHING it...its just that sumthng is restricting it to install :laugh:
hi! I have a question regarding recoveries... i have a recovery by yannou90 installed on my htc explorer, will this recovery work for other roms such as CM9 and CM10? It worked well with JaggyJags rom (3.2.1).. i am wondering if I need to switch to other recovery prior to installing CM roms.. thanks!
iamwin said:
hi! I have a question regarding recoveries... i have a recovery by yannou90 installed on my htc explorer, will this recovery work for other roms such as CM9 and CM10? It worked well with JaggyJags rom (3.2.1).. i am wondering if I need to switch to other recovery prior to installing CM roms.. thanks!
Click to expand...
Click to collapse
Yeah, ll work for all rom installation...
Hit :thumbup: if i helped...
R. SAINT said:
Yeah, ll work for all rom installation...
Hit :thumbup: if i helped...
Click to expand...
Click to collapse
got it man!
the steos for flashing the recovery worked for me but after 2 weeks now it responds to nothing when i try to wipe dalwik cache or perform any other funtion it displays nothing only the green title saying yonnou90 recovery.
Mayank T said:
the steos for flashing the recovery worked for me but after 2 weeks now it responds to nothing when i try to wipe dalwik cache or perform any other funtion it displays nothing only the green title saying yonnou90 recovery.
Click to expand...
Click to collapse
My initial response to such a situation would be start the phone in fastboot mode and then flash the recovery from there. Download the ZIP here: http://forum.xda-developers.com/attachment.php?attachmentid=913094&d=1329843100, extract it and double click "recovery.bat" once the phone is in fastboot mode (start phone holding volume down, select fastboot from menu instead of recovery).
This assumes you're on Windows. If you're on Mac/Linux, find the fastboot binary for your platform and run the following command in a terminal:
Code:
./fastboot flash recovery recovery.img
where recovery.img is taken from the ZIP I linked above.
Alternatively, you could install a more up-to-date recovery such as TWRP or a newer build of CWM (not sure of links for the latest versions of either, but have a look around the forum and you should find them. Also some older builds of CWM had bugs [hence this thread exists], but I think the newer builds work fine on the Explorer; not 100% sure as I still use yannou90's build)
I'm here give full guide for what I was learned from merrickville, codelover, and rocketero so all credits go to all of them either by direct guide and correction or by understanding their modified files. (is it OK codelover :good
To whom who don't know BlueStacks (as me before a week), it's emulated android system to works under windows system. for more info go to company page
A- REMOVE BLUESTACKS
Good tool from "Microsoft Fix it to install/uninstall Programs" thanx Ba7rani123
1- Run command (Win Key + R) -> "%programfiles%\BlueStacks\HD-Quit.exe" (WinX86) "%programfiles(x86)%\BlueStacks\HD-Quit.exe" (WinX64)
2- Open "task manager" by run command "taskmgr" -> "Processes" tab -> "HD-LogRotatorService.exe" -> right click -> "End Process Tree"
3- Open "programs and features" by run command "appwiz.cpl" -> uninstall "BlueStacks App Player" & "Notifications Center"
4- Delete all BS folders
"%userprofile%\AppData\Local\BlueStacksSetup"
"%programfiles%\BlueStacks" (WinX86), "%programfiles(x86)%\BlueStacks" (WinX64),
"%programdata%\BlueStacks"
"%programdata%\BlueStacksSetup"
Setup from Desktop
"%windir%\Installer" -> "View" -> "Details" -> right click on column header (i.e "Name", "Date Modified", "Type") -> "Authors" -> click over column header of "Authors" to sort files according authors -> search for "BlueStacks" and delete.
Note: "%ProgramData%\BlueStacks\Logs\Hypervisor.log" will persist to delete, we will delete it later after restart
5- Download RegScanner v1.95
Install -> open it -> Registry Scan Options (it will open automatic) -> select all keys in option Scan the following base key -> write on Find String "BlueStacks" -> wait till search finish -> select all and delete -> Resisted keys can be deleted manually by open in Regedit (F8)
I can't support this application because I have Windows 7 Manager, with perfect Registry Tools 1.1, it backup & delete all keys automatic
6- Repeat step (5) by searching for "Notification Center"
7- Reboot your devive now.
8- Now you can remove %ProgramData%\BlueStacks\Logs\Hypervisor.log
Click to expand...
Click to collapse
B- ROOTING BLUESTACKS
B-I- FIRST ROOTING METHOD (Ready made rooted /system)
Download rooted "Root.fs" and modified "initrd.img" for BlueStacks 0.7.7.813:
1- Download "BlueStacks-ThinInstaller_0.7.7.813.exe", "Root_Mod.rar" and "initrd_Mod.rar" from HERE
2- Setup BlueStacks 0.7.7.813 by file "BlueStacks-ThinInstaller_0.7.7.813.exe"
3- After setup finish installing, and BS open, close it (even before click "Got it") then run command (Win key + R) "%ProgramFiles%\BlueStacks\HD-Quit.exe" (WinX86), "%programfiles(x86)%\BlueStacks\HD-Quit.exe" (WinX64).
4- Extract "Root_Mod.rar" and "initrd.rar" into same folder "%programdata%\BlueStacks\Android" (P.S no need to make backup because it's already packed in zip file on "%programdata%\BlueStacksSetup\[xxxxxxxx].zip"
5- Open run command "%programfiles%\BlueStacks\HD-StartLauncher.exe" (WinX86), "%programfiles(x86)%\BlueStacks\HD-StartLauncher.exe" (WinX64)
Now your BlueStacks have root permission (Thanks CodeLover) and google apps (already supported).
OR
Download rocketero's rooted Root.fs & initrd.img from the 3rd post , thanks rocketero
Click to expand...
Click to collapse
B-II- SECOND ROOTING METHOD (Custom made rooted /system)
Rooting your "Root.fs" by your self, this method allow you root any versions of BlueStacks. it need to download "Portable Ubuntu Remix", [INFO: it's a portable Linux Ubuntu 10.4 LTS emulator that works under windows environment. for more information see PROJECT.
1- Download "Portable Ubuntu Remix" from HERE
2- Download "BlueStacks" from HERE
3- Run "Portable Ubuntu Remix" and change the path to "%programfiles%\" (WinX86) "%ProgramFiles(x86)%\" (WinX64)
4- Setup "BlueStacks" until it open -> close it.
5- Open run command (win key + R) "%ProgramFiles%\BlueStacks\HD-Quit.exe" (WinX86), "%programfiles(x86)%\BlueStacks\HD-Quit.exe" (WinX64).
6- Make RAR backup of your original "%programdata%\BlueStacks\Android\Data.sparsefs" in case of any errors may happen later.
7- Follow steps of F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES .
8- Follow steps of H- EDITING INITRD.IMG and place it in "%ProgramData%\BlueStacks\Android" (P.S: don't worry about original "initrd.img" because it is packed in zip file @ "%ProgramData%\BlueStacksSetup\[xxxxxxx].zip".
9- Open run command "%programfiles%\Portable_Ubuntu_V4_slim2\pubuntu.exe" (WinX86), "%ProgramFiles(x86)%\Portable_Ubuntu_V4_slim2\pubuntu.exe" (WinX64) and wait till it fully loaded (i.e top toolbar).
10- From the top toolbar select Applications -> Accessories -> Terminal.
11- Write the following commands (P.S: # means a note for you, it's not a command):
Code:
# Take a root permission
sudo su
# It will ask you for a root password: 123456
# Create a working folders
mkdir /b
mkdir /b/root
mkdir /b/system_sfs
mkdir /b/system_img
# Resize Root.fs to 500 MB
e2fsck -f -y "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs"
resize2fs -f "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" 500M
# Mount root.fs to root folder
mount -o loop "/media/cofs2/ProgramData/BlueStacks/Android/Root.fs" /b/root
# Mount system.sfs to system_sfs folder
mount -o loop /b/root/android/system.sfs /b/system_sfs
# Extract system.img to /b folder
cp /b/system_sfs/system.img /b/root/android
# Resize system.img
e2fsck -f -y /b/root/android/system.img
resize2fs -f /b/root/android/system.img 480M
# Unmount system_sfs and delete it (make sure the command not unmount)
umount /b/system_sfs
rm /b/root/android/system.sfs
rmdir /b/system_sfs
# Mount system.img into system_img
mount -o loop /b/root/android/system.img /b/system_img
# Copy MOD "Superuser" & extracted "su" binary, busybox files (which you already did in step 7)
cp "/media/cofs2/pubuntu/Superuser.apk" /b/system_img/app
cp "/media/cofs2/pubuntu/su" /b/system_img/bin
cp "/media/cofs2/pubuntu/su" /b/system_img/xbin
cp "/media/cofs2/pubuntu/busybox" /b/system_img/xbin
chmod 6755 /b/system_img/bin/su
chmod 6755 /b/system_img/xbin/su
# Un mount system_img & delete folder
umount /b/system_img
rmdir /b/system_img
# Set Permission for system.img
chown 0:2000 /b/root/android/system.img
chmod 0644 /b/root/android/system.img
# Unmount root and save changes into root.fs
umount /b/root
rmdir /b/root
rmdir /b
12- Close Terminal and shut down Portable Ubuntu from system menu at top toolbar -> Shut Down
13- Open run command "%programfiles%\BlueStacks\HD-StartLauncher.exe" (WinX86), "%Programfiles(x86)%\BlueStacks\HD-StartLauncher.exe" (WinX64)
14- After BlueStacks run, download custom launcher (like Go Launcher HD for Pad, Apex).
15- Now your BlueStacks have root permission.
16- Make RAR backup of your "Root.fs" and "initrd.img".
Click to expand...
Click to collapse
C- BLUESTACKS INSTALLING TROUBLESHOOTS
1- If you have msgbox telling you of missing img, rerun the setup
2- If you the setup just start and finish very soon
See section A- REMOVE BLUESTACKS @ the top
Click to expand...
Click to collapse
D- ROOTING TROUBLESHOOTS
You have to reset BS files:
a) If you follow B-I- FIRST ROOTING METHOD:
1- Download "Root_MOD.rar", "initrd_MOD.rar" and "Data_Org.rar" from HERE
2- Extract them on "%programdata%\BlueStacks\Android"
b) If you follow B-II SECOND ROOTING METHOD:
1- If you already have previous root and made backup of your rooted "Root.fs" & edited "initrd.img" & stock "Data.sparsefs" -> just extract all back to "%programdata%\BlueStacks\Android"
2- If you don't have backup -> either extract them from "%programdata%\BlueStacksSetup\[xxxxxx].zip" and start from scrach, or follow above (a) steps of B-I- FIRST ROOTING METHOD.
Click to expand...
Click to collapse
E- BACKUP/RESTORE BLUESTACKS by Codelover via bat executable commands see HIS POST
F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES I got it from codelover's MOD superuser4BS.apk
1- Download last version of Superuser for x86 from HERE
2- Download 7-Zip & install it from HERE (if you didn't have it)
3- Download latest version of "busybox-i686" from HERE to "C:\pubuntu" (take attention it should be small letter) and rename the downloaded file into "busybox"
4- Extract "\system\bin\su" to "C:\pubuntu" we need it to copy it to "/system/bin" & "/system/xbin"
5- Extract "\system\app\Superuser.apk" to "C:\pubuntu"
6- Close 7-zip
7- Open "Superuser.apk" via "7-zip" -> extract "assets\sutools-x86" -> rename it into "sutools-armeabi" -> drag it back in 7-zip to replace existed "sutools-armeabi".
8- Make copy of "busybox" and rename this copy to "busybox-armeabi" -> drag it again in 7-zip to replace existed "busybox-armeabi"
8- Close 7-zip and now, you have latest files MOD Superuser,apk, extracted "su" binary and busybox files
Click to expand...
Click to collapse
G- COPY FILES TO /SYSTEM via ADB modified from codelover's commands (take a look on his POST)
You should have "su" with root permission.
[GOOD TOOL: "Add_Open_Command_Window_Here_as_Administrator.reg" HERE to allow you open command from any folder]
a) To replace old "superuser.apk" with new file
1- Download "CodeLover_SU.rar" (superuserX86-3.2RC3) from HERE -> extract it into "C:\pubuntu" OR use your own MOD file from step F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES
2- Run "Add_Open_Command_Window_Here_as_Administrator.reg" from "C:\pubuntu" folder
3- Write commands
Code:
adb connect 127.0.0.1:5555
adb -s 127.0.0.1:5555 shell su -c "rm /*uperuser.apk"
adb -s 127.0.0.1:5555 uninstall com.noshufou.android.su
adb -s 127.0.0.1:5555 install *uperuser.apk
Click to expand...
Click to collapse
b)Replace old "su" binary file with new file
1- Download "CodeLover_SU.rar" (suX86-3.2RC3) from HERE -> extract it into "C:\pubuntu" OR use your own Extracted file from step F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES
2- Run "Add_Open_Command_Window_Here_as_Administrator.reg" from "C:\pubuntu" folder
3- Write commands
Code:
adb connect 127.0.0.1:5555
adb -s 127.0.0.1:5555 push su.86 /sdcard/
adb -s 127.0.0.1:5555 shell su -c "cp /sdcard/su.86 /system/xbin/"
adb -s 127.0.0.1:5555 shell su -c "chown 0.0 /system/xbin/su.86"
adb -s 127.0.0.1:5555 shell su -c "chmod 6755 /system/xbin/su.86"
adb -s 127.0.0.1:5555 shell su -c "mv /system/xbin/su.86 /system/xbin/su"
adb -s 127.0.0.1:5555 shell su -c whoami # if you got "Root"
adb -s 127.0.0.1:5555 shell su -c "cp /system/xbin/su /system/bin/su"
Click to expand...
Click to collapse
c)Replace old "busybox" file with new file
1- Download latest version of "busybox-i686" from HERE to "C:\pubuntu" and rename the downloaded files into "busybox" OR use one you already download it in step F- MOD LATEST "SUPERUSER.APK", EXTRACTED "SU" BINARY, BUSYBOX FILES
2- Run "Add_Open_Command_Window_Here_as_Administrator.reg" from "C:\pubuntu" folder
3- Write commands
Code:
adb connect 127.0.0.1:5555
adb -s 127.0.0.1:5555 push busybox /sdcard/
adb -s 127.0.0.1:5555 shell su -c "cp /sdcard/busybox /system/xbin/busybox-i686"
adb -s 127.0.0.1:5555 shell su -c "chown 0.2000 /system/xbin/busybox-i686"
adb -s 127.0.0.1:5555 shell su -c "chmod 0755 /system/xbin/busybox-i686"
adb -s 127.0.0.1:5555 shell su -c "mv /system/xbin/busybox-i686 /system/xbin/busybox"
adb -s 127.0.0.1:5555 shell busybox
You should not have error
Click to expand...
Click to collapse
Click to expand...
Click to collapse
H- EDITING INITRD.IMG to mount /system for read & write, I got it from merrickville's initrd.img
1- Download 7-zip and install it
2- Download "NotePad++" from HERE and install it.
3- Copy "initrd.img" from "%programdata%\BlueStacks\Android\initrd.img" or extract it from "%programdata%\BlueStacksSetup\runtimedata_[xxxxxxx].zip" (where xxxxxx = ur BS version) to "C:\pubuntu".
4- Open 7-zip -> Tools -> Options -> Editor -> put the path of installed "NotePad++" ["%ProgramFiles%\Notepad++\notepad++.exe"]
5- Extract "initrd.img" via 7-zip -> open extracted file "initrd" via 7-zip -> right click "initrd" -> Edit
6- Search for:
Code:
[B]try_mount [COLOR="red"]ro[/COLOR] "$device /mnt || continue[/B]
(It should be after "for device in /dev/sr* /dev/sd.....")
and replaced with
[B]"try_mount [COLOR="red"]rw[/COLOR] $device /mnt || continue[/B]
7- Close it and save the file -> accept replacing of the file -> close 7-zip
8- Open "initrd.img" via 7-zip and replace "initrd"
9- Now you have your edited initrd.img -> copy back to "%programdata%\BlueStacks\Android"
Click to expand...
Click to collapse
If it helps you, give me thanks :good:
Looks preety awesome...
Will try it soon...
Sent from my GT-S7500 using xda premium
"E=mohazia;33618109]I'm here give full guide for what I was learned from mammadkhata and merrickville so all credits go to both of them.
To whom who don't know BlueStacks (as me before a week), it's emulated android system to works under windows system. for more info go to company page
You have 2 choices,
First Method:
:
Click to expand...
Click to collapse
I have a Root.fs rooted (& Initrd.img Edited) with system.img (/system partition) resized to 500MB that is working fine with BS07.7.813.
you can download it here: https://www.dropbox.com/s/rdf35z9cupl5xnb/Root-fs_and_Initrd-img-bs077813.rar
it's MD5(sum) is: FFA77658EF35AACDDA06B379CBF52CB8
it contains Root.fs and Initrd.img, this still can follow your method # 1 to root BS 077813.
A few notes:
- system partition resized to 500MB
- su version 3.2 x86-RC3-signed was added not only to /system/xbin but also to /system/bin as well as busybox to keep a fallback when updating the su binary.
- binary /system/bin/ls was symlinked to busybox instead of toolbox to get nice color file listings in a terminal
- superuser4BS.apk (moded by @codelover) was added to /system/app"
rocketero said:
Does your first method contain a Root.fs with /system resized to let's say 300MB or more?
I have a Root.fs rooted and with system.img resized to 500MB that is working fine with BS07.7.813.
you can download it here: https://www.dropbox.com/s/rdf35z9cupl5xnb/Root-fs_and_Initrd-img-bs077813.rar
it contains Root.fs and Initrd.img, this still can follow your method # 1 to root BS 077813.
A few notes:
- system partition resized to 500MB
- su version 3.2 x86 was added not only to /system/xbin but also to /system/bin as well as busybox to keep a fallback when updating the su binary.
- binary /system/bin/ls was symlinked to busybox instead of toolbox to get nice color file listings in a terminal
- superuser-3.1.3.apk was added to /system/app
Click to expand...
Click to collapse
Your link was added, thanx
but I'd like to ask, why u'll need system 500MB ???
mohazia said:
but I'd like to ask, why u'll need system 500MB ???
Click to expand...
Click to collapse
it's not exactly that you need 500M on /system partition, as the size will just increase as you add files to /system, if you don't add any files the partition will stay the size it was originally, it works as the sparcefs file sistem does, it will show only what you have added from the total. Let's say you have grown the /system parttition to 300MB, that's what it will show when you do a 'df -h /system' command.
rocketero said:
it's not exactly that you need 500M on /system partition, as the size will just increase as you add files to /system, if you don't add any files the partition will stay the size it was originally, it works as the sparcefs file sistem does, it will show only what you have added from the total. Let's say you have grown the /system parttition to 300MB, that's what it will show when you do a 'df -h /system' command.
Click to expand...
Click to collapse
aha, thanks.
The image u just share didn't had google account, right.
I had now data.fs and sdcard.fs, which I extracted from BS 0.7.2... and already integrated into my BS 0.7.7.813, the advantages of .fs that I can resize it very easy. Do u advice me to share it?
actually, rooting and make some customization, was attractive, now joy was solved, it's boring
I can't even play where's my water? on BS, is for me only or with all?
mohazia said:
aha, thanks.
The image u just share didn't had google account, right.
I had now data.fs and sdcard.fs, which I extracted from BS 0.7.2... and already integrated into my BS 0.7.7.813, the advantages of .fs that I can resize it very easy. Do u advice me to share it?
actually, rooting and make some customization, was attractive, now joy was solved, it's boring
I can't even play where's my water? on BS, is for me only or with all?
Click to expand...
Click to collapse
I do have a sdcard.fs of 8GB working with v0.7.7.813, but even that I have not much in it the size would be huge to share it which makes it almost impossible to upload to any file-sharing site like dropox or box.net. I saw in an old post a shared sdcard 2GB in size but that's the default size when installing BS older than 0.7.3.x I believe. The Data.fs it has been always 2GB in size.
The good thing from updating BS from older versions to the new ones is that it will carry out the old Data.fs and Sdcard.fs and it will incorporate them into Data.sparsefs and SDcard.sparcefs
About the apps/games that run in BS it's just trial an error, sometimes very disappointing that it doesn't run the one's preferred apps.
It says that "Blue stack player app download in progress" and says its "already installed", error. idk what happens
tichs said:
It says that "Blue stack player app download in progress" and says its "already installed", error. idk what happens
Click to expand...
Click to collapse
You'll get more responses if you post on the official BS thread here: http://forum.xda-developers.com/showthread.php?p=33701742#post33701742
Code:
11- Open Superuser -> Settings -> Automatic Response -> Allow
Now your BlueStacks have root permission and google apps.
you mean that now i don't need anymore google play store because the Google apps are integrated in my bluestacks market?
thanks
kianty99 said:
Code:
11- Open Superuser -> Settings -> Automatic Response -> Allow
Now your BlueStacks have root permission and google apps.
you mean that now i don't need anymore google play store because the Google apps are integrated in my bluestacks market?
thanks
Click to expand...
Click to collapse
no what I actually meant is that ur system now have google permission, you can now install google play and it will works.
OK, when I did this guide, I did not differentiate between apps that set on /system/app and /data/app.
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
Code:
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
excuse me... i have search for google play apk on first post but i don't found it... where is it?
thanks
kianty99 said:
Code:
I will attach google play now to installed as com.nosh*.apk, just download it and double click to install
excuse me... i have search for google play apk on first post but i don't found it... where is it?
thanks
Click to expand...
Click to collapse
I'm review now the method from scrash
i've installed the two apk you mentioned and say me an error:
Code:
apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
kianty99 said:
i've installed the two apk you mentioned and say me an error:
Code:
apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
Click to expand...
Click to collapse
OK, I just remove BS, for re-install it, to start from scrach, I will update soon
AMD Appzone its better than bluestacks? I read that they have some unique technology that uses the gpu to accelerate everything, is that available to normal blue stacks builds?
tichs said:
AMD Appzone its better than bluestacks? I read that they have some unique technology that uses the gpu to accelerate everything, is that available to normal blue stacks builds?
Click to expand...
Click to collapse
no, bs is a no gpu accelerator. Even youtube not work
Sent from my HTC Desire HD using xda premium
kianty99 said:
i've installed the two apk you mentioned and say me an error:
Code:
apk installation failed: INSTALL_PARSE_FAILED_NO_CERTIFICATES
Click to expand...
Click to collapse
1- Now delete ur root.fs & data.s* from %programdata%\bluestacks
2- Extract data.s* from the archeive @ %programdata%\bluestackssetup on %programdata%\bluestacks
3- Follow new guide (exactly) with excluding steps 1 and 3 (just skip and contiune in same sequance)
Sent from my HTC Desire HD using xda premium
mohazia said:
no, bs is a no gpu accelerator. Even youtube not work
Sent from my HTC Desire HD using xda premium
Click to expand...
Click to collapse
so they are the same thing right just different name?