Database Info

How to get APPS back into system/apps/

I updated my rom and there are some omitted apps that I would like to get back into system/apps/ for example VoiceDialer.apk, but I cannot seem to get them back on. I am using Fresh Rom 0.4 and the phone is obviously rooted. maybe I am doing something wrong in adb shell but I keep getting one of 2 different erors. Either permission denied or adb not found. Thank you in advance for your help.

flaav8r said:
I updated my rom and there are some omitted apps that I would like to get back into system/apps/ for example VoiceDialer.apk, but I cannot seem to get them back on. I am using Fresh Rom 0.4 and the phone is obviously rooted. maybe I am doing something wrong in adb shell but I keep getting one of 2 different erors. Either permission denied or adb not found. Thank you in advance for your help.
Click to expand...
Click to collapse
1) Permission denied - make sure that when you do an adb shell, you're root (have the # prompt) and make sure you've mounted /system as rw (adb remount)
2) adb not found - make sure there's only one adb.exe on your computer and that it's the one from the SDK and that the SDK's /tools directory is in your path (to be safe, you can always just run adb from that directory)

jmanley69 said:
1) Permission denied - make sure that when you do an adb shell, you're root (have the # prompt) and make sure you've mounted /system as rw (adb remount)
2) adb not found - make sure there's only one adb.exe on your computer and that it's the one from the SDK and that the SDK's /tools directory is in your path (to be safe, you can always just run adb from that directory)
Click to expand...
Click to collapse
1. the procedure I used is this: from the cmd prompt in the androidsdk/tools/ directory:
adb shell
$ su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# cd /system/app
# adb push VoiceDialer.apk system/app
but its a no go. Can't understand why.
BTW, I have the VoiceDialer.apk file in the androidsdk/tools folder just to make the push easier.

Ok, here is a screen shot from my command prompt window. I know someone knows what the hell I'm doing wrong. Just wanna get the damn voice dialer back on my phone. Please help, thank you.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Barry>cd \
C:\>cd androidsdk\tools\
C:\AndroidSDK\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ su
su
# mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
# adb push VoiceDialer.apk /system/app/
adb push VoiceDialer.apk /system/app/
adb: not found
#

you cant do adb push while in shell ($ or #). Exit out and just try tying the adb push

goku14238 said:
you cant do adb push while in shell ($ or #). Exit out and just try tying the adb push
Click to expand...
Click to collapse
When I do that I get permission denied or something to that effect.

Yeah there's a post about this in the Fresh thread.
The most straightforward way is this:
Reboot to the recovery partition.
adb shell into the phone.
Issue the following command to mount the system partition:
mount -t yaffs2 /dev/block/mtdblock3 /system
Type exit to exit the shell.
Then do:
adb push c:\directory-with-the-apks /system/app

jonnythan said:
Yeah there's a post about this in the Fresh thread.
The most straightforward way is this:
Reboot to the recovery partition.
adb shell into the phone.
Issue the following command to mount the system partition:
mount -t yaffs2 /dev/block/mtdblock3 /system
Type exit to exit the shell.
Then do:
adb push c:\directory-with-the-apks /system/app
Click to expand...
Click to collapse
Thank-you, I will give it a try.

Re-install mediascape after root.

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 ;-)

[Q] ROOT For Noontec A9 ICS 4.0.4 Needed?

Hi, im new to this forum so please go easy guys....
I have a Noontec A9 that i have flashed with ICS 4.0.4 update_RK2918_Android4.0_DDR512M_456M_20120604.img
using RKBatchTool
Described in post #7 here:
http://forum.xda-developers.com/showthread.php?t=1526623The firmware is realy good BUT I cant get root access...
Tried installing superuser etc with no luck :'(
Does anyone know how to root this firmware or is there an alternitive rooted ICS 4.0.4 ROM out???
Verg0

Hi,
Not sure if I can help you with the root problem - but just wondering how you where you can get the ICS update as I can't seem to find this anywhere.
I've got root on the my Noontec A9 based on the previous firmware I installed but its only 2.3. Would much rather have ICS without root (although root is handy).
Thanks in advance.

bjingham said:
Hi,
Not sure if I can help you with the root problem - but just wondering how you where you can get the ICS update as I can't seem to find this anywhere.
I've got root on the my Noontec A9 based on the previous firmware I installed but its only 2.3. Would much rather have ICS without root (although root is handy).
Thanks in advance.
Click to expand...
Click to collapse
Read my top post there is a link to the thread its post number 7, i cant post external links as i dont have enough post counts

verg0 said:
Read my top post there is a link to the thread its post number 7, i cant post external links as i dont have enough post counts
Click to expand...
Click to collapse
Am wondering if there's any development for this? Post number 7 is meant for firmware v1.2.09 but mine is v1.2.10. Furthermore, will it upgrade to ICS? What about the performance since only got 512MB RAM?

So any update on ICS for this device? I dont want to rip apart my machine. Should be a way to do this with USB drive or SD media card.

damez2000 said:
So any update on ICS for this device? I dont want to rip apart my machine. Should be a way to do this with USB drive or SD media card.
Click to expand...
Click to collapse
(missing "www" in all links due to post restrictions...)
- First, regarding the upgrade to ICS 4.0.4 4 (shared.com/zip/UeXHOs6t/Noontec_A9.html), it is NOT necessary to open the device to manage to install the adb driver.
With android in debugging mode when you connect the usb "printer" cable to the PC it will ask for the adb driver.
Get the adb driver from the service page of nontec noontec.com/files/updAteforA9/A9%20software%20update%20guide.zip (it is inside the folder step one_install the driver > ADB_driver_r03-windows)
When you run the RKbatchtool now you should see a pink color in connected device 1. If you press the switch button, it will ask for rockusb driver. Get it from the rockusb_driver folder. After install the color turns blue and you are ready to upgrade to ICS 4.0.4.
- Now it is turn to root ICS 4.0.4
download the adb driver for ICS here mediafire.com/download.php?kmy55fhj9ab2kfe
download the script here multiupload.nl/83WWEZI22K
You get a general script that is NOT necessary to run in full because the adb shell already has root access when in debugging mode;
instead run this simplified "runme.bat" script :
Code:
@files\adb wait-for-device
@echo --- DEVICE FOUND
@echo --- remounting /system rw
@files\adb shell "mount -o remount,rw /system"
@echo --- pushing busybox
@files\adb push files\busybox /system/xbin/.
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@files\adb shell "chmod 06755 /system/bin/su"
@echo --- correcting symlinks
@files\adb shell "rm /system/xbin/su"
@files\adb shell "ln -s /system/bin/su /system/xbin/su"
@echo --- pushing Superuser app
@files\adb push files\Superuser.apk /system/app/.
@echo --- remounting /system ro
@files\adb shell "mount -o remount,ro /system"
@echo --- rebooting
@files\adb reboot
@echo ALL DONE!!!
@pause

jmatbastos said:
(missing "www" in all links due to post restrictions...)
- First, regarding the upgrade to ICS 4.0.4 4 (shared.com/zip/UeXHOs6t/Noontec_A9.html), it is NOT necessary to open the device to manage to install the adb driver.
With android in debugging mode when you connect the usb "printer" cable to the PC it will ask for the adb driver.
Get the adb driver from the service page of nontec noontec.com/files/updAteforA9/A9%20software%20update%20guide.zip (it is inside the folder step one_install the driver > ADB_driver_r03-windows)
When you run the RKbatchtool now you should see a pink color in connected device 1. If you press the switch button, it will ask for rockusb driver. Get it from the rockusb_driver folder. After install the color turns blue and you are ready to upgrade to ICS 4.0.4.
- Now it is turn to root ICS 4.0.4
download the adb driver for ICS here mediafire.com/download.php?kmy55fhj9ab2kfe
download the script here multiupload.nl/83WWEZI22K
You get a general script that is NOT necessary to run in full because the adb shell already has root access when in debugging mode;
instead run this simplified "runme.bat" script :
Code:
@files\adb wait-for-device
@echo --- DEVICE FOUND
@echo --- remounting /system rw
@files\adb shell "mount -o remount,rw /system"
@echo --- pushing busybox
@files\adb push files\busybox /system/xbin/.
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@files\adb shell "chmod 06755 /system/bin/su"
@echo --- correcting symlinks
@files\adb shell "rm /system/xbin/su"
@files\adb shell "ln -s /system/bin/su /system/xbin/su"
@echo --- pushing Superuser app
@files\adb push files\Superuser.apk /system/app/.
@echo --- remounting /system ro
@files\adb shell "mount -o remount,ro /system"
@echo --- rebooting
@files\adb reboot
@echo ALL DONE!!!
@pause
Click to expand...
Click to collapse
Thanks. Just used your method and got ICS rooted without opening the box. But the main reason for having this rooted is to have network drives mounted. Has anyone figured out a working cifs.ko configuration?

Noontec A9 ICS Problem
jmatbastos said:
(missing "www" in all links due to post restrictions...)
- First, regarding the upgrade to ICS 4.0.4 4 (shared.com/zip/UeXHOs6t/Noontec_A9.html), it is NOT necessary to open the device to manage to install the adb driver.
With android in debugging mode when you connect the usb "printer" cable to the PC it will ask for the adb driver.
Get the adb driver from the service page of nontec noontec.com/files/updAteforA9/A9%20software%20update%20guide.zip (it is inside the folder step one_install the driver > ADB_driver_r03-windows)
When you run the RKbatchtool now you should see a pink color in connected device 1. If you press the switch button, it will ask for rockusb driver. Get it from the rockusb_driver folder. After install the color turns blue and you are ready to upgrade to ICS 4.0.4.
- Now it is turn to root ICS 4.0.4
download the adb driver for ICS here mediafire.com/download.php?kmy55fhj9ab2kfe
download the script here multiupload.nl/83WWEZI22K
You get a general script that is NOT necessary to run in full because the adb shell already has root access when in debugging mode;
instead run this simplified "runme.bat" script :
Code:
@files\adb wait-for-device
@echo --- DEVICE FOUND
@echo --- remounting /system rw
@files\adb shell "mount -o remount,rw /system"
@echo --- pushing busybox
@files\adb push files\busybox /system/xbin/.
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/xbin/busybox"
@echo --- correcting permissions
@files\adb shell "chmod 04755 /system/xbin/busybox"
@echo --- pushing SU binary
@files\adb push files\su /system/bin/su
@echo --- correcting ownership
@files\adb shell "chown root.shell /system/bin/su"
@echo --- correcting permissions
@files\adb shell "chmod 06755 /system/bin/su"
@echo --- correcting symlinks
@files\adb shell "rm /system/xbin/su"
@files\adb shell "ln -s /system/bin/su /system/xbin/su"
@echo --- pushing Superuser app
@files\adb push files\Superuser.apk /system/app/.
@echo --- remounting /system ro
@files\adb shell "mount -o remount,ro /system"
@echo --- rebooting
@files\adb reboot
@echo ALL DONE!!!
@pause
Click to expand...
Click to collapse
Hi,
many thanks for all your hard work in colating this info. Could you help me please? I have upgraded to ICS on the A9, and whilst it looks good and no doubt offers more scope for usage, it doesn't agree with simple movie watching and You Tube, causiing audio slippage. I have tried to connect again to the pc but try as I might, the PC doesn't want to know. The device is essentially on it's own. Any ideas how to ressurect the old firmware? I have tried the two pin shorting methods to no avail.
Many thanks in advance.

mcpherson35 said:
Hi,
many thanks for all your hard work in colating this info. Could you help me please? I have upgraded to ICS on the A9, and whilst it looks good and no doubt offers more scope for usage, it doesn't agree with simple movie watching and You Tube, causiing audio slippage. I have tried to connect again to the pc but try as I might, the PC doesn't want to know. The device is essentially on it's own. Any ideas how to ressurect the old firmware? I have tried the two pin shorting methods to no avail.
Many thanks in advance.
Click to expand...
Click to collapse
1- Get Rom Toolbox from Google Play Store
2- Run Rom Toolbox > Rebooter > Reboot Bootloader
3 - RKBatchTool and RKAndroidTool will now detect the device and you can flash another firmware
4 - run "step four_ Install Firmware" from
noontec.com/files/updAteforA9/A9%20software%20update%20guide.zip
to get back to Android 2.3

[GUIDE] Rooting Samsung Galaxy [email protected] GT-B5330

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.

[Q] Help! Problem with Tablet Olidata WB7-l

Hi! I'm a noob user, with a weird tablet.
The brand is Olidata (Chile), and the model is Wb7-l. The first problem was that the tipycal: many worng pattern attempts. I though about the usual: hard reset, but this weird tablet doesn't have one!So I tried all button combinations to enter th the hard reset menu, but was unuseful.
Then, I found a post, it said that with a program I could put anoter ROM (PhoenixSuite), and with the ADB Drivers. I could put another ROM, but the touch system doesn't work. Then I searched a second and a Third ROM, but was the same. Then, I remembered that the chip was a A13, and I found another post, where a user said that with a script you could fix that problem. I use the script and... it died :crying: . After that, i tried to connect it to the computer again, but I couldn't.
THEN, i read the script. Now, i'm really really afraid, because maybe the Tablet is dead.
Here's the script:
(I open it with notepad)
@ECHO off
echo Remount
adb remount
adb shell cd /
echo Mount root
adb shell mount -o remount,rw -t ext4 /dev/root /
echo Make dir bootfs
adb shell mkdir bootfs
echo Mount bootfs
adb shell mount -t vfat /dev/block/nanda /bootfs
echo Copy script.bin
adb push "script.bin" /bootfs/script.bin
echo Copy script0.bin
adb push "script.bin" /bootfs/script0.bin
echo Copy zet6221.ko to /system/vendor
adb push "zet6221.ko" /system/vendor/zet6221.ko
adb shell chmod 644 /system/vendor/zet6221.ko
echo Copy zet6221_ts.idc to /system/usr/idc
adb push "zet6221_ts.idc" /system/usr/idc/zet6221_ts.idc
adb shell chmod 644 /system/usr/idc/zet6221_ts.idc
echo Copy preinstall.sh
adb push "preinstall.sh" /system/bin/preinstall.sh
adb shell chmod 755 /system/bin/preinstall.sh
echo Copy setupsensors.sh
adb push "setupsensors.sh" /system/bin/setupsensors.sh
adb shell chmod 755 /system/bin/setupsensors.sh
pause
adb shell reboot
How can I undo what I did? What's the right ROM? (The other one was one called F1(A13)-20121129.1.1.1- )
Please, please help
(Sorry for my weird english, I know just a bit )