Related
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?
To install from CMD - Terminal
1. Download the fxps script. http://db.tt/zjiwMQw
2. adb shell mount -o rw,remount /dev/block/stl6 /system
3. adb push fxps /system/bin/fxps
4. adb shell busybox chmod 755 /system/bin/fxps
5. adb shell reboot
To Run it
1. adb shell fxps
2 adb shell reboot
To install from Terminal Emulator
"Download the fxps script and move it in your SD Card" http://db.tt/zjiwMQw
$ su
# adb shell mount -o rw,remount /dev/block/stl6 /system (Puts the system in R/W mode)
# cp /sdcard/fxps /system/bin/fxps (Copys the script from SD Card to bin directory)
# chmod 755 /system/bin/fxps (Gives root access to the script)
# reboot
To Run it open the Terminal Emulator and enter
$ su
# fxps (It will start... When it finish reboot)
# reboot
This Script is not mine i just find it and gine it to you in simple way
Thanks the Dev of this Script i hope to see it in Power Menu some day...
or you can use the Root Explorer to paste it in the /system/bin/ directory and
then with Root Explorer edit permitions by long touching the fxps file and tick all the permitions
Thanks!
rudolf895 said:
Thanks!
Click to expand...
Click to collapse
no problem mate hope to help in my way... and cross yours
can anyone confirm it .... please
Ok trying
Will post results
EDIT:
Installed
took 1m41s
The media fire link has.txt file
You need to rename that
Or directly use this
Direct dl link:
http://db.tt/zjiwMQw
Can you add to first post?
cdesai said:
Ok trying
Will post results
EDIT:
Installed
took 1m41s
The media fire link has.txt file
You need to rename that
Or directly use this
Direct dl link:
http://db.tt/zjiwMQw
Can you add to first post?
Click to expand...
Click to collapse
thanks mate ......
It doesnt work
No change occurred
Before it no fc
After it no fc
But now I can't listen music
All players say file not supported for mp3s which I was listening before fxps
cdesai said:
It's crap
No change occurred
Before it no fc
After it no fc
But now I can't listen music
All players say file not supported fire mp3s which I was listening before fxps
Click to expand...
Click to collapse
i cant confirm that you are correct mate... i tryed a lot of my players and my MP3s work so fine.... so dont hurry to make conclusions... i toke this script from "rom manager v3.0.1.0.apk" and decompile the file and then toke the script... so if all the others we are CRAP who use the Rom manager and clockwork recovery then you are correct... (Think Before you Talk its Easy...)
nikkpap said:
i cant confirm that you are correct mate... i tryed a lot of my players and my MP3s work so fine.... so dont hurry to make conclusions... i toke this script from "rom manager v3.0.1.0.apk" and decompile the file and then toke the script... so if all the others we are CRAP who use the Rom manager and clockwork recovery then you are correct... (Think Before you Talk its Easy...)
Click to expand...
Click to collapse
ok dude
but now it has seriously started fcing
i m fed up
need to reflash
btw u tried on wich rom
on kyrillos 3.3 4.0rc 4.0 rc2 4.0 rc3 i have no problem with you in personal only i dont like hyronic style sorry again ...
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?
Deodexed files for build 15.3.A.1.14 from here
1. Copy app and framework folder to root of internal sd
2. Place adb tools somewhere on your windows PC
3. Turn on USB Debugging on and stay awake under developers options (If you didnt didn't get the developer options press build number 7 times)
4. Connect your phone to PC and make sure drivers are installed
5. Run the bat "Copy_Deodexed_and_Reboot.bat" under adb tools
6. The phone will reboot and if all worked fine, you will see "Android is Upgrading" on next boot as it creates Dalvik Cache
Enjoy !
Note: Those who are facing unexpected system reboots during deodexing process please first install remountrebootfix by [NUT]. You can download it from here.
Thanks to serajr for bat file
Great bro... :good:
I think this script will help! It worked here with no "remont fix" by [NUT] !!!
Code:
adb devices
adb shell "su -c 'stop'"
adb shell "su -c 'mount -o rw,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system'"
adb shell "su -c 'chmod 777 /system/app'"
adb shell "su -c 'chmod 777 /system/framework'"
adb shell "su -c 'cp /sdcard/app/* /system/app/'"
adb shell "su -c 'rm /system/app/*.odex'"
adb shell "su -c 'cp /sdcard/framework/* /system/framework/'"
adb shell "su -c 'rm /system/framework/*.odex'"
adb shell "su -c 'mount -o ro,remount -t ext4 /dev/block/platform/msm_sdcc.1/by-name/system /system'"
adb reboot
.
.
don't need remountfix but do need to be rooted.
i cant download dedexed files, it says "there's an error during download"
Download this LINK
I have edit some batch with your deodex folder....app and framework..
Just Extract to Computer then connect your devices with enable USB DEBUGGING.
Then Open Menu.bat, choose number 2 for deodex...
wait untill all file have push to system, then enter any key to reboot..
BTW great job:good:
Levered said:
Download this LINK
I have edit some batch with your deodex folder....app and framework..
Just Extract to Computer then connect your devices with enable USB DEBUGGING.
Then Open Menu.bat, choose number 2 for deodex...
wait untill all file have push to system, then enter any key to reboot..
BTW great job:good:
Click to expand...
Click to collapse
Does not work for me says push completed at the end but my files still have .odex changed nothing i have root access and latest busybox also developer options> USB dedugging on help
Taher.apk said:
Does not work for me says push completed at the end but my files still have .odex changed nothing i have root access and latest busybox also developer options> USB dedugging on help
Click to expand...
Click to collapse
does you enable unknown sources?
Levered said:
does you enable unknown sources?
Click to expand...
Click to collapse
Yes i do
Levered said:
does you enable unknown sources?
Click to expand...
Click to collapse
i did it via root explorer any way thank you very much for the deodex
How did You replace files using root explorer , i have problem with busybox (system halt on remount system) with system ver.15.3.A.0.26 ?
Levered said:
Download this LINK
I have edit some batch with your deodex folder....app and framework..
Just Extract to Computer then connect your devices with enable USB DEBUGGING.
Then Open Menu.bat, choose number 2 for deodex...
wait untill all file have push to system, then enter any key to reboot..
BTW great job:good:
Click to expand...
Click to collapse
I've enabled USB Debugging an Unknown Sources, the batch pushes everything and when it's time to copy to system, i'm getting error: device not found... and my L reboots...
I don't have installed remountrebootfix, because i think it's not necessary; i've mounted r/w with root explorer and my device didn't reboot... even i deleted a lot of bloatware before
still got odex files.. i'm trying to delete it manually using rootex but when i'm trying to restart it i've got bootloop :crying:
me too still odex files help please!!!!!!!
Its work!i dont have odex files..:good:
Hipom said:
Its work!i dont have odex files..:good:
Click to expand...
Click to collapse
How did you make it work? Have you used remount reboot fix?
Escrito desde mi Xperia L y weá
EDIT: Worked like a charm... Steps i did:
1. Root by the VRoot method, the installed SuperSU
2. Installed RemountRebootFix
3. Used the batch file by Levered
No odex files remaining!
Thanks all!
I just use deodex JB.zip extract zip and run the bat..odex files gone..
Sent from my C2105 using xda app-developers app
Deodexing working fine!
just download the deodexed files link mentioned in first post
then copy the app and framework folder to the deodexer tool which we had used for .17 firmware.
next execute the batch file and follow onscreen instructions!
your'e done!
Deodex build 15.3.A.1.12
Download files from here
Extract somewhere
Copy "app" and "framework" folder to root of your internal sd card
Make sure that USB Debugging is on
Run the batch under "adb tools" folder
Thanks to serajr for bach file
After i use this deodexed files my XperiaHome not working The latest XperiaHome 6.1.T.0.6 not working but version 6.1.A.0.5 working well )
[r[/QUOTE] Heh, You think giving us complicated code without instruction will deodexed the new firmware with just one touch ? huh,,i know you're A PRO (whoa tat crazy pro fuyoo giler ar sheram nih ,,) but PLEASE TEACH THE NOOBS STEP BY STEP .. Please give us a simple step for putting the code through Command prompt(it should run as admin etc) bla2,,man you take this really easy..this really dissapointed me,,