yashsingh1/xdaforums huggingface dataset:
[One (M7) Q&A, Help & Troubleshooting] randomA:
[MENTION=2605798]nkk71[/MENTION]

further to our prev discussion.

getvar :

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.20.707.6
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4320mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-59adc32b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.065s

1 - did you recently flash something not for your phone? (such as a Sprint ROM?)

No I didn't

2 - status of your phone (any working ROM?),

TWRP recovery doesn't work. CWM works but cannot flash MY OWN rom for some stupid Status 7 Error at symlinking stage. (my vers is 4.20.707.6_stock_odexed.zip )

3 - and what you flashed to end up in this situation

Nothing. This morning I wake up, I unlock the screenlock to check my notification, and at some point the phone freezes for like 1, 2 seconds and then self-reboots and enters an endless boot loop.

So i try to go for rom re-flashing and i discover that my TWRP doesn't work anymore and bootloops as well.

That's it.

How to proceed ?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Oh that doesn't sound nice :( let's hope it's not a hardware problem!!

Before we proceed with checking and wiping some partitions, is there anything extremely valuable on the phone, that you need to

try

to recover?

and go ahead, and flash back CWM, we'll use that to do whatever we need to do.
[One (M7) Q&A, Help & Troubleshooting] randomA:
can't we just flash CWM and install the rom?

what would you call extremely valuable ?

of course i have my whole /sdcard/ folder that is pretty valuable and what about doing a nandroid backup?

anyway, i'll flash cwm right away.
[One (M7) Q&A, Help & Troubleshooting] nkk71:
if CWM is giving you the "set_metadata_recursive: some changes failed", then you would need to install a 4.3 ROM.

but we can check the partitions using CWM, so once you have CWM up and running, open a shell

adb shell

mount

copy/paste back.
[One (M7) Q&A, Help & Troubleshooting] randomA:
is this what you're looking for ?

~ # 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 /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)
~ #
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yes, now run the following commands (this will only check the filesystem for error, it won't repair anything, let's see what it has to say): it will check /system, /cache and /data (/data includes your scdard)

[B]e2fsck -n -v -f /dev/block/mmcblk0p35

e2fsck -n -v -f /dev/block/mmcblk0p36

e2fsck -n -v -f /dev/block/mmcblk0p37[/B]
[One (M7) Q&A, Help & Troubleshooting] nkk71:
35 is /system which has no problems

36 is /cache and wasn't checked cause it was mounted/in use, no big deal

37 is /data (that includes apps+data+settings and your sdcard), and as you said is messed up :(

when you said "the process was locked by the saving of the files from /sdcard/ for backup purposes", does that mean you were able to backup your things? cause we're going to have to format your entire /data partition, which will wipe everything.
[One (M7) Q&A, Help & Troubleshooting] randomA:
i dont' know what's in the data partition. i have an old TWRP nandroid backup from the last phone mess that i asked you about 1 or 2 months ago (derp).

I think that one should be sufficient if i need some urgent stuff with TiBa later.

The /sdcard/, i've extracted it all on my HD so that one's safe.

Is there anything else that I should consider from /data/ ?

otherwise i think you can proceed with the guide steps, so that i can finally fix this ***** for good and be done with it.

also, at the end of it all, will i be able to have a functioning TWRP ?

also, any idea of why TWRP crashes while CWM is the only functioning recovery?

Cheers!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
no that's about it.

exit the adb shell if you're still in it.

to format it, first download this: http://www.androidfilehost.com/?fid=23329332407589581

extract the file and place it in your adb/fastboot folder

then

adb push mkfs.ext4 /tmp/

adb shell

chmod 777 /tmp/mkfs.ext4

/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37

once that completes successfully, while still in the shell:

mount /data

mkdir -p /data/media/0

exit

adb reboot bootloader

you should now be in bootloader again (if the "adb reboot bootloader" didnt work, manually reboot to bootloader)

then go ahead and flash TWRP, and use either OTG cable, adb push or adb sideload, to install the ROM you wanted.
[One (M7) Q&A, Help & Troubleshooting] wpetestraw:
Was just getting ready to ask for that :good: thanks!
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Why do you need it??
[One (M7) Q&A, Help & Troubleshooting] wpetestraw:
I've been following this thread because it seems that the One I have suffers from the same fate as doomhendi's: TWRP crash and bootloop, CWM works, but unable to mount cache partition, ADB works with CWM, but nothing else, etc. Hopefully, I can get it working. I just formatted the partitions and made the dir on sd, gonna push ARHD and attempt to install that, and see if it fixes my problem. Everything is looking up now. Before finding this thread, I couldn't do much of anything with it, now I at least seem to be getting somewhere, all thanks to you :good:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
Ah OK, just asked cause TWRP has the "Format Data" option (as opposed to wipe) already built in... not sure about CWM, haven't used it in a while.

let me know if you need any help, and remember those partitions numbers are for m7_u and m7_ul only, not Sprint/Verizon/Dual-SIM.

and btw, unable to mount cache is ok, it's usually only due to the "fastboot erase cache"

Good Luck :fingers-crossed:
[One (M7) Q&A, Help & Troubleshooting] wpetestraw:
Well, then . . . that might cause some issues, I have a Sprint m7 :eek: any advice? I have not flashed ROM yet, push just completed
[One (M7) Q&A, Help & Troubleshooting] randomA:
Ok, after doing all that now TWRP works again.

At the moment it's pushing the rom to /sdcard/ , will report back soon to see how it ends.

In the meantime the adb shell gave this message, is it just sometime to be ignored?

"This filesystem will be automatically checked every 39 mounts or

180 days, whichever comes first. Use tune2fs -c or -i to override."
[One (M7) Q&A, Help & Troubleshooting] nkk71:
that message is perfectly normal :)

now as long as this is not a hardware problem, then you should be good to go.

run an e2fsck -n -v -f /dev/block/mmcblk0p37 later or tomorrow to make sure no more errors are creeping up, if they do come up, then the hardware may have become faulty.

in custom recovery:

umount /data
umount /sdcard
e2fsck -n -v -f /dev/block/mmcblk0p37

the first two commands could give an error, but it's just to make sure p37 is not mounted, otherwise you'll get that "resource is busy" error when trying to run the filesystem check.

---------- Post added at 06:50 PM ---------- Previous post was at 06:42 PM ----------

That's a lot of cross-posting, and this is how my eyes look now: :eek: seriously

Maybe best to open your own thread, possibly in the Q&A section for Sprint M7: http://xdaforums.com/sprint-htc-one

Info you should provide:

1) a "fastboot getvar all" (excluding IMEI, MEID, s/n)

2) what you flashed that got you into this situation (name and link)

3) anything else that you can think of being important

if you want me to get notified (though I'm not too familiar with Sprint devices), just tag me using @ nkk71 <- without the space, and I'll see it in my notifications, and try to assist.
[One (M7) Q&A, Help & Troubleshooting] wpetestraw:
Cool, thanks for the help. I'll hop on over there. Glad you pointed out the partition ids btw thanks
[One (M7) Q&A, Help & Troubleshooting] randomA:
ok, the rom was flashed correctly and the phone is back from the dead.

However, i cant seem to run whatever command you asked me to run.

i go back to recovery.

i do adb shell and then type those but here's the errors:

~ # ←[6nunmount /data
unmount /data
/sbin/sh: unmount: not found
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
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?
~ # ←[6n

think i missed some other line inbetween?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
you didnt miss anything, you just added an "N" it's umount <- without the n
[One (M7) Q&A, Help & Troubleshooting] randomA:
and that's that:

~ # ←[6nunmount /data
unmount /data
/sbin/sh: unmount: not found
~ # ←[6numount /data
umount /data
~ # ←[6numount /sdcard
umount /sdcard
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck -n -v -f /dev/block/mmcblk0p37
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

5021 inodes used (0.29%)
355 non-contiguous files (7.1%)
5 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 4656/41
673539 blocks used (9.88%)
0 bad blocks
0 large files

3636 regular files
1062 directories
0 character device files
0 block device files
3 fifos
0 links
304 symbolic links (304 fast symbolic links)
7 sockets
--------
5012 files
~ # ←[6n
[One (M7) Q&A, Help & Troubleshooting] nkk71:
m7_wls (Sprint) partitions:

mmcblk0p37: 73fffc00 00000200 "system"
mmcblk0p38: 27fffe00 00000200 "cache"
mmcblk0p39: 680000000 00000200 "userdata"

m7_u/ul partitions:

mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"

---------- Post added at 07:11 PM ---------- Previous post was at 07:07 PM ----------

Looks clean now :good: :good:
[One (M7) Q&A, Help & Troubleshooting] randomA:
Thanks for saving the day again, man, seriously, god knows what we'd do without a gentleman like you.

I'll be probably back next month for the next break-down though haha ! :laugh::laugh:
[One (M7) Q&A, Help & Troubleshooting] nkk71:
no problem, glad to be of help.... and hopefully NOT: "I'll be probably back next month for the next break-down" ;)

feel free to hit the thanks button on the useful post :o

Forum Etiquette #15
[One (M7) Q&A, Help & Troubleshooting] doomhendi:
Keep rolling rolling rolling rolling ..

Hehe I am glad my thread is still alive and obviously kind of helpful ^^

And of cause nkk71 keeps on saving the day of so many people - good man :good:
[One (M7) Q&A, Help & Troubleshooting] randomA:
Hey [MENTION=2605798]nkk71[/MENTION], guess what. the phone messed up again.

phone is boot looped. When I try to go into TWRP, it boot loops as well.

i was trying to proceed with this same guide (flashing CWM first) but this time flashboot won't even install CWM.

It says FAILED (remote: not allowed). However my bootloader says unlocked, s-off.

rest of my getvar all:

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.707.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 3811mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s

~

UPDATE:

I fixed it with a reboot of my Win7 and/or using a different USB port. The issue was PC-side apparently.

Flashed CWM correctly. Accessed adb.

Now the problem is another.

I am trying to :

1. do a nandroid backup through CWM .

However CWM isn't able to mount the /system and /cache partitions.

The nandroid fails on the /system backup and it just says 'Error mounting /system'

2. do a sdcard backup extracting all the files from the SD.

However adb is not letting me as it gives me chain I/O error that I have no idea what it means.

~ # ls sdcard/0/
ls sdcard/0/
ls: sdcard/0/Download: I/O error
ls: sdcard/0/WhatsApp: I/O error
ls: sdcard/0/TWRP: I/O error
ls: sdcard/0/viber: I/O error
ls: sdcard/0/IMFile: I/O error
ls: sdcard/0/My Documents: I/O error
ls: sdcard/0/media: I/O error
ls: sdcard/0/com.facebook.katana: I/O error
7digital Ringtones
Alarms TitaniumBackup
Android UPDATE-SuperSU-v1.99r3.zip
DCIM _nero_sync
Movies data
Music eBooks
Notifications nmdsdcid
Pictures tencent
Podcasts

How to fix this?
[One (M7) Q&A, Help & Troubleshooting] cdxcess:
Clear cache

Try clearing Cache when boot into cwm ok
[One (M7) Q&A, Help & Troubleshooting] nkk71:
That doesn't look promising :(, if this (the bootloop) happened by itself, it could very well be your memory chip is becoming defective.

plus unable to mount /system and the above I/O errors, hmm

Do you need to pull some information from the phone first, because we're going to eventually end up wiping it.

If you need to pull as much content as possible (due to I/O errors you will likely not get all of it), so

step 1: make sure the problem is not related to PC, USB port(s), cable, dirty phone USB port

step 2: pull what you can to PC

adb pull /sdcard/ C:\MyBackup\

step 3: try repairing the partitions (as opposed to formatting)

adb shell
umount /system
umount /cache
umount /data
e2fsck -y -v -f /dev/block/mmcblk0p35
e2fsck -y -v -f /dev/block/mmcblk0p36
e2fsck -y -v -f /dev/block/mmcblk0p37

don't worry if the 'umount' (it's umount not unmount) gives an error, which it will do if the partition is already unmounted

and copy/paste the command prompt output back, to see what the output is, but stay in recovery, if the filesystem repair works, you may be able to mount /system again, and pull even more files from internal storage (fingers crossed)
[One (M7) Q&A, Help & Troubleshooting] randomA:
Yes, i do need to save the sd thing at the very least. I actually would need to do a nandroid backup too, but if /system is not read then how to do it?

ok, let's start with the ordeal

C:\fastboot>adb pull /sdcard/ C:\fastboot\backup\
pull: building file list...
0 files pulled. 0 files skipped.

C:\fastboot>

and this was the ls just for reference

~ # ls
ls
boot init sd-ext
cache init.rc sdcard
charger init.recovery.qcom.rc seapp_contexts
data internal_sd sepolicy
datadata lpm.rc storage
default.prop mnt sys
dev proc system
emmc property_contexts tmp
etc recovery ueventd.qcom.rc
external_sd res ueventd.rc
file_contexts root
fstab.qcom sbin
[One (M7) Q&A, Help & Troubleshooting] nkk71:
hmm, sdcard not there, output of:

adb shell
mount

edit: oops, didn't see it at first

anyway, give me output of "mount", then do

adb pull /data/media c:\mybackup

EDIT2: you wouldn't happen to have an OTG cable would you?
[One (M7) Q&A, Help & Troubleshooting] randomA:
C:\fastboot>adb shell
~ # 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 /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)
~ # exit
exit

BUT!

I used the mount command on CWM and now it's pulling stuff out...

I'll be in touch.

edit: never had an OTG in my life :(
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yep, /data wasn't mounted.

good luck, i'll check back when i can
[One (M7) Q&A, Help & Troubleshooting] randomA:
step 3 here below for your review.

C:\fastboot>adb shell
~ # umount /system
umount /system
umount: can't umount /system: Invalid argument
~ # umount /cache
umount /cache
umount: can't umount /cache: Invalid argument
~ # umount /data
umount /data
~ # e2fsck -y -v -f /dev/block/mmcblk0p35
e2fsck -y -v -f /dev/block/mmcblk0p35
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/mmcblk0p35: recovering journal
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

2598 inodes used (2.27%)
84 non-contiguous files (3.2%)
3 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2508/5
424624 blocks used (92.56%)
0 bad blocks
0 large files

2432 regular files
80 directories
0 character device files
0 block device files
0 fifos
0 links
77 symbolic links (77 fast symbolic links)
0 sockets
--------
2589 files
~ # e2fsck -y -v -f /dev/block/mmcblk0p36
e2fsck -y -v -f /dev/block/mmcblk0p36
e2fsck 1.41.14 (22-Dec-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p
36

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>

~ # e2fsck -y -v -f /dev/block/mmcblk0p37
e2fsck -y -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Directory entry for '.' in ... (475156) is big.
Split? yes

Missing '..' in directory inode 475156.
Fix? yes

Setting filetype for entry '..' in ... (475156) to 2.
Pass 3: Checking directory connectivity
'..' in /data/com.viber.voip/app_webview/Cache (475156) is <The NULL inode> (0),
should be /data/com.viber.voip/app_webview (418181).
Fix? yes

Pass 4: Checking reference counts
Inode 2 ref count is 33, should be 34. Fix? yes

Pass 5: Checking group summary information

/dev/block/mmcblk0p37: ***** FILE SYSTEM WAS MODIFIED *****

44453 inodes used (2.61%)
1233 non-contiguous files (2.8%)
41 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 43993/133
1732604 blocks used (25.42%)
0 bad blocks
2 large files

41842 regular files
2276 directories
0 character device files
0 block device files
3 fifos
0 links
312 symbolic links (305 fast symbolic links)
11 sockets
--------
44444 files
~ #

in the meantime... on CWM, i tried mounting /system and it did mount something.

i started the process for a new nandroid backup. let's see if it gives error or succeeds.

---------- Post added at 05:46 PM ---------- Previous post was at 05:38 PM ----------

nandroid failed the backup.

it says " Error while making a backup image of /system!"

However I see a (partial?) backup in the adb shell CWM folder.... what exactly is inside there?

What now?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
/cache partition is OK

/data partition had some errors, hopefully fixed now, so if something didn't get pulled before you may want to try again

but unfortunately /system is a complete mess "e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p36", i don't think you'll be able to repair that to make a nandroid,

does the recovery you are running have the option of making a nandroid excluding /system? if so you can do that (at least you

should

be able to restore apps+data using Titanium Backup or Nandroid Manager)

if that option doesn't exist, you'll need to wipe /system within recovery (that should format it, if it doesn't we'll have to use mkfs), then you should be able to make a nandroid and pull it; obviously the /system (the ROM) partition will be empty, but at least you'd get apps+data+settings in that nandroid.
[One (M7) Q&A, Help & Troubleshooting] randomA:
no, i just have CWM and CWM doesnt have such option :((

its nandroid uses the system as well. so i guess this way isn't viable.

for your 2nd option, please provide the guide steps ?

Also, please provide the steps for what happens AFTER these files are all saved.

Thanks a lot
[One (M7) Q&A, Help & Troubleshooting] nkk71:
i haven't used CWM in a very long time, try going to the WIPE menu, and find an option to only wipe /system (not /data not /sdcard not internal storage)

if you can't find it, then we'll have to do it through adb shell, let me know
[One (M7) Q&A, Help & Troubleshooting] randomA:
the closest thing i found is "format /system"

is that ok?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
yes, that should be the one, you just want to avoid /data, internal storage, /sdcard

after it formats /system, it should be able to do a successful nandroid (of course it won't contain any rom, but you can get your apps+data from it)
[One (M7) Q&A, Help & Troubleshooting] randomA:
ok done! great thanks!

pulling it to my pc.

now the next step should be to push the rom inside the adb and load it through CWM right ?

or can i just install TWRP before pushing the rom ? will it work? I really dont like Cwm...
[One (M7) Q&A, Help & Troubleshooting] nkk71:
once you have everything pulled to your PC, you should reflash TWRP because CWM is not compatible with 4.4 ROMs

hopefully it will no longer bootloop (i'm

guessing

, the corrupt /system partition was the reason TWRP wasn't booting properly), now that this is fixed, TWRP should function again.

once TWRP is up and running, push the ROM (or sideload) and install the ROM, if all goes well, after a couple of hours and a few reboots, you should run the e2fsck commands again to make sure no errors are coming up.
[One (M7) Q&A, Help & Troubleshooting] randomA:
Ok so, the nandroid backup process ended giving this error:

Backup of data completed.

No .android_secure found. Skipping backup of application on external storage.

Backing up cache...

Can't mount /cache!

I guess it's still ok anyway, right?
[One (M7) Q&A, Help & Troubleshooting] nkk71:
check the folder you pulled, a full CWM nandroid would look like this:

Directory of X:\zHTC One M7\nandroids\2013-11-25.16.37.37

02/01/2014 18:51 <DIR> .
02/01/2014 18:51 <DIR> ..
25/11/2013 19:37 16,777,216 boot.img
25/11/2013 19:42 0 cache.ext4.tar
25/11/2013 19:42 13,824 cache.ext4.tar.a
[B][COLOR="Blue"]25/11/2013 19:39 0 data.ext4.tar
25/11/2013 19:40 1,000,000,000 data.ext4.tar.a
25/11/2013 19:41 1,000,000,000 data.ext4.tar.b
25/11/2013 19:42 390,490,112 data.ext4.tar.c[/COLOR][/B]
[B][COLOR="Blue"]25/11/2013 19:43 542 nandroid.md5[/COLOR][/B]
25/11/2013 19:37 16,776,704 recovery.img
25/11/2013 19:43 678,619 recovery.log
25/11/2013 19:37 0 system.ext4.tar
25/11/2013 19:38 1,000,000,000 system.ext4.tar.a
25/11/2013 19:39 304,979,456 system.ext4.tar.b
13 File(s) 3,729,716,473 bytes
2 Dir(s) 120,811,356,160 bytes free

obviously your system partition is going to close to zero, since you formatted it.

if you wanna do a "double-backup", once you have TWRP flashed, make another nandroid of the /data partition only (since in TWRP you can select which ones you want)