Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,785,988 Members 55,566 Now Online
XDA Developers Android and Mobile Development Forum

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

Tip us?
 
fromtheaudible
Old
(Last edited by fromtheaudible; 30th January 2014 at 04:24 PM.) Reason: Name in console log
#31  
Junior Member - OP
Thanks Meter 0
Posts: 18
Join Date: Sep 2010
Quote:
Originally Posted by nkk71 View Post
i thought you don't have a working ROM, did i misunderstand?
Kind of, but it's okay. The rom is "semi" functional, radio and all.
I can make calls, send texts, etc.
However it will randomly reboot whether or not I'm using it.
I've seemed to narrow it down, and it looks like this happens mainly when data is being written to the device.
Pushing/copying files to the device will reboot it, as will heavy use immediately when the device reboots.

At that, when it reboots, it seems to remember a previous phone state.
So apps that have been updated since this started happening on Sunday, will no longer be updated anymore and will begin auto-updated.
Texts that have been received since that day will be absent.
Voicemails that have been deleted since then will be back.
I also get quite a few crashes in apps when it reboots.

However, if I let it do its thing for a few minutes after the reboot into the ROM, then go to use it, it functions as normal.
It's basically a half working device though with a lit fuse on the end.

Also, just tried to relock the bootloader and got this:
Code:
localhost:platform-tools ****$ fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off 
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.155s
I threw it back into bootloader and it still shows as unlocked.
 
nkk71
Old
#32  
nkk71's Avatar
Recognized Contributor
Thanks Meter 2,836
Posts: 5,733
Join Date: May 2010
Location: Beirut
Quote:
Originally Posted by fromtheaudible View Post
Kind of, but it's okay. The rom is "semi" functional, radio and all.
I can make calls, send texts, etc.
However it will randomly reboot whether or not I'm using it.
I've seemed to narrow it down, and it looks like this happens mainly when data is being written to the device.
Pushing/copying files to the device will reboot it, as will heavy use immediately when the device reboots.

At that, when it reboots, it seems to remember a previous phone state.
So apps that have been updated since this started happening on Sunday, will no longer be updated anymore and will begin auto-updated.
Texts that have been received since that day will be absent.
Voicemails that have been deleted since then will be back.
I also get quite a few crashes in apps when it reboots.

However, if I let it do its thing for a few minutes after the reboot into the ROM, then go to use it, it functions as normal.
It's basically a half working device though with a lit fuse on the end.

Also, just tried to relock the bootloader and got this:
Code:
localhost:platform-tools ****$ fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off 
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
ERROR: usb_read failed with status e00002ed
FAILED (status read failed (No such file or directory))
finished. total time: 1.155s
I threw it back into bootloader and it still shows as unlocked.
Are you able to flash a stock recovery?
 
fromtheaudible
Old
#33  
Junior Member - OP
Thanks Meter 0
Posts: 18
Join Date: Sep 2010
Quote:
Originally Posted by nkk71 View Post
Are you able to flash a stock recovery?
Code:
localhost:platform-tools ****$ fastboot flash recovery Android_Recovery_3e_JB.img
sending 'recovery' (7680 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
finished. total time: 2.150s
Ugh.
 
nkk71
Old
#34  
nkk71's Avatar
Recognized Contributor
Thanks Meter 2,836
Posts: 5,733
Join Date: May 2010
Location: Beirut
Quote:
Originally Posted by fromtheaudible View Post
Code:
localhost:platform-tools ****$ fastboot flash recovery Android_Recovery_3e_JB.img
sending 'recovery' (7680 KB)...
ERROR: usb_write failed with status e00002ed
FAILED (data transfer failure (No such file or directory))
finished. total time: 2.150s
Ugh.
this keeps coming up: "ERROR: usb_write failed with status e00002ed"

and i have no idea what that means, at first I thought it's cause of mac, but this is getting weird!!!!

Do you have access to another computer Win7, otherwise make yourself an Ubuntu 12.04 LTS Live USB:
http://forum.xda-developers.com/show...&postcount=280

and try fastboot there

(no need to install Ubuntu, just use the "Try Ubuntu" option)
 
fromtheaudible
Old
#35  
Junior Member - OP
Thanks Meter 0
Posts: 18
Join Date: Sep 2010
Quote:
Originally Posted by nkk71 View Post
this keeps coming up: "ERROR: usb_write failed with status e00002ed"

and i have no idea what that means, at first I thought it's cause of mac, but this is getting weird!!!!

Do you have access to another computer Win7, otherwise make yourself an Ubuntu 12.04 LTS Live USB:
http://forum.xda-developers.com/show...&postcount=280

and try fastboot there

(no need to install Ubuntu, just use the "Try Ubuntu" option)
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
sending 'recovery' (7680 KB)...
OKAY [  1.117s]
writing 'recovery'...
OKAY [  0.780s]
finished. total time: 1.899s
That's the same stock JB recovery used on the mac, just renamed to recovery.img.
When I boot into recovery, CWM remains...
 
nkk71
Old
#36  
nkk71's Avatar
Recognized Contributor
Thanks Meter 2,836
Posts: 5,733
Join Date: May 2010
Location: Beirut
Quote:
Originally Posted by fromtheaudible View Post
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery recovery
.img
sending 'recovery' (7680 KB)...
OKAY [  1.117s]
writing 'recovery'...
OKAY [  0.780s]
finished. total time: 1.899s
That's the same stock JB recovery used on the mac, just renamed to recovery.img.
When I boot into recovery, CWM remains...
This looks like it's beyond me So I give up,

one last thing, download attached file (credit to @cschmitt), and flash in ruu mode
fastboot oem rebootRUU
fasbtoot flash zip firmware_twrp.zip
fastboot reboot-bootloader
fastboot erase cache


-> enter recovery, see if TWRP shows up

EDIT: oh, this is probably not going to work either: you're S-On with Unlocked bootloader, so ruu mode probably wont work.
Attached Files
File Type: zip firmware_twrp.zip - [Click for QR Code] (9.05 MB, 1 views)
 
cross222
Old
(Last edited by cross222; 5th March 2014 at 10:27 PM.)
#37  
Junior Member
Thanks Meter 0
Posts: 1
Join Date: Aug 2013
Quote:
Originally Posted by fromtheaudible View Post
My AT&T HTC One (32 GB) that I bought day one keeps rebooting randomly.

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.

Any ideas guys?
Hello, I have same problem(
At the same time the body starts normally, but after 15-20 seconds after the phone is fully loaded, it goes to reboot.
Wipe using TWRP v2.6.3.3 does not work
(m7 ul, s-off, cid-1111111, hbot-1.54.0000, radio-4a.22.3263.14, os-4.06.1540.2)
android 4.4, viperone 4.3, TWRP 2.6.3.3, windows 8,

 
c:\mini-sdk>adb shell
~ # ←[6ncat /proc/emmc
cat /proc/emmc
dev: size erasesize name
mmcblk0p19: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
mmcblk0p33: 01000000 00000200 "boot"
mmcblk0p35: 73fffc00 00000200 "system"
mmcblk0p26: 00140200 00000200 "local"
mmcblk0p36: 27fffe00 00000200 "cache"
mmcblk0p37: 680000000 00000200 "userdata"
mmcblk0p22: 01400000 00000200 "devlog"
mmcblk0p24: 00040000 00000200 "pdata"
mmcblk0p27: 00010000 00000200 "extra"
mmcblk0p31: 04b00200 00000200 "radio"
mmcblk0p16: 03c00400 00000200 "adsp"
mmcblk0p15: 00100000 00000200 "dsps"
mmcblk0p17: 007ffa00 00000200 "radio_config"
mmcblk0p20: 00400000 00000200 "modem_st1"
mmcblk0p21: 00400000 00000200 "modem_st2"
mmcblk0p28: 00100000 00000200 "cdma_record"
mmcblk0p18: 02000000 00000200 "reserve_1"
mmcblk0p30: 034ffa00 00000200 "reserve_2"
mmcblk0p32: 05fffc00 00000200 "reserve_3"
mmcblk0p29: 06069e00 00000200 "reserve"
~ # ←[6nmount
mount
rootfs on / type rootfs (rw)
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)
/dev/block/mmcblk0p37 on /sdcard type ext4 (rw,seclabel,relatime)


 
c:\mini-sdk>adb shell
~ # ←[6numount /system
umount /system
umount: can't umount /system: Invalid argument
~ # ←[6numount /data
umount /data
~ # ←[6numount /sdcard
umount /sdcard
~ # ←[6numount /cache
umount /cache
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p35
e2fsck -n -v -f /dev/block/mmcblk0p35
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
Free blocks count wrong (165656, counted=165475).
Fix? no


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


2749 inodes used (2.31%)
35 non-contiguous files (1.3%)
5 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2441/1
309479 blocks used (65.13%)
0 bad blocks
0 large files

2366 regular files
75 directories
0 character device files
0 block device files
0 fifos
0 links
299 symbolic links (299 fast symbolic links)
0 sockets
--------
2740 files

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

18 inodes used (0.04%)
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: 10
5266 blocks used (3.21%)
0 bad blocks
0 large files

5 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
--------
9 files

~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p35
e2fsck -n -v -f /dev/block/mmcblk0p35
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
Free blocks count wrong (165656, counted=165475).
Fix? no


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


2749 inodes used (2.31%)
35 non-contiguous files (1.3%)
5 non-contiguous directories (0.2%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 2441/1
309479 blocks used (65.13%)
0 bad blocks
0 large files

2366 regular files
75 directories
0 character device files
0 block device files
0 fifos
0 links
299 symbolic links (299 fast symbolic links)
0 sockets
--------
2740 files
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p36
e2fsck -n -v -f /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

18 inodes used (0.04%)
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: 10
5266 blocks used (3.21%)
0 bad blocks
0 large files

5 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
--------
9 files
~ # ←[6ne2fsck -n -v -f /dev/block/mmcblk0p37
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
Pass 2: Checking directory structure
Entry 'Weather.apk' in /media/0/vrtheme/apply/system/priv-app/aligned (918063) h
as deleted/unused inode 918081. Clear? no

Entry 'aligned' in /media/0/vrtheme/apply/system/framework (918051) has deleted/
unused inode 918082. Clear? no

Entry 'aligned' in /media/0/vrtheme/apply/system/framework (918051) has an incor
rect filetype (was 2, should be 1).
Fix? no

Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Inode 918051 ref count is 3, should be 2. Fix? no

Pass 5: Checking group summary information
Block bitmap differences: -(100064--100265) -(103424--104447) -(106496--107184)
-(116736--118783) -3673725 -(3718674--3719092) -(4165632--4166800) -(4271950--4
273224)
Fix? no

Free blocks count wrong for group #1 (7062, counted=16592).
Fix? no

Free blocks count wrong for group #2 (7295, counted=5853).
Fix? no

Free blocks count wrong for group #3 (7427, counted=20958).
Fix? no

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

Free blocks count wrong for group #5 (4838, counted=8546).
Fix? no

Free blocks count wrong for group #6 (3296, counted=4320).
Fix? no

Free blocks count wrong for group #7 (1550, counted=4731).
Fix? no

Free blocks count wrong for group #8 (2158, counted=4153).
Fix? no

Free blocks count wrong for group #9 (4286, counted=8344).
Fix? no

Free blocks count wrong for group #10 (6357, counted=9030).
Fix? no

Free blocks count wrong for group #11 (10219, counted=10584).
Fix? no

Free blocks count wrong for group #12 (10800, counted=13214).
Fix? no

Free blocks count wrong for group #15 (13644, counted=15894).
Fix? no

Free blocks count wrong for group #27 (3825, counted=5873).
Fix? no

Free blocks count wrong for group #28 (7128, counted=8067).
Fix? no

Free blocks count wrong for group #111 (19350, counted=14994).
Fix? no

Free blocks count wrong for group #112 (16285, counted=11156).
Fix? no

Free blocks count wrong for group #113 (26334, counted=17521).
Fix? no

Free blocks count wrong for group #116 (18714, counted=17104).
Fix? no

Free blocks count wrong for group #127 (16994, counted=14656).
Fix? no

Free blocks count wrong (3508076, counted=3529988).
Fix? no

Inode bitmap differences: -(918081--918086)
Fix? no

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

Free inodes count wrong for group #53 (8191, counted=8189).
Fix? no

Free inodes count wrong for group #55 (8170, counted=8169).
Fix? no

Free inodes count wrong for group #97 (8181, counted=8180).
Fix? no

Free inodes count wrong for group #98 (8182, counted=8192).
Fix? no

Free inodes count wrong for group #111 (7027, counted=5991).
Fix? no

Directories count wrong for group #111 (61, counted=93).
Fix? no

Free inodes count wrong for group #112 (8096, counted=7610).
Fix? no

Directories count wrong for group #112 (25, counted=87).
Fix? no

Free inodes count wrong for group #140 (8192, counted=8191).
Fix? no

Free inodes count wrong for group #141 (8175, counted=8174).
Fix? no

Free inodes count wrong for group #158 (8186, counted=8187).
Fix? no

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

Free inodes count wrong (1682152, counted=1681087).
Fix? no


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


21784 inodes used (1.28%)
718 non-contiguous files (3.3%)
24 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 22431/75
3307668 blocks used (48.53%)
0 bad blocks
1 large file

19797 regular files
2708 directories
0 character device files
0 block device files
0 fifos
0 links
320 symbolic links (320 fast symbolic links)
9 sockets
--------
22836 files


 
c:\mini-sdk>adb push mkfs.ext4 /tmp
2824 KB/s (3537143 bytes in 1.223s)

c:\mini-sdk>adb shell
~ # ←[6nchmod 777 /tmp/mkfs.ext4
chmod 777 /tmp/mkfs.ext4
~ # ←[6numount /data
umount /data
~ # ←[6numount /sdcard
umount /sdcard
~ # ←[6numount /system
umount /system
umount: can't umount /system: Invalid argument
~ # ←[6n

~ # ←[6n/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,^ext
ra_isize -m 0 /dev/block/mmcblk0p35
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
118800 inodes, 475135 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
15 block groups
32768 blocks per group, 32768 fragments per group
7920 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912

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

This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6n

~ # ←[6n/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,^ext
ra_isize -m 0 /dev/block/mmcblk0p35
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
118800 inodes, 475135 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
15 block groups
32768 blocks per group, 32768 fragments per group
7920 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912

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

This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6n

~ # ←[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,^ext
ra_isize -m 0 /dev/block/mmcblk0p37
mke2fs 1.41.12 (17-May-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1703936 inodes, 6815744 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
208 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,

4096000

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

This filesystem will be automatically checked every 22 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6n


Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes