Currently trying to get this to work on my S2 and having issues.
My phone is running official KH3, CF-Rooted.
Using ubuntu.zip from here: http://nexusonehacks.net/nexus-one-hacks/how-to-install-ubuntu-on-your-android/
This guide: http://androlinux.com/android-ubuntu-development/how-to-install-ubuntu-on-android/
bootubuntu script:
Code:
#modprobe ext2
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
export kit=/sdcard/ubuntu
export bin=/system/bin
if ! test -d /data/local/ubuntu
then
mkdir /data/local/ubuntu
fi
export mnt=/data/local/ubuntu
export PATH=$bin:/usr/bin:/usr/sbin:/bin:$PATH
export TERM=linux
export HOME=/root
#mknod /dev/loop1 b 7 0
losetup /dev/block/loop7 /sdcard/ubuntu/ubuntu.img
mount -t ext2 /dev/block/loop7 /data/local/ubuntu
#mount -o loop,noatime -t ext2 $kit/ubuntu.img $mnt
mount -o bind /proc $mnt/proc
mount -o bind /dev $mnt/dev
mount -t devpts devpts $mnt/dev/pts
mount -t proc proc $mnt/proc
mount -t sysfs sysfs $mnt/sys
sysctl -w net.ipv4.ip_forward=1
echo "Setting /etc/resolv.conf to Google Open DNS 8.8.8.8 and 8.8.4.4"
echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
echo "Setting localhost on /etc/hosts "
echo "127.0.0.1 localhost" > $mnt/etc/hosts
echo "READY TO ROCK AND ROLL BABY! "
echo "Brought to you by NexusOneHacks.net and the open source community! "
echo " "
chroot $mnt /bin/bash
#After exit command is executed clear it all up
echo " "
echo "Shutting down Ubuntu"
umount $mnt/dev/pts
umount $mnt/proc
umount $mnt/sys
umount $mnt
losetup -d /dev/block/loop7
I get this error (after typing "sh bootubuntu"):
Code:
>adb shell
/ $ su
su
# cd /sdcard
cd /sdcard
# cd ubuntu
cd ubuntu
# sh ubuntu.sh
sh ubuntu.sh
modprobe: chdir(2.6.35.7-I9100XXKH3-CL479037): No such file or directory
←[H←[Jmkdir: can't create directory '/data/local/mnt': File exists
←[H←[Jchmod: bootubuntu: Operation not permitted
chmod: fsrw: Operation not permitted
chmod: mountonly: Operation not permitted
chmod: ubuntu.img: Operation not permitted
chmod: ubuntu.sh: Operation not permitted
chmod: unionfs: Operation not permitted
←[H←[J
Ubuntu Chroot Bootloader v0.1
Ubuntu Bootloader is now installed!
This process does NOT damage Android OS!
Original Installer by Charan Singh
Modified for Ubuntu Chroot by Max Lee at AndroLinux.com ,G2Hacks.com and NexusOn
eHacks.net
To enter the Ubuntu Linux console just type 'bootubuntu'
# sh bootubuntu
sh bootubuntu
failed: No such file or directoryk3 on /system
bootubuntu: line 41: syntax error: unexpected end of file (expecting "then")
#
Any ideas?
Thats right Folks, I am sitting here holding a ROOTED Acer A200 In my hands...
This was done on ICS 4.0.3 Leaked.
However This SHOULD work for the OTA update.
I hate to have to say this. but........
YOU ARE TAKING RESPONSIBILITY FOR DOING THIS, AND YOU ALONE ASSUME ALL RISKS. THIS HAS WORKED FOR ME BUT I ASSUME NO RESPONSIBILITY IF YOU BRICK YOUR TABLET!
Credit goes to saurik (hxxps://github.com/saurik/mempodroid) for the root method, Jason A. Donenfeld (zx2c4) (Linux Local Privilege Escalation via SUID /proc/pid/mem Write | Nerdling Sapple) for finding the exploit
and to Rkeene (Rooting the Toshiba Thrive) for Getting around the /system mount as RW issue.
First,
( You are going to need to have the android sdk installed, so you have ADB, There are plenty of docs on doing this )
then go here
hxxps://github.com/saurik/mempodroid...ster/README.md
get the precompiled binary, (mempodroid )
then
adb push mempodroid /data/local
adb push su /data/local
adb shell
chmod 777 /data/local/mempodroid
Once you have this completed.
goto Rkeenes Site.
hxxp://rkeene.org/projects/info/wiki/210
skip down to step 16.
Follow the instructions there.. Mind you there is a specific offset that you must use for your acer. ( It is listed on his page now )
but this WILL work.
I have done it..
Please please please. Give MASSIVE Credit where Credit is due on this, Saurik, Jason A. Donenfeld (zx2c4), and RKeene.
In Our case here, RKeene took the time to work with me to get the offsets for the Acer, so we can get the /system folder mounted RW. ( I would say an hour or two )
-Hex
Have anyone confirmed this working?
Quick Question
Does the root process being taken require access to a linux machine or can it be done from windows. Most of the commands look like they take place in adb shell but some of the adb push commands look like they are run from a linux command line. I know sounds stupid but not sure and dont want to brick device. The reson I ask is because I run mempodroid and run mkdir command. gets
"[email protected]:/ $ /data/local/mempodroid 0xd9f0 0xad4b -o remount,re "/system
/data/local/mempodroid 0xd9f0 0xad4b -o remount,re "/system
> /data/local/mempodroid 0xd9f0 0xaf47 sh
/data/local/mempodroid 0xd9f0 0xaf47 sh
> mkdir /data/x-root
mkdir /data/x-root
> mkdir /data/x-root/bin
mkdir /data/x-root/bin
> ^C
C:\Program Files\Android\android-sdk\platform-tools>adb push busybox /data/x-root/bin/busybox
failed to copy 'busybox' to '/data/x-root/bin/busybox': No such file or directory"
What am i missing?
Update
Now it shows this
"[email protected]:/ $ chmod 777 data/local/mempodroid
chmod 777 data/local/mempodroid
[email protected]:/ $ /data/local/mempodroid 0xd9f0 0xaf47 mount -o remount,rw /system
0xaf47 mount -o remount,rw /system <
mount: Operation not permitted"
This is killing me!?
I get to here
mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
and it tells me
mount: invalid argument
what the?
---------- Post added at 12:47 PM ---------- Previous post was at 11:55 AM ----------
Ok, this was a pain in the arse!
I hope I can remember the steps I took in order to get this done.
By the way, I'm using windows
adb push mempodroid /data/local
adb push su /data/local
adb shell
$ chmod 777 /data/local/mempodroid
Click to expand...
Click to collapse
Then I went to here as directed,
http://rkeene.org/projects/info/wiki/210
but didn't follow the steps as they were shown because I got stuck many times and had to start over.
So here are my steps.
1.
$ /data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
which then should turn the $ into a #
2.
# mkdir /data/x-root /data/x-root/bin
Click to expand...
Click to collapse
3. Download this,
http://www.rkeene.org/projects/info/resources/diatribes/root-toshiba-thrive/busybox
and then move the file to where you have mempodroid and su so you can adb push them easier
4.
adb push busybox /data/x-root/bin/busybox
adb push su /data/x-root/bin/su
adb shell
Click to expand...
Click to collapse
5. This is where it got tricky. If you don't pay close attention, you will most likely do what I did and put files where they aren't supposed to go. So please, PAY ATTENTION!
If you still have the # in the shell, move forward. Otherwise,
/data/local/mempodroid 0xd9f0 0xaf47 sh
Click to expand...
Click to collapse
and then move forward once # is confirmed.
# cd /data/x-root/bin
# chmod 755 busybox
# ./busybox bash
Click to expand...
Click to collapse
Now, there is no doubting it, you will get the "bash: precmd: not found" error.
# unset PS1 PROMPT_COMMAND
# ./busybox bash
# for tool in $(./busybox --list); do ln -s busybox $tool; done
# PATH="${PATH}:/data/x-root/bin"; export PATH
Click to expand...
Click to collapse
6. AGAIN, PAY CLOSE ATTENTION HERE!!
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
Click to expand...
Click to collapse
7. This is where I ran into another problem, so pay attention.
# cd /
# mkdir /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
You will see nothing as the steps describe. This is because we skipped a step. Why? Because mount -o ro -t ext4 /dev/loop0 /dev/tmpdir for some strange reason wouldn't unmount so I could mount the next step. So instead, we move on and then check again.
Here is the removed step
# mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
# umount /dev/tmpdir
Click to expand...
Click to collapse
You can try this but I advise not to or you could very well run into the same issue I had where you can't unmount in order to move on with the root process
# mount -t ext4 /dev/loop0 /dev/tmpdir
# ls -l /dev/tmpdir
Click to expand...
Click to collapse
And now you will see /system mounted.
8.
# cp /data/x-root/bin/su /dev/tmpdir/bin/
# chmod 4555 /dev/tmpdir/bin/su
# umount /dev/tmpdir
# losetup -d /dev/loop0
# sync
# reboot
Click to expand...
Click to collapse
9. Now once your A200 reboot and displays the home screen, we will confirm.
adb shell
[email protected]:/ $ su
Click to expand...
Click to collapse
If the $ doesn't turn into a #, you did something wrong...
Thank you hexmare, for opening this thread and giving the guidance.
Thank you d10369319, for "/data/local/mempodroid 0xd9f0 0xaf47 sh", I would have never figured this out.
Thank you RKeene, for writing out the guide to Root the Toshiba Thrive
And Thank you Saurik along with zx2c4, for mempodroid
By the way, I'm posting this in the Dev section...
been away
Thanks for clearing up the questions. I have been gone the past couple hours. Also thanks for reposting this in the dev section as well, I would have but I don't have enough posts on here to post under that section yet.
-Hex
So i'm stucks again
where did i go wrong?
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found
Anytime, buddy. I figured if I was having problems rooting, others would have problems as well so I wanted to make it as simple as possible...
---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------
d10369319 said:
where did i go wrong?
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found
Click to expand...
Click to collapse
I think you might have missed these steps.
# unset PS1 PROMPT_COMMAND
# ./busybox bash
# for tool in $(./busybox --list); do ln -s busybox $tool; done
Click to expand...
Click to collapse
Something that I want to point out as well. Especially those that are trying this root on a200's that have the OTA update.
Please for the love of all that is holy, MOUNT AS READ ONLY FIRST. You need to make sure that you have the correct offset for the system area that you mount.
If you have the wrong offset, mount as RW, and write to it, you can REALLY hose up your tablet and possibly brick it.
mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
ls -l /dev/tmpdir
ls -l /system
** COMPARE THEM if they pass then continue.**
umount /dev/tmpdir
mount -t ext4 /dev/loop0 /dev/tmpdir
sorry for the several caps spots. But this is really important. I don't want Shiny bricks being formed.
-Hex
Tryed agin get this
philosophics said:
Anytime, buddy. I figured if I was having problems rooting, others would have problems as well so I wanted to make it as simple as possible...
---------- Post added at 03:40 PM ---------- Previous post was at 03:37 PM ----------
I think you might have missed these steps.
Click to expand...
Click to collapse
I tried it again and still got same error. When i run it i get
[email protected]:/data/x-root/bin # unset PS1 PROMPT_COMMAND
unset PS1 PROMPT_COMMAND
[email protected]/busybox bash
./busybox bash
/data/x-root/bin # for tool in $(./busybox --list); do ln -s busybox $tool; done
for tool in $(./busybox --list); do ln -s busybox $tool; done
link failed File exists
link failed File exists<====This shows up a bunch
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found
---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------
Are you running the OTA update or the dev leak ICS?
d10369319 said:
for tool in $(./busybox --list); do ln -s busybox $tool; done
link failed File exists
link failed File exists<====This shows up a bunch
Click to expand...
Click to collapse
This is because you've already completed this step so it's already there.
---------- Post added at 12:08 AM ---------- Previous post was at 12:06 AM ----------
Are you running the OTA update or the dev leak ICS?
Click to expand...
Click to collapse
I am running the OTA
And by the way, I think I know what's wrong. I put one step in the wrong place.
Before you cd / try this
# mknod /dev/loop0 b 7 0
# losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
then try cd / and continue.
If that's what went wrong, I will revise the guide
---------- Post added at 04:25 PM ---------- Previous post was at 04:22 PM ----------
hexmare said:
Something that I want to point out as well. Especially those that are trying this root on a200's that have the OTA update.
Please for the love of all that is holy, MOUNT AS READ ONLY FIRST. You need to make sure that you have the correct offset for the system area that you mount.
If you have the wrong offset, mount as RW, and write to it, you can REALLY hose up your tablet and possibly brick it.
mount -o ro -t ext4 /dev/loop0 /dev/tmpdir
ls -l /dev/tmpdir
ls -l /system
** COMPARE THEM if they pass then continue.**
umount /dev/tmpdir
mount -t ext4 /dev/loop0 /dev/tmpdir
sorry for the several caps spots. But this is really important. I don't want Shiny bricks being formed.
-Hex
Click to expand...
Click to collapse
Yes, but this is where I got stuck. When I tried to run the umount command for this, it basically told me no. This is why I intentionally left that particular step out...
Well since you are running OTA, ( Which was my main concern ) and you didn't brick it I guess we are in good shape for the offsets. Since mine is the leaked version, I didn't want people on OTA to try and arf up.
so Thumbs up to you.
now since you have the OTA and root. Would you mind pulling a System Dump, including Boot and recovery images so those of us on leak can move back to official??
-Hex
I ran it from the point were i got
"link failed File exists
link failed File exists
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found"
Still same problem
---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------
Started completely over from sctratch 4 times and still get stuck in the same exact spot. Completely insane.
hexmare said:
now since you have the OTA and root. Would you mind pulling a System Dump, including Boot and recovery images so those of us on leak can move back to official??
-Hex
Click to expand...
Click to collapse
I would be glad to do so, but have never done it before. Mind throwin me the steps for that?
---------- Post added at 04:42 PM ---------- Previous post was at 04:40 PM ----------
d10369319 said:
I ran it from the point were i got
"link failed File exists
link failed File exists
/data/x-root/bin # #PATH="${PATH}:/data/x-root/bin";export PATH
#PATH="${PATH}:/data/x-root/bin";export PATH
/data/x-root/bin # cd /
cd /
/ # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
bash: mknod: not found"
Still same problem
---------- Post added at 12:37 AM ---------- Previous post was at 12:31 AM ----------
Started completely over from sctratch 4 times and still get stuck in the same exact spot. Completely insane.
Click to expand...
Click to collapse
I just updated the guide. Misplaced some steps. Try it again with the revised steps.
Are there any specific device settings that your running other than usb debuging on your device, and what version of windows are you using cause im thinking maybe device drivers may be an issue.
I'm running windows 7
If you are able to use adb with the A200, then drivers would not be an issue.
GOT ROOT!!!!!!!!!!!!
Found the error
"/data/x-root/bin # PATH="${PATH}:/data/x-root/bin"; export PATH
PATH="${PATH}:/data/x-root/bin"; export PATH
/data/x-root/bin # mknod
mknod
BusyBox v1.19.3-Stericson (2011-11-01 20:22:18 CDT) multi-call binary.
Usage: mknod [-m MODE] NAME TYPE MAJOR MINOR
Create a special file (block, character, or pipe)
-m MODE Creation mode (default a=rw)
TYPE:
b Block device
c or u Character device
p Named pipe (MAJOR and MINOR are ignored)
/data/x-root/bin # mknod /dev/loop0 b 7 0
mknod /dev/loop0 b 7 0
/data/x-root/bin # losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
losetup -o 25165824 /dev/loop0 /dev/block/mmcblk0
/data/x-root/bin # cd /
cd /
/ # mkdir /dev/tmpdir
mkdir /dev/tmpdir
/ # ls -l /dev/tmpdir
ls -l /dev/tmpdir
/ # mount -t ext4 /dev/loop0 /dev/tmpdir
mount -t ext4 /dev/loop0 /dev/tmpdir
/ # ls -l /dev/tmpdir
ls -l /dev/tmpdir
drwxr-xr-x root root 2012-02-16 16:27 app
drwxr-xr-x root shell 2012-02-16 16:27 bin
-rw-r--r-- root root 1939 2008-08-01 08:00 build.prop
drwxr-xr-x root root 2012-02-16 16:27 etc
drwxr-xr-x root root 2012-02-16 16:27 fonts
drwxr-xr-x root root 2012-02-16 16:27 framework
drwxr-xr-x root root 2012-02-16 16:27 lib
drwxr-xr-x root root 1969-12-31 19:00 lost+found
drwxr-xr-x root root 2012-02-16 16:27 media
-rw-r--r-- root root 595088 2008-08-01 08:00 recovery-from-boot.p
drwxr-xr-x root root 2012-02-16 16:27 tts
drwxr-xr-x root root 2012-02-16 16:27 usr
drwxr-xr-x root shell 2012-02-16 16:27 vendor
drwxr-xr-x root shell 2012-02-16 16:27 xbin
/ # cp /data/x-root/bin/su /dev/tmpdir/bin/
cp /data/x-root/bin/su /dev/tmpdir/bin/
/ # chmod 4555 /dev/tmpdir/bin/su
chmod 4555 /dev/tmpdir/bin/su
/ # unmount /dev/tmpdir
unmount /dev/tmpdir
bash: unmount: not found
/ # umount /dev/tmpdir
umount /dev/tmpdir
/ # losetup -d /dev/loop0
losetup -d /dev/loop0
losetup: /dev/loop0: No such device or address
/ # losetup -d /devo/loop0
losetup -d /devo/loop0
losetup: /devo/loop0: No such file or directory
/ # sync
sync
/ # reboot
reboot
reboot returned
/ #
C:\Program Files\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ #"
run #PATH="${PATH}:/data/x-root/bin"; export PATH
Thats were the error occured and was causing a problem.
Thanx to saurik (hxxps://github.com/saurik/mempodroid) for the root method, Jason A. Donenfeld (zx2c4) (Linux Local Privilege Escalation via SUID /proc/pid/mem Write | Nerdling Sapple) for finding the exploit
And a big thanks to philosophics for helping me out.
---------- Post added at 01:17 AM ---------- Previous post was at 01:15 AM ----------
philosophics said:
I'm running windows 7
If you are able to use adb with the A200, then drivers would not be an issue.
Click to expand...
Click to collapse
Turns out it was a typo in the direction's, only needs one # for the path command and thats whats was causing the error. Ty so much for your help philosophics.
You are most welcome. I remember what the original android days were like. Kind of a pain to get anything done...
Grats on the root!!!
Before I dive in head first, will my iconia be wiped while performing this root?? Just want to back up if need be.
And it's confirmed working on the OTA??
No, your device will not be wiped...
Yes, I performed this on the OTA
Hi everyone,
I'm a noob on this forum so i'll try to be as clear as possible.
I have some issues trying to install backtrack 5 ARM version on my Nexus 10.
Config :
Nexus 10
4.3
Kernel : 3.4.39-g446c9cf
Build number : JWR66Y
Terminal emulator
Busybox Free
What I did :
I rooted my Nexus 10 following this tutorial (checking custom recovery) :
http://forum.xda-developers.com/showthread.php?t=2015467
I tried to install Backtrack 5 following this tutorial :
http://forum.xda-developers.com/showthread.php?t=1079898
But it didn't succeed. I tried to figure out my problem but I'm quite lost and not sure what the real problem is :
The script bt :
Code:
perm=$(id|cut -b 5)
if [ "$perm" != "0" ];then echo "This script requires root! Type: su"; exit; fi
mount -o remount,rw /dev/block/mmcblk0p5 /system
export kit=/sdcard/bt5
export bin=/system/bin
export mnt=/data/local/mnt
mkdir $mnt
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export HOME=/root
if [ -b /dev/loop7 ]; then
echo "Loop device exists"
else
busybox mknod /dev/loop7 b 7 0
fi
#mount -o loop,noatime -t ext2 $kit/bt5.img $mnt
losetup /dev/block/loop7 $kit/bt5.img
mount -t ext2 /dev/block/loop7 $mnt
mount -t devpts devpts $mnt/dev/pts
mount -t proc proc $mnt/proc
mount -t sysfs sysfs $mnt/sys
busybox sysctl -w net.ipv4.ip_forward=1
echo "nameserver 8.8.8.8" > $mnt/etc/resolv.conf
echo "nameserver 8.8.4.4" >> $mnt/etc/resolv.conf
echo "127.0.0.1 localhost bt5" > $mnt/etc/hosts
echo "Ubuntu is configured with SSH and VNC servers that can be accessed from the IP:"
ifconfig eth0
echo " "
busybox chroot $mnt /bin/bash
echo "Shutting down BackTrack ARM"
umount $mnt/dev/pts
umount $mnt/proc
umount $mnt/sys
umount $mnt
losetup -d /dev/loop7
I have theese errors (by doing sh -x bt)
mount -t ext2 /dev/block/loop7 $mnt
>mount: Operation not supported on transport endpoint.
ifconfig etho
>eth0 : No such device
busybox chroot $mnt /bin/bash
>chroot: can't execute '/bin/bash' no such file or directory
losetup -d /dev/loop7
>losetup: /dev/loop7: No such device or address
I search on the forum but I can't find what is the real problem :
http://forum.xda-developers.com/showthread.php?t=2116059
--> cd /storage/emulated/legacy/bt5/ don't change anything.
I readed that ext2 and chroot not working could come from the 4.3 but I'm not sure about this information.
I readed that most of custom ROM handle this.
/bin/bash doesn't exist, but /system/bin/sh does exists but :
busybox chroot $mnt /system/bin/sh don't changes anything.
I'd be glad if you can help me understanding my problem
Best,
Sanchorizo.
Problem with /efs partition (can't mount but IMEI OK)
Hi guys,
I've been searching for two days before posting this.. I'm completely mad on how to repair this problem.
I tried to flash a custom recovery on my GT-9505 doing this in terminal (of course my phone was rooted):
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10
The problem is that I flashed the recovery on the wrong partition, as /mmcblk0p10 is for /efs (right?)
I was on stock firmware I9505XXUDMH8.
When I reboot, phone went on factory mode and I couldn't make calls. Wifi was working right.
I flashed CM 10.1.3 last night and now I can make calls. IMEI and wifi mac are shown ok in status, but bt is not not available and I think serial number is wrong (3403a6f2??)
I suppose that if I go back to stock the problem will be the same with factory mode and no calls because flashing this won't write on /efs.
I have a backup of efs (efs_19700508_054443.img) (~13MB) done in philz touch recovery, but this was made after I corrupted the /efs.
So the problem is I can't mount /efs in recovery neither in File Manager or terminal.
Any ideas on what can I do to repair it?? Thanks in advance and sorry if I have posted in wrong place
Update:
I've made another backup but with EFS Professional: GT-I9505_20131026_190930.tar.gz -> efs.img.ext4
If it holds for something...
Edit: BT address is showing correctly when BT is ON (sorry for that mistake!)
So the only thing is showing wrong (i think) is serial number.
i still cannot mount /efs nor access it via root explorer...:crying:
If I'm on Windows 7, is there any way to mount the efs.img file to edit files into it? (I.e. Like in daemon tools)
If I can format /efs then I'll only hace to edit the files in efs.img to edit my serial number for the good one and copy these files into /efs.
Then my /efs partition won't be corrupted and I will be able to mount it
Someone can give any idea?
Up!
Up!
Uuuup..!
If I restore the .img backup that I have of /efs in recovery it doesn't change anything... Maybe cause it's corrupted?
fran41 said:
If I restore the .img backup that I have of /efs in recovery it doesn't change anything... Maybe cause it's corrupted?
Click to expand...
Click to collapse
try these commands in terminal emulator:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
sync
reboot
samersh72 said:
try these commands in terminal emulator:
Code:
su
mount -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
sync
reboot
Click to expand...
Click to collapse
Thanks for reply.
First line (mount -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs) Mount: invalid argument
Something spelled wrong?
fran41 said:
Thanks for reply.
First line (mount -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs) Mount: invalid argument
Something spelled wrong?
Click to expand...
Click to collapse
Ok, try without first command (mount....)
if not try this
Code:
mount -w -t ext4 /dev/block/mmcblk0p10
samersh72 said:
Ok, try without first command (mount....)
if not try this
Code:
mount -w -t ext4 /dev/block/mmcblk0p10
Click to expand...
Click to collapse
[email protected]:/ # echo -n ON > /efs/FactoryApp/keystr
sh: can't create /efs/FactoryApp/keystr: No such file or directory
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Should be like this??:
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10 /efs
mount: Invalid argument
fran41 said:
[email protected]:/ # echo -n ON > /efs/FactoryApp/keystr
sh: can't create /efs/FactoryApp/keystr: No such file or directory
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10
Usage: mount [-r] [-w] [-o options] [-t type] device directory
Should be like this??:
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10 /efs
mount: Invalid argument
Click to expand...
Click to collapse
it is weird! try:
Code:
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
or
Code:
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
samersh72 said:
it is weird! try:
Code:
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
or
Code:
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
Click to expand...
Click to collapse
[email protected]:/ # mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
mount: Invalid argument
fran41 said:
[email protected]:/ # mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10
Usage: mount [-r] [-w] [-o options] [-t type] device directory
1|[email protected]:/ # mount -r -w -o remount,rw -t ext4 /dev/block/mmcblk0p10 /efs
ext4 /dev/block/mmcblk0p10 /efs <
mount: Invalid argument
Click to expand...
Click to collapse
this command work for me (mount -o remount,rw -t ext4 /dev/block/mmcblk0p10)
i dont know what is the matter with your efs partition!
by the way, install busybox then do the commands
samersh72 said:
this command work for me (mount -o remount,rw -t ext4 /dev/block/mmcblk0p10)
i dont know what is the matter with your efs partition!
by the way, install busybox then do the commands
Click to expand...
Click to collapse
I have busybox installed! I'm getting mad with this Nothing seems to work...
fran41 said:
I have busybox installed! I'm getting mad with this Nothing seems to work...
Click to expand...
Click to collapse
try to re-partition the phone partitions using pit file with the firmware, it may help
samersh72 said:
try to re-partition the phone partition using pit file with the firmware, it may help
Click to expand...
Click to collapse
I did that once flashing it with stock and nothing...
fran41 said:
I did that once flashing it with stock and nothing...
Click to expand...
Click to collapse
my last commands to mount efs (make sure that busybox binaries are installed from the application)
Code:
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10 /efs
or
Code:
busybox mount -w -t ext4 /dev/block/mmcblk0p10 /efs
you can try also to flash the modem twice in odin as "phone"
if not, i guess you have the service center option
samersh72 said:
my last commands to mount efs (make sure that busybox binaries are installed from the application)
Code:
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10 /efs
or
Code:
busybox mount -w -t ext4 /dev/block/mmcblk0p10 /efs
you can try also to flash the modem twice in odin as "phone"
if not, i guess you have the service center option
Click to expand...
Click to collapse
This doesn't work:
[email protected]:/ # busybox mount -w -t ext4 /dev/block/mmcblk0p10 /efs
busybox mount -w -t ext4 /dev/block/mmcblk0p10 /efs
mount: mounting /dev/block/mmcblk0p10 on /efs failed: Invalid argument
This works:
255|[email protected]:/ # mke2fs /dev/block/mmcblk0p10
mke2fs /dev/block/mmcblk0p10
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
3488 inodes, 13952 blocks
697 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=14417920
2 block groups
8192 blocks per group, 8192 fragments per group
1744 inodes per group
Superblock backups stored on blocks:
8193
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 27 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[email protected]:/ #
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p10 /efs
mount -w -t ext4 /dev/block/mmcblk0p10 /efs
[email protected]:/ #
Now I go to /efs in root explorer and there's a folder lost+found