Hi @all,
haven't found any definite answer to this unsing the search function.
Is there any image out there supporting the HDD version of the 80G9 tablet? Except the official image of course.
Installed the lastest 4.4.2 developer image, now I know what the H-Model is (No "H" model support)... otherwise working great so far.
Thanks for your answers!
martinwag said:
Hi @all,
haven't found any definite answer to this unsing the search function.
Is there any image out there supporting the HDD version of the 80G9 tablet? Except the official image of course.
Installed the lastest 4.4.2 developer image, now I know what the H-Model is (No "H" model support)... otherwise working great so far.
Thanks for your answers!
Click to expand...
Click to collapse
It's really confusing...
[URL="http://forum.xda-developers.com/showpost.php?p=50137500&postcount=61" @[email protected][/URL] has reported that it works... I really don't know whats going wrong...
@[email protected]: Can you give a statement, if the harddisk storage works for you?
Quallenauge said:
It's really confusing...
[URL="http://forum.xda-developers.com/showpost.php?p=50137500&postcount=61" @[email protected][/URL] has reported that it works... I really don't know whats going wrong...
@[email protected]: Can you give a statement, if the harddisk storage works for you?
Click to expand...
Click to collapse
Yes, but I could only install till version 23_01_2014-21_52_56 yet.
And I need to mount it manually e.g. via 'adb shell':
[email protected]:/ # mount /dev/block/platform/omap/usbhs_omap/sdb1 /storage/sdcard1/
[email protected] said:
Yes, but I could only install till version 23_01_2014-21_52_56 yet.
And I need to mount it manually e.g. via 'adb shell':
[email protected]:/ # mount /dev/block/platform/omap/usbhs_omap/sdb1 /storage/sdcard1/
Click to expand...
Click to collapse
Can you please adapt the fstab file "/fstab.archosa101hboard" to this location?
Code:
[STRIKE]/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1.1/1-1.1:1.0/ auto auto defaults voldmanaged=sdcard1:auto[/STRIKE]
[B]/dev/block/platform/omap/usbhs_omap/sdb1 auto auto defaults voldmanaged=sdcard1:auto[/B]
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
/dev/block/zram0
And see if it helps? (Maybe you can play with the old path definition; does it exist? Maybe this is sufficient:
Code:
/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/
)
Hint: Don't forget to unlock the device in order to modify the system file:
Code:
adb shell mount -o remount,rw /
Actually I am not used to writing in those forum systems, so my original try to answer is now blocked
---------- Post added at 01:10 AM ---------- Previous post was at 12:59 AM ----------
I try without any quotes and just a very short version:
Actually I forgot that I had a mini card reader and sdcard in the 3G USB plugged in, without this card it is in fact sda1
---------- Post added at 01:22 AM ---------- Previous post was at 01:10 AM ----------
... Nevertheless it didn't worked, so I searched and found fstab.archosa101hboard is not really in use and I changed init.archosa101hboard.rc first.
---------- Post added at 01:27 AM ---------- Previous post was at 01:22 AM ----------
please try a grep fstab.archosa init* to find that always the sboard fstab files are mounted
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Don't know if this can be useful information for you in init.archosa.*board.rc files, but I found in init.rc this import line via ${ro.hardware}:
import /init.${ro.hardware}.rc
back to the harddisk:
still not knowing why it didn't work I changed fstab.archosa101hboard to double-check my fix above is okay:
#/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
#/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
/dev/block/zram0 none swap defaults zramsize=134217728
Okay I got the right file, as after reboot I got it mounted:
[email protected]:/ # df
Filesystem Size Used Free Blksize
...
/storage/sdcard1 231.0G 187.5M 230.9G 4096
...
I do not understand "voldmanaged=sdcard1:auto", so I need to stop here and wait for your further support.
I have already played around a lot also with the information from android source website, which I cannot link here (new user)
[email protected] said:
Actually I am not used to writing in those forum systems, so my original try to answer is now blocked
---------- Post added at 01:10 AM ---------- Previous post was at 12:59 AM ----------
I try without any quotes and just a very short version:
Actually I forgot that I had a mini card reader and sdcard in the 3G USB plugged in, without this card it is in fact sda1
---------- Post added at 01:22 AM ---------- Previous post was at 01:10 AM ----------
... Nevertheless it didn't worked, so I searched and found fstab.archosa101hboard is not really in use and I changed init.archosa101hboard.rc first.
---------- Post added at 01:27 AM ---------- Previous post was at 01:22 AM ----------
please try a grep fstab.archosa init* to find that always the sboard fstab files are mounted
---------- Post added at 01:38 AM ---------- Previous post was at 01:27 AM ----------
Don't know if this can be useful information for you in init.archosa.*board.rc files, but I found in init.rc this import line via ${ro.hardware}:
import /init.${ro.hardware}.rc
Click to expand...
Click to collapse
Thanks for your report ! The fstab is loaded on specific archos model init file.
Code:
on fs
# mount partitions
mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
mount_all /fstab.archosa101hboard
swapon_all /fstab.archosa101hboard
This init file is loaded on top at the init.archos_init.rc file. The ${ro.hardware} reflects the model property. You can verify this with
Code:
adb shell getprop ro.hardware
.
Then the correct fstab should loaded.
please try a grep fstab.archosa init* to find that always the s board fstab files are mounted
Click to expand...
Click to collapse
PS: Which version do you use? I had a fix a few weeks ago (Correct fstab file name for non a80s devices.) which is used in newer releases.
back to the harddisk:
still not knowing why it didn't work I changed fstab.archosa101hboard to double-check my fix above is okay:
#/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
#/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
/dev/block/zram0 none swap defaults zramsize=134217728
Okay I got the right file, as after reboot I got it mounted:
[email protected]:/ # df
Filesystem Size Used Free Blksize
...
/storage/sdcard1 231.0G 187.5M 230.9G 4096
...
I do not understand "voldmanaged=sdcard1:auto", so I need to stop here and wait for your further support.
I have already played around a lot also with the information from android source website, which I cannot link here (new user)
Click to expand...
Click to collapse
The output of the df command is ok. Please check if it is possible to use the following:
Code:
/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto
. The destination mount point is determined from the vold daemon, which starts the appropriate "sdcard" daemon.
Thank you all for your answers!
Great, the HDD is already avaliable in /dev/block/platform/omap/usbhs_omap/sda1... Why didn't I just do a find * | grep sda ...
I'm at the point where [email protected] is now, only difference is that I'm using the 80h files instead of the 101h ones.
- enable write on /
Code:
busybox mount -o remount,rw /
- edit fstab.archosa80hboard
Code:
#/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto #original
#/dev/block/platform/omap/usbhs_omap/sda1 auto auto defaults voldmanaged=sdcard1:auto #as suggested, doesn't work
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2 #works
- edit init.archosa80hboard.rc
Code:
#mount partitions
mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs #as is
mount_all /fstab.archosa80hboard #replace s with h
swapon_all /fstab.archosa80hboard #replace s with h
I'm using Image 12_02_2014-20_55_45.7z, which was current last weekend at least
Maybe this has been reported before, but 12_02_2014-20_55_45.7z don't boot on my tab.
I get nothing, but a black screen and the green LED - not even the Archos logo or a logcat
Latest running version is 23_01_2014-21_52_56
[email protected] said:
Maybe this has been reported before, but 12_02_2014-20_55_45.7z don't boot on my tab.
I get nothing, but a black screen and the green LED - not even the Archos logo or a logcat
Latest running version is 23_01_2014-21_52_56
Click to expand...
Click to collapse
That's weird.... I get this behavior in case I'm flash via SDE and when I choose "Flash kernel and initramfs" the USB drive is mounted on my PC.
When I copy the two files to the destination, sometimes I forget to unmount the removable storage drive and choose "continue" (or something like this) on the tablet. Then the incomplete kernel/initramfs files are written to the internal ssd which causes the black screen on start.
Can you please check if this was also the case?
[email protected] said:
Maybe this has been reported before, but 12_02_2014-20_55_45.7z don't boot on my tab.
I get nothing, but a black screen and the green LED - not even the Archos logo or a logcat
Latest running version is 23_01_2014-21_52_56
Click to expand...
Click to collapse
If I don't open a terminal and sudo sync before disconnecting the usb cable it happens most of the time for me.
stevemp said:
If I don't open a terminal and sudo sync before disconnecting the usb cable it happens most of the time for me.
Click to expand...
Click to collapse
Quallenauge said:
That's weird.... I get this behavior in case I'm flash via SDE and when I choose "Flash kernel and initramfs" the USB drive is mounted on my PC.
When I copy the two files to the destination, sometimes I forget to unmount the removable storage drive and choose "continue" (or something like this) on the tablet. Then the incomplete kernel/initramfs files are written to the internal ssd which causes the black screen on start.
Can you please check if this was also the case?
Click to expand...
Click to collapse
Thank you for the suggestions, so I could find out a bit what is actually my problem:
I did in fact not disconnecting the USB cable before rebooting.
This was never a problem for the old versions - may be you could add this to your installation instructions if really necessary:
Quallenauge said:
- reboot into SDE menu and under Developer Edition Mernu , Flash Kernel and Initramfs : copy zImage and initramfs.cpio.lzo on the new driver that appears on desktop/laptop
- Wait for reboot your devices : after reboot you can see Android prepares the system for a while .....be patient !
Click to expand...
Click to collapse
Nevertheless the device immediately stops (freeze) also directly when I later plug in the USB cable and further after a short time it shows again a black screen and the green LED. I have also tested to connect an OTG cable adapter and it also directly stops (with and without a mouse). Sometimes after plugging off the cable the device automatically reboots.
I switched the 3g dongle on to test the other USB port with a mouse, but no lights - it doesn't work either.
I have no time for testing now and for the rest of the week, I'll check next week for requested logs or a new version fixing it. :fingers-crossed:
Cheers!
[email protected] said:
Thank you for the suggestions, so I could find out a bit what is actually my problem:
I did in fact not disconnecting the USB cable before rebooting.
This was never a problem for the old versions - may be you could add this to your installation instructions if really necessary:
Click to expand...
Click to collapse
Sorry, I meant something different :angel: You can leave the USB cable plugged into the device. I mean, you have to eject (sign off,...) the drive removable in windows / linux after you finish the file transfer to the device (both when you copy the kernel+initramfs and also when updating the archos.ext4.update file). This way the data is synced on the device (to avoid corrupted data).
[email protected] said:
Nevertheless the device immediately stops (freeze) also directly when I later plug in the USB cable and further after a short time it shows again a black screen and the green LED. I have also tested to connect an OTG cable adapter and it also directly stops (with and without a mouse). Sometimes after plugging off the cable the device automatically reboots.
I switched the 3g dongle on to test the other USB port with a mouse, but no lights - it doesn't work either.
I have no time for testing now and for the rest of the week, I'll check next week for requested logs or a new version fixing it. :fingers-crossed:
Cheers!
Click to expand...
Click to collapse
Does at least the archos screen appear before the screen goes black?
Quallenauge said:
Sorry, I meant something different :angel: You can leave the USB cable plugged into the device. I mean, you have to eject (sign off,...) the drive removable in windows / linux after you finish the file transfer to the device (both when you copy the kernel+initramfs and also when updating the archos.ext4.update file). This way the data is synced on the device (to avoid corrupted data).
Does at least the archos screen appear before the screen goes black?
Click to expand...
Click to collapse
Actually I am using linux and I follow exactly your process with sync and umount ... and I was used to leaving the USB cable plugged into the device, but starting with CM 11.0 from 11_02_2014-23_03_07 the tablet was not booting and the archos screen did not appear any more.
I saw that you classified the kernel "Important: Highly experimental!" and "No "H" model support", so I thought just "bad luck" and went back to the old version. (and I bought a sony xperia tablet s)
stevemp wrote "before disconnecting the usb cable", so I tried also without the cable and it boots. Later I realized that I cannot use the micro USB plug at all, because the tablet directly freeze when I connect anything to it. (No problem with power, as the H model has a separated power plug)
May be I didn't explained it well: It always freeze: either before booting or/and also during booting or/and also after booting in normal operating: just plug it in -> directly freeze.
I have no idea what happens and how it can be analyzed.
This happens not when I run CM 11.0 version from 23_01_2014-21_52_56, so I do not believe in a hardware bug.
[email protected] said:
Actually I am using linux and I follow exactly your process with sync and umount ... and I was used to leaving the USB cable plugged into the device, but starting with CM 11.0 from 11_02_2014-23_03_07 the tablet was not booting and the archos screen did not appear any more.
I saw that you classified the kernel "Important: Highly experimental!" and "No "H" model support", so I thought just "bad luck" and went back to the old version. (and I bought a sony xperia tablet s)
stevemp wrote "before disconnecting the usb cable", so I tried also without the cable and it boots. Later I realized that I cannot use the micro USB plug at all, because the tablet directly freeze when I connect anything to it. (No problem with power, as the H model has a separated power plug)
May be I didn't explained it well: It always freeze: either before booting or/and also during booting or/and also after booting in normal operating: just plug it in -> directly freeze.
I have no idea what happens and how it can be analyzed.
This happens not when I run CM 11.0 version from 23_01_2014-21_52_56, so I do not believe in a hardware bug.
Click to expand...
Click to collapse
Thanks for your explanation! Now it's clear for me, the update process was done correctly.
Sadly, I updated the kernel since the 23_01_2014-21_52_56, so I think this is a kernel bug, which affects the JMicron USB SATA controller :-/
Sadly only a few people has a serial cable connected to their *H devices, so we don't have an easy way to track down this issue.
I see a light chance to get the boot log. I can send you a archive where you can test the kernel from your existing installation.
If you have time for some experiments, let me know.
Quallenauge said:
Thanks for your explanation! Now it's clear for me, the update process was done correctly.
Sadly, I updated the kernel since the 23_01_2014-21_52_56, so I think this is a kernel bug, which affects the JMicron USB SATA controller :-/
Sadly only a few people has a serial cable connected to their *H devices, so we don't have an easy way to track down this issue.
I see a light chance to get the boot log. I can send you a archive where you can test the kernel from your existing installation.
If you have time for some experiments, let me know.
Click to expand...
Click to collapse
Yeah, I can test it, but I think not before Monday next week.
Quallenauge said:
I had a fix a few weeks ago (Correct fstab file name for non a80s devices.) which is used in newer releases.
Click to expand...
Click to collapse
Sorry your fix does not really correct all:
Code:
localhost / # grep fstab.archosa init*
init.archosa101[B]h[/B]board.rc: mount_all /fstab.archosa101[B]s[/B]board
init.archosa101[B]h[/B]board.rc: swapon_all /fstab.archosa101[B]s[/B]board
...
After fixing this I have also tested a bit changing the fstab.archosa101hboard.rc file, as your described, but I couldn't get the hard disk mounted with the voldmanaged=sdcard1:auto setting.
Only this line automatically mount it:
Code:
/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
I also wonder about a link (/sys/class/block/sda1) which has no correct target:
Code:
localhost / # find / -name sda1 2>/dev/null
/sys/class/block/sda1
/dev/block/sda1
/dev/block/platform/omap/usbhs_omap/sda1
localhost / # ls -l /sys/class/block/sda1 /dev/block/sda1 /dev/block/platform/omap/usbhs_omap/sda1
lrwxrwxrwx 1 root root 15 Mar 7 00:16 /dev/block/platform/omap/usbhs_omap/sda1 -> /dev/block/sda1
brw------- 1 root root 8, 1 Mar 7 00:16 /dev/block/sda1
lrwxrwxrwx 1 root root 0 Mar 7 00:22 /sys/class/block/sda1 -> ../../devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1.1/1-1.1:1.0/host0/target0:0:0/0:0:0:0/block/sda/sda1
/sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1.1 does not exist, just
/sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1/1-1:1.0
Code:
localhost / # ls -l /sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1
drwxr-xr-x 4 root root 0 Mar 7 00:22 1-1:1.0
-rw-r--r-- 1 root root 4096 Mar 7 00:22 authorized
-rw-r--r-- 1 root root 4096 Mar 7 00:22 avoid_reset_quirk
-rw-r--r-- 1 root root 4096 Mar 7 00:22 bConfigurationValue
-r--r--r-- 1 root root 4096 Mar 7 00:22 bDeviceClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bDeviceProtocol
-r--r--r-- 1 root root 4096 Mar 7 00:22 bDeviceSubClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bMaxPacketSize0
-r--r--r-- 1 root root 4096 Mar 7 00:22 bMaxPower
-r--r--r-- 1 root root 4096 Mar 7 00:22 bNumConfigurations
-r--r--r-- 1 root root 4096 Mar 7 00:22 bNumInterfaces
-r--r--r-- 1 root root 4096 Mar 7 00:22 bcdDevice
-r--r--r-- 1 root root 4096 Mar 7 00:22 bmAttributes
-r--r--r-- 1 root root 4096 Mar 7 00:22 busnum
-r--r--r-- 1 root root 4096 Mar 7 00:22 configuration
-r--r--r-- 1 root root 65553 Mar 7 00:22 descriptors
-r--r--r-- 1 root root 4096 Mar 7 00:22 dev
-r--r--r-- 1 root root 4096 Mar 7 00:22 devnum
-r--r--r-- 1 root root 4096 Mar 7 00:22 devpath
lrwxrwxrwx 1 root root 0 Mar 7 00:22 driver -> ../../../../../../../bus/usb/drivers/usb
drwxr-xr-x 3 root root 0 Mar 7 00:22 ep_00
-r--r--r-- 1 root root 4096 Mar 7 00:22 idProduct
-r--r--r-- 1 root root 4096 Mar 7 00:22 idVendor
-r--r--r-- 1 root root 4096 Mar 7 00:22 maxchild
drwxr-xr-x 2 root root 0 Mar 7 00:22 power
-r--r--r-- 1 root root 4096 Mar 7 00:22 quirks
--w------- 1 root root 4096 Mar 7 00:22 remove
-r--r--r-- 1 root root 4096 Mar 7 00:22 speed
lrwxrwxrwx 1 root root 0 Mar 7 00:22 subsystem -> ../../../../../../../bus/usb
-rw-r--r-- 1 root root 4096 Mar 7 00:22 uevent
-r--r--r-- 1 root root 4096 Mar 7 00:22 urbnum
drwxr-xr-x 3 root root 0 Mar 7 00:22 usb_device
-r--r--r-- 1 root root 4096 Mar 7 00:22 version
localhost / # ls -l /sys/devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/1-1:1.0
-r--r--r-- 1 root root 4096 Mar 7 00:22 bAlternateSetting
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceNumber
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceProtocol
-r--r--r-- 1 root root 4096 Mar 7 00:22 bInterfaceSubClass
-r--r--r-- 1 root root 4096 Mar 7 00:22 bNumEndpoints
lrwxrwxrwx 1 root root 0 Mar 7 00:22 driver -> ../../../../../../../../bus/usb/drivers/hub
drwxr-xr-x 3 root root 0 Mar 7 00:22 ep_81
-r--r--r-- 1 root root 4096 Mar 7 00:22 modalias
drwxr-xr-x 2 root root 0 Mar 7 00:22 power
lrwxrwxrwx 1 root root 0 Mar 7 00:22 subsystem -> ../../../../../../../../bus/usb
-r--r--r-- 1 root root 4096 Mar 7 00:22 supports_autosuspend
-rw-r--r-- 1 root root 4096 Mar 7 00:22 uevent
I've also played around a little bit, but without any further progress...
- tried to just mount hdd over whatever is on /storage/sdcard0 -> doesn't work as sdcard0 is a link to Storage/emulated/legacy which itself is again a link to /mnt/shell/emulated/0 and apps seem to use that. Mounting on top of /mnt/shell/emulated/0 also doesn't work for some reason unknown to me :crying:
- had a look at vold configuration file in /system/etc/vold.A80H.fstab (in the case of my A80), but I don't even know if that file is interpreted at some time. Changing the faulty hdd path in there had no effect whatsoever.
I'm back to one of the rooted Archos Images, as I want to actually use the thing again I don't think there is a way to dual boot to do some further investigations?
Hi @Quallenauge,
(I don't know if I can talk about it here but it has a relation with the latest kernel update you've done) With your last update, I have a little problem : Indeed my Internal storage is recognized as an external SDcard when I use the file explorer and also I don't have access to the contents of my Internal storage in my computer.
Thank you in advance.
Hi again,
I could actually manage to use the HD for apps and data. It was easier than expected, but still a hack and need some tuning. So don't blame me if it doesn't run on your device.
Okay here is what I have done:
(I use Ubuntu and don't know how to do it on Windows or iOS)
a) Reset and format the device and the HD to start with a clean environment. (Don't forget to save your data somewhere outside)
b) Download and extract @Quallenauge 's CM11 ROM 09_03_2014-12_04_52
c) Mount the archos.ext4.update file
d) Fix the init.archosa101hboard.rc (init.archosa80hboard.rc) file to get the correct file loaded fstab.archosa101hboard (fstab.archosa80hboard.rc)
-> Just seach for 101s (80s) and change to 101h (80h)
e) Change fstab.archosa101hboard (fstab.archosa80hboard.rc) to use the HD for /data:
Code:
#/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,barrier=1 wait
#/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1 wait,check
#/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check,encryptable=footer
#/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check
# mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
# mount ext4 /dev/block/mmcblk0p2 /mnt/system noatime nosuid noexec
# mount ext4 /dev/block/mmcblk0p4 /data noatime nosuid
#/dev/block/mmcblk0p1 /mnt/rawfs rawfs
/dev/block/mmcblk0p2 /mnt/system ext4 noatime,nosuid,noexec wait
#/dev/block/mmcblk0p4 /data ext4 noatime,nosuid wait,check,encryptable=footer
/dev/block/platform/omap/usbhs_omap/sda1 /data ext4 defaults 0 2
/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
#/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/dev/block/zram0 none swap defaults zramsize=134217728
f) Unmount the archos.ext4.update file
g) Install as usual
My impressions:
- I could install all (!) my apps :laugh:
- I have still only 512 MB RAM, so e.g. Adblock Plus be stopped when Chrome is running. I have installed Greenify, which helps a bit. Need more investigation. Any thoughts are welcome!
- Booting takes a bit longer
- As the HD is used to falling quick back in sleep mode and it cannot cache all needed files, it takes some extra time to open an app or switch to one of the other screens.
- Don't know what to do with /dev/block/mmcblk0p4 - Can we use it for caching the HD or as swap device?
- After some time sleeping, the device need to reboot by long pressing on/off (I think that is in discussion in the main [ROM] [4.4.2] CyanogenMod 11.0 thread)
- Not tested yet, but activating the 3g dongle for USB memory would change the HD partiion from sda1 to sdb1, so wouldn't run. Maybe copying the HD to a SD card would be nice to have.
- Battery time: Don't know, as it is always plugged in
At the end I think it is the best ROM for this poor device - so thanks again @Quallenauge
[email protected] said:
Hi again,
I could actually manage to use the HD for apps and data. It was easier than expected, but still a hack and need some tuning. So don't blame me if it doesn't run on your device.
Okay here is what I have done:
(I use Ubuntu and don't know how to do it on Windows or iOS)
a) Reset and format the device and the HD to start with a clean environment. (Don't forget to save your data somewhere outside)
b) Download and extract @Quallenauge 's CM11 ROM 09_03_2014-12_04_52
c) Mount the archos.ext4.update file
d) Fix the init.archosa101hboard.rc (init.archosa80hboard.rc) file to get the correct file loaded fstab.archosa101hboard (fstab.archosa80hboard.rc)
-> Just seach for 101s (80s) and change to 101h (80h)
e) Change fstab.archosa101hboard (fstab.archosa80hboard.rc) to use the HD for /data:
Code:
#/dev/block/platform/omap/omap_hsmmc.1/by-name/FACTORYFS /system ext4 ro,barrier=1 wait
#/dev/block/platform/omap/omap_hsmmc.1/by-name/EFS /efs ext4 nosuid,nodev,barrier=1 wait,check
#/dev/block/platform/omap/omap_hsmmc.1/by-name/DATAFS /data ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check,encryptable=footer
#/dev/block/platform/omap/omap_hsmmc.1/by-name/CACHE /cache ext4 noatime,nosuid,nodev,barrier=1,discard,noauto_da_alloc,journal_async_commit wait,check
# mount rawfs /dev/block/mmcblk0p1 /mnt/rawfs
# mount ext4 /dev/block/mmcblk0p2 /mnt/system noatime nosuid noexec
# mount ext4 /dev/block/mmcblk0p4 /data noatime nosuid
#/dev/block/mmcblk0p1 /mnt/rawfs rawfs
/dev/block/mmcblk0p2 /mnt/system ext4 noatime,nosuid,noexec wait
#/dev/block/mmcblk0p4 /data ext4 noatime,nosuid wait,check,encryptable=footer
/dev/block/platform/omap/usbhs_omap/sda1 /data ext4 defaults 0 2
/devices/platform/omap/omap_hsmmc.0 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/omap/musb-omap2430/musb-hdrc/usb2/2-1/2-1:1.0 auto auto defaults voldmanaged=usbdisk:auto
#/dev/block/platform/omap/usbhs_omap/sda1 /storage/sdcard1 ext4 defaults 0 2
/dev/block/zram0 none swap defaults zramsize=134217728
f) Unmount the archos.ext4.update file
g) Install as usual
My impressions:
- I could install all (!) my apps :laugh:
- I have still only 512 MB RAM, so e.g. Adblock Plus be stopped when Chrome is running. I have installed Greenify, which helps a bit. Need more investigation. Any thoughts are welcome!
- Booting takes a bit longer
- As the HD is used to falling quick back in sleep mode and it cannot cache all needed files, it takes some extra time to open an app or switch to one of the other screens.
- Don't know what to do with /dev/block/mmcblk0p4 - Can we use it for caching the HD or as swap device?
- After some time sleeping, the device need to reboot by long pressing on/off (I think that is in discussion in the main [ROM] [4.4.2] CyanogenMod 11.0 thread)
- Not tested yet, but activating the 3g dongle for USB memory would change the HD partiion from sda1 to sdb1, so wouldn't run. Maybe copying the HD to a SD card would be nice to have.
- Battery time: Don't know, as it is always plugged in
At the end I think it is the best ROM for this poor device - so thanks again @Quallenauge
Click to expand...
Click to collapse
Nice work [email protected] I'm glad someone is still trying to bring this tablet to the present. Let me know if you need a tester. I have a 80 G9 Turbo 250GB.
Related
So,
I am at a loss on how to get the GN to activate USB storage in CM Recovery.
parted shows:
Code:
~ # parted /dev/block/platform/omap/omap_hsmmc.0/mmcblk0 print
Model: MMC VYL00M (sd/mmc)
Disk /dev/block/mmcblk0: 15.8GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 131kB 262kB 131kB xloader
2 524kB 4194kB 3670kB sbl
3 4194kB 25.2MB 21.0MB ext4 efs
4 25.2MB 33.6MB 8389kB param
5 33.6MB 37.7MB 4194kB misc
6 37.7MB 41.9MB 4194kB dgs
7 41.9MB 50.3MB 8389kB boot
8 50.3MB 62.8MB 12.5MB recovery
13 62.8MB 62.9MB 65.5kB metadata
9 62.9MB 79.7MB 16.8MB radio
10 79.7MB 765MB 686MB ext4 system
11 765MB 1218MB 453MB ext4 cache
12 1218MB 15.8GB 14.5GB ext4 userdata
so, I see part 12 as my "/mnt/sdcard" partition..
previous versions I looked at had syntax like:
Code:
case $1 in
on)
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
echo "USB Mass Storage enabled"
;;
off)
echo "" > /sys/devices/platform/usb_mass_storage/lun0/file
echo "USB Mass Storage disabled"
;;
--)
;;
On this device, there is:
Code:
[email protected]:/sys/devices/platform/omap/omap_hsmmc.0
lrwxrwxrwx root root 2012-01-26 10:15 driver -> ../../../../bus/platform/drivers/omap_hsmmc
-r--r--r-- root root 4096 2012-01-26 10:15 microamps_requested_omap_hsmmc.0-vmmc
drwxr-xr-x root root 2012-01-26 09:49 mmc_host
-r--r--r-- root root 4096 2012-01-26 10:15 modalias
drwxr-xr-x root root 2012-01-26 09:49 power
lrwxrwxrwx root root 2012-01-26 10:15 subsystem -> ../../../../bus/platform
-rw-r--r-- root root 4096 2012-01-26 09:49 uevent
Anyone have any ideas how to do this before I spend a day figuring it out?
Thanks!
Anyone have any ideas how to do this [...] ?
Click to expand...
Click to collapse
You can't. There is no UMS/mass storage support with the Galaxy Nexus.
(This thread should be in the q&a section.)
gokpog said:
You can't. There is no UMS/mass storage support with the Galaxy Nexus.
(This thread should be in the q&a section.)
Click to expand...
Click to collapse
+1
(10 chars)
use adb push pull for your basic requirements
It's also not CM Recovery. It's Clockwork Recovery.
Also wrong section.
gokpog said:
You can't. There is no UMS/mass storage support with the Galaxy Nexus.
(This thread should be in the q&a section.)
Click to expand...
Click to collapse
There actually is.. It is in the kernel I am using, and I can successfully send a block device out it using /sys/devices/platform/omap/musb-omap2430/musb-hdrc/gadget/lun0/file
The nexus has to have it's persistent usb modes set properly (turn off MTP)..
I just cannot make it work in recovery even though it's kernel has the feature as well. Recovery is the only place I want it too
Oh well, I'll keep using ad like I have been.
Thanks
ghost_o said:
There actually is.. It is in the kernel I am using, and I can successfully send a block device out it using /sys/devices/platform/omap/musb-omap2430/musb-hdrc/gadget/lun0/file
The nexus has to have it's persistent usb modes set properly (turn off MTP)..
I just cannot make it work in recovery even though it's kernel has the feature as well. Recovery is the only place I want it too
Oh well, I'll keep using ad like I have been.
Thanks
Click to expand...
Click to collapse
ghost_o, I really want to know how you can make it work. I setted the persistent usb config to only adb (no mtp) and tried to sent the userdata block device to that lun0 but the block device is not properly sent to the usb connected computer. My goal is to be able to use an app called usb sharer or something similar.
Without Ninthsense and Roothorick this would not be possible, and all credit for this belongs to them!
This is a guide for installing a recovery.img from your SDcard, without the use of your USB port, ODIN, or CWM
This is through the android terminal emulator app, with root permissions. or via ADB over WIFI
**The issue: I cannot transfer data at all through my USB port and was not gonna attempt flashing out of fear of brick!
I was able to extract the recovery.img from the ODIN flashable CWMrecovery 6.0.1.2 package developed by Terinfire but was unable to create a CWM flashable zip because I lack the expertise. (I still have my old CWM touch recovery developed by Aquethys).
After reaching out Ninthsense and Roothorick helped me with the command line to make this possible.
Whats needed:
1) a broke USB (don't attempt this unless its the very last option)
2) the recovery image file for this phone
3) ROOT ACCESS!!!
4) a terminal app or ADB over WIFI
Below is the Partition Table for the Glide(thanks ninthsense):
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
To connect ADB over WIFI (thanks ninthsense):
Connect your phone and laptop to your wifi.
Goto Settings developer options - turn on "ADB over netwrok"
adb connect 192.168.x.x:5555
**if doing this using ADB you must enter a shell and run the su command
adb shell
su
Now do the following:
1) move "recovery.img" to root of SDcard
2) backup current recovery:
(if in terminal and not ADB over WIFI you must enter "su" before continuing)
dd if=/dev/block/mmcblk0p8 of=/sdcard/current-recovery.img
3) Install new recovery:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
Thats it!!!! reboot recovery and enjoy!!!
Hey you forgot the first step :laugh: , on how to connect to the device through "ADB over network".
ninthsense said:
Hey you forgot the first step :laugh: , on how to connect to the device through "ADB over network".
Click to expand...
Click to collapse
I will modify the OP, I figured I would list the terminal steps because of its ease of use Ill add both!
**edit** done! how's that looking?
Cprager said:
I will modify the OP, I figured I would list the terminal steps because of its ease of use Ill add both!
Click to expand...
Click to collapse
Add the list of partitions as well, maybe somebody will find it useful for backing up and restoring something else as well.
ninthsense said:
Add the list of partitions as well, maybe somebody will find it useful for backing up and restoring something else as well.
Click to expand...
Click to collapse
done!
You're a life saver!!!!
Cprager said:
Without Ninthsense and Roothorick this would not be possible, and all credit for this belongs to them!
This is a guide for installing a recovery.img from your SDcard, without the use of your USB port, ODIN, or CWM
This is through the android terminal emulator app, with root permissions. or via ADB over WIFI
**The issue: I cannot transfer data at all through my USB port and was not gonna attempt flashing out of fear of brick!
I was able to extract the recovery.img from the ODIN flashable CWMrecovery 6.0.1.2 package developed by Terinfire but was unable to create a CWM flashable zip because I lack the expertise. (I still have my old CWM touch recovery developed by Aquethys).
After reaching out Ninthsense and Roothorick helped me with the command line to make this possible.
Whats needed:
1) a broke USB (don't attempt this unless its the very last option)
2) the recovery image file for this phone
3) ROOT ACCESS!!!
4) a terminal app or ADB over WIFI
Below is the Partition Table for the Glide(thanks ninthsense):
Starting recovery on Fri Dec 28 19:23:18 2012
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v6.0.0.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p9 (null) 0
2 /cache ext4 /dev/block/mmcblk0p3 (null) 0
3 /data ext4 /dev/block/mmcblk0p6 (null) 0
4 /recovery emmc /dev/block/mmcblk0p8 (null) 0
5 /sdcard vfat /dev/block/mmcblk0p4 /dev/block/mmcblk0 0
6 /system ext4 /dev/block/mmcblk0p2 (null) 0
7 /efs ext4 /dev/block/mmcblk0p1 (null) 0
To connect ADB over WIFI (thanks ninthsense):
Connect your phone and laptop to your wifi.
Goto Settings developer options - turn on "ADB over netwrok"
adb connect 192.168.x.x:5555
**if doing this using ADB you must enter a shell and run the su command
adb shell
su
Now do the following:
1) move "recovery.img" to root of SDcard
2) backup current recovery:
(if in terminal and not ADB over WIFI you must enter "su" before continuing)
dd if=/dev/block/mmcblk0p8 of=/sdcard/current-recovery.img
3) Install new recovery:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p8
Thats it!!!! reboot recovery and enjoy!!!
Click to expand...
Click to collapse
:victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory::victory:
I cannot thank you enough for this post! I was trying to locate that partition since the USB doesn't work on the Glide I am repairing, and alas! - you came and saved the day!
Thanks alot, mate!
:good::good::good::good::good::good::good::good::good::good::good::good::good::good::good::good:
Hi,
recently i updated via CWM my unblocked, rooted xperia m (C1905). Phone has FXP317, earlier i updated radio installing stock 4.3 and it going well, besides fatal GPS, as usual
After upgrade form FXP317 to FXP319 and reboot phone, it running veeeryy slow and suddenly hangs up. After restart to CWM (it lasts couple minutes), i try to install it again (install from zip) and it failed - it shows problem with mounting /DATA.
Now i attempt to format /DATA but it failed - CWM says that partition can't be mounted.
Another try - flash stock rom (Flasher form Androxyde) gives
Code:
19/048/2014 07:48:57 - INFO - Device connected in flash mode
19/049/2014 07:49:06 - INFO - Selected Bundle for Xperia M C1905. FW release : Google Android 4.3 (Jelly Bean). Customization : 15.4.A.0.23
19/049/2014 07:49:06 - INFO - Preparing files for flashing
19/049/2014 07:49:53 - INFO - Please connect your device into flashmode.
19/049/2014 07:49:54 - INFO - Opening device for R/W
19/049/2014 07:49:54 - INFO - Reading device information
19/049/2014 07:49:54 - INFO - Phone ready for flashmode operations.
19/049/2014 07:49:54 - INFO - Current device : Unknown: Mar 7 2014/10:51:59 - YT910M7GB9 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59 - Unknown: Mar 7 2014/10:51:59
19/049/2014 07:49:54 - INFO - Start Flashing
19/049/2014 07:49:54 - INFO - Processing loader.sin
19/049/2014 07:49:54 - INFO - Checking header
19/049/2014 07:49:54 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of loader.sin finished.
19/049/2014 07:49:55 - INFO - Loader : S1_Root_dbe9 - Version : loader_MSM8X30_10 / Boot version : S1_Boot_MSM_8227_5 / Bootloader status : ROOTED
19/049/2014 07:49:55 - INFO - Processing partition-image.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - INFO - Processing of partition-image.sin finished.
19/049/2014 07:49:55 - INFO - Parsing boot delivery
19/049/2014 07:49:55 - INFO - Phone boot version : S1_Boot_MSM_8227_5. Boot delivery version : S1_Boot_MSM_8227_5
19/049/2014 07:49:55 - INFO - Boot delivery up to date. Nothing to do
19/049/2014 07:49:55 - INFO - Processing kernel.sin
19/049/2014 07:49:55 - INFO - Checking header
19/049/2014 07:49:55 - INFO - Flashing data
19/049/2014 07:49:55 - ERROR - Processing of kernel.sin finished with errors.
19/049/2014 07:49:55 - INFO - Ending flash session
19/049/2014 07:49:55 - ERROR - ERR_SEVERITY="MINOR";ERR_CODE="0017";ERR_DYNAMIC="0x8020001C ";
Soft from SONY - SUS, PC Companion, EMMA did't recognize my phone and gives up.
Meanwhile i flash kernel and i made fatal mistake (i thought so) - i tried to flash wrong kernel (it has 83 bytes), but after choosing the right file I could install the appropriate kernel.
Now i have CWM 6.0.4.8, and i can connect phone in flash mode, also in fastboot but i can't flash any rom because i can't mount /data
Command adb devices -l gives
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
How to mount /data or how to do the re-partition? What should I do to flash the stock rom?
Have you flashed the stock ROM again? Does it still show the same error?
elmkzgirxp said:
Have you flashed the stock ROM again? Does it still show the same error?
Click to expand...
Click to collapse
Yes, i did and same again. I have stock ROM 4.1.2, stock ROM 4.3. One thing - phone starts and - after maybe 30 min or so - stops on "Encryption unsuccessful bla bla bla". I try even recovery backup form http://forum.xda-developers.com/showthread.php?p=51574842 but it failed - folder /system cannot be restored.
I'm thinking about partitioning internal memory, but i don't know how. I have an access via flashmode and i'm looking for solution about using adb
Encryption? How'd that get there?
elmkzgirxp said:
Encryption? How'd that get there?
Click to expand...
Click to collapse
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.
TomekParuszewski said:
In my case - remove battery, wait 5 sec, i turn on the phone and wait about 30 min - after that long boot this is all i see.
Click to expand...
Click to collapse
Why not refer here... This might solve your problem.
elmkzgirxp said:
Why not refer here... This might solve your problem.
Click to expand...
Click to collapse
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see
Exact same problem
With fxp 18
TomekParuszewski said:
Thx, so far i don't find exactly the same problem as mine, but now i try rubber band trick. I don't know how this will help, will see
Click to expand...
Click to collapse
Hmm, according to the definition of soft brick, and therefore that I can enter fastboot mode and flashmode and CWM, the phone is not soft bricked, but there is a problem with partitions or privileges SU, because I can not reflash rom. The system is still not able to mount the directory / data.
I will try connect to phone by the adb command and see, err, i don't know what - i must check available commands. Right now i'm waiting for CWM
After get into adb shell i get:
Code:
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nsu
su
/sbin/sh: su: not found
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
C:\SDK\sdk\platform-tools>adb remount
remount failed: Success
C:\SDK\sdk\platform-tools>adb devices -l
List of devices attached
YT910M7GB9 recovery product:C1905 model:C1905 device:nicki
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6ndf -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 430.6M 128.0K 430.4M 0% /dev
tmpfs 430.6M 8.0K 430.6M 0% /tmp
tmpfs 430.6M 0 430.6M 0% /storage
tmpfs 430.6M 0 430.6M 0% /mnt/secure
tmpfs 430.6M 0 430.6M 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
246.2M 4.6M 241.7M 2% /cache
~ # ←[6nfdisk
fdisk
BusyBox v1.22.1 static (2014-04-06 21:24 +0200) multi-call binary.
Usage: fdisk [-ul] [-C CYLINDERS] [-H HEADS] [-S SECTORS] [-b SSZ] DISK
Change partition table
-u Start and End are in sectors (instead of cylinders)
-l Show partition table for each DISK, then exit
-b 2048 (for certain MO disks) use 2048-byte sectors
-C CYLINDERS Set number of cylinders/heads/sectors
-H HEADS
-S SECTORS
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6nfdisk -l
fdisk -l
~ # ←[6n^C
C:\SDK\sdk\platform-tools>
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls
ls
boot logo.rle
boot.txt mnt
cache proc
charger property_contexts
data recovery
datadata res
default.prop root
dev sbin
emmc sd-ext
etc sdcard
external_sd seapp_contexts
file_contexts sepolicy
fstab.qcom storage
init sys
init.qcom.syspart_fixup.sh system
init.rc tmp
init.recovery.qcom.rc ueventd.qcom.rc
internal_sd ueventd.rc
~ # ←[6ndf
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 440892 128 440764 0% /dev
tmpfs 440892 8 440884 0% /tmp
tmpfs 440892 0 440892 0% /storage
tmpfs 440892 0 440892 0% /mnt/secure
tmpfs 440892 0 440892 0% /mnt/fuse
/dev/block/platform/msm_sdcc.1/by-name/cache
252136 4660 247476 2% /cache
~ # ←[6ncd data
cd data
/data # ←[6nls
ls
media
/data # ←[6n^C
C:\SDK\sdk\platform-tools>adb shell
~ # ←[6nls -l
ls -l
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x 2 root root 0 May 21 04:33 boot
-rw-r--r-- 1 root root 579 May 21 04:33 boot.txt
drwxrwx--x 6 system cache 4096 May 17 10:36 cache
-rwxr-x--- 1 root root 284696 May 21 04:33 charger
drwxr-xr-x 3 root root 0 May 21 04:33 data
drwxr-xr-x 2 root root 0 May 21 04:33 datadata
-rw-r--r-- 1 root root 3920 May 21 04:33 default.prop
drwxr-xr-x 10 root root 3260 May 21 04:33 dev
drwxr-xr-x 2 root root 0 May 21 04:33 emmc
drwxr-xr-x 2 root root 0 May 21 04:33 etc
drwxr-xr-x 2 root root 0 May 21 04:33 external_sd
-rw-r--r-- 1 root root 10961 May 21 04:33 file_contexts
-rw-r----- 1 root root 1213 May 21 04:33 fstab.qcom
-rwxr-x--- 1 root root 187840 May 21 04:33 init
-rwxr-x--- 1 root root 2704 May 21 04:33 init.qcom.syspart_fixup.sh
-rwxr-x--- 1 root root 2892 May 21 04:33 init.rc
-rwxr-x--- 1 root root 512 May 21 04:33 init.recovery.qcom.rc
drwxr-xr-x 2 root root 0 May 21 04:33 internal_sd
-rw-r--r-- 1 root root 14452 Jan 1 1970 logo.rle
drwxrwxr-x 5 root system 0 May 21 04:33 mnt
dr-xr-xr-x 131 root root 0 Jan 1 1970 proc
-rw-r--r-- 1 root root 2161 May 21 04:33 property_contexts
drwxr-xr-x 2 root root 0 May 21 04:33 recovery
drwxr-xr-x 3 root root 0 May 21 04:33 res
drwx------ 2 root root 0 May 13 22:52 root
drwxr-x--- 2 root root 0 May 21 04:33 sbin
drwxr-xr-x 2 root root 0 May 21 04:33 sd-ext
lrwxrwxrwx 1 root root 11 May 21 04:33 sdcard -> /data/media
-rw-r--r-- 1 root root 660 May 21 04:33 seapp_contexts
-rw-r--r-- 1 root root 95689 May 21 04:33 sepolicy
d---r-x--- 2 root sdcard_r 40 May 21 04:33 storage
dr-xr-xr-x 14 root root 0 May 21 04:33 sys
drwxr-xr-x 3 root root 0 May 21 04:33 system
drwxrwxr-x 2 root shell 60 May 21 04:33 tmp
-rw-r--r-- 1 root root 8196 May 21 04:33 ueventd.qcom.rc
-rw-r--r-- 1 root root 7275 May 21 04:33 ueventd.rc
I don't have any information about partitions (filesystem tmpfs)!
TomekParuszewski said:
I don't have any information about partitions (filesystem tmpfs)!
Click to expand...
Click to collapse
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.
Bonoboo said:
Firstly you need mount partitions through recovery: item mounts and storage
Also from there try to format all of them and then flash via flashtool / via ZIP / restore backup.
Here is possibility that your NAND-flash (internal 4GB memory chip) broken or have a lot bad sectors.
Click to expand...
Click to collapse
Unfortunately, I can not mount / data or / system. After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears. is below:
(i'm wainting rught now - 14:29)
I have version 6.0.4.8 CWM and I see no formatting options. I tried to upload the CWM 6.0.4.7 from this post http://forum.xda-developers.com/showthread.php?t=2494793 but I could not do that. I still have my version. My bad, of course i have format command.
Does this mean that my phone died? Do I still have any chance to fix it?
TomekParuszewski said:
After a very long time the command mount / data, then throws an error, the contents of which I can not remember now. I will try to rewrite its contents exactly as it appears.
Click to expand...
Click to collapse
Command from ADB? Try from recovery menu.
And output of command will be helpful.
TomekParuszewski said:
Does this mean that my phone died?
Click to expand...
Click to collapse
Don't give up for now.
UPD: I googled ERR_DYNAMIC=0x8020001C and found 7 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6, 7
All them have error while flashing different parts: kernel and data.
And no solution there for now.
Bonoboo said:
Command from ADB? Try from recovery menu.
And output of command will be helpful.
Don't give up for now.
Click to expand...
Click to collapse
thank you for your words of encouragement - I'm gonna fight to the end
BTW - in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)
Bonoboo said:
UPD: I googled ERR_DYNAMIC=0x8020001C and found 6 threads with same problem with Xperia M:
1, 2, 3, 4, 5, 6
All them have error while flashing different parts: kernel and data.
And no solution there for now.
Click to expand...
Click to collapse
yes, most of them i've seen, thx
Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
2. Try mounts and storage > format all
3. Try mount via menu in recovery
Bonoboo said:
Just info :
Re-partition method not available for now.
Maybe when flashing via flashtool keep tick only on partition-image.sin restore stock.
There is some method to erase internal memory via adb, but it for other model.
And I don't know will it help here.
Questions:
1. So your device not was encrypted, right?
3. You sure that in mounts and storage no format options?
4. Try mount via menu in recovery?
2. How about post error while mounting?
Click to expand...
Click to collapse
Answers:
If i'm wait long enough, phone boot to screen "Encryption unsuccessful", so i don't know - I do not encrypt the phone as I remember
Sorry, of course there is format command in recovery, my bad
I will try again and write exact message from the screen
Sorry for messing numbers, I edited post.
TomekParuszewski said:
in time when i'm waiting to output for command mount /data from recovery, I have access to the phone via adb (but it's normal after all, i suppose)
Click to expand...
Click to collapse
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
FOTAKernel -> /dev/block/mmcblk0p23
LTALabel -> /dev/block/mmcblk0p16
TA -> /dev/block/mmcblk0p1
aboot -> /dev/block/mmcblk0p6
alt_aboot -> /dev/block/mmcblk0p12
alt_rpm -> /dev/block/mmcblk0p15
alt_s1sbl2 -> /dev/block/mmcblk0p10
alt_sbl1 -> /dev/block/mmcblk0p8
alt_sbl2 -> /dev/block/mmcblk0p9
alt_sbl3 -> /dev/block/mmcblk0p11
alt_tz -> /dev/block/mmcblk0p13
boot -> /dev/block/mmcblk0p17
cache -> /dev/block/mmcblk0p26
fsg -> /dev/block/mmcblk0p21
modem -> /dev/block/mmcblk0p18
modemst1 -> /dev/block/mmcblk0p19
modemst2 -> /dev/block/mmcblk0p20
persist -> /dev/block/mmcblk0p24
ramdump -> /dev/block/mmcblk0p22
rpm -> /dev/block/mmcblk0p14
s1sbl2 -> /dev/block/mmcblk0p4
sbl1 -> /dev/block/mmcblk0p2
sbl2 -> /dev/block/mmcblk0p3
sbl3 -> /dev/block/mmcblk0p5
system -> /dev/block/mmcblk0p25
tz -> /dev/block/mmcblk0p7
userdata -> /dev/block/mmcblk0p27
Bonoboo said:
Sorry for messing numbers, I edited post.
Seems not. Reboot.
Try formatting.
Just note about adb output earlier.
ls shows temporary FS that recovery creates in RAM.
By fact blocks devices in /dev/block/ and we can do something with them, like recreate partitions using mke2fs
Or erase them by dd if=/dev/zero
Try commands:
cat /proc/partitions
mount
fdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p5
And try flashing via flashtool:
– untick wipe data and cache
– tick all in Exclude section except partition
Here useful commands (similar problem for Samsung, restoring partition table helps)
And here list of all our partitions relatively number:
Click to expand...
Click to collapse
ok, here the log from CWM - i don't know when each event occurred
Code:
persist.audio.low.latency.rec=false
persist.debug.wfd.enable=1
persist.radio.apm_sim_not_pwdn=1
persist.timed.enable=true
persist.fuse_sdcard=true
keyguard.no_require_sim=true
telephonu.lteOnCdmaDevice=0
DEVICE_PROVISIONED=1
I: Checking for extendedcommand
I:Skipping for extendedcommand, file not found...
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
I:using /data/media for /sdcard/0/clockworkmod/.no_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:using /data/media for /sdcard/0/clockworkmod/.many_confirm.
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/userdata on /data failed: invalid argument
W:failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata (File exists)
I:Can't partition non mmcblk device: /devices/platform/msm_sdcc.3/mmc_host/mmc1
And here is the result of your command
Code:
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
YT910M7GB9 recovery
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>adb shell
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 3866624 mmcblk0
179 1 2048 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 256 mmcblk0p4
179 5 512 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 128 mmcblk0p8
179 9 256 mmcblk0p9
179 10 256 mmcblk0p10
179 11 512 mmcblk0p11
179 12 512 mmcblk0p12
179 13 512 mmcblk0p13
179 14 512 mmcblk0p14
179 15 512 mmcblk0p15
179 16 16384 mmcblk0p16
179 17 20480 mmcblk0p17
179 18 65536 mmcblk0p18
179 19 3072 mmcblk0p19
179 20 3072 mmcblk0p20
179 21 3072 mmcblk0p21
179 22 5120 mmcblk0p22
179 23 16384 mmcblk0p23
179 24 4096 mmcblk0p24
179 25 1228800 mmcblk0p25
179 26 256000 mmcblk0p26
179 27 2183151 mmcblk0p27
179 32 1955840 mmcblk1
179 33 1954816 mmcblk1p1
~ # ←[6nls -la /dev/block/mmcblk*
ls -la /dev/block/mmcblk*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- 1 root root 179, 0 May 21 11:43 /dev/block/mmcblk0
brw------- 1 root root 179, 1 May 21 11:43 /dev/block/mmcblk0p1
brw------- 1 root root 179, 10 May 21 11:43 /dev/block/mmcblk0p10
brw------- 1 root root 179, 11 May 21 11:43 /dev/block/mmcblk0p11
brw------- 1 root root 179, 12 May 21 11:43 /dev/block/mmcblk0p12
brw------- 1 root root 179, 13 May 21 11:43 /dev/block/mmcblk0p13
brw------- 1 root root 179, 14 May 21 11:43 /dev/block/mmcblk0p14
brw------- 1 root root 179, 15 May 21 11:43 /dev/block/mmcblk0p15
brw------- 1 root root 179, 16 May 21 11:43 /dev/block/mmcblk0p16
brw------- 1 root root 179, 17 May 21 11:43 /dev/block/mmcblk0p17
brw------- 1 root root 179, 18 May 21 11:43 /dev/block/mmcblk0p18
brw------- 1 root root 179, 19 May 21 11:43 /dev/block/mmcblk0p19
brw------- 1 root root 179, 2 May 21 11:43 /dev/block/mmcblk0p2
brw------- 1 root root 179, 20 May 21 11:43 /dev/block/mmcblk0p20
brw------- 1 root root 179, 21 May 21 11:43 /dev/block/mmcblk0p21
brw------- 1 root root 179, 22 May 21 11:43 /dev/block/mmcblk0p22
brw------- 1 root root 179, 23 May 21 11:43 /dev/block/mmcblk0p23
brw------- 1 root root 179, 24 May 21 11:43 /dev/block/mmcblk0p24
brw------- 1 root root 179, 25 May 21 11:43 /dev/block/mmcblk0p25
brw------- 1 root root 179, 26 May 21 11:43 /dev/block/mmcblk0p26
brw------- 1 root root 179, 27 May 21 11:43 /dev/block/mmcblk0p27
brw------- 1 root root 179, 3 May 21 11:43 /dev/block/mmcblk0p3
brw------- 1 root root 179, 4 May 21 11:43 /dev/block/mmcblk0p4
brw------- 1 root root 179, 5 May 21 11:43 /dev/block/mmcblk0p5
brw------- 1 root root 179, 6 May 21 11:43 /dev/block/mmcblk0p6
brw------- 1 root root 179, 7 May 21 11:43 /dev/block/mmcblk0p7
brw------- 1 root root 179, 8 May 21 11:43 /dev/block/mmcblk0p8
brw------- 1 root root 179, 9 May 21 11:43 /dev/block/mmcblk0p9
brw------- 1 root root 179, 32 May 21 11:43 /dev/block/mmcblk1
brw------- 1 root root 179, 33 May 21 11:43 /dev/block/mmcblk1p1
~ # ←[6nmount
mount
rootfs on / type rootfs (rw,seclabel,relatime)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/platform/msm_sdcc.1/by-name/cache on /cache type ext4 (rw,seclabel,re
latime,data=ordered)
~ # ←[6nfdisk -l /dev/block/mmcblk0p17
fdisk -l /dev/block/mmcblk0p17
Disk /dev/block/mmcblk0p17: 20 MB, 20971520 bytes
4 heads, 16 sectors/track, 640 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p17 doesn't contain a valid partition table
~ # ←[6nfdisk -l /dev/block/mmcblk0p5
fdisk -l /dev/block/mmcblk0p5
Disk /dev/block/mmcblk0p5: 0 MB, 524288 bytes
4 heads, 16 sectors/track, 16 cylinders
Units = cylinders of 64 * 512 = 32768 bytes
Disk /dev/block/mmcblk0p5 doesn't contain a valid partition table
~ # ←[6n
C:\adt-bundle-windows-x86-20140321\adt-bundle-windows-x86-20140321\sdk\platform-
tools>
If both partitions are incorrect, should I try to flash?
My S3 went haywire a few days ago and in my attempts to recover data I loaded the TWRP bootloader and a custom ROM hoping I could eventually reboot it and reset the flash counter. Unfortunately, it still won't reboot - it hangs on the pulsing SAMSUNG animation, after the "Samsung Galaxy SIII" splash screen and the Android blast-off animation.
I've already done a cache wipe and factory reset so ideally I'd like to get it into a state where I can run data recovery software to retrieve my deleted files. But if that can't be done, at the least I want to reset the flash counter so the phone will be replaced under warranty.
Since I received the last replacement in Oct 2013 I forgot to enable USB Debugging and I didn't root phone. In my searches, it looks like the power button is stuck (doesn't feel like it, though) and the phone randomly reboots when is Recovery Mode or Download Mode. About 10% of the time I can get it into either mode and remain stable.
Tools I downloaded & installed:
SkipSoft Android Toolkit (updated and registered)
Samsung USB Drivers v1.5.42.0
Google ADT (updated)
Odin 3.09
Here's what I haven/haven't done so far:
Haven't enabled USB Debugging in the OS
Haven't rooted phone
Installed TWRP 2.7.0.0
Installed root66_TMO_T999UVDMD5.tar, but device still won't boot completely
After TWRP installed, I had to updated driver in Device Manager to "Intel USB Flash Loader Utility" from Samsung. In the TWRP logs I see:
E: Could not mount /data and unable to find crypto footer.
E: Unable to mount '/data'
E: Unable to recreate /data/media folder.
Updating partition details...
E: Unable to mount '/data'
E: Unable to mount internal storage.
E: Unable to mount /data/media during GUI startup.
Full SELinux support is present.
Running boot script...
Finished running boot script.
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file.
E: Unable to mount '/data'
Do I have any hope of recovering the data or resetting the flash counter? I've also considered trying JTAG recovery through a local vendor, but still would like to reset the counter.
Thanks - any help would be GREATLY appreciated.
some progress
OK, with some persistence I managed to get the device to a bootable state. I managed to installed TWRP Bootloader and Chainfire's SuperUser, and that got the phone bootable. Android version is 4.1.2, USB Debugging is now ON, and I went through the setup process but disabled all antennas once I noticed it was downloading content.... PHEW...
For anyone dealing with this issue, here's what worked and didn't:
1 - Spraying CRC brand circuit cleaner on power button - didn't try it, too lazy/scared that I'd break something else
2 - Knocking Power button with a pencil eraser (found elsewhere in xda-developers forum) - this seemed to clear up the issue intermittently
3 - Loaded TWRP using Odin - this worked
4 - Loaded Chainfire AutoRoot - this failed when using miscellaneous tutorials online, BUT it worked when I went straight to the CF Autoroot site (autoroot.chainfire.eu) downloaded the specific file for my device, and loaded it via Odin
Now I'm trying to get data recovery software to recognize the device to analyze the drive and find any recoverable data. Any suggestions?
So far I've tried:
Recuva - unable to see phone
Asoftech Data Recovery - unable to see phone
Glary Undelete - unable to see phone
yodot - unable to see phone
Search xda for an app called Easy UMS. (I think). Then use it to connect as a USB Mass Storage device. If that doesn't help im not sure what else to tell you.
DocHoliday77 said:
Search xda for an app called Easy UMS. (I think). Then use it to connect as a USB Mass Storage device. If that doesn't help im not sure what else to tell you.
Click to expand...
Click to collapse
DocHoliday - thanks for the tip, but Easy UMS only allows access to the external SD card. I'm continuing my search. There must be something that at least allows a full bit-wise backup of the entire device to an SD card that I can then use for forensics.
maradamc said:
DocHoliday - thanks for the tip, but Easy UMS only allows access to the external SD card. I'm continuing my search. There must be something that at least allows a full bit-wise backup of the entire device to an SD card that I can then use for forensics.
Click to expand...
Click to collapse
It looks like BusyBox and the DD command can create a bit-by-bit partition dump but I'm not sure how to issue the commands. I have ADB and SU access, BusyBox installed.
dd if=/dev/block/mmcblk0p15 of=c:\path\saving\to
This will dump the entire userdata partition to an image file on your Windows computer. Note the direction of the /'s.
Thanks Doc! I reformatted my external SD Card to exFAT, then ran the DD command to dump the userdata partition. I'm using DiskInternals Linux Recovery right now to scan the image for any recoverable files.
Where can I find more info on those different partitions in /dev/block/? I think some of the files I want to recover are in /data/data/ and I don't know which partition that would be. I've tried "mount" and "ls -l /dev/block/platform/*/by-name/" but I can't find any reference to a /data/ mount.
My last shot will be to downgrade the OS to ICS version and try data recovery directly via the USB cable. All this stuff I'm finding sure will make a good tutorial afterwards.
The dump you created is the entire /data partition. So it should have everything you need. (Userdata/data, same thing in this case. Sorry if I wasn't more clear on that)
You can google t999 galaxy s3 partition layout and should be able to find the rest. Don't have time to look it up and write it ir I'd just post it here for you.
I did some digging and found I need to pull data from:
/sdcard/callrecorder/
/storage/emulated/0/sounds/
I'm trying to decipher if I need to dump any additional partitions. No luck finding much useful information on S3 partitions - this was the closest I found - http://forum.xda-developers.com/galaxy-s3/general/galaxy-s-iii-partition-layout-basic-efs-t1689623
In ADB, I retrieved the following, but none of them obviously map to sdcard or storage/emulated.
ls -l /dev/block/platform/*/by-name/
lrwxrwxrwx root root 1969-12-31 22:16 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 1969-12-31 22:16 backup -> /dev/block/mmcblk0p20
lrwxrwxrwx root root 1969-12-31 22:16 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 1969-12-31 22:16 cache -> /dev/block/mmcblk0p17
lrwxrwxrwx root root 1969-12-31 22:16 efs -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 1969-12-31 22:16 fota -> /dev/block/mmcblk0p19
lrwxrwxrwx root root 1969-12-31 22:16 fsg -> /dev/block/mmcblk0p21
lrwxrwxrwx root root 1969-12-31 22:16 grow -> /dev/block/mmcblk0p23
lrwxrwxrwx root root 1969-12-31 22:16 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 1969-12-31 22:16 modemst1 -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 1969-12-31 22:16 modemst2 -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 1969-12-31 22:16 pad -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 1969-12-31 22:16 param -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 1969-12-31 22:16 persist -> /dev/block/mmcblk0p16
lrwxrwxrwx root root 1969-12-31 22:16 recovery -> /dev/block/mmcblk0p18
lrwxrwxrwx root root 1969-12-31 22:16 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 1969-12-31 22:16 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 1969-12-31 22:16 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 1969-12-31 22:16 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 1969-12-31 22:16 ssd -> /dev/block/mmcblk0p22
lrwxrwxrwx root root 1969-12-31 22:16 system -> /dev/block/mmcblk0p14
lrwxrwxrwx root root 1969-12-31 22:16 tz -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 1969-12-31 22:16 userdata -> /dev/block/mmcblk0p15
[email protected]:/ # mount
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
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/platform/msm_sdcc.1/by-name/system /system ext4 ro,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/userdata /data ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc,discard 0 0
/dev/block/platform/msm_sdcc.1/by-name/cache /cache ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/persist /persist ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/platform/msm_sdcc.1/by-name/modem /firmware vfat ro,relatime,gid=1000,fmask=0006,dmask=0006,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,noexec,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
Additionally, the DD for userdata is 12GB while the whole device is 16GB... still trying to figure out how to capture the remaining 4GB. And to complicate things, I've gotten data recovery software to recognize the image dump and scan it, but the files I want have uncommon file extensions (*.m4a, *.3ga) or no extensions at all. <sigh>... it's gonna be a long week...
The 4gb is reserved for the os and firmware. So a 16gb S3 will have 12gb allocated for /data.
The internal sdcard is not a partition of its own. Its simply part of the data partition.
Also, the link you provided is for the I9300, the international S3 which is a very different device with a different partition layout.
This is ours:
Code:
Number Start End Size FS-Type Name Flags
-------------------------------------------------------------------------------
1 4194304B 67108863B 62914560B modem
2 67108864B 67239935B 131072B sbl1
3 67239936B 67502079B 262144B sbl2
4 67502080B 68026367B 524288B sbl3
5 68026368B 70123519B 2097152B aboot
6 70123520B 70647807B 524288B rpm
7 70647808B 81133567B 10485760B boot
8 81133568B 81657855B 524288B tz
9 81657856B 82182143B 524288B pad
10 82182144B 92667903B 10485760B param
11 92667904B 106954751B 14286848B ext4 efs
12 106954752B 110100479B 3145728B modemst1
13 110100480B 113246207B 3145728B modemst2
14 113246208B 1686110207B 1572864000B ext4 system
15 1686110208B 30337400831B 28651290624B ext4 userdata
16 30337400832B 30345789439B 8388608B ext4 persist
17 30345789440B 31226593279B 880803840B ext4 cache
18 31226593280B 31237079039B 10485760B recovery
19 31237079040B 31247564799B 10485760B fota
20 31247564800B 31253856255B 6291456B backup
21 31253856256B 31257001983B 3145728B fsg
22 31257001984B 31257010175B 8192B ssd
23 31257010176B 31262253055B 5242880B grow
(Just thought it might be a little easier to read this way)
As for pulling the files you need from the .img and the unknown extensions, im not sure. Are you using linux or Windows?
Thanks for that table! I noticed that link wasn't for the T999, which is why I hesitated to rely on it. IDK why I'm having such a hard time finding info on the T999.
Anyway, I managed to DD every single partition by running:
dd if=/dev/block/mmcblk0p5 of=/storage/extSdCard/aboot.img
dd if=/dev/block/mmcblk0p20 of=/storage/extSdCard/backup.img
dd if=/dev/block/mmcblk0p7 of=/storage/extSdCard/boot.img
dd if=/dev/block/mmcblk0p17 of=/storage/extSdCard/cache.img
dd if=/dev/block/mmcblk0p11 of=/storage/extSdCard/efs.img
dd if=/dev/block/mmcblk0p19 of=/storage/extSdCard/fota.img
dd if=/dev/block/mmcblk0p21 of=/storage/extSdCard/fsg.img
dd if=/dev/block/mmcblk0p23 of=/storage/extSdCard/grow.img
dd if=/dev/block/mmcblk0p9 of=/storage/extSdCard/pad.img
dd if=/dev/block/mmcblk0p10 of=/storage/extSdCard/param.img
dd if=/dev/block/mmcblk0p16 of=/storage/extSdCard/persist.img
dd if=/dev/block/mmcblk0p18 of=/storage/extSdCard/recovery.img
dd if=/dev/block/mmcblk0p6 of=/storage/extSdCard/rpm.img
dd if=/dev/block/mmcblk0p2 of=/storage/extSdCard/sb11.img
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/sb12.img
dd if=/dev/block/mmcblk0p4 of=/storage/extSdCard/sb13.img
dd if=/dev/block/mmcblk0p22 of=/storage/extSdCard/ssd.img
dd if=/dev/block/mmcblk0p14 of=/storage/extSdCard/system.img
dd if=/dev/block/mmcblk0p8 of=/storage/extSdCard/tz.img
dd if=/dev/block/mmcblk0p15 of=/storage/extSdCard/userdata.img
For data recovery, I'm running windows and have installed several tools so I'm able to mount the Linux image as a drive.
Cygwin - I've only played with basics in *nix terminal but am comfortable using command prompt
Ext2Fsd
DiskInternals (Linux Reader & Recovery)
OSFMount
I'll tally up the data recovery/carving tools I've downloaded and tried. Now that I have the images dumped, I'm installing ICS 4.0.4 in an attempt to get USB drive access and try the data recovery software directly against the device.
It may seem difficult to find info on the T999, but a lot of that is due to it being posted in other S3 forums. All US S3's are similar enough that most information applies to all of them. The partition table is one of these. They all are partitioned exactly the same.
Btw, when looking for the internal sdcard data, it will be in the /data/media folder. So in the image just look for the media folder.
I will remember that. Any suggestions where to track down /storage/emulated/0/sounds/ from a partition perspective?
I just finished flashing down to ICS 4.0.4. Even though Odin said it was successful, it's hanging on boot-up at the pulsing Samsung logo just like when this whole mess started. Time for another Factory Reset... not like I can do any more harm.
/storage/emulated/0 = /data/media
Nice! My list of pulled partitions matches the one you provided. Glad to know I was on the right track.
So now I have Android 4.0.4 installed on my device. The problem I have now is that the device isn't recognized in Windows and I can't find a driver for it to work. I've tried Samsung_USB_Driver_for_Mobile_Phones_v1.5.14.0 and v1.5.42.0 - no go. Also tried the ADT driver (android_winusb.inf), still no go. Also tried the driver bundled with the Unified Android Toolkit (by SkipSoft, an XDA dev'r) - no luck. Any suggestions? It must be a driver that supports the old USB Drive mode instead of MTP.
For others who might try this downgrade, I rebooted the device into Download mode and during installation, Odin kept getting an error before finishing. I think it was because I was trying to multitask on the computer because once I let Odin do its thing with and stepped away from the PC, the installation completed successfully. Reboots then kept freezing up but a Factory Reset resolved that.
The S3 never supported using UMS (USB drive), so using different driver versions won't make any difference there. Im honestly not sure if anyone's ever found a way to do this at all. Other than the Easy UMS app.
Hello guys, Im a experienced user with ROMs, recovery, boot and etc but i have a problem now, and i will try to explain shortly:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I have a connection with pc(win8.1)
- The computer can communicate with the phone in fastboot mode and adb(recovery)
- the drivers are installed correctly
- BOOTLOOPIN ON GOOGLE
How this happened:
I was minding my own business and my phone was on my desk when it suddenly rebooted itself and then it bootlooped forever. I had some situations when it rebooted itself but always ended in a successful boot, this time it didnt wanted to start.
What have i done till now:
- First thing i entered recovery(TWRP) and dirtyflashed my current rom version and wiped dalvik/cache. (unsuccessful)
- after several times doing the dirtyflash i finally decided to make a complete hard/factory reset the result was none (after i rebooted to recovery again ALL THE DATA WAS THERE WITHOUT ANY DIFFERENCE, like nothing happened)
- Second thing i tried flashing with Odin3 in Download mode - result was unsuccessful (Operation failed at ~45% and the phone freezed) - I tried this several times with different versions of the software and firmware on 2 different computers (same result)
- Third thing i tried to push img with ADB - no result
- Fourth thing i tried the NexusToolKit and using the UNROOT/GOBACK TO STOCK/SOFTBRICK option - operation was SUCCESSFUL (that's what the cmd console said) BUT, after around 15 mins booting on GOOGLE it started booting my old custom ROM that i had (CarbonROM) with its custom boot animation and i was WTF?! - after several minutes it finally booted the rom. As i tried to unlocked it the touchscreen and processing was very slow and unresponsive, it took around 10-15sec. to unlock the phone and then opening the home menu, and in a short delay the phone restarted itself.
- I tried deleting system,data,userdata,cache and etc with the toolkit but same resault - when i rebooted the information was still there.
- I readed alot on the forums and i found that it maybe caused my my eMMC but long ago i checked with a google store app that my chip is from the safe ones and cant go brickbug.
Some information about the phone:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version - I9250XXLJ1
carrier info - none
serial number - 0149C7ED0D020018
signing - production
lock state- unlocked
if anything needed pls ask
valkata1212 said:
Hello guys, Im a experienced user with ROMs, recovery, boot and etc but i have a problem now, and i will try to explain shortly:
AT THE MOMENT:
- I get into fastboot mode
- I get into odin downloading mode
- I have a connection with pc(win8.1)
- The computer can communicate with the phone in fastboot mode and adb(recovery)
- the drivers are installed correctly
- BOOTLOOPIN ON GOOGLE
How this happened:
I was minding my own business and my phone was on my desk when it suddenly rebooted itself and then it bootlooped forever. I had some situations when it rebooted itself but always ended in a successful boot, this time it didnt wanted to start.
What have i done till now:
- First thing i entered recovery(TWRP) and dirtyflashed my current rom version and wiped dalvik/cache. (unsuccessful)
- after several times doing the dirtyflash i finally decided to make a complete hard/factory reset the result was none (after i rebooted to recovery again ALL THE DATA WAS THERE WITHOUT ANY DIFFERENCE, like nothing happened)
- Second thing i tried flashing with Odin3 in Download mode - result was unsuccessful (Operation failed at ~45% and the phone freezed) - I tried this several times with different versions of the software and firmware on 2 different computers (same result)
- Third thing i tried to push img with ADB - no result
- Fourth thing i tried the NexusToolKit and using the UNROOT/GOBACK TO STOCK/SOFTBRICK option - operation was SUCCESSFUL (that's what the cmd console said) BUT, after around 15 mins booting on GOOGLE it started booting my old custom ROM that i had (CarbonROM) with its custom boot animation and i was WTF?! - after several minutes it finally booted the rom. As i tried to unlocked it the touchscreen and processing was very slow and unresponsive, it took around 10-15sec. to unlock the phone and then opening the home menu, and in a short delay the phone restarted itself.
- I tried deleting system,data,userdata,cache and etc with the toolkit but same resault - when i rebooted the information was still there.
- I readed alot on the forums and i found that it maybe caused my my eMMC but long ago i checked with a google store app that my chip is from the safe ones and cant go brickbug.
Some information about the phone:
Product Name - tuna
Variant - maguro 16gb
HW version - 9
Bootloader Version - primemd04
baseband version - I9250XXLJ1
carrier info - none
serial number - 0149C7ED0D020018
signing - production
lock state- unlocked
if anything needed pls ask
Click to expand...
Click to collapse
first question is, what do you mean by download mode and odin? are you not using the google galaxy nexus? for all i know, that device has fastboot but not download mode, which is a proprietary fork of fastboot (i think). am i wrong? how do you boot into download mode?
your emmc might be locked in read-only mode. when the emmc firmware data structures get corrupted beyond the firmware capacity to fix them, the firmware downgrades to read-only mode, in which you can at least recover the stored information (or part of it).
grab a different custom recovery version than the one in your phone and "fastboot flash" it. then get into the recovery. do you get the newly flashed recovery or the old one that was already on your phone?
Lanchon said:
first question is, what do you mean by download mode and odin? are you not using the google galaxy nexus? for all i know, that device has fastboot but not download mode, which is a proprietary fork of fastboot (i think). am i wrong? how do you boot into download mode?
your emmc might be locked in read-only mode. when the emmc firmware data structures get corrupted beyond the firmware capacity to fix them, the firmware downgrades to read-only mode, in which you can at least recover the stored information (or part of it).
grab a different custom recovery version than the one in your phone and "fastboot flash" it. then get into the recovery. do you get the newly flashed recovery or the old one that was already on your phone?
Click to expand...
Click to collapse
Im using the Samsung galaxy nexus and under "download mode odin" i mean VOLUME DOWN + power button. Phone got both odin and fastboot. Fastboot works in bootloader mode ( volume up + volume down + power button).
I already tried with another custom recovery different from the one currently using, yes it flashes the new one - i tried with philz and cw recovery, both booted but again i couldnt wipe everything.
Lanchon said:
first question is, what do you mean by download mode and odin? are you not using the google galaxy nexus? for all i know, that device has fastboot but not download mode, which is a proprietary fork of fastboot (i think). am i wrong? how do you boot into download mode?
your emmc might be locked in read-only mode. when the emmc firmware data structures get corrupted beyond the firmware capacity to fix them, the firmware downgrades to read-only mode, in which you can at least recover the stored information (or part of it).
grab a different custom recovery version than the one in your phone and "fastboot flash" it. then get into the recovery. do you get the newly flashed recovery or the old one that was already on your phone?
Click to expand...
Click to collapse
the galaxy nexus certainly has download mode/Odin.
it is a Samsung device, they all have this.
just like even the HTC nexus device have hboot
to the op, I wish you much luck, I cannot comment much on this, I had similar happen once and I used "fastboot boot recovery.img" and luckily was able to fix my device from there, but I see this happen sometimes to others (few threads on here about it) where they weren't able to get her back up and running I hope that is not the case for you.
---------- Post added at 12:13 AM ---------- Previous post was at 12:08 AM ----------
oh, also, do you have multiple batteries? have you tried another battery? seems simple enough, but I've heard of devices acting awry similar to this when the battery has taken a crap. (sometime the battery will act as if it's charging and holding charge just fine, but it never actually gets itself to fully charged, for example I think fully charged battery should read about 4.12 with a voltmeter, but one that's gone faulty doesn't reach that, is as if it just cannot provide enough juice needed to get things done causing the device to fail while trying to use that battery)
ashclepdia said:
the galaxy nexus certainly has download mode/Odin.
it is a Samsung device, they all have this.
just like even the HTC nexus device have hboot
to the op, I wish you much luck, I cannot comment much on this, I had similar happen once and I used "fastboot boot recovery.img" and luckily was able to fix my device from there, but I see this happen sometimes to others (few threads on here about it) where they weren't able to get her back up and running I hope that is not the case for you.
---------- Post added at 12:13 AM ---------- Previous post was at 12:08 AM ----------
oh, also, do you have multiple batteries? have you tried another battery? seems simple enough, but I've heard of devices acting awry similar to this when the battery has taken a crap. (sometime the battery will act as if it's charging and holding charge just fine, but it never actually gets itself to fully charged, for example I think fully charged battery should read about 4.12 with a voltmeter, but one that's gone faulty doesn't reach that, is as if it just cannot provide enough juice needed to get things done causing the device to fail while trying to use that battery)
Click to expand...
Click to collapse
I have one and only stock battery. TWRP has a battery counter and it seems ok it stays always on 100% when plugged in the usb. I will try to check it with a voltmeter but i doubt that the problem is from the battery.
Waiting Lanchon to asnwer
valkata1212 said:
Im using the Samsung galaxy nexus and under "download mode odin" i mean VOLUME DOWN + power button. Phone got both odin and fastboot. Fastboot works in bootloader mode ( volume up + volume down + power button).
I already tried with another custom recovery different from the one currently using, yes it flashes the new one - i tried with philz and cw recovery, both booted but again i couldnt wipe everything.
Click to expand...
Click to collapse
ok! i had 2 galaxy nexus and never realized they had download mode lol, or at least i dont remember knowing!
so to confirm: you flash any recovery and it sticks and works. you flash it using "fastboot flash recovery x.img". you ARE NOT booting it directly with "fastboot boot x.img". confirm?
this means that your emmc is not fully locked down, and is good news.
Lanchon said:
ok! i had 2 galaxy nexus and never realized they had download mode lol, or at least i dont remember knowing!
so to confirm: you flash any recovery and it sticks and works. you flash it using "fastboot flash recovery x.img". you ARE NOT booting it directly with "fastboot boot x.img". confirm?
this means that your emmc is not fully locked down, and is good news.
Click to expand...
Click to collapse
BAD NEWS: NOPE, i do not confirm, i only did fastboot boot x.img!! Now i tried fastboot flash recovery x.img, restarted bootloader, and entered to recovery and - bang - old recovery is there. It's seems that my phone is a goner right??
valkata1212 said:
BAD NEWS: NOPE, i do not confirm, i only did fastboot boot x.img!! Now i tried fastboot flash recovery x.img, restarted bootloader, and entered to recovery and - bang - old recovery is there. It's seems that my phone is a goner right??
Click to expand...
Click to collapse
ok your emmc is locked in read-only mode. i had a gnex brought to me in that condition and there was absolutely nothing i could do to fix it. writes are ignored by the emmc (but return "ok" to the kernel) and take near zero time. i tried issuing emmc erase commands, etc, and they were all ignored. i tried booting via USB (via an OMAP debugger) and i couldn't accomplish anything. there is a thread here in xda that details what i tried and what i found out. in the end, i had to replace the motherboard of that phone.
but... i know more now
there is one thing you could try: completely reset the emmc. but really, given that you didnt follow a simple fastboot flash instruction and did a fastboot boot instead makes me think that you wont be able to correctly follow the procedure to completion, but we can try.
the trick is to resize the boot partitions, and during that operation the complete emmc will be wiped. this includes the corrupted FTL data structures inside the emmc that i suspect are causing the read-only lock.
so, caveats:
-this has never ever been tried on this device or this emmc. but it was done successfully in some kindles of the same era, which have a different but similar emmc (both are samsung emmcs). take a look here but DO NOT follow that procedure:
http://forum.xda-developers.com/showthread.php?t=2413453
-everything gets wiped! including bootloaders, partition table, partitions, etc.
-the kindle can boot from usb, but the gnex cant. if the gnex is shut down or rebooted after wiping the emmc but before reconstituting the boot chain, THE DEVICE WILL BE BRICKED FOREVER and never boot again.
-if something goes wrong, BRICK.
-the procedure we will improvise and try can be plain wrong, and the device might BRICK.
-the emmc might ignore the boot partition resize command, in which case it wont brick any further, but this whole adventure would be a failure.
-actually i lied. if the device is rebooted without a proper boot chain, there is a boot-over-USB OMAP debugger that can boot it into a monitor. but reconstituting the boot chain from there might be impossible.
read everything twice and make sure you understand everything i write. ASK instead of guessing!
FROM NOW ON: everything you do, you will do it in latest release of TWRP for your device. before doing ANYTHING here, each time you boot your phone you will enter fastboot mode and "fastboot boot" this TWRP image. then you will "adb shell" to it, or "adb push/pull" to/from it.
first i need a map of your emmc. adb shell then run this and paste the output:
ls -l /dev/block/mmc*
ls -l /dev/block/platform/[whatever device name]/by-name
fdisk -l /dev/block/mmcblk0
---------- Post added at 03:25 PM ---------- Previous post was at 03:19 PM ----------
please post outputs in [ CODE ] tags so that its more readable.
Lanchon said:
ok your emmc is locked in read-only mode. i had a gnex brought to me in that condition and there was absolutely nothing i could do to fix it. writes are ignored by the emmc (but return "ok" to the kernel) and take near zero time. i tried issuing emmc erase commands, etc, and they were all ignored. i tried booting via USB (via an OMAP debugger) and i couldn't accomplish anything. there is a thread here in xda that details what i tried and what i found out. in the end, i had to replace the motherboard of that phone.
but... i know more now
there is one thing you could try: completely reset the emmc. but really, given that you didnt follow a simple fastboot flash instruction and did a fastboot boot instead makes me think that you wont be able to correctly follow the procedure to completion, but we can try.
the trick is to resize the boot partitions, and during that operation the complete emmc will be wiped. this includes the corrupted FTL data structures inside the emmc that i suspect are causing the read-only lock.
so, caveats:
-this has never ever been tried on this device or this emmc. but it was done successfully in some kindles of the same era, which have a different but similar emmc (both are samsung emmcs). take a look here but DO NOT follow that procedure:
http://forum.xda-developers.com/showthread.php?t=2413453
-everything gets wiped! including bootloaders, partition table, partitions, etc.
-the kindle can boot from usb, but the gnex cant. if the gnex is shut down or rebooted after wiping the emmc but before reconstituting the boot chain, THE DEVICE WILL BE BRICKED FOREVER and never boot again.
-if something goes wrong, BRICK.
-the procedure we will improvise and try can be plain wrong, and the device might BRICK.
-the emmc might ignore the boot partition resize command, in which case it wont brick any further, but this whole adventure would be a failure.
-actually i lied. if the device is rebooted without a proper boot chain, there is a boot-over-USB OMAP debugger that can boot it into a monitor. but reconstituting the boot chain from there might be impossible.
read everything twice and make sure you understand everything i write. ASK instead of guessing!
FROM NOW ON: everything you do, you will do it in latest release of TWRP for your device. before doing ANYTHING here, each time you boot your phone you will enter fastboot mode and "fastboot boot" this TWRP image. then you will "adb shell" to it, or "adb push/pull" to/from it.
first i need a map of your emmc. adb shell then run this and paste the output:
ls -l /dev/block/mmc*
ls -l /dev/block/platform/[whatever device name]/by-name
fdisk -l /dev/block/mmcblk0
---------- Post added at 03:25 PM ---------- Previous post was at 03:19 PM ----------
please post outputs in [ CODE ] tags so that its more readable.
Click to expand...
Click to collapse
Im doing the adb shell commands now but I have 1 question: How to find my DEVICE NAME?? im not sure what to type from all the data i get, i will wait until you respond to proceed.
EDIT: This is what i get for now:
Code:
~ # ←[6nls -l /dev/block/mmc*
ls -l /dev/block/mmc*
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
brw------- root root 179, 0 2015-02-05 15:26 mmcblk0
brw------- root root 179, 8 2015-02-05 15:26 mmcblk0boot0
brw------- root root 179, 16 2015-02-05 15:26 mmcblk0boot1
brw------- root root 179, 1 2015-02-05 15:26 mmcblk0p1
brw------- root root 259, 2 2015-02-05 15:26 mmcblk0p10
brw------- root root 259, 3 2015-02-05 15:26 mmcblk0p11
brw------- root root 259, 4 2015-02-05 15:26 mmcblk0p12
brw------- root root 259, 5 2015-02-05 15:26 mmcblk0p13
brw------- root root 179, 2 2015-02-05 15:26 mmcblk0p2
brw------- root root 179, 3 2015-02-05 15:26 mmcblk0p3
brw-rw---- radio radio 179, 4 2015-02-05 15:26 mmcblk0p4
brw------- root root 179, 5 2015-02-05 15:26 mmcblk0p5
brw------- root root 179, 6 2015-02-05 15:26 mmcblk0p6
brw------- root root 179, 7 2015-02-05 15:26 mmcblk0p7
brw------- root root 259, 0 2015-02-05 15:26 mmcblk0p8
brw-rw---- radio radio 259, 1 2015-02-05 15:26 mmcblk0p9
~ # ←[6n
Code:
~ # ←[6nls -l /dev/block/platform/
ls -l /dev/block/platform/
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2015-02-05 15:26 omap
~ # ←[6n
Code:
~ # ←[6nls -l /dev/block/platform/omap
ls -l /dev/block/platform/omap
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
drwxr-xr-x root root 2015-02-05 15:26 omap2_mcspi.3
drwxr-xr-x root root 2015-02-05 15:26 omap_hsmmc.0
~ # ←[6n
Code:
~ # ←[6nfdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
~ # ←[6n
Tell me if you need something
valkata1212 said:
How to find my DEVICE NAME??
Click to expand...
Click to collapse
you should try all options!
but i think it is probably omap/omap_hsmmc.0
are you sure you are "fastboot boot" booting into the latest TWRP recovery before doing adb shell??? your fdisk command doesn't support GPT disks, that is very strange.
also do:
cat /proc/partitions
cat /proc/mounts
also from the pc (are you using linux or windows?):
create a PC folder and cd into it, then:
adb pull -p /dev/block/mmcblk0boot0
adb pull -p /dev/block/mmcblk0boot1
tell me the exact size of the two downloaded files. KEEP THESE FILES SAFE!
Lanchon said:
you should try all options!
but i think it is probably omap/omap_hsmmc.0
are you sure you are "fastboot boot" booting into the latest TWRP recovery before doing adb shell??? your fdisk command doesn't support GPT disks, that is very strange.
also do:
cat /proc/partitions
cat /proc/mounts
also from the pc (are you using linux or windows?):
create a PC folder and cd into it, then:
adb pull -p /dev/block/mmcblk0boot0
adb pull -p /dev/block/mmcblk0boot1
tell me the exact size of the two downloaded files. KEEP THESE FILES SAFE!
Click to expand...
Click to collapse
I can 100% confirm Im on the newest TWRP recovery version v2.8.4.0 flashed with fastboot boot x.img
And here are the results i got, and also those new commands:
Code:
~ # ←[6nls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
lrwxrwxrwx root root 2015-02-05 18:06 boot -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2015-02-05 18:06 cache -> /dev/block/mmcblk0p11
lrwxrwxrwx root root 2015-02-05 18:06 dgs -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2015-02-05 18:06 efs -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2015-02-05 18:06 metadata -> /dev/block/mmcblk0p13
lrwxrwxrwx root root 2015-02-05 18:06 misc -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2015-02-05 18:06 param -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2015-02-05 18:06 radio -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2015-02-05 18:06 recovery -> /dev/block/mmcblk0p8
lrwxrwxrwx root root 2015-02-05 18:06 sbl -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2015-02-05 18:06 system -> /dev/block/mmcblk0p10
lrwxrwxrwx root root 2015-02-05 18:06 userdata -> /dev/block/mmcblk0p12
lrwxrwxrwx root root 2015-02-05 18:06 xloader -> /dev/block/mmcblk0p1
~ # ←[6n
Code:
~ # ←[6ncat /proc/partitions
cat /proc/partitions
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1
179 2 3584 mmcblk0p2
179 3 20480 mmcblk0p3
179 4 8192 mmcblk0p4
179 5 4096 mmcblk0p5
179 6 4096 mmcblk0p6
179 7 8192 mmcblk0p7
259 0 12224 mmcblk0p8
259 1 16384 mmcblk0p9
259 2 669696 mmcblk0p10
259 3 442368 mmcblk0p11
259 4 14198767 mmcblk0p12
259 5 64 mmcblk0p13
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
~ # ←[6n
Code:
~ # ←[6ncat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
tmpfs /tmp tmpfs rw,seclabel,relatime 0 0
/dev/block/mmcblk0p11 /cache ext4 rw,seclabel,relatime,user_xattr,barrier=1,data
=ordered 0 0
/dev/block/mmcblk0p12 /data ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=
ordered 0 0
/dev/block/mmcblk0p12 /sdcard ext4 rw,seclabel,relatime,user_xattr,barrier=1,dat
a=ordered 0 0
~ # ←[6n
AND THIS IS WHAT I GET WHEN I TRIED TO PULL THE FILES U ASKED: (both mmcblk0boot0/1)
Code:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb pull -p /dev/block/mmcbl
k0boot0
remote object '/dev/block/mmcblk0boot0' not a file or directory
lol please repeat:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
using a wider terminal so that the output can be read
your partitions are:
Code:
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1 xloader
179 2 3584 mmcblk0p2 sbl
179 3 20480 mmcblk0p3 efs
179 4 8192 mmcblk0p4 param
179 5 4096 mmcblk0p5 misc
179 6 4096 mmcblk0p6 dgs
179 7 8192 mmcblk0p7 boot
259 0 12224 mmcblk0p8 recovery
259 1 16384 mmcblk0p9 radio
259 2 669696 mmcblk0p10 system
259 3 442368 mmcblk0p11 cache
259 4 14198767 mmcblk0p12 userdata
259 5 64 mmcblk0p13 metadata
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
---------- Post added at 03:34 PM ---------- Previous post was at 03:28 PM ----------
cat /proc/mtd
cat /proc/emmc
dd if=/dev/block/mmcblk0boot0 of=/tmp/mmcblk0boot0
dd if=/dev/block/mmcblk0boot1 of=/tmp/mmcblk0boot1
from the PC:
adb pull /tmp/mmcblk0boot0
adb pull /tmp/mmcblk0boot1
---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------
get the latest philz touch recovery for gnex. fastboot boot into it, then try this again:
fdisk -l /dev/block/mmcblk0
Lanchon said:
lol please repeat:
ls -l /dev/block/platform/omap/omap_hsmmc.0/by-name
using a wider terminal so that the output can be read
your partitions are:
Code:
major minor #blocks name
31 0 1024 mtdblock0
179 0 15388672 mmcblk0
179 1 128 mmcblk0p1 xloader
179 2 3584 mmcblk0p2 sbl
179 3 20480 mmcblk0p3 efs
179 4 8192 mmcblk0p4 param
179 5 4096 mmcblk0p5 misc
179 6 4096 mmcblk0p6 dgs
179 7 8192 mmcblk0p7 boot
259 0 12224 mmcblk0p8 recovery
259 1 16384 mmcblk0p9 radio
259 2 669696 mmcblk0p10 system
259 3 442368 mmcblk0p11 cache
259 4 14198767 mmcblk0p12 userdata
259 5 64 mmcblk0p13 metadata
179 16 2048 mmcblk0boot1
179 8 2048 mmcblk0boot0
---------- Post added at 03:34 PM ---------- Previous post was at 03:28 PM ----------
cat /proc/mtd
cat /proc/emmc
dd if=/dev/block/mmcblk0boot0 of=/tmp/mmcblk0boot0
dd if=/dev/block/mmcblk0boot1 of=/tmp/mmcblk0boot1
from the PC:
adb pull /tmp/mmcblk0boot0
adb pull /tmp/mmcblk0boot1
---------- Post added at 03:36 PM ---------- Previous post was at 03:34 PM ----------
get the latest philz touch recovery for gnex. fastboot boot into it, then try this again:
fdisk -l /dev/block/mmcblk0
Click to expand...
Click to collapse
Code:
~ # ←[6ncat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00100000 00001000 "w25q80"
~ # ←[6n
hmm :?
Code:
~ # ←[6ncat /proc/emmc
cat /proc/emmc
cat: can't open '/proc/emmc': No such file or directory
~ # ←[6n
I downloaded and fastboot booted latest phillz and i did the command again, but the resault is the same:
Code:
~ # fdisk -l /dev/block/mmcblk0
fdisk -l /dev/block/mmcblk0
Disk /dev/block/mmcblk0: 15.7 GB, 15758000128 bytes
1 heads, 16 sectors/track, 1923584 cylinders
Units = cylinders of 16 * 512 = 8192 bytes
Device Boot Start End Blocks Id System
/dev/block/mmcblk0p1 1 1923584 15388671+ ee EFI GPT
Partition 1 does not end on cylinder boundary
~ #
So i pulled both mmcblk files, they are 2,048 KB each.
this is going to be redundant, buy do it just in case:
adb pull -p /dev/block/mmcblk0p##
where ## is 1 to 9 and 13 (skip 10, 11, 12)
Lanchon said:
this is going to be redundant, buy do it just in case:
adb pull -p /dev/block/mmcblk0p##
where ## is 1 to 9 and 13 (skip 10, 11, 12)
Click to expand...
Click to collapse
Done. had to do the trick with dd if=/dev/block/mmcblk0p of=/tmp/mmcblk0p first then adb pull /tmp/mmcblk0p, but i got the files now, their size range are from 64 KB to 20,480 KB (largest one)
Whats next:?
EDIT: first reboot into clean latest TWRP
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-beg bs=1M count=96
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
from the PC:
adb pull -p /tmp/mmcblk0-beg
adb pull -p /tmp/mmcblk0-end
beg should be 96MB
end should be 28MB
verify, that on the PC.
DO NOT REBOOT THE PHONE FROM THIS POINT FORWARD!
we want those files in the ramdrive
Lanchon said:
EDIT: first reboot into clean latest TWRP
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-beg bs=1M count=96
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
from the PC:
adb pull -p /tmp/mmcblk0-beg
adb pull -p /tmp/mmcblk0-end
beg should be 96MB
end should be 28MB
verify, that on the PC.
DO NOT REBOOT THE PHONE FROM THIS POINT FORWARD!
we want those files in the ramdrive
Click to expand...
Click to collapse
downloaded beg and i confirm its 98 MB but i have a problem with END, it doesnt want to copy it im tmp, i deleted the "skip=15000 part" and it came out 250 MB!! but couldnt pull it cuz it game me "no space left on device"
What should i do? Reboot and do this again or ?
valkata1212 said:
downloaded beg and i confirm its 98 MB but i have a problem with END, it doesnt want to copy it im tmp, i deleted the "skip=15000 part" and it came out 250 MB!! but couldnt pull it cuz it game me "no space left on device"
What should i do? Reboot and do this again or ?
Click to expand...
Click to collapse
reboot
redo first dd
no need to pull again
redo second dd, and tell me the error message or whatever it outputs. form now on, i recommend you dont try to fix things without posting first, one error can mean BRICK.
Lanchon said:
reboot
redo first dd
no need to pull again
redo second dd, and tell me the error message or whatever it outputs. form now on, i recommend you dont try to fix things without posting first, one error can mean BRICK.
Click to expand...
Click to collapse
Code:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb shell
~ # ←[6ndd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
It doesnt start the operation dont know why, just like the first time i did. Beg finished for 2-3 sec but -end just doesnt show up.
valkata1212 said:
Code:
E:\WugFresh Development\Nexus Root Toolkit\data\MMC>adb shell
~ # ←[6ndd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
dd if=/dev/block/mmcblk0 of=/tmp/mmcblk0-end bs=1M skip=15000
It doesnt start the operation dont know why, just like the first time i did. Beg finished for 2-3 sec but -end just doesnt show up.
Click to expand...
Click to collapse
you are saying:
-no error displayed
-no file created
?
does the phone stop responding?