Okay, so I tried doing the One-Click Exploit and nothing happened (yes, I had the USB Debugging checked, allow for external developers, and USB Charge Only). So then I tried the manual root. My phone rebooted, but it wasn't rooted. Now when I try to do the Manual Root it says (after the ./zerg) :
[-] Cannot copy boomsh.: Permission denied
[1] + Stopped <signal> ./zerg
And when I tried doing the One-Click again, it rebooted my A2 a couple times and still didn't get it rooted. Help???
Ok first remove the tmp directory in the same place you copied zerg to.
Here are the commands:
From windows:
Launch a command line - go to start run and type cmd or command
Then from the prompt cd to the directory you installed the SDK in and do the following commands:
adb shell
cd /data/local (This will need to be the directory you copied the zerg file to the first time.)
rm ./tmp/*
rm ./tmp/*.*
rm ./tmp
Then follow this post from the root thead:
http://forum.xda-developers.com/showpost.php?p=19916762&postcount=194
Right now there is not a one click for the latest root methods.
The other thing I would do is read through the how to root thread, because there are people that have been able to root by using both the one click and the manual method at the same time to get it to root.
Link to the root thread:
http://forum.xda-developers.com/showthread.php?t=1327741&page=20
Alright, thank you...but I'm a bit rusty with my MS-DOS and I didn't get very far to begin with. So what do you mean by "cd to the directory" and how would I do that? Unfortunately I'm not very sure which directory I installed the SDK in. I think it's data/local/. Here's some of the lines:
c:\Users\User\Deskstop\Exploit\adb shell
shell(character I don't recognize)edison:/$ cd /data/local
cd /data/local
shell(" "):/data/local$ chmod 777 zerg
Sorry for being a little on the illiterate side...I'm like the shadetree mechanic of computers.
According to the xda news,superoneclick has added the zerg rush exploit to it's program.might could try it.
Sent from my MB865
Sent from my MB865
JDtech1701 said:
I'm like the shadetree mechanic of computers.
Click to expand...
Click to collapse
Hey shadetree mechanics keep cars running
Sent from my MB865 using xda premium
JDtech1701 said:
Alright, thank you...but I'm a bit rusty with my MS-DOS and I didn't get very far to begin with. So what do you mean by "cd to the directory" and how would I do that? Unfortunately I'm not very sure which directory I installed the SDK in. I think it's data/local/. Here's some of the lines:
c:\Users\User\Deskstop\Exploit\adb shell
shell(character I don't recognize)edison:/$ cd /data/local
cd /data/local
shell(" "):/data/local$ chmod 777 zerg
Sorry for being a little on the illiterate side...I'm like the shadetree mechanic of computers.
Click to expand...
Click to collapse
You will just highlight each line of commands ONE AT A TIME, then past it to your DOS terminal window then hit return, but just one line at a time.
Ok after you connect to your phone with ADB shell you should see:
see a $ for your prompt.
then copy these lines and paste them one at a time and hit return in your DOS terminal window:
su
cd /data/local
rm ./tmp/*
rm ./tmp/*.*
rm ./tmp
Then follow this:
http://forum.xda-developers.com/showpost.php?p=19916762&postcount=194
http://forum.xda-developers.com/showthread.php?t=1327741
Alright, I put in:
c:\Users\User\Deskstop\Exploit\adb push zerg /data/local
c:\Users\User\Deskstop\Exploit\adb push su /data/local
c:\Users\User\Deskstop\Exploit\adb push superuser.apk data/local
c:\Users\User\Deskstop\Exploit\adb shell
And then I put in all the commands you gave and..."rm failed"
lilhaiti said:
Hey shadetree mechanics keep cars running
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
I know, I was a shadetree auto mechanic myself for a couple years (now I'm a heavy equipment diesel technician...intern). I'm just trying to say that I'm not literate enough to be a developer or anything, but at the same time I know more than your average user.
JDtech1701 said:
Alright, I put in:
c:\Users\User\Deskstop\Exploit\adb push zerg /data/local
c:\Users\User\Deskstop\Exploit\adb push su /data/local
c:\Users\User\Deskstop\Exploit\adb push superuser.apk data/local
c:\Users\User\Deskstop\Exploit\adb shell
And then I put in all the commands you gave and..."rm failed"
Click to expand...
Click to collapse
can you paste the output for me, so I can point you to the next step, or give me the exact error that rm showed? If I can get than I can help you move forward.
It looks like you were having an issue with a previous attemp at root, and there are some temp files we will need to find and remove first before you can try to root again.
Sure!
C:\Users\User\Desktop\Exploit>adb shell
shell(character I don't recognize)edison:/$ su
su
su: not found
shell(" ")edison:/$ cd /data/local
cd /data/local
shell(" ")edison:/data/local$ rm ./tmp/*
rm ./tmp/*
shell(" ")edison:/data/local$ rm ./tmp/*.*
rm ./tmp/*.*
rm failed for ./tmp/*.* No such file or directory
shell(" ")edison:/data/local$ rm ./tmp
rm ./tmp
rm failed for ./tmp, Is a director
shell(" ")edison:/data/local$
JDtech1701 said:
Sure!
C:\Users\User\Desktop\Exploit>adb shell
shell(character I don't recognize)edison:/$ su
su
su: not found
shell(" ")edison:/$ cd /data/local
cd /data/local
shell(" ")edison:/data/local$ rm ./tmp/*
rm ./tmp/*
shell(" ")edison:/data/local$ rm ./tmp/*.*
rm ./tmp/*.*
rm failed for ./tmp/*.* No such file or directory
shell(" ")edison:/data/local$ rm ./tmp
rm ./tmp
rm failed for ./tmp, Is a director
shell(" ")edison:/data/local$
Click to expand...
Click to collapse
Ok, good lets try this to remove the tmp directory.
adb shell
cd /data/local
rm -r ./tmp/
If that does not work install the root explorer app from the adroid market
https://market.android.com/details?id=com.speedsoftware.rootexplorer&hl=en
and locate the /data/local directory and then delete the tmp directory there. This will be the easiest way to remove that stubborn old tmp directory and those files that are holding you up from getting root. Once you have that done try the oneclick again, from here:
http://forum.xda-developers.com/showthread.php?t=1327741
In my experience, deleting the sh and boomsh files is sufficient to enable zergrush to run again. I didn't have to delete the tmp directory itself.
This would've been done in the step you already ran
Code:
shell(" ")edison:/data/local$ rm ./tmp/*
jimbridgman said:
and locate the /data/local directory and then delete the tmp directory there. This will be the easiest way to remove that stubborn old tmp directory and those files that are holding you up from getting root. Once you have that done try the oneclick again, from here:
http://forum.xda-developers.com/showthread.php?t=1327741
Click to expand...
Click to collapse
OK download the moto drivers. 32x or 64x.
Then get the zip file from the root link I'm this forum it should be a batch file your run. It opens a cmd window and follow the steps.
Profit.
It was super easy phone reboots and your rooted on the stock firmware. Pm me of you need the files for some reason I have them.saved in my mass android folder.
Best of luck.
Sent from my Rooted MB865 using XDA App
jimbridgman said:
Ok, good lets try this to remove the tmp directory.
adb shell
cd /data/local
rm -r ./tmp/
If that does not work install the root explorer app from the adroid market
https://market.android.com/details?id=com.speedsoftware.rootexplorer&hl=en
and locate the /data/local directory and then delete the tmp directory there. This will be the easiest way to remove that stubborn old tmp directory and those files that are holding you up from getting root. Once you have that done try the oneclick again, from here:
http://forum.xda-developers.com/showthread.php?t=1327741
Click to expand...
Click to collapse
Uh...are you sure I should remove the tmp directory? It looks like it's got some important stuff in there. Wait...is "tmp" short for temporary?
JDtech1701 said:
Uh...are you sure I should remove the tmp directory? It looks like it's got some important stuff in there. Wait...is "tmp" short for temporary?
Click to expand...
Click to collapse
Yes, but this is not the OS temporary directory, just the one that is, I am guessing in /data/local, or where you copied those files to... I am guessing since you don't have root yet that, that is not /, because then ./tmp would be /tmp (the OS temporary directory, we don't want to remove that one)..... but I am guessing that is not the case since you don't have root.
Yeah I am pretty sure it is safe... I work with UNIX and Linux for a living, and Android happens to be a form of Linux.
Like others have posted, you might be able to try the root process again, since the files that zerg was complaining about are now gone, from the rm ./tmp/* command you ran before... I was just trying to be very thorough.
Okay, I got that Root Explorer and went into tmp and did select all and delete. Now there's .. Parent folder, .X11-unix, appicon, and commdrv left. I tried doing the adb push zerg all the way down to ./zerg as listed in the How To you linked...and it gave me the exact same result. And when I opened Root Explorer, I went straight to tmp. I tried going to the data folder but it said my phone needed to be rooted first. Okay, figuring this app out...yeah, I went to /tmp. I'm not going to be able to access /data/local without rooting it first.
both the 1-click and the manual process fails for me too. I have tried deleting all the files and directory as well and it still doesn't work. When I run either ./zerg or ./zergRush it both fails with the message "Hellion with Blue Flame". Any help would be appreciated.
bbygfy said:
both the 1-click and the manual process fails for me too. I have tried deleting all the files and directory as well and it still doesn't work. When I run either ./zerg or ./zergRush it both fails with the message "Hellion with Blue Flame". Any help would be appreciated.
Click to expand...
Click to collapse
Which system version are you running.... You can find this out by going into settings --> About phone; then give me the text under System version. It should be something like 55.11.16.MB865.ATT.en.US.
Jim
55.11.16.MB865.ATT.en.US
Thanks!
Related
I have been following the unlock instructions on these posts on how to unlock the Hero, but I am having some trouble. When to comes to making the adb shell, it just doesn't do it. It shows a dollar sign and says that the request is denied. I just don't get what I'm doing wrong. Are there extra steps for me because there are x86 files? If I have to put the android sdk into the program files x86 folder, how would I enter that into the commander? Any help would be appreciated guys, this is driving me crazy.
OK so you get to the dollar sign. What do you do then?
Kamar234 said:
I have been following the unlock instructions on these posts on how to unlock the Hero, but I am having some trouble. When to comes to making the adb shell, it just doesn't do it. It shows a dollar sign and says that the request is denied. I just don't get what I'm doing wrong. Are there extra steps for me because there are x86 files? If I have to put the android sdk into the program files x86 folder, how would I enter that into the commander? Any help would be appreciated guys, this is driving me crazy.
Click to expand...
Click to collapse
Just extract the sdk so its a folder. Then go to Start->Run-> type cmd.exe in the box that opens. Now navigate to where you extracted the sdk folder. If you extracted it straight onto the c:\ drive at top level, you'd do something like this:
Code:
cd c:\android-sdk\tools
That will get you into the directory that has adb.exe
Now follow the instructions in the "how to root" thread.
I can get down to the point where I execute the adp push and all the lines come up saying that the adp is restarted and there is obviously a command that is executed.
adb shell
chmod 0755 /data/local/asroot2
this part is when it says access is denied. I follow everything perfectly, but I just don't get it.
Oh, easy.
Type "su" and hit enter.
The dollar sign prompt indicates you are running as a regular user. Run su and it will give you a # prompt indicating you are running as root.
Then do the chmod.
It specifically says after entering this line
/data/local/asroot2 /system/bin/sh
system cannot find the path specified. Any ideas?
so when the dollar sign comes up, just type su and hit enter, that's it?
Kamar234 said:
It specifically says after entering this line
/data/local/asroot2 /system/bin/sh
system cannot find the path specified. Any ideas?
Click to expand...
Click to collapse
Are you sure the asroot2 file has been copied over to your phone? What I did is extract asroot2 into the tools folder, so that I could just say adb push asroot2 /data/local/
My suggestion is to make sure the file is in /data/local/
Also, here is the full thing taken from the other thread:
Code:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
adb shell
chmod 0755 /data/local/asroot2
/data/local/asroot2 /system/bin/sh
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
cd /system/bin
cat sh > su
chmod 4755 su
Yup, I put it in the tool folder within the android sdk. I am using the 1.5 sdk as well.
I just really can't understand what I'm doing wrong
Do:
ls -al /data/local
Do you see asroot there?
it says not found. I entered it by the dollar sign
Kamar234 said:
it says not found. I entered it by the dollar sign
Click to expand...
Click to collapse
That means the file isn't copied over. You need to do the adb push line again, and make sure it copies the file over.
how do I do that? Is there a something that it does or says to let you know it has copied over?
Kamar234 said:
how do I do that? Is there a something that it does or says to let you know it has copied over?
Click to expand...
Click to collapse
The first line here:
Code:
adb push /directory_you_placed_asroot2/asroot2 /data/local/
That puts the asroot2 file into your phone's /data/local/ directory.
This line gets you into your phone's shell:
Code:
adb shell
AT THIS POINT, you should see a $ dollar sign. This means you are in your phone.
This line will let you check that asroot2 has been copied over:
Code:
ls -al /data/local
This line gives the file you just copied over, permission to execute/run:
Code:
chmod 0755 /data/local/asroot2
This line runs the file you copied over:
Code:
/data/local/asroot2 /system/bin/sh
This line mounts your file system on your phone as writable:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
I am also running windows 7 through vmware fusion, do you think that would make a difference.
Kamar234 said:
I am also running windows 7 through vmware fusion, do you think that would make a difference.
Click to expand...
Click to collapse
I don't know, I don't think it should. Can you type everything in and then paste us your results?
Type pwd and hit enter.
What do you see?
Thank you so much for all your help everyone. I think I may have finally gotten it. If I am installing an app that needs root access, will it install at all if the phone isn't rooted?
So as the title says, I pushed an apk to "system/tools" on my phone on accident instead of apps. How can I remove this push. I have tried rm -r /system/tools/__.apk but its telling me it doesn't exist. Is it possible it did nothing? I got a file transfer after doing so. I've also tried finding that folder (tools) in astro, but its not a folder and gives me the mesage file type not found. Thanks
barnacles10 said:
So as the title says, I pushed an apk to "system/tools" on my phone on accident instead of apps. How can I remove this push. I have tried rm -r /system/tools/__.apk but its telling me it doesn't exist. Is it possible it did nothing? I got a file transfer after doing so. I've also tried finding that folder (tools) in astro, but its not a folder and gives me the mesage file type not found. Thanks
Click to expand...
Click to collapse
Get andExplorer and browse to the /system/app folder to see if it is there, of on a computer use Android Commander.
You would also have to remount
Code:
adb remount
adb shell
rm -r /system/tools/XYZ.apk
Kcarpenter said:
You would also have to remount
Code:
adb remount
adb shell
rm -r /system/tools/XYZ.apk
Click to expand...
Click to collapse
rm -r is a recursive deletion. For a single file leave off the -r. Why?
Because if you accidentally forget to put in the file name it will delete everything in the directory and below it.
Kcarpenter said:
You would also have to remount
Code:
adb remount
adb shell
rm -r /system/tools/XYZ.apk
Click to expand...
Click to collapse
Correct, but when I try this it says its not a valid directory. And when I navigate to that folder with astro is not an openable folder. Which led me to believe it didn't transfer, or just wouldn't allow it. However, cmd showed the transfer data and time after pushing. Thats why I was confused
smw is correct, -r is for directories only, so the proper command would be:
Code:
adb remount
adb shell
rm /system/tools/XYZ.apk
gu1dry said:
smw is correct, -r is for directories only, so the proper command would be:
Code:
adb remount
adb shell
rm /system/tools/XYZ.apk
Click to expand...
Click to collapse
I've tried this too I get
"rm failed for system/tools/app.apk, Not a Directory"
try this:
adb remount
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
then cd to the right directory and type
rm xxxx.apk
since their is no tools directory it clearly didn't autmoatically create one. Instead it just made a file called /system/tools which is your apk file. to remove it just "adb shell rm /system/tools"
alexthearmo said:
try this:
adb remount
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
then cd to the right directory and type
rm xxxx.apk
Click to expand...
Click to collapse
after the command "
alexthearmo said:
try this:
adb remount
adb shell
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
" I try a cd /system/tools/" and get a can't cd error. hmm
Click to expand...
Click to collapse
darchstar said:
since their is no tools directory it clearly didn't autmoatically create one. Instead it just made a file called /system/tools which is your apk file. to remove it just "adb shell rm /system/tools"
Click to expand...
Click to collapse
Ah ha. So there is no such thing as /system/tools on the phone? This is what I was curious about. So deleting the file will /system/tools altogether should be ok?
cd into /system & then ls to make sure there is tools folder.
sorry for the recursive thing, wasn't thinking about what I was typing.
-r is not needed.
Thanks for the great job done by developers. However, I noticed mediascape was removed after root. Personally I think mediascape is nice but failed to install it from the app folder on sdcard. Searched the whole thread but didn't find a method.
I tried manually copy the mediascape.apk to /data/app, reboot, then mediascape is restored in the application drawer and can be run functionally.
Here is the details.
Connect the X10 to PC using USB debug mode.
Get the adb.exe ready (you can run it from the root step4 folder directly)
0. Copy mediascape.apk to the step4 folder.
1. Start command prompt as administrater.
2. Change to the step4 folder.
3. Run "adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" without quotes.
4. Run "adb shell chmod 777 /data/app" without quotes.
5. Run "adb push mediascape.apk /data/app" no quotes.
6. Run "adb shell reboot" no quotes.
BTW: I have copied all the mediascape related files back to /system/app as well, by running "adb shell chmod 777 /system/app" and using adb push.
Seems it's not ideal as the apk is not installed but added to the X10 directly.
Any better ideas?
Try RealPlayer for Android, it's a new app, really good!
w w w.real.com/realplayer/android
Nah, nothing can beat mediascape.
anyway, how can one get timescape back?
Fuzalert2k said:
Nah, nothing can beat mediascape.
anyway, how can one get timescape back?
Click to expand...
Click to collapse
you mean timescape? or mediascape?
shvyue said:
Thanks for the great job done by developers. However, I noticed mediascape was removed after root. Personally I think mediascape is nice but failed to install it from the app folder on sdcard. Searched the whole thread but didn't find a method.
I tried manually copy the mediascape.apk to /data/app, reboot, then mediascape is restored in the application drawer and can be run functionally.
Here is the details.
Connect the X10 to PC using USB debug mode.
Get the adb.exe ready (you can run it from the root step4 folder directly)
0. Copy mediascape.apk to the step4 folder.
1. Start command prompt as administrater.
2. Change to the step4 folder.
3. Run "adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system" without quotes.
4. Run "adb shell chmod 777 /data/app" without quotes.
5. Run "adb push mediascape.apk /data/app" no quotes.
6. Run "adb shell reboot" no quotes.
BTW: I have copied all the mediascape related files back to /system/app as well, by running "adb shell chmod 777 /system/app" and using adb push.
Seems it's not ideal as the apk is not installed but added to the X10 directly.
Any better ideas?
Click to expand...
Click to collapse
done this and mediscape still dont apear and cant install it through astro file manager
Can you see mediascape.apk in the /data/app folder? If yes have you copied 4 mediascape files back to /system/app?
Sent from my SO-01B using Tapatalk
hmm I don't seem to have the app folder in my data folder, in my memory card can someone help me out
The data/app folder is not on your sdcard. Up one level.
Sent from my SO-01B using Tapatalk
shvyue said:
you mean timescape? or mediascape?
Click to expand...
Click to collapse
I mean timescape
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
hey is der ne way i can get mediascape running on ne othr device than x10??? just asking
nosidefcp said:
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
Click to expand...
Click to collapse
How exactly do you do this? What do you edit... siggh
nosidefcp said:
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
Click to expand...
Click to collapse
This worked for me. Thanks!
Fuzalert2k said:
How exactly do you do this? What do you edit... siggh
Click to expand...
Click to collapse
Turn on USB-debugging mode. Run command prompt (start->run->"cmd"). Change to your step4 directory. Enter those commands line by line.
nosidefcp said:
done this and it works. mediascpae reinstaled in my rooted x10
open dos prompt with administrator privileges, change do step4 folder and do this:
Originally Posted by maxmaniac View Post
Well Root worked for me,
Thanks Guys!!!
Anyway, I was able to get Mediascape to work again using a small script I wrote (looking at those made by our developers).
Here's what i've done:
IMPORTANT: you must have *.apk and *.odex files on your sdcard!!
----------------------------------------------------
@echo off
adb shell mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
adb shell dd if=/sdcard/apps/MediascapePluginManager.apk of=/system/app/MediascapePluginManager.apk
adb shell dd if=/sdcard/apps/MediascapePluginManager.odex of=/system/app/MediascapePluginManager.odex
adb shell chmod 644 /system/app/MediascapePluginManager*
adb shell dd if=/sdcard/apps/mediascape.apk of=/system/app/mediascape.apk
adb shell dd if=/sdcard/apps/mediascape.odex of=/system/app/mediascape.odex
adb shell chmod 644 /system/app/mediascape*
adb shell reboot
----------------------------------------------------
I don't know if this will work for all of you, but it worked for me.
Don't really know if this breaks anything in your X10, so use this at your own risk.
Thanks again for rooting this thing!!
André
Click to expand...
Click to collapse
op's method did not work for me but this one worked perfect
it worked now.
thanks so much for the instruction
thanksss it works
would anyone please upload *.apk and *.odex files please, since i cant find em on my x10 anymore. thanks
*.odex files
can some one please share mediascape.odex and MediascapePluginManager.odex files
Both the stock 2.1 gallery and for example doubletwist or poweramp kicks mediascapes ass when it comes to usability, I installed Z's 2.2.1 ROM a week ago and must admit that I dont miss media/timescape one bit Bottom case is that I'll rather use a semi-stable 2.2 ROM than a slow SE rom ;-)
Hello.
I have some files that I want to push inside the /sdcard.They are all of the same type (.img).Here is what I am experiencing:
Code:
adb push *.img /sdcard
returns the adb command help... doesn't work obviously
If I put all the files inside a folder (eg. img):
Code:
adb push C:\Nexus/img /sdcard/
it starts copying all the contents of the img folder to /sdcard (adb ls /sdcard/ confirms so)
now if I want to remove those files from /sdcard, since they happen to have the same extension:
Code:
adb shell rm /sdcard/*.img
and all these image files (.img) are removed - the wildcard now is working.
Now is this normal behaviour or am I missing something? I mean is it that ADB command does not support wildcards?
If so copying the contents of a folder is it the only way to mass copy from PC to the phone?
Thank you.
Yea i believe it will only push or pull a full folder or a specific file.. but thats the beauty of it.. dump all the files you want in a folder and push it right where you want them
Based on my very limited experience, wildcards are not supported by push/pull commands, but you can pass along anything you want through "adb shell" and wildcards will be processed as expected.
-- Sent from my TouchPad using Communities
Yes I 've searched a lot myself and seems the only way is the "copy to folder" trick.Thanks for your input.
*Puzzled why they didn't include that option inside the command*
Can I change permissions of several Files that I have pushed into a system folder ??
DJLamontagneIII said:
Yea i believe it will only push or pull a full folder or a specific file.. but thats the beauty of it.. dump all the files you want in a folder and push it right where you want them
Click to expand...
Click to collapse
:good:Information shared on this thread is useful to me..
I come to understand that I can push multiple files to /system/<directory> using following command
Can I do this:
Copy all file to a folder and then copied the whole folder to adb.exe directory. sy my Folder name is "MoveAll" in C:\<adb directory)
adb push MoveAll system/app (got root access and remount rw to do this)
or
adb push MoveAll system/lib
Now my question is that can I change the file permissions as well in on shot ???
adb shell chmod 644 /system/app/*.apk (if all files that i copied are .apk files)
or
adb shell chmod 644 /system/lib/*.so (if all files that i copied are .so files)
................................will it work ???
A little help on this would be highly appreciated. Thanks in advance !!! :good:
VioletR said:
:good:Information shared on this thread is useful to me..
I come to understand that I can push multiple files to /system/<directory> using following command
Can I do this:
Copy all file to a folder and then copied the whole folder to adb.exe directory. sy my Folder name is "MoveAll" in C:\<adb directory)
adb push MoveAll system/app (got root access and remount rw to do this)
or
adb push MoveAll system/lib
Now my question is that can I change the file permissions as well in on shot ???
adb shell chmod 644 /system/app/*.apk (if all files that i copied are .apk files)
or
adb shell chmod 644 /system/lib/*.so (if all files that i copied are .so files)
................................will it work ???
A little help on this would be highly appreciated. Thanks in advance !!! :good:
Click to expand...
Click to collapse
What operating system do you use on your computer?
I test with:
Code:
adb push *.img /sdcard
Code:
adb push C:\Nexus/img /sdcard/
Code:
adb shell rm /sdcard/*.img
But They do not work. Can you help me???
kid1519 said:
I test with:
Code:
adb push *.img /sdcard
Code:
adb push C:\Nexus/img /sdcard/
Code:
adb shell rm /sdcard/*.img
But They do not work. Can you help me???
Click to expand...
Click to collapse
Hello.
Wildcards (*.fileExtension) do not work with adb or so it seems.You could always use the "copy to folder" trick though.
Put all your images in a folder - I assume you have windows.So:
all images to C:\Images
then open adb and:
adb push C:\Images/ /sdcard/Images/
the above command will copy all the contents of the C:\Images folder (so practically all your images in there) to the /sdcard/Images folder (could be any folder you prefer).
TR-909 said:
Hello.
Wildcards (*.fileExtension) do not work with adb or so it seems.You could always use the "copy to folder" trick though.
Put all your images in a folder - I assume you have windows.So:
all images to C:\Images
then open adb and:
adb push C:\Images/ /sdcard/Images/
the above command will copy all the contents of the C:\Images folder (so practically all your images in there) to the /sdcard/Images folder (could be any folder you prefer).
Click to expand...
Click to collapse
thanks. :X
Now, i can push. ok.
But
adb shell chmod
Click to expand...
Click to collapse
can you show me.
ex:
adb shell chmod 644 /system/app/mp3.zing.vn.apk
adb shell chmod 644 /system/app/mp3.zing.vn.odex
adb shell chmod 644 /system/app/mxtech.videoplayer.apk
adb shell chmod 644 /system/app/mxtech.videoplayer.odex
adb shell chmod 644 /system/app/nct.apk
adb shell chmod 644 /system/app/nct.odex
adb shell chmod 644 /system/app/notepad.color.note.apk
adb shell chmod 644 /system/app/notepad.color.note.odex
adb shell chmod 644 /system/app/Quickofficev5.7.327.apk
adb shell chmod 644 /system/app/Quickofficev5.7.327.odex
adb shell chmod 644 /system/app/Screenshot.ER.PROv2.4.3.2.apk
adb shell chmod 644 /system/app/Screenshot.ER.PROv2.4.3.2.odex
adb shell chmod 644 /system/app/viber.apk
adb shell chmod 644 /system/app/viber.odex
adb shell chmod 644 /system/app/vietmobitv.apk
adb shell chmod 644 /system/app/vietmobitv.odex
adb shell chmod 644 /system/app/yahoo.mobile.apk
adb shell chmod 644 /system/app/yahoo.mobile.odex
adb shell chmod 644 /system/app/youtube.apk
adb shell chmod 644 /system/app/youtube.odex
Click to expand...
Click to collapse
--->>>
adb shell chmod 644 /system/app/*.apk
adb shell chmod 644 /system/app/*.odex
Click to expand...
Click to collapse
kid1519 said:
thanks. :X
Now, i can push. ok.
But
can you show me.
ex:
--->>>
Click to expand...
Click to collapse
Well I am not familiar with multiple permission changes through adb or even shell.Maybe some other more experienced member could help.Or maybe better make a post of your own exclusively for that.
This might work on other devices.
WARNING: this might brick your phone use it at your own risk.
Warning you have to have some knowlage of linux to do this kind of stuff.
WARNING: actually you have to have _good_ knowlage of linux/gnu stuff to do it.
The idea is this is to make the /system/bin/toolbox from the stock rom suid (permision 6755, it originaly has 0755)
This is how I did it. It might be simpler.
get a stock rom that you want. for me it was B5330XWALH3
it is now available at samsung-updates.
You need odin (heimdal will not work with my phone) (my was 3.07)
unpack the zip.
you get a .tar.md5 file (the tar file has broken headers so tar from ubuntu 12.04 will not unpackit).
the tar file works in sectors of 512 bytes.
take out the md5sum at the end of file. (some thing like: head -c (the size up to the last md5sum) original.tar.md5 > file1)
split the file so you will have the system.img.md5 separated (some thing like: head -c (the size upto "system.img.md5") file1 > file2;
head -c (the size upto "dt-blob.md5") file1 | tail -c +(the size upto "system.img.md5" + 1) > file3;
tail -c +(the size upto "dt-blob.md5" + 1) file1 > file4
file3 now has the system.img.md5, trim the md5sum from the tail and the tar headr from head (ex.:
head -c (upto the md5sum output from the rear of the file) file3 | tail -c +513 > file5)
file5 is a sparce image file of an ext4 filesystem. run simg2img (from ext4fs_utils (search on xda)) (ex.:
simg2img file5 file6)
sudo mount -o loop,ro file6 /mnt
look for the file /mnt/bin/toolbox (ex.: ls -l /mnt/bin/toolbox) it will give you an output like this:
-rwxr-xr-x 1 root 2000 99068 Aug 9 07:59 /mnt/bin/toolbox
sudo umount /mnt
the permisions and the size of the file yield the following hex sequence that you get in the file (we will hexedit the ext4 fs): ED 81 00 00 FC 82 01 00
in file3 edit the sequence (it should be only one in the file) from ED 81 00 00 FC 82 01 00 to ED 8D 00 00 FC 82 01 00 (practically adding the suid guid bits to the inode of the toolbox)
we are almost done, now to pack our bags and go.
verify that you have indeed put suid guid to toolbox:
head -c (upto the md5sum output from the rear of the file) file3 | tail -c +513 > file5;
simg2img file5 file6;
sudo mount -o loop,ro file6 /mnt;
ls -l /mnt/bin/toolbox
It should give an output:
-rwsr-sr-x 1 root 2000 99068 Aug 9 07:59 /mnt/bin/toolbox
sudo umount /mnt
recalculate the md5sum to the _expanded_ image: md5sum file6 > file7
overide the md5sum at the end of file3 with the one from file7
now pack the pieces in one tar: cat file2 file3 file4 > myfirmware.tar
add the md5sum to it: md5sum myfirmware.tar >> myfirmware.tar
change the name to .tar.md5: mv myfirmware.tar myfirmware.tar.md5
copy the file on a windowze machine (that has odin and the samsung drivers intalled).
update with odin the new firmware (which you should put in the PDA section) (don't forget to un check the repartitioning).
you should have now a practivally rooted device.
in order to have su and Superuser.apk on it you have to do the following steps:
push with adb su, busybox and Superuser.apk into /data/local/tmp on device (you get the files from other forums here at xda)
the next steps are on device (use adb shell)
verify that indeed we have a suid toolbox: ls -l /system/bin/toolbox should give that wanderfull -rwsr-sr-x permission.
find a rw mount that has suid (in my case a tmpfs is mounted /mnt/obb)
copy su to /mnt/obb (remember that we have suid toolbox this means that toolbox now gives you root on any command):
dd if=/data/local/tmp/su of=/mnt/obb/su
give su suid and make it owned by root: chmod 6755 /mnt/obb/su; chown 0.0 /mnt/obb/su
run su now and enjoy the #: /mnt/obb/su -
Click to expand...
Click to collapse
Ofcorse after you get # you should remount /system as rw, copy su in /system/xbin, copy Superuser.apk in /system/app, copy busybox in /system/xbin, make symlinks to busybox for all the comands in /system/xbin.
You should also upon success remove suid from toolbox so as to not mistakely do damage to the system (for instance "rm /")
And here you have it.
If you do not understand what I have done, you should read more linux / tar / ext4 / md5sum.
This method should work for any phone provided that it has odin as bootloader and there is the stock rom available.
hello
I don't have knowledge about how you have rooted the firmware for b5330, the steps you made are waaaay to dificult for me . Could you provide here an already rooted firmware, to download and install. thanks in advance
ETTT said:
This might work on other devices.
WARNING: this might brick your phone use it at your own risk.
Warning you have to have some knowlage of linux to do this kind of stuff.
WARNING: actually you have to have _good_ knowlage of linux/gnu stuff to do it.
The idea is this is to make the /system/bin/toolbox from the stock rom suid (permision 6755, it originaly has 0755)
This is how I did it. It might be simpler.
Ofcorse after you get # you should remount /system as rw, copy su in /system/xbin, copy Superuser.apk in /system/app, copy busybox in /system/xbin, make symlinks to busybox for all the comands in /system/xbin.
You should also upon success remove suid from toolbox so as to not mistakely do damage to the system (for instance "rm /")
And here you have it.
If you do not understand what I have done, you should read more linux / tar / ext4 / md5sum.
This method should work for any phone provided that it has odin as bootloader and there is the stock rom available.
Click to expand...
Click to collapse
bogdan_rize said:
I don't have knowledge about how you have rooted the firmware for b5330, the steps you made are waaaay to dificult for me . Could you provide here an already rooted firmware, to download and install. thanks in advance
Click to expand...
Click to collapse
no need to upload 400M for this little modification.
I'm unable to post links, goto samsung-updates
go and download B5330XWALI2_B5330OXXALI2_B5330XWLH1_HOME stock firmware.
and apply this xdelta patch over it.
xdelta patch sGTB5330.patch B5330XWALI2_B5330OXXALI2_B5330XWLH1_HOME.tar.md5 myfrm.tar.md5
Click to expand...
Click to collapse
after that you have the firmware that I use to root my phone.
Still... this firmware will not have "su" install, it will just be a rootable firware because it has a suid'ed toolbox.
a suid'ed toolbox in android means that you can exec chown and chmod as a root.
So. After the patching of the stock rom and flashing it. you have to have this md5sum output:
032b4344ab503c8413db9127efaa3d83 myfrm.tar.md5
Click to expand...
Click to collapse
odin will accept it (I've used Oding 3.07).
after that you push the files from the attached tar.gz to /data/local/tmp
tar -xzf superuser_stuff.tar.gz
adb push su /data/local/tmp
adb push Superuser.apk /data/local/tmp
adb push busybox /data/local/tmp
Click to expand...
Click to collapse
after that you bassically have to run this commands in an android shell in order to get to a stardard rooted android:
adb shell # enter the in the phone
dd if=/data/local/tmp/su of=/mnt/obb/su # copy the su binary to a place that can be sudoed
chown 0.0 /mnt/obb/su # modify the owner
chmod 6755 /mnt/obb/su # set SUID flag.
/mnt/obb/su # becomes root !!
mount -o remount,rw /system # remount the system partition as readwrite.
dd if=/data/local/tmp/su of=/system/xbin/su #copy su in path
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chmod 755 /system/bin/toolbox # close the security hole (toolbox is nologer with SUID)
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk # copy the superuser application
chown 0.0 /system/app/Superuser.apk
chmod 666 /system/app/Superuser.apk
#now this is done for busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown 0.0 /system/xbin/busybox
chmod 755 /system/xbin/busybox
Click to expand...
Click to collapse
have fun.
I downloaded this firmware: Samsung-Updates.com-GT-B5330_COA_1_20120913171601_pducfx5hbw.zip. Where, how, what???...i unzipped it and now how to apply the patch? The rest of the stept i think i get it....i think For you it's easy to say, for me it's hard to do. I've had sgs1, sgs2 and sgs3, and the root of those was sooooooo easy... but this piece of crap b5330 drives me crazy )
ETTT said:
no need to upload 400M for this little modification.
I'm unable to post links, goto samsung-updates
go and download B5330XWALI2_B5330OXXALI2_B5330XWLH1_HOME stock firmware.
and apply this xdelta patch over it.
after that you have the firmware that I use to root my phone.
Still... this firmware will not have "su" install, it will just be a rootable firware because it has a suid'ed toolbox.
a suid'ed toolbox in android means that you can exec chown and chmod as a root.
So. After the patching of the stock rom and flashing it. you have to have this md5sum output:
odin will accept it (I've used Oding 3.07).
after that you push the files from the attached tar.gz to /data/local/tmp
after that you bassically have to run this commands in an android shell in order to get to a stardard rooted android:
have fun.
Click to expand...
Click to collapse
bogdan_rize said:
I downloaded this firmware: Samsung-Updates.com-GT-B5330_COA_1_20120913171601_pducfx5hbw.zip. Where, how, what???...i unzipped it and now how to apply the patch? The rest of the stept i think i get it....i think For you it's easy to say, for me it's hard to do. I've had sgs1, sgs2 and sgs3, and the root of those was sooooooo easy... but this piece of crap b5330 drives me crazy )
Click to expand...
Click to collapse
I've used xdelta package.
if you are on win then you're on your own.
there is xdelta.org and it seems to have pachage for windows.
for sgs[123] was easy because are main streams. may hackers were working on it.
this device is very new/obscure.
I whould have made a script, but alas, "heimdal" firmware loader whould not work with this device.
I've used linux to patch the firmware and windowze to upload it.
So a script whould be imposible, but after you pach .tar.md5 file and load it on your phone is just about cut and paste form my previous post.
My hope is that a more android savy guy will take this concept and make it a script.
I am just happy that I can now have debian on my phone.
yes, i am on win....there is no way to patch that COA firmware (i am from romania) and upload somewhere to download???i know i am probably asking to much from you, but i dont't think i will manage by my own...this rooting busines is driving me crazyyyyy :crying::crying::crying: thank you so much for your answer!!!
ETTT said:
I've used xdelta package.
if you are on win then you're on your own.
there is xdelta.org and it seems to have pachage for windows.
for sgs[123] was easy because are main streams. may hackers were working on it.
this device is very new/obscure.
I whould have made a script, but alas, "heimdal" firmware loader whould not work with this device.
I've used linux to patch the firmware and windowze to upload it.
So a script whould be imposible, but after you pach .tar.md5 file and load it on your phone is just about cut and paste form my previous post.
My hope is that a more android savy guy will take this concept and make it a script.
I am just happy that I can now have debian on my phone.
Click to expand...
Click to collapse
bogdan_rize said:
yes, i am on win....there is no way to patch that COA firmware (i am from romania) and upload somewhere to download???i know i am probably asking to much from you, but i dont't think i will manage by my own...this rooting busines is driving me crazyyyyy :crying::crying::crying: thank you so much for your answer!!!
Click to expand...
Click to collapse
ok here it is the modified firmware.
http://dl.transfer.ro/myfrm-transfer_ro-29oct-8a4089.zip
Interesting, reading carefully
Sent from my GT-B5330 using xda app-developers app
Thank you so much, tomorow morning i know how i'll spend my time...installing and rooting my b5330, unfortunately this evening i don't have my laptop on me forgoted at work ), but i've downloaded the firmware from phone and now waiting to have it done...finally!!! I'll let you know what have i done. Have a nice day and once again thanks!!!
ETTT said:
ok here it is the modified firmware.
http://dl.transfer.ro/myfrm-transfer_ro-29oct-8a4089.zip
Click to expand...
Click to collapse
it's not working, when i'm trying to adb remont it says: remount failed: Opertaion not permited. After i flashed with odin the firmware you gave to me, i think i do not have permission to make any changes, and i don't know why
ETTT said:
ok here it is the modified firmware.
http://dl.transfer.ro/myfrm-transfer_ro-29oct-8a4089.zip
Click to expand...
Click to collapse
Can you make patch for dxlh3..? Thanks
Sent from my GT-B5330 using xda app-developers app
bogdan_rize said:
it's not working, when i'm trying to adb remont it says: remount failed: Opertaion not permited. After i flashed with odin the firmware you gave to me, i think i do not have permission to make any changes, and i don't know why
Click to expand...
Click to collapse
There commands are supposed to be given in a command line box (cmd on win).
where does it gives you error?
adb shell # enter the in the phone
dd if=/data/local/tmp/su of=/mnt/obb/su # copy the su binary to a place that can be sudoed
chown 0.0 /mnt/obb/su # modify the owner
chmod 6755 /mnt/obb/su # set SUID flag.
/mnt/obb/su # becomes root !!
mount -o remount,rw /system # remount the system partition as readwrite.
dd if=/data/local/tmp/su of=/system/xbin/su #copy su in path
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chmod 755 /system/bin/toolbox # close the security hole (toolbox is nologer with SUID)
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk # copy the superuser application
chown 0.0 /system/app/Superuser.apk
chmod 666 /system/app/Superuser.apk
#now this is done for busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown 0.0 /system/xbin/busybox
chmod 755 /system/xbin/busybox
finally it worked
yeeeees, damn you're good!!!! i have managed to root my b5330, root checher tell me that i am rooted and busybox is instaled...the only problem is that it shows me that i do not have installed superuser and supersu. Is there a problem if i just copy paste the apk file (supersu.apk and superuser.apk -> i've downloaded the pro version of bouth of them ) straight into the directory /data/local/tmp where it should be? or to copy-paste in another directory. Thanks in advance, CMD(and adb shell) gave me headache, but i finally got it an succedeed )) :victory::good:
ETTT said:
There commands are supposed to be given in a command line box (cmd on win).
where does it gives you error?
adb shell # enter the in the phone
dd if=/data/local/tmp/su of=/mnt/obb/su # copy the su binary to a place that can be sudoed
chown 0.0 /mnt/obb/su # modify the owner
chmod 6755 /mnt/obb/su # set SUID flag.
/mnt/obb/su # becomes root !!
mount -o remount,rw /system # remount the system partition as readwrite.
dd if=/data/local/tmp/su of=/system/xbin/su #copy su in path
chown 0.0 /system/xbin/su
chmod 6755 /system/xbin/su
chmod 755 /system/bin/toolbox # close the security hole (toolbox is nologer with SUID)
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk # copy the superuser application
chown 0.0 /system/app/Superuser.apk
chmod 666 /system/app/Superuser.apk
#now this is done for busybox
dd if=/data/local/tmp/busybox of=/system/xbin/busybox
chown 0.0 /system/xbin/busybox
chmod 755 /system/xbin/busybox
Click to expand...
Click to collapse
bogdan_rize said:
yeeeees, damn you're good!!!! i have managed to root my b5330, root checher tell me that i am rooted and busybox is instaled...the only problem is that it shows me that i do not have installed superuser and supersu. Is there a problem if i just copy paste the apk file (supersu.apk and superuser.apk -> i've downloaded the pro version of bouth of them ) straight into the directory /data/local/tmp where it should be? or to copy-paste in another directory. Thanks in advance, CMD(and adb shell) gave me headache, but i finally got it an succedeed )) :victory::good:
Click to expand...
Click to collapse
1. I'm glad you got it.
2. You should give thanks (that button) if I helped you.
3. I'm you dont read instructions. Maybe it's a problem with us romanian engineers, or maybe engineers in general
look at item 11. from my previous post. maybe I just c&p here.
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
So, when you are in adb shell and you go root (su command, you get the promt with #) and you have the /system mounted rw.
Then any apk that you copy to /system/app folder will get intalled and when you list your application (the button with 16 squares) you should see it.
Have fun.
i was having trouble understanding adb shell and cmd from the begining. I never used this command tool...ever ) and i think from yesterday to this day i managed really ok . Anyway i think i will just copy-paste the superuser.apk in "app" folder directly in the system (it's the same thing, isn't it??). I have done that in item 11., and after a restart supersu was instaled, only superuser.apk didn't, i think i wrote something wrong in adb shell
ETTT said:
1. I'm glad you got it.
2. You should give thanks (that button) if I helped you.
3. I'm you dont read instructions. Maybe it's a problem with us romanian engineers, or maybe engineers in general
look at item 11. from my previous post. maybe I just c&p here.
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
So, when you are in adb shell and you go root (su command, you get the promt with #) and you have the /system mounted rw.
Then any apk that you copy to /system/app folder will get intalled and when you list your application (the button with 16 squares) you should see it.
Have fun.
Click to expand...
Click to collapse
hihihi
neeeah, my bad, i thought that in "superuser_stuff" is superuser and supersu files, it was just su->for superuser.apk, easy peasy, it worked and installed from the first time...it was just me verry verry dizzy and confused. Your guide is 100% OK, my phone is rooted and now i can enjoy !!!
ETTT said:
1. I'm glad you got it.
2. You should give thanks (that button) if I helped you.
3. I'm you dont read instructions. Maybe it's a problem with us romanian engineers, or maybe engineers in general
look at item 11. from my previous post. maybe I just c&p here.
dd if=/data/local/tmp/Superuser.apk of=/system/app/Superuser.apk
So, when you are in adb shell and you go root (su command, you get the promt with #) and you have the /system mounted rw.
Then any apk that you copy to /system/app folder will get intalled and when you list your application (the button with 16 squares) you should see it.
Have fun.
Click to expand...
Click to collapse
can you release xdelta patch for your XWALH3 because we have the same device..
phyxar said:
can you release xdelta patch for your XWALH3 because we have the same device..
Click to expand...
Click to collapse
I've started a new more universal thread:
http://forum.xda-developers.com/showthread.php?t=1965600
There you have the shell-script that will patch the firmware for you.
If you still want an xdelta patch I'll make one for you but:
Give a man a fish and it will be full for the day, teach him how to fish and it will never go hungry again.
Have fun.
ETTT said:
ok here it is the modified firmware.
dl.transfer.ro/myfrm-transfer_ro-29oct-8a4089.zip
Click to expand...
Click to collapse
Hello, i'm new here and i don't know about scripting, so need your help..
i downloaded your firmware and install it to my b5330 and did the cmd command, and it worked, thanks..:good:
but now i've a new problem that my b5330 can't type a question mark ('?').. can you help me please..
whenever i want to type a question mark it always typed a comma (',') in the screen..:crying:
it also it change the symbol and language key to emoticon and symbol, but that's not a problem for me..
andhikarogue said:
Hello, i'm new here and i don't know about scripting, so need your help..
i downloaded your firmware and install it to my b5330 and did the cmd command, and it worked, thanks..:good:
but now i've a new problem that my b5330 can't type a question mark ('?').. can you help me please..
whenever i want to type a question mark it always typed a comma (',') in the screen..:crying:
it also it change the symbol and language key to emoticon and symbol, but that's not a problem for me..
Click to expand...
Click to collapse
That's because you have use the romanian firmware. whitch has a qwerty layout keyboard.
you have to do it the right way:
first. find the firmaware for your region:
http://samsung-updates.com/device/?id=GT-B5330
second. find a linux machine and run the script from the thread.
It is unrealistic for me to just upload all the 40 version of the firmware patched.
That is why I've made the script.
If you don't have a linux machine then look for a virtual box ubuntu and run on it.
Cheers.