Hi,
I'm a bit of a noob when it comes to Linux but i'm trying to take the Chinese based firware for my device unpack it, modify it and re pack it to make a English starting vanilla build.
Let me begin, i've got a Ubuntu 12.04 install with ext4_utils. I've used a allwinner kitchen to extract the RFSFAT16_SYSTEM_000000000.fex file. I've used simg2img to convert it to original.img and then mounted it as tempdir.
I make changes and all seems ok.
the thing i'm struggling with now is once i've made changes to the output.img through the tempdir through nautilus i try to convert it back to sparse and the conversion completes BUT then when i re pack it into an image and flash the rom doesn't work and gets stuck on boot animation. If if leave the file as ext4 and repack it.. it loads fine but the system image is huge.
If i try to use ./mkuserimg.sh -s /home/Desktop/Android/ext4_utils ./Onda.img ext4 ./temp 512M it creates a .img file with a padlock on it.. (permissions). If i rename this to RFSFAT16_SYSTEM_000000000 and repack the root doesn't boot.
Ive followed this thread and whilst i can get it to work in ext4 i can't get it to work as sparse.
Any help please?
hi,
i have the same problem.
when i mount the repacked image.
original:
drwxr-xr-x 2 root 2000 4096 2012-02-23 09:20 .
drwxr-xr-x 14 root root 4096 1970-01-01 01:00 ..
-rwxr-xr-x 1 root 2000 97144 2012-02-23 09:15 adb
-rwxr-xr-x 1 root 2000 191 2012-02-23 09:02 am
-rwxr-xr-x 1 root 2000 50056 2012-02-23 09:15 applypatch
-rwxr-xr-x 1 root 2000 165772 2012-02-23 09:15 applypatch_static
-rwxr-xr-x 1 root 2000 9920 2012-02-23 09:17 app_process
mount after repack (sparse)
drwxr-xr-x 2 root root 4096 2012-02-23 09:20 .
drwxr-xr-x 14 root root 4096 1970-01-01 01:00 ..
-rw-r--r-- 1 root root 97144 2012-02-23 09:15 adb
-rw-r--r-- 1 root root 191 2012-02-23 09:02 am
-rw-r--r-- 1 root root 50056 2012-02-23 09:15 applypatch
-rw-r--r-- 1 root root 165772 2012-02-23 09:15 applypatch_static
-rw-r--r-- 1 root root 9920 2012-02-23 09:17 app_process
onyone a clue?
Related
Hi, I am using tnt 4.4.0 on my g tablet and I see the system/apps directory with loads of apk's that came packaged with the tnt rom.
My question or issue is this.
When I download an app from the marketplace I can't seem to figure out where it goes.
Using file expert v3.1.0 I searched all over and still no luck.. using this same app I can make backups of my apps by clicking the apps tab and long clicking an app and selecting backup but I would assume the original Zip or APK that I downloaded is on my device somewhere?
Or is it just unzipping from the market and I then have to zip them into a new file with an apk extension?
Innerchaos said:
My question or issue is this.
When I download an app from the marketplace I can't seem to figure out where it goes.
Click to expand...
Click to collapse
To answer this part of your question:
Downloaded apps are either in /data/app or /mnt/asec (this, after much filesystem path-manipulation magic post system boot) for apps moved to SD card:
Code:
$ su
# find /data/ -name *.apk
/data/app/com.google.android.street-1.apk
/data/app/com.google.android.youtube-1.apk
/data/app/com.android.vending-2.apk
/data/app/com.curvefish.widgets.wifionoff.donate-1.apk
/data/app/com.jasoncalhoun.android.systeminfowidget-1.apk
/data/app/com.facebook.katana-1.apk
/data/app/com.dataviz.docstogoapp-1.apk
/data/app/org.zooper.acw-1.apk
/data/app/jackpal.androidterm-1.apk
/data/app/com.curvefish.apps.appremover-1.apk
/data/app/com.curvefish.widgets.bluetoothonoff-1.apk
/data/app/com.noshufou.android.su-1.apk
/data/app/org.adwfreak.launcher-1.apk
#
# find /mnt/asec/ -name *.apk
/mnt/asec/com.rovio.angrybirdsrio-2/pkg.apk
/mnt/asec/com.google.android.apps.maps-2/pkg.apk
/mnt/asec/com.alensw.PicFolder-1/pkg.apk
/mnt/asec/com.farproc.wifi.analyzer-2/pkg.apk
/mnt/asec/com.redirectin.rockplayer.android.unified-2/pkg.apk
/mnt/asec/com.speedsoftware.rootexplorer-2/pkg.apk
/mnt/asec/com.google.android.voicesearch-1/pkg.apk
/mnt/asec/com.dataviz.docstogo-2/pkg.apk
/mnt/asec/net.androidcomics.acv-1/pkg.apk
/mnt/asec/com.rovio.angrybirdsseasons-1/pkg.apk
/mnt/asec/com.seesmic-1/pkg.apk
/mnt/asec/com.rovio.angrybirds-1/pkg.apk
/mnt/asec/com.adobe.flashplayer-1/pkg.apk
/mnt/asec/com.google.android.gm-1/pkg.apk
/mnt/asec/com.google.android.stardroid-1/pkg.apk
As to your other questions, I don't have definitive answers, but, looking inside those 2 directories (/data, and, /mnt/sdcard after you've unmount it) might prove instructive.
My mnt/asec directory is empty as well
Innerchaos said:
My mnt/asec directory is empty as well
Click to expand...
Click to collapse
Did you run the find command as root? (Or, have root permissions when you looked inside /mnt/asec?)
/mnt/asec might also be empty simply because you haven't moved any apps to the SD card.
The actual .apk files are in /mnt/sdcard/.android_secure/, but with a .asec extension instead of .apk. You'll have to unmount /mnt/sdcard in Settings > Storage first, then mount it again manually for you to see the files in that directory:
Code:
$ su
# mount -r -t vfat /dev/block/mmcblk3p1 /mnt/sdcard
# ls -l /mnt/sdcard/.android_secure/
total 124216
-rwxr-xr-x 1 root root 13870592 Jun 8 23:17 com.adobe.flashplayer-2.asec
-rwxr-xr-x 1 root root 2161664 May 30 03:37 com.alensw.PicFolder-1.asec
-rwxr-xr-x 1 root root 7483904 May 20 08:44 com.dataviz.docstogo-2.asec
-rwxr-xr-x 1 root root 2161664 Jun 3 03:24 com.farproc.wifi.analyzer-2.asec
-rwxr-xr-x 1 root root 8548352 May 26 22:18 com.google.android.apps.maps-2.asec
-rwxr-xr-x 1 root root 4290560 May 17 10:22 com.google.android.gm-1.asec
-rwxr-xr-x 1 root root 4290560 May 17 10:21 com.google.android.stardroid-1.asec
-rwxr-xr-x 1 root root 4290560 May 17 10:22 com.google.android.voicesearch-1.asec
-rwxr-xr-x 1 root root 9612800 May 17 10:22 com.redirectin.rockplayer.android.unified-2.asec
-rwxr-xr-x 1 root root 21321728 May 17 10:21 com.rovio.angrybirds-1.asec
-rwxr-xr-x 1 root root 19192832 May 19 19:58 com.rovio.angrybirdsrio-2.asec
-rwxr-xr-x 1 root root 22386176 May 17 10:21 com.rovio.angrybirdsseasons-1.asec
-rwxr-xr-x 1 root root 3226112 May 17 10:22 com.seesmic-1.asec
-rwxr-xr-x 1 root root 2161664 May 24 20:11 com.speedsoftware.rootexplorer-2.asec
-rwxr-xr-x 1 root root 2161664 May 28 16:03 net.androidcomics.acv-1.asec
#
# umount /mnt/sdcard
You won't see those files when the SD card is mounted normally by Android. Then, the /mnt/sdcard/.android_secure directory will appear to be empty.
You might also have to use /dev/block/mmcblk2p1 instead of /dev/block/mmcblk3p1 in the mount command above, if you run a Gingerbread-based ROM.
Hi all,
I've posted a question in the Galaxy S2 forums but realise it's probably a more generic issue.
http://forum.xda-developers.com/showthread.php?p=17892549
I've broken my screen and it no longer responds to touch. I can view it using an MHL > HDMI adapter but without any touch input I can't get past the pattern unlock.
I was hoping to pair a bluetooth mouse using adb or somehow so I can then use the mouse to pattern unlock and generally use my phone.
If anyone thinks they might be able to help with advice or techniques, please let me know!
Many thanks!
I think you can send touch events via adb, dig roung Google and you should find out how.
Sorry, I never tried it but I'm pretty sure its possible.
Sent from my HTC Desire using XDA App
It turns out that it's possible but it's not documented at all from what I can see.
My main hurdle at the moment though is that I do not have debugging enabled in normal mode so even if I worked out the correct sequence, I wouldn't be able to push it to the phone in normal mode through adb...
Also, it seems my sqlite3 is missing?!
If your rom supports init.d scripts you could add a script that starts the adb server on startup from recovery.
Sent from my HTC Desire using XDA App
That's a grand idea. Yeah there is an init.d directory so seems fine.
I know adb start-server from the pc side, however there are a few folders etc with adb in them and I've not found which is the right one to kick of debug mode. Seeing as I can't actually see the screen it's hard to play with trial and error Any suggestions on that would be great.
Code:
/system/etc/init.d # find / | grep adb | while read in
> do
> echo "${in}: "
> ls -lrt $in
> done
/dev/android_adb_enable:
crw-rw---- 1 adb adb 10, 57 Sep 27 12:06 /dev/android_adb_enable
/dev/android_adb:
crw-rw---- 1 adb adb 10, 58 Sep 27 12:06 /dev/android_adb
/sys/devices/virtual/misc/android_adb:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 uevent
drwxr-xr-x 2 root root 0 Sep 27 12:06 power
lrwxrwxrwx 1 root root 0 Sep 27 12:12 subsystem -> ../../../../class/misc
-r--r--r-- 1 root root 4096 Sep 27 12:12 dev
/sys/devices/virtual/misc/android_adb/uevent:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 /sys/devices/virtual/misc/android_adb/uevent
/sys/devices/virtual/misc/android_adb/dev:
-r--r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb/dev
/sys/devices/virtual/misc/android_adb/subsystem:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/devices/virtual/misc/android_adb/subsystem -> ../../../../class/misc
/sys/devices/virtual/misc/android_adb/power:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 wakeup
-rw-r--r-- 1 root root 4096 Sep 27 12:12 control
/sys/devices/virtual/misc/android_adb/power/control:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb/power/control
/sys/devices/virtual/misc/android_adb/power/wakeup:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb/power/wakeup
/sys/devices/virtual/misc/android_adb_enable:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 uevent
drwxr-xr-x 2 root root 0 Sep 27 12:06 power
lrwxrwxrwx 1 root root 0 Sep 27 12:12 subsystem -> ../../../../class/misc
-r--r--r-- 1 root root 4096 Sep 27 12:12 dev
/sys/devices/virtual/misc/android_adb_enable/uevent:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 /sys/devices/virtual/misc/android_adb_enable/uevent
/sys/devices/virtual/misc/android_adb_enable/dev:
-r--r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb_enable/dev
/sys/devices/virtual/misc/android_adb_enable/subsystem:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/devices/virtual/misc/android_adb_enable/subsystem -> ../../../../class/misc
/sys/devices/virtual/misc/android_adb_enable/power:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 wakeup
-rw-r--r-- 1 root root 4096 Sep 27 12:12 control
/sys/devices/virtual/misc/android_adb_enable/power/control:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb_enable/power/control
/sys/devices/virtual/misc/android_adb_enable/power/wakeup:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/misc/android_adb_enable/power/wakeup
/sys/devices/virtual/usb_composite/adb:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 uevent
drwxr-xr-x 2 root root 0 Sep 27 12:06 power
lrwxrwxrwx 1 root root 0 Sep 27 12:12 subsystem -> ../../../../class/usb_composite
-rw-r--r-- 1 root root 4096 Sep 27 12:12 enable
/sys/devices/virtual/usb_composite/adb/uevent:
-rw-r--r-- 1 root root 4096 Sep 27 12:06 /sys/devices/virtual/usb_composite/adb/uevent
/sys/devices/virtual/usb_composite/adb/subsystem:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/devices/virtual/usb_composite/adb/subsystem -> ../../../../class/usb_composite
/sys/devices/virtual/usb_composite/adb/power:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 wakeup
-rw-r--r-- 1 root root 4096 Sep 27 12:12 control
/sys/devices/virtual/usb_composite/adb/power/control:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/usb_composite/adb/power/control
/sys/devices/virtual/usb_composite/adb/power/wakeup:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/usb_composite/adb/power/wakeup
/sys/devices/virtual/usb_composite/adb/enable:
-rw-r--r-- 1 root root 4096 Sep 27 12:12 /sys/devices/virtual/usb_composite/adb/enable
/sys/class/misc/android_adb:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/class/misc/android_adb -> ../../devices/virtual/misc/android_adb
/sys/class/misc/android_adb_enable:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/class/misc/android_adb_enable -> ../../devices/virtual/misc/android_adb_enable
/sys/class/usb_composite/adb:
lrwxrwxrwx 1 root root 0 Sep 27 12:12 /sys/class/usb_composite/adb -> ../../devices/virtual/usb_composite/adb
/sbin/adbd:
-rwxr-xr-x 1 system graphics 118004 Jul 11 05:25 /sbin/adbd
Think I've found it in /sbin/adbd ...
I've seem many threads about it, but couldn't really find a solution.
I just pulled out my sdcard to do some updates in my rom (I was running Th3Bill's miui v4).
I've copied a couple of .zips to try, and when I inserted back, my I /sdcard wasn't mounting.
I've tried to format in windows (fast and normal mode); I've putted this very same card in my tabled (xoom2 me) and it was working fine.
I've tried to run format /sdcard in cwm. same error mounting;
I went to advance > show log:
CWM-based Recovery v5.0.2.7-atrix5
Error mounting /sdcard!
ro.bootloader=unknown
ro.hardware=olympus
ro.revision=33776
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand. file not found...
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory)
W:failed to mount /dev/block/mmcblk1 (No such file or directory)
Error mounting /sdcard!
I've tried some stuff on adb (someone mentioned it, not sure what it means):
C:\Users\Neon\Documents\Android\Auto stuff>adb shell ln -n -s /data/media /sdcar
d
ln: /sdcard/media: File exists
C:\Users\Neon\Documents\Android\Auto stuff>adb shell ls -a -l
drwxr-xr-x 21 root root 0 Aug 7 02:15 .
drwxr-xr-x 21 root root 0 Aug 7 02:15 ..
drwxr-xr-x 2 root root 0 Aug 7 02:15 boot
drwxrwx--x 5 system cache 4096 Aug 7 01:43 cache
drwxrwx--x 2 root root 0 Jan 1 1970 data
drwxr-xr-x 2 root root 0 Aug 7 02:15 datadata
-rw-r--r-- 1 root root 3875 Jan 1 1970 default.prop
drwxr-xr-x 9 root root 3260 Aug 7 02:15 dev
drwxr-xr-x 2 root root 0 Aug 7 02:15 emmc
drwxr-xr-x 2 root root 0 Aug 7 02:15 etc
-rwxr-x--- 1 root root 94404 Jan 1 1970 init
-rwxr-x--- 1 root root 783 Jan 1 1970 init.rc
drwxr-xr-x 2 root root 0 Aug 7 02:15 osh
drwxr-xr-x 2 root root 0 Aug 7 02:15 pds
drwxr-xr-x 2 root root 0 Aug 7 02:15 preinstall
dr-xr-xr-x 95 root root 0 Jan 1 1970 proc
drwxr-xr-x 3 root root 0 Jan 1 1970 res
drwx------ 2 root root 0 Sep 5 2011 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxr-xr-x 2 root root 0 Aug 7 02:15 sd-ext
drwxr-xr-x 2 root root 0 Aug 7 02:16 sdcard
drwxr-xr-x 14 root root 0 Jan 1 1970 sys
drwxr-xr-x 3 root root 0 Jan 1 1970 system
drwxr-xr-x 2 root root 0 Aug 7 02:15 tmp
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 9731 Jan 1 1970 ueventd.olympus.rc
-rw-r--r-- 1 root root 4078 Jan 1 1970 ueventd.rc
What do I need to do?
Maybe is there some pins not working in my phone? Because I've tried another micro sd and got same error!
Thanks in advance!
Sounds like you really do have some issues with the built-in card slot. Try inspecting it visually, maybe there is some visible damage. Other than that, I'm not sure what can you do... Maybe claim warranty on it?
You should also never run random commands if you don't have at least some idea what they do. Those commands have nothing to do with fixing the sdcard, luckily for you they didn't work.
ravilov said:
Sounds like you really do have some issues with the built-in card slot. Try inspecting it visually, maybe there is some visible damage. Other than that, I'm not sure what can you do... Maybe claim warranty on it?
You should also never run random commands if you don't have at least some idea what they do. Those commands have nothing to do with fixing the sdcard, luckily for you they didn't work.
Click to expand...
Click to collapse
Well, Actually those commands weren't trying to fix it, and I know what ls does, I wasn't much sure about how ln works, but I know that it wouldn't damage my stuff.
I just checked some stuff here, it seems to be a hardware issue indeed, when I put my nail under the card, it reads! Unfortunately I can't claim warranty. I bought this phone used, via ebay, like and year ago, from a seller in USA (I'm in Brazil). I'll try to arrange some workaround (maybe some paper under it might work,...) and hope it works properly.
Hello XDA-Developers!
I want to install Back Track 5 ARM in my AllWinner A10 based tablet, I followed the lesson for Galaxy and I downloaded the boot script for Galaxy and the bt5.img(3.25G). I changed some of the codes to launch BT5 in external sdcard and suit my ROM,then launched it, only to find some errors. Well, the source code of the boot script(modified by myself to suit my device) like this:
perm=$(id|busybox cut -b 5)
if [ "$perm" != "0" ];then echo "This Script Needs Root! Type : su";exit;fi
mount -o remount,rw /dev/block/mmcblk0p1 /system
export kit=/mnt/extsd/BT5
export bin=/system/bin
export mnt=/mnt
mkdir -p $mnt
export PATH=$bin:/usr/bin:/usr/local/bin:/usr/sbin:/bin:/usr/local/sbin:/usr/games:$PATH
export TERM=linux
export HOME=/
if [ -b /dev/loop2 ]; then
echo "Loop device exists"
else
busybox mknod /dev/loop2 b 7 0
fi
busybox mount -o loop,noatime -t extsd $kit/bt5.img $mnt
busybox mount --bind /dev/pts $mnt/dev/pts
busybox mount --bind /proc $mnt/proc
busybox mount --bind /sys $mnt/sys
busybox sysctl -w net.ipv4.ip_forward=1
echo "nameserver 8.8.8.8" > $/etc/resolv.conf
echo "127.0.0.1 localhost bt5" > $/etc/hosts
busybox chroot $/bin/bash
echo "Shutting down BackTrack ARM For Xoom"
umount $/dev/pts
umount $/proc
umount $/sys
umount $mnt
when I launch the script(bootbtV) in Terminal Emulator, only to find some errors like this:
[email protected]:/ $ su
[email protected]:/ # cd mnt/extsd/BT5
[email protected]:/mnt/extsd/BT5 # sh bootbtV
Loop device exists
mount: mounting /dev/loop8 on /mnt failed: No such device
mount: mounting /dev/pts on /mnt/dev/pts failed: No such file or directory
mount: mounting /proc on /mnt/proc failed: No such file or directory
mount: mounting /sys on /mnt/sys failed: No such file or directory
net.ipv4.ip_forward = 1
bootbtV[23]: can't create $/etc/resolv.conf: No such file or directory
bootbtV[24]: can't create $/etc/hosts: No such file or directory
chroot: can't change root directory to $/bin/bash: No such file or directory
Shutting down BackTrack ARM For Xoom
failed: No such file or directory
failed: No such file or directory
failed: No such file or directory
failed: Invalid argument
1|[email protected]:/mnt/extsd/BT5 #
Well, In my opinion, according to the errors "No such file or directory", I think it is the difference between my device and Galaxy that causes the errors. In my device, the file structure is different from what the boot script means, such is the file structure of my device's root directory:
drwxr-xr-x root root 2013-01-16 11:22 acct
drwxrwx--- system cache 2013-01-16 09:51 cache
dr-x------ root root 2013-01-16 11:22 config
lrwxrwxrwx root root 2013-01-16 11:22 d -> /sys/kernel/debug
drwxrwx--x system system 2013-01-13 17:14 data
-rw-r--r-- root root 116 1970-01-01 08:00 default.prop
drwxr-xr-x root root 2013-01-16 11:27 dev
lrwxrwxrwx root root 2013-01-16 11:22 etc -> /system/etc
-rwxr-x--- root root 105268 1970-01-01 08:00 init
-rwxr-x--- root root 2344 1970-01-01 08:00 init.goldfish.rc
-rwxr-x--- root root 19030 1970-01-01 08:00 init.rc
-rwxr-x--- root root 2644 1970-01-01 08:00 init.sun4i.rc
-rwxr-x--- root root 2230 1970-01-01 08:00 init.sun4i.usb.rc
-rwxr-x--- root root 1637 1970-01-01 08:00 init.trace.rc
-rwxr-x--- root root 3915 1970-01-01 08:00 init.usb.rc
-rwxr-x--- root root 1536000 1970-01-01 08:00 initlogo.rle
drwxrwxr-x root system 2013-01-16 11:22 mnt
-rw-r--r-- root root 782728 1970-01-01 08:00 nand.ko
dr-xr-xr-x root root 1970-01-01 08:00 proc
drwx------ root root 2012-10-11 13:57 root
drwxr-x--- root root 1970-01-01 08:00 sbin
lrwxrwxrwx root root 2013-01-16 11:22 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2013-01-16 11:22 sys
drwxr-xr-x root root 2013-01-13 17:59 system
-rw-r--r-- root root 272 1970-01-01 08:00 ueventd.goldfish.rc
-rw-r--r-- root root 3879 1970-01-01 08:00 ueventd.rc
-rw-r--r-- root root 1313 1970-01-01 08:00 ueventd.sun4i.rc
lrwxrwxrwx root root 2013-01-16 11:22 vendor -> /system/vendor
I think, the only way to launch BT5 in my device successfully is to modify the boot script so that it can suit my device, especially the file structure. But I am a green hand in Linux, I don't know what does some of the codes mean, if you are good at Linux script, would you please give me some advice?
Thank you very much!
My phone felt down and lost it network.
Everything else functions 100% (wifi,gps,audio,video,bluetooth, camera, etc)
when I dial *#06# I got what you can see on the attached screenshot.
Tried many-many things from this forum and some others. Nothing.
my /efs folder looks as follows:
[email protected]:/ # ls -la /efs/
drwxrwxr-x root root 2013-08-21 12:59 .files
-rwx------ radio radio 1048576 2010-12-31 17:00 .nv_core.bak
-rwx------ radio radio 32 2010-12-31 17:00 .nv_core.bak.md5
-rwx------ radio radio 2097152 2010-12-31 17:00 .nv_data.bak
-rwx------ radio radio 32 2010-12-31 17:00 .nv_data.bak.md5
-rw-rw-rw- radio radio 1 2010-12-31 17:00 .nv_state
drwxrwxr-x radio system 2013-08-21 12:59 bluetooth
-rw-rw-rw- system system 6 2013-08-19 18:22 calibration_data
-rw-r--r-- system system 9 2000-01-01 02:05 cryptprop_applied_result
-rw-r--r-- root root 1 2000-01-01 02:03 cryptprop_essiv
-rw-r--r-- system system 5 2011-12-20 15:51 cryptprop_lock_pattern_autolock
-rw-r--r-- system system 6 2011-11-17 09:58 cryptprop_lock_pattern_tactile_feedback_enabled
-rw-r--r-- system system 5 2011-11-18 17:15 cryptprop_lock_pattern_visible_pattern
-rw-r--r-- system system 10 2011-12-25 20:25 cryptprop_lockscreen.lockoutattemptdeadline
-rw-r--r-- system system 6 2011-12-20 15:51 cryptprop_lockscreen.password_type
-rw-r--r-- system system 5 2011-12-20 15:51 cryptprop_lockscreen.patterneverchosen
-rw-r--r-- root root 5 2011-12-20 15:44 cryptprop_onetimeboot
-rw-r--r-- system system 3 2011-12-20 15:50 cryptprop_persist.sys.language
-rw-r--r-- system system 12 2000-01-01 02:00 cryptprop_persist.sys.timezone
-rw-r--r-- root root 1 2000-01-01 02:03 cryptprop_rebootMode
-rw-r--r-- root root 3 2011-12-20 15:44 cryptprop_securewipedata
drwx------ system system 2013-08-21 12:59 dmp
-rw-rw-rw- system system 256 2011-11-17 09:58 edk_d
-rw-rw-rw- system system 256 2011-11-17 09:58 edk_p
drwxrwxr-x radio radio 2013-08-21 12:59 imei
drwx------ root root 2013-08-21 12:53 lost+found
-rw-rw-rw- radio radio 1205 2010-12-31 17:00 nv.log
-rwx------ radio radio 2097152 2010-12-31 17:00 nv_data.bin
-rwx------ radio radio 32 2010-12-31 17:00 nv_data.bin.md5
-rwxrwxr-- radio radio 880 2010-12-31 17:02 redata.bin
drwxrwxr-x radio system 2013-08-21 12:59 wifi
Click to expand...
Click to collapse
Any chance to get back the mobile network?
thanks!
If you say you've 'tried everything' & don't have an 'good' EFS backup (either made automatically by a kernel like Siyah, or one you took manually with the several apps available for same) then you don't have much choice other than to take it to a service centre or a local mobile shop. Or you could buy a RIFF box, but unless you know how to use it/are prepared to learn & be careful, you'll end up needing a service centre trip if you get it wrong plus you'll have paid for something you'll likely never use again.
Me too
But i flash zsmg2 and all fine worked but my language is farsi it is honkong
I cannot downgrade or install any stock rom
What is your rom?
how to know my phone locked ?
only i9070zsmg2 worked in my phone