[Q] /data filesystem problem - Moto G Q&A, Help & Troubleshooting

In the ADB shell as root I get the following results
Code:
/data # ls -la dalvik-cache/
ls -la dalvik-cache
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
ls: dalvik-cache/[email protected]@[email protected]: No such file or directory
drwxrwx--x 4 root root 57344 Mar 14 12:36 .
drwxrwx--x 41 system system 4096 Mar 15 07:45 ..
drwx--x--x 2 root root 53248 Mar 15 07:45 arm
drwx--x--x 2 system system 20480 Mar 14 20:56 profiles
/data # ls -la property/
ls -la property
ls: property/persist.atvc.allow_res_core: No such file or directory
ls: property/persist.atvc.allow_all_core: No such file or directory
ls: property/persist.radio.adb_log_on: No such file or directory
drwx------ 2 root root 4096 Mar 15 08:25 .
drwxrwx--x 41 system system 4096 Mar 15 07:45 ..
-rw------- 1 root root 1 Jan 2 2009 persist.atvc.adb
-rw------- 1 root root 1 Mar 15 07:45 persist.atvc.allow_res_panic
....
This doesn't seem right. Since /data is an F2FS partition I can't fsck it.
Any ideas on how to get rid of those errors?
What I've tried:
listing (ls), removing, stat'ing, fsck.f2fs'ing, nothing works from the shell.
Is there possibly a better forum to ask this question? I have plenty *nix experience, but am stumped on how to solve this. Normally filechecking tools are necessary but a good one for F2FS doesn't seem available (on Android).

Which ROM are you running on your phone? I'm not sure if that makes a difference since GPE uses ext4 and stock uses f2fs.

I've only run stock KK and L.
In the end I could only solve it by completely wiping the /data partition with dd and reformatting with mkfs.f2fs.
Done from adb shell in recovery.
I dunno how I ended up in this situation but it's solved now.
Running the Brzilian XT1032 ROM now, will reinstall sometime when the EU image is available.
Sent from my XT1032 using XDA Free mobile app

Quark^2 said:
I've only run stock KK and L.
In the end I could only solve it by completely wiping the /data partition with dd and reformatting with mkfs.f2fs.
Done from adb shell in recovery.
I dunno how I ended up in this situation but it's solved now.
Running the Brzilian XT1032 ROM now, will reinstall sometime when the EU image is available.
Sent from my XT1032 using XDA Free mobile app
Click to expand...
Click to collapse
Could you give a link to the file and a list of commands you used?
I'm probably stuck in the same situation as you were.

Related

[Q] Building Harmony/GTablet CyanogenMod from source?

I'm getting pretty far along building CyanogenMod for the GTablet on Mandriva Linux x86_64, I pulled the latest source and did the following from a bash shell:
Code:
cd device/nvidia/harmony
./extract-files.sh
cd ../../..
cp ./vendor/cyanogen/products/cyanogen_harmony.mk ./buildspec.mk
. build/envsetup.sh
lunch cyanogen_harmony-eng
cd vendor/cyanogen
./get-rommanager
./get-google-files -v hdpi
cd ../..
make -j6 CYANOGEN_WITH_GOOGLE=true bacon
I'm wondering if I should have gotten the mdpi-tegra google apps instead? get-google-files requires the following change if so:
Code:
FILENAME=["gapps-hdpi-20101114-signed.zip","gapps-mdpi-20101020-signed.zip","gapps-mdpi-tiny-20101020-signed.zip","gapps-mdpi-tegra-20101020-signed.zip"]
VERSIONS=["hdpi","mdpi","mdpi-tiny","mdpi-tegra"]
then do:
Code:
./get-google-files -v mdpi-tegra
Has anyone gotten this working?
I'm almost 100% positive that you cannot use HDPI gapps. MDPI gapps are the ones that you need to use for CM6.1 for this device.
Good to know, I just got it built but now clockwork doesn't see the update-cm-6.1.0-Beta4-Harmony-signed.zip on the sdcard?!? I can mount and verify the .zip from linux, the file should be in the root directory, correct?
Weird, I tried copying over the clockwork update.zip and recovery/ dirs, now I can see LOST.DIR but nothing else from the recovery install from sdcard option...
Dumb question....but did you mount the sdcard? I've seen that happen if the card is not mounted to /sdcard
Possible /sdcard and /sdcard2 mount confusion?
Nope, from adb shell I can see /mnt/sdcard with the files (which match md5 checksums):
Code:
# ls -lF /mnt/sdcard
d---rwxr-x 3 system sdcard_r 4096 Jan 25 06:51 Android/
d---rwxr-x 2 system sdcard_r 4096 Jan 25 06:51 LOST.DIR/
d---rwxr-x 2 system sdcard_r 4096 Oct 29 2010 recovery/
----rwxr-x 1 system sdcard_r 83928334 Dec 5 2010 update-cm-6.1.0-Beta4-Harmony-signed.zip*
----rwxr-x 1 system sdcard_r 4003082 Nov 9 2010 update.zip*
Is there anything special that needs to be done with permissions? I did have to repartition the sd card, somehow it got really messed up when I tried formatting it from the tablet's setup app.
edit: I found out that the .zip needs to be on /mnt/emmc (which I guess shows up as sdcard from clockwork recovery).

New OTA Update (Telstra 1.89)

Seems Telstra users got a 1.89 OTA update today :highfive:
I'll see if an RUU is available, but I think this makes it the newest official ROM version of the One X / XL so far?
Changes?
the_scotsman said:
Seems Telstra users got a 1.89 OTA update today :highfive:
I'll see if an RUU is available, but I think this makes it the newest official ROM version of the One X / XL so far?
Click to expand...
Click to collapse
Yepity yep.
Questions- Do we know the changes? Release notes?
Seems quicker to load up apps.....although that could just be because it rebooted for the first time since I bought it.... :laugh:
the_scotsman said:
Seems Telstra users got a 1.89 OTA update today :highfive:
I'll see if an RUU is available, but I think this makes it the newest official ROM version of the One X / XL so far?
Click to expand...
Click to collapse
indeed
it got to be just pushing out this afternoon, it wasn't available this morning
Anyone tried rooting the new OTA after updating?
doesn't work
Code:
$ ./root-linux.sh
Don't touch the device or unplug while rooting!
Push files
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
rm failed for /data/local/installbusybox, No such file or directory
rm failed for /data/local/installbusybox2, No such file or directory
rm failed for /data/local/root, No such file or directory
rm failed for /data/local/root2, No such file or directory
rm failed for /data/local/sysro, No such file or directory
rm failed for /data/local/sysro2, No such file or directory
rm failed for /data/local/sysrw, No such file or directory
rm failed for /data/local/sysrw2, No such file or directory
rm failed for /data/local/unroot, No such file or directory
rm failed for /data/local/unroot2, No such file or directory
rm failed for /data/local/busybox, No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/Superuser.apk, No such file or directory
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
rm failed for /data/local.prop, No such file or directory
Reboot
/system/bin/sh: cannot create /data/local.prop: Permission denied
Reboot again...
mount: Operation not permitted
mount: Operation not permitted
/system/bin/sh: cannot create /system/xbin/busybox: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
/system/bin/sh: busybox: not found
/system/bin/sh: busybox: not found
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
Reboot one last time...
erasen1 said:
doesn't work
Code:
$ ./root-linux.sh
Don't touch the device or unplug while rooting!
Push files
error: protocol fault (no status)
* daemon not running. starting it now *
* daemon started successfully *
rm failed for /data/local/installbusybox, No such file or directory
rm failed for /data/local/installbusybox2, No such file or directory
rm failed for /data/local/root, No such file or directory
rm failed for /data/local/root2, No such file or directory
rm failed for /data/local/sysro, No such file or directory
rm failed for /data/local/sysro2, No such file or directory
rm failed for /data/local/sysrw, No such file or directory
rm failed for /data/local/sysrw2, No such file or directory
rm failed for /data/local/unroot, No such file or directory
rm failed for /data/local/unroot2, No such file or directory
rm failed for /data/local/busybox, No such file or directory
rm failed for /data/local/su, No such file or directory
rm failed for /data/local/Superuser.apk, No such file or directory
failed to copy 'busybox' to '/data/local/busybox': Permission denied
failed to copy 'su' to '/data/local/su': Permission denied
failed to copy 'Superuser.apk' to '/data/local/Superuser.apk': Permission denied
Unable to chmod /data/local/busybox: No such file or directory
Unable to chmod /data/local/su: No such file or directory
Unable to chmod /data/local/Superuser.apk: No such file or directory
failed on '/data/local/tmp' - Permission denied
link failed File exists
rm failed for /data/local.prop, No such file or directory
Reboot
/system/bin/sh: cannot create /data/local.prop: Permission denied
Reboot again...
mount: Operation not permitted
mount: Operation not permitted
/system/bin/sh: cannot create /system/xbin/busybox: Read-only file system
Unable to chmod /system/xbin/busybox: No such file or directory
/system/bin/sh: /system/xbin/busybox: not found
/system/bin/sh: busybox: not found
/system/bin/sh: busybox: not found
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/xbin/su: No such file or directory
Unable to chmod /system/app/Superuser.apk: No such file or directory
rm failed for /data/local.prop, No such file or directory
rm failed for /data/local/tmp, Permission denied
failed on '/data/local/tmp.bak' - No such file or directory
Reboot one last time...
Click to expand...
Click to collapse
Damn, thanks for letting us know.
EDIT: Those errors looks like an issue with the root install process. Obviously your phone was connected and you have the drivers installed? It looks like it's not seeing the phone at all.
the phone is connected, there was an adb instance in another terminal thats why you see script starts adb-mac at the top.
I tried some commands in the script it looks the update changed file permissions
Code:
$ adb push su /data/local/su
failed to copy 'su' to '/data/local/su': Permission denied
$ adb shell
1|[email protected]:/ $ mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
someone on stock 1.81 can compare
Code:
[email protected]:/ $ 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
/dev/block/mmcblk0p33 /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p35 /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,discard 0 0
/dev/block/mmcblk0p34 /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,discard 0 0
/dev/block/mmcblk0p26 /devlog ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered,discard 0 0
/sys/kernel/debug /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/mmcblk0p17 /firmware_radio vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p18 /firmware_q6 vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p19 /firmware_wcnss vfat ro,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
tmpfs /data/secure/data tmpfs rw,relatime,mode=755,gid=1000 0 0
htcfs /data/htcfs fuse.htcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
DxDrmServerIpc /data/DxDrm/fuse fuse.DxDrmServerIpc rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other 0 0
/dev/block/vold/179:36 /mnt/sdcard vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
/dev/block/vold/179:36 /mnt/secure/asec vfat rw,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro,discard 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
[email protected]:/ $
[email protected]:/ $ ls -la
drwxr-xr-x root root 2012-07-13 22:44 acct
drwxrwx--- system cache 2012-07-13 21:13 cache
dr-x------ root root 2012-07-13 22:44 config
-rw-r--r-- root root 1387 1970-01-01 10:00 cwkeys
lrwxrwxrwx root root 2012-07-13 22:44 d -> /sys/kernel/debug
drwxrwx--x system system 2012-07-13 17:06 data
-rw-r--r-- root root 118 1970-01-01 10:00 default.prop
drwxr-xr-x root root 2012-07-13 22:44 dev
drwx------ root root 2012-07-13 22:45 devlog
lrwxrwxrwx root root 2012-07-13 22:44 etc -> /system/etc
drwxrwx--x system system 2012-07-13 22:44 firmware_dsps
drwxrwxrwx root root 1970-01-01 10:00 firmware_q6
drwxrwxrwx root root 1970-01-01 10:00 firmware_radio
drwxrwxrwx root root 1970-01-01 10:00 firmware_wcnss
-rwxr-x--- root root 111620 1970-01-01 10:00 init
-rwxr-x--- root root 19133 1970-01-01 10:00 init.elite.rc
-rwxr-x--- root root 2344 1970-01-01 10:00 init.goldfish.rc
-rwxr-x--- root root 13114 1970-01-01 10:00 init.qcom.rc
-rwxr-x--- root root 9588 1970-01-01 10:00 init.qcom.sh
-rwxr-x--- root root 22080 1970-01-01 10:00 init.rc
-rwxr-x--- root root 3314 1970-01-01 10:00 init.target.rc
-rwxr-x--- root root 7760 1970-01-01 10:00 init.usb.rc
drwxrwxr-x root system 2012-07-13 22:44 mnt
dr-xr-xr-x root root 1970-01-01 10:00 proc
drwx------ root root 2012-06-19 18:46 root
drwxr-x--- root root 1970-01-01 10:00 sbin
lrwxrwxrwx root root 2012-07-13 22:44 sdcard -> /mnt/sdcard
drwxr-xr-x root root 2012-07-13 22:44 sys
drwxr-xr-x root root 2012-07-13 20:04 system
drwxrwx--x system system 2012-07-13 22:44 tombstones
-rw-r--r-- root root 272 1970-01-01 10:00 ueventd.goldfish.rc
-rw-r--r-- root root 8451 1970-01-01 10:00 ueventd.rc
drwxrwx--x system system 2012-07-13 22:44 vendor
[email protected]:/ $
I smell an ATT update and possibly kernel source release soon
Sent from my HTC One X using xda app-developers app
Im ganna wait till there is a rooted deodexed version of this before I let it update, but Im hoping this means source code finally!
Sent from my HTC One XL using Tapatalk 2
Yes I did an OTA update to 1.89 from my stock 1.81. Worked fine even though i'm in UK atm. I don't see any differences from playing with the phone today.
I wonder if we can sniff out the 1.89 RUU some how. Is it possible to see where the OTA itself is downloading from? Maybe that site hosts RUU too?
juicejuice said:
Yes I did an OTA update to 1.89 from my stock 1.81. Worked fine even though i'm in UK atm. I don't see any differences from playing with the phone today.
I wonder if we can sniff out the 1.89 RUU some how. Is it possible to see where the OTA itself is downloading from? Maybe that site hosts RUU too?
Click to expand...
Click to collapse
I am in contact with someone who has access to the RUUs. This new one isn't yet available.
I don't know if this is of any help but here's the downloaded update file (even though I can't apply it I can still download it ad nauseum)
https://www.dropbox.com/s/wxsqmdhwc...81.841.1_R_release_266785ap9qro3i4pvkmhv0.zip
ethantarheels123 said:
I smell an ATT update and possibly kernel source release soon
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
I spoke to a high up tech at HTC and they said AT&T will have a maintenance update within 3 weeks. Not sure if it's the same. He told me wifi will be 99.99% fixed and blutooth radio will be optimized. I asked him about jellybean and he just laughed. I guess they haven't even discussed jellybean yet.
OP - Did you notice better multi-tasking? Better battery life?
I just got the update also. I had to manually check for it. I haven't noticed the font changing it messages yet. Although messages did crash on me once. I'll see how my battery goes today and report back. Where is the changelog. Can't seem to find it anywhere
Sent from my HTC One XL using xda app-developers app
Some version info for people.
1.81.841.1 -> 1.89.841.9
Kernel
3.0.8-01145 -> 3.0.8-01159
Radio
17a.32.09.03_2_10.85.32.16L -> 18c.32.09.01_10.93a.32.20L
hboot
1.09.0000 -> 1.11.0000
OpenDSP
v25.1.0.32.0405 -> 28.1.0.32.0504
Apr(I forgot to write the rest) -> Jun 7 2012,13:10:34
karan1203 said:
I spoke to a high up tech at HTC and they said AT&T will have a maintenance update within 3 weeks. Not sure if it's the same. He told me wifi will be 99.99% fixed and blutooth radio will be optimized. I asked him about jellybean and he just laughed. I guess they haven't even discussed jellybean yet.
OP - Did you notice better multi-tasking? Better battery life?
Click to expand...
Click to collapse
Isn't Wifi a hardware issue? Will this be another "fix" like what Asus did with Prime tablets? Heh.
Anyone who has applied this update, do you lose root and if so can you get it back easy enough. Also I've not unlocked the bootloader, is this still possible after upgrading HBOOT?
Never actually used an official update, got sick of waiting for telstra to bring froyo when I had my Desire and never looked back.
hmm i couldnt do the update.
i think cause my phone has been rooted.
anyone experience the same problem?
Itaintrite said:
Isn't Wifi a hardware issue? Will this be another "fix" like what Asus did with Prime tablets? Heh.
Click to expand...
Click to collapse
Why do you think it is hardware based?
Some of the issues people report are:
-auto 2.4/5ghz doesnt work (cant obtain IP aka no data flow). Must force 2.4ghz
-wifi does not disconnect when out of range. Must turn wifi off/on
-wifi does not reconnect when in range. Must turn wifi off/on
I think the general understanding is all of these are likely just a software issue.
---------- Post added at 08:08 AM ---------- Previous post was at 08:06 AM ----------
dejapanda said:
hmm i couldnt do the update.
i think cause my phone has been rooted.
anyone experience the same problem?
Click to expand...
Click to collapse
I believe you need stock recovery for it to work. Maybe also require locked bootloader.
I personally locked the bootloader, flashed Telstra RUU and then installed the update. Followed by unlocking bootloader and replacing recovery again
twistedddx said:
I believe you need stock recovery for it to work. Maybe also require locked bootloader.
I personally locked the bootloader, flashed Telstra RUU and then installed the update. Followed by unlocking bootloader and replacing recovery again
Click to expand...
Click to collapse
Did you try rooting again after the update?

Cannot write direclty to /mnt/extSdCard with adb or Android Commander

In adb shell, with myself set as su, I cannot write directly to /mnt/extSdCard. Get's "permission denied"
When I do a chmod or chown to root, I get an "operation not permitted"
I have to copy (push) files to /mnt/sdcard and use the device to move/copy stuff over to /mnt/extSdCard.....pretty annoying.
I guess the reason is because the ownership looks like this:
ls -al
...
drwxrwxr-x system media_rw 2012-10-12 10:07 extSdCard
drwxr-xr-x root system 2012-10-11 09:10 obb
drwxrwxr-x root sdcard_rw 2012-10-12 10:29 sdcard
drwx------ root root 2012-10-11 09:10 secure
Any ideas how I can write to /mnt/extSdCard - even Android Commander is not doing anything
I think you have to mount it first with something that should look like,
"Adb mount /mnt/blk/[some wierd path here]/" or something
Not sure but that's my best guess since no one else was offering insight
Sent from my GT-N8013 using xda app-developers app
Same problem here, have you already found a solution or workaround?

[Completed] move album to SD Card

I have screen captures and downloads on my phone that I want to move to my SD card.
When I mount the phone on my Linux computer, I see:
/run/user/1000/gvfs/mtp:host=%5Busb%3A010%2C018%5D$ ls -l
total 0
drwx------ 1 me me 0 Dec 31 1969 Card
drwx------ 1 me me 0 Dec 31 1969 Phone
I did: mkdir Card/DCIM/Screenshots and that worked.
cp -a Phone/Pictures/Screenshots Card/DCIM/Screenshots gives the error "Operation not supported".
I checked the permissions on all the directories in the path and they seem ok.
I tried to chmod to make everything writeable by everyone but that fails too.
I've tried to copy/move the files with a file manager on the phone but that fails too.
$ ls -l
total 0
dr-x------ 1 me me 0 Dec 31 1969 mtp:host=%5Busb%3A010%2C018%5D
$ chmod o+w *
chmod: changing permissions of 'mtp:host=%5Busb%3A010%2C018%5D': Operation not supported
bjlockie said:
I have screen captures and downloads on my phone that I want to move to my SD card.
When I mount the phone on my Linux computer, I see:
/run/user/1000/gvfs/mtp:host=%5Busb%3A010%2C018%5D$ ls -l
total 0
drwx------ 1 me me 0 Dec 31 1969 Card
drwx------ 1 me me 0 Dec 31 1969 Phone
I did: mkdir Card/DCIM/Screenshots and that worked.
cp -a Phone/Pictures/Screenshots Card/DCIM/Screenshots gives the error "Operation not supported".
I checked the permissions on all the directories in the path and they seem ok.
I tried to chmod to make everything writeable by everyone but that fails too.
I've tried to copy/move the files with a file manager on the phone but that fails too.
$ ls -l
total 0
dr-x------ 1 me me 0 Dec 31 1969 mtp:host=%5Busb%3A010%2C018%5D
$ chmod o+w *
chmod: changing permissions of 'mtp:host=%5Busb%3A010%2C018%5D': Operation not supported
Click to expand...
Click to collapse
Hi,
Try this:
Code:
/run/user/1000/gvfs/mtp:host=%5Busb%3A010%2C018%5D$ cp -R Phone/Pictures/Screenshots $HOME/Card/DCIM/Screenshots
I might have your file paths wrong but the logic should work.

Weirdest problem on my gear s2

I have model sm-732 purchased in US and i am the least bit close to a developer.
Went to sell it today because it had been sitting in a drawer and thought that somebody should have it. I only wore it a few times and then it became of no use to me after i was involved in a robbery wearing it.
It worked after that, dont get me wrong, but i decided to not wear it and but it in a drawer were it has been ever since. I did take it out once to reset it via the software which was successfull. I then placed it in the drawer again and forgot about it. Until i remembered i could sell it. Took it out and charged it up and went to sell it. Turned it on when i got to the buyer and it wouldnt work saying it had failed to start and if it persisted to take it to samsung. I am way out if warrenty to they wont do anything for me. I watched a video on bootlooping and i went to the reset screen where download mode is, and just tried to restore. It came back in russian. All russian.
So i went to the internet. People namely said flash it so i got ap, bl, and csc pack for it and flashed it wirelessly with a passing rating from odin.
I have done this twice now and it will say installing new configuration... (which was displayed in russian but now is displayed in english) after that the gear s2 logo will flash and then the samsung logo and then poof it just shuts down and goes back to russian!
Goodlord help me. I am an idiot.
Same here! If I flash Combinations-FTMA it work (but limited) , after flashing full firmware ... Failed.If the Same here! If I flash Combinations-FTMA it work (but limited) , after flashing full firmware ... Failed.If the problem persists, visit a customer service centre.
@Karmaus
Sorry. Less time...
1.
I can see Warranty Void blabla... so something with Knox happens in Photo 1...
2.
No idea what exact fail...
I can remember during my experiments 1 time I have killed BT address in CSA area...
So first boot ends with Error as no connection possible with Phone...
It was very hard for me to restore BT... but it is not impossible... :angel:
2.1
Maybe check BT AND WiFi connection in FTMA Combination Firmware...
2.2
You could also try to catch Log Files...
Code:
*#9900#
Best Regards
Edit 1.
Forgotten...
SM-R732 have 2 Regions... OXA AND OXX...
Maybe this is the reason... if CSC is not inside Firmware package...
@adfree
adfree said:
@Karmaus
Sorry. Less time...
1.
I can see Warranty Void blabla... so something with Knox happens in Photo 1...
2.
No idea what exact fail...
I can remember during my experiments 1 time I have killed BT address in CSA area...
So first boot ends with Error as no connection possible with Phone...
It was very hard for me to restore BT... but it is not impossible... :angel:
2.1
Maybe check BT AND WiFi connection in FTMA Combination Firmware...
2.2
You could also try to catch Log Files...
Code:
*#9900#
Best Regards
Edit 1.
Forgotten...
SM-R732 have 2 Regions... OXA AND OXX...
Maybe this is the reason... if CSC is not inside Firmware package...
Click to expand...
Click to collapse
1. i've try to write both ftma & full firmware , same result
2. indeed bt is killed ...
Edit1. Thanks for regions!
So can you remember how to restore bt ?
My Edit 1 : I've added my dump log ...
@Karmaus
Limited time... and long time ago...
But if I remember correct.
You can use easy Shell script *.sh inside Combination Firmware...
Write me PM... and I will try to search in my Computers... how I solved lost BT...
Best Regards
Code:
#!/bin/sh
#
# Script for setting Bluetooth Address
#
#if [ -e /opt/etc/.bd_addr ]
#then
# echo "Already .bd_addr exists"
# exit 0
#fi
/usr/bin/setbd
echo "Set BT address successes"
bt-set-addr.sh
@Karmaus
Something like this I did to restore BT...
This Shell Script is inside Combination Firmware...
All my attempts to restore my own CSA dump failed... Seems higher secured...
But with this easy Script it was easy...
Best Regards
adfree said:
Code:
#!/bin/sh
#
# Script for setting Bluetooth Address
#
#if [ -e /opt/etc/.bd_addr ]
#then
# echo "Already .bd_addr exists"
# exit 0
#fi
/usr/bin/setbd
echo "Set BT address successes"
bt-set-addr.sh
@Karmaus
Something like this I did to restore BT...
This Shell Script is inside Combination Firmware...
All my attempts to restore my own CSA dump failed... Seems higher secured...
But with this easy Script it was easy...
Best Regards
Click to expand...
Click to collapse
Thanks so much ... i Will try right now and come with a reply in few minutes!
About BT address...
Example to check if file is absent...
Code:
sh-3.2$ cd csa
sh-3.2$ ls
bluetooth csc factory lost+found prov prov_data sensor
sh-3.2$ cd bluetooth
sh-3.2$ ls
sh-3.2$ ls -a -1 -l
total 6
drwxr-xr-x 2 root root 1024 Sep 4 2015 .
drwxr-xr-x 9 root root 1024 Jan 1 2015 ..
-rw-r--r-- 1 root root 14 Sep 4 2015 .bd_addr
sh-3.2$ cat .bd_addr
0002
fc
68f142sh-3.2$
Here is all okay... BT address is not gone/erased...
BUT IMHO this requires ROOT... Combination Firmware...
Best Regards
adfree said:
About BT address...
Example to check if file is absent...
Code:
sh-3.2$ cd csa
sh-3.2$ ls
bluetooth csc factory lost+found prov prov_data sensor
sh-3.2$ cd bluetooth
sh-3.2$ ls
sh-3.2$ ls -a -1 -l
total 6
drwxr-xr-x 2 root root 1024 Sep 4 2015 .
drwxr-xr-x 9 root root 1024 Jan 1 2015 ..
-rw-r--r-- 1 root root 14 Sep 4 2015 .bd_addr
sh-3.2$ cat .bd_addr
0002
fc
68f142sh-3.2$
Here is all okay... BT address is not gone/erased...
BUT IMHO this requires ROOT... Combination Firmware...
Best Regards
Click to expand...
Click to collapse
In my similar case, I haven't seen anything
Code:
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell
sh-3.2# ls
bin csa etc initrd lost+found mnt proc run sdcard srv tmp var
boot dev home lib media opt root sbin smack sys usr
sh-3.2# cd csa
sh-3.2# ls -l
total 0
sh-3.2#
My post: https://forum.xda-developers.com/smartwatch/gear-s2/gear-s2-rm-720-loop-t3977853
Edit:
I tried to run /usr/bin/setbd but I can't.
Bluetooth Address Setting
mkdir: Read-only file system (30) File not exist
Can't open address file
Code:
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell chmod 777 /usr/bin/
chmod: changing permissions of `/usr/bin/': Read-only file system
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb root on
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell chmod 777 /usr/bin/
chmod: changing permissions of `/usr/bin/': Read-only file system
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb root off
Switched to 'developer' account mode
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell chmod 777 /usr/bin/
chmod: changing permissions of `/usr/bin/': Read-only file system
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell /usr/bin/setbd
-l: /usr/bin/setbd: Permission denied
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell cp /usr/bin/setbd /opt/usr/media/
cp: cannot stat `/usr/bin/setbd': Permission denied
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb root on
Switched to 'root' account mode
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell cp /usr/bin/setbd /opt/usr/media/
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell ls -l /opt/usr/media/
total 24
drwxrwxrwx 2 app app 4096 Oct 6 2015 Downloads
drwxrwxrwx 2 app app 4096 Oct 6 2015 Images
drwxrwxrwx 2 app app 4096 Oct 6 2015 Music
drwxrwxrwx 3 app app 4096 Oct 6 2015 Sounds
-rwxr-xr-x 1 root root 6004 Jan 5 11:51 setbd
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell chmod 777 /opt/usr/media/setbd
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell ls -l /opt/usr/media/
total 24
drwxrwxrwx 2 app app 4096 Oct 6 2015 Downloads
drwxrwxrwx 2 app app 4096 Oct 6 2015 Images
drwxrwxrwx 2 app app 4096 Oct 6 2015 Music
drwxrwxrwx 3 app app 4096 Oct 6 2015 Sounds
-rwxrwxrwx 1 root root 6004 Jan 5 11:51 setbd
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>adb shell /opt/usr/media/setbd
Bluetooth Address Setting
mkdir: Read-only file system(30)File not exist
Can't open address file
C:\Users\msdda\Desktop\WiFi_Odin V1.0\GearFit2>
@danicifu01
Is sooooooooo looooooooong ago....
Code:
mount -o remount,rw /
Try this Command before in:
Code:
sdb shell
Best Regards
adfree said:
@danicifu01
Is sooooooooo looooooooong ago....
Code:
mount -o remount,rw /
Try this Command before in:
Code:
sdb shell
Best Regards
Click to expand...
Click to collapse
thanks but:
Code:
sh-3.2# ls -l
total 44
drwxr-xr-x 3 root root 4096 Oct 6 2015 abuild
drwxr-xr-x 10 app app 4096 Jan 6 09:57 app
-rwxrwxrwx 1 root root 136 Jan 10 18:14 bt.sh
drwxr-xr-x 2 developer developer 4096 Oct 6 2015 developer
drwxr-xr-x 4 root root 4096 Jan 5 13:49 root
drwxr-xr-x 5 system system 4096 Jan 5 11:10 system
sh-3.2# sh bt.sh
bt.sh: line 1: cript: command not found
Bluetooth Address Setting
mkdir: Permission denied(13)File not exist
Can't open address file
bt.sh is the script
i try run the script but the file not exit. why?

Categories

Resources