[Q] [HELP] My phone reboots itself in hboot, fastboot, recovery...

Search This thread

enel_

Senior Member
Aug 28, 2009
433
108
The second:

~ # cat/proc/emmc
cat/proc/emmc
/sbin/sh: cat/proc/emmc: not found
~ #
 

enel_

Senior Member
Aug 28, 2009
433
108
Sorry sorry, my mistake, here it is:

~ # cat /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"
~ #
 

r.ciesla

Senior Member
Mar 28, 2010
122
83
Poole
Here is a picture of my hboot and so far it's very stable, fastboot stable, fastboot usb stable, laptop recognizes my phone, hboot stable.

Lock your bootloader, next you'll need to downgrade the base with flashing THAT

You'll need to rename PN07IMG_M7_UL_JB_50_HTC_Europe_1.29.401.13_Radio_4A.14.3250.13_10.33.1150.01_release_316789_signed.zip
to rom.zip, then place it to directory where you keep fastboot & adb.

next put your phone in fastboot usb, then in windows cmd:
Code:
fastboot oem rebootRUU

now your phone is in RUU mode and now you need to be really really really careful!
type:
Code:
fastboot flash zip rom.zip

your phone will reboot in RUU mode by itself, do not be scared
You should see at the end of cmd saying:
some errors or error 99 or something like that
at it will say Flush Image Immediately!!!
retype:
Code:
fastboot flash zip rom.zip

And NOW LEAVE AND DO NOT TOUCH your phone. It will take about 15-20 minutes.

When it's done the progress bar will be at very end showing like it stuck, do not be scared ;)
In Windows CMD should say: SUCCESSFUL!!!

type in cmd:
Code:
fastboot reboot

And your phone will be like out from the box :)

Be REALLY Careful with this procedure :)
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
Sorry sorry, my mistake, here it is:

~ # cat /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"
~ #

yep, missing spaces is no good, let's go ahead and check the partitions:

~# umount /data


~# e2fsck -n -v -f /dev/block/mmcblk0p35

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

~# e2fsck -n -v -f /dev/block/mmcblk0p37

just report back, nothing else ;)
 

enel_

Senior Member
Aug 28, 2009
433
108
yep, missing spaces is no good, let's go ahead and check the partitions:

~# umount /data


~# e2fsck -n -v -f /dev/block/mmcblk0p35

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

~# e2fsck -n -v -f /dev/block/mmcblk0p37

just report back, nothing else ;)

First:

~ # e2fsck -n -v -f /dev/block/mmcblk0p35
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
/lost+found not found. Create? no

Pass 4: Checking reference counts
Pass 5: Checking group summary information

/dev/block/mmcblk0p35: ********** WARNING: Filesystem still has errors *********
*


2632 inodes used (2.29%)
122 non-contiguous files (4.6%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2538/12
442710 blocks used (96.50%)
0 bad blocks
0 large files

2470 regular files
80 directories
0 character device files
0 block device files
0 fifos
0 links
73 symbolic links (73 fast symbolic links)
0 sockets
--------
2623 files
~ #
 

enel_

Senior Member
Aug 28, 2009
433
108
Second:

~ # e2fsck -n -v -f /dev/block/mmcblk0p36
e2fsck -n -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>

~ #
 

enel_

Senior Member
Aug 28, 2009
433
108
Third:

~ # e2fsck -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
Inodes that were part of a corrupted orphan linked list found. Fix? no

Inode 247105 was part of the orphaned inode list. IGNORED.
Inode 247106 was part of the orphaned inode list. IGNORED.
Inode 247107 was part of the orphaned inode list. IGNORED.
Inode 247108 was part of the orphaned inode list. IGNORED.
Inode 247109 was part of the orphaned inode list. IGNORED.
Inode 247110 was part of the orphaned inode list. IGNORED.
Inode 247111 was part of the orphaned inode list. IGNORED.
Inode 247112 was part of the orphaned inode list. IGNORED.
Inode 247113 was part of the orphaned inode list. IGNORED.
Inode 247114 was part of the orphaned inode list. IGNORED.
Inode 247115 was part of the orphaned inode list. IGNORED.
Inode 247116 was part of the orphaned inode list. IGNORED.
Inode 247117 was part of the orphaned inode list. IGNORED.
Inode 247118 was part of the orphaned inode list. IGNORED.
Inode 247119 was part of the orphaned inode list. IGNORED.
Inode 247120 was part of the orphaned inode list. IGNORED.
Inode 247122 was part of the orphaned inode list. IGNORED.
Inode 247123 was part of the orphaned inode list. IGNORED.
Inode 247124 was part of the orphaned inode list. IGNORED.
Inode 247125 was part of the orphaned inode list. IGNORED.
Inode 247126 was part of the orphaned inode list. IGNORED.
Inode 247127 was part of the orphaned inode list. IGNORED.
Inode 247128 was part of the orphaned inode list. IGNORED.
Inode 247129 was part of the orphaned inode list. IGNORED.
Inode 247130 was part of the orphaned inode list. IGNORED.
Inode 247131 was part of the orphaned inode list. IGNORED.
Inode 247132 was part of the orphaned inode list. IGNORED.
Inode 247133 was part of the orphaned inode list. IGNORED.
Inode 247134 was part of the orphaned inode list. IGNORED.
Inode 247135 was part of the orphaned inode list. IGNORED.
Inode 247136 was part of the orphaned inode list. IGNORED.
Inode 247137 was part of the orphaned inode list. IGNORED.
Inode 247138 was part of the orphaned inode list. IGNORED.
Inode 247143 was part of the orphaned inode list. IGNORED.
Inode 247144 was part of the orphaned inode list. IGNORED.
Inode 247148 was part of the orphaned inode list. IGNORED.
Inode 247149 was part of the orphaned inode list. IGNORED.
Inode 247150 was part of the orphaned inode list. IGNORED.
Inode 247151 was part of the orphaned inode list. IGNORED.
Inode 247152 was part of the orphaned inode list. IGNORED.
Inode 247153 was part of the orphaned inode list. IGNORED.
Inode 247154 was part of the orphaned inode list. IGNORED.
Inode 247155 was part of the orphaned inode list. IGNORED.
Inode 247156 was part of the orphaned inode list. IGNORED.
Inode 247157 was part of the orphaned inode list. IGNORED.
Inode 247158 was part of the orphaned inode list. IGNORED.
Inode 247159 was part of the orphaned inode list. IGNORED.
Inode 247160 was part of the orphaned inode list. IGNORED.
Inode 247161 was part of the orphaned inode list. IGNORED.
Inode 247162 was part of the orphaned inode list. IGNORED.
Inode 247163 was part of the orphaned inode list. IGNORED.
Inode 247164 was part of the orphaned inode list. IGNORED.
Inode 247165 was part of the orphaned inode list. IGNORED.
Inode 247166 was part of the orphaned inode list. IGNORED.
Inode 247167 was part of the orphaned inode list. IGNORED.
Inode 247182 was part of the orphaned inode list. IGNORED.
Inode 247183 was part of the orphaned inode list. IGNORED.
Inode 247184 was part of the orphaned inode list. IGNORED.
Inode 247185 was part of the orphaned inode list. IGNORED.
Inode 247186 was part of the orphaned inode list. IGNORED.
Inode 247188 was part of the orphaned inode list. IGNORED.
Inode 247189 was part of the orphaned inode list. IGNORED.
Inode 247190 was part of the orphaned inode list. IGNORED.
Inode 247191 was part of the orphaned inode list. IGNORED.
Inode 247192 was part of the orphaned inode list. IGNORED.
Inode 247193 was part of the orphaned inode list. IGNORED.
Inode 247194 was part of the orphaned inode list. IGNORED.
Inode 247195 was part of the orphaned inode list. IGNORED.
Inode 638980 was part of the orphaned inode list. IGNORED.
Inode 638981 was part of the orphaned inode list. IGNORED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Inode bitmap differences: -245909
Fix? no

Free inodes count wrong for group #30 (6877, counted=6876).
Fix? no

Free inodes count wrong (1700699, counted=1700698).
Fix? no


/dev/block/mmcblk0p37: ********** WARNING: Filesystem still has errors *********
*


3237 inodes used (0.19%)
315 non-contiguous files (9.7%)
2 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2920/20
341182 blocks used (5.01%)
0 bad blocks
1 large file

2085 regular files
854 directories
0 character device files
0 block device files
0 fifos
0 links
284 symbolic links (284 fast symbolic links)
5 sockets
--------
3228 files
~ #
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
Holy Crap, you have lots or corrupt stuff, unfortunately at this stage I'm going to have to say it's most likely a hardware defect, I'm going to post back shortly with instructions on "real" formatting the partitions back to scratch, but if after the format, the filesystem doesn't hold, then it's a hardware problem.


@xavier_largeaux, how is he going to run a downgrade with S-On??



@enel_ I'll post back in a few minutes.....
 

enel_

Senior Member
Aug 28, 2009
433
108
Holy Crap, you have lots or corrupt stuff, unfortunately at this stage I'm going to have to say it's most likely a hardware defect, I'm going to post back shortly with instructions on "real" formatting the partitions back to scratch, but if after the format, the filesystem doesn't hold, then it's a hardware problem.


@xavier_largeaux, how is he going to run a downgrade with S-On??



@enel_ I'll post back in a few minutes.....

Oh God, I hoped not to hear this... No problem man, I'm going to wait for your instructions. And thank you for helping me out.
 

enel_

Senior Member
Aug 28, 2009
433
108
Bad news, my phone was connected to my laptop, in cwm, suddenly it rebooted, rebooted twice, and booted back to my homescreen. And at my homescreen it rebooted again...

So I think we are again in the reboot horror story and it's going to reboot itself when he wants...
 
Last edited:

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
Third:

~ # e2fsck -n -v -f /dev/block/mmcblk0p37
Inodes that were part of a corrupted orphan linked list found. Fix? no
~ #

Download this: http://goo.gl/pmZ9Mt (credit to @mike1986. for his excellent article: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html)

now open a new command prompt (but leave the shell one open as well, we're going back to that in a minute), and push the downloaded file:
adb push mkfs.ext4 /tmp

now go back to the shell and type:
~# chmod 777 /tmp/mkfs.ext4

and then format the data partition, we're going to leave /system (doesnt look bad) and /cache (looks bad :() for later, if we need to:

Code:
~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37[/B]

Once it formats successfully:
~# mount /data
~# mkdir -p /data/media/0

NOTE: THE ABOVE PROCEDURE WILL COMPLETELY WIPE ALL DATA INCLUDING INTERNAL STORAGE

your phone is going to be completely empty, so you will have to push your rom to your phone, so exit the shell "~# exit" and
adb push <name of rom>.zip /data/media/ <- this will take 5 to 15 minutes depending on the ROM and should come back with success

then in recovery select "install zip" -> "choose zip" -> select the ROM, and go through the installer (hopefully with Success) and reboot.

post back when done, and what's happening

---------- Post added at 07:28 PM ---------- Previous post was at 07:26 PM ----------

Bad news, my phone was connected to my laptop, in cwm, suddenly it rebooted, rebooted twice, and booted back to my homescreen. And at my homescreen it rebooted again...

So I think we are again in the reboot horror story and it's going to reboot itself when he wants...

OK, just saw that, you'll probably have to format /cache as well

Can you get back to recovery? (if need be, do the fastboot commands from before again)

EDIT: i'll be back in 10 minutes
 

enel_

Senior Member
Aug 28, 2009
433
108
We are again in the same horror story as before. I can't boot my phone, as far as I can see I'm going to need like 50 attempts to boot it once.

If I should boot it, can I flash again the boot.img? Flashing it today gave as this time window when my phone was stable?
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
We are again in the same horror story as before. I can't boot my phone, as far as I can see I'm going to need like 50 attempts to boot it once.

If I should boot it, can I flash again the boot.img? Flashing it today gave as this time window when my phone was stable?

we are now at over 70% chance that it is a hardware problem, I'm sorry to say, even if you flash boot.img or whatever, you're phone may be stable for 10 minutes or 10 seconds.

In my humble opinion:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader


-> enter RECOVERY

adb push mkfs.ext4 /tmp

adb shell

~# chmod 777 /tmp/mkfs.ext4
~# umount /data
~# umount /cache
--> nevermind if it gives an error, then
Code:
~#[B] /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p36[/B]

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

/system didnt look to bad so we'll not format it.

then
~# mount /data
~# mkdir -p /data/media/0
~# exit

adb push <name of rom>.zip /data/media/

and try installing it.

Good luck, hope for the best, and post back
 

enel_

Senior Member
Aug 28, 2009
433
108
Thank you very much nkk71, I'm just fu*king sad about this.

I'm going to do all your steps once I've booted into recovery and I hope this will solve my problem.

Just one more question, is unlocking my bootloader the reason for all this?

Or is it flashing TWRP? Or something else...?
 

r.ciesla

Senior Member
Mar 28, 2010
122
83
Poole
Holy Crap, you have lots or corrupt stuff, unfortunately at this stage I'm going to have to say it's most likely a hardware defect, I'm going to post back shortly with instructions on "real" formatting the partitions back to scratch, but if after the format, the filesystem doesn't hold, then it's a hardware problem.


@xavier_largeaux, how is he going to run a downgrade with S-On??



@enel_ I'll post back in a few minutes.....

The Link what I posted earlier is Signed RUU for HTC One Europe HTC__001 PN071000 There will be a signature check and it will reflash entire all partitions but bootloader must be locked otherwise it will fail on first stage. This is only 1 solution what I can think of if the partition table is corrupted and some blocks are not allocated properly. I'm just trying to help :(
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
Thank you very much nkk71, I'm just fu*king sad about this.

I'm going to do all your steps once I've booted into recovery and I hope this will solve my problem.

Just one more question, is unlocking my bootloader the reason for all this?

Or is it flashing TWRP? Or something else...?

Unlocking -> NO
Flashing anything -> NO
TWRP -> highly unlikely (though the two cases I was able to successfully help, had a version of TWRP installed, so there could have been something in one of the versions), but again HIGHLY unlikely, those devs are great and test their stuff to the limit.

if the "real format" doesnt work, then it's a hardware fault. not because you flashed anything!

I'm checking something with mike, and when he get's back to me, if the info has changed I'll let you know. try the steps and post back. wish you best of luck

---------- Post added at 08:10 PM ---------- Previous post was at 08:05 PM ----------

The Link what I posted earlier is Signed RUU for HTC One Europe HTC__001 PN071000 There will be a signature check and it will reflash entire all partitions but bootloader must be locked otherwise it will fail on first stage. This is only 1 solution what I can think of if the partition table is corrupted and some blocks are not allocated properly. I'm just trying to help :(

Salut Xavier, I wasn't trying to be disrespectful or anything really!! Sorry if I offended you, I apologize, and I know you are trying to help :good:

But even with a signed RUU, it will fail because it's an older version than the one on his phone. the only way to downgrade is if you have S-Off.
 

enel_

Senior Member
Aug 28, 2009
433
108
Unlocking -> NO
Flashing anything -> NO
TWRP -> highly unlikely (though the two cases I was able to successfully help, had a version of TWRP installed, so there could have been something in one of the versions), but again HIGHLY unlikely, those devs are great and test their stuff to the limit.

if the "real format" doesnt work, then it's a hardware fault. not because you flashed anything!

I'm checking something with mike, and when he get's back to me, if the info has changed I'll let you know. try the steps and post back. wish you best of luck

---------- Post added at 08:10 PM ---------- Previous post was at 08:05 PM ----------



Salut Xavier, I wasn't trying to be disrespectful or anything really!! Sorry if I offended you, I apologize, and I know you are trying to help :good:

But even with a signed RUU, it will fail because it's an older version than the one on his phone. the only way to downgrade is if you have S-Off.

I was able to boot into recovery and I did all steps to

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

In the middle of this step my phone rebooted. When I boot again into recovery, should I countinue from this step?
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
I was able to boot into recovery and I did all steps to

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

In the middle of this step my phone rebooted. When I boot again into recovery, should I countinue from this step?

hold, were you able to format partition mmcblk0p36 properly?? copy/paste please
 

enel_

Senior Member
Aug 28, 2009
433
108
hold, were you able to format partition mmcblk0p36 properly?? copy/paste please

Here is a copy of cmd:

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb push mkfs.ext
4 /tmp
3398 KB/s (3537143 bytes in 1.016s)

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb shell
~ # chmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # umount /data
umount /data
~ # umount /cache
umount /cache
umount: can't umount /cache: Invalid argument
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p36
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p36
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
40960 inodes, 163839 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
5 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

4096000

Writing inode tables: 171/208
C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>
 

nkk71

Inactive Recognized Developer / Contributor
May 26, 2010
8,741
7,571
53
Beirut
Here is a copy of cmd:

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb push mkfs.ext
4 /tmp
3398 KB/s (3537143 bytes in 1.016s)

C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>adb shell
~ # chmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # umount /data
umount /data
~ # umount /cache
umount /cache
umount: can't umount /cache: Invalid argument
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p36
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p36
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
40960 inodes, 163839 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
5 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304

Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # /tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

4096000

Writing inode tables: 171/208
C:\Users\enel\AppData\Local\Android\android-sdk\platform-tools>

ok both formats look successfull, now run e2fsck to confirm to more errors:
~# e2fsck -n -v -f /dev/block/mmcblk0p36

~# e2fsck -n -v -f /dev/block/mmcblk0p37

if it says "in use", then ~# umount /cache and/or ~# umount /data and run again
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    ok here it is:

    1. in HBOOT select FASTBOOT USB with connected cable
    2. type in cmd:
    Code:
    fastboot erase cache
    3. now you should be able to access recovery, check if you are using latest recovery I'd recommend THIS
    4. reflash recovery in cmd:
    Code:
    fastboot flash recovery <file_name>.img
    5. boot your phone in recovery, you may see some errors but that's fine, mount /data partition only
    6. push rom to your (virtual) sd card by cmd:
    Code:
    adb push <file_name>.zip /data/media/0/
    7. wait about 6 minutes until rom is being transferred to your phone.
    8. in recovery format /system then format /cache and next format /data (do NOT select /data/media !!!)
    9. reboot recovery - you may see some errors but that's fine.
    10. reflash your rom :D

    Hope that helps
    1
    I managed to upload my logcat, here it is:

    http://www14.zippyshare.com/v/26697521/file.html



    I'm afraid xavier to flash a new rom because my phone is unstable in recovery, what if it freezes and shuts itself down in the middle of the flashing process?

    What if I just flash the stock recovery and lock my bootloader again? Maybe my phone is so unstable because of the bootloader?

    if you only unlocked bootloader that's fine you wouldn't have chance to brick your device, however if you S-OFF there is high risk of soft / hard bricking device as you have unrestricted access to ALL partitions, with S-ON you have access to only few partitions.
    When you unlocked your bootloader it WIPED automatically your /data partition and you lost everything what you had on it.
    I remember some time ago that someone after installing TWRP recovery had the same issue what you have described in your post.
    Either you must lock you bootloader and flash entire RUU matching your CID & MID.
    Or follow all steps in my previous post.
    1
    No no, I just unlocked my bootloader, flashed recovery and installed superSU.

    Unfortunately I flashed TWRP also after I unlocker my bootloader...

    10 min ago I wanted to flash stock recovery then clockworkmod and then the rest of your process. Somehow I booted my phone into fastboot, after a lot of attempts to boot it, connected it to my laptop, went into cmd, typed fastboot flash recovery recovery. img it started but suddenly my phone shut itself down, I got a failure in cmd and now after over 30 attempts I can't boot my device.

    Is the interruption of this process something bad? Bricked device?
    switch off your device and connect it to pc using cable, is it going into recovery?
    1
    good to know the progress man, i can imagine how frustrated/worried you must be
    1
    I've made some progress.

    First a extracted boot.img from the latest stock sense rom. I flashed boot. img via cmd with the command fastboot flassh boot boot.img.

    After that I typed fastboot erase cache and then fastboot flash recovery "clockworkmod.img" (the real name is too long).

    After that I tried to boot into recovery but I only got the white screen with the HTC logo and on top "boot in revocery" or something like that, but I waited few minutes, it didn't changed and it didn't booted into recovery.

    So I turned of my phone, turned it back again into hboot, then fastboot, erased cache again, flashed stock recovery and went to boot into stock recovery. But all I got there is a totally black screen and it was black for minutes, so I went to shut down my phone again but suddenly my back and home key went on and I got a picture on my display, it was like an HTC but with a red triangle.

    After that it booted normally to my homescreen, now my phone is on and I connected it my charger because I'm running out of battery.

    For now we have some progress, let wait for the battery to charge up so I can continue to boot into recovery.
    Ohhh man, it seems like partition table is corrupted ;/
    Charge your battery, then lock your bootloader, next flash entire RUU,
    I'd recommend using Superuser and CWM rather than SuperSU & TWRP if you like root & custom recovery.
    Personally I had always problem with TWRP, SuperSU mostly the time did not work properly for me.