I've tried just about every automated/one click/whatever method for rooting my spiffy new Captivate, and they all failed for one reason or another. I finally got it to work using adb & the command line. Here's how I did it. Oh, and before someone asks "Why didn't you just use Windoze?", it's because all my computers run Linux so that's not an option.
STANDARD DISCLAIMER: If you root your phone, the ceiling will collapse on your head and your family will die. No one should ever follow these instructions. In fact, I should probably be banned for even posting them.
MY SETUP:
Ubuntu 11.04 (natty)
Samsung Captivate i897, stock, KB2
AT&T
1. Download SuperOneClick
http://forum.xda-developers.com/showthread.php?t=803682
I used 1.9.5, only because another poster told me he had successfully rooted his Captivate using that specific version. This may also work with the files from a newer version; I don't see why it wouldn't.
2. Extract everything
Duh.
3. Put adblinux, psneuter, busybox, su-v2, and Superuser.apk in one directory.
I don't know that it has to specifically be su-v2, but that one worked for me, so huzzah.
4. Put the phone in USB debug mode; plug it in to your computer.
Settings -> Applications -> Development (check the box for USB debugging). Linux users need no drivers.
5. Open a terminal, cd into wherever you extracted the SOC files.
6. Let's dance:
Code:
./adblinux push psneuter /data/local/tmp
./adblinux push su-v2 /data/local/tmp
./adblinux push busybox /data/local/tmp
./adblinux shell
$ cd /data/local/tmp
Make everything you just pushed over executable:
Code:
$ chmod 6755 psneuter
$ chmod 6755 su-v2
$ chmod 6755 busybox
Run the exploit:
Code:
$ /data/local/tmp/psneuter
Running psneuter successfully kicked me out of the shell, so go back. You should also notice when you re-enter the shell that your prompt has changed from "$" to "#", indicating psneuter was successful. This also means you have root privileges, at least temporarily, for the rest of your work.
Code:
./adblinux shell
# mount
"mount" should spit out something that looks like this:
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
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
/dev/block/stl9 /system rfs ro,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepa ge=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
Click to expand...
Click to collapse
On your phone, that output might look a little different, but you're looking for the line in BOLD. In the example above, "/dev/block/stl9" is the mount point for "/system". If "mount" gives you a different mount point, then use that in the commands below. The stuff after that tells you the properties of "/system"; "ro" is the one we're concerned with. That tells us that "/system" is mounted as "read-only". We need to change that so we can move some files over.
Code:
# mount -o remount,rw /dev/block/stl9 /system
"/system" is now writable. Let's move some files over.
Code:
# /data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin
# chmod 6755 /system/xbin/busybox
# /data/local/tmp/busybox chown 0.2000 /system/xbin/busybox
A functional copy of busybox now resides at /system/xbin, so from now on you can just call it with "busybox" instead of having to use the full path to the one we pushed over earlier.
Code:
# busybox mv /data/local/tmp/su-v2 /system/xbin/su
# chmod 6755 /system/xbin/su
# busybox chown 0.2000 /system/xbin/su
# busybox ln -s /system/xbin/su /system/bin/su
IMPORTANT: Do not leave your "/system" mounted as read-write; change it back and exit the shell:
Code:
# mount -o remount,ro /dev/block/stl9 /system
# exit
$ exit
You should be back at your basic Linux command prompt now. Install the Superuser app.
Code:
./adblinux install Superuser.apk
7. Reboot your phone
When everything loads back up, you should have root privileges. Update BusyBox from the market. If everything went according to plan, when you try to install BusyBox you should get a prompt from the Superuser app asking if you want to grant the BusyBox installer superuser privileges. If so, everything worked the way it was supposed to, and you're now a 1337 [email protected]><0r or something.
8. Troubleshooting
Mine didn't take the first time for some reason. After reboot, I installed BusyBox and Titanium Backup, both of which failed to get root privileges. I went back into the phone with adblinux, remounted /system as rw, again set the privileges for "/system/xbin/su" to 6755, then remounted /system as ro and rebooted. It took the second time, so I'm assuming I may have typed something wrong.
Another thing I was keen to try is installing the Superuser app FIRST, then running the hacks to root the phone. The phone does not need to be rooted to install Superuser, only for it to work as designed. I am curious if "SU->root->reboot" would work the first time, instead of "Root->SU->Reboot->Re-Root->Reboot", which is how it's been working now. If I happen to reinstall and try this again, I'll update. If anyone else gives it a whirl, post a comment and I'll update accordingly.
I hope this helps someone else. Please comment below with questions/criticisms/flames.
Thanks bro this is a very handy guide i to use only linux and it kills me how many people say ehh just install windows it easier BLAAA is what i say great work keep it coming...
tkienzle said:
Thanks bro this is a very handy guide i to use only linux and it kills me how many people say ehh just install windows it easier BLAAA is what i say great work keep it coming...
Click to expand...
Click to collapse
I'm with you. I HATE hearing "just use Odin" or "you can buy a copy of Windoze for not much $$$!" If I wanted Windoze, I'd be using it already. If I could use Odin, I'd probably just follow the directions for that and not be asking questions about Heimdall.
+1 thanks. been running linux since 2002, wasn't looking forward to using a friends computer just to root a phone.
Related
I need the following directories of a stock phone (no custom recovery/boot applied):
Tar it up and send them my way.
/.info
/lib
/lib/modules
/res
/res/images
/sbin
/sbin/images
Any files found in the / (root) directory.
my phone is stock minus the apps I've removed. I don't know how to copy this info but I will be happy to figure it out and get it done if no one else is already doing this.
If rooted is alright, let me know and I will get you what you need.
What is the best way to get the files to you?
What program can get that information on a stock vibrant? Or would we need root?
Sent from my Vibrant using xda app
I think you need at least root to have busybox installed that gives you the cp function but I could be wrong.
Without root which busybox comes with.. I don't know that the software allows a copy feature.
If nobody gets them to you by the time I get home from work then I will pull them for you.
Sent from my SGH-T959 using XDA App
Koush said:
I need the following directories of a stock phone (no custom recovery/boot applied):
Tar it up and send them my way (ignore the numbers, just note the directory name).
dir /.info 755 0 0
dir /dev 755 0 0
dir /lib 755 0 0
dir /lib/modules 755 0 0
dir /mnt 755 0 0
dir /mnt/.lfs 755 0 0
dir /proc 755 0 0
dir /res 755 0 0
dir /res/images 755 0 0
dir /sbin 755 0 0
dir /sbin/images 755 0 0
dir /sd-ext 755 0 0
dir /sys 755 0 0
dir /system 755 0 0
dir /system/etc 755 0 0
dir /tmp 755 0 0
dir /tmp/bootchart 755 0 0
Click to expand...
Click to collapse
pulling as I type
EDIT: ok, I was able to pull everything except /mnt, /info, and /sd-ext. I have the .tgz file. where do I send it? it's over 300mb
jroid did you just make a new folder with
mkdir then use cp of those requested folders? Newbie just trying to make sure I'm doing something the best way.
thanks
jroid said:
pulling as I type
EDIT: ok, I was able to pull everything except /mnt, /info, and /sd-ext. I have the .tgz file. where do I send it? it's over 300mb
Click to expand...
Click to collapse
I was having an issue grabbing the /proc directory for some reason. Since he got the others I am attahcing /mnt and /.info.
/sd-ext I could not find......
msw1382 said:
I was having an issue grabbing the /proc directory for some reason. Since he got the others I am attahcing /mnt and /.info.
/sd-ext I could not find......
Click to expand...
Click to collapse
/mnt my terminal said it was pulled, but the folder i extracted it to didn't show anything. so i'm assuming it didn't pull. Thanks
rsfaze said:
jroid did you just make a new folder with
mkdir then use cp of those requested folders? Newbie just trying to make sure I'm doing something the best way.
thanks
Click to expand...
Click to collapse
no I adb pulled everything seperately
Koush,
I can help you. But, when i try to adb pull these things. Esp in proc. the process just stops.
If i remove proc from the list. the it pulls some then just reboots
Is there a special way to do so?
Thanks
I went and trimmed down what I need to just this following list:
/.info
/lib
/lib/modules
/res
/res/images
/sbin
/sbin/images
That should make the resultant package less than 20mb. Let me know!
A raw dump of the boot area would also help (this is completely safe, just type it properly):
dd if=/dev/block/bml7 of=/sdcard/bml7.img
Then send me /sdcard/bml7.img
Koush said:
A raw dump of the boot area would also help (this is completely safe, just type it properly):
dd if=/dev/block/bml7 out=/sdcard/bml7.img
Then send me /sdcard/bml7.img
Click to expand...
Click to collapse
OLD: dd if=/dev/block/bml7 out=/sdcard/bml7.img
NEW: Should be dd if=/dev/block/bml7 of=/sdcard/bml7.img
Here you go.
Don't know if this is what you want but I thought I'd throw you completely stock no root up here... Astro let me copy them no problems.
img of course can't be made without root
daropedia said:
Don't know if this is what you want but I thought I'd throw you completely stock no root up here... Astro let me copy them no problems.
img of course can't be made without root
Click to expand...
Click to collapse
Awesome! Can you also send me the files in the root directory? Ie, init.rc, recovery.rc, and whatever else you find?
here you go
thanks for the hard work.. heres mine
xspeed9190 said:
thanks for the hard work.. heres mine
Click to expand...
Click to collapse
The directory structure isn't preserved in this properly (seems all mashed together). All I need now is the files in the root directory!
Koush said:
The directory structure isn't preserved in this properly (seems all mashed together). All I need now is the files in the root directory!
Click to expand...
Click to collapse
Well, hopefully this helps, here are all the random files I found in my root dir.
Thanks for the hard work.
cheers!
I have Android SDK on my pc. I got Busybox installed on the phone. when I use command prompt to navigate to \tools directory and i type adb remount, i get the error message of "remount failed: no such file or directory"
Is there something im doing wrong here?
Please help
Sent from my SAMSUNG-SGH-I897 using XDA App
I've never used the command adb remount. Only adb shell and adb devices.
Sent from my SAMSUNG-SGH-I897 using XDA App
If I use adb shell it doesnt let me push files into certain folders. It says push is not a command... I'm trying to change my bootscreen
Sent from my SAMSUNG-SGH-I897 using XDA App
Hmm, I would help you if I could, but I don't know the steps for changing the boot screen. I haven't had the need for adb remount, sorry.
Sent from my SAMSUNG-SGH-I897 using XDA App
Just curious if you made sure usb debugging is on.
I've also never used the adb remount, but as for your comment about pushing... push isn't ran from "adb shell"
you should be doing "adb push <file to push> /path/to/where/it/goes/<file>"
Of course this needs root and, in places where the NAND is mounted as read only, you must do the remount option with r/w
There are tons of guides on how to do this on our forum, but I'm too lazy to find them.
The thing is, I'm already rooted so I don't know why I can't do those commands. I will try to mount with "adb remount r/w"?
Sent from my SAMSUNG-SGH-I897 using XDA App
flashman2002 said:
Just curious if you made sure usb debugging is on.
Click to expand...
Click to collapse
yes i have usb debugging mode on.
i tried adb remount r/w and i get the following message:
D:\ANDROID SDK\android-sdk-windows>cd tools
D:\ANDROID SDK\android-sdk-windows\tools>adb remount r/w
* daemon not running. starting it now *
* daemon started successfully *
remount failed: No such file or directory
D:\ANDROID SDK\android-sdk-windows\tools>
can somebody please point me a a guide that works. the ones that ive searched for does not seem to work for me. complete newb here
I get exactly the same thing but can't seem to find any help
I was having a similar issue. Maybe I can help.
First, I am already rooted and have busybox installed. Don't know if that matters, but can't hurt.
Here's what you can do:
Code:
C:\Program Files\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount
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
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
[COLOR="Red"]/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0[/COLOR]
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
At this point, we can see that /system is mounted at /dev/block/stl9. With that knowledge:
Code:
$ su
# mount -o remount,rw /dev/block/stl9 /system
Now your free to do whatever it is you were trying to do. When you're done, don't forget to :
Code:
# mount -o remount,ro /dev/block/stl9 /system
That should do it. Standard disclaimer, not responsible, blah,blah,blah...
How can I add these commands as aliases to the phone's shell?
shilob said:
I was having a similar issue. Maybe I can help.
First, I am already rooted and have busybox installed. Don't know if that matters, but can't hurt.
Here's what you can do:
Code:
C:\Program Files\android-sdk-windows\tools>adb shell
* daemon not running. starting it now *
* daemon started successfully *
$ mount
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
/dev/block/stl6 /mnt/.lfs j4fs rw 0 0
tmpfs /sqlite_stmt_journals tmpfs rw,size=4096k 0 0
none /dev/cpuctl cgroup rw,cpu 0 0
[COLOR="Red"]/dev/block/stl9 /system rfs rw,vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0[/COLOR]
/dev/block/mmcblk0p2 /data rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,ioc
harset=utf8 0 0
/dev/block/stl10 /dbdata rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocha
rset=utf8 0 0
/dev/block/stl11 /cache rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iochar
set=utf8 0 0
/dev/block/stl3 /efs rfs rw,nosuid,nodev,vfat,llw,check=no,gid/uid/rwx,iocharset
=utf8 0 0
/dev/block//vold/179:1 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=
1015,fmask=0102,dmask=0002,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,s
hortname=mixed,utf8,errors=remount-ro 0 0
$
At this point, we can see that /system is mounted at /dev/block/stl9. With that knowledge:
Code:
$ su
# mount -o remount,rw /dev/block/stl9 /system
Now your free to do whatever it is you were trying to do. When you're done, don't forget to :
Code:
# mount -o remount,ro /dev/block/stl9 /system
That should do it. Standard disclaimer, not responsible, blah,blah,blah...
Click to expand...
Click to collapse
Everything is fine until I get to
$ su
I get "Permission denied"
Hmm... anyone has any tips? Thanks!
when you type su into the command prompt, you should get a pop-up on your phone saying unknown is requesting superuser permissions and you need to allow it or you will get denied permission.
Thanks! I passed that.. Now Im confused about whats the next step to push an apk into /system/app. I tried exiting from shell ("exit" twice until I saw C:\Program Files\android-sdk-windows\tools>) and then tried adb push.... but again I got No permission message ..
any advice?
jvanja said:
Thanks! I passed that.. Now Im confused about whats the next step to push an apk into /system/app. I tried exiting from shell ("exit" twice until I saw C:\Program Files\android-sdk-windows\tools>) and then tried adb push.... but again I got No permission message ..
any advice?
Click to expand...
Click to collapse
Did you do the "mount -o remount,ro ..." before you exited the shell ? sounds like your still on Read-only .
-First thing copy the .apk app into the sdk tools folder.
-Then do the following
Code:
adb shell
su
mount -o remount,rw /dev/block/stl9 /system
exit
exit
-Now from your windows command prompt in sdk tools folder
adb push my_app.apk /system/app
-Once your finish
adb reboot
After the reboot your /system is returned to it's original read-only state.
Thats exactly what I did..:/ Does shell give you a confirm that you got the rw rights after doing:
mount -o remount,rw /dev/block/stl9 /system??
In my case it only responded with the same line below..
jvanja said:
Thats exactly what I did..:/ Does shell give you a confirm that you got the rw rights after doing:
mount -o remount,rw /dev/block/stl9 /system??
In my case it only responded with the same line below..
Click to expand...
Click to collapse
No it wont say anything. After you've done the remount,rw check your mount with "mount" in the shell. The /dev/block/stl9 /system line should read like this.
Code:
/dev/block/stl9 /system rfs [color=green]rw[/color],vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
rather then
Code:
/dev/block/stl9 /system rfs [color=red]ro[/color],vfat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0
would it hurt to change
rootfs / rootfs ro 0 0
to rw...
via
mount -o rw,remount -t ext2 rootfs / rootfts /sytem
i at least think that would be the command...also would that be doable via the terminal emulator on the nook.
the reason i want to do this is because every time i try to clear my youtube user data via terminal i get a ro only error...though this could also be due to using the terminal emu...i just get sick of having to adb whenever i wanna change something...so just wondering.
Meh nevermind I just went at it with root explorer and deleted the .xml file from /data/data/com.google.android.youtube/shared_prefs
Hi All,
(I've read tons of Threads here, but not yet found a solution).
My Galaxy Tab 10.1 is useless right now as it cannot write to internal storage.
Lots of apps crashing on use and doing a factory reset from the recovery menu does not help (Tablet is in exact same state aon reboot).
So, I've been using adb
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Operation not permitted
Here's the mount information from shell
Code:
[email protected]:/mnt/asec $ mount
mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p4 /system ext4 ro,relatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p5 /cache ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p8 /data ext4 ro,nosuid,nodev,noatime,barrier=1,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/mmcblk0p1 /efs ext4 rw,nosuid,nodev,noatime,barrier=1,data=ordered 0 0
/dev/fuse /mnt/sdcard fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
So, I've tried to mount manually from adb shell:
Code:
[email protected]:/ $ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
mount: Operation not permitted
[email protected]:/ $
[email protected]:/ $ mount -o remount,rw -t rfs /dev/block/stl9 /system
mount -o remount,rw -t rfs /dev/block/stl9 /system
mount: Operation not permitted
But, I have no SU command:
Code:
[email protected]:/ $ su
su
/system/bin/sh: su: not found
I've got the su binary from downloading off this forum, but I cannot copy that up either (even to seemingly writable mount points)
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push su /cache
failed to copy 'su' to '/cache/su': Permission denied
Any hints to what I can do now?
Ro
Hey, this forum is for Samsung Galaxy Tab 7.
Here is link for SGT 10.1
http://forum.xda-developers.com/forumdisplay.php?f=1050
But looks like your device is not yet rooted correctly.
The easiest thing is to find pre-rooted kernel and flash them via odin.
Thanks for the reply, yappoe!
I was following a guide I found linked on a forum to get the Tablet Restocked to factory settings.
However, when I try to write via Odin, I get an error message on the tablet in Red
Code:
Bct_sync_Odin: Error to NvBuBctUpdate![err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DownloadPartition![err:0x140005]
Obviously a write error, presumably as the File system is in Read-Only mode ?
Ro
Yes, because permission is not set correctly. You need root access to do that.
I really don't know much about G-Tab 10.1, and I don't know what you were trying to do or are trying to do.
But if you are trying to go back to stock firmware, you can follow this steps.. it works on most Samsung. (Note: Unless you are moving from Honeycomb to ICS or vice versa, you do NOT need to re-partition).
you can download any official firmware at http://fus.nanzen.se/
1. Download Fus Check Downloader 2.1 and downloaded a Firmware for your region. It will automatically decode the .enc2 file to.zip file
(or find your firmware at sammobile.com, you can skip step 2).
2. Extract the .zip file generated from decoding file to a folder and I got
tar.md 5 file.
3. Start Odin - put the .md5 to PDA and leave everything else as is.
4. Go to download mode on the G-tab
and click start. It takes about 6 to 7 minutes to do the flashing.
Can't guarentee if it would work, but good luck.
Once you get it work with STOCK, go to the Galaxy Tab 10.1 forum
and find the instruction there to ROOT
http://forum.xda-developers.com/forumdisplay.php?f=1050
Thanks yappoe,
That is a nice tool for firmware downloading.
Unfortunately I get the exact same error immediately when trying to write to the tablet via Odin.
Code:
Bct_sync_Odin: Error to NvBuBctUpdate![err:0x140005]
DownloadPartition_Odin: Error to Bct_sync_Odin![err:0x140005]
Tegra_Nand_Write: Error to DownloadPartition![err:0x140005]
I think I have a sort of chicken and egg situation where I my problem is my drive is mounted in read-only mode and I cannot change it without rooting/executing su
Ro
same situation
I have the same situation but with my omnia 2.
suddenly, the internal storage became read-only.
I have tried flashing the ROM and unchecking "preserve device contents".
I have tried spyware, malware, antivirus from PC via usb mode.
I have tried low-level format.
I have tried hard reset.
I have tried below cabs.
MoviPatch_Eng_100416
nueStorageManager-v1.1
Til now, i still have the problem.
Im using a micro sd instead.
Im planning on opening my phone and removing the internal memory chip instead lol.
I did open up my tablet.
The internal memory is part of a single mainboard.
(I think its the same in almost every device)
Looking into getting a replacement mainboard now.
It's possible to use an external SD card as the internal storage. This won't fix the internal storage, but your Tab will work again. See this thread.
ableeker said:
It's possible to use an external SD card as the internal storage. This won't fix the internal storage, but your Tab will work again. See this thread.
Click to expand...
Click to collapse
Cheers for the pointer, but the Galaxy Tab 10.1 doesn't have a place for an SD / micro SD card addition.
Ah. But you asked in the wrong forum.
Go to Galaxy tab 10.1 forum
Sent from my GT-P1000 using xda app-developers app
Yeah i asked a technician if he could do it, he said he has no idea where that chip is in the mainboard
Sent from my GT-I8160 using Tapatalk 2
supersaiyanx said:
Yeah i asked a technician if he could do it, he said he has no idea where that chip is in the mainboard
Click to expand...
Click to collapse
The mainboard cannot have components removed/added ... You have to replace the entire mainboard.
Sorry if this is known but I just saw this today and though some people might like to know. There's a link to Busybox within.
tizenexperts.com/2014/06/developers-install-busy-box-on-your-root-tizen-samsung-gear-smartwatch
.Killabyte said:
Sorry if this is known but I just saw this today and though some people might like to know. There's a link to Busybox within.
tizenexperts.com/2014/06/developers-install-busy-box-on-your-root-tizen-samsung-gear-smartwatch
Click to expand...
Click to collapse
Can't figure out the sdb instructions to actually install it?
lazer9 said:
Can't figure out the sdb instructions to actually install it?
Click to expand...
Click to collapse
Yeah I got the same issue here so apologies. I pushed the file to a couple directories and did "root on" then "sdb shell" to make sure but when it goes to install it complains about needing something like 188kb free space (the package is half that).
So yeah obviously a regular sdb install won't work and it seems I don't know which directory to have the package in when I try to install but that's all I got.
Recreation steps:
1) Ran sdb devices until device was listed (had usb debugging enabled on the gear being rooted running the original Gear Tizen release)
2) Ran sdb root on again to be paranoid
3) Ran sdb shell
4) Copied the file in to /home with "sdb push filename /home". Later on I tried the same thing using the Tizen SDK explorer function to a few more directories since that has drag and drop.
5) Ran the install command it has (rpm -i busybox-1.17.1-2.3.armv7l.rpm)
6) Got free space error. Grr'd.
Here's some of my log excluding the first part:
C:\tizen-wearable-sdk\tools>sdb push busybox-1.17.1-2.3.armv7l.rpm /home
pushed busybox-1.17.1-2.3.armv7l.rpm 100% 75KB
1 file(s) pushed. 0 file(s) skipped.
busybox-1.17.1-2.3.armv7l.rpm 1172 KB/s (76839 bytes in 0.064s)
C:\tizen-wearable-sdk\tools>sdb shell
sh-3.2# ls
bin dev home lost+found opt run smack system var
boot efs initrd media proc sbin srv tmp
csa etc lib mnt root sdcard sys usr
sh-3.2# cd home
sh-3.2# ls
abuild app busybox-1.17.1-2.3.armv7l.rpm developer root
sh-3.2# rpm -i busybox-1.17.1-2.3.armv7l.rpm
installing package busybox-1.17.1-2.3.armv7l needs 188KB on the / filesystem
Ok so someone clued me in to the missing mount command and now I can get it installed! But like the article states the only advantage I see immediately is a working VI from sdb shell. There's no icon created in the launcher. The only way I know it's installed is when I run the command it tells me and busybox is in the /bin directory. Now some more adventurous people may Google and find out how to manually install busybox packages so for those let me know if you find anything cool!
Here's the log. This was on the initial Tizen release with the root package installed.
C:\tizen-wearable-sdk\tools>sdb devices
* daemon not running. starting it now on port 26099 *
* daemon started successfully *
List of devices attached
412ba0e141019466 device SM-V700
C:\tizen-wearable-sdk\tools>sdb root on
Switched to 'root' account mode
C:\tizen-wearable-sdk\tools>sdb shell
sh-3.2# su
sh-3.2# mount -o remount,rw /
//The line above was the missing step.
sh-3.2# exit
//Then I go back to command prompt to push the package again to root.
C:\tizen-wearable-sdk\tools>sdb push busybox-1.17.1-2.3.armv7l.rpm /
pushed busybox-1.17.1-2.3.armv7l.rpm 100% 75KB
1 file(s) pushed. 0 file(s) skipped.
busybox-1.17.1-2.3.armv7l.rpm 1316 KB/s (76839 bytes in 0.057s)
C:\tizen-wearable-sdk\tools>sdb shell
sh-3.2# mount -o remount,rw /
sh-3.2# rpm -i busybox-1.17.1-2.3.armv7l.rpm
package busybox-1.17.1-2.3.armv7l is already installed
sh-3.2# mount -o remount,rw /
sh-3.2# reboot
Rebooting.
The guy that gave me the said to do this again after. I imagine you might need to do this anytime you try to play around with Busybox if you don't see files listed when you do an "ls -a" or get permission errors:
sdb root on
sdb shell
sdb mount -o remount,rw /
exit
Hope this helps someone.