[Q] Phone Reboots every 2 minutes. Stuck on ARHD 31.6 - One (M7) Q&A, Help & Troubleshooting

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?

Related

[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] 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] Random Shutdowns. Reverts to previous phone state on reboot.

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?
does this happens on any other ROM?
kamilmirza said:
does this happens on any other ROM?
Click to expand...
Click to collapse
Nope. Never had this happen before. I just wonder how something could have changed without me doing anything.
try any other ROM and see
kamilmirza said:
try any other ROM and see
Click to expand...
Click to collapse
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.
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.
Click to expand...
Click to collapse
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"
Click to expand...
Click to collapse
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
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?
have you tried the latest CWM?
kamilmirza said:
have you tried the latest CWM?
Click to expand...
Click to collapse
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.
Had something similar happen on a nexus ages ago. Internal SD died..
we need a professional here
let's call @nkk71 :fingers-crossed:
kamilmirza said:
we need a professional here
let's call @nkk71 :fingers-crossed:
Click to expand...
Click to collapse
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
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?
Click to expand...
Click to collapse
My AT&T HTC One (32 GB) that I bought day one keeps rebooting randomly.
Click to expand...
Click to collapse
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]
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.
Maybe too low voltage?
Or http://android-revolution-hd.blogspot.ch/2013/10/fix-data-htc-one.html ?
fromtheaudible said:
1. Haven't had the problem from day one. This just started occurring. I've had the device since day 1.
Click to expand...
Click to collapse
ah, ok my bad, i misunderstood.
2. I run Windows 7, and Mac OSX 10.9 on separate computers. I've got options.
Click to expand...
Click to collapse
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
Click to expand...
Click to collapse
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.
Click to expand...
Click to collapse
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 **********
Click to expand...
Click to collapse
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
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
Click to expand...
Click to collapse
That's what I gathered I'd have to do once LibertyMarine linked that forum post from Mike1986.
I'm all for it.
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.
Click to expand...
Click to collapse
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
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 25 mounts or 180 days, whichever comes first.
Use tune2fs -c or -i to override.
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?)
No working mirror for mkfs.ext4 file. :/
fromtheaudible said:
No working mirror for mkfs.ext4 file. :/
Click to expand...
Click to collapse
working here: http://www.androidrevolution.nl/downloader/download.php?file=mkfs.ext4
otherwise i'll upload it to my dropbox.

[Q] Help GPE --> Sense! Touchscreen non responsive

Hello Everyone. I need help!!
I had an 801n HTC one M7UL.. I swapped back and forth to the point that I do not recall.. what version I had to begin with.
NON RESPONSIVE TOUCHSCREEN - Only top third
1) Only top third of my touch screen responds (this was after an attempt to flash SOME recovery img..).. and I am not able to fix this no matter what recovery img I tried!!! I went to accessibility etc.... nothigng helps!!! (unless this coincided with the dropping of my phone.. I have two boys... I AM NO NAMIMG ANY NAMES!!....
Unsuccessful attempts to revert from GPE ---> Sense (xx.401.xx)
2) I tried to go from GPE (which I migrated to seamlessly) back to Sense 5.5.... but NO luck. ARHD 52 fails during install (set-metadata-recursive, changes failed etc....).. I tried EVERYTHING!... What am I missing? I tried odexed/deodex 4.19.401.9 along with the recovery.. and firmware.. NOTHING allows me to install proper ROM. Odex. also fails with Status 7.
WHAT AM I DOING WRONG? I went back to GPE after I bricked my htc M7UL... What eXACTLY must I do?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35VWXXXXXXX
(bootloader) imei: 354XXXXXXXXXX5193
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3906mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
I have attempted Developer Edition as well.. xx.1540.x.. with SuperCID.. but to no avail. What am I doing wrong?
abdoulwane said:
Hello Everyone. I need help!!
I had an 801n HTC one M7UL.. I swapped back and forth to the point that I do not recall.. what version I had to begin with.
NON RESPONSIVE TOUCHSCREEN - Only top third
1) Only top third of my touch screen responds (this was after an attempt to flash SOME recovery img..).. and I am not able to fix this no matter what recovery img I tried!!! I went to accessibility etc.... nothigng helps!!! (unless this coincided with the dropping of my phone.. I have two boys... I AM NO NAMIMG ANY NAMES!!....
Unsuccessful attempts to revert from GPE ---> Sense (xx.401.xx)
2) I tried to go from GPE (which I migrated to seamlessly) back to Sense 5.5.... but NO luck. ARHD 52 fails during install (set-metadata-recursive, changes failed etc....).. I tried EVERYTHING!... What am I missing? I tried odexed/deodex 4.19.401.9 along with the recovery.. and firmware.. NOTHING allows me to install proper ROM. Odex. also fails with Status 7.
WHAT AM I DOING WRONG? I went back to GPE after I bricked my htc M7UL... What eXACTLY must I do?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: FA35VWXXXXXXX
(bootloader) imei: 354XXXXXXXXXX5193
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3906mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.071s
Click to expand...
Click to collapse
I think this could be caused by either a wrong recovery, kernel, or rom. Your bootloader appears to be just fine. You should never flash "SOME" recovery image as the wrong ones for a different system can really mess up your device. Have you tried using a stock full RUU? Find one for your carrier. I have AT&T so I use the their first ever RUU for Android 4.1.2 if my phone ever gets messed up to the point of no return. And since your fastboot is working, try to relock your bootloader before using a stock RUU or the update won't happen. If that doesn't work there are other options. Good thing is that you're S-Off so you have a lot more options. You could try a stock Google Play Edition RUU. I recommend that one as it is smaller than Sense and I've never encountered any issues with whatsoever when it comes to recovering my device.
Thanks... and also...
Thank you for you message!!! I will attempt your suggestion. I hope I did not permanently "mess up" my device!! By the way... I did try Google Play Edition RUU which is what unbricked my phone.. but I have not recovered touchscreen response.
For what it's worth.. here is the LOG on the ARHD insall. 6.1 GPE works.. but not the ARHD52.......
Prophet16 said:
I think this could be caused by either a wrong recovery, kernel, or rom. Your bootloader appears to be just fine. You should never flash "SOME" recovery image as the wrong ones for a different system can really mess up your device. Have you tried using a stock full RUU? Find one for your carrier. I have AT&T so I use the their first ever RUU for Android 4.1.2 if my phone ever gets messed up to the point of no return. And since your fastboot is working, try to relock your bootloader before using a stock RUU or the update won't happen. If that doesn't work there are other options. Good thing is that you're S-Off so you have a lot more options. You could try a stock Google Play Edition RUU. I recommend that one as it is smaller than Sense and I've never encountered any issues with whatsoever when it comes to recovering my device.
Click to expand...
Click to collapse
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Android Revolution HD
ROM Version : 52.0
ROM Author : mike1986
Device : HTC One
Start at : Sat Mar 15 04:50:41 2014
I:emmc_scan_partitions:[partition_count:22] [allocat_num:50]
bad option "defaults"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p33 /boot emmc defaults defaults
bad option "defaults"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p34 /recovery emmc defaults defaults
bad option "ro"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p35 /system ext4 ro,noatime,barrier=0 wait
bad option "nosuid"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p36 /cache ext4 nosuid,nodev,noatime,barrier=0 wait,check
bad option "noatime"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p37 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0 wait,check,encryptable=/dev/block/mmcblk0p27
bad option "ro"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p31 /firmware/mdm vfat ro,fmask=0000,dmask=0000,shortname=lower wait
bad option "ro"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p16 /firmware/q6 vfat ro,fmask=0000,dmask=0000,shortname=lower wait
bad option "defaults"
skipping malformed recovery.fstab line: /devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=usbdisk:auto
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
=================================
Android Revolution HD by mike1986
=================================
>>> Formatting partitions
unmount of /system failed; no such volume
(system is unmounted already)
I:emmc_scan_partitions:[partition_count:22] [allocat_num:50]
Creating filesystem with parameters:
Size: 1879048192
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 7168
Label:
Blocks: 458752
Block groups: 14
Reserved block group size: 111
Created filesystem with 11/114688 inodes and 15045/458752 blocks
unmount of /cache failed; no such volume
(cache is unmounted already)
I:emmc_scan_partitions:[partition_count:22] [allocat_num:50]
Creating filesystem with parameters:
Size: 671084544
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2559
Label:
Blocks: 163839
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/40960 inodes and 5255/163839 blocks
unknown volume for path [/data]
(data is mounted already)
>>> Mounting partitions
unknown volume for path [/system]
(system is mounted already)
unknown volume for path [/data]
(data is mounted already)
>>> Cleaning process
about to run program [/tmp/clean.sh] with 1 args
rm: can't remove '/data/app/eu.chainfire.supersu*.apk': No such file or directory
rm: can't remove '/data/app/eu.chainfire.supersu.pro*.apk': No such file or directory
>>> Writing Data & System
about to run program [/sbin/busybox] with 5 args
about to run program [/tmp/sqlite3] with 3 args
Error: unable to open database "/data/data/com.htc.opensense.social/databases/stream.db": unable to open database file
run_program: child exited with status 1
about to run program [/sbin/sync] with 1 args
>>> Installing Google Chrome
>>> Installing Google Maps & Google Street
>>> Installing Google Music
>>> Installing Google Plus
>>> Installing Google Now
>>> Installing Google Keep
>>> Installing Google Hangouts
>>> Installing Google YouTube
>>> Installing Google Drive
>>> Installing Dropbox
>>> Installing ES File Explorer
>>> Installing Facebook
>>> Installing Adobe Flash Player
>>> Installing Adobe Reader
>>> Installing Twitter
>>> Installing Sense 5 Toolbox & Xposed
>>> Creating toolbox symlinks
>>> Creating additional symlinks
>>> Installing busybox
about to run program [/system/xbin/busybox] with 4 args
>>> Setting permissions
ApplyParsedPerms: removexattr of /system/xbin/su to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Installer Error (Status 7)
End at : Sat Mar 15 04:51:50 2014
I Initially had PN071000/HTC__0001 mid/cid..... and now SuperCID. Which one should I use?
RUU M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed
abdoulwane said:
Thank you for you message!!! I will attempt your suggestion. I hope I did not permanently "mess up" my device!!
For what it's worth.. here is the LOG on the ARHD insall. 6.1 GPE works.. but not the ARHD52.......
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : Android Revolution HD
ROM Version : 52.0
ROM Author : mike1986
Device : HTC One
Start at : Sat Mar 15 04:50:41 2014
I:emmc_scan_partitions:[partition_count:22] [allocat_num:50]
bad option "defaults"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p33 /boot emmc defaults defaults
bad option "defaults"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p34 /recovery emmc defaults defaults
bad option "ro"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p35 /system ext4 ro,noatime,barrier=0 wait
bad option "nosuid"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p36 /cache ext4 nosuid,nodev,noatime,barrier=0 wait,check
bad option "noatime"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p37 /data ext4 noatime,nosuid,nodev,noauto_da_alloc,barrier=0 wait,check,encryptable=/dev/block/mmcblk0p27
bad option "ro"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p31 /firmware/mdm vfat ro,fmask=0000,dmask=0000,shortname=lower wait
bad option "ro"
skipping malformed recovery.fstab line: /dev/block/mmcblk0p16 /firmware/q6 vfat ro,fmask=0000,dmask=0000,shortname=lower wait
bad option "defaults"
skipping malformed recovery.fstab line: /devices/platform/msm_hsusb_host/usb auto auto defaults voldmanaged=usbdisk:auto
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
=================================
Android Revolution HD by mike1986
=================================
>>> Formatting partitions
unmount of /system failed; no such volume
(system is unmounted already)
I:emmc_scan_partitions:[partition_count:22] [allocat_num:50]
Creating filesystem with parameters:
Size: 1879048192
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 7168
Label:
Blocks: 458752
Block groups: 14
Reserved block group size: 111
Created filesystem with 11/114688 inodes and 15045/458752 blocks
unmount of /cache failed; no such volume
(cache is unmounted already)
I:emmc_scan_partitions:[partition_count:22] [allocat_num:50]
Creating filesystem with parameters:
Size: 671084544
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2559
Label:
Blocks: 163839
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/40960 inodes and 5255/163839 blocks
unknown volume for path [/data]
(data is mounted already)
>>> Mounting partitions
unknown volume for path [/system]
(system is mounted already)
unknown volume for path [/data]
(data is mounted already)
>>> Cleaning process
about to run program [/tmp/clean.sh] with 1 args
rm: can't remove '/data/app/eu.chainfire.supersu*.apk': No such file or directory
rm: can't remove '/data/app/eu.chainfire.supersu.pro*.apk': No such file or directory
>>> Writing Data & System
about to run program [/sbin/busybox] with 5 args
about to run program [/tmp/sqlite3] with 3 args
Error: unable to open database "/data/data/com.htc.opensense.social/databases/stream.db": unable to open database file
run_program: child exited with status 1
about to run program [/sbin/sync] with 1 args
>>> Installing Google Chrome
>>> Installing Google Maps & Google Street
>>> Installing Google Music
>>> Installing Google Plus
>>> Installing Google Now
>>> Installing Google Keep
>>> Installing Google Hangouts
>>> Installing Google YouTube
>>> Installing Google Drive
>>> Installing Dropbox
>>> Installing ES File Explorer
>>> Installing Facebook
>>> Installing Adobe Flash Player
>>> Installing Adobe Reader
>>> Installing Twitter
>>> Installing Sense 5 Toolbox & Xposed
>>> Creating toolbox symlinks
>>> Creating additional symlinks
>>> Installing busybox
about to run program [/system/xbin/busybox] with 4 args
>>> Setting permissions
ApplyParsedPerms: removexattr of /system/xbin/su to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Installer Error (Status 7)
End at : Sat Mar 15 04:51:50 2014
Click to expand...
Click to collapse
Didnt read, but:
abdoulwane said:
>>> Setting permissions
ApplyParsedPerms: removexattr of /system/xbin/su to 0 failed: Operation not supported on transport endpoint
script aborted: set_metadata_recursive: some changes failed
set_metadata_recursive: some changes failed
Click to expand...
Click to collapse
You need TWRP 2.6.3.3 or later for (most) 4.4 ROMs.
abdoulwane said:
I Initially had PN071000/HTC__0001 mid/cid..... and now SuperCID. Which one should I use?
RUU M7 UL JB 50 HTC Europe 1.20.401.1 Radio 4A.13.3227.06 10.27.1127.01 Release 308001 Signed 2 4
RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed
Click to expand...
Click to collapse
The second! 1.28.401.7
Got an error!! UNKNOWN ERROR.. Shall I lock first???
nkk71 said:
Didnt read, but:
You need TWRP 2.6.3.3 or later for (most) 4.4 ROMs.
The second! 1.28.401.7
Click to expand...
Click to collapse
abdoulwane said:
Got an error!! UNKNOWN ERROR.. Shall I lock first???
Click to expand...
Click to collapse
NO
what is "Got an error!! UNKNOWN ERROR.."
anyway, you have a hardware problem, so changing roms isnt going to fix it. or did i misunderstand something?
INDEED it stated so
ERROR(): UNKNOWN ERROR was the status
nkk71 said:
NO
what is "Got an error!! UNKNOWN ERROR.."
anyway, you have a hardware problem, so changing roms isnt going to fix it. or did i misunderstand something?
Click to expand...
Click to collapse
abdoulwane said:
INDEED it stated so
ERROR(): UNKNOWN ERROR was the status
Click to expand...
Click to collapse
ok, but what does "it" refer to?
:cyclops: I ran the RUU.exe file.. (RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed) and it went through confirmation screens then.... Error: UNKNOWN ERROR.
I proceeded with the RUU.ZIp (of RUU Zip M7_Google Edition_4.4_3.58.1700.5) . (506184 bytes in size)
It was successful as before.. performed the 4.4.2 update.... but STILL no luck with TouchScreen... Have I messed up my device permanently?
or shall attempt to make x.401.xxx work first? and see if that would restore my device fonctionality??
nkk71 said:
ok, but what does "it" refer to?
Click to expand...
Click to collapse
abdoulwane said:
:cyclops: I ran the RUU.exe file.. (RUU M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed) and it went through confirmation screens then.... Error: UNKNOWN ERROR.
I proceeded with the RUU.ZIp (of RUU Zip M7_Google Edition_4.4_3.58.1700.5) . (506184 bytes in size)
It was successful as before.. performed the 4.4.2 update.... but STILL no luck with TouchScreen... Have I messed up my device permanently?
or shall attempt to make x.401.xxx work first? and see if that would restore my device fonctionality??
Click to expand...
Click to collapse
1- are you on Win 8.1?
2- i thought you said the touchscreen being messed up, was due to an unnamed offspring
I am on Windows 7 Ultimate with service Pack 1 actually.
I am suspecting one of my boys,... although I have no proof or sign of the htc being dropped. It coincided with my installation of TouchRecover (6 months ago).. and might have put the wrong version..... and have not been able to trace my steps back....
nkk71 said:
1- are you on Win 8.1?
2- i thought you said the touchscreen being messed up, was due to an unnamed offspring
Click to expand...
Click to collapse
abdoulwane said:
I am on Windows 7 Ultimate with service Pack 1 actually.
I am suspecting one of my boys,... although I have no proof or sign of the htc being dropped. It coincided with my installation of TouchRecover (6 months ago).. and might have put the wrong version..... and have not been able to trace my steps back....
Click to expand...
Click to collapse
Win7 is good, go for ruu.zip method using the one mentioned in my guide,
no need to go through all of it, just post #1 (in particular the FAQs) then post #3 (the RUU.ZIP flashing).... no need for locking/s-on etc, just flash the ruu.zip for your MID.
Thanks a lot. I presume this one?
RUU Zip M7 UL JB 50 HTC Europe 1.28.401.7 Radio 4A.13.3231.27 10.31.1131.05 Release 310878 Signed
nkk71 said:
Win7 is good, go for ruu.zip method using the one mentioned in my guide,
no need to go through all of it, just post #1 (in particular the FAQs) then post #3 (the RUU.ZIP flashing).... no need for locking/s-on etc, just flash the ruu.zip for your MID.
Click to expand...
Click to collapse
I had trouble flashing a RUU.exe the other day, tried several versions and after I managed to downgrade my hboot to 1.44 it worked 1st time
Sent from my HTC One using Tapatalk
Thanks Guys, The Zip method worked.. however. I STILL do not have touchscreen functionality on the bottom two thirds of my screen. In xx.401.x for now.. I may go back to Google.. and send my phone for repair... or buy a used HTC One M7. Repair costs the same!!!!
seanicca said:
I had trouble flashing a RUU.exe the other day, tried several versions and after I managed to downgrade my hboot to 1.44 it worked 1st time
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
nkk71 said:
ok, but what does "it" refer to?
Click to expand...
Click to collapse
He means the fastboot command for flashing the RUU, right?

[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.

Categories

Resources