Database Develop

how to dump your zio

I wrote this up in another forum and it also got lost in the 1.6 thread. Thought I'd pull it out.
---------
Instructions on how to dump your image manually:
Note: Everything in green is a command to type.
Pre)You installed the Kyocera USB drivers that came with the phone.
Kyocera ZIO - Downloads
Direct: http://www.ziobykyocera.com/downloads/files/M6000_USB_Driver.zip
Also, on the phone: Menu->Settings->Applications->Development->USB Debugging [selected]
Steps:
Root your phone:
[APP] [ROOT] 1-click root for N1 (Latest ver: 1.6.2 beta 5) - xda-developers
Direct: xda-developers
Install Android SDK for windows:
Android SDK | Android Developers
Direct: http://dl.google.com/android/android-sdk_r07-windows.zip
Extract that somewhere convinient, for ex: c:\
You'll need dump_image to get the img, find it here:
My Brain Hurts: Porting Clockwork Recovery to New Devices
Direct: http://koush.tandtgaming.com/test/dump_image
Copy that to the root of your sdcard, we'll use it later.
Lets connet to your phone.
Plug it in to the usb, make sure it is not mounted for reading the sdcard. On the phone, in the notification window tap the 'usb connected' notice and select "don't mount".
Now in windows, click Start->Run and type cmd.
cd \android-sdk-windows\tools\
adb.exe devices
It should list your device if all has gone well.
adb.exe shell
It should have connected to the phone and you have a "$" prompt.
su root
Now look at the phone, the Super User program (was installed after 1-click-root) should have popped up and asked if you want to allow root access, allow it.
Now you are at a "#" prompt.
Installing dump_image:
dump_image should be on the root of your sdcard from step 3.
Copy it to your bin directory:
cat /sdcard/dump_image > /system/bin/dump_image
Give it executable permission:
chmod 6755 /system/bin/dump_image
What to dump:
cat /proc/mtd
You're going to want to copy the output of that to the forum.
There should be a number of lines begining with mtd#
and the last name column has the name we'll need in quotes.
The dump:
mkdir /sdcard/dumped
dump_image boot /sdcard/dumped/boot.img
That just pulled the boot image. We need to do that for all the other images now:
dump_image name_here /sdcard/dumped/name_here.img
There could be 6-8 of them. Total will take a couple hundred megs.
Final:
Now we have it all, so zip up the files in /sdcard/dumped and put it on megaupload.com or something like that and post a link and the output from "cat /proc/mtd"
And that's it
Simple, yeah?
Some of those partitions that were listed in /proc/mtd are probably not needed, but I'm not certain as to which ones those are. I'm guessing "cache" and "userdata" probably aren't needed.

There was some issues with using the dump_image on yaffs2 partitions. For those the yaffs2 utility is useful. Here's some more info that was in the 1.6 thread:
Get it here:
http://jiggawatt.org/badc0de/android/mkfs.yaffs2.arm.tar.gz
(I attached it as well since that's the only place I could find an actual working version)
There's also a utility to extract the yaffs2 image (source)
You can also google for "mkyaffs2image" which is for something I can't recall.
Kind of shows how to use it in the middle of this section:
http://jiggawatt.org/badc0de/android/index.html#dynamic
adb push mkfs.yaffs2 /data/misc/mkfs.yaffs2
adb shell
# cd /data/misc
# ./mkfs.yaffs2 /system /system.img
# exit
adb pull /system.img ./system.img
Click to expand...
Click to collapse
Other useful info:
Code:
#cat /proc/mtd
dev: size erasesize name
mtd0: 01080000 00020000 "fota_amss"
mtd1: 00400000 00020000 "boot"
mtd2: 06780000 00020000 "system"
mtd3: 011e0000 00020000 "flex"
mtd4: 00500000 00020000 "recovery"
mtd5: 0ba60000 00020000 "userdata"
mtd6: 00600000 00020000 "fota_boot"
mtd7: 06780000 00020000 "cache"
mtd8: 000c0000 00020000 "misc"
Code:
#mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
/dev/block/mtdblock2 /system yaffs2 rw,relatime 0 0
/dev/block/mtdblock5 /data yaffs2 rw,nosuid,nodev,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/mtdblock7 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock3 /data/FLEX yaffs2 rw,nosuid,nodev,relatime 0 0
/dev/block/vold/179:1 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:1 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
So
Code:
boot not yaffs2
system yaffs2
recovery ...most likely yaffs2
userdata yaffs2
cache yaffs2
misc ...no clue

I've also tossed a bug in clockworkmods ears -- maybe if enough people request, we can get a fully supported recovery through rom manager.

dump_image data /sdcard/data.img
can't find data partition
is this a yaffs2 partition?
edit: mkfs.yaffs2 allows me to dump the partition, dump_image will not.
Could you clarify, ftr, what filesystem each of the partitions are?

I added more info the the second post about the yaffs2 and partitions.

[SOLVED] Soft bricked my HTC One M7, ADB not working

Hi there,
So I was installing CM10.2 on my HTC One (GSM) m7ul this evening when suddenly everything went wrong.
- I copied the CM .zip and GAPPS .zip to the internal storage using windows (7) file explorer;
- I installed the CM boot.img via fastboot flash boot boot.img;
- I rebooted into recovery mode (twrp 2.6.3.0);
- wiped cache and dalvik cache;
- Tried to find the installation.zip;
No zip files found. Actually, twrp did not find any file and could not mount f.i. system, cache, sdcard, etc
I tried using another bootloader (clockwork touch 6.0.4.3), but has the same issues as twrp.
ADB is not working as my phone was not in developer mode when I started to install CM10.2. Rebooting my phone is not working also because I replaced the boot.img via fastboot. I cannot reach my backup via twrp (on phone and PC).
Do you have tips for me to get my phone to work properly again?

basv81 said:
So I was installing CM10.2 this evening when suddenly everything went wrong.
- I copied the CM .zip and GAPPS .zip to the internal storage using windows (7) file explorer;
- I installed the CM boot.img via fastboot flash boot boot.img;
- I rebooted into recovery mode (twrp 2.6.3.0);
- wiped cache and dalvik cache;
- Tried to find the installation.zip;
No zip files found. Actually, twrp did not find any file and could not mount f.i. system, cache, sdcard, etc
I tried using another bootloader (clockwork touch 6.0.4.3), but has the same issues as twrp.
ADB is not working as my phone was not in developer mode when I started to install CM10.2. Rebooting my phone is not working also because I replaced the boot.img via fastboot. I cannot reach my backup via twrp (on phone and PC).
Do you have tips for me to get my phone to work properly again?
Click to expand...
Click to collapse
Mate you made a bad move flashing the boot.img file before installing the .zip. Always install the zip first then flash the boot.img and after clear cache. And make sure the zip is at the root of your sdcard in twrp before proceeding to anything!
I tried using another bootloader (clockwork touch 6.0.4.3)
Click to expand...
Click to collapse
You mean ''I tried another RECOVERY''
Rebooting my phone is not working also because I replaced the boot.img via fastboot
Click to expand...
Click to collapse
try holding power + Vol down and reboot in bootloader
Nowt that you are in bootloader, select fastboot and connect usb cable, navigate to your adb/fastboot folder of your computer and start a cmd prompt from there.
you can flash twrp again as your recovery
Code:
fastboot flash recovery <name-of-recovery>.img
reboot into bootloader
Code:
fastboot reboot bootloader
then go in recovery (adb is supported inside twrp).
push your zip files to your phone
Code:
adb push <name_of_rom>.zip /sdcard/
adb push <name_of_gapps>.zip /sdcard/
- install the zip of your cm rom first via twrp ---> select ''install'' and then navigate to /sdcard/ and select your zip.
- reboot phone in bootloader ---> select reboot from twrp main menu, after select bootloader.
- when in bootloader select fastboot
flash your kernel:
Code:
fastboot flash boot boot.img
after go back in twrp recovery and install you gapps.zip and after clear cache and dalvik cache then reboot normally.

Thanks for your reply.
alray said:
Mate you made a bad move flashing the boot.img file before installing the .zip. Always install the zip first then flash the boot.img and after clear cache. And make sure the zip is at the root of your sdcard in twrp before proceeding to anything!
You mean ''I tried another RECOVERY''
Click to expand...
Click to collapse
:good:
try holding power + Vol down and reboot in bootloader
Nowt that you are in bootloader, select fastboot and connect usb cable, navigate to your adb/fastboot folder of your computer and start a cmd prompt from there.
you can flash twrp again as your recovery
Code:
fastboot flash recovery <name-of-recovery>.img
reboot into bootloader
Code:
fastboot reboot bootloader
then go in recovery (adb is supported inside twrp).
Click to expand...
Click to collapse
Done all that. ADB sideload option tells me it cannot mount /sdcard, /data, /system.
push your zip files to your phone
Code:
adb push <name_of_rom>.zip /sdcard/
adb push <name_of_gapps>.zip /sdcard/
Click to expand...
Click to collapse
ADB cannot find the device.
- install the zip of your cm rom first via twrp ---> select ''install'' and then navigate to /sdcard/ and select your zip.
Click to expand...
Click to collapse
twrp and cwmod can't see any files (although I allready put the zip files in the root directory of the device)
- reboot phone in bootloader ---> select reboot from twrp main menu, after select bootloader.
- when in bootloader select fastboot
flash your kernel:
Code:
fastboot flash boot boot.img
after go back in twrp recovery and install you gapps.zip and after clear cache and dalvik cache then reboot normally.
Click to expand...
Click to collapse
I think the data on my device somehow got corrupt.

./

Stolpert said:
I assume you've got the correct drivers installed, you should be able to use ADB in recovery, at least in cwm but I guess also in twrp. Try and install HTC Sync manager for all the drivers, go back in recovery and type:
Code:
adb devices
If it's there you can follow the guide above.
Click to expand...
Click to collapse
Most recent drivers installed. I only don't get any serial numbers on my screen (only "List of devices attached" and below is empty). Not sure whether I get te "error: device not found" message with that command.

basv81 said:
Thanks for your reply.
:good:
Done all that. ADB sideload option tells me it cannot mount /sdcard, /data, /system.
ADB cannot find the device.
twrp and cwmod can't see any files (although I allready put the zip files in the root directory of the device)
I think the data on my device somehow got corrupt.
Click to expand...
Click to collapse
to check you're /data partition, reboot to recovery then:
adb devices -> to make sure it's connected, if OK proceed with below:
adb shell
~ # umount /data
umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
and see if it reports errors or not. (copy/paste your command prompt)

nkk71 said:
to check you're /data partition, reboot to recovery then:
adb devices -> to make sure it's connected, if OK proceed with below:
adb shell
~ # umount /data
umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
and see if it reports errors or not. (copy/paste your command prompt)
Click to expand...
Click to collapse
I'll do that tonight (that's within 12 hrs).

alray said:
you can flash twrp again as your recovery
Code:
fastboot flash recovery <name-of-recovery>.img
reboot into bootloader
Code:
fastboot reboot bootloader
then go in recovery (adb is supported inside twrp).
Click to expand...
Click to collapse
basv81 said:
Thanks for your reply.
Done all that. ADB sideload option tells me it cannot mount /sdcard, /data, /system.
Click to expand...
Click to collapse
ADB tells you that? You are using the fastboot commands? ADB cannot communicate with fastboot and shouldn't tell you anything.

basv81 said:
I'll do that tonight (that's within 12 hrs).
Click to expand...
Click to collapse
We're one hour apart, so hopefully I'll check in on you tonight

Stolper said:
ADB tells you that? You are using the fastboot commands? ADB cannot communicate with fastboot and shouldn't tell you anything.
Click to expand...
Click to collapse
fastboot commands work perfectly within fastboot, but adb does not as the ADB sideload options in twrp and cw fail.

Are you using a Sprint Htc one? (M7WLS) If yes you need a different version of twrp. Go back in fastboot and type "fasboot getvat all" and copy paste info here (remove imei and s/n)
Sent from my HTC One using xda app-developers app

alray said:
Are you using a Sprint Htc one? (M7WLS) If yes you need a different version of twrp. Go back in fastboot and type "fasboot getvat all" and copy paste info here (remove imei and s/n)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
No, I'm using a HTC One (GSM) m7ul
I'll post the info tonight.

I had the same crap happen on SPRINT HTC One. All I ended up doing in the end was booting to bootloader and derp- I mean, uh, running a stock RUU. Repartitioned all the partitions.
Sent from my HTC One using XDA Premium 4 mobile app

nkk71 said:
to check you're /data partition, reboot to recovery then:
adb devices -> to make sure it's connected, if OK proceed with below:
adb shell
~ # umount /data
umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
and see if it reports errors or not. (copy/paste your command prompt)
Click to expand...
Click to collapse
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT35CW***** recovery
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
~ # ←[6numount /data
umount /data
umount: can't umount /data: Invalid argument
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n

alray said:
Are you using a Sprint Htc one? (M7WLS) If yes you need a different version of twrp. Go back in fastboot and type "fasboot getvat all" and copy paste info here (remove imei and s/n)
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **********
(bootloader) imei: ***************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4318mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s

basv81 said:
nkk71 said:
Hi basv81,
If "e2fsck -n -v -f /dev/block/mmcblk0p37" returns an error, send me a PM so it get's my attention to check your thread, before proceeding. Another guy turned out to have this and we were able to fix it, coincidentally he was from the Netherlands too.
I'll probably be here till 10~11pm your time.
Click to expand...
Click to collapse
Hi nkk71,
I get the following results:
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT35xxxxxxxxxxxxx recovery
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
~ # ←[6numount /data
umount /data
umount: can't umount /data: Invalid argument
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
~ # ←[6n
I think I can be pretty sure the file system is corrupt :crying:
Click to expand...
Click to collapse
oh man, it's pretty late. can we pick this up anytime tomorrow or over the weekend? i need to get some sleep, and yeah looks like a corrupt partition. sorry man, i hate to be the bad guy
check into this: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
first thing you need to make sure of, is "cat /proc/emmc" to make sure we're looking at the right partition.
I can't do this tonight, but you might wanna check: http://forum.xda-developers.com/showthread.php?t=2504542
page 8 or 9 and onwards.
sorry man, but too late for me, i need to get some sleep before work tomorrow

nkk71 said:
oh man, it's pretty late. can we pick this up anytime tomorrow or over the weekend? i need to get some sleep, and yeah looks like a corrupt partition. sorry man, i hate to be the bad guy
check into this: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html
first thing you need to make sure of, is "cat /proc/emmc" to make sure we're looking at the right partition.
I can't do this tonight, but you might wanna check: http://forum.xda-developers.com/showthread.php?t=2504542
page 8 or 9 and onwards.
sorry man, but too late for me, i need to get some sleep before work tomorrow
Click to expand...
Click to collapse
No problem I have to go to sleep too because of the same.
cat /proc/emmc responds as follows:
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata" <<----------
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
I don't dare to format the partition yet (http://forum.xda-developers.com/showthread.php?t=2504542&page=9&p=47046727 and onwards). I'm online in the vicinity of my phone again tomorrow night after 8/9PM CET and Thursday night. After that it will be after the weekend.

basv81 said:
No problem I have to go to sleep too because of the same.
cat /proc/emmc responds as follows:
Code:
C:\Users\Bas\Desktop\HTC_One_files\HTCOneRoot\HTCOneRoot>adb shell
adb server is out of date. killing...
* daemon started successfully *
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata" <<----------
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
I don't dare to format the partition yet (http://forum.xda-developers.com/showthread.php?t=2504542&page=9&p=47046727 and onwards). I'm online in the vicinity of my phone again tomorrow night after 8/9PM CET and Thursday night. After that it will be after the weekend.
Click to expand...
Click to collapse
Anyway back to your thread, so /data isn't mounting, even if encrypted it should mount, but not be readable.
Here's what I'd like you to do, reboot to recovery, then:
adb shell
# e2fsck -v -f /dev/block/mmcblk0p37
and let's see if it ask for repair of any kind

alray said:
push your zip files to your phone
Code:
adb push <name_of_rom>.zip /sdcard/
adb push <name_of_gapps>.zip /sdcard/
- install the zip of your cm rom first via twrp ---> select ''install'' and then navigate to /sdcard/ and select your zip.
- reboot phone in bootloader ---> select reboot from twrp main menu, after select bootloader.
- when in bootloader select fastboot
flash your kernel:
Click to expand...
Click to collapse
This first part is working by the way: adb push worked when I used another USB port on my PC. I can see the two zip files I pushed, but cannot install them.

nkk71 said:
Anyway back to your thread, so /data isn't mounting, even if encrypted it should mount, but not be readable.
Here's what I'd like you to do, reboot to recovery, then:
adb shell
# e2fsck -v -f /dev/block/mmcblk0p37
and let's see if it ask for repair of any kind
Click to expand...
Click to collapse
Code:
~ # ←[6ne2fsck -v -f /dev/block/mmcblk0p37
e2fsck -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
I think I know what happened: I got my work e-mail on the phone, so the storage is encrypted. That's probably the reason that I don't see any files in there. Only problem is that I can't boot the phone to undo the encryption.

Htc one boots again and again, memory problem?

Hello, my problem is:
After an update from Htc my phone boot again and again.
Some times in recoverey it boot again.
sometimes data can not be mount, or cache can not be mount or unmount.
Installing an rom ends in bootloop.
The google rom starts up with google logo and colors. but also ends with a bootloop
Please help me

roluc said:
Hello, my problem is:
After an update from Htc my phone boot again and again.
Some times in recoverey it boot again.
sometimes data can not be mount, or cache can not be mount or unmount.
Installing an rom ends in bootloop.
The google rom starts up with google logo and colors. but also ends with a bootloop
Please help me
Click to expand...
Click to collapse
Hi, here's what I'd like you to do: reboot your phone into recovery and connect to PC, then
adb devices <- to confirm it's working
adb shell
~ # cat /proc/emmc
~ # mount
copy/paste the command prompt output and post here for us to take a look at, then we can proceed

nkk71 said:
Hi, here's what I'd like you to do: reboot your phone into recovery and connect to PC, then
adb devices <- to confirm it's working
adb shell
~ # cat /proc/emmc
~ # mount
copy/paste the command prompt output and post here for us to take a look at, then we can proceed
Click to expand...
Click to collapse
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mmcblk0p37 on /data type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p36 on /cache type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p35 on /system type ext4 (rw,relatime,data=ordered)
~ # ←[6n

roluc said:
mmcblk0p37: 680000000 00000200 "userdata"
~ # ←[6nmount
/dev/block/mmcblk0p37 on /data type ext4 (rw,relatime,data=ordered)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,relatime,data=ordered)
~ # ←[6n
Click to expand...
Click to collapse
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,relatime,data=ordered) <- hmm
ok now:
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
if e2fsck says it's still mounted, then
~ # umount /sdcard
and try again:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
was you filesystem encrypted by any chance?
copy/paste back

nkk71 said:
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,relatime,data=ordered) <- hmm
ok now:
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
if e2fsck says it's still mounted, then
~ # umount /sdcard
and try again:
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
was you filesystem encrypted by any chance?
copy/paste back
Click to expand...
Click to collapse
I do not know if filesystem was encrypted, How can this be done?
~ # ←[6numount /data
umount /data
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
~ # ←[6numount /sdcard
umount /sdcard
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
64 inodes used (0.00%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 55
261437 blocks used (3.84%)
0 bad blocks
1 large file
2 regular files
52 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
0 sockets
--------
55 files
~ # ←[6n

roluc said:
I do not know if filesystem was encrypted, How can this be done?
~ # ←[6numount /data
umount /data
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
~ # ←[6numount /sdcard
umount /sdcard
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
... 55 files
~ # ←[6n
Click to expand...
Click to collapse
filesystem doesn't seem to be corrupt at all, can you
~ # cd /data
~ # ls <- thats lowercase L not an i
~ # cd /data/media
~ # ls

nkk71 said:
filesystem doesn't seem to be corrupt at all, can you
~ # cd /data
~ # ls <- thats lowercase L not an i
~ # cd /data/media
~ # ls
Click to expand...
Click to collapse
i have already done some commands from your other post.
these are the results:
/data # ←[6ncd /data
cd /data
/data # ←[6nls
ls
/data # ←[6ncd data/media
cd data/media
/sbin/sh: cd: can't cd to data/media
/data # ←[6nls
ls
/data # ←[6n

roluc said:
i have already done some commands from your other post.
these are the results:
/data # ←[6ncd /data
cd /data
/data # ←[6nls
ls
/data # ←[6ncd data/media
cd data/media
/sbin/sh: cd: can't cd to data/media
/data # ←[6nls
ls
/data # ←[6n
Click to expand...
Click to collapse
/data # ←[6ncd /data/media
cd /data/media
/sbin/sh: cd: can't cd to /data/media
/data # ←[6n

roluc said:
i have already done some commands from your other post.
/data # ←[6ncd data/media
cd data/media
/sbin/sh: cd: can't cd to data/media
Click to expand...
Click to collapse
please note the command "cd /data/media" not "cd data/media". honestly please be careful with missing spaces, extra spaces, etc.
some of the commands (not yet but eventually) can be quite dangerous if mistyped, and if you end up formatting a wrong partition, you'll really have a brick on your hands.
So far it looks like the filesystem was encrypted, and not corrupt, and a simple wipe/format/factory rest, should do the job just fine, if it doesn't we can go for the "real" formatting, but let's not be too hasty about it.
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
roluc said:
/data # ←[6ncd /data/media
cd /data/media
/sbin/sh: cd: can't cd to /data/media
/data # ←[6n
Click to expand...
Click to collapse
OK, just saw that after I typed the post, try a wipe / factory reset / format (whatever it's called in TWRP) of /data , /sdcard , /data/media

nkk71 said:
please note the command "cd /data/media" not "cd data/media". honestly please be careful with missing spaces, extra spaces, etc.
some of the commands (not yet but eventually) can be quite dangerous if mistyped, and if you end up formatting a wrong partition, you'll really have a brick on your hands.
So far it looks like the filesystem was encrypted, and not corrupt, and a simple wipe/format/factory rest, should do the job just fine, if it doesn't we can go for the "real" formatting, but let's not be too hasty about it.
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
OK, just saw that after I typed the post, try a wipe / factory reset / format (whatever it's called in TWRP) of /data , /sdcard , /data/media
Click to expand...
Click to collapse
At wipe i get error unable to wipe /usb-otg
/data # ←[6ncd /data/media
cd /data/media
/data/media # ←[6nls
ls
/data/media # ←[6n
and this

roluc said:
At wipe i get error unable to wipe /usb-otg
/data # ←[6ncd /data/media
cd /data/media
/data/media # ←[6nls
ls
/data/media # ←[6n
and this
Click to expand...
Click to collapse
not "/usb-otg" that would refer to an external USB stick attached with an OTG cable. hold on while I install TWRP to see the options, I'll post back in a few minutes.....
PS: Hit the thanks button if I'm helping
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
roluc said:
At wipe i get error unable to wipe /usb-otg
Click to expand...
Click to collapse
EDIT: do you insist on TWRP, I have CWM installed:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
could you flash it instead of TWRP:
in bootloader/FASTBOOT USB:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
then enter RECOVERY, select "mounts and storage" -> "format /data and /data/media (/sdcard)"

nkk71 said:
not "/usb-otg" that would refer to an external USB stick attached with an OTG cable. hold on while I install TWRP to see the options, I'll post back in a few minutes.....
PS: Hit the thanks button if I'm helping
---------- Post added at 06:24 PM ---------- Previous post was at 06:18 PM ----------
EDIT: do you insist on TWRP, I have CWM installed:
recovery-clockwork-touch-6.0.3.2-m7--v2.img 7.2 MB
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
could you flash it instead of TWRP:
in bootloader/FASTBOOT USB:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
then enter RECOVERY, select "mounts and storage" -> "format /data and /data/media (/sdcard)"
Click to expand...
Click to collapse
I see now clockworkmod recovery v6.0.3.2
e:can't mount /cache/recovery/command
e:can't mount /cache/recovery/log
e:can't open cache/recovery/log
e:can't mount /cache/recovery/last_log
e:can't open /cache/recovery/last_log
formatting /data...
after formatting i get back done

roluc said:
I see now clockworkmod recovery v6.0.3.2
e:can't mount /cache/recovery/command
e:can't mount /cache/recovery/log
e:can't open cache/recovery/log
e:can't mount /cache/recovery/last_log
e:can't open /cache/recovery/last_log
formatting /data...
after formatting i get back done
Click to expand...
Click to collapse
cant mount cache is perfectly normal.
now push you rom to your phone:
adb push <name of rom>.zip /data/media/
this will take anywhere between 5 to 15 minutes, after which it should report success, then in recovery "install zip" -> "choose zip" -> select the ROM you just pushed.
if at any point it reboots, let me know, and we'll just "real" format your /data partition (eventhough it does not look corrupted)

nkk71 said:
cant mount cache is perfectly normal.
now push you rom to your phone:
adb push <name of rom>.zip /data/media/
this will take anywhere between 5 to 15 minutes, after which it should report success, then in recovery "install zip" -> "choose zip" -> select the ROM you just pushed.
if at any point it reboots, let me know, and we'll just "real" format your /data partition (eventhough it does not look corrupted)
Click to expand...
Click to collapse
Okay the rom is now ready, must i install it?

roluc said:
Okay the rom is now ready, must i install it?
Click to expand...
Click to collapse
yep go to: install zip -> choose zip, select it and go through the installer

nkk71 said:
yep go to: install zip -> choose zip, select it and go through the installer
Click to expand...
Click to collapse
I am now installing android revulution hd by mike1986
Now rebooting
Htc is booting
now google and the collors
seeem to freez i see 4 points,
now rebooting
white screen with htc logo
reboots again withe htc logo
now google a four couloprd box
rebooting
white htc again
rebooing google and the 4 colours again and freezing
rebooting
white htc logo again.
and again white htc logo again
white htc again.
now for about 40 seconds
and again
shall i stop it?

roluc said:
I am now installing android revulution hd by mike1986
Now rebooting
Htc is booting
now google and the collors
seeem to freez i see 4 points,
now rebooting
white screen with htc logo
reboots again withe htc logo
now google a four couloprd box
rebooting
white htc again
rebooing google and the 4 colours again and freezing
rebooting
white htc logo again.
and again white htc logo again
white htc again.
now for about 40 seconds
and again
shall i stop it?
Click to expand...
Click to collapse
Sorry but have to go for about 15 minutes
Will you still be here?
Thanks for now hope to see you in a few minutes

roluc said:
I am now installing android revulution hd by mike1986
Now rebooting
Htc is booting
now google and the collors
seeem to freez i see 4 points,
now rebooting
Click to expand...
Click to collapse
what's that? the "rebooing google and the 4 colours again and freezing"
can you take a picture and post it please. also go to bootloader/FASTBOOT USB and post a "fastboot getvar all" (remove IMEI and s/n before posting)
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
roluc said:
Sorry but have to go for about 15 minutes
Will you still be here?
Thanks for now hope to see you in a few minutes
Click to expand...
Click to collapse
No problem. I'll be here for a while, will let you know if I have to stop.
Hit the thanks button from time to time

nkk71 said:
what's that? the "rebooing google and the 4 colours again and freezing"
can you take a picture and post it please. also go to bootloader/FASTBOOT USB and post a "fastboot getvar all" (remove IMEI and s/n before posting)
---------- Post added at 07:03 PM ---------- Previous post was at 07:01 PM ----------
No problem. I'll be here for a while, will let you know if I have to stop.
Hit the thanks button from time to time
Click to expand...
Click to collapse
Here are the photo's

roluc said:
Here are the photo's
Click to expand...
Click to collapse
Ok this it
C:\mini-sdk>adb push romA.zip /data/media
2218 KB/s (452221989 bytes in 199.102s)
C:\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA369W*******
(bootloader) imei: 35786*********
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.052s
C:\mini-sdk>

[Q] Full-wipe --> no ROM on SD --> mac OS issues

Hello guys,
first of all: thanks for the great things you're creating around the android os and for the useful and worthy enhancements, i really appreciate that...not just saying so because I'm in trouble..what I actually really am!
Had my HTC One M7 (unlocked boot loader) flashed with AR HD 62....had some issues with rebooting and freezing, so i wanted to do a full wipe...unfortunately (because of simply not really knowing too much about the function of the shell and android os itself) I deleted obviously everything...I think also the whole SD card, as it seems
So as it says in the title, I'm running a Mac for my flashing...and now the phone is out of reach somehow
I managed - as far as the terminal window and i can tell - to flash recovery by use of fast boot...but from that moment on, I don't know how to continue...
I also think, that my adb does not completely work...can't access the bootloader by using adb commands....
adb devices is listing the phone, but when I want do wipe it with fastboot -w, it reads "waiting for device"...nothing changes!
Can anyone tell me how to get on? This is the worst case I've had so far and I've been using custom roms and flashing since the Desire HD onwards...
Thanks in advance!
greetings from austria
alex

If you use CWM, you can use adb while in recovery. Just type in "adb push NAMEOFFILE /sdcard/rom.zip". Then reboot into recovery again and flash it. I don't think this works in TWRP, but it might...I've never tried it.

aooga said:
If you use CWM, you can use adb while in recovery. Just type in "adb push NAMEOFFILE /sdcard/rom.zip". Then reboot into recovery again and flash it. I don't think this works in TWRP, but it might...I've never tried it.
Click to expand...
Click to collapse
Yes, I'm running TWRP...and I've tried to do so...but if i type in the command an press enter, the terminal window just gets kinda inactive....it neither freezes nor reacts to commands any more from this moment on...
I hope there's something like the CWM procedure for TWRP, too...
However..thanks for your input!
Greetings Alex
Appendix:
*** TAMPERED ***
*** UNLOCKED ***
S-ON
HBOOT-1.44.0000
RADIO-4A.13.3231.27
I've already tried this http://forum.xda-developers.com/showthread.php?t=2318497, but my devices keeps being listed as "host" instead of "sideload"
If I want to push the file, the same issues as I described above turn up in context with the terminal window
How likely is it, that it's just my Mac that keeps me from successfully installing the ROM?!...I'm quite curious about that...

dr.zikzak said:
Yes, I'm running TWRP...and I've tried to do so...but if i type in the command an press enter, the terminal window just gets kinda inactive....it neither freezes nor reacts to commands any more from this moment on...
I hope there's something like the CWM procedure for TWRP, too...
.....
How likely is it, that it's just my Mac that keeps me from successfully installing the ROM?!...I'm quite curious about that... [/B]
Click to expand...
Click to collapse
I have a mac and I just tried it with twrp and it worked fine. What do you get when you run "adb devices" while in recovery.
Also, worst case, just run an RUU and root again.

Okay...so there seems to be sth wrong with me or the mac!
If I'm in fastboot usb, I get "list of devices attached"....and nothing else
If I'm in recovery, I get the ID of the device and "recovery" as the status
Oh my...I'm the man :-/
Greetings Alex

So when it comes to flashing RUU....i don't really know which one matches my HTC...
I got a 1.28.771.6 installed, CID is H3G_106...so I couldn't really find the matching file on the internet....which one can i use as an alternative?
Is there sth wrong with my bootloader itself? I can't access it via Mac as I was used to before...so adb reboot bootloader doesn't work at all...it also seems to be kind of a matter of luck what i get with the fastboot commands...sometimes I can e.g. read the version-main, a few seconds later it says "waiting for device" and I have to exit the terminal window...
Please be lenient with me if there's an obvious fallacy...
Would it make sense or is it even possible to flash CWM over TWRP to solve the sideload issue respectively mount the SD card?
Thanks and greetings
Alex

Is there a way to get SuperCID from my point?
Or flash another RUU than the original H3G? Are there any universal RUUs, just to get out of this misery at least?
Thanks!
Here some more input:
fastboot getvar all
Alexanders-MacBook-Pro:~ dr_zikzak$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.771.6
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35********
(bootloader) imei: 3544360******
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__106
(bootloader) battery-status: good
(bootloader) battery-voltage: 4249mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s
~ # mount
~ # mount
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)
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)
~ #
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Greetings Alex

dr.zikzak said:
Is there a way to get SuperCID from my point?
Greetings Alex
Click to expand...
Click to collapse
take a look at http://forum.xda-developers.com/showthread.php?p=51774312&postcount=50
(either the entire thread, from the beginning, or whatever part you think applies to you)
PS: this is for m7_u or m7_ul models only... Sprint and Verizon have different partitions

nkk71 said:
take a look at http://forum.xda-developers.com/showthread.php?p=51774312&postcount=50
(either the entire thread, from the beginning, or whatever part you think applies to you)
PS: this is for m7_u or m7_ul models only... Sprint and Verizon have different partitions
Click to expand...
Click to collapse
Hello!
Thanks for having a look...I've gone through the thread and did what pavel122 did, here are the results:
~ # cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ # umount /cache
umount: can't umount /cache: Invalid argument
~ # umount /data
~ # umount /data
umount: can't umount /data: Invalid argument
~ # umount /system
~ # umount /system
umount: can't umount /system: Invalid argument
~ # e2fsck -n -v -f /dev/block/mmcblk0p35
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
11 inodes used (0.01%)
0 non-contiguous files (0.0%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 3
15607 blocks used (3.28%)
0 bad blocks
0 large files
0 regular files
2 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
2 files
~ # e2fsck -n -v -f /dev/block/mmcblk0p36
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
18 inodes used (0.04%)
1 non-contiguous file (5.6%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 10
5279 blocks used (3.22%)
0 bad blocks
0 large files
6 regular files
3 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
9 files
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
What does it tell me...are the files okay? Should i mount data again?
And if so, just go to adb sideload in TWRP and try command "adb sideload ROM.zip" and it should work?
Thank you!
Greetings Alex

If I mount data again and go to sideload in TWRP and type "adb sideload ROM.zip", it gives me this:
Alexanders-MacBook-Pro:Android dr_zikzak$ adb push /Users/dr_zikzak/Desktop/Android/R62.zip
Android Debug Bridge version 1.0.26
-d - directs command to the only connected USB device
returns an error if more than one USB device is present.
-e - directs command to the only running emulator.
returns an error if more than one emulator is running.
-s <serial number> - directs command to the USB device or emulator with
the given serial number. Overrides ANDROID_SERIAL
environment variable.
-p <product name or path> - simple product name like 'sooner', or
a relative/absolute path to a product
out directory like 'out/target/product/sooner'.
If -p is not specified, the ANDROID_PRODUCT_OUT
environment variable is used, which must
be an absolute path.
devices - list all connected devices
connect <host>[:<port>] - connect to a device via TCP/IP
Port 5555 is used by default if no port number is specified.
disconnect [<host>[:<port>]] - disconnect from a TCP/IP device.
Port 5555 is used by default if no port number is specified.
Using this ocmmand with no additional arguments
will disconnect from all connected TCP/IP devices.
device commands:
adb push <local> <remote> - copy file/dir to device
adb pull <remote> [<local>] - copy file/dir from device
adb sync [ <directory> ] - copy host->device only if changed
(-l means list but don't copy)
(see 'adb help all')
adb shell - run remote shell interactively
adb shell <command> - run remote shell command
adb emu <command> - run emulator console command
adb logcat [ <filter-spec> ] - View device log
adb forward <local> <remote> - forward socket connections
forward specs are one of:
tcp:<port>
localabstract:<unix domain socket name>
localreserved:<unix domain socket name>
localfilesystem:<unix domain socket name>
dev:<character device name>
jdwp:<process pid> (remote only)
adb jdwp - list PIDs of processes hosting a JDWP transport
adb install [-l] [-r] [-s] <file> - push this package file to the device and install it
('-l' means forward-lock the app)
('-r' means reinstall the app, keeping its data)
('-s' means install on SD card instead of internal storage)
adb uninstall [-k] <package> - remove this app package from the device
('-k' means keep the data and cache directories)
adb bugreport - return all information from the device
that should be included in a bug report.
adb help - show this help message
adb version - show version num
DATAOPTS:
(no option) - don't touch the data partition
-w - wipe the data partition
-d - flash the data partition
scripting:
adb wait-for-device - block until device is online
adb start-server - ensure that there is a server running
adb kill-server - kill the server if it is running
adb get-state - prints: offline | bootloader | device
adb get-serialno - prints: <serial-number>
adb status-window - continuously print device status for a specified device
adb remount - remounts the /system partition on the device read-write
adb reboot [bootloader|recovery] - reboots the device, optionally into the bootloader or recovery program
adb reboot-bootloader - reboots the device into the bootloader
adb root - restarts the adbd daemon with root permissions
adb usb - restarts the adbd daemon listening on USB
adb tcpip <port> - restarts the adbd daemon listening on TCP on the specified port
networking:
adb ppp <tty> [parameters] - Run PPP over USB.
Note: you should not automatically start a PPP connection.
<tty> refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
[parameters] - Eg. defaultroute debug dump local notty usepeerdns
adb sync notes: adb sync [ <directory> ]
<localdir> can be interpreted in several ways:
- If <directory> is not specified, both /system and /data partitions will be updated.
- If it is "system" or "data", only the corresponding partition
is updated.
environmental variables:
ADB_TRACE - Print debug information. A comma separated list of the following values
1 or all, adb, sockets, packets, rwx, usb, sync, sysdeps, transport, jdwp
ANDROID_SERIAL - The serial number to connect to. -s takes priority over this if given.
ANDROID_LOG_TAGS - When used with the logcat option, only these debug tags are printed.
By the way, as it does neither work the one, nor the other way: is "adb sideload ROM.zip" just to name the zips only name or the whole path?
Thanks!

If I check with the e2fsck commands, it shows exactly the same as pavel122 device!
data is in use or still mounted --> but if i force "umount /data", it says:
~ # umount /data
umount: can't umount /data: Invalid argument
If i mount data and go with that, i can actually send sth. to the device with "adb sideload"...but if I want to install the zip, it fails!
What to do?
Thanks and greetings Alex

You can never "sideload" an entire rom. Thats just for updating a current rom, thats why you fail. The md5sum checks will not add up.
The mmcblk0p35 is the userdata partition so why was it busy? Either way it doesn´t matter.
If all you need to do is copy a complete rom to your phone from you computer the command is
Code:
adb push filename.zip /sdcard/download
and the rom should end up in your download folder on your phone. Install it from the menu in recovery.

xxerkxx said:
You can never "sideload" an entire rom. Thats just for updating a current rom, thats why you fail. The md5sum checks will not add up.
The mmcblk0p35 is the userdata partition so why was it busy? Either way it doesn´t matter.
If all you need to do is copy a complete rom to your phone from you computer the command is
Code:
adb push filename.zip /sdcard/download
and the rom should end up in your download folder on your phone. Install it from the menu in recovery.
Click to expand...
Click to collapse
1- you can sideload an entire ROM, it has nothing to do with updating current ROM
2- mmcblk0p35 is: mmcblk0p35: 73fffc00 00000200 "system" not userdata
dr.zikzak said:
If I check with the e2fsck commands, it shows exactly the same as pavel122 device!
data is in use or still mounted --> but if i force "umount /data", it says:
~ # umount /data
umount: can't umount /data: Invalid argument
If i mount data and go with that, i can actually send sth. to the device with "adb sideload"...but if I want to install the zip, it fails!
What to do?
Thanks and greetings Alex
Click to expand...
Click to collapse
Did you fix (ie format) the partition?
this error:
Code:
~ # umount /data
umount: can't umount /data: Invalid argument
is normal if it's already unmounted, but did you also umount /sdcard
then run e2fsck
if you still get errors you need to format it, not just wipe.
Once the format is complete, you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
.

imo, it is much easier (and safer) to get yourself an USB OTG cable / cardreader and write your backup to it and flash your roms from it
I use this one LINK
Whats sucks more than eraseing that last backup when you do a full wipe by accident. next to that, when i switch to a complete other rom I always do a full wipe. realy helps the stability of your rom

nkk71 said:
1- you can sideload an entire ROM, it has nothing to do with updating current ROM
2- mmcblk0p35 is: mmcblk0p35: 73fffc00 00000200 "system" not userdata
Did you fix (ie format) the partition?
this error:
Code:
~ # umount /data
umount: can't umount /data: Invalid argument
is normal if it's already unmounted, but did you also umount /sdcard
then run e2fsck
if you still get errors you need to format it, not just wipe.
Once the format is complete, you can either:
1- OTG cable
2- adb push <name of rom>.zip /sdcard/
3- initiate sideload in custom recovery, then adb sideload <name of rom>.zip
.
Click to expand...
Click to collapse
Hello again!
I'm just writing this from the HTC One...unbelievable
Thanks for your help....I was on the brink of smashing it yesterday!
I've gone through the e2fsck once again and it seemed okay...so I tried to push the rom as it is supposed, so just the zip name and correct order of steps!
I also asked mike1986. for his opinion and he told me that the "freezing" does only look as if it freezes....
A mistake I made was not to wait until the cursor started blinking again when I was pushing the rom over to the device....I didn't notice that there was a running process...no percentage or something!
So I tried again and pushed the ROM again...it took approx 7 minutes and the cursor started blinking again...
The file was completely transferred and so I could start flashing it fr recovery! Worked at first attempt, no bootloop or crashes!
The phone is smooth again..even better than before I dare say....
I've learned a lot, especially from you, Mr. nkk71..thank you for spending so much time on the problems caused by the stupidity of people like me
THANKS THANKS THANKS very much!
Greetings Alex

Thanks for the info about sideload, didn´t know that it could replace the entire rom!
nkk71 said:
1- you can sideload an entire ROM, it has nothing to do with updating current ROM
2- mmcblk0p35 is: mmcblk0p35: 73fffc00 00000200 "system" not userdata
.
Click to expand...
Click to collapse
It was i typo from my part I ment blk37:
e2fsck: Device or resource busy while trying to open /dev/block/mmcblk0p37
Filesystem mounted or opened exclusively by another program?
Click to expand...
Click to collapse

dr.zikzak said:
Hello again!
I'm just writing this from the HTC One...unbelievable
Thanks for your help....I was on the brink of smashing it yesterday!
I've gone through the e2fsck once again and it seemed okay...so I tried to push the rom as it is supposed, so just the zip name and correct order of steps!
I also asked mike1986. for his opinion and he told me that the "freezing" does only look as if it freezes....
A mistake I made was not to wait until the cursor started blinking again when I was pushing the rom over to the device....I didn't notice that there was a running process...no percentage or something!
So I tried again and pushed the ROM again...it took approx 7 minutes and the cursor started blinking again...
The file was completely transferred and so I could start flashing it fr recovery! Worked at first attempt, no bootloop or crashes!
The phone is smooth again..even better than before I dare say....
I've learned a lot, especially from you, Mr. nkk71..thank you for spending so much time on the problems caused by the stupidity of people like me
THANKS THANKS THANKS very much!
Greetings Alex
Click to expand...
Click to collapse
yeah, sorry, i should have mentioned that, i should have actually linked this:
Code:
C:\ADB3>[B][COLOR="Blue"]adb devices[/COLOR][/B]
List of devices attached
HT34xxxxxxxx recovery [I][SIZE="1"]<- you are now in recovery[/SIZE][/I]
C:\ADB3>[B][COLOR="Blue"]adb push Android_Revolution_HD-One_52.0.zip /sdcard/[/COLOR][/B]
2990 KB/s (1172224138 bytes in 382.835s) [I][B]<- yes, it took over 5 mins,
[U]without[/U] showing any progress[/B][/I]
[I][U][SIZE="1"]Just to double-check the file is not corrupt[/SIZE][/U][/I]
C:\ADB3>[B][COLOR="Blue"]adb shell md5sum /sdcard/Android_Revolution_HD-One_52.0.zip[/COLOR][/B]
2eff0d37fec5789b946c43f7da2c13bf /sdcard/Android_Revolution_HD-One_52.0.zip
[INDENT]from the OP:
Android Revolution HD 52.0 -- MD5 sum: 2EFF0D37FEC5789B946C43F7DA2C13BF --
==> so all is good :)[/INDENT]
C:\ADB3>
-> in recovery, select "install" and install the ROM
---------- Post added at 04:58 PM ---------- Previous post was at 04:56 PM ----------
xxerkxx said:
Thanks for the info about sideload, didn´t know that it could replace the entire rom!
It was i typo from my part I ment blk37:
Click to expand...
Click to collapse
no worries, just pointed it out so the OP doesn't get confused, and adb sideload can install a full ROM with no problems:
in TWRP recovery -> Advanced -> ADB Sideload -> swipe
C:\ADB3>adb devices
List of devices attached
HT34xxxxxxxx sideload
^^ now you're in sideload, and can start adb sideload rom.zip
I believe sideload even shows progress, though I've never used it, I prefer push

It was just my mistake...could have waited a little longer, couldn't I? ....patience has never been one of my virtues
Nonetheless everything's fine and I'm happy again...
I should also remain behind increasing my knowledge about android an it's components...just to know what I'm actually doing and what is possible with this system!
What would you recommend? Just read the forum or is there any source where I can read about that...just basics about the system itself...
Thanks once more and keep it up, really appreciate it!
Greetings Alex

dr.zikzak said:
What would you recommend? Just read the forum or is there any source where I can read about that...just basics about the system itself...
Click to expand...
Click to collapse
yeah mostly the forum and also @mike1986. blog has very good info: http://android-revolution-hd.blogspot.com/p/android-guides.html

[Solved] /efs partition gone

Hello, [Solution lower in this thread]
My /EFS partition is gone. I dont know why, because I wasnt doing anything with my phone at that moment. Until this problem I was running cyanogenmod nightly. The battery was wasted I think because it feels slightly thicker than normal. I already replaced it.
I have an efs.img made with SA manager.
Symptoms:
Bootloop
Original recovery says:
Code:
E: failed to mount /efs (invalid argument)
I can get into recovery & download mode.
I can still flash philz custom recovery.
When in cwm I can still flash a zip with a rom, but it wont start.
These are the steps I tried to get my phone working again:
ODIN
Flashed stock jellybean with original pit file, and checked "clear efs" in odin 3.09.
Custom Recovery
Connected with ADB, and executed the following commands:
Code:
But as you can see that doesnt help much.
I tried several other things, but they boil down to the same. I used an aroma efs restore tool, but it just executes the dd command and fails the same way.

jogai said:
Hello,
My /EFS partition is gone. I dont know why, because I wasnt doing anything with my phone at that moment. Until this problem I was running cyanogenmod nightly. The battery was wasted I think because it feels slightly thicker than normal. I already replaced it.
I have an efs.img made with SA manager.
Symptoms:
Bootloop
Original recovery says:
Code:
E: failed to mount /efs (invalid argument)
I can get into recovery & download mode.
I can still flash philz custom recovery.
When in cwm I can still flash a zip with a rom, but it wont start.
These are the steps I tried to get my phone working again:
ODIN
Flashed stock jellybean with original pit file, and checked "clear efs" in odin 3.09.
Custom Recovery
Connected with ADB, and executed the following commands:
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
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/mmcblk0p7 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered)
/dev/block/vold/259:3 on /storage/sdcard0 type vfat (rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_uime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro)
~ # mke2fs /dev/block/mmcblk0p3
mke2fs /dev/block/mmcblk0p3
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
160 inodes, 1280 blocks
64 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=1310720
1 block group
8192 blocks per group, 8192 fragments per group
160 inodes per group
Writing inode tables: done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 27 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # dd if=/storage/sdcard0/efs.img of=/dev/block/mmcblk0p3 bs=4096
dd if=/storage/sdcard0/efs.img of=/dev/block/mmcblk0p3 bs=4096
dd: writing '/dev/block/mmcblk0p3': No space left on device
321+0 records in
320+0 records out
1310720 bytes (1.3MB) copied, 0.035800 seconds, 34.9MB/s
~ # chown 1001:radio /efs/nv_data.bin
chown 1001:radio /efs/nv_data.bin
chown: /efs/nv_data.bin: No such file or directory
But as you can see that doesnt help much.
I tried several other things, but they boil down to the same. I used an aroma efs restore tool, but it just executes the dd command and fails the same way.
Click to expand...
Click to collapse
so hold on!
the dd is failing because the img file is larger than the partition
why?
https://github.com/CyanogenMod/andr...common/blob/cm-11.0/rootdir/fstab.smdk4210#L9
i dont have an exynos4 device, but it seems p1 is /efs. and you are flashing p3, wtf!!! its a miracle if the phone is not fully bricked!! also, was efs mounted while you dd'ed? that would have corrupted it! not to mention using chown on it.
seriously, please stop randomly touching things and be very sure of what you do next or you'll have an unrecoverable brick soon.
p2 and p3 seem to be the bootloaders:
https://gitlab.com/ameer1234567890/...part_layouts/raw/partlayout4nandroid.GT-N7000
so. have you tried rebooting the phone after this? do you still have recovery and download mode?
if so, you need to recover p3 somehow. google a method then ASK before doing anything.
go to recovery and adb shell to it.
use blockdev command to find out the sizes of partitions p1 p2 and p3.
compare it to the size of the alleged-efs.img file you have, which apparently may actually be anything but.
unmount everything from recovery, then you can just adb pull /dev/your/desired/partition.
(i havent seen this used anywhere in xda, but i use it all the time. easier than dd'ing)
get images of your current p1 p2 and p3.
check that p3 and alleged-efs.img match (except for size) to verify that p3 was actually overwritten.
check the contents of alleged-efs.img and verify that it actually is an efs partition image.
dont make any further changes, and post the result of EVERYTHING here

Yes. Can confirm p1 is EFS.
This is N7000 partition table print by parted.
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 4194kB 25.2MB 21.0MB ext4 EFS
2 25.2MB 26.5MB 1311kB SBL1
3 27.3MB 28.6MB 1311kB SBL2
4 29.4MB 37.7MB 8389kB PARAM
5 37.7MB 46.1MB 8389kB KERNEL
6 46.1MB 54.5MB 8389kB RECOVERY
7 54.5MB 264MB 210MB ext4 CACHE
8 264MB 281MB 16.8MB MODEM
9 281MB 1174MB 893MB ext4 FACTORYFS
10 1174MB 3322MB 2147MB ext4 DATAFS
11 3322MB 15.2GB 11.9GB fat32 UMS
12 15.2GB 15.8GB 537MB ext4 HIDDEN
The efs backup image in my phone is about 20mb.
GL.

you havent answered my questions.
so. have you tried rebooting the phone after this? do you still have recovery and download mode?
go to recovery and adb shell to it.
use blockdev command to find out the EXACT sizes of partitions p1 p2 and p3.
or use any other command you want.
compare it to the EXACT size of the alleged-efs.img file you have.
apparently it might be a match for p1, which is good.
get images of your current p1 p2 and p3:
unmount everything from recovery, then you can just adb pull /dev/your/desired/partition.
(i havent seen this used anywhere in xda, but i use it all the time. easier than dd'ing)
this is another way to find the exact partition sizes by the way: looking at the image sizes
check that p3 and alleged-efs.img match (except for size) to verify that p3 was actually overwritten.
do you absolutely trust that your alleged-efs.img is a good efs backup? you can mount it read only in your linux pc and check the contents of it to verify that it actually is an efs partition image. or you can just be sure that it is the right image. or you can pm it to me and i can check that.
you can pm the 4 partition images so i can see whats going on.
i think the phone has two equal bootloader copies (because corruption means unrecoverable brick) and you borked one. that's why it might be still booting. we need to restore p3 asap. please google the subject and check my asumption if you can.
---------- Post added at 03:31 PM ---------- Previous post was at 02:35 PM ----------
of course if you are lazy you can just:
dd if=/storage/sdcard0/efs.img of=/dev/block/mmcblk0p1
or:
adb push your/pc/dir/efs.img /dev/block/mmcblk0p1
MAKE SURE that the efs partition is not mounted before doing those.
you dont need any kind of chown if the backup is ok.
you need to recover p3. it could be as simple as:
adb pull /dev/block/mmcblk0p2 sbl.img
adb push sbl.img /dev/block/mmcblk0p3
if the two copies are the same, BUT DONT DO ANYTHING UNTIL YOU ARE VERY SURE!
if you use, say, odin now, and the writing of p2 gets interrupted for any reason, there wont be p3 to boot! so device is bricked FOREVER. no recovery possible without JTAG. you need to fix this ASAP.
your first TO-DO: verify the assumption that p2 and p3 are supposed to be two bit-by-bit exact copies of the bootloader.
any rom that contains a bootloader is extremely dangerous to flash at this time. this includes stock.

Thanks for your concern!
I got my instructions from here: http://techbeasts.com/2013/11/29/how-to-restore-and-back-up-efs-data-on-samsung-galaxy-devices/
Thats why I was tring p3. The aroma backup tool did try the same partition.
I tried all this several times, and tried to odin flash several times. The phone is still not bricked and I still can get to download & recovery just fine.
I'm at work now, but will post my findings asap.

jogai said:
Thanks for your concern!
I got my instructions from here: http://techbeasts.com/2013/11/29/how-to-restore-and-back-up-efs-data-on-samsung-galaxy-devices/
Thats why I was tring p3. The aroma backup tool did try the same partition.
I tried all this several times, and tried to odin flash several times. The phone is still not bricked and I still can get to download & recovery just fine.
I'm at work now, but will post my findings asap.
Click to expand...
Click to collapse
I would try to restore efs first to see how it goes. I suspect SBL2 maybe not important!

forest1971 said:
I would try to restore efs first to see how it goes. I suspect SBL2 maybe not important!
Click to expand...
Click to collapse
SBL2 is probably the 2nd copy of the bootloader. if SBL1 gets damaged (eg: interrupted odin) the phone is bricked and unbrickable, except by taking it to a JTAG house.
if you are not going to reseach this, at least copy p2 over p3:
adb pull /dev/block/mmcblk0p2 sbl.img
adb push sbl.img /dev/block/mmcblk0p3

Code:
~ # dd if=/dev/block/mmcblk0p2 of=sdcard/sbl1.img
dd if=/dev/block/mmcblk0p2 of=sdcard/sbl1.img
2560+0 records in
2560+0 records out
1310720 bytes (1.3MB) copied, 0.400897 seconds, 3.1MB/s
~ # dd if=/dev/block/mmcblk0p3 of=sdcard/sbl3.img
dd if=/dev/block/mmcblk0p3 of=sdcard/sbl3.img
2560+0 records in
2560+0 records out
1310720 bytes (1.3MB) copied, 0.161615 seconds, 7.7MB/s
Result:
https://filetea.me/t1sxlmPdQ9xSe2qh94HX82wMQ
https://filetea.me/t1sVUTXpxrWQ2mRSIx600aCqg
Code:
~ # dd if=sdcard/efs.img of=/dev/block/mmcblk0p1
dd if=sdcard/efs.img of=/dev/block/mmcblk0p1
40960+0 records in
40960+0 records out
20971520 bytes (20.0MB) copied, 6.726656 seconds, 3.0MB/s
Seems to work!
Code:
~ # mkdir /efs
mkdir /efs
~ # busybox mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox mount -w -t ext4 /dev/block/mmcblk0p1 /efs
I think its strange I had to make /efs, and after reboot its seems gone:
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
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/mmcblk0p7 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,journal_async_commit,data=ordered)
While in fstab.smdk4210:
Code:
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0 auto auto defaults voldmanaged=sdcard0:11,nonremovable,noemulatedsd
/devices/platform/s3c-sdhci.2/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard1:auto
/devices/platform/s3c_otghcd/usb auto auto defaults voldmanaged=usbdisk0:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p8 /modem emmc defaults recoveryonly
Odin'd & working again!
Many thanks to everyone who wanted to help this dumbass out! Much appreciated!

I think its strange I had to make /efs, and after reboot its seems gone:
Code:
~ # mount
mount
rootfs on / type rootfs (rw)
Click to expand...
Click to collapse
/ is rootfs which is a special instance of tempfs (which is a ram drive). nothing you put in / will survive a reboot.