Hi all.. Has anyone been able to successfully remount a Verizon EH03 for rooting?
Like I've seen people report on other forums, this line "mount -o remount,rw -t rfs /dev/block/stl19 /system" returns an Operation not permitted.
Short of installing a custom rom, how can I get 2.3.5 rooted ?
Rooted. Had to instal ClockWorksMod.
Related
hey friends i have been trying a couple of roms but each custom rom i try it gets stuck on bootloop
except for the stock
please help me with it
asap
hey guys please don't just view please reply i need to get a custom rom
i am looking forward to install the 2.3.7 stock like
thanks in advance
aniketbullet said:
hey friends i have been trying a couple of roms but each custom rom i try it gets stuck on bootloop
except for the stock
please help me with it
asap
Click to expand...
Click to collapse
Well just explain the steps you do before you install any ROM briefly.. coz i do that stuff all the time and I don't end up in bootloops.
Please HELP! I'm in the same situation.
I made the steps to unlock my phone:
1 c:> cd C:android/android-sdk-windows/platform-tools
2 >adb
3 > adb shell
4 > su
5 # cd /
6 # mount -o remount rw / (
7 # mkdir /efs
8 # mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
9 # cat /efs/mits/perso.txt
10 # umount /efs
it seems like I format the efs partition, or the bootloader.
Anyway, I tried everything I found, with no luck... I can enter in Download mode, and Odin detects the phone, but if I install any stock firmware or cmw, the phone enter in a loop and reboot without showing me the Samsung Logo.
Please HELP!
---------- Post added at 11:22 PM ---------- Previous post was at 10:59 PM ----------
Anybody?
Hello xda, have not found a solution using search on this site so forgive me if i didnt find it and it is there. Basically when i try to use parted on my data partition (stl13) located in /dev/block it freezes. I have a Samsung Replenish which is semi-bricked...i think i found the reason for this which is my /system /data /cache somehow went back to rfs when then custom rom i installed changes those 3 to ext4...was going to delete and remake the partitions, however adb freezes on stl13 which is my /data (stl12 is system, stl14 cache)...i have a CWM based recovery that i can boot into however it fails to format or mount /data, it just freezes. same thing when trying to reinstall the rom. any help or push in the right direction would be really appreciated, have been trying to figure out on my own/scour the internet for a solution but this isnt a very popular device. thanks!
Hello all,
I have been trying to gain root on a Android 4.0.4 device and was able to, but I can't seem to keep system rw long term.
I run the following command
mount -o remount,rw /system
or
adb remount (from a PC)
the mount command will then show that system is in rw mode. However, if I attempt to copy any data into /system, the first file copy fails and the system then reports read only. To make things even more odd, commands like chmod on a file in /system work just fine.
It seems to me that there is something that detects something writing to /system, and then forces the mount back to ro.
Does anyone have any ideas about this? Is this a common technique manufactures use?
The closest thing I could find on XDA is a reference to Sony Xperia devices having a watchdog service that doesn't something like this, but this device is a Kenwood Head unit and not a Sony device.
Thanks!
chris.davis925 said:
Hello all,
I have been trying to gain root on a Android 4.0.4 device and was able to, but I can't seem to keep system rw long term.
I run the following command
mount -o remount,rw /system
or
adb remount (from a PC)
the mount command will then show that system is in rw mode. However, if I attempt to copy any data into /system, the first file copy fails and the system then reports read only. To make things even more odd, commands like chmod on a file in /system work just fine.
It seems to me that there is something that detects something writing to /system, and then forces the mount back to ro.
Does anyone have any ideas about this? Is this a common technique manufactures use?
The closest thing I could find on XDA is a reference to Sony Xperia devices having a watchdog service that doesn't something like this, but this device is a Kenwood Head unit and not a Sony device.
Thanks!
Click to expand...
Click to collapse
I would think that you might need to run a script to remount on boot perhaps, such as one along this idea http://www.3c71.com/android/?q=node/466. Like via init.d or if that isn't possible on this then maybe something like this could do it http://forum.xda-developers.com/showthread.php?t=2378274 ?
Just spit balling ideas.
Correct me if I am wrong, but it seems to me that I wouldn't be able to do those options since system doesn't actually stay rw?
Really depends on the phone. Sometimes you can slip a script in during boot that will keep the system open. Sometimes you need to have a special module too such as this: http://forum.xda-developers.com/showthread.php?t=2230341 Sometimes the kernel doesn't allow it. I would think on 4.0.4 it shouldn't be near as hard as some of the newer JB and KK things. What do you have?
It is the Kenwood DNN990HD running Android 4.0.4.
I will try and run the binary tool you linked.
Thanks!
Okay so here it goes. I had missing IMEI problem in a custom ROM when not on a samsung base. I had a neatefs (app on android) backup which I tried to restore using HC ktool (Bad idea, I know). It gives me a successfully done message and tells me to reboot. Now my phone is stuck in bootloop no matter what (Stock firmware, wipe data, factory reset nothing works) and the recovery gives the error mentioned in the title.
/efs is unmountable for me. I tried various methods mentioned for S3 and Note such as connecting the phone in ADB mode and following the steps but none of that works.
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
AKAndrew41 said:
Have you tried formatting /system, /boot, /preload /storage/sdcard0 ? From a rooted kernel, of course.
And then trying reflashing the original stock rom.
Click to expand...
Click to collapse
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
ruleh said:
hope this helps http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Click to expand...
Click to collapse
I've tried all that, none helps. I've even installed a busybox as mentioned somewhere else which said that the syntax mke2fs is not available without a busybox. Nothing worked. Still unable to mount efs afterwards.
pHraiL^ said:
I have tried formatting /system and I don't think that formatting /sdcard0 is going to help, it will just increase the burdon of data transfer. As for others, I was afraid it will make more mess than solve any. Are you sure formatting those will not affect anything?
Click to expand...
Click to collapse
I'm pretty sure it won't damage anything, or at least to me didn't. Because whenever I want to reinstall a new ROM I always format everything I've mentioned earlier so I don't find it harmful for the device, as long as you don't have data worth backing up.
Also, wipe dalvik.
If you installed busybox, make sure you uninstall the previous version prin pressing uninstall, and them installing 1.23.1 because for me sometimes it says it's intalled, but after reboot I still have the old one.
After you do that, connect phone to PC and try running
adb shell
Once you do that, give a try to the command
umount -f /efs
even if it says it's umounted, then type
mount /dev/block/mmcblk0p3 /efs
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
Click to expand...
Click to collapse
These two are the commands everyone is talking about the S3 phone having same issue. I tried everything. The first command works and it shows something like:
"The filesystem will be automatically checked every 35 mounts or 180 days, whichever comes first. Use tune2fs -c or -i to override."
For the second line of code when I try, this is what I get:
"It says "mount: can´t find /dev/block/mmcblk0p3 in /etc/fstab"
Now I have also tried adding space and /efs to the second command. It gives me nothing, not even any error. So I presume it works but then when I reboot efs is still messed up. I have no idea what these commands does actually. I think it has something related to re partitioning. Shouldn't the second command line give the same output as the first one? Its been a whole day searching for this thing. I got my phone messed up real bad.
EDIT: One more thing, when I hit the # df command on ADB, it shows 3 drives (/dev, /cache, /emmc) when not in su and 4 when in su (/dev, /cache, /emmc, /system). No where it shows any efs partition. Is there suppose to be any?
EDIT2: After the second line command. Using mount -t following someone's guide I get the efs partition but I think it is way too small. See the attachment. This partition is gone again after reboot.
OH GOD I got it working. After more searching, I found out the the block used for efs storage in S2 is mmcblk0p1 not mmcblk0p3. Phew!
Follow the same commands to make it work. Just rename the block.
Here is a guide which helped me figure out the block: http://www.usoftsmartphone.com/t306464.html
Thanks everyone
im having same trouble now with the S7. the page you share not there anymore. please share me how to figure out the block
Hi
I've unlocked and rooted my phone. Everything works fine, except one little thing. The system partition is still read-only.. I have tried "# mount -o rw,remount /system" in adb on computer and terminal on the phone, but I get an error saying that the operation is not permitted. I find this wery odd, because I have granted superuser permissions. Also, when i type the command "adb devices", there is an empty list. Any suggestions?
Also, I can't install busybox.. Getting an error saying it failed, if anyone know how to fix this too, i will be wery greatfull
Skanin said:
Hi
I've unlocked and rooted my phone. Everything works fine, except one little thing. The system partition is still read-only.. I have tried "# mount -o rw,remount /system" in adb on computer and terminal on the phone, but I get an error saying that the operation is not permitted. I find this wery odd, because I have granted superuser permissions. Also, when i type the command "adb devices", there is an empty list. Any suggestions?
Also, I can't install busybox.. Getting an error saying it failed, if anyone know how to fix this too, i will be wery greatfull
Click to expand...
Click to collapse
This is because of a protection called Sony RIC. You can find some solutions if you make a search.
pec0ra said:
This is because of a protection called Sony RIC. You can find some solutions if you make a search.
Click to expand...
Click to collapse
Okey, thanks