Develop Bugs

[GUIDE] Recovery Install w/out USB

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:

[Q] 80G9 image with HDD support

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.

[help] Gnex brick/softbrick/emmc problem

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?

[GUIDE][GT-I9192][stuck at splash] how to get your data back

This is how I got my data from my GT-I9192 with TWRP and CM13. I don't know if it works for the other GT-I91XX models or with other firmware, but if you are in a similar situation like me it is worth a try.
Background:
I installed Cyanogenmod 13 and TWRP successfully about two month ago.
About a week ago my phone suddenly was black and did not want to boot at all. I convinced it to restart after pulling battery/recharge cable some times and putting them back, sometimes whilest holding power button pressed at the same time, until it gave a life sign again.
Current situation:
My phone stucks at samsung logo splash screen and reboots.
When trying to boot into recovery (TWRP; VOL.UP+HOME(+POWER)) the TeamWinRecovery logo screen is shown but then reboots.
Download mode (VOL.DOWN+HOME) works, Odin recognizes phone, but flashing TWRP successfully again does not fix anything.
Fastboot and adb do not recognize phone while it is in boot loop/recovery start loop/download mode!
But the interesting part is:
I am able to get via adb shell onto the phone while it is offline! Pull battery, put it back again, connect the phone via USB to PC and leave it off. Battery charging screen shows up and about a minute later adb shell is possible. It is in a strange state then, neither sdcard nor any else partition besides system is mounted, but mounting sdcard and data partition manually is possible.
Required:
Installed Samsung drivers, downloaded ADB tools, CM13(?), root enabled for adb.
make sure phone is off (pull battery/cable, put it back again)
connect phone via usb to pc
at pc cmd type
Code:
adb wait-for-device
when prompt is back, type
Code:
adb shell
use the commands below to get to your data
list internal partitions by name:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
output:
Code:
total 0
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 aboot -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 backup -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 boot -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 cache -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 efs -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 fota -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 fsg -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 hidden -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 modem -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 modemst1 -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 modemst2 -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 pad -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 param -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 persdata -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 persist -> /dev/block/mmcblk0p19
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 recovery -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 rpm -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl1 -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl2 -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 sbl3 -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 ssd -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 system -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 20 1970-01-01 00:00 tz -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 1970-01-01 00:00 userdata -> /dev/block/mmcblk0p24 [COLOR="red"]<<< there is your userdata[/COLOR]
list all partitions with size:
Code:
cat /proc/partitions
output:
Code:
major minor #blocks name
179 0 7634944 mmcblk0
179 1 61440 mmcblk0p1
179 2 128 mmcblk0p2
179 3 256 mmcblk0p3
179 4 512 mmcblk0p4
179 5 2048 mmcblk0p5
179 6 512 mmcblk0p6
179 7 512 mmcblk0p7
179 8 12800 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 13952 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 3072 mmcblk0p12
179 13 10240 mmcblk0p13
179 14 10240 mmcblk0p14
179 15 10240 mmcblk0p15
179 16 7160 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 8 mmcblk0p18
179 19 8192 mmcblk0p19
179 20 12288 mmcblk0p20
179 21 1536000 mmcblk0p21
179 22 204800 mmcblk0p22
179 23 36864 mmcblk0p23
179 24 5685231 mmcblk0p24 [COLOR="red"]<<< userdata partition has about 5.7 GB size[/COLOR]
179 32 30703616 mmcblk1
179 33 30703582 mmcblk1p1 [COLOR="red"]<<< this is your external sdcard partition[/COLOR]
get partition format
Code:
blkid
output:
Code:
/dev/block/mmcblk0p1: SEC_TYPE="msdos" UUID="00BC-614E" TYPE="vfat"
/dev/block/mmcblk0p10: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p19: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p20: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p21: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p22: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p23: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4"
/dev/block/mmcblk0p24: UUID="57f8f4bc-abf4-655f-bf67-946fc0f9f25b" TYPE="ext4" [COLOR="Red"]<<< userdata has ext4 format[/COLOR]
/dev/block/mmcblk1p1: UUID="02A3-21FE" LABEL="Volume" TYPE="exfat" [COLOR="Red"]<<< external sdcard has exfat format[/COLOR]
get currently mounted partitions
Code:
mount
output:
Code:
rootfs on / type rootfs (rw,seclabel)
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)
/sys/kernel/debug on /sys/kernel/debug type debugfs (rw,seclabel,relatime)
none on /acct type cgroup (rw,relatime,cpuacct)
none on /sys/fs/cgroup type tmpfs (rw,seclabel,relatime,mode=750,gid=1000)
none on /sys/fs/cgroup/memory type cgroup (rw,relatime,memory)
tmpfs on /mnt type tmpfs (rw,seclabel,relatime,mode=755,gid=1000)
none on /dev/memcg type cgroup (rw,relatime,memory)
none on /dev/cpuctl type cgroup (rw,relatime,cpu)
none on /sys/fs/cgroup/bfqio type cgroup (rw,relatime,bfqio)
/dev/block/mmcblk0p21 on /system type ext4 (ro,seclabel,relatime,data=ordered)
neither data nor external sdcard is mounted
mount your external sdcard
Code:
mkdir /mnt/sdext
mount /dev/block/mmcblk1p1 /mnt/sdext
extract your data partition as image to your sdcard
Code:
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata.img
important info: as your data partition is larger than 4GB, you can only put the whole image to your sdcard if it is in exFat or NTFS format (fat32 does not allow files larger than 4GB). You could copy the image splitted like follows:
Code:
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata_1.img count=4000000
dd if=/dev/block/mmcblk0p24 of=/mnt/sdext/userdata_2.img skip=4000000
copy your images later to pc and put it together in windows cmd with
Code:
copy /B userdata_1.img + userdata_2.img userdata.img
Not tested though.
look if there is enough space on your external sdcard
Code:
df -H
H=human readable sizes with 1000 based system; use no option to list number of 1k blocks; use -P do list 512byte blocks, usefull as dd uses same block size per default
output:
Code:
Filesystem Size Used Avail Use% Mounted on
tmpfs 708M 41k 708M 1% /dev
none 708M 0 708M 0% /sys/fs/cgroup
tmpfs 708M 0 708M 0% /mnt
/dev/block/mmcblk0p21 1.5G 986M 562M 64% /system
/dev/block/mmcblk0p24 [COLOR="red"]5.7G[/COLOR] 5.3G 423M 93% /mnt/userdata
/dev/block/mmcblk1p1 31G 14G [COLOR="red"]18G[/COLOR] 44% /mnt/sdext
or mount your internal data partition as well and copy only the data you need
Code:
mkdir /mnt/userdata
mount /dev/block/mmcblk0p24 /mnt/userdata
use cd and ls -al commands to find your desired data;
in a secondary cmd at your pc copy directly to your pc via e.g. (contacts, sms, photos, TWRP backup, ...)
Code:
adb pull /mnt/userdata/data/com.android.providers.contacts/databases/contacts2.db
adb pull /mnt/userdata/data/com.android.providers.telephony/databases/mmssms.db
adb pull /mnt/userdata/media/0/DCIM
adb pull /mnt/userdata/media/0/TWRP
However, copying whole directories often failed and resulted in reboot of phone...
So, what to do with this image?
Mounting it in windows as new drive worked very well with OSFMount. As windows can not read ext4 partitions, you might want to install a ext4 driver like ext2fsd. And there is your data. Interesting folders are /media/0 where your internal sdcard data (like photos) resides and /data where all your apps store its data. You can find your contacts here /data/com.android.providers.contacts/databases/contacts2.db and your SMS here /data/com.android.providers.telephony/databases/mmssms.db. You can copy this databases to your new phone or inspect them via sqlite3.exe from your Android Development Tools. Here is a macro that could convert your contacts to vcard.
Credits:
Many of these information can be found at various xda threads, i do not remember all threads where I got which information from. Everything here was written from mind. Google and Wikipedia is also helpfull when it comes to command details. However this thread contains also most of the commands i showed above. This thread might give some inspirations about reading ext4 partition images under windows. If you feel that another thread has to be mentioned here, please write a message and I'll add it.

Thank you for this clarify guide. I try it even if my phone isn't bricked.
GT-I9190 cihazımdan Tapatalk kullanılarak gönderildi

Pixel 3 XL softbricked after Android 12 update. TWRP stuck at splashscreen. How to rescue data?

Hi,
today, I received an OTA update for my Pixel 3 XL (I had rooted and unlocked it before). The phone boots up, but right before the PIN/fingerprint screen appears, the UI flickers a few times and apparently crashes, causing the device to reboot infinitely. A similar problem is reported here:
Does anyone have a serious bug in the Lock Screen since android 12 was installed? Using Pixel 5 - Google Pixel Community
support.google.com
I guess the problem would be solved if I flashed with -w (a full factory reset), but I do not want to wipe before saving some important data such as WhatsApp backup. I have my WhatsApp backup at Google, but on Google Drive it shows me a gray triangle with an exclamation mark next to the entry for WhatsApp (see attachment) and according to some users on Reddit, restoring the backup did not work for some people who had that gray triangle. Can somebody confirm that the backup did work despite having that gray triangle? (In Google Drive, click the gear symbol on the right top and go to "Applications", then scroll down to WhatsApp).
I tried re-flashing the factory image of android 12 (without -w) without success.
I also tried flashing the factory image of android 11, but after that I only get an infinite google logo loading screen.
I also downloaded the most recent TWRP and flashed it (fastboot flash boot twrp.img), but it is always stuck at the splashscreen. In this state, however, I can at least enter the adb shell. I have root access to the system, but I cannot mount the data partition (probably it is encrypted somehow). "twrp mount" fails with the error message saying that TWRP is not running (which is probably true since it is stuck at the splashscreen).
Code:
1|crosshatch:/ # twrp mount
TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit.
Contents of /etc/fstab
Code:
/dev/block/dm-0 /system_root ext4 ro 0 0
/dev/block/dm-1 /vendor ext4 ro 0 0
/dev/block/dm-2 /product ext4 ro 0 0
/dev/block/sda20 /metadata ext4 rw 0 0
/dev/block/sda21 /data f2fs rw 0 0
/auto0 vfat rw 0 0
/dev/block/sdf2 /persist ext4 rw 0 0
ls /dev/block:
Code:
crosshatch:/ # ls /dev/block/by-name
ALIGN_TO_128K_1 aop_a boot_b cmnlib_b dip fsg keystore misc modemst2 product_b sdc splash storsec_b tz_b vendor_a xbl_config_b
ALIGN_TO_128K_2 aop_b cdt ddr dtbo_a hyp_a klog modem_a msadp_a qupfw_a sdd spunvm system_a uefivar vendor_b
ImageFv apdp_a cmnlib64_a devcfg_a dtbo_b hyp_b limits modem_b msadp_b qupfw_b sde ssd system_b userdata xbl_a
abl_a apdp_b cmnlib64_b devcfg_b frp keymaster_a logfs modemcal persist sda sdf sti toolsfv vbmeta_a xbl_b
abl_b boot_a cmnlib_a devinfo fsc keymaster_b metadata modemst1 product_a sdb sec storsec_a tz_a vbmeta_b xbl_config_a
I assume the "userdata" device (which symlinks to /dev/block/sda21) to contain my data, however I'm not sure about it.
The normal mount command does not work either:
Code:
crosshatch:/ # mount -o rw /dev/block/bootdevice/by-name/userdata /data
mount: /dev/block/bootdevice/by-name/userdata: need -t
1|crosshatch:/ # mount -t ext4 -o rw /dev/block/bootdevice/by-name/userdata /data
mount: '/dev/block/bootdevice/by-name/userdata'->'/data': Invalid argument
1|crosshatch:/ # mount -t f2fs -o rw /dev/block/bootdevice/by-name/userdata /data
mount: '/dev/block/bootdevice/by-name/userdata'->'/data': Invalid argument
I executed:
Code:
adb pull /dev/block/bootdevice/by-name/userdata userdata.img
This succeeded and I got a ~50GB file. Can I mount or decrypt this somehow on my PC?
Thanks and have a nice day!