I got a new x10 from Best Buy Mobile as a loaner phone, running 1.6 on AT&T fresh out of the box. followed the ATT thread to go to 2.1 using flash tool.
I have tried nearly everything to root it, flash tool tells me phone should be rooted after reboot, it isnt, X10root.apk fails, superoneclick fails (maybe adb related & not sure why.. had adb path set up properly and shows device id, but says protocol error?), z4root doesnt even get temp root.
Im on generic 2.1 x10a , this wall all done on my win 7 64 bit laptop. I will try via adb on my computer at work running win xp later today, but the root .apks should have rooted, I dont understand why.
I will post a log for you guys to check out, Im not a n00b, but not an expert either.
I may have the phone for a week or a month, while my other LCD is repaired.
Thanks everyone!
Go for root !
Version: Universal Androot - v1.6.2 beta 5
Detected OS version:7
ls -l /system/etc
-rw-r--r-- root root 461 2011-01-07 06:11 pvextensions.cfg
-rw-r--r-- root root 418 2011-01-07 06:11 iddd.conf
-rw-r--r-- root root 684 2011-01-07 06:11 wiperconfig.xml
-rw-r--r-- root root 1853914 2010-12-15 20:46 dop.iso
drwxr-xr-x root root 2011-01-26 05:16 wifi
-rw-r--r-- root root 1358 2011-01-07 06:11 hw_config.sh
drwxr-xr-x root root 2011-01-26 05:16 firmware
-rw-r--r-- root root 2046 2011-01-07 06:11 bookmarks.xml
drwxr-xr-x root root 2011-01-26 05:16 ppp
-rw-r--r-- root root 8319 2011-01-07 06:11 event-log-tags
-r-xr-x--- root shell 1176 2011-01-07 06:11 init.goldfish.sh
-rw-r--r-- root root 85623 2011-01-07 06:11 NOTICE.html.gz
-rw-r--r-- root root 438 2010-10-08 04:40 apns-conf.xml
-rw-r--r-- root root 8858 2010-11-30 20:14 default-capability.xml
drwxr-xr-x root root 2011-01-26 05:16 semc
-rw-r--r-- root root 197 2011-01-07 06:11 pvasfstreaming.cfg
drwxr-xr-x root root 2011-01-26 05:16 dhcpcd
-rw-r--r-- root root 3396 2011-01-07 06:11 init.es209ra.bt.sh
-rw-r--r-- root root 2 2011-01-07 06:11 DualMicControl.txt
-rw-r--r-- root root 177 2011-01-07 06:11 pvasflocal.cfg
drwxr-xr-x root root 2011-01-26 05:16 security
-r--r----- bluetooth bluetooth 935 2011-01-07 06:11 dbus.conf
drwxr-xr-x root root 2011-01-26 05:16 customization
drwxr-xr-x root root 2011-01-26 05:16 permissions
-rw-r--r-- root root 935 2011-01-07 06:11 gps.conf
-rw-r--r-- root root 458 2011-01-07 06:11 pvplayer.cfg
drwxr-xr-x root root 2011-01-26 05:16 bluez
-rw-r--r-- root root 85 2011-01-07 06:11 01_qcomm_omx.cfg
-rw-r--r-- root root 1462 2011-01-07 06:11 vold.conf
-rw-r--r-- root root 285 2011-01-07 06:11 sensors.conf
-rw-r--r-- root root 25 2011-01-07 06:11 hosts
-rw-r--r-- root root 1804 2011-01-07 06:11 loc_parameter.ini
ls -l /system/bin/reboot
lrwxr-xr-x root shell 2011-01-26 05:17 reboot -> toolbox
cat /proc/sys/kernel/osrelease
2.6.29
getprop ro.product.model
X10a
getprop ro.product.brand
SEMC
getprop ro.product.name
X10a_1234-4820
getprop ro.product.manufacturer
Sony Ericsson
getprop ro.build.product
X10a
ls -l /sqlite_stmt_journals
-rw------- app_96 app_96 1 2011-05-02 08:41 persist.service.adb.enable
-rw------- app_96 app_96 158741 2011-05-02 08:41 Superuser.apk
-rw------- app_96 app_96 26256 2011-05-02 08:41 su
-rw------- app_96 app_96 1001388 2011-05-02 08:41 busybox
-rwxr-xr-x app_96 app_96 19114 2011-05-02 08:40 exploid
lrwxrwxrwx app_96 app_96 2011-05-01 23:35 data -> /proc/sys/kernel/hotplug
-rw-r--r-- app_96 app_96 29 2011-05-02 08:41 hotplug
-rw-rw-rw- app_96 app_96 0 2011-05-02 08:41 loading
-rw------- app_96 app_96 164788 2011-05-01 23:30 com.noshufou.android.su.apk
ls -l /data/local/tmp
opendir failed, Permission denied
ls -l /app-cache
/app-cache: No such file or directory
run mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock2 /system yaffs2 ro 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,user_id=0,group_id=0,allow_other 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
run df
/dev: 143500K total, 12K used, 143488K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 1388K used, 2708K available (block size 4096)
/system: 361088K total, 248980K used, 112108K available (block size 4096)
/data: 476160K total, 96052K used, 380108K available (block size 4096)
/cache: 113920K total, 3316K used, 110604K available (block size 4096)
/sdcard: 1913216K total, 368864K used, 1544352K available (block size 16384)
/data/DxDrm/fuse: Permission denied
Preparing Exploit ... :true
Preparing busybox binary ... :true
User selected: Eclair
Preparing Su binary ... :true
Preparing Superuser apk ... :true, resid:2131034118
Preparing root toolkit script ... :true
Trying to get mount point:/data
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0
Trying to get mount point:/system
/dev/block/mtdblock2 /system yaffs2 ro 0 0
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
mkdir /system/xbin
cat su > /system/xbin/su
chmod 04755 /system/xbin/su
ln -s /system/xbin/su /system/bin/su
mount -o remount,ro -t yaffs2 /dev/block/mtdblock2 /system
mount -o remount,rw,nosuid,nodev -t yaffs2 /dev/block/mtdblock3 /data
mount -o remount,rw -t yaffs2 /dev/block/mtdblock2 /system
rm /system/bin/su
rm /system/xbin/su
Preparing to execute exploit, do chmod
Executing exploit..
cmd: /data/data/com.corner23.android.universalandroot/files/getroot /dev/block/mtdblock3 yaffs2
[*] Android local root exploid (C) The Android Exploid Crew
[*] Modified by shakalaca for various devices
[+] Using basedir=/sqlite_stmt_journals, path=/data/data/com.corner23.android.universalandroot/files/getroot
[+] opening NETLINK_KOBJECT_UEVENT socket
[-] creat: Permission denied
Wifi enabled ...
/sqlite_stmt_journals/rootshell missing ..
/app-cache/rootshell missing ..
/data/local/tmp/rootshell missing ..
Install/Uninstall rootkit: false
ls -l /sqlite_stmt_journals
-rw------- app_96 app_96 1 2011-05-02 08:41 persist.service.adb.enable
-rw------- app_96 app_96 158741 2011-05-02 08:41 Superuser.apk
-rw------- app_96 app_96 26256 2011-05-02 08:41 su
-rw------- app_96 app_96 1001388 2011-05-02 08:41 busybox
-rwxr-xr-x app_96 app_96 19114 2011-05-02 08:40 exploid
lrwxrwxrwx app_96 app_96 2011-05-01 23:35 data -> /proc/sys/kernel/hotplug
-rw-r--r-- app_96 app_96 29 2011-05-02 08:41 hotplug
-rw-rw-rw- app_96 app_96 0 2011-05-02 08:41 loading
-rw------- app_96 app_96 164788 2011-05-01 23:30 com.noshufou.android.su.apk
ls -l /data/local/tmp
opendir failed, Permission denied
ls -l /app-cache
/app-cache: No such file or directory
run mount
rootfs / rootfs ro 0 0
tmpfs /dev tmpfs rw,mode=755 0 0
devpts /dev/pts devpts rw,mode=600 0 0
proc /proc proc rw 0 0
sysfs /sys sysfs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
/dev/block/mtdblock2 /system yaffs2 ro 0 0
/dev/block/mtdblock3 /data yaffs2 rw,nosuid,nodev 0 0
/dev/block/mtdblock1 /cache yaffs2 rw,nosuid,nodev 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,user_id=0,group_id=0,allow_other 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
run df
/dev: 143500K total, 12K used, 143488K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 1388K used, 2708K available (block size 4096)
/system: 361088K total, 248980K used, 112108K available (block size 4096)
/data: 476160K total, 96044K used, 380116K available (block size 4096)
/cache: 113920K total, 3316K used, 110604K available (block size 4096)
/sdcard: 1913216K total, 368864K used, 1544352K available (block size 16384)
/data/DxDrm/fuse: Permission denied
I just want to flash a gingerbread ROM of course, but I will need xrecovery right? which isnt installing without root.
Unless its possible for me to flash a new rooted rom without xrecovery, I uppose that will work although it might be dangerous.
I'll post back as soon as I can.
use the latest version of superoneclick and make sure you have USB debugging enabled
if you have rooted with flash tool you do not need to do anything else it will be rooted you dont need x10root or other one click apk apps as flash tool rooted your phone
test it with a tool that requires root such as adfree or terminal emulator
flash tool says success with root, but its not rooted, as i cant install busybox, says not rooted and entering su in terminal says permission denied
please help!
chrisrotolo said:
flash tool says success with root, but its not rooted, as i cant install busybox, says not rooted and entering su in terminal says permission denied
please help!
Click to expand...
Click to collapse
try using SuperOneClick here
failing that use SuperOneClickv1.5.5 here
i already tried the newest SOC, no dice.
ill try the older one too.
I think it may have to do with the drivers, it looks like regular drivers dont work, Im installing the SE developer ones.
but that doesnt really explain why z4root didnt work, and universal androot fails too.
thanks guys. this is killing me.
chrisrotolo said:
i already tried the newest SOC, no dice.
ill try the older one too.
I think it may have to do with the drivers, it looks like regular drivers dont work, Im installing the SE developer ones.
but that doesnt really explain why z4root didnt work, and universal androot fails too.
thanks guys. this is killing me.
Click to expand...
Click to collapse
what firmware are you using on your phone(under about phone) !?
and try the 1.5.5 version make sure when you run it you have USB debugging enabled! (under settings /applications/development ) you may also want to make sure you have UNKNOWN SOURCES checked!
z4 and universal will no longer work after the first version of 2.1! so dont bother with those!
you could also try the root tool that comes with the lastest flashtool
make sure when you root you choose 'connect phone' and not mount for usb storage mode!
2.1-update 1
build 2.1.a.0.435
2.6.29 [email protected] #1
x10a
this is beginning to p1ss me off, I think it must be a driver/adb issue, i did the fix for 64 bit, and now Im on xp and still cant connect to daemon when i say adb devices in cmd. I have the latests drivers, maybe i need to install older ones, maybe these have security?
also what are the signfiles.bat ,etc on my sdcard, they look SE signing tools , like they verify signature, etc.
also tried downloading the new rooting method for 2.1, rootme.tar, but server is unavailable.
yahhhhh! this is nuts!
adb kill-server and start-server work, so I know my adb is ok, I have android sdk installed. path>adb devices **daemon still not runningerror: cannot connect to daemon, so it has to be the phone or the drivers Im guessing. arrghhh!
i have tried different usb ports, still nothing!
Best way to root, install Xrecovery and JIT enable your phone is via Flash Tool. I'm on AT&T too, and found it rather simple.
Follow the guide found here:
http://forum.xda-developers.com/showthread.php?t=1012380
Make sure you have installed java on your computer.
Also, do not mount your SD card. While your phone is on, connect your phone via usb and hit root once your phone is recognized.
I'm not sure if this is necessary for rooting but for flashing purposes you need to connect your phone via pc companion or SEUS. Check to see if you have the latest firmware and set your phone up to flash new firmware. The computer will install flash drivers onto your computer. You don't have to install the latest AT&T firmware if there is one. You just want to have those flash drivers on your PC.
Hope this helps!
ok, so i was trying to follow the AT&T giude from 1.6 -2.1, which says update then root, should I go back to 1.6 and try universalandroot or z4root, root first, then update? or will I lose root when I update? Thanks guys.
installed PC companion update my driver, but still no adb devices cannot connect to daemon, and SOC 1.5.5 failed
I installed SEUS on my other PC too, didnt seem to change much, drivers were the same.
this is crazy, what should i do guys? use pc companion to repair? go back to 1.6 and try rooting then update??
Just use flash tool and press root if you just want to root. You don't have to sideload any apps which is blocked by AT&T anyways.
Update to 2.1 in order to install xrecovery. Once done updating, root it afterwards by pressing the root button on flash tool. No need to go back to 1.6 just to root. Just follow the guide and then you can install any rom you want. The Agent got your back.
Ok, so I re-read your thread. Let me summarize what I know.
1. Flash tool says you have root after your phone rebooted
2. You can not install busybox via flash tool
It might be that your phone is already rooted. If you tried to install busybox or xrecovery through flash tool and have seen that the advanced options are greyed out, it is because you need to press "ask root permissions" and then accept on your phone.
Also check to see if superuser is working correctly, Install Titanium backup to check. Install it from the marketplace open it up. A box should pop up saying "Allow Root Access"?
If so, then you have done it correctly.
I'm not keen with all the coding so I don't know how to read those logs you have noted.
Try pressing root again on flash tool and let it reboot, let me know what you see afterwards.
TYhanks for the help , I appreciate it guys.
im at my home laptop with win7 64 bit and adb devices shows serial number connected. adb push gives me cannot connect to daemon error, and super one click fails. I have busybox and superuser .apks installed from astro but both not "fully" installed without root. I know how to check for root, and I do not have it even when flashtool tells me I should. Really strange. what is going on??
ok, didnt want to do it, but im going to try the old way, with the 3 .bat files, is this a good idea? wish me luck! (if i can find clearer instructions)
cant go to sony ericsson unlock bootlloader online with IMEI, becuase its a loaner and says invalid IMEI... *double facepalm*!
I had those same issues with my 64bit windows 7 too. I think it has to do with Java and how adb tools works better with 32 bit. Troubleshooting your computer and phone might be the way to go.
Make sure on your phone you have usb debugging clicked via Settings>applications>Development. Also, just for the hell of it, click unknown sources.
Make sure on your computer, UAC/User Access Controls is turned off. If you recently installed java, reboot your computer.
After reboot, restart cmd and get into your adb folder. Type adb devices. Should show if you have your phone connected/computer recognizes your phone.
chrisrotolo said:
TYhanks for the help , I appreciate it guys.
im at my home laptop with win7 64 bit and adb devices shows serial number connected. adb push gives me cannot connect to daemon error, and super one click fails. I have busybox and superuser .apks installed from astro but both not "fully" installed without root. I know how to check for root, and I do not have it even when flashtool tells me I should. Really strange. what is going on??
ok, didnt want to do it, but im going to try the old way, with the 3 .bat files, is this a good idea? wish me luck!
Click to expand...
Click to collapse
Start over with new download of Flash Tool and 2.1.A.0.435 ftf firmware.
this is terrible!
will try to reflash the 2.1 update again.
relashed fine, without rebooting, ran Root option from flashtool, says should be rooted after reboot, havent rebooted yet, but definetly no root.
F%ck! after flash tool finishes and reboot still zilch! I dont think flashtool is installing superuser, here's a log, man this is awful!
02/022/2011 20:22:40 - INFO - <- This level is successfully initialized
02/022/2011 20:22:54 - ERROR - Cannot identify your device. Found while expecting X10, E10, U20 or E15 (read from ro.product.model from build.prop)
02/022/2011 20:22:54 - INFO - Selecting from user input
02/023/2011 20:23:17 - INFO - Connected device : X10
02/023/2011 20:23:23 - INFO - Installed version of busybox : * daemon not running. starting it now on port 5037 *
02/023/2011 20:23:29 - INFO - Pushing .\custom\root\busyboxX10 to /data/local/tmp/busybox
02/023/2011 20:23:40 - INFO - Running busyhelper
02/023/2011 20:23:45 - INFO - Pushing .\custom\root\givmeroot.tar to /data/local/tmp/
02/023/2011 20:23:51 - INFO - Running part1 of Root Exploit, please wait
02/023/2011 20:23:55 - INFO - Running rootit
02/024/2011 20:24:07 - INFO - Running part2 of Root Exploit
02/024/2011 20:24:08 - INFO - Running rootit2
02/024/2011 20:24:10 - INFO - Finished!.
02/024/2011 20:24:10 - INFO - Root should be available after reboot!
02/025/2011 20:25:06 - ERROR - Cannot identify your device. Found while expecting X10, E10, U20 or E15 (read from ro.product.model from build.prop)
02/025/2011 20:25:06 - INFO - Selecting from user input
02/025/2011 20:25:10 - INFO - Connected device : X10
02/025/2011 20:25:10 - INFO - Installed version of busybox : /system/bin/busybox: not found
strange.. now i cant seem to get adb devices, with the latest drivers, to show anything.. cant connect to daemon... give me a break.
24 hour bump! hopeless
Hate to say it, but it sounds like a isolated issue. Thousands of people used the flash tool and superoneclick successfully. Are you sure you selected the next tab, "root permissions" after root? You need to do that to install SuperUser and Busybox.
Also, antivirus should be disabled.
Problem fixed !!! Thansk!
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??
would thing you get the $ prompt if you open the adb shell
enter "su" - the prompt should change to #
then the remount command should succeed
enter "su" - the prompt should change to # in shell mode
then type : # adb remount ?
could you get me a detail command set ?. because kindle fire is my first's android device , BIG THANKS!
this should be the way it works:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
#
the bold commands are the ones to enter ...
My file is saved in c:\apps\hk.cedime.inputmethod.apk
and also have a copy in c:\adb\hk.cedime.inputmethod.apk
Show many error ??? Any expert can help?
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# install c:\apps\hk.cedime.inputmethod.apk /system/app/
install c:\apps\hk.cedime.inputmethod.apk /system/app/
install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
# install hk.cedime.inputmethod.apk /system/app/
install hk.cedime.inputmethod.apk /system/app/
install: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp hk.cedime.inputmethod.apk /system/app/
cp hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' hk.cedime.inputmethod.apk' : No such file or directory
#cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp c:\apps\hk.cedime.inputmethod.apk /system/app/
cp: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
install: can't stat ' c:appshk.cedime.inputmethod.apk' : No such file or directory
Click to expand...
Click to collapse
it don't find the .apk file
i use to put the files to install in the directory where adb.exe resides
and do the command without a path ie: install hk.cedime.inputmethod.apk /system/app/
furthermore i'm not shure if the command works inside the adb shell
would also try (from command prompt):
adb install c:\apps\hk.cedime.inputmethod.apk /system/app/
or if .apk in current directory (where adb resides):
adb install hk.cedime.inputmethod.apk /system/app/
Adb command is my first choice
But the system show the error : can't find '/system/app/' to install
then it seems not to be mounted ...
try to check with:
"adb shell"
"su"
"mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system"
"cd \system"
"ls -l" -> any directory listing here ?
"cd app"
"ls -l" -> any apk's listed ?
OH! my God!
c:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
mount -o remount, rw -t yaffs2/dev/block/mtdblock3/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
#
no problem - if it's not mounted it's hard to remount
would try:
"mount /system" in adb shell
or
"adb shell mount -o remount rw /system" from the command prompt
Sorry, many problem can't fix...............
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>
c:\ADB>adb shell mount -o remount rw/system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
c:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# ls -l
ls -l
dr-x------ root root 2012-03-19 05:51 config
drwxrwx--- system system 2012-03-20 07:00 dropbox
drwxrwx--- system cache 2012-03-19 05:51 cache
lrwxrwxrwx root root 2012-03-19 05:51 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-03-19 05:51 acct
drwxrwxr-x root system 2012-03-19 05:51 mnt
lrwxrwxrwx root root 2012-03-19 05:51 vendor -> /system/vendor
lrwxrwxrwx root root 2012-03-19 05:51 d -> /sys/kernel/debug
lrwxrwxrwx root root 2012-03-19 05:51 etc -> /system/etc
-rw-r--r-- root root 4203 1969-12-31 16:00 ueventd.rc
-rw-r--r-- root root 840 1969-12-31 16:00 ueventd.omap4430.rc
-rw-r--r-- root root 0 1969-12-31 16:00 ueventd.goldfish.rc
drwxr-xr-x root root 2012-01-19 04:27 system
drwxr-xr-x root root 2012-03-19 05:51 sys
drwxr-x--- root root 1969-12-31 16:00 sbin
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rwxr-x--- root root 14869 1969-12-31 16:00 init.rc
-rwxr-x--- root root 11357 1969-12-31 16:00 init.omap4430.rc
-rwxr-x--- root root 1677 1969-12-31 16:00 init.goldfish.rc
-rwxr-x--- root root 94200 1969-12-31 16:00 init
-rw-r--r-- root root 118 1969-12-31 16:00 default.prop
drwxrwx--x system system 2012-03-18 06:53 data
drwx------ root root 2012-01-09 22:20 root
drwxr-xr-x root root 2012-03-19 06:01 dev
# cd app
cd app
cd: can't cd to app
#
from your post #5:
adb shell
$ su
su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
this has seemed to work - or was there allways a error message following up which you did'nt copy and paste ?
usually "mount /system" is sufficient - "mount -w /system" should work too
# cd app
cd app
cd: can't cd to app
Click to expand...
Click to collapse
if you look to the directory listing you are on the root - there is no directory or mountpoint "app" - it is in the system directory - the command should be:
"cd \system"
"ls -l" -> any directory listing here ?
and then if you are in "system"
"cd app"
"ls -l" -> any apk's listed ?
as in post #8
Expert ! Next step what can i do?
C:\ADB>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
6C18000600000001 device
C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
# cd \system
cd \system
# ls -l
ls -l
drwxr-xr-x root root 1969-12-31 16:00 lost+found
drwxr-xr-x root root 2012-03-19 05:49 app
drwxr-xr-x root shell 2012-03-17 18:19 bin
-rw-r--r-- root root 2151 2008-08-01 05:00 build.prop
drwxr-xr-x root root 2012-01-19 04:27 etc
drwxr-xr-x root root 2012-01-19 04:27 fonts
drwxr-xr-x root root 2012-01-19 04:27 framework
drwxr-xr-x root root 2012-01-19 04:27 lib
drwxr-xr-x root root 2012-01-19 04:27 media
drwxr-xr-x root root 2012-01-19 04:27 tts
drwxr-xr-x root root 2012-01-19 04:27 usr
drwxr-xr-x root shell 2012-01-19 04:27 vendor
drwxr-xr-x root shell 2012-03-17 20:51 xbin
# cd app
cd app
# ls -l
ls -l
-rw-r--r-- root root 2669573 2008-08-01 05:00 ATVAndroidClient.apk
-rw-r--r-- root root 233689 2008-08-01 05:00 AccountAndSyncSettings.ap
k
-rw-r--r-- root root 3581879 2008-08-01 05:00 AmazonVenezia.apk
-rw-r--r-- root root 29574 2008-08-01 05:00 ApplicationsProvider.apk
-rw-r--r-- root root 3574986 2008-08-01 05:00 AudibleAndroidApplication
-venezia.apk
-rw-r--r-- root root 164188 2008-08-01 05:00 CSApp-unsigned.apk
-rw-r--r-- root root 152004 2008-08-01 05:00 CalendarProvider.apk
-rw-r--r-- root root 116225 2008-08-01 05:00 CertInstaller.apk
-rw-r--r-- root root 4019454 2008-08-01 05:00 Cloud9-release-unsigned.a
pk
-rw-r--r-- root root 57208 2008-08-01 05:00 Cloud9SystemBrowserProvid
er-unsigned.apk
-rw-r--r-- root root 2049942 2008-08-01 05:00 Contacts.apk
-rw-r--r-- root root 145545 2008-08-01 05:00 ContactsProvider.apk
-rw-r--r-- root root 20748 2008-08-01 05:00 DefaultContainerService.a
pk
-rw-r--r-- root root 196150 2008-08-01 05:00 DownloadProvider.apk
-rw-r--r-- root root 106749 2008-08-01 05:00 DownloadProviderUi.apk
-rw-r--r-- root root 32432 2008-08-01 05:00 DrmProvider.apk
-rw-r--r-- root root 2315338 2008-08-01 05:00 Email.apk
-rw-r--r-- root root 16892 2008-08-01 05:00 Facebook.apk
-rw-r--r-- root root 833544 2008-08-01 05:00 Gallery3D.apk
-rw-r--r-- root root 22792 2008-08-01 05:00 HTMLViewer.apk
-rw-r--r-- root root 1685594 2008-08-01 05:00 IMDb-2.3.apk
-rw-r--r-- root root 16424244 2008-08-01 05:00 KindleForOtter.apk
-rw-r--r-- root root 1082002 2008-08-01 05:00 LatinIME.apk
-rw-r--r-- root root 12174497 2008-08-01 05:00 Launcher.apk
-rw-r--r-- root root 1140587 2008-08-01 05:00 LiveWallpapers.apk
-rw-r--r-- root root 51276 2008-08-01 05:00 LiveWallpapersPicker.apk
-rw-r--r-- root root 224152 2008-08-01 05:00 MagicSmokeWallpapers.apk
-rw-r--r-- root root 20778 2008-08-01 05:00 MarketIntentProxy.apk
-rw-r--r-- root root 62533 2008-08-01 05:00 MediaProvider.apk
-rw-r--r-- root root 149119 2008-08-01 05:00 MyAccount-unsigned.apk
-rw-r--r-- root root 253116 2008-08-01 05:00 OOBE-unsigned.apk
-rw-r--r-- root root 26983 2008-08-01 05:00 OTASilentInstall.apk
-rw-r--r-- root root 110563 2008-08-01 05:00 OtterAppManager.apk
-rw-r--r-- root root 1907710 2008-08-01 05:00 OtterTutorial.apk
-rw-r--r-- root root 122758 2008-08-01 05:00 PackageInstaller.apk
-rw-r--r-- root root 22282 2008-08-01 05:00 PicoTts.apk
-rw-r--r-- root root 10496 2008-08-01 05:00 Provision.apk
-rw-r--r-- root root 2305323 2008-08-01 05:00 Pulse-amazon.apk
-rw-r--r-- root root 412698 2008-08-01 05:00 QuickSearchBox.apk
-rw-r--r-- root root 320688 2008-08-01 05:00 QuickSettings.apk
-rw-r--r-- root root 6302776 2008-08-01 05:00 Quickoffice_AMAZON_4.1.46
7_VC.apk
-rw-r--r-- root root 3751962 2008-08-01 05:00 Settings.apk
-rw-r--r-- root root 48682 2008-08-01 05:00 SettingsProvider.apk
-rw-r--r-- root root 604484 2008-08-01 05:00 SystemUI.apk
-rw-r--r-- root root 30187 2008-08-01 05:00 TtsService.apk
-rw-r--r-- root root 16928 2008-08-01 05:00 UserDictionaryProvider.ap
k
-rw-r--r-- root root 165579 2008-08-01 05:00 VisualizationWallpapers.a
pk
-rw-r--r-- root root 34247 2008-08-01 05:00 VpnServices.apk
-rw-r--r-- root root 1669753 2008-08-01 05:00 Windowshop.apk
-rw-r--r-- root root 6113490 2008-08-01 05:00 air_runtime.apk
-rw-r--r-- root root 2109670 2008-08-01 05:00 amazonmp3-unsigned.apk
-rw-r--r-- root root 2500819 2008-08-01 05:00 com.amazon.dcp.apk
-rw-r--r-- root root 45888 2008-08-01 05:00 oem_install_flash_player_
signed.apk
-rw-r--r-- root root 843503 2008-02-28 10:33 Superuser.apk
-rw-rw-rw- root root 89707 2011-12-07 02:26 GoogleFeedback.apk
-rw-rw-rw- root root 1401398 2011-12-07 02:13 GoogleServicesFramework.a
pk
-rw-rw-rw- root root 1529836 2011-12-07 02:15 Vending.apk
-rw-rw-rw- root root 4089926 2011-12-07 02:22 GO_Launcher_EX_2.65.apk
-rw-rw-rw- root root 2053065 2012-03-19 05:49 hk.cedime.inputmethod.apk
#
C:\ADB>adb shell mount -o remount rw /system
mount: Operation not permitted
Click to expand...
Click to collapse
as you run a unsecure kernel i think the command should be:
adb shell su -c "remount"
or
adb shell su -c "mount -o remount rw /system"
C:\ADB>adb shell
$ su
su
# mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount, rw -t yaffs2 /dev/block/mtdblock3 /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Click to expand...
Click to collapse
the second attempt succeeded - so your question seems to be answered or not ?
Any ONE can help?
My kindle fire already rooted, every time i want to install the input method by adb remount is fail.
remount failed: operation not permitted!
how can i fix it??
Click to expand...
Click to collapse
Expert!
i follow this link
http://forum.xda-developers.com/showthread.php?t=1364543
to fixed my problem, Thanks for your support again!!
glad to help ...
please mark the subject of the topic (edit first post) with [Solved]
Hi,
A little while back, my Z00T stopped booting (would bootloop shortly after the splash screen). Even with stock.
Looks like logcat line 187 is kicking my butt.
I can get in TWRP with no issue, so I have been tracking down the problem from there, and now suspect a corrupt /firmware partition (or a few files within).
Can a Z00T owner with the MM bootloader (preferably June 2nd 2016 update, can verify with first command below), go into TWRP, mount the firmware partition (under Mounts) and run the following two commands?:
Code:
~ # ls -l /firmware/image/keymaste.*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
-rwxrwxrwx 1 root root 180 Jun 2 2016 /firmware/image/keymaste.b00
-rwxrwxrwx 1 root root 6568 Jun 2 2016 /firmware/image/keymaste.b01
-rwxrwxrwx 1 root root 126672 Jun 2 2016 /firmware/image/keymaste.b02
-rwxrwxrwx 1 root root 8132 Jun 2 2016 /firmware/image/keymaste.b03
-rwxrwxrwx 1 root root 6748 Jun 2 2016 /firmware/image/keymaste.mdt
~ # md5sum /firmware/image/keymaste.*
ccaf75b641f15b9b8b33cefc836f29e0 /firmware/image/keymaste.b00
0a446b039708f600cebf1cba89865cd8 /firmware/image/keymaste.b01
8749be39e11338cf5a7998b57da4549c /firmware/image/keymaste.b02
f10be3e59e81f92243166b5e92fb4e47 /firmware/image/keymaste.b03
af9f26f61a4f12b82e99f028867174ea /firmware/image/keymaste.mdt
~ #
Please paste your results in a reply with the CODE tags for comparison (feel free to give me a mention or have a partial QUOTE in your reply).
Bonus points for (if you have the right date but a different hash)...
I will probably need a new firmware partition, and hope my internal SD is not dying.
If noone knows where I can find an official one, you can make one by first verifying the partition number (should be 41):
Code:
adb shell cat /proc/mounts | grep firmware
Then make an image copy to file with dd* to the external sd (using partition 41), download to PC:
Code:
adb shell dd if=/dev/block/mmcblk0p41 of=/sdcard1/firmware.img
adb pull /sdcard1/firmware.img
* Issue the command verbatim, or don't issue at all if not familiar with dd. If used incorrectly, dd can do some serious damage. Been there, done that, always check your work.
This will help me out in continuing to use this device for development purposes.
ZD551KL Selfi / Z00T. ROM CM13 for Z00T
Code:
C:\adb>adb shell ls -l /firmware/image/keymaste.*
-r--r--r-- root root 180 2016-08-05 04:59 keymaste
-r--r--r-- root root 6568 2016-08-05 04:59 keymaste
-r--r--r-- root root 126672 2016-08-05 04:59 keymaste
-r--r--r-- root root 8132 2016-08-05 04:59 keymaste
-r--r--r-- root root 6748 2016-08-05 04:59 keymaste
C:\adb>adb shell md5sum /firmware/image/keymaste.*
ccaf75b641f15b9b8b33cefc836f29e0 /firmware/image/keymaste.b00
0a446b039708f600cebf1cba89865cd8 /firmware/image/keymaste.b01
8749be39e11338cf5a7998b57da4549c /firmware/image/keymaste.b02
f10be3e59e81f92243166b5e92fb4e47 /firmware/image/keymaste.b03
af9f26f61a4f12b82e99f028867174ea /firmware/image/keymaste.mdt
Well then...that blows that out of the water - the hashes match even with a different model num and OTA date.
Unless the partition is only readable under certain circumstances (system boot not being one of them but TWRP seems more forgiving), then I will need a replacement ZE551KL firmware.img. If it is still something else, I will then be unsure how to proceed since this is a problem across multiple boot.img's so it's not a kernel or ramdisk issue yet still prevents /vendor from getting set up before /vendor symlinks to /system/vendor.
Here is md5sum of my z00t ze601kl
Code:
ccaf75b641f15b9b8b33cefc836f29e0 /firmware/image/keymaste.b00
0a446b039708f600cebf1cba89865cd8 /firmware/image/keymaste.b01
8749be39e11338cf5a7998b57da4549c /firmware/image/keymaste.b02
f10be3e59e81f92243166b5e92fb4e47 /firmware/image/keymaste.b03
af9f26f61a4f12b82e99f028867174ea /firmware/image/keymaste.mdt
Code:
-r--r--r-- system system 180 2016-08-03 00:38 keymaste.b00
-r--r--r-- system system 6568 2016-08-03 00:38 keymaste.b01
-r--r--r-- system system 126672 2016-08-03 00:38 keymaste.b02
-r--r--r-- system system 8132 2016-08-03 00:38 keymaste.b03
-r--r--r-- system system 6748 2016-08-03 00:38 keymaste.mdt
Hello,
I am trying to install USB host-mode on my rooted nook simple touch so that I can use a keyboard or a mouse as a page turner. I am running 1.2.1, and rooted the nook using nook manager https://forum.xda-developers.com/showthread.php?t=2040351. This completed successfully. Then I installed a terminal app (can't find the link but it's called jackpal.androidterm.apk, can attach if needed) by putting it on a micro sd card and installing the file using relaunch (a file explorer app that appeared after rooting). Then I followed the instructions on https://forum.xda-developers.com/wiki/BN_Nook_Simple_Touch/Replacing_boot_files writing
su
mount -o rw,remount rootfs /
mkdir /boot
mount -t vfat /dev/block/mmcblk0p1 /boot
into the terminal app. It asked for permissions after su, which I granted and the other lines produced no errors but also no outputs. Now I am trying to find the /boot partition to replace uImage, as per the instructions, but I can't find /boot. It appears nowhere in the file explorer, and under advanced functions, the nook lists the following disks/partitions: /rom, /system, /data, /cache, /sdcard, /media, but no /boot
Any ideas? Really unsure as to why it's not showing up, because the commands that are supposed to create it seemed to complete without issue.
p.s. I also checked show hidden files in folders in the advanced settings
I dunno. Your "File Explorer" may be leading you astray.
Just do an ls -l in terminal and check.
ls -l produces:
drwxrwx--- system system 1969-12-31 16:00 rom
drwxrwxrwt root root 2018-02-26 11:11 sqlite_stmt_journals
d---rwxr-x system sdcard_rw 1969 -12-31 16:00 sdcard
drwxrwxr-x system sdcard_rw 1969 -12-31 16:00 media
drwxrwx--- system cache 2018-02-15 11:23 cache
drwxrwxrwx root root 2018-02-26 11:11 tmp
lrwxrwxrwx root root 2018-02-26 11:11 etc -> /system/etc
-rw-r--r-- root root 118 2018-02-15 12:03 init.rc.orig
-rw-r--r-- root root 118 2018-02-15 12:19 default.prop.orig
drwxr-xr-x root root 2018-02-05 12:19 system
drwxr-xr-x root root 1969-12-31 16:00 sys
drwxr-x--- root root 2018-02-15 12:03 sbin
dr-xr-xr-x root root 1969-12-31 16:00 proc
-rwxr-x--- root root 1677 2018-02-15 12:03 init.goldfish.rc
-rwxr-x--- root root 128000 2018-02-15 12:03 init
-rwxr-x--- root root 324 2018-02-15 12:03 env.txt
drwxrwx--x system system 2018-02-15 11:24 data
-rw-r--r-- root root 118 2018-02-15 12:03 default.prop
-rwxr-x--- root root 19284 2018-02-15 12:03 init.rc
drwx------ root root 2012-12-07 14:34 root
drwxr-xr-x root root 2018-02-26 11:11 dev
Further, I tried to copy uImage into /boot using the terminal and it acted as if /boot didn't exist, so I'm pretty sure that it isn't there for some reason.
Thanks
Well, something you're doing isn't working.
The commands are correct.
Code:
su
Did this work? Do you get a # prompt? Type "id", does it say you're root?
Code:
mount -o rw,remount rootfs /
Ok, did it remount? Type "mount" and see if rootfs is actually "rw".
Code:
mkdir /boot
Apparently this didn't work because you should see an empty directory at least.
Code:
mount -t vfat /dev/block/mmcblk0p1 /boot
Apparently this didn't work.
Did this work? Do you get a # prompt? Type "id", does it say you're root?
su produces a # prompt, and id produces: uid=0(root) gid=0(root), so i think this part worked.
Ok, did it remount? Type "mount" and see if rootfs is actually "rw".
mount produces: rootfs / rootfs rw 0 0, and then a bunch of other stuff, so i think this worked too.
mkdir /boot
this produces nothing, just another # prompt, so this might be the problem
mount -t vfat /dev/block/mmcblk0p1 /boot
this also produces nothing, just another # prompt.
Any idea why mkdir /boot would fail?
Thanks for being so helpful!
Well, the mkdir should have created an empty directory.
You should be able to "ls -l /" it.
If not, you could mkdir and mount anywhere.
Code:
cd /data/local/tmp
mkdir mybooty
mount -t vfat /dev/block/mmcblk0p1 /data/local/tmp/mybooty
There's nothing special about the name "boot".
Okay,
That solved the problem. Thanks for all your help!