Hi all,
I got a 2nd-hand i5700 and I'm trying to upgrade it to 2.3 from 2.2.
I have noticed that its IMEI shows all zero so that I'm guessing its EFS partition has corrupted.
I follow the EFS restoration method thread from tom3q and I get the error message
Code:
# cat /dev/stl10 > /sdcard/efs.stl
cat /dev/stl10 > /sdcard/efs.stl
cat: can't open '/dev/stl10': Invalid argument
#
I'm looking for help to solve this problem.
Thank you.
Related
Hi guys,
A friend of mine recently rooted his I9505 and tried to install a custom Rom.
He made an Nandroid backup of his Stock rom but TWRP wasn't able to mount /efs.
So he ignored it and made a Backup without checking /efs.
As he installed a custom Rom he did something wrong and wasn't able to boot system.
So he went back to stock rom.
The Problem now is that his /efs folder is empty and he has no lockscreen and powermenu.
But the strange thing is that he has no problems with IMEI or Baseband.
Is it somehow possible to get his /efs files back?
Or at least get his lockscreen an powermenu back working?
He would be even happy with and alternative lockscreen and powermenu. maybe a app?
I hope someone can help us
Thank you very much in advance for your answers
SOLVED:
I tried many different methods so i don't really know which one worked.
But here are several methods you can try if you have the same problem:
Method 1:
Code:
su
busybox mount /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Method 2:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Method 3:
Code:
su
mount -w -t ext4 /dev/block/mmcblk0p10
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Try them all and one of them should work
Try a factory reset. If that doesn't work odin to stock should get you fixed up
Sent from my Nexus 10
9233 said:
Hi guys,
A friend of mine recently rooted his I9505 and tried to install a custom Rom.
He made an Nandroid backup of his Stock rom but TWRP wasn't able to mount /efs.
So he ignored it and made a Backup without checking /efs.
As he installed a custom Rom he did something wrong and wasn't able to boot system.
So he went back to stock rom.
The Problem now is that his /efs folder is empty and he has no lockscreen and powermenu.
But the strange thing is that he has no problems with IMEI or Baseband.
Is it somehow possible to get his /efs files back?
Or at least get his lockscreen an powermenu back working?
He would be even happy with and alternative lockscreen and powermenu. maybe a app?
I hope someone can help us
Thank you very much in advance for your answers
Click to expand...
Click to collapse
efs is not empty. you can not see inside because it is not mounted.
root the device, install terminal emulator. type:
Code:
su
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
samersh72 said:
efs is not empty. you can not see inside because it is not mounted.
root the device, install terminal emulator. type:
Code:
su
mount /efs
mount -o remount,rw /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Click to expand...
Click to collapse
mount /efs is not working. I'm getting this Error Message:
http://dl.xda-developers.com/attachdl/8c9fb4bc3dc504c869fd2aebc109f0df/523b4bef/2/2/6/8/9/0/0/IMG-20130919-WA0003.jpg
9233 said:
mount /efs is not working. I'm getting this Error Message:
http://dl.xda-developers.com/attachdl/8c9fb4bc3dc504c869fd2aebc109f0df/523b4bef/2/2/6/8/9/0/0/IMG-20130919-WA0003.jpg
Click to expand...
Click to collapse
try without mounting: "su" then the "echo"
if not try mounting with these commands:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
if not, ignore mke2fs...... line
samersh72 said:
try without mounting: "su" then the "echo"
if not try mounting with these commands:
Code:
su
mke2fs /dev/block/mmcblk0p10
mount -w -t ext4 /dev/block/mmcblk0p10
reboot
if not, ignore mke2fs...... line
Click to expand...
Click to collapse
Thank you.
I don't have the phone here so i'll try it tomorrow and see what happens.
Your mount command didn't work because you are using the /system/bin/mount that is a part of Android. This version must get the device name and the mount point, you cannot omit one of them (with busybox mount you can omit one or the other).
I had the EXACT problem and already started a thread.
There was a lot of help given to me, try reading through my thread mate.
http://forum.xda-developers.com/showthread.php?t=2388663
In the end it turned out my EFS partition was so corrupt it had to go to service centre.
Sent from my GT-I9505 using XDA Premium HD app
Hi guys,
I tried it with the following and it works!!!
Code:
su
busybox mount /efs
echo -n ON > /efs/FactoryApp/keystr
echo -n ON > /efs/FactoryApp/factorymode
reboot
Thank you all for your Help and have a nice day!
Hi folks,
I am trying to mount an ugly path to the nicer "/sdcard/external_sd".
Since this is not working with this solution, I tried to understand access rights - and failed miserably.
Code:
echo ------------------------------------------
echo Secondary_Storage is $SECONDARY_STORAGE . Have look what is there:
ls $SECONDARY_STORAGE && "/*.*"
echo ...done
# echo Breaks any existing Bind mount to avoid creating duplicate Bind entries. A "failed" response is acceptable as is no response.
# umount /sdcard/external_sd
ls /sdcard/external_sd/*.*
#echo ------------------------------------------
#echo execute Micro SD mount - card must be plugged in or Invalid Argument error will occur.
# mount -o bind /storage /sdcard/external_sd
#echo I guess I am done
#echo Now: Did it work?
# ls /storage/sdcard1:/storage/usbdisk0/*.*
Attached screenshot proves that (exFAT, 64 GB) external card is readable.I can rw access no problem via /storage/sdcard1:/storage/usbdisk0/ (the ugly link I want to get rid of)
1. Why is there an error after(!) successfully displaying the contents of the external SD card's directory listing?
2. Why is /sdcard/external_sd/*.* not displayed? This directory was deleted and re-created by root, set CHMOD 777 (result is only 755! why this?) and copied some files via FTP. Files are there OK, dan be seen by ES Datei Explorer and others.
I am using CM10.1-AOSP_fuse-mountsd_6.4_HMkX2.ZIP (found here: http://forum.xda-developers.com/showthread.php?t=2155363) and have read about "access right problems with fuse" here.
My next try was to follow "To custom-map mountpoints, create a ".mounthere" file in the root of each partition." (grey "EXPERTS" box here). Failed, will post this there...
Unhappy, but hoping...
Sam
Hi!
I just upgraded to 4.4.3 and lost root access. The /system/xbin/su binary is still present, but does nothing:
Code:
[email protected]:/ $ which su
/system/xbin/su
[email protected]:/ $ ls -l /system/xbin/su
-rwsr-sr-x root shell 104576 2013-12-13 19:17 su
[email protected]:/ $ su
1|[email protected]:/ $ whoami
whoami: unknown uid 2000
I booted into fast boot mode. The information there says (if it is of any help):
Code:
FASTBOOT MODE
PRODUCT NAME - grouper
VARIANT - grouper
HW VERSION - ER3
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SERIAL NUMBER - XXX
SIGNING - not defined yet
LOCK STATE - UNLOCKED
And I can't seem to boot into recovery mode - it just shows "android" lying on his back with his tummy open with a red triangle (with exclamation mark) .
I guess the 4.3 update changed some stuff. I'm on a Mac. What can I do to regain root access?
Regards,
Miha.
Further to that, I stupidly also accepted the update - CWM seems to have been wiped, and when I try to flash it, I get the following error. The weird (and gratifying) thing is that other than that, the tablet seems to operating fine - for which I'm grateful - is there anything I can try to sort it out?
I was completely stock (but rooted with CWM 6.0.4.3).
Code:
goatees-MacBook-Air:platform-tools goatee$ fastboot flash recovery recovery-clockwork-touch-6.0.4.3-grouper.img
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
ERROR: usb_read failed with status e00002ed
ERROR: usb_read failed with status e000404f
sending 'recovery' (7318 KB)...
ERROR: usb_read failed with status e000404f
FAILED (status read failed (No such file or directory))
finished. total time: 3.057s
mihaval said:
Hi!
I just upgraded to 4.4.3 and lost root access. The /system/xbin/su binary is still present, but does nothing:
Code:
[email protected]:/ $ which su
/system/xbin/su
[email protected]:/ $ ls -l /system/xbin/su
-rwsr-sr-x root shell 104576 2013-12-13 19:17 su
[email protected]:/ $ su
1|[email protected]:/ $ whoami
whoami: unknown uid 2000
I guess the 4.3 update changed some stuff. I'm on a Mac. What can I do to regain root access?
Regards,
Miha.
Click to expand...
Click to collapse
Ok, so I've resolved my problem. I don't know if it's coincidence, but this time when I tried to reflash cwm
Instead of doing
Code:
fastboot flash recovery recovery-blah-grouper.img
I did this - and it worked
Code:
./fastboot flash recovery recovery-blah-grouper.img
This time, it flashed successfully, which let me reinstall root (by flashing the Super SU .zip)
I'm in OS X, (used *nix for the past 18 years or so), and it was successfully starting the fastboot binary before - so perhaps it's just a coincidence. The only other thing I did different was that my USB keyboard wasn't plugged in.
---------- Post added at 09:14 PM ---------- Previous post was at 09:06 PM ----------
And in fact, if that doesn't work for you - towelroot should do the job. See http://forum.xda-developers.com/showthread.php?t=2783157 or http://www.towelroot.com
goatee said:
Ok, so I've resolved my problem. I don't know if it's coincidence, but this time when I tried to reflash cwm
Click to expand...
Click to collapse
I confirm that it works for me too. CWM asked me whether to fix su: "Possible root access lost. Fix su?" and I chose yes (the first time and now, when I reflashed recovery too). And that actually breaks it. On second run, I chose no, and su is working again.
I saw reports about 4.4.4 update coming - we'll what that brings us...
Miha
Ah. . . I wonder why the SWM root fix didn't work correctly. Anyhow, glad you're also back to normal .
mihaval said:
I confirm that it works for me too. CWM asked me whether to fix su: "Possible root access lost. Fix su?" and I chose yes (the first time and now, when I reflashed recovery too). And that actually breaks it. On second run, I chose no, and su is working again.
I saw reports about 4.4.4 update coming - we'll what that brings us...
Miha
Click to expand...
Click to collapse
HELP! I am tried repair the Data Partition it fails saying ,
/sbin/e2fsck -fp /dev/block/mmcblk0p40 process ended with Error: 1
unable to repair Data.
kindly now guide me what should I do.
Hi all,
I tried to identify partitions on the device (userdata, vendor, system, etc.)
Device: Oneplus2 (unrooted).
After
Code:
adb shell
ls -l /dev/block/by-name
It returns
Code:
/dev/block/by-name: Permission denied
I also tried
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
The same result followed.
So
1. How to solve this "permission denied" problem?
2. Would it nevertheless be possible identify partitions on an unrooted device?
Thanks in advance.
Cheers,
Wen