How to: Fix a random reboots on the HTC One M8

Some time ago I described a method to format the /data partition on the HTC One (M7) - How to: Fix a corrupted DATA partition on the HTC One. This method is suitable for more HTC devices (all with EXT4 support) and with the mkfs.ext4 tool you can format system and cache partitions as well. All you need to know is the proper /dev/block/mmcblk0pXY number of the partition you want to format.

However, formatting the partition always means that your data will be gone. On the HTC One M8 I noticed a problem, most likely caused by the wp_mod.ko module (module to disable system R/W protection). When the module is loaded too late and anything ever gets changed before the module is loaded the file-structure of the /data partition might (and probably will) get corrupted. As a result your device will reboot each time you'll try to make and change on the /system partition (even if mounted as RW). So removing, copying, moving, re-naming or editing any file on a system partition will result with the following message in the kernel log (last_kmsg.txt):

Formatting the /data partition is not the best idea for some and it's not needed in most cases.

Repair Process

1. Download this mini-sdk package and extract it to c:\mini-sdk
2. Download this fsck.ext4 binary and put it into c:\mini-sdk
3. Connect your device to the PC
4. Boot your device in recovery mode
5. Open a command prompt on the PC (cmd.exe), type and confirm each command with ENTER:
6. cd /d c:\mini-sdk
7. adb push fsck.ext4 /tmp
8. adb shell
9. chmod 777 /tmp/fsck.ext4
10. /tmp/fsck.ext4 -fn /dev/block/mmcblk0p47

This will fix your /data partition and you should see the following output (numbers in the last line will be different in each case):

e2fsck 1.42.9 (28-Dec-2013)
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
/dev/block/mmcblk0p47: 19050/712704 files (2.7% non-contiguous), 2320338/2850816 blocks

Your /data partition is now fixed and you should no longer experience random reboots problem on your device (assuming that the corrupted /data partition was the source of the problem). Keep in mind that the fsck.ext4 -fn command can be used to check other EXT4 partitions on any device that has EXT4 file-system structure. All you need to know is the partition name or block number.

Do you have any questions or comments? Feel free to share! Also, if you like this article, please use media sharing buttons (Twitter, G+, Facebook) below this post!

For latest news follow Android Revolution HD on popular social platforms:

My fight with Samsung - part 1.

It is a common knowledge that the theory is one thing and the practice is sometimes completely different. Today I've felt on my own skin how Samsung is trying to fool its customers. Keep on reading and please share this on any of your social network.

Some time ago I bought a Samsung tablet – Galaxy Note 10.1 (2014 Edition). Few days ago I realized that the S-Pen stylus is no longer working. The touch screen simply didn't react when I was trying to write anything on the front panel. So I took the device to the authorized Samsung service in Krakow - "W&K Wlodarski Łukasz". 

How much I was surprised when I received a text message after 20 minutes that my device is ready to be picked up. When I came back I was told that the warranty is voided because of "unauthorized software integration". Let's now point out some important technical details.

1. In ODIN mode: CURRENT BINARY: Samsung Official
2. In ODIN mode: SYSTEM STATUS: Official
3. Current OS: official P605XXUCNF2
4. Kernel: official
5. Recovery: official
6. ROOTED: no!

So... what the f... hell? Where is the "unauthorized software integration"?

I asked the technician for some more details. He wasn't able to answer any of my questions. He wasn't able to show me this "software integration" and what would that be.

Let's now focus on the legal part. Warranty terms attached to my device do state about software modifications, but it's a crucial ability to read it with understanding and a proper interpretation.

What does it mean? The key word in this part is "due to". So basically, there has to be a causal link (a cause ---> effect relationship). So if the modified software caused the failure, the warranty does not cover it. But if the modified software has no relation with the failure, then YOU MUST FIX IT, DEAR SAMSUNG!

The other very important thing is the burden of proof. The burden of proof is the imperative on a party in a trial to produce the evidence that will shift the conclusion away from the default position to one's own position. In simply words that means: if you say something - prove it! It is not MY obligation to prove that I haven't modified the software. If you, dear Samsung claim that my warranty is voided because of software modification, you need to prove this software modification.

To sum up this first part:

1. Samsung service didn't prove their statement that I made an unauthorized software integration.
2. Samsung service didn't demonstrate a causal relationship between the unauthorized software integration (if there was one) and the device failure.
3. Samsung service refused to fix my device and the worker said "Sir you have no chance, just give up and leave".

Few minutes ago I wrote a long e-mail to Samsung support centre, explaining the whole situation. What comes next? Let's wait for a part two...

Please share it.

Do you have any questions or comments? Feel free to share! Also, if you like this article, please use media sharing buttons (Twitter, G+, Facebook) below this post!

For latest news follow Android Revolution HD on popular social platforms: