Database Develop

[Q]M7_u wont boot

Hello,
I have a m7_u that wont boot up, I tried few custom roms by sideload, and aroma backups but nothing helped. every thing goes fine but after few min on the first lockscreen it reboots.
any thing I can try?
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: **************
(bootloader) imei: **************
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3648mV
(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!

deadwolf666 said:
Hello,
I have a m7_u that wont boot up, I tried few custom roms by sideload, and aroma backups but nothing helped. every thing goes fine but after few min on the first lockscreen it reboots.
any thing I can try?
(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.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__K18
(bootloader) battery-status: good
(bootloader) battery-voltage: 3648mV
(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!
Click to expand...
Click to collapse
Remove the s/n and imei please!!!
What Rom are you running at the minute? When installing the Rom did it say it was complete and did you do a full wipe?
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
stovie_steve said:
Remove the s/n and imei please!!!
What Rom are you running at the minute? When installing the Rom did it say it was complete and did you do a full wipe?
Click to expand...
Click to collapse
Also what is the status of your bootloader - locked or unlocked? And have you installed any custom firmware?

stovie_steve said:
Remove the s/n and imei please!!!
What Rom are you running at the minute? When installing the Rom did it say it was complete and did you do a full wipe?
---------- Post added at 12:57 PM ---------- Previous post was at 12:56 PM ----------
Also what is the status of your bootloader - locked or unlocked? And have you installed any custom firmware?
Click to expand...
Click to collapse
At the moment I flashed Guru_Reset_M7_3.62.401.1.zip with no root, It was complete successfully and I fully wiped. tried to boot directly after flash also after installing stock recovery )from the zip file) and locking the bootloader.

deadwolf666 said:
At the moment I flashed Guru_Reset_M7_3.62.401.1.zip with no root, It was complete successfully and I fully wiped. tried to boot directly after flash also after installing stock recovery )from the zip file) and locking the bootloader.
Click to expand...
Click to collapse
Try the 2.24.401.8 guru reset - I'm wondering if that one you flashed is for the latest firmware and latest hboot
Try that and see how it goes
After that I would run rumrunner for 2.24.401.8 to get s-off, remove tampered and lock the bootloader using the adb shell command then update via OTA

stovie_steve said:
Try the 2.24.401.8 guru reset - I'm wondering if that one you flashed is for the latest firmware and latest hboot
Try that and see how it goes
After that I would run rumrunner for 2.24.401.8 to get s-off, remove tampered and lock the bootloader using the adb shell command then update via OTA
Click to expand...
Click to collapse
Same after 2.24.401.8 stuck on the first lockscreen, I changed the cid to 11111111 with riff box but same result.

deadwolf666 said:
Same after 2.24.401.8 stuck on the first lockscreen, I changed the cid to 11111111 with riff box but same result.
Click to expand...
Click to collapse
Try this guide I wrote. Use the appropriate firmware. I know you are not S-OFF but try and wipe as much as possible before reinstalling everything.
Which firmware are you using ? And what ROM are you installing ?

attanasi0 said:
Try this guide I wrote. Use the appropriate firmware. I know you are not S-OFF but try and wipe as much as possible before reinstalling everything.
Which firmware are you using ? And what ROM are you installing ?
Click to expand...
Click to collapse
Cant find any firmware\RUU\Nand (Stock ot not) to match and cant get s-off. 2.24.401.8 wont work and net next one is 3.XX...\
Also I can erase only the cache partition.

deadwolf666 said:
Cant find any firmware\RUU\Nand (Stock ot not) to match and cant get s-off. 2.24.401.8 wont work and net next one is 3.XX...\
Also I can erase only the cache partition.
Click to expand...
Click to collapse
We'll just try it without updating the firmware, then once you have S-OFF you'll be able to make everything work.
Just do the Reinstalling Recovery and Installing Custom ROM portion of the guide.

attanasi0 said:
We'll just try it without updating the firmware, then once you have S-OFF you'll be able to make everything work.
Just do the Reinstalling Recovery and Installing Custom ROM portion of the guide.
Click to expand...
Click to collapse
No matter what I try to install I cant get pass the lock screen, the phone just reboots (also after minute)

deadwolf666 said:
Same after 2.24.401.8 stuck on the first lockscreen, I changed the cid to 11111111 with riff box but same result.
Click to expand...
Click to collapse
deadwolf666 said:
Cant find any firmware\RUU\Nand (Stock ot not) to match and cant get s-off. 2.24.401.8 wont work and net next one is 3.XX...\
Also I can erase only the cache partition.
Click to expand...
Click to collapse
1- How did you chance CID if you're not S-Off
2- rumrunner should work to get s-off for you (provided u are on a 2.24.401.x rom and rooted), it did for two others with HTC__K18 and 2.24 ROM/firmware

nkk71 said:
1- How did you chance CID if you're not S-Off
2- rumrunner should work to get s-off for you (provided u are on a 2.24.401.x rom and rooted), it did for two others with HTC__K18 and 2.24 ROM/firmware
Click to expand...
Click to collapse
1- Jtag with riff box..
2- Cant run any Soff method if the wont boot normally, It wont get to the main screen so I cant debug also it wont stay on for more then 1 min or so

deadwolf666 said:
No matter what I try to install I cant get pass the lock screen, the phone just reboots (also after minute)
Click to expand...
Click to collapse
You have to be on the white Fastboot screen. If that doesn't load it doesn't look good but it did since you said you were able to erase cache.
So go into Fastboot and do this :
Download this
Hold the Volume-Down button
Hold the Power button for around 10 seconds
Release the Power button (but keep Volume-Down pressed)
You should see something similar to this :
{
"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"
}
Using the Volume buttons and the Power button, select Fastboot and make sur FASTBOOT USB shows up (like on the picture)
To make sure fastboot is properly connected, use
Code:
fastboot devices
If the results show up as positive, then use
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]
Using the Volume buttons, select Bootloader and then select Recovery.
Select the option "Wipe data/factory reset" (You will loose everything not previously backed up outside the phone.)
Select "Wipe Cache partition"
Select "Advanced -> Wipe Dalvik Cache"
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !

deadwolf666 said:
1- Jtag with riff box..
2- Cant run any Soff method if the wont boot normally, It wont get to the main screen so I cant debug also it wont stay on for more then 1 min or so
Click to expand...
Click to collapse
but flashing is going normal? have you tried factory reset and format/wipe /data and /data/media (/sdcard) then install? also try changing recovery, which one and version are you on?

attanasi0 said:
You have to be on the white Fastboot screen. If that doesn't load it doesn't look good but it did since you said you were able to erase cache.
So go into Fastboot and do this :
Download this
Hold the Volume-Down button
Hold the Power button for around 10 seconds
Release the Power button (but keep Volume-Down pressed)
You should see something similar to this :
Using the Volume buttons and the Power button, select Fastboot and make sur FASTBOOT USB shows up (like on the picture)
To make sure fastboot is properly connected, use
Code:
fastboot devices
If the results show up as positive, then use
Code:
fastboot flash recovery [pathonyourcomputer/recovery.img]
Using the Volume buttons, select Bootloader and then select Recovery.
Select the option "Wipe data/factory reset" (You will loose everything not previously backed up outside the phone.)
Select "Wipe Cache partition"
Select "Advanced -> Wipe Dalvik Cache"
While in recovery, type
Code:
adb push [path/rom.zip] /sdcard/rom.zip
Select "Install zip"
Select "Choose zip from sdcard"
Voila ! You should be good to go !
Click to expand...
Click to collapse
nkk71 said:
but flashing is going normal? have you tried factory reset and format/wipe /data and /data/media (/sdcard) then install? also try changing recovery, which one and version are you on?
Click to expand...
Click to collapse
All is good I did flashed custom roms and guru nands (with every recovery I found - various versions of CWM and TWRP) but after I finish the phone gets to the first lock screen before the first wizard and then it reboots

deadwolf666 said:
All is good I did flashed custom roms and guru nands (with every recovery I found - various versions of CWM and TWRP) but after I finish the phone gets to the first lock screen before the first wizard and then it reboots
Click to expand...
Click to collapse
can you check you're /data partition please:
1- reboot into recovery, and connect to PC
2- confirm it's recognized "adb devices" -> should show your serial number
3- now do the following on your pc:
adb shell
~ # mount
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
copy/paste the command prompt output (not screenshot, just copy/paste the text)

nkk71 said:
can you check you're /data partition please:
1- reboot into recovery, and connect to PC
2- confirm it's recognized "adb devices" -> should show your serial number
3- now do the following on your pc:
adb shell
~ # mount
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
copy/paste the command prompt output (not screenshot, just copy/paste the text)
Click to expand...
Click to collapse
~ # mount
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/mmcblk0p36 on /cache type ext4 (rw,nodev,noatime,nodiratime,data=orde
red)
/dev/block/mmcblk0p37 on /data type ext4 (rw,nodev,noatime,nodiratime,data=order
ed)
~ # umount /data
umount /data
~ # 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
Pass 2: Checking directory structure
Directory inode 2, block #0, offset 0: directory corrupted
Salvage? no
e2fsck: aborted
Edit: after running # e2fsck -v -f /dev/block/mmcblk0p37 and pressing Yes for some fixes
~ # 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
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
12 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: 3
150981 blocks used (2.22%)
0 bad blocks
1 large file
0 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
--------
3 files

deadwolf666 said:
~ # mount
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/mmcblk0p36 on /cache type ext4 (rw,nodev,noatime,nodiratime,data=orde
red)
/dev/block/mmcblk0p37 on /data type ext4 (rw,nodev,noatime,nodiratime,data=order
ed)
~ # umount /data
umount /data
~ # 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
Pass 2: Checking directory structure
Directory inode 2, block #0, offset 0: directory corrupted
Salvage? no
e2fsck: aborted
Edit: after running # e2fsck -v -f /dev/block/mmcblk0p37 and pressing Yes for some fixes
~ # 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
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
12 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: 3
150981 blocks used (2.22%)
0 bad blocks
1 large file
0 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
--------
3 files
Click to expand...
Click to collapse
CRAP, corrupt data partition, let's hope it's not a hardware fault, repairing is OK, and should get you going, but I would recommend a full "real" format, gimme a few minutes and I'll post back with details.....
Hit the thanks button if I've helped
---------- Post added at 07:49 PM ---------- Previous post was at 07:16 PM ----------
deadwolf666 said:
~ # 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
Pass 2: Checking directory structure
Directory inode 2, block #0, offset 0: directory corrupted
Salvage? no
Click to expand...
Click to collapse
Ok, so here's how to "real" format the data partition: (thanks to @mike1986. for his article http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html)
1- download this: http://goo.gl/pmZ9Mt
2- then push it to your phone: adb push mkfs.ext4 /tmp
3- open a shell:
adb shell
~# chmod 777 /tmp/mkfs.ext4
~# umount /data
Code:
~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37[/B]
(I have to enclose that in a code section, otherwise there's an extra space which should NOT be there)
the output should be similar to:
Code:
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: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 24 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
if all OK, you need to recreate media, so within the shell
~# mount /data
~# mkdir -p /data/media/0
exit the shell using ~# exit
finally push or sideload your rom, and flash it. if everything goes well, it will no longer reboot, if it does then it could be a hardware fault.
So far I've helped 3 people with this, two out of the three worked fine, the last one was a hardware fault.

nkk71 said:
CRAP, corrupt data partition, let's hope it's not a hardware fault, repairing is OK, and should get you going, but I would recommend a full "real" format, gimme a few minutes and I'll post back with details.....
Hit the thanks button if I've helped
---------- Post added at 07:49 PM ---------- Previous post was at 07:16 PM ----------
Ok, so here's how to "real" format the data partition: (thanks to @mike1986. for his article http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html)
1- download this: http://goo.gl/pmZ9Mt
2- then push it to your phone: adb push mkfs.ext4 /tmp
3- open a shell:
adb shell
~# chmod 777 /tmp/mkfs.ext4
~# umount /data
Code:
~# [B]/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37[/B]
(I have to enclose that in a code section, otherwise there's an extra space which should NOT be there)
the output should be similar to:
Code:
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: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 24 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
if all OK, you need to recreate media, so within the shell
~# mount /data
~# mkdir -p /data/media/0
exit the shell using ~# exit
finally push or sideload your rom, and flash it. if everything goes well, it will no longer reboot, if it does then it could be a hardware fault.
So far I've helped 3 people with this, two out of the three worked fine, the last one was a hardware fault.
Click to expand...
Click to collapse
Thanks for your help, I tried your guide but same result(restart after first screenlock) then I installed CM and I got pass the screenlock but it reboots after 2-5 minutes :\

deadwolf666 said:
Thanks for your help, I tried your guide but same result(restart after first screenlock) then I installed CM and I got pass the screenlock but it reboots after 2-5 minutes :\
Click to expand...
Click to collapse
did you format the partition as suggested? if so go back to post #16 and run e2fsck again, if it gives error again, then it's faulty hardware
The reason CM installs is because it doesnt use the /data partition, however after booting up, at some point it needs to use /data and if it's corrupt, it will reboot without any error message.
So if you did successfully format it, and e2fsck reports errors again after one or two reboots, then it's unfortunately a hardware issue.

nkk71 said:
did you format the partition as suggested? if so go back to post #16 and run e2fsck again, if it gives error again, then it's faulty hardware
The reason CM installs is because it doesnt use the /data partition, however after booting up, at some point it needs to use /data and if it's corrupt, it will reboot without any error message.
So if you did successfully format it, and e2fsck reports errors again after one or two reboots, then it's unfortunately a hardware issue.
Click to expand...
Click to collapse
Code:
~ # e2fsck -v -f /dev/block/mmcblk0p37
e2fsck -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
2147 inodes used (0.13%)
207 non-contiguous files (9.6%)
2 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2031/8
193238 blocks used (2.84%)
0 bad blocks
0 large files
1602 regular files
437 directories
0 character device files
0 block device files
0 fifos
0 links
93 symbolic links (92 fast symbolic links)
6 sockets
--------
2138 files
No errors this time, Any suggestion for a ROM that works OK on the M7_U ?
EDIT:
I Soff ed with revone and now trying this guide :
http://forum.xda-developers.com/showthread.php?t=2489914
will post soon

[Q] Phone Reboots every 2 minutes. Stuck on ARHD 31.6

Here's the output of my getvar
(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.707.1
(bootloader) version-misc: PVT SHIP S-ON
(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: 3850mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I cannot S-OFF it since I'm not on stock rom. Even if I try to it fails since the phone reboots every 2 minutes. I'm currently downloading Guru_Reset_M7_2.24.707.1.zip. And additional information, my HBOOT got upgraded from 1.44.
So my question is, will I be able to reset the RUU on this one using the file I'm still downloading? it matches the version of my getvar.
Any help is appreciated.
Thank you

bright light
try holding it under a bright light while its restarting and see if that works.
otherwise re flash your rom and make sure you do a factory reset first

pbarakhsan said:
try holding it under a bright light while its restarting and see if that works.
otherwise re flash your rom and make sure you do a factory reset first
Click to expand...
Click to collapse
That didn't help. I dont have signal, I dont have lockscreen, I can't do anything past the booting of the phone. Any ideas?

recovery mode?
can you get to the recovery mode?

pbarakhsan said:
can you get to the recovery mode?
Click to expand...
Click to collapse
Yes I can. What can I do here? I'm on S-ON. and I dont think RUU would help.

b3rx said:
Yes I can. What can I do here? I'm on S-ON. and I dont think RUU would help.
Click to expand...
Click to collapse
how long is your phone stable in recovery, more than 2 minutes? no random restarts?

nkk71 said:
how long is your phone stable in recovery, more than 2 minutes? no random restarts?
Click to expand...
Click to collapse
It never restarts whenever I'm in bootloader or recovery.. So whatever I can do with recovery I can do it.

b3rx said:
It never restarts whenever I'm in bootloader or recovery.. So whatever I can do with recovery I can do it.
Click to expand...
Click to collapse
hmm, pretty late for me, but if recovery is ok, would you mind running the following shell:
adb shell
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
Code:
~ # 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
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
39356 inodes used (2.31%)
350 non-contiguous files (0.9%)
31 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 38933/54
4696398 blocks used (68.91%)
0 bad blocks
1 large file
36560 regular files
2426 directories
0 character device files
0 block device files
0 fifos
0 links
357 symbolic links (357 fast symbolic links)
4 sockets
--------
39347 files
~ #

nkk71 said:
hmm, pretty late for me, but if recovery is ok, would you mind running the following shell:
adb shell
~ # umount /data
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
Code:
~ # 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
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
39356 inodes used (2.31%)
350 non-contiguous files (0.9%)
31 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 38933/54
4696398 blocks used (68.91%)
0 bad blocks
1 large file
36560 regular files
2426 directories
0 character device files
0 block device files
0 fifos
0 links
357 symbolic links (357 fast symbolic links)
4 sockets
--------
39347 files
~ #
Click to expand...
Click to collapse
Here's my output
Code:
~ # 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
979 inodes used (0.06%)
59 non-contiguous files (6.0%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 684
158589 blocks used (2.33%)
0 bad blocks
1 large file
190 regular files
493 directories
0 character device files
0 block device files
0 fifos
0 links
281 symbolic links (281 fast symbolic links)
6 sockets
--------
970 files

b3rx said:
Here's my output
Code:
~ # 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
979 inodes used (0.06%)
59 non-contiguous files (6.0%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 684
158589 blocks used (2.33%)
0 bad blocks
1 large file
190 regular files
493 directories
0 character device files
0 block device files
0 fifos
0 links
281 symbolic links (281 fast symbolic links)
6 sockets
--------
970 files
Click to expand...
Click to collapse
looks good enough, go ahead with Guru Reset, (ROOTed), and get S-Off using rumrunner (IMHO)

nkk71 said:
looks good enough, go ahead with Guru Reset, (ROOTed), and get S-Off using rumrunner (IMHO)
Click to expand...
Click to collapse
I went for Guru Reset. but then again still the same. it boots, I get the time and battery life indication, but I can't go to notification settings, no signal, no icons, no home screen, and after a minute or two, it reboots. same cycle.

I can go to RUU mode, but I can't find any RUU zip or exe for my 2.24.707.1.

tried aosp yet?
b3rx said:
I can go to RUU mode, but I can't find any RUU zip or exe for my 2.24.707.1.
Click to expand...
Click to collapse
that is weird. try flashing an aosp rom to see if it works there

pbarakhsan said:
that is weird. try flashing an aosp rom to see if it works there
Click to expand...
Click to collapse
I've almost tried any rom there is for HTC One. and the result is the same, it doesnt have GSM signal, can't do much on it really. I think RUU is the way, but I can't since I'm not on S-OFF. Is there an RUU.exe for 2.24.707.1?

try this
b3rx said:
I've almost tried any rom there is for HTC One. and the result is the same, it doesnt have GSM signal, can't do much on it really. I think RUU is the way, but I can't since I'm not on S-OFF. Is there an RUU.exe for 2.24.707.1?
Click to expand...
Click to collapse
try his rom and tell me what happens
http://forum.xda-developers.com/showthread.php?t=2383508

pbarakhsan said:
try his rom and tell me what happens
http://forum.xda-developers.com/showthread.php?t=2383508
Click to expand...
Click to collapse
I've tried that as well. same difference. same result. keeps on rebooting after awhile.

b3rx said:
I've tried that as well. same difference. same result. keeps on rebooting after awhile.
Click to expand...
Click to collapse
im running out of ideas then

b3rx said:
I can go to RUU mode, but I can't find any RUU zip or exe for my 2.24.707.1.
Click to expand...
Click to collapse
b3rx said:
I've tried that as well. same difference. same result. keeps on rebooting after awhile.
Click to expand...
Click to collapse
hmmm, doesnt sound nice
too late for me to do this now, but I'll check in tomorrow and we'll take a closer look at your phones partitions.

nkk71 said:
hmmm, doesnt sound nice
too late for me to do this now, but I'll check in tomorrow and we'll take a closer look at your phones partitions.
Click to expand...
Click to collapse
Maybe this will not help you, but having the same problem as you, I used Adb push, to get a different rom (i installed hd revolution with android 4.3), then did soff as mentioned here earlier and now I installed hd revolution 5.1 and all works fine.
Thanks for the comments. Really helped me

nkk71 said:
hmmm, doesnt sound nice
too late for me to do this now, but I'll check in tomorrow and we'll take a closer look at your phones partitions.
Click to expand...
Click to collapse
I'm now ready for another set of debugging sessions. any other ideas?

[Q] M7UL Baseband & IMEI Unknown - Partitions?

Please help and thank you in advance.
I'll try to make this as easy to read as possible.
Device (originally)
- M7_UL
- MID: PN0714000
- CID: HTC__044
- HBOOT: 1.54
Main problem:
- Baseband & IMEI shows as "unknown". However, values are still available through fastboot getvar all.
Suspected cause:
- Official OTA
Tried mixture of nearly everything:
- HBOOT 1.44, 1.54, 1.55, 1.56
- RUU zip, RUU exe, custom ROMs
- Sense or Google Editions
- Bootloader locked, unlocked, relocked
- s-on, s-off (rumrunner)
Results:
- Some ROMs bootable and usable except for baseband unknown = no cell signal. WiFi ok. (especially Google Edition ROMs)
- Some ROMs just keeps restarting (especially Sense ROMs)
- Some ROMs reach the lock screen, but once unlock only shows white screen with big HTC logo. Then auto restarts. (especially Sense ROMs)
- Some ROMs stops restarting when back to s-on. But still baseband unknown.
Please advice:
Anyone have suggestions on how to fix this?
I read somewhere that this could be a problem with partitions.
But I couldn't find any more info on how to check/fix partition problem.
==========================================
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: <removed>
(bootloader) imei: <removed>
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3869mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.066s

sotplug said:
Please help and thank you in advance.
Click to expand...
Click to collapse
Nicely written up :good: (next time also include the getvar all output except IMEI and s/n; xxxx at least part of them out)
Have you tried a different radio, check here: http://forum.xda-developers.com/showthread.php?t=2419699
(flashable through custom recovery)

nkk71 said:
Nicely written up :good: (next time also include the getvar all output except IMEI and s/n; xxxx at least part of them out)
Have you tried a different radio, check here: http://forum.xda-developers.com/showthread.php?t=2419699
(flashable through custom recovery)
Click to expand...
Click to collapse
Will try the radios and report back (maybe tomorrow).
By the way, first post edited to add the fastboot getvar info.
Thank you.

nkk71 said:
Nicely written up :good: (next time also include the getvar all output except IMEI and s/n; xxxx at least part of them out)
Have you tried a different radio, check here: http://forum.xda-developers.com/showthread.php?t=2419699
(flashable through custom recovery)
Click to expand...
Click to collapse
sotplug said:
Will try the radios and report back (maybe tomorrow).
By the way, first post edited to add the fastboot getvar info.
Thank you.
Click to expand...
Click to collapse
Tried every radio in the post and baseband is still unknown.

sotplug said:
Tried every radio in the post and baseband is still unknown.
Click to expand...
Click to collapse
You Try flashing a RUU?

sotplug said:
Tried every radio in the post and baseband is still unknown.
Click to expand...
Click to collapse
Yup. Didn't work as well.
Sent from my HTC One using xda app-developers app

Hi nkk71. I followed your instructions from this post for checking partitions and this is the result.
GE firmware and ROM from this post.
Code:
[B]adb shell[/B]
[B]~ # mount[/B]
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)
/dev/block/mmcblk0p36 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p37 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
[B]~# umount /data[/B]
[B]~# e2fsck -n -v -f /dev/block/mmcblk0p37[/B]
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?
[B]~# e2fsck -n -v -f /dev/block/mmcblk0p35[/B]
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
1893 inodes used (1.59%)
12 non-contiguous files (0.6%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1602
202103 blocks used (42.54%)
0 bad blocks
0 large files
1537 regular files
64 directories
0 character device files
0 block device files
0 fifos
0 links
283 symbolic links (283 fast symbolic links)
0 sockets
--------
1884 files
Definitely not the expected result.
I think I'll try going back to as close as stock as possible (ROM and firmware) and run this check again.

sotplug said:
Hi nkk71. I followed your instructions from this post for checking partitions and this is the result.
GE firmware and ROM from this post.
Code:
[B]adb shell[/B]
[B]~ # mount[/B]
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)
[B][COLOR="Blue"]/dev/block/mmcblk0p36 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p37 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
[/COLOR][/B]
[B]~# umount /data[/B]
[B]~# e2fsck -n -v -f /dev/block/mmcblk0p37[/B]
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?
[B]~# e2fsck -n -v -f /dev/block/mmcblk0p35[/B]
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
1893 inodes used (1.59%)
12 non-contiguous files (0.6%)
1 non-contiguous directory (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 1602
202103 blocks used (42.54%)
0 bad blocks
0 large files
1537 regular files
64 directories
0 character device files
0 block device files
0 fifos
0 links
283 symbolic links (283 fast symbolic links)
0 sockets
--------
1884 files
Definitely not the expected result.
I think I'll try going back to as close as stock as possible (ROM and firmware) and run this check again.
Click to expand...
Click to collapse
I don't think it's a partition issue, but you've only checked /system you can still check /data, but you need to umount it first:
~# umount /data
~# umount /sdcard
then you can run ~# e2fsck -n -v -f /dev/block/mmcblk0p37

nkk71 said:
I don't think it's a partition issue, but you've only checked /system you can still check /data, but you need to umount it first:
~# umount /data
~# umount /sdcard
then you can run ~# e2fsck -n -v -f /dev/block/mmcblk0p37
Click to expand...
Click to collapse
I see. Need to unmount sdcard as well.
Now it does give some output without error:
Code:
[B]adb shell[/B]
[B]umount /data[/B]
[B]umount /sdcard[/B]
[B]e2fsck -n -v -f /dev/block/mmcblk0p37[/B]
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
5279 inodes used (0.31%)
245 non-contiguous files (4.6%)
4 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 5118/15
1118049 blocks used (16.40%)
0 bad blocks
1 large file
4398 regular files
734 directories
0 character device files
0 block device files
0 fifos
0 links
132 symbolic links (132 fast symbolic links)
6 sockets
--------
5270 files
If it isn't partition, then I'm really lost.
And there do seems to be quite a few users with similar issues (constant auto reboot).
By the way, for my case, Google roms seems to be better. Sense roms all auto reboot.

sotplug said:
I see. Need to unmount sdcard as well.
Now it does give some output without error:
If it isn't partition, then I'm really lost.
And there do seems to be quite a few users with similar issues (constant auto reboot).
Click to expand...
Click to collapse
so even after a RUU, (no updates) it still doesn't hold? which RUU are you using, link please

nkk71 said:
so even after a RUU, (no updates) it still doesn't hold? which RUU are you using, link please
Click to expand...
Click to collapse
Got my RUU from here:
ruu_m7_ul_jb_50_htc_asia_wwe_1-29-707-3_r_radio_4a-14-3250-13_10-33-1150-01_release_311678_signed-exe/
After lock screen, no Sense UI.
Just white HTC logo screen.
Then auto restarts every 1-2 mins.
Then using stock recovery, apply OTA:
ota_m7_ul_jb_50_htc_asia_wwe_1-29-707-16_r-1-29-707-3_r_release_318610_signedkaytj0xrerk0cnd9-zip/
Same result.
Not easy to find a x.xx.707.x RUU.
However, this is a hboot 1.44 RUU.
My phone started out originally as hboot 1.54.
Could this be a problem?
===== Update =====
adb shell
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)
/dev/block/mmcblk0p36 on /cache type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p37 on /data type ext4 (rw,seclabel,relatime,data=ordered)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,seclabel,relatime,data=ordered)
umount /data
umount /sdcard
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
644 inodes used (0.04%)
4 non-contiguous files (0.6%)
1 non-contiguous directory (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 634
151815 blocks used (2.23%)
0 bad blocks
1 large file
40 regular files
593 directories
0 character device files
0 block device files
0 fifos
0 links
1 symbolic link (1 fast symbolic link)
1 socket
--------
635 files
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 **********
2367 inodes used (2.06%)
4 non-contiguous files (0.2%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2298
370293 blocks used (80.72%)
0 bad blocks
0 large files
2213 regular files
85 directories
0 character device files
0 block device files
0 fifos
0 links
60 symbolic links (60 fast symbolic links)
0 sockets
--------
2358 files

sotplug said:
Pass 3: Checking directory connectivity
/lost+found not found. Create? no
/dev/block/mmcblk0p35: ********** WARNING: Filesystem still has errors **********
Click to expand...
Click to collapse
Minor error, once the ROM boots up it should recreate lost&found when needed.
sotplug said:
Not easy to find a x.xx.707.x RUU.
However, this is a hboot 1.44 RUU.
My phone started out originally as hboot 1.54.
Could this be a problem?
Click to expand...
Click to collapse
No, shouldnt be a problem.
sotplug said:
Got my RUU from here:
ruu_m7_ul_jb_50_htc_asia_wwe_1-29-707-3_r_radio_4a-14-3250-13_10-33-1150-01_release_311678_signed-exe/
After lock screen, no Sense UI.
Just white HTC logo screen.
Then auto restarts every 1-2 mins.
Click to expand...
Click to collapse
starting to sound like a hardware issue.
1- try removing the SIM card
2- set CID back to original
3- run the RUU (you may need to downgrade hboot separately first)
once the RUU is successfully applied, go to bootloader and check "fastboot getvar all", that baseband and firmware versions are correct.

nkk71 said:
Minor error, once the ROM boots up it should recreate lost&found when needed.
Click to expand...
Click to collapse
I did let it boot/auto-reboot a few times until the HTC lock screen.
So it seems that the boots are incomplete.
nkk71 said:
starting to sound like a hardware issue.
1- try removing the SIM card
2- set CID back to original
3- run the RUU (you may need to downgrade hboot separately first)
once the RUU is successfully applied, go to bootloader and check "fastboot getvar all", that baseband and firmware versions are correct.
Click to expand...
Click to collapse
Actually, this is exactly what I did.
I even used stock hboot and recovery from the RUU (decrypted using ruuveal)
Anyway, will try a few times again with different RUUs.
If still unsuccessful, maybe I should just bring back for warranty service.
And thanks a lot for trying to help. Really appreciate it.

sotplug said:
I did let it boot/auto-reboot a few times until the HTC lock screen.
So it seems that the boots are incomplete.
Actually, this is exactly what I did.
I even used stock hboot and recovery from the RUU (decrypted using ruuveal)
Anyway, will try a few times again with different RUUs.
If still unsuccessful, maybe I should just bring back for warranty service.
And thanks a lot for trying to help. Really appreciate it.
Click to expand...
Click to collapse
no problem, probably best to take it to service, we could try formatting the partitions (only data and system, not the raw ones), but i wouldnt hold my breath that it would help.

Running into the same problems
I have the same problems. I was about to try S-Off and RUU, but I just read here that it doesn't seem to work.
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: <removed>
(bootloader) imei: <removed>
(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: 4276mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) gencheckpt: 0
As you see, I'm still on HBOOT 1.44. I never installed another one.
(it started with random auto-reboots, they got more frequent and regular, so I re-flashed different roms and restored a backup with TWRP. The baseband started to be unknown in every rom after the restore or after flashing CM)
Did you find a solution or send it to service ? Successfully ?
What should I do ? Do I have any chance with RUU and going back to stock ?
Or should I just send it to service and hope ?
Thanks !

i have the same problem , any idea ?!
please help us

anyone , help us , heeeelp

Has anyone made progress on this issue? I have been unable to find a solution.

Same issue here..
I tried sky-fall ROM recently and it keep the device without restarting few days..
Is this hardware issue?

Same issue here..
I tried few roms , all fails..
After trying few radios it works..
But again i lost it..
Here some points i notices.
when phone is cold flashing radio is work..
Flashing radio with philz recovery only works ( TWRP didnt work )
I got a full nandroid backup via TWRP when everything works. But when i restore it , it did not work,
any suggestions...

[Q] E: Unable to Mount '/System

My m7 had some problem yesterday and I decided to dirty flash my ROM again to see if it can fix it. But then when I rebooted into TWRP recovery (v2.8.1.0) and flashing, the aroma installer stuck at "formatting system" and I rebooted again into TWRP it has "E: Unable to Mount '/System" in the log
I tried to google it but couldn't find anyway to fix it.
Could anyone please help?:crying:
[Fixed by using TWRP 2.6.3.3]

d.kuyt said:
My m7 had some problem yesterday and I decided to dirty flash my ROM again to see if it can fix it. But then when I rebooted into TWRP recovery (v2.8.1.0) and flashing, the aroma installer stuck at "formatting system" and I rebooted again into TWRP it has "E: Unable to Mount '/System" in the log
I tried to google it but couldn't find anyway to fix it.
Could anyone please help?:crying:
Click to expand...
Click to collapse
did you try factory reset or format data in TWRP ?

d.kuyt said:
My m7 had some problem yesterday and I decided to dirty flash my ROM again to see if it can fix it. But then when I rebooted into TWRP recovery (v2.8.1.0) and flashing, the aroma installer stuck at "formatting system" and I rebooted again into TWRP it has "E: Unable to Mount '/System" in the log
I tried to google it but couldn't find anyway to fix it.
Could anyone please help?:crying:
Click to expand...
Click to collapse
Boot your device to TWRP Recovery. Select "Mounts" and uncheck/unmount System, Data and cache.
Now in the adb command window type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p37
exit
These are M7_UL partitions if you have Sprint or Verizon let me know.
Then after checking the md5 of your Rom try to flash it again

Tried, nothing changed, the code is as follow:
C:\ADB>adb shell
~ # e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p35
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/mmcblk0p35
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 -fvy dev/block/mmcblk0p36
e2fsck -fvy 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
19 inodes used (0.05%)
1 non-contiguous file (5.3%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 10/1
7454 blocks used (4.55%)
0 bad blocks
0 large files
6 regular files
4 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
10 files
~ # e2fsck -fvy dev/block/mmcblk0p37
e2fsck -fvy 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
54505 inodes used (3.20%)
4542 non-contiguous files (8.3%)
67 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 53704/489/2
5511071 blocks used (80.86%)
0 bad blocks
1 large file
49281 regular files
4903 directories
0 character device files
0 block device files
0 fifos
0 links
303 symbolic links (293 fast symbolic links)
9 sockets
--------
54496 files
~ # exit
exit
C:\ADB>

d.kuyt said:
Tried, nothing changed, the code is as follow:
C:\ADB>adb shell
~ # [6ne2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p35
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/mmcblk0p35
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>
~ # [6ne2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy 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
19 inodes used (0.05%)
1 non-contiguous file (5.3%)
0 non-contiguous directories (0.0%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 10/1
7454 blocks used (4.55%)
0 bad blocks
0 large files
6 regular files
4 directories
0 character device files
0 block device files
0 fifos
0 links
0 symbolic links (0 fast symbolic links)
0 sockets
--------
10 files
~ # [6ne2fsck -fvy dev/block/mmcblk0p37
e2fsck -fvy 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
54505 inodes used (3.20%)
4542 non-contiguous files (8.3%)
67 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 53704/489/2
5511071 blocks used (80.86%)
0 bad blocks
1 large file
49281 regular files
4903 directories
0 character device files
0 block device files
0 fifos
0 links
303 symbolic links (293 fast symbolic links)
9 sockets
--------
54496 files
~ # [6nexit
exit
C:\ADB>
Click to expand...
Click to collapse
Still can't mount system? Does it only show this when you try to flash the Rom? Can you please post the output of
Code:
fastboot getvar all
Please remove serial and imei numbers before posting.
What is the Rom your trying to flash. A link would be great

Danny201281 said:
Boot your device to TWRP Recovery. Select "Mounts" and uncheck/unmount System, Data and cache.
Now in the adb command window type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p37
exit
These are M7_UL partitions if you have Sprint or Verizon let me know.
Then after checking the md5 of your Rom try to flash it again
Click to expand...
Click to collapse
Danny201281 said:
Still can't mount system? Does it only show this when you try to flash the Rom? Can you please post the output of
Code:
fastboot getvar all
Please remove serial and imei numbers before posting.
What is the Rom your trying to flash. A link would be great
Click to expand...
Click to collapse
The "fastboot getvar all"
C:\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---
(bootloader) imei: ---
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
C:\ADB>
and the ROM I want to flash is ViperOne 7.0.1 (I successfully flashed it before, same zip file)

d.kuyt said:
The "fastboot getvar all"
C:\ADB>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.708.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ---
(bootloader) imei: ---
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__622
(bootloader) battery-status: good
(bootloader) battery-voltage: 4321mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.047s
C:\ADB>
and the ROM I want to flash is ViperOne 7.0.1 (I successfully flashed it before, same zip file)
Click to expand...
Click to collapse
Try a full format but it will wipe the device completely. You'll need to push a Rom with adb to install afterwards.
In TWRP go to "Wipe" and select "Format Data" you will be prompted to type "yes" to confirm. After its done Reboot to recovery (the reboot is important don't skip it.
Then use adb to push or sideload your Rom.

Danny201281 said:
Try a full format but it will wipe the device completely. You'll need to push a Rom with adb to install afterwards.
In TWRP go to "Wipe" and select "Format Data" you will be prompted to type "yes" to confirm. After its done Reboot to recovery (the reboot is important don't skip it.
Then use adb to push or sideload your Rom.
Click to expand...
Click to collapse
I will try it later (I have other things to do now)
Thanks [emoji6]
Sent from my HTC One_M8

You could just install 2.6.3.3 TWRP recovery and install it.....
That seems to solve most problems....

ss4adib said:
You could just install 2.6.3.3 TWRP recovery and install it.....
That seems to solve most problems....
Click to expand...
Click to collapse
Thanks, using TWRP 2.6.3.3 fixed my problem
Sent from my HTC One_M8

You're welcome dude

I'm going to test this later. Thanks.

[SOLVED] *******PLEASE HELP ME!!!!!!!!!! - seems like i've got a permanent soft brick

Hello everybody im wondering if someone can help me
im trying to reinstall a rom to my HTC One m7
But everytime i try to use fastboot or RUU exe to unbrick it i get stuck at the signature verification part.
my phone info is as follows (bootloader):
*** TAMPERED ***
*** RELOCKED ***
*** Security Warning ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.13.3231.27
OpenDSP-v26.120.274.0202
eMMC-boot
Mar 7 2013,23:09:00-1
IF I TYPE IN FASTBOOT: fastboot getver version-main I receive: 1.28.61.7
My CID: ORANG001
TWRP recovery version: 2.8.7.0
I am able to unlock and relock at my own will using fastboot to relock and using HTC-Dev toekn .bin file to unlock via fastboot.
I am able install both TWRP and CWM recoveries... but when I enter recovery with (unlocked device) neither can mount the sdcard so i can copy a rom to the phone to install.
I am abdle to use adb to copy files to my internal storage but am not able to use the abd sideload as the TWRP recovery cannot seem to mount the sdcar or system or data
The phone is completely wiped and I dont know what else to do. I understand that if i was able to gain S-OFF then the signature verification would pass but is there a way to do this when I cant do anything but get into my bootloader and recovery?
Maybe its down to the RUU exe and zip files im using i dont know??? but it seems very hard to find a link to one that is for my phone.
any help would be very appreciated and links also please
HELP ME
SOLUTION
Quote:
Originally Posted by nkk71
Hey @basv81, I'm leaving this for you cause I'm probably not going to be online tonight:
I don't think you will be able to do this. TWRP and CWM, although they say "format", what it actually does is only wipe the contents of the partition. Since TWRP is unable to mount it, means it's really corrupt. not only /data/media (internal storage), but the whole /data partition.
If you read through this post: http://android-revolution-hd.blogspo...a-htc-one.html
You can clearly see it pretty much applies to your case: "E:Unable to mount '/data'" and e2fsck reporting error.
I would follow the repair instructions from that article, basically (while in recovery):
download this: http://goo.gl/pmZ9Mt, 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,^ext ra_isize -m 0 /dev/block/mmcblk0p37
that last command is quite long and not the easiest , so I recommend you type is in very slowly, and be particularly careful with extra or missing spaces, check the link above to make sure it's correct. (it didn't work for the other guy I mentioned cause I told him to copy/paste it, but that introduced an extra space which we both overlooked; so we had to solve it using e2fsck, which in your case is not able to fix the filesystem ).
Once formatting is complete, you need to recreate the /data/media folder, so while still in the adb shell:
mount /data
mkdir -p /data/media/0
then you can use adb push or sideload to get your phone working.
Good luck, and post back with hopefully positive results
Checked if my device was connected properly:
Code:
C:\Repair_HTC_One_m7ul>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
H*********** recovery
As that was the case I continued. First I read the topic nkk71 suggested: http://android-revolution-hd.blogspo...a-htc-one.html
First of all I pushed the downloaded mkfs.ext4 file to my device:
Code:
C:\Repair_HTC_One_m7ul>adb push mkfs.ext4 /tmp
3255 KB/s (3537143 bytes in 1.061s)
After that, I changed the file's permissions and executed it with the long command:
Code:
C:\Repair_HTC_One_m7ul>adb shell
~ # ←[6nchmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # ←[6n/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_isize -m 0 /dev/block/mmcblk0p37
/tmp/mkfs.ext4 -b 4096 -O ^huge_file,^dir_nlink,^ext_attr,^resize_inode,^extra_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: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 24 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
I mounted the /data folder and made directory /data/media/0. After that I quitted the shell.
Code:
~ # ←[6nmount /data
mount /data
~ # ←[6nmkdir -p /data/media/0
mkdir -p /data/media/0
~ # ←[6nexit
exit
I pushed the latest stable Cyanogenmod ROM to my device, including the corresponding Google Apps (so my android keyboard keeps working when I install it):
Code:
C:\Repair_HTC_One_m7ul>adb push cm-10.1.3-m7ul.zip /data/media/0
3284 KB/s (187979506 bytes in 55.886s)
C:\Repair_HTC_One_m7ul>adb push gapps-jb-20130812-signed.zip /data/media/0
3516 KB/s (100751136 bytes in 27.981s)
In twrp:
install
navigated to CM10.1.3 zip-file
installed CM10.1.3 zip-file
Rebooted to bootloader, so I can flash the boot.img again (AFTER installing CM)
Code:
C:\Repair_HTC_One_m7ul>fastboot flash boot boot.img
sending 'boot' (5558 KB)...
OKAY [ 0.993s]
writing 'boot'...
OKAY [ 0.514s]
finished. total time: 1.510s
Rebooted system to see if CM10.1.3 would start for first run. It did, YAY, so I rebooted to recovery again to install Google apps.
Entered recovery (twrp):
install
navigated to gapps zip-file
installed gapps zip-file
wiped cache/dalvik
Many, many thanks to @nkk71 for all support you've given. Without you I'd still be hopelessy stuck!

i rule123 said:
Many, many thanks to @nkk71 for all support you've given. Without you I'd still be hopelessy stuck!
Click to expand...
Click to collapse
glad you got it sorted, for future reference or anybody else that happens to check here, the "manual" formatting method is not really necessary, you can do it in TWRP
TWRP -> Wipe -> Format data -> type 'yes' (this will do a real format of your entire data partition)
I've mentioned it in the FAQ Sticky in particular on page 3
But happy everything worked out for you :good::good:

The links are dead. Could someone please update? I'm having the same issue and would like to use this solution.