Related
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
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.
I have an HTC One M8, and I installed Cyanogenmod 12.1 (I followed their guide and did HTCdev Unlock). For a little while, LTE was working fine with my phone, but then about a couple of weeks ago, my LTE connection stopped working, and it hasn't worked since. So ultimately that's the problem I'm looking to solve.
I had backed up my HTC factory ROM and restored that to see if LTE would work there. That's when I found that it wants me to do an update, but the update reboots me into TWRP and doesn't work. My thought is that to solve this, I will need to apply the update somehow, and if that's the case, then I could use some help figuring out how to do that. (I'm trying to run "Update Profile".)
If you have other ideas of what I can do to fix LTE, then I'm open to hearing them as well.
Thanks!
You need to install stock recovery to enable the update to install.
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
komi_9 said:
Thanks for the response. I'm trying to work out from your signature links (thanks for those!) how to do that.
I found the link to the Stock Recoveries. In there, I found a bunch of different versions. The version numbers seemed to match my version-main: 2.16.651.4, so I should use Stock_2.16.651.4_recovery.img, correct?
And I'm back on CM now, so should I restore the stock before doing this? It seems so, since I don't know if the other recovery will be able to restore it.
So I will:
1) restore the stock ROM
2) flash the stock recovery
3) boot up and do the system update
4) update Profile and PRF (I'm hoping this fixes the LTE issue)
5) put TWRP back on
6) restore CM
Does this sound right? And to put TWRP back on, do I just do the same fastboot flash recovery command, but with the TWRP file?
Thanks so much for the help!
Click to expand...
Click to collapse
Yup sounds correct except being you are on 2.16 there will be a few updates you will need to do to get current.
I went through the process, and each step went fine (you were right about having to update a few times), but LTE is still not working in CM when I switched back over. It is working on the Stock ROM side of things; that's how I did my OTA update. (At least it says LTE in the status bar, so I assume that's what it's using, as opposed to just defaulting to LTE but switching to 3G when LTE is not present.)
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Thanks for the help again!
Any other suggestions that I should try? Could this be a Cyanogenmod issue? Should I ask in their forums?
Click to expand...
Click to collapse
I don't use CM so can't answer but yeah your best bet would be to ask in their forum.
And another question if I need to go through this again in the future. The stock software is now 4.(something). This doesn't match any of the Stock recovery version numbers in that zip file. Do I need to go locate the proper recovery, or can I use the latest (3.30.651.2)? (And what does the HK suffix on some of the recoveries mean?)
Click to expand...
Click to collapse
If you took all the update to make you current you should have the latest stock recovery. You can always pull the stock recovery from the latest Full Firmware zip.
HK = Harmon Kardon Edition
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
komi_9 said:
Do you use a custom ROM? Or do you have a suggestion of a different one? I'd like to experiment with something else to see if this is specific to CM.
Click to expand...
Click to collapse
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Sloth said:
I use LeeDroid...never had any issues with it.
http://forum.xda-developers.com/htc-one-m8/development/rom-leedroid-one-m8-l-v1-0-5-t3019102
Click to expand...
Click to collapse
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
komi_9 said:
I tried installing that, but I get an installer status 7 error. When I boot the phone up, it just takes me back into recovery. I'm not sure what's going on there.
Click to expand...
Click to collapse
Have you updated your twrp recently?
I have 2.8.7.0 downloaded from here: https://dl.twrp.me/m8/twrp-2.8.7.0-m8.img
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
komi_9 said:
I just remembered that I didn't do a full wipe. Could this be the problem? I was scared that it would wipe my personal data. If I've done a backup to an SD card, can I restore that and get back to my original set up with a full wipe?
Click to expand...
Click to collapse
Yes that might be the problem. A full wipe shouldn't wipe anything important.
If you have a backup and you need to use it you will be back to the ROM you made the backup of.
Sent from a Glade Plugin.
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
komi_9 said:
It still didn't work. I tried some of the steps advised here: http://forum.xda-developers.com/showthread.php?t=2728644
I did a factory reset from TWRP, then I specifically wiped the system folder, then I did a full wipe withing the Leedroid installer. Also, I put the Leedroid zip file in internal storage instead of my SD card. But regardless I get the same error. Here's my log file:
Code:
AROMA Installer version 2.70RC2
(c) 2013 by amarullz xda-developers
ROM Name : LeeDrOiD One M8 S7
ROM Version : V7.4.2
ROM Author : LeeDrOiD
Device : HTC One M8
Start at : Wed Oct 28 12:11:04 2015
I:emmc_scan_partitions:[partition_count:47] [allocat_num:128]
bad option "flags=display="Cache""
skipping malformed recovery.fstab line: /cache ext4 /dev/block/platform/msm_sdcc.1/by-name/cache flags=display="Cache"
bad option "flags=display="System""
skipping malformed recovery.fstab line: /system ext4 /dev/block/platform/msm_sdcc.1/by-name/system flags=display="System"
bad option "flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra"
skipping malformed recovery.fstab line: /data ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata flags=encryptable=/dev/block/platform/msm_sdcc.1/by-name/extra
bad option "flags=display="Recovery""
skipping malformed recovery.fstab line: /recovery emmc /dev/block/platform/msm_sdcc.1/by-name/recovery flags=display="Recovery"
bad option "flags=display="Micro"
skipping malformed recovery.fstab line: /external_sd vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 flags=display="Micro SDcard";storage;wipeingui;removable;andsec
bad option "flags=display="USB-OTG";storage;wipeingui;removable"
skipping malformed recovery.fstab line: /usb_otg vfat /dev/block/sda1 /dev/block/sda flags=display="USB-OTG";storage;wipeingui;removable
bad option "flags=display="SD-Ext";wipeingui;removable"
skipping malformed recovery.fstab line: /sd-ext ext4 /dev/block/mmcblk1p2 flags=display="SD-Ext";wipeingui;removable
recovery filesystem table in updater...
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/block/platform/msm_sdcc.1/by-name/misc (null) 0
2 /boot emmc /dev/block/platform/msm_sdcc.1/by-name/boot (null) 0
3 /devlog ext4 /dev/block/platform/msm_sdcc.1/by-name/devlog (null) 0
Now Flashing LeeDrOiD to your HTC One M8
Please be patient
1st boot may take a few minutes
about to run program [/sbin/mount] with 2 args
mount: mounting /dev/block/mmcblk0p47 on /data failed: Device or resource busy
run_program: child exited with status 255
about to run program [/sbin/mount] with 2 args
Extract scripts and tools
Wiping Data without /media
about to run program [/tmp/wipe.sh] with 1 args
Writing Data
about to run program [/tmp/fbrem.sh] with 1 args
chattr: stat /data/data/com.facebook.katana/databases/qe_db: No such file or directory
Writing System
about to run program [/sbin/mke2fs] with 6 args
mke2fs 1.42.9 (28-Dec-2013)
Discarding device blocks: 4096/688128528384/688128 done
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
172032 inodes, 688128 blocks
0 blocks (0.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=704643072
21 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912
Allocating group tables: 0/21 done
Writing inode tables: 0/21 done
Creating journal (16384 blocks): done
Writing superblocks and filesystem accounting information: 0/21 done
about to run program [/sbin/mount] with 2 args
Installing Hacked Linker
Carrier Selection
Sprint
Customising HTC Apps
Installing HTC Car & HTC Speak
Customising Widgets
Customising Google and Other Apps
Installing Google CloudPrint
Installing Google Drive
Installing Google Search
Installing Adaway
Installing Es File Explorer
Installing Facebook
Removing Kid Mode
Extras
Disabling Exchange Mail Security
about to run program [/tmp/tweaks.sh] with 4 args
ERROR: DataBase /data/data/com.android.providers.settings/databases/settings.db not found!
Applying Big Caller Photo
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/Telephony/Telephony.apk
updating: resources.arsc (deflated 74%)
Zipaligning /system/priv-app/Telephony/Telephony.apk
Shrinking Nav Bar To 42 DPI
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/framework/framework-res.apk
updating: resources.arsc (deflated 77%)
Zipaligning /system/framework/framework-res.apk
about to run program [/tmp/res_patch.sh] with 2 args
Processing /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
updating: resources.arsc (deflated 79%)
Zipaligning /system/priv-app/HtcContactsDialer/HtcContactsDialer.apk
Creating toolbox symlinks
Installing busybox
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
script aborted: set_perm: some changes failed
set_perm: some changes failed
Installer Error (Status 7)
End at : Wed Oct 28 12:12:56 2015
Click to expand...
Click to collapse
V7.4.2 is not the latest version...try the latest and see if it makes a difference. Usually status 7 error means the updater script is out of date (if I remember correctly).
When I do a full wipe I choose Advance Wipe then check the boxes next to cache/dal cache/data/system. From my experience wiping in twrp and then wiping again in Aroma usually causes problems. I prefer the twrp method myself.
I also put anything I'm going to flash on the EXT sdcard.
The 7.4.3 version is only available as a patch to 7.4.2 as far as I can tell. The full download is only available in 7.4.2. Or at least that's all I see.
Anyway, the point is moot now since I seem to have gotten LTE working. I went into APN settings and the option CDMA 0 was selected. Any of the other options pop me over to the Sprint LTE Internet option, but that one will just sit there and not work. I'm not quite sure how I got stuck on that APN. But oh well, since it's working now.
I really appreciate all the help! One day I might embark on trying out different ROMs again, but for now I'm happy that CM is working out OK.
Cool glad you got it sorted.
[Q] Managed to delete everything, "could not detect filesystem" so can't flash anythi
Hi there!
So, being an idiot, I managed to wipe my phone completely whilst attempting to upgrade my firmware.
Now, I can't flash anything, as when I try to do so I get the following text...
Code:
Flashing AICP System files...
could not detect filesystem for /dev/block/platform/msm_sdcc.
1/by-name/system, assuming ext4 mount: failed to mount /dev/
block/platform/msm_sdcc. 1/by-name/system at system:
no such volume
script succeeded: result was [0.200000]
Updating partition details...
Can't check permissions
after Factory Reset
Please boot rom and try
again after you reboot into
recovery.
Done
Unfortunately, when I then reboot, I don't have an OS so it just sits at the HTC logo.
After a lot of effort, I did manage to get a rom onto my internal memory, but as shown above, it just won't let me flash it
Any ideas what is wrong and how it can be fixed?
EDIT1: Additional information:
Code:
M7_UL PVT SHIP S-ON RH
HBOOT-1.55.0000
RADIO-4A.21.3263.04
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048Mb
EDIT2: Tried sideloading, this didn't work either
EDIT3: Using CWM recovery instead of TWRP seems to have worked
?
How did you manage to erase it like that? 0_o
Tried
fastboot format system
?
After format, try flashing a ROM.
Lavanoid said:
How did you manage to erase it like that? 0_o
Tried
fastboot format system
?
After format, try flashing a ROM.
Click to expand...
Click to collapse
I'm not entirely sure how I managed this.
When trying fastboot format system I got the following
Code:
Creating filesystem with parameters:
Size: 1946152960
Block size: 4096
Blocks per group: 32768
Inodes per group: 7920
Inode size: 256
Journal blocks: 7423
Label:
Blocks: 475135
Block groups: 15
Reserved block group size: 119
Created filesystem with 11/118800 inodes and 15607/475135 blocks
target reported max download size of 1526722560 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.016s
Hhm
I think I read another post with a similar problem, earlier today in this forum. If you look around the Q&A forum, you should be able to find it.
Saidinsaidar said:
Code:
Flashing AICP System files...
[COLOR="Red"]could not detect filesystem for /dev/block/platform/msm_sdcc.
1/by-name/system[/COLOR], assuming ext4 mount: failed to mount /dev/
block/platform/msm_sdcc. 1/by-name/system at system:
no such volume
Click to expand...
Click to collapse
Looks like you are simply not using the right recovery version for the rom you want to flash. Roms that need "by-name" partitions mounting (lie all Cyanogenmod based roms) requires twrp 2.7.1.1+ or CWM 6.0.4.8+.
alray said:
Looks like you are simply not using the right recovery version for the rom you want to flash. Roms that need "by-name" partitions mounting (lie all Cyanogenmod based roms) requires twrp 2.7.1.1+ or CWM 6.0.4.8+.
Click to expand...
Click to collapse
That's odd, I'm using the most up to date version of TWRP, downloaded and flashed with fastboot this evening :/
EDIT: Changed to CWM recovery and tried flashing, seems to have been successful. Hooray!
My device: HTC One M7 Android 4.2.2, S-ON, Root, CWM recovery (years old version)
My ultimate goal was: Get xposed framework. Install via app failed after rebooting due to S-ON, so I wanted to install through recovery. (this is irrelevant to the issue IMO)
What I tried to get there: Decrypting my /data partition in adb (because CWM doesn't support it)
What I found: https : // forumDOTfairphoneDOTcom/t/how-to-mount-encrypted-data-in-recovery/25724
Everything(!) I actually did: (commands after $ means executed on host machine (ubuntu), prefixed by ~ # means run on phone in adb shell)
$ adb shell
~ # setprop ro.crypto.state encrypted
~ # vdc cryptfs checkpw "<wrong password>"
200 0 1
~ # mount /dev/block/dm-0 /data
mount: mounting /dev/block/dm-0 on /data failed: no such file or directory
(( a couple commands like ls and cat to find out what my /data partition should be ))
(( ended up finding out in fstab that it's mmcblk0p37 ))
~ # mount /dev/block/mmcblk0p27 ((accidentally wrong one))
mount: mounting /dev/block/mmcblk0p27 on /data failed: Invalid argument
~ # mount /dev/block/mmcblk0p37
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
(( notice i entered wrong password ))
~ # vdc cryptfs checkpw "<right password>"
200 0 2
~ # mount /dev/block/mmcblk0p37
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
(( a couple more tried of the previous two commands for no legit reason ))
~ # mount -o rw,remount /dev/block/mmcblk0p37
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
(( exit adb shell ))
(( execute $ adb remount )) (( as google suggested (on host machine, not in adb shell obv) ))
$ adb shell
~ # mount -t ext2 /dev/block/mmcblk0p37 (( accidentally wrong fstype ))
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
~ # mount -t ext4 /dev/block/mmcblk0p37
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
~ # mount -t ext4 /dev/block/mmcblk0p27 (( why not? ))
mount: mounting /dev/block/mmcblk0p37 on /data failed: Invalid argument
~ # exit (( i got frustrated ))
Before I did all this the phone was working normally (after install xposed via app (which gave me xposed version 3x because I had that one previously installed via receovery. But I wanted the newest (5x) so I went all that way)). After I did all these steps - which to me are readonly things which shouldn't brick anything - I got frustrated and wanted to give up, so I rebooted. Now everytime I enter the - 100% correct - password, it tells me to "try again" (guessing it means wrong password? idk).
The whole xposed stuff is irrelevant in my opinion, because after I've installed it using the xposed installer (APK) I rebooted twice and decryption worked fine both times.
What the hell have I done (I'd say I'm a linux expert and I honestly don't see how I could've possible broken anything by what I did) and how can I fix it?
UPDATE: I got myself the cryptheader from the "extra" partition using the read_emmc vulnerability. That way I got the encrypted key and salt. (cryptheader)
I then used this and a modified bruteforce script to check if my right password is still right. Result: It doesn't seem so.
My password contained special characters and was 15 chars long, bruteforce is not an option.
Is there anyway what I did could've changed the password? If so, can I reproduce and get the new key somehow? The cryptheader is not corrupted and still intact. The /data partition (encrypted) is not corrupted and still intact. (I assume this because the encrypted partition's hexdump starts with "This is an encrypted partition", which is a HTC easter egg.)
htcuser311 said:
UPDATE: I got myself the cryptheader from the "extra" partition using the read_emmc vulnerability. That way I got the encrypted key and salt. (cryptheader)
I then used this and a modified bruteforce script to check if my right password is still right. Result: It doesn't seem so.
My password contained special characters and was 15 chars long, bruteforce is not an option.
Is there anyway what I did could've changed the password? If so, can I reproduce and get the new key somehow? The cryptheader is not corrupted and still intact. The /data partition (encrypted) is not corrupted and still intact. (I assume this because the encrypted partition's hexdump starts with "This is an encrypted partition", which is a HTC easter egg.)
Click to expand...
Click to collapse
I'm far from being a linux expert but the simplest would be to factory reset using htc's recovery to remove /data encryption and start from scratch (unless you have some really important data that must be saved from your /data partition)
alray said:
I'm far from being a linux expert but the simplest would be to factory reset using htc's recovery to remove /data encryption and start from scratch (unless you have some really important data that must be saved from your /data partition)
Click to expand...
Click to collapse
I have decided to give up on trying and did a "factory reset" (formatted /data and /data/sdcard through CWM, rebooted, set up device for first use, formatted /data again through CWM to result in clean system).
Fun-fact: Before I did what bricked the system I actually made a backup. The device (µSD-Card) decided to go corrupted filesystem though. I managed to recover most of the files but the /system partition backup (which might have saved me) remained corrupted. I was able to restore all my personal data though, so doing a factory reset wasn't that bad for me.