Related
Soo,
I want to start a project to make a script which includes the Market in a "bare bone" ROM.
The goal is to have cyanogen to make ROM's without Google Experience and let the user run a script to reinclude the Market.
I have an idea how:
The user has to download a file from the HTC Website: The ADP1 Systemimage.
He places it into a folder in which is a script which unyaffs the image, copys the necesarry files and makes an update.zip out of it which can be flashed over the "bare bone-rom".
I don't know if this legal or not, but Google won't attack the end-user, but the one who provides software illegal.
But HTC has a license, so there shouldn't be a problem.
The end-user does something illegal I think, but he won't get into any trouble with google.
The hardest part is to find the necesarry files.
I diffed the folders of a market and non-market ROM and filtered out some unneeded parts.
Here's the list of which files to copy.
# Apps
cp system/app/BugReport.apk gfiles/app/BugReport.apk
cp system/app/checkin.apk gfiles/app/checkin.apk
cp system/app/Gmail.apk gfiles/app/Gmail.apk
cp system/app/GmailProvider.apk gfiles/app/GmailProvider.apk
cp system/app/GoogleApps.apk gfiles/app/GoogleApps.apk
cp system/app/GoogleContactsProvider.apk gfiles/app/GoogleContactsProvider.apk
cp system/app/GooglePartnerSetup.apk gfiles/app/GooglePartnerSetup.apk
cp system/app/GoogleSettingsProvider.apk gfiles/app/GoogleSettingsProvider.apk
cp system/app/GoogleSubscribedFeedsProvider.apk gfiles/app/xx.apk
cp system/app/GoogleSubscribedFeedsProvider.apk gfiles/app/GoogleSubscribedFeedsProvider.apk
cp system/app/gtalkservice.apk gfiles/app/gtalkservice.apk
cp system/app/ImProvider.apk gfiles/app/ImProvider.apk
cp system/app/MediaUploader.apk gfiles/app/MediaUploader.apk
cp system/app/NetworkLocation.apk gfiles/app/NetworkLocation.apk
cp system/app/SetupWizard.apk gfiles/app/SetupWizard.apk
cp system/app/Street.apk gfiles/app/Street.apk
cp system/app/Talk.apk gfiles/app/Talk.apk
cp system/app/Vending.apk gfiles/app/Vending.apk
cp system/app/VoiceDialer.apk gfiles/app/VoiceDialer.apk
cp system/app/VoiceSearch.apk gfiles/app/VoiceSearch.apk
cp system/app/YouTube.apk gfiles/app/YouTube.apk
# Framework
cp system/framework/com.google.android.gtalkservice.jar gfiles/framework/com.google.android.gtalkservice.jar
cp system/framework/com.google.android.maps.jar gfiles/framework/com.google.android.maps.jar
# Permissions
cp system/etc/permissions/com.google.android.gtalkservice.xml gfiles/etc/permissions/com.google.android.gtalkservice.xml
cp system/etc/permissions/com.google.android.maps.xml gfiles/etc/permissions/com.google.android.maps.xml
Click to expand...
Click to collapse
PLEASE ONLY DEV-TALK!
LINUX
The script for linuxusers is ready. It's attached.
Usage:
Go to the folder
chmod +x extract
./extract
You will need your device connected with a ROM without Google Apps, but root, and you'll need the drivers (usb rules) if it doesn't work from the start.
IT WILL TELL YOU TO DOWNLOAD A FILE, YOU HAVE TO GOOGLE FOR IT!
CUSTOM RECOVERY
Usage:
Place "signed-dream_devphone_userdebug-img-150275.zip" on your sdcard.
Boot into this recovery, adb into the device and run:
sh /sbin/gapps
It will do ALL automatically!
I hope I can later include it in the menu =)
Download: http://www.4shared.com/file/135537189/25541756/recoverynewimg.html
It's based on Amom_RA's great recovery!
Improved list for the backup and restore after flash or leave untouched strategies:
GOOGLE AND HTC STUFF (?)
/system/app/BugReport.apk
/system/app/checkin.apk
/system/app/Clicker.apk
/system/app/Gmail.apk
(easy to substitute with other mail client):
pop.gmail.com port 995 with SSL
smtp.gmail.com port 465 with SSL)
/system/app/GmailProvider.apk
/system/app/GoogleApps.apk
android/cupcake/packages/providers/GoogleContactsProvider is open source
/system/app/GoogleContactsProvider.apk
/system/app/GooglePartnerSetup.apk
/system/app/GoogleSettingsProvider.apk
android/cupcake/packages/providers/GoogleSubscribedFeedsProvider is open source
/system/app/GoogleSubscribedFeedsProvider.apk
/system/app/gtalkservice.apk
android/cupcake/packages/providers/ImProvider is open source
/system/app/ImProvider.apk
/system/app/MediaUploader.apk
/system/app/NetworkLocation.apk
/system/app/SetupWizard.apk
android/cupcake/packages/apps/Stk/src/com/android/stk is open source
/system/app/Stk.apk
/system/app/Street.apk
/system/app/Talk.apk
/system/app/TmoImPlugin.apk
/system/app/Vending.apk
android/cupcake/packages/apps/VoiceDialer is open source
/system/app/VoiceDialer.apk
/system/app/VoiceSearch.apk
/system/app/YouTube.apk
/system/etc/permissions/com.google.android.gtalkservice.xml
/system/etc/permissions/com.google.android.maps.xml
/system/framework/com.google.android.gtalkservice.jar
/system/framework/com.google.android.maps.jar
/system/framework/com.htc.framework.jar
/system/framework/com.htc.resources.apk
/system/lib/libcerttool_jni.so
Other closed source(?) files:
/system/bin/akmd
(/system/etc/AudioFilter.csv)
(/system/etc/AudioPara4.csv)
(/system/etc/AudioPreProcess.csv)
/system/etc/firmware/brf6300.bin
(/system/etc/gps.conf)
/system/etc/wifi/Fw1251r1c.bin
(/system/etc/wifi/tiwlan.ini)
/system/lib/libaudioeq.so
/system/lib/libgps.so
/system/lib/libhgl.so
/system/lib/libhtc_acoustic.so
/system/lib/libhtc_ril.so
/system/lib/libjni_pinyinime.so
/system/lib/libmm-adspsvc.so
/system/lib/libOmxCore.so
/system/lib/libOmxH264Dec.so
/system/lib/libOmxMpeg4Dec.so
/system/lib/libOmxVidEnc.so
/system/lib/libopencorehw.so
/system/lib/libpvasf.so
/system/lib/libpvasfreg.so
/system/lib/libqcamera.so
/system/lib/libspeech.so
/system/lib/hw/lights.goldfish.so
/system/lib/hw/lights.msm7k.so
/system/lib/hw/sensors.trout.so
WAREZ (?)
/system/app/HTC_IME.apk
/system/lib/libt9.so
/system/app/ PDFViewer.apk
/system/lib/libpdfreader.so
/data/app/Quickoffice_HTC_1.0.1.apk
/data/app/teeter.apk
also posted here http://forum.xda-developers.com/showthread.php?t=564303&page=6
Were gonna need Stk.apk it's for the sim card without that it's impossible to make calls.
And vending.apk is for Market and without that it is impossible to download the majority of apps.
I would suggest a different strategy that is even easier. Every user has this
files already on his rom, most (all?) of them are 1.5 based. So before
updating the phone with a cooked rom you have only to backup (tar)
the not redistributable files to the sdcard. After having flashed the coocked rom
you just need to untar them to the flash memory.
Z҉A҉L҉G҉O̚̕̚ said:
Were gonna need Stk.apk it's for the sim card without that it's impossible to make calls.
And vending.apk is for Market and without that it is impossible to download the majority of apps.
Click to expand...
Click to collapse
Stk.apk is for the Sim menu. You can make calls even if you delete it from your rom
farmatito said:
I would suggest a different strategy that is even easier. Every user has this
files already on his rom, most (all?) of them are 1.5 based. So before
updating the phone with a cooked rom you have only to backup (tar)
the not redistributable files to the sdcard. After having flashed the coocked rom
you just need to untar them to the flash memory.
Click to expand...
Click to collapse
The problem with that is that the apk's have odexes and resource id's that must match the build number to actually work even Cyanogen said that.
And regarding the keep-proprietary-apps-on-device-for-custom-rom install, with all the odexing and resource id mismatches... Ugh.
Click to expand...
Click to collapse
I'm building the AOSP android-1.5_r3 now and will load it onto my device and will try to push the files to it.
Please wait for the results.
If I have success, I'll start making a script which automates the process.
maxisma said:
I'm building the AOSP android-1.5_r3 now and will load it onto my device and will try to push the files to it.
Please wait for the results.
If I have success, I'll start making a script which automates the process.
Click to expand...
Click to collapse
Good luck and good speed.
Z҉A҉L҉G҉O̚̕̚ said:
The problem with that is that the apk's have odexes and resource id's that must match the build number to actually work even Cyanogen said that.
Click to expand...
Click to collapse
If i recall correctly JF made a tool to convert odex files to dex files which could then be repacked in the apk. Don't know if this could be run on the phone tough.
SUCCESS! I found the needed files, got market working on AOSP!
It's the list above (first post).
I'm writing a script now ;-)
Edit:
Script for Linux users is done, testing it now and looking for bugs, will then make a windows-one.
Ok, script is in the first post.
Couldn't this script run from within a recovery image with little if no changes?
i.e. consider this install procedure for a new ROM
1) push update.zip for new ROM to SD card
2) push signed-dream_devphone_userdebug-img-150275.zip to SD (I suspect most people would just have it milling about their SD card in the end!)
3) wipe
4) apply update.zip
5) run (obviously slightly modded) script in recovery before rebooting and running ROM for first time
There'd need to be some kind of unzip capacity within the recovery image, otherwise, there doesn't seem to be anything you're doing in your script that couldn't be done on the handset itself.
Loccy said:
Couldn't this script run from within a recovery image with little if no changes?
i.e. consider this install procedure for a new ROM
1) push update.zip for new ROM to SD card
2) push signed-dream_devphone_userdebug-img-150275.zip to SD (I suspect most people would just have it milling about their SD card in the end!)
3) wipe
4) apply update.zip
5) run (obviously slightly modded) script in recovery before rebooting and running ROM for first time
There'd need to be some kind of unzip capacity within the recovery image, otherwise, there doesn't seem to be anything you're doing in your script that couldn't be done on the handset itself.
Click to expand...
Click to collapse
Yeah, you're right!
But the unzip process would last much longer on this little, little handset.
But ok i'll make a script
EDIT:
Have written a script, untested.
# Mounting
mount sdcard
mount system
# Chmod the files
chmod +x sbin/unyaffs
# Unzip Image
mkdir /sdcard/system
mv /sdcard/signed-dream_devphone_userdebug-img-150275.zip /sdcard/system/signed-dream_devphone_userdebug-img-150275.zip
unzip /sdcard/system/signed-dream_devphone_userdebug-img-150275.zip
# Remove not needed files, move & unyaffs the system
cd /sdcard/system
rm boot.img
rm recovery.img
rm userdata.img
rm android-info.txt
./sbin/unyaffs /sdcard/system/system.img
rm system.img
# Copy the needed files & create folders
cd /sdcard
mkdir gfiles
mkdir gfiles/app
mkdir gfiles/etc
mkdir gfiles/etc/permissions
mkdir gfiles/framework
# Apps
cp system/app/BugReport.apk gfiles/app/BugReport.apk
cp system/app/checkin.apk gfiles/app/checkin.apk
cp system/app/Gmail.apk gfiles/app/Gmail.apk
cp system/app/GmailProvider.apk gfiles/app/GmailProvider.apk
cp system/app/GoogleApps.apk gfiles/app/GoogleApps.apk
cp system/app/GoogleContactsProvider.apk gfiles/app/GoogleContactsProvider.apk
cp system/app/GooglePartnerSetup.apk gfiles/app/GooglePartnerSetup.apk
cp system/app/GoogleSettingsProvider.apk gfiles/app/GoogleSettingsProvider.apk
cp system/app/GoogleSubscribedFeedsProvider.apk gfiles/app/GoogleSubscribedFeedsProvider.apk
cp system/app/gtalkservice.apk gfiles/app/gtalkservice.apk
cp system/app/ImProvider.apk gfiles/app/ImProvider.apk
cp system/app/MediaUploader.apk gfiles/app/MediaUploader.apk
cp system/app/NetworkLocation.apk gfiles/app/NetworkLocation.apk
cp system/app/SetupWizard.apk gfiles/app/SetupWizard.apk
cp system/app/Street.apk gfiles/app/Street.apk
cp system/app/Talk.apk gfiles/app/Talk.apk
cp system/app/Vending.apk gfiles/app/Vending.apk
cp system/app/VoiceDialer.apk gfiles/app/VoiceDialer.apk
cp system/app/VoiceSearch.apk gfiles/app/VoiceSearch.apk
cp system/app/YouTube.apk gfiles/app/YouTube.apk
# Framework
cp system/framework/com.google.android.gtalkservice.jar gfiles/framework/com.google.android.gtalkservice.jar
cp system/framework/com.google.android.maps.jar gfiles/framework/com.google.android.maps.jar
# Permissions
cp system/etc/permissions/com.google.android.gtalkservice.xml gfiles/etc/permissions/com.google.android.gtalkservice.xml
cp system/etc/permissions/com.google.android.maps.xml gfiles/etc/permissions/com.google.android.maps.xml
# Put back the ADPimg
mv /sdcard/system/signed-dream_devphone_userdebug-img-150275.zip /sdcard/signed-dream_devphone_userdebug-img-150275.zip
#Push the files to the device & reboot it
cp -r /sdcard/system/* /system/
echo "Please reboot!"
Click to expand...
Click to collapse
Code:
cp system/app/GoogleSubscribedFeedsProvider.apk gfiles/app/xx.apk
cp system/app/GoogleSubscribedFeedsProvider.apk gfiles/app/GoogleSubscribedFeedsProvider.apk
Think there is typo error in the first line.
Could be a good thing to set explicitely the permissions and ownership of the files.
I think the last line should be
Code:
cp -r /gfiles/* /system/
rt ?
Yap, there is 1 line too much @farmatito, thanks, will fix that!
@sureshg:
I rewrite the script for the recovery.. thanks!
Another possible way to do this is to make a script that makes an update.zip file from HTC's yaffs file.
It would only consists of the apk's and libraries we need to modify (market, IM, Maps, whatever) which would make flashing it faster on the device. And it would also be flashable with Cyanogen's bootloader after we flash an AOSP build since we can flash any .zip file with it.
However, I would like to be able to back up the new market and all associated libraries before trying it in case I wanna switch back
@ maxisma: Thanks for taking this in a positive direction. I was thinking along the same lines, and just posted the below to another thread before I saw this thread:
It looks to me as though Google is bluffing. Here is copyright law that, IMHO, gives every user the right to make and use a backup: COPYRIGHT LAW Just because Google say something, doesn't mean it is true.
I believe the solution to this whole mess is very simple. Here is the roadmap:
1) Cyanogen makes a list of all the closed source apps that need to be left out of the ROM.
2) Some kind person(s) write an app that the user can run to backup the list of files, signs and zips it so that it can be flashed later. Let's call that app "GoogleBack," and make it freely available here (and on the Market?).
3) Cyanogen produces each new ROM without the proprietary files that are on the backup list.
4) User runs "GoogleBack" one time and resulting googleback.zip is stored on /sdcard (root directory).
5) User installs new CM update.zip from Recovery as usual.
6) User also flashes googleback.zip while still in Recovery.
7) User reboots as usual, and now has a new ROM, complete with Google's precious proprietary apps.
8) Everybody goes home happy.
Alternatively, Cyanogen could add a step to the reboot process (home+back) that runs a script to copy the backup files from the backup file (and maybe also run fix_permissions if necessary). This would make that first reboot a longer process, but it would get the job done.
We need to get busy on a solution. This whole issue is just a speed-bump on the Android highway.
I think you are absolutely on the right track. Keep up the good work. Thanks also to everyone else who is making this happen.
use of deviceinstalled official rom
Hi,
why not use the already installed software on the user device. The update.zip of the custom rom could rely on the vanilla stock firmware and do all the needed patching and homebrew additions on base of the stock rom during first boot. So enduser has to flash an official rom first, unit is in an well known state and the dev update.zip just does the conversion to the custom rom during first boot.
I think the end user may not be allowed to run these modification software but he won't be punished. Don't know if it is legal to redistribute a rom which does the patching but that would be the same problem of redistributing software which does a merge of two roms on the enduser side.
Greetings Lopiuh
stellarman said:
@ maxisma: Thanks for taking this in a positive direction. I was thinking along the same lines, and just posted the below to another thread before I saw this thread:
It looks to me as though Google is bluffing. Here is copyright law that, IMHO, gives every user the right to make and use a backup: COPYRIGHT LAW Just because Google say something, doesn't mean it is true.
I believe the solution to this whole mess is very simple. Here is the roadmap:
1) Cyanogen makes a list of all the closed source apps that need to be left out of the ROM.
2) Some kind person(s) write an app that the user can run to backup the list of files, signs and zips it so that it can be flashed later. Let's call that app "GoogleBack," and make it freely available here (and on the Market?).
3) Cyanogen produces each new ROM without the proprietary files that are on the backup list.
4) User runs "GoogleBack" one time and resulting googleback.zip is stored on /sdcard (root directory).
5) User installs new CM update.zip from Recovery as usual.
6) User also flashes googleback.zip while still in Recovery.
7) User reboots as usual, and now has a new ROM, complete with Google's precious proprietary apps.
8) Everybody goes home happy.
Alternatively, Cyanogen could add a step to the reboot process (home+back) that runs a script to copy the backup files from the backup file (and maybe also run fix_permissions if necessary). This would make that first reboot a longer process, but it would get the job done.
We need to get busy on a solution. This whole issue is just a speed-bump on the Android highway.
I think you are absolutely on the right track. Keep up the good work. Thanks also to everyone else who is making this happen.
Click to expand...
Click to collapse
This is almost exactly what I was talking about (except I was thinking that the "GoogleBack" zip should be made on a computer since it would be faster to make) and that we could use HTC's official provided yaffs image (because they are licensed to distribute it) instead of the ones from an existing phone.
How to patch the market in your I5500 Galaxy5
First step is the rooting of the phone
Use this UniversalAndroot_1.6.1.apk
Just put the file in your sdcard , use Oiexplorer or other file explorer for android and just click to .apk file.
Open the application named Universal Androot and
Verifiy if the object in combo is SuperUser for android 2.0 – 2.2
And click Root J
The apps say Woow , your device is rooted !!
If it’s the case :
Download adb.zip and extract to c:\adb
(if you want to use adb.exe to all cmd add c:\adb to the path. For more information contact me)
Downlad aline_vending_galaxy5.apk and put it to c:\adb\
Thks to alineFR of portalandroid.org for the file
Unmount the sdcard of your pc
Open a cmd dos box
Type cd c:\adb (or the folders where is the adb file)
Type adb push aline_vending_galaxy5.apk /sdcard/aline_vending_galaxy5.apk
Type adb shell
On adb
Type
su
cat /system/app/Vending.apk > /sdcard/Vending.apk.orig
cat /data/app/com.android.vending.apk > /sdcard/com.android.vending.apk.orig
Create a backup of old market
Warning the next operation is open the system file for write don’t erase any file !
Type :
mount -o rw,remount /dev/stl12 /system
cat sdcard/Aline-Vending-Galaxy5.apk > /system/app/Vending.apk
cat sdcard/Aline-Vending-Galaxy5.apk > /data/app/com.android.vending.apk
rm -r /data/data/com.android.vending
mount -o ro,remount /dev/stl12 /system
May be to reboot the phone
what effects does this actually have?
Hi,
this give acces to all apps off the market
ex : skype,busybox install , google goggles .... and many other apps and root apps (tethering,Task killer ....)
ahh sweet, was wondering why some games werent showing up
Thanks, I've tried various options. One app almost bricked my phone
Anyway, I tried yours but didn't work on my phone (I5503) - model no. in my country. The market app disappeared but was able to restore thanks to your tip
anyone succesfull?
Hi all, im making a NEW thread for how to make custom ROM, change build.prop, how to theme (coming later)! i will make a colection of how to´s to this thread for now all of the how to´s are made by me but in future i will take how to´s from others too (with their permission ofc )
so subscribe to this thread!!
i hope that there will be many custom ROMs after this
now you all think why did i do this if theres another tutorial for making custom ROM? answer: this is good alternative and this is not just one HOWTO!
HOWTO´S
-custom ROM
-edit build.prop
-5 lockscreen mod and extended power menu
-deodexing
-install android sdk and use ADB
-port themes (coming later)
-make own bootanimation (coming later)
** you can also post your ideas for new how to´s!!!
have a nice day
p.s dont blame me if something happens to your device while doing these how to´s
p.p.s if you want some special how to you can always suggest it in this thread
[HOWTO] make a custom ROM
How to make custom rom:
you will need: ADB, root explorer (maybe) and the files that are going to be in your rom!
the guide is based on The Dark Lestat's guide, i made it more easier and specific
code to delete unwanted apps: (if ADB)
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
rm /system/app/nameofapk.apk
code to add apps and stuff: (if ADB)
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameofapk.apk /system/app/
1. flash the ROM that will be your ROMs base. example: my ROMs base is JPM so i flashed clean JPM
2. make a list of the features that are going to be in your ROM
3. then start adding those features. example: i added live wallpaper support so i did this --> http://forum.xda-developers.com/showthread.php?t=793823 i also added JIT so i ran the automatic batch file from the thread --> http://forum.xda-developers.com/showthread.php?t=1026870 . then you just add those features.
4. put your sd card on to your phone (if it isnt there already )
5. when your done adding different features you go to ADB and type this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
dd if=/dev/block/stl6 of=/sdcard/factoryfs.rfs
then you wait about 2 minutes and there will be some text and then you type this
Code:
exit
exit
and in your sd-card will be freshly created factoryfs.rfs, import your freshly created factoryfs.rfs to your desktop. now you choose your kernel.
5. kernel, download the kernel you want to your desktop.
6. download total commander to your pc
7. open total commander, open the base ROM.tar. example: my base ROM was JPM so i opened the JPM.tar and replaced the kernel and factoryfs.rfs with my factoryfs.rfs and my kernel (fugumod 2.2) using total commander.
delete everything else in the .tar but, Cache.rfs, factoryfs.rfs, zlmage and data.rfs and the logo!
then you test if you can flash your ROM... if it boots, you did it. if it doesnt, try again.
[HOWTO] edit BUILD.prop
HOW TO change firmware version, phone model, build version in "about phone"
1. open root explorer
2. go to /system, find build.prop, change to read/write mode. open the build.prop in text editor
* change build version: 4th line should say ro.build.display.id=(here you write your build version name), reboot and check build version in "about phone"
* change model number: 15th line should say ro.product.model=(here write your model number ), reboot and check model number in "about phone"
* change firmware version: 8th line should say ro.build.version.release=(here write your firmware version, like 3.0 honeycomb ), reboot and check firmware version in "about phone"
you can also change different things but ill write a guide of that later
hope you like it!
[HOWTO] port a THEME
reserved for later use
[HOWTO] get 5 lockscreen mod and extended power menu
-your ROM must be deodexed!
-you can get extended power menu and 5 lockscreen mod by downloading this --> http://www.megaupload.com/?d=PKHVA57W
-extract it to root of your sd-card
-open root explorer and copy/paste the files to /system/framework
-reboot and done
OR
use adb like this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameoffile.jar /system/framework/
-reboot and done
***NOTE rebooting might take some time so dont panic
[HOWTO] deodex ROM
you must be rooted
What you'll need:
A Windows based machine
xUltimate v2.2
Patience
Process:
-Unzip xUltimate v2.2, and launch "Main.exe"
-If everything goes well xUltimate should recognize the phone and make a connection. You now should see a list of options.
-Run option 1. After option 1 is done, run option 2.
-Now these well take a while. Run option 3.
-IMPORTANT: After you have run option 3, you MUST navigate to the xUltimate folder and find "origi_frame" folder, and delete "guava.odex" (if you even have it). It's a bad file, and interferes with deodexing process.
-Now run option 4, and wait.
-Exit xUltimate, and put the phone in USB mass storage.
-Go back into the xUltimate folder and copy "done_frame", and "done_app", and move them to the root of the sdcard.
-Open a command prompt, and do the following:
Code:
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
and voila your phone is deodexed
original guide by webst3r, i changed it so its easier to understand
[HOWTO] get ADB up and running (easy way)
ADB is an acronym for Android Debug Bridge and is a development tool for the Android Mobile Operating System
NOTE this is only for windows!
-open this link --> http://adf.ly/Xfyl wait 5 secs and click upper right corner "skip ads" it will download a program that automaticly installs android sdk (wich includes ADB)
-Open the app, leave the destination as C:\ and click ok/install
-Installing ADB/USB Drivers:
*NOTE* You may need additional (Device Specific) Drivers for your Device!
- Connect your Android Device to your PC using the provided USB Cable or just a plain ole 6-pin to 4-pin usb cable... (I prefer to use one with a ferite core)
- When the new hardware device notification pops-up on your pc point windows to the driver folder we moved to our C-drive(C:\android-sdk-windows\google-usb_driver) and install the adb driver.
** if your having issues with installing ADB drivers read this --> http://dl.dropbox.com/u/20575563/ADB_Drivers_for_dummies.pdf
-Running ADB from the Command Prompt:
-Windows XP: Select Start or Tap the Windows Key on your Keyboard, select
"Run" and type "CMD" then hit "Enter".
-Windows Vista/Win7: Select Start or Tap the Windows Key on your Keyboard, select the search box on the left and type "cmd" then hit "Enter".
Add the "ADB" directory path as a system variable in windows:
-To do this right-click on "My Computer" and select Properties. Next select the Advanced tab(Advanced Settings in Vista/7) then select Environment Variables.
-Click "New" under System Variables and add the following:
Variable =
Code:
adb
Value =
Code:
C:\android-sdk-windows\platform-tools
-Call up your Command Prompt:
Time to start adb
- Open up a Command Prompt Windows
- Type the commands below:
Code:
cd C:\android-sdk-windows\platform-tools
<-- Press Enter
Code:
adb.exe
<--Press Enter
and voila You will see alot of scripting fly through the command prompt window.
***note! you have to enable usb debugging in --> settings --> applications --> developement --> check usb debugging
tutorial is not made by me, its made by AndroidSamurai. i found it after lot of researching
[HOWTO] make your own update.zip
download and install, then watch the video
http://youtu.be/i0KzFPMA6-8
program and video made by Daneshm90
balaji.admin said:
Please include a Post for Deodexing the ROM. I've tried to deodex the DDJP2. But never succeeded.
Hope your post will help me.
Click to expand...
Click to collapse
there is a tut by rudolf..
[HOWTO] change app icon
How to change icons for app!
1.)
Things you need:
original app
your custom icon (size should be 48x48)
win rar
2.)
Unpack APK
3.)
Find file, for example: ic_launcher_settings.png (for settings.apk)
It should be in: res/drawable-mdpi or res/drawable-ldpi (dont know which icon phone uses, just replace both)
4.)
Rename you icon to, for example: ic_launcher_settings.png (for settings.apk)
5.)
Replace it
6.)
Final step is add files to old settings.apk archive and using root explorer copy it into /system/app/
DONE!
guide by peldax
jazux said:
hey, one question coming from me our device has the same resolution as htc wildfire? right? and device is ldpi or mdpi? please answer ASAP!!! i may have found very useful HOWTO that you will LOVE!!!
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
Click to expand...
Click to collapse
galaxy3 has ldpi - look there: http://developer.android.com/guide/practices/screens_support.html
jazux said:
-your ROM must be deodexed!
-you can get extended power menu and 5 lockscreen mod by downloading this --> http://www.megaupload.com/?d=PKHVA57W
-extract it to root of your sd-card
-open root explorer and copy/paste the files to /system/framework
-reboot and done
OR
use adb like this:
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
adb push nameoffile.jar /system/framework/
-reboot and done
Click to expand...
Click to collapse
is this suit for every rom？
dxdiag32 said:
is this suit for every rom？
Click to expand...
Click to collapse
what do you mean? like does this work on other fw's than JPM? im not sure because i havent tested it, but i think it should work.
but it will surely work on every JPM based ROMs
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
Hey man a really nice tutorial
Can you add my tutorial on how to make bootanimations too
It would be appreciated
P.S. : If you tell yes,i'll give you a shortened version too
Deodexed Rom? How can i do it?.
cdesai said:
Hey man a really nice tutorial
Can you add my tutorial on how to make bootanimations too
It would be appreciated
P.S. : If you tell yes,i'll give you a shortened version too
Click to expand...
Click to collapse
yes i can add it
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
AndroKite said:
Deodexed Rom? How can i do it?.
Click to expand...
Click to collapse
ill do a tutorial later tonight!
>>>>>>>>>>>>>>>>>>>>>>>>>
POX v.1.0 beta 2 released! be sure to try it out :]
<<<<<<<<<<<<<<<<<<<<<<<<<
GreeModding from finland :]
AndroKite said:
Deodexed Rom? How can i do it?.
Click to expand...
Click to collapse
for now you can use this:
Thanks,i dont remenbre that you make a tutorial ,Thx.
AndroKite said:
Thanks,i dont remenbre that you make a tutorial ,Thx.
Click to expand...
Click to collapse
you welcome
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?
My process was a manual project, this was the steps I took.
1. Download VirtualBox or MemuHyperv Tool (if you have MEmu installed)
2. Download an Ubuntu Image (I used version 15.04 but I am sure any version will do)
3. Download Bluestacks (any version) and install.
Now if you are going to use my VDI file, you need to have version 2.7.320.8504 (and you can skip to step 9), otherwise you need to follow these steps.
Step 1.
After downloading you need to open VirtualBox or MemuHyperv Tool (this is basically a clone of VirtualBox but you have to have MEmu installed on your PC. Extract the tool to [drive]:\[MEmu Location]\Microvirt\MEmuHyperv\
Step 2.
Import the Ubuntu Image
Step3.
Select the Ubuntu Device in the list and click settings. Select the Storage Tab. Select the SATA header then click the + symbol. Navigate to the Bluestacks folder. [drive]:\Program Files\Bluestacks\Android
Make a copy of Root.vdi
Then Select Root.vdi
Then click OK to save changes.
Step 4.
Run the Ubuntu Device. When you downloaded your version, take note of the user name and password. Version 15.04 is user: ubuntu password: reverse
Step 5.
Download the latest SuperSU while inside the Ubuntu Device. It has firefox as default browser. Then extract the file.
We want 4 files from this zip
In folder /x86/ make a copy of su and name the copy daemonsu
Open the drive name (8,6 GB Volume) and move su, daemonsu, and supolicy to /android/system/xbin/
In Folder /x86/ move libsupol.so to (8,6 GB Volume)/android/system/lib/
In Folder /common/ move Superuser.apk to (8,6 GB Volume)/android/system/app/
Step 6.
Open Terminal, then drag and drop su from the 8,6 GB Volume to terminal.
This will give you the complete path to the file. remove the single quote and backspace out su. Use the left Arrow to move to the front of the volume location, backspace out the single quote then type "cd "
You should now be in the xbin folder on 8,6 GB Volume
You can close all the open windows except terminal
Step 7.
In Terminal type these commands to give ownership of the the above files to root:root
sudo chmod 755 su
sudo chmod 755 daemonsu
sudo chmod 755 supolicy
cd ../lib
sudo chmod 644 libsupol.so
cd ../app
sudo chmod 644 Superuser.apk
Close Terminal
Step 8.
Open 8,6 GB Volume
Open (with a text editor) android/system/etc/init.sh
Find this code at the bottom of the file:
init|"")
do_init
;;
esac
Change it to:
init|"")
do_init
/system/xbin/daemonsu --auto-daemon &
;;
esac
Step 9.
You are done with Ubuntu.
Now you replace the Root.vdi file with the one you modified if you downloaded my VDI file, otherwise skip this step since you modified the original earlier.
Step 10.
Open Bluestacks
Load Google Play Store
Find SuperSU, it should already be shown as installed, run it from the play store
Select the begin button at the bottom
Chose what ever you like on Following ChainFire
Select Continue on the next popup
Select Normal on next Popup
You are now done and Bluestacks is Rooted.
Links:
Tools
https://www.virtualbox.org/wiki/Downloads
http://www.memuplay.com/blog/index.php/2016/08/08/memuhyperv-tool/
Ubuntu Image
https://virtualboxes.org/images/ubuntu/
SuperSU
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
VDI
https://drive.google.com/file/d/0B4EBuy-Yq05xUWstcGJHYnl1cWM/view?usp=drivesdk