[Q] Random Shutdowns. Reverts to previous phone state on reboot.

fromtheaudible · Jan 28, 2014

My AT&T HTC One (32 GB) that I bought day one keeps rebooting randomly.

From day one, I rooted, unlocked my bootloader, flashed CWM, and installed Android Revolution.
I've since updated up to AR 31.0 without any problem, and have been running that version for quite a few months.
I have never had any problems with Mike's roms on any of my other phones.

Recently, it reboots completely, even when I'm not touching it.
Once booted up, it will revert to a previous state. The same apps will begin to update, I will be notified of the same emails, voicemails, texts, etc.
If I touch it while all this happens, it will reboot again, and do all of the same things.
If I leave it alone until all of this occurs, I might have some luck using the phone in a stable state.

I've not installed anything new recently.
I run Seeder, a few Xposed tweaks, a couple of Sense Toolbox tweaks, and Tasker at root level, but all of these things have been running simultaneously without a problem for months.
This just started happening out of no where.

Again, running AR 31.0, Android 4.3, Sense 5.5. Random reboots.
Any ideas guys?

kamilmirza · Jan 28, 2014

does this happens on any other ROM?

fromtheaudible · Jan 28, 2014

kamilmirza said:
does this happens on any other ROM?

Nope. Never had this happen before. I just wonder how something could have changed without me doing anything.

kamilmirza · Jan 28, 2014

try any other ROM and see

fromtheaudible · Jan 28, 2014

kamilmirza said:
try any other ROM and see

Been trying to.
I've tried to flash the rom cleanly, but it reaches 30% and reboots every time.

I'd flash another rom, but I'm running CWM, and all I seem to find is new roms that require TWRP.
When trying to install TWRP recovery, the phone still boots into CWM.

I have no idea what to do.

kamilmirza · Jan 28, 2014

fromtheaudible said:
Been trying to.
I've tried to flash the rom cleanly, but it reaches 30% and reboots every time.

I'd flash another rom, but I'm running CWM, and all I seem to find is new roms that require TWRP.
When trying to install TWRP recovery, the phone still boots into CWM.

I have no idea what to do.

download TWRP from here
then place it in your adb folder

Boot into HBOOT then Fastboot
From fastboot. Use command "fastboot erase cache"
From fastboot. Use command "fastboot flash recovery recovery_file.img"

then reboot your phone into recovery and try any other ROM

---------- Post added at 12:07 AM ---------- Previous post was at 12:04 AM ----------

before all that paste the "fastboot getvar all" (without S/N and IMEI removed) from the bootloader

fromtheaudible · Jan 28, 2014

Tried exactly that twice before you posted it, but still no luck.
Boots into CWM, won't allow full flashes, and still reboots randomly.
Here's the info though:

(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:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4237mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s

I found the usb read status to be interesting. Maybe that's the issue.
Any idea how to fix that if that's the problem?

kamilmirza · Jan 28, 2014

have you tried the latest CWM?

fromtheaudible · Jan 28, 2014

kamilmirza said:
have you tried the latest CWM?

I'm on CWM 6.0.3.1.
Just tried to flash two different versions of TWRP, and CWM, standard and touch.
None of them stuck when I tried to enter recovery from the bootloader, even though fastboot gave me successful flashes.

SaHiLzZ · Jan 28, 2014

Had something similar happen on a nexus ages ago. Internal SD died..

kamilmirza · Jan 28, 2014

we need a professional here

let's call @nkk71 :fingers-crossed:

nkk71 · Jan 28, 2014

kamilmirza said:
we need a professional here
let's call @nkk71 :fingers-crossed:

Didn't read much, but

1- CWM 6.0.3.1... r u kidding?

2- 31.0 was released (at first) with w/p kernel, so changes wont stick,
Use 31.6 instead

3- 'random reboots' -> how's your power button?
Go to bootloader, any reboots ->
no -> go to custom recovery -> any reboots?
If yes to any of above, then ur power button is stuck.

Good night...

Sent from my HTC One using Tapatalk

nkk71 · Jan 29, 2014

fromtheaudible said:
Tried exactly that twice before you posted it, but still no luck.
Boots into CWM, won't allow full flashes, and still reboots randomly.
Here's the info though:

(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001

ERROR: usb_read failed with status e00002e8
getvar:all FAILED (status read failed (No such file or directory))
finished. total time: 0.042s

I found the usb read status to be interesting. Maybe that's the issue.
Any idea how to fix that if that's the problem?

My AT&T HTC One (32 GB) that I bought day one keeps rebooting randomly.

okay, just reread, so a couple of questions:

1- So you had this problem from day 1? and didnt think of exchanging it?

2- what OS you running (Win7, mac, etc)

Code:

(bootloader) version-main:

3- what did you try to flash (any firmware)??

Code:

(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001

4- have you tried restoring to stock using RUU_1.26.502.12_PN0712000_CWS__001_4A.14.3250.13

5- The random reboots, could indicate a hardware problem and/or corrupted partition(s), you could check those by opening a shell while in custom recovery (CWM or TWRP), and check the output:

Code:

C:\...> [B]adb devices[/B]
List of devices attached
H***********    recovery <- yep it's in recovery

C:\...> [B]adb shell
umount /system
umount /data
umount /sdcard
umount /cache[/B]

[B]e2fsck -n -v -f /dev/block/mmcblk0p35[/B] <- this checks /system
[B]e2fsck -n -v -f /dev/block/mmcblk0p36[/B] <- this checks /cache
[B]e2fsck -n -v -f /dev/block/mmcblk0p37[/B] <- this checks /data

if there are no major errors then output will look something like this:
[HIDE]~ # 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[/HIDE]
if there [B]are [/B]major error, then output will look something like this:
[HIDE]~# e2fsck -v -f /dev/block/mmcblk0p37
e2fsck -v -f /dev/block/mmcblk0p37
e2fsck 1.41.11 (14-Mar-2010)
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/mmcblk0p37

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>[/HIDE]

fromtheaudible · Jan 29, 2014

In response to your post:

1. Haven't had the problem from day one. This just started occurring. I've had the device since day 1.

2. I run Windows 7, and Mac OSX 10.9 on separate computers. I've got options.

3. I have tried running the RUU you linked. No dice. Image versions don't match up and won't allow me to push the stock rom. I've tried another that had a closer image version, and also tried a world wide edition. No luck.
My image version is 3.62.401.1

4. Here is my adb shell log:

Code:

localhost:~ ****$ adb devices
List of devices attached 
HT34GW905119	recovery

localhost:~ ****$ adb shell
~ # umount /system
umount: can't umount /system: Invalid argument
~ # umount /data
~ # umount /sdcard
umount: can't umount /sdcard: Invalid argument
~ # umount /cache
~ # e2fsck -n -v -f /dev/block/mmcblk0p35
e2fsck 1.41.14 (22-Dec-2010)
Pass 1: Checking inodes, blocks, and sizes
Deleted inode 31691 has zero dtime.  Fix? no

Deleted inode 31907 has zero dtime.  Fix? no

Deleted inode 31908 has zero dtime.  Fix? no

Deleted inode 79295 has zero dtime.  Fix? no

Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences:  -(133064--133066) -(148739--148743) -(154603--154607) -(341749--342089)
Fix? no

Free blocks count wrong for group #4 (1802, counted=1797).
Fix? no

Free blocks count wrong (125515, counted=125510).
Fix? no

Inode bitmap differences:  -31691 -(31907--31908) -79295
Fix? no

Free inodes count wrong for group #4 (7691, counted=7690).
Fix? no

Free inodes count wrong (116323, counted=116322).
Fix? no


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


    2477 inodes used (2.09%)
      21 non-contiguous files (0.8%)
       2 non-contiguous directories (0.1%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 2171
  349620 blocks used (73.58%)
       0 bad blocks
       0 large files

    2091 regular files
      79 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
     295 symbolic links (295 fast symbolic links)
       0 sockets
--------
    2465 files
~ # e2fsck -n -v -f /dev/block/mmcblk0p36
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
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

      21 inodes used (0.05%)
       1 non-contiguous file (4.8%)
       0 non-contiguous directories (0.0%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 13
    5719 blocks used (3.49%)
       0 bad blocks
       0 large files

       8 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
--------
      12 files
~ # e2fsck -n -v -f /dev/block/mmcblk0p37
e2fsck 1.41.14 (22-Dec-2010)
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found.  Fix? no

Inode 254019 was part of the orphaned inode list.  IGNORED.
Inode 254153 was part of the orphaned inode list.  IGNORED.
Deleted inode 255336 has zero dtime.  Fix? no

Inode 255428 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
Block bitmap differences:  -1016475 -(2083011--2083012) -2178670 -2178844 -2180689 +2186831
Fix? no

Free blocks count wrong for group #58 (5718, counted=5716).
Fix? no

Free blocks count wrong for group #63 (21182, counted=21181).
Fix? no

Free blocks count wrong (2577130, counted=1786950).
Fix? no

Inode bitmap differences:  -254019 -254153 -255336 -255428
Fix? no

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

Free inodes count wrong for group #31 (5994, counted=5963).
Fix? no

Free inodes count wrong for group #116 (6273, counted=6272).
Fix? no

Free inodes count wrong for group #117 (6642, counted=6497).
Fix? no

Free inodes count wrong for group #160 (7948, counted=7947).
Fix? no

Free inodes count wrong (1679719, counted=1674260).
Fix? no


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


   24217 inodes used (1.42%)
    1679 non-contiguous files (6.9%)
      39 non-contiguous directories (0.2%)
         # of inodes with ind/dind/tind blocks: 0/0/0
         Extent depth histogram: 29119/223
 4238614 blocks used (62.19%)
       0 bad blocks
       1 large file

   27526 regular files
    1815 directories
       0 character device files
       0 block device files
       0 fifos
       0 links
     313 symbolic links (313 fast symbolic links)
       9 sockets
--------
   29663 files

Didn't see anything there that looked like a corrupt partition. But I haven't had success unmounting system or sdcard.

To respond to an earlier post, power button is fine. Bootloader and recovery never reboot. First thing I noticed.

LibertyMarine · Jan 29, 2014

Maybe too low voltage?

Or http://android-revolution-hd.blogspot.ch/2013/10/fix-data-htc-one.html ?

nkk71 · Jan 29, 2014

fromtheaudible said:
1. Haven't had the problem from day one. This just started occurring. I've had the device since day 1.

ah, ok my bad, i misunderstood.

2. I run Windows 7, and Mac OSX 10.9 on separate computers. I've got options.

Windows 7 should do nicely.

3. I have tried running the RUU you linked. No dice. Image versions don't match up and won't allow me to push the stock rom. I've tried another that had a closer image version, and also tried a world wide edition. No luck.
My image version is 3.62.401.1

I think above refers to your ROM, cause your "(bootloader) version-main: " (ie firwmare) is blank, and since you're on hboot 1.44 + radio 4A.14.3250.13 should equal the RUU I posted earlier.
but nevermind for now

Didn't see anything there that looked like a corrupt partition. But I haven't had success unmounting system or sdcard.

it won't unmount if it's already umounted, so that was not really an error

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

and there we go

, the plot thickens, both /system and /data have some corruptions, not completely unmountable but also not completely clean, which would be a good reason you're experiencing problems.

the one thing i'm concerned about it that the problem is with both /system and /data, which may indicate a hardware fault.

we can go ahead and perform a "real" format (as opposed to wipe) of these partitions, if the formatting sticks (ie without filesystem errors coming up again), then it could just be a software issue.

Let me know if you want to proceed? (if you are going to format /system and /data), you need to be comfy with adb shell, adb push and/or adb sideload)

PS: I may need to offline in about 20mins, and could be back in a few (probably like 3+) hours or so

fromtheaudible · Jan 29, 2014

nkk71 said:
ah, ok my bad, i misunderstood.

Windows 7 should do nicely.

I think above refers to your ROM, cause your "(bootloader) version-main: " (ie firwmare) is blank, and since you're on hboot 1.44 + radio 4A.14.3250.13 should equal the RUU I posted earlier.
but nevermind for now

it won't unmount if it's already umounted, so that was not really an error

and there we go , the plot thickens, both /system and /data have some corruptions, not completely unmountable but also not completely clean, which would be a good reason you're experiencing problems.

the one thing i'm concerned about it that the problem is with both /system and /data, which may indicate a hardware fault.

we can go ahead and perform a "real" format (as opposed to wipe) of these partitions, if the formatting sticks (ie without filesystem errors coming up again), then it could just be a software issue.

Let me know if you want to proceed? (if you are going to format /system and /data), you need to be comfy with adb shell, adb push and/or adb sideload)

PS: I may need to offline in about 20mins, and could be back in a few (probably like 3+) hours or so

That's what I gathered I'd have to do once LibertyMarine linked that forum post from Mike1986.
I'm all for it.

nkk71 · Jan 29, 2014

fromtheaudible said:
That's what I gathered I'd have to do once LibertyMarine linked that forum post from Mike1986.
I'm all for it.

i've done it with other users 3 or 4 times successfully, and 1 failure because of the filesystem errors kept coming back and back and back = hardware problem.

so have you read @mike1986. thread? you comfy with it?

here goes:
1- download this: http://goo.gl/pmZ9Mt and place it in your adb/fastboot folder
2- in recovery:

Code:

[B]adb push mkfs.ext4 /tmp/

adb shell
chmod 777 /tmp/mkfs.ext4

umount /data
umount /sdcard
umount /system

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

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

you can see the expected output in mike's blog: http://android-revolution-hd.blogspot.com/2013/10/fix-data-htc-one.html

if that goes all well, continue in the shell:

Code:

[B]mount /data
mkdir -p /data/media/0
exit[/B]

then push your rom:

adb push rom.zip /data/media/0/ <- this will take 5 mins or so with no progress showing until finished

then install your rom in recovery, and hope for the best, stay away from 4.4 (KitKat) ROMs for now, because of recovery version (BTW: which one and version do you have?)

fromtheaudible · Jan 29, 2014

No working mirror for mkfs.ext4 file. :/

nkk71 · Jan 29, 2014

fromtheaudible said:
No working mirror for mkfs.ext4 file. :/

working here: http://www.androidrevolution.nl/downloader/download.php?file=mkfs.ext4

otherwise i'll upload it to my dropbox.

[Q] Random Shutdowns. Reverts to previous phone state on reboot.

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Member

Senior Member

Senior Member

Inactive Recognized Developer / Contributor

Inactive Recognized Developer / Contributor

Member

Senior Member

Inactive Recognized Developer / Contributor

Member

Inactive Recognized Developer / Contributor

Member

Inactive Recognized Developer / Contributor

Similar threads

Top Liked Posts