[One (M7) Q&A, Help & Troubleshooting] i rule123:
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 :D

Quote:

Originally Posted by nkk71

Hey [MENTION=5527318]basv81[/MENTION], 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 [MENTION=2605798]nkk71[/MENTION] for all support you've given. Without you I'd still be hopelessy stuck!