$ export PATH=/data/local/bin:$PATH
$ su
# mount -o rw,remount /dev/block/mmcblk0p12 /system
# mount -o rw,remount /dev/bloxk/mmcblk0p17 /system
# rm /system/bin/su
# rm /preinstall/sqlite3
rm failed for /preinstall/sqlite3, Read-only file system
# rm /preinstall/dosu
rm failed for /preinstall/dosu, Read-only file system
#
WHAT DO I DO NOW???? i need to send this in for replacement !
Related
Hey guys, just got my hands on one of these suckers, it runs 2.1
Can anyone point me in the right direction to get root?
Im also looking for froyo, however dont expect it soon, manufacturer is working on it.
Sent from my S7 using XDA App
I second davidcampbell! We need froyo here
The root method is the same as the s7.
download z4root from market and root, after wards install busybox by titanium backup and you are set.
The app2sd mod works for this device since it is similar to the sony x10 on 2.1 but is risky because i lost wifi aftewards. So just explore until we get some real developers working on it hopefully cm6.1 port but after huawei realeases the recovery.img and source to mess around with though.
being able to overclock to 1ghz wouldnt hurt either.
S7 Bootloader?
Has anyone figured out how to get into the bootloader for this device?
Havent been able to through any apps \ commands. Just go to a black screen and thats it, and recovery sends you into factory settings for your device
I only know that pressing back key and call\send key when when powering on the device puts it into update mode.
alexisprz said:
The root method is the same as the s7.
download z4root from market and root, after wards install busybox by titanium backup and you are set.
The app2sd mod works for this device since it is similar to the sony x10 on 2.1 but is risky because i lost wifi aftewards. So just explore until we get some real developers working on it hopefully cm6.1 port but after huawei realeases the recovery.img and source to mess around with though.
being able to overclock to 1ghz wouldnt hurt either.
Click to expand...
Click to collapse
Zomg, nice, thank you alexisprz, it's rooting time
I really wish Android had a better term for rooting, it sounds like I'm either breaking it, or trying to cram my man bits into it some how.
Will this affect my ability to use the manufacturers update to froyo in the future?
UPDATE: z4root worked great, I installed busybox no problemo, very happy forum member here
sir i just bought one telstra touch tab can you plz help me to debrand it and unlock it i also have jtag too
pre needs, new rom and rooted with busybox on SD with linux ext2/3 Partition.
download z4root from market and root
copy 3 files to sd
run App-2-sd.sh
File 1 "App-2-sd.sh"
#!/bin/sh
# untitled.sh
#
#
# Created by Andew Blazely on 5/02/11.
# Copyright 2011 SOFTHOUSE. All rights reserved.
#
# un Hash data if you wish but it will slow the S7 down and cause lots of waiting problems
# pre needs, new rom and rooted with busybox on SD with linux ext2/3 Partition.
# mount the file systems
mount -o rw,remount -t yaffs2 /dev/block/mtdblock1 /system
busybox mkdir /system/sd
mount -t ext2 /dev/block/vold/179:2 /system/sd
# archive dirs (easier than copying)
cd /data/
busybox tar -cvf /system/sd/app.tar app
busybox tar -cvf /system/sd/app-private.tar app-private
# busybox tar -cvf /system/sd/data.tar data
busybox tar -cvf /system/sd/dalvik-cache.tar dalvik-cache
# unpack arcives in correct place
cd /system/sd
busybox tar -xvf app.tar
busybox tar -xvf app-private.tar
# busybox tar -xvf data.tar
busybox tar -xvf dalvik-cache.tar
# cleanup
busybox rm *.tar
# copy and set system files
busybox cp /sdcard/install-recovery.sh /system/etc
busybox cp /sdcard/init-sd.sh /system/etc
busybox chmod 755 /system/etc/install-recovery.sh
busybox chmod 755 /system/etc/init-sd.sh
# un Hash whatis needed if you intend NOT to remove SD
#cd /data/app
#busybox rm -rf *
#cd /data/app-private
#busybox rm -rf *
#cd /data/data/
#busybox rm -rf *
#cd /data/dalvik-cache
#busybox rm -rf *
# binding mount of new file structure
mount -o bind /system/sd/app /data/app
mount -o bind /system/sd/app-private /data/app-private
# mount -o bind /system/sd/data /data/data
mount -o bind /system/sd/dalvik-cache /data/dalvik-cache
reboot
File 2 "init-sd.sh"
#!/system/bin/sh
#
MYLOG=/sdcard/install-recovery.log
echo "$(date) Starting install-recovery.sh" > $MYLOG
echo "$(date) Waiting SD to become ready..." >> $MYLOG
sleep 10
# un Hash whatis needed if you intend NOT to remove SD
#echo "$(date) Erasing system files..." >> $MYLOG
#cd /data/app
#busybox rm -rf *
#cd /data/app-private
#busybox rm -rf *
#cd /data/data/
#busybox rm -rf *
#cd /data/dalvik-cache
#busybox rm -rf *
#echo "$(date) Erased system files..." >> $MYLOG
mount -t ext2 /dev/block/vold/179:2 /system/sd 1>>$MYLOG 2>>$MYLOG
mount -o bind /system/sd/app /data/app 1>>$MYLOG 2>>$MYLOG
mount -o bind /system/sd/app-private /data/app-private 1>>$MYLOG 2>>$MYLOG
# Hash this out if you haven't moved /data/data
#mount -o bind /system/sd/data /data/data 1>>$MYLOG 2>>$MYLOG
# Hash this out if you haven't move /data/dalvik-cache
mount -o bind /system/sd/dalvik-cache /data/dalvik-cache 1>>$MYLOG 2>>$MYLOG
mount >> $MYLOG
echo "$(date) Finishing install-recovery.sh" >> $MYLOG
File 3 "install-recovery.sh"
#!/system/bin/sh
#
/system/etc/init-sd.sh&
And BOB's your uncle.. this has worked many times for me give it a try
Perform a system dump and share the ICS love.
1 root your phone [guide in dev section]
2 install busybox [app on market to do it for you]
3 enter these commands from terminal
Code:
su
cd /sdcard
mount -o rw,remount -t ext4 /dev/block/mmcblk1p21 /system
chmod 777 /system/xbin/busybox
/system/xbin/busybox tar czvf dump.tar /system
I will donate 9 dollars to first person posting a working dump
Can't wait, come on some kind skyrocket soul share the wealth to our beloved t989.
Sent from my SGH-T989 using Tapatalk
Yes please! This would be very helpful!
About to start the dump, hold on guys.
Unable to chmod /system/xbin/busybox: No such file or directory
10|[email protected]:/sdcard # chmod 777 /system/xbin/busybox
thats what im getting with the commands
cdshepherd said:
Unable to chmod /system/xbin/busybox: No such file or directory
10|[email protected]:/sdcard # chmod 777 /system/xbin/busybox
thats what im getting with the commands
Click to expand...
Click to collapse
is busybox installed?
try
chmod 777 /system/bin/busybox
starskyrob said:
is busybox installed?
try
chmod 777 /system/bin/busybox
Click to expand...
Click to collapse
[email protected]:/sdcard # chmod 777 /system/xbin/busybox
Unable to chmod /system/xbin/busybox: Read-only file system
thats with busy box installed
cdshepherd said:
[email protected]:/sdcard # chmod 777 /system/xbin/busybox
Unable to chmod /system/xbin/busybox: Read-only file system
thats with busy box installed
Click to expand...
Click to collapse
ok so before you chmod,
type this
mount -o rw,remount -t ext4 /dev/block/mmcblk1p21 /system
and btw, thank you. so so much
starskyrob said:
ok so before you chmod,
type this
mount -o rw,remount -t ext4 /dev/block/mmcblk1p21 /system
and btw, thank you. so so much
Click to expand...
Click to collapse
I'm doing the same thing, so whoever dumps first dumps first.
starskyrob said:
is busybox installed?
try
chmod 777 /system/bin/busybox
Click to expand...
Click to collapse
wouldnt he need su to be able to chmod a system file?
starskyrob said:
ok so before you chmod,
type this
mount -o rw,remount -t ext4 /dev/block/mmcblk1p21 /system
and btw, thank you. so so much
Click to expand...
Click to collapse
your welcome.
1|[email protected]:/mnt/sdcard # /system/bin/busybox tar czvf dump.tar /system
sh: /system/bin/busybox: not found
127|[email protected]:/mnt/sdcard #
strange
I can get past everything, but when I type the command to start the dump, this happens.
/system/xbin/busybox tar czvf dump.tar /system
tar: invalid option -- z
Longcat14 said:
I can get past everything, but when I type the command to start the dump, this happens.
/system/xbin/busybox tar czvf dump.tar /system
tar: invalid option -- z
Click to expand...
Click to collapse
same here
127|[email protected]:/sdcard # /system/xbin/busybox tar czvf dump.tar /system
tar: invalid option -- z
BusyBox v1.19.4-Stericson (2012-02-20 19:30:32 CST) multi-call binary.
Usage: tar -[cxtZhmvO] [-X FILE] [-T FILE] [-f TARFILE] [-C DIR] [FILE]...
I used the xUltimate-v2.3.3 to make deodex.
Then it comes to two folders "done_app" & "done_frame"
I copy the two folders into my sdcard, and I want to use adb shell to push & replace
files to system/app /frams
down are my situation.
===========================
C:\android-sdk-windows\tools>adb shell
[email protected]:/$ su
su
[email protected]:/# stop
.................................then it stop...I can't do anything
===========================
down are the sample code from internet
============================
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
=====================================
Can you help me ?
I did wrong on what step....
My OS system is windows7 x64 in command line.
dickluo said:
i used the xultimate-v2.3.3 to make deodex.
Then it comes to two folders "done_app" & "done_frame"
i copy the two folders into my sdcard, and i want to use adb shell to push & replace
files to system/app /frams
down are my situation.
===========================
c:\android-sdk-windows\tools>adb shell
[email protected]:/$ su
su
[email protected]:/# stop
.................................then it stop...i can't do anything
===========================
down are the sample code from internet
============================
adb shell
su
stop
mount -o rw,remount -t ext3 /dev/block/mmcblk1p21 /system
cp /sdcard/done_app/* /system/app/
cp /sdcard/done_frame/* /system/framework/
rm /system/app/*.odex
rm /system/framework/*.odex
mount -o ro,remount -t ext3 /dev/block/mmcblk1p21 /system
reboot
=====================================
can you help me ?
I did wrong on what step....
My os system is windows7 x64 in command line.
Click to expand...
Click to collapse
記得右鍵點擊cmd圖標,選擇 以管理員身份運行。 看看你是不是忘記了這一步~
No use about that.
Maybe I'll try it on winxp system.
Sent from my ME865 using xda premium
I have a rooted HTC and need to create a custom file in /system/xbin. I execute a mount command (for read-write permission on /system), create the file, remount /system in readonly and after that my file magically disappear. Here are the commands I wrote in a su shell via adb.
Code:
[email protected]:/system/xbin # mount | grep system
/dev/block/mmcblk0p35 /system ext4 ro,seclabel,relatime,data=ordered 0 0
[email protected]:/system/xbin # mount -o rw,remount /dev/block/mmcblk0p35 /system
[email protected]:/system/xbin # cd /system/xbin
[email protected]:/system/xbin # echo test > myfile
[email protected]:/system/xbin # ls
daemonsu
dexdump
dexus
myfile <- 'myfile' is created
nc
su
[email protected]:/system/xbin # cat myfile
test
[email protected]:/system/xbin # mount -o ro,remount /dev/block/mmcblk0p35 /system
[email protected]:/system/xbin # ls
daemonsu
dexdump
dexus
nc
su
PUFF after remounted /system in readonly my file is disappeared. Any idea about this?
NOTE: If I try to re-execute the commands, my HTC restarts itself ... EDIT 2: As you could see in the 'ls' command output, in /system/xbin exist 'su' installed with a root tool. How could this root tool install 'su' permanently?
Trying to deodex my apks, they're deodexed but I can't push them into the /system/app folder
Code:
C:\Users\Terrence\AppData\Local\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
[email protected]:/ # exit
exit
[email protected]:/ $ exit
exit
C:\Users\Terrence\AppData\Local\Android\android-sdk\platform-tools>adb push C:\U
sers\Terrence\deodexed_apps /system/app/
push: C:\Users\Terrence\deodexed_apps/YahoostockWidget.apk -> /system/app/Yahoos
tockWidget.apk
failed to copy 'C:\Users\Terrence\deodexed_apps/YahoostockWidget.apk' to '/syste
m/app/YahoostockWidget.apk': Permission denied
Phone is rooted according to RootChecker. No Knox or anything else like that. Android 4.1.