Database Develop

Please help unbrick a Telus HTC One

Hi everyone.
I unlocked the bootloader and rooted a Telus HTC One. But the latest flash went wrong and I went into bootloop. Somehow, I seem to have gotten myself into a situation where there's no ROM installed. I can still get into Bootloader and Recovery. When I try to start the phone, it's stuck at "HTC Quietly Brilliant" screen.
I've tried factory resetting, wiping everything, relocking the bootloader and loading the Factory RUU Zip using the All-In-One tool kit by Hasoon, and sideloading a ROM. Nothing seems to work. I also managed to push a ROM to the phone using the adb push command. When I try to install it using TWRP, I get an error msg "Unable to open zip file." It failed using CWM recovery as well.
When I plug the phone into a computer, it recognizes something is plugged in. But I can't open the drive at all. I get error msgs when I try to mount sdcard, system, data, anything. Things don't seem to be mounting/recognized at all. HTC sync and drivers are installed.
Experts, what else can I try?

Try downloading a Telus clean nandroid backup. Then go back into recovery (depends of what nandroid you get, make sure you have the right recovery, so if you download a CWM nandroid use CWM).

G-Bus said:
Try downloading a Telus clean nandroid backup. Then go back into recovery (depends of what nandroid you get, make sure you have the right recovery, so if you download a CWM nandroid use CWM).
Click to expand...
Click to collapse
Thanks for the suggestion. Not having any luck finding a Telus nandroid. Would it make matters worse if I try to restore from a non-Telus nandroid? My phone can't mount the /sdcard right now. Suppose I'll have to adb push it to the phone again?

runlsd said:
Thanks for the suggestion. Not having any luck finding a Telus nandroid. Would it make matters worse if I try to restore from a non-Telus nandroid? My phone can't mount the /sdcard right now. Suppose I'll have to adb push it to the phone again?
Click to expand...
Click to collapse
You don't mount the sdcard in HTC One you mount the data partition.
Also what happens if you sideload a ROM?
PHP:
adb sideload <ROM>
Have you tried erasing cache after installing a ROM if successful?

Riyal said:
You don't mount the sdcard in HTC One you mount the data partition.
Also what happens if you sideload a ROM?
PHP:
adb sideload <ROM>
Have you tried erasing cache after installing a ROM if successful?
Click to expand...
Click to collapse
When I sideloaded, It said
Can't Open /sdcard/rom.zip" (bad).
Installation aborted
Sideloading now gives me this error
failed to open driver control: No such file or directory
Restarting adbd
hmm, okay. I thought since recovery says "Install zip from sdcard" i thought /sdcard needed to be mounted. /data is mounted at the moment. No connectivity between computer and the phone unless through the All-in-one kit.

Riyal said:
Have you tried erasing cache after installing a ROM if successful?
Click to expand...
Click to collapse
And I haven't had successfully installed a ROM since I bricked the phone.

Install a custom ROM and kernel on your USB from the computer, mount the USB in Twrp using the otg cable. Flash ROM, if it doesnt boot, flash the kernel.
Flashing the kernel fixed it for me.
Another way is to use an adb pusher app and transfer thevfiles to your SD card.
Sent from my Nexus 10 using XDA Premium HD app

Thanks everyone. Somehow it sideloaded when I tried for the twentieth time.

[Q] Can only access bootloader. Soft brick?

Hey guys,
Today I attempted to root my HTC One. I successfully unlocked it and successfully flashed twrp 2.5 onto my phone. Without creating a backup and after flashing superuser and arhd 11.0 my phone would only boot into bootloader. Then I found I had trouble going back into recovery. I tried reflashing twrp and it worked and led me back into recovery. I was unable to find any of the ROMs I put into the internal memory and I get an error that says I am unable to mount data. I've tried flashing cwm recovery, which only lead to booting into bootloader, and then back to twrp which worked at first, but now I can't get either to work. I've been at this for hours. Hope any of you guys could help me out. Thanks in advance!
Also, I think my problem began by trying to flash arhd 11.0 from stock without doing a full wipe.
Update: Was able to get twrp to work again by clearing cache, but still unable to mount data.
This is an error i see inside twrp.
E : Unable to mount '/data'
E : Unable to recreate /data/media folder.
Updating partition details...
E : Unable to mount '/cache'
E : Unable to mount '/data'
E : Unable to mount internal storage.
E : Unable to mount /data/media during GUI startup
E : Unable to mount '/cache'
E: TWFunc : : Copy_Log -- Can't open destination
etc...
Click to expand...
Click to collapse
Update: SOLVED. Tried flashing Viper Rom and it worked great.

I believe that you install ARHD 11 from a 4.1 based rom, right? If that's the case, moving from 4.1 to 4.2 will mess up your data structure a bit. Because you have flashed arhd 11, all the rom files you had put earlier on 4.1 will be at other folder. My advice is you boot into twrp, open adb sideload (advance menu). On your computer use "adb sideload rom.zip" (rom.zip is the name of the rom you wanna flash). After it loaded the rom to the sd card, reboot to bootloader and you should see a file named sideloaded.zip. flash it. After finish, clear cache and reboot system.
or you can search in media/0
hope it helps

ryryzz said:
I believe that you install ARHD 11 from a 4.1 based rom, right? If that's the case, moving from 4.1 to 4.2 will mess up your data structure a bit. Because you have flashed arhd 11, all the rom files you had put earlier on 4.1 will be at other folder. My advice is you boot into twrp, open adb sideload (advance menu). On your computer use "adb sideload rom.zip" (rom.zip is the name of the rom you wanna flash). After it loaded the rom to the sd card, reboot to bootloader and you should see a file named sideloaded.zip. flash it. After finish, clear cache and reboot system.
or you can search in media/0
hope it helps
Click to expand...
Click to collapse
So I should sideload and flash a 4.1 based rom or a 4.2?
I've tried sideloading ARHD 11 and it brings me into the same bootloader loop. Could you send me a link to a ROM that may work?
Here's the steps I am taking if it helps;
1. fastboot erase cache
2. fastboot flash recovery twrp.img
3. go into recovery
4. adb sideload arhd11
5. reboot into recovery
6. flash sideload
7. reboot system
8. gives me a message saying my phone is not rooted would I like to install SuperSU now?
9. regardless of if i put 'do not install' or 'swipe to install' phone reboots into bootloader and I start over with the same problem
Click to expand...
Click to collapse

zasuncion said:
So I should sideload and flash a 4.1 based rom or a 4.2?
I've tried sideloading ARHD 11 and it brings me into the same bootloader loop. Could you send me a link to a ROM that may work?
Here's the steps I am taking if it helps;
Click to expand...
Click to collapse
Can you access recovery?
If yes, adb push name_of_rom.zip /sdcard/
rom will now be on your sdcard after the transfer. install it.
all roms using aroma installer crash sometimes, just keep trying.
edit: IF you can't find it, select install zip from sideload in recovery and command
adb sideload name_of_rom.zip
after the transfer it will begin to install automatically - you shouldn't need to reboot after a sideload.

redbull123 said:
Can you access recovery?
If yes, adb push name_of_rom.zip /sdcard/
rom will now be on your sdcard after the transfer. install it.
all roms using aroma installer crash sometimes, just keep trying.
Click to expand...
Click to collapse
Yes, I can access recovery. Just tried this. After flashing ARHD11 again I am still rebooting into bootloader.
Maybe it's just the ROM itself that I'm having trouble with? Could anyone direct me to one that will work for sure in my case?
Also after every flash, when I choose to reboot, twrp gives me a message saying my phone is not rooted and if I should install SuperSU. Should I say yes or not install? or is there a problem with flashing the ROM?

zasuncion said:
Yes, I can access recovery. Just tried this. After flashing ARHD11 again I am still rebooting into bootloader.
Maybe it's just the ROM itself that I'm having trouble with? Could anyone direct me to one that will work for sure in my case?
Also after every flash, when I choose to reboot, twrp gives me a message saying my phone is not rooted and if I should install SuperSU. Should I say yes or not install? or is there a problem with flashing the ROM?
Click to expand...
Click to collapse
So ARHD goes through and installs (as in gets to 100% in aroma) then reboots to bootloader?
Sent from my HTC One using xda premium

redbull123 said:
So ARHD goes through and installs (as in gets to 100% in aroma) then reboots to bootloader?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Yes. And the only way to get back into recovery from there is to reflash. I also can't use cwm, I can only use twrp. If that means anything.

[Q] 6 Hours later - Still Bricked.

Hello,
First and foremost I would like to give the important information away:
Phone: HTC One (M7)
Carrier: Rogers (I think same as AT&T?)
State: Unlocked, S-On, TWRP v2.7.1.0 installed, Hboot 1.57 and without an OS
The story:
Advance Wiped Everything:
So I didn't transfer the ROM before I used the "wipe" option in TWRP and deleted everything (using advanced wipe). Now I'm left with a phone that is "soft-bricked".
ADB Sideload
I rooted and installed TWRP my phone using QbKing77's guide
I tried googling a soultion and found a guide that told me to enter TWRP->Advanced->ADB Sideload and realized my phone cannot enter ABD sideload mode...so I'm like there must be another way, so I look up ADB push and again the same problem...it wont work. ADB shows: "error:device not found" in cmd.
Drivers
Now I think the problem is in the driver and I have reinstalled all the correct drivers (including Android SDK Google USB drivers). Then it strikes me that if the problem is with the drivers why was I able to use fastboot and not ADB?
RUU
After 4 hours of trying I gave up and was like lets try a RUU, same freaking problem. I get error code 155 which after researching seems to be pointing at my phone's bootloader not being "Re-locked" when the freaking screen says ***tampered*** re-locked****. So now I have unlocked it again and relocked the bootloader again, still no luck. I tried downloading different RUUs for both Rogers and AT&T and both give that exact same error even after "fastboot oem lock" command. After giving up on that I go back to try to entter ADB sideload mode via TWRP, I downloaded TWRP 2.5-2.7 and none of them would allow me to enter ADB sideload mode.. As of now its been 1 hour and TWRP still states: "Starting ADB sideload feature...".
Conclusion
If there is any way to get my phone to it's stock settings (IDC about the tampered, and relocked messages) I am all ears, I'm sorry if the information given isn't organized enough, but I'm very exhausted at this point. I will be more than happy to answer any more questions anybody might have.
Thanks!

haqsaber said:
Hello,
First and foremost I would like to give the important information away:
Phone: HTC One (M7)
Carrier: Rogers (I think same as AT&T?)
State: Unlocked, S-On, TWRP v2.7.1.0 installed, Hboot 1.57 and without an OS
The story:
Advance Wiped Everything:
So I didn't transfer the ROM before I used the "wipe" option in TWRP and deleted everything (using advanced wipe). Now I'm left with a phone that is "soft-bricked".
ADB Sideload
I rooted and installed TWRP my phone using QbKing77's guide
I tried googling a soultion and found a guide that told me to enter TWRP->Advanced->ADB Sideload and realized my phone cannot enter ABD sideload mode...so I'm like there must be another way, so I look up ADB push and again the same problem...it wont work. ADB shows: "error:device not found" in cmd.
Drivers
Now I think the problem is in the driver and I have reinstalled all the correct drivers (including Android SDK Google USB drivers). Then it strikes me that if the problem is with the drivers why was I able to use fastboot and not ADB?
RUU
After 4 hours of trying I gave up and was like lets try a RUU, same freaking problem. I get error code 155 which after researching seems to be pointing at my phone's bootloader not being "Re-locked" when the freaking screen says ***tampered*** re-locked****. So now I have unlocked it again and relocked the bootloader again, still no luck. I tried downloading different RUUs for both Rogers and AT&T and both give that exact same error even after "fastboot oem lock" command. After giving up on that I go back to try to entter ADB sideload mode via TWRP, I downloaded TWRP 2.5-2.7 and none of them would allow me to enter ADB sideload mode.. As of now its been 1 hour and TWRP still states: "Starting ADB sideload feature...".
Conclusion
If there is any way to get my phone to it's stock settings (IDC about the tampered, and relocked messages) I am all ears, I'm sorry if the information given isn't organized enough, but I'm very exhausted at this point. I will be more than happy to answer any more questions anybody might have.
Thanks!
Click to expand...
Click to collapse
first, do not use twrp 2.7.1.0 but 2.6.3.3 and use HTC divers not Google drivers. you will then be able to sideload or push a rom to your phone. Also make sure to use at least adb 1.0.29, sideload will not work on previous version.

alray said:
first, do not use twrp 2.7.1.0 but 2.6.3.3 and use HTC divers not Google drivers. you will then be able to sideload or push a rom to your phone. Also make sure to use at least adb 1.0.29, sideload will not work on previous version.
Click to expand...
Click to collapse
Thanks for your response.
I have flashed TWRP 2.6.3.3, and when I boot into recovery it asks me for a password? I was still unable to boot up ADB sideload (This time I get an error message instead of it failing to start all together). But I was able to access the adb shell and was able to push a custom rom into the device into /data/ and then tried installing it, which failed.
I flashed the ROM using this command: fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
then after the transfer was done typed: fastboot erase cache
as of now when I type adb devices into the command prompt my phone is being detected which is an improvement from last night! Thanks!

haqsaber said:
Thanks for your response.
I have flashed TWRP 2.6.3.3, and when I boot into recovery it asks me for a password? I was still unable to boot up ADB sideload (This time I get an error message instead of it failing to start all together). But I was able to access the adb shell and was able to push a custom rom into the device into /data/ and then tried installing it, which failed.
Click to expand...
Click to collapse
you don't have to use an adb shell to push a rom, only use adb normally from your computer with the phone booted in recovery. And the destination of the rom when you push it is not /data, its /sdcard
adb push name_of_rom.zip /sdcard/
when complete, select "install" in recovery and choose your rom.

alray said:
you don't have to use an adb shell to push a rom, only use adb normally from your computer with the phone booted in recovery. And the destination of the rom when you push it is not /data, its /sdcard
adb push name_of_rom.zip /sdcard/
when complete, select "install" in recovery and choose your rom.
Click to expand...
Click to collapse
The rom.zip is now in my /sdcard/ folder and when I try to install it I get the following error:
Code:
Updating partition details....
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
and my ADB version is 1.0.31
Edit: So I went in the mount option and noticed that "cache" was selected so I deselected it and tried to flash again and it just said
Code:
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
So now I'm thinking there must be something wrong with the ROM, so i'm downloading and will retry.
Code:
KitKat (Android 4.4.3 + HTC Sense 6.0)
Download Android Revolution HD 81.0
Nope, that didn't work either. Could it be that I need to put in that password first? If so what is the TWRP password?

haqsaber said:
The rom.zip is now in my /sdcard/ folder and when I try to install it I get the following error:
Code:
Updating partition details....
E:Unable to mount '/cache'
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
E:Unable to mount '/cache'
and my ADB version is 1.0.31
Edit: So I went in the mount option and noticed that "cache" was selected so I deselected it and tried to flash again and it just said
Code:
Error Flashing zip '/sdcard/rom.zip'
Updating partition details...
So now I'm thinking there must be something wrong with the ROM, so i'm downloading and will retry.
Code:
KitKat (Android 4.4.3 + HTC Sense 6.0)
Download Android Revolution HD 81.0
Nope, that didn't work either. Could it be that I need to put in that password first? If so what is the TWRP password?
Click to expand...
Click to collapse
looks like you have enabled data encryption in the OS...
in twrp wipe everything and format data
then push the rom again and install it.

alray said:
looks like you have enabled data encryption in the OS...
in twrp wipe everything and format data
then push the rom again and install it.
Click to expand...
Click to collapse
And that worked! Thank you so much!!

htc1 m7 keeps rebooting and won't detect network

Last week after software update using auto update Option , after installing the softare , the phone will keep rebooting and won't detect the network. I guess that my phone battery was low at the time of installation(10%) however it was connected to a charger. The problem is after turning on the phone, the phone will reboot after aprox. 1minute 50 seconds and the htc1 won't show network. The settings option in network setting would appear greyed out.
After this problem, I tried factory reset, no avail. Tried recovery from bootloader option but no avail.
Tried Using RUU- RUU_M7_U_JB_50_HTC_Europe_1.29.401.2_R_Radio_4A.14.3250.13_10.33.1150.01_release_311663_signed_2_4
Gives me error 155 in Update Utility.
After searching the threads, I decided to unlock and unroot the phone so that I could install any custom ROMs, did unlocking and unrooting.
My htc1 m7 with following specs now
Tampered
Unlocked
M7_U S-On
Hboot- 1.57.0000
Radio0- 4T.28.3218.04
OS-6.15.599.101
Android version 4.4.3 and Sense 6

Some guys recommended me to post my query on xda and I came here with lots of hopes. Unfortunately after couple of days no one from expert community has responded to this query.

htc1resetting said:
Some guys recommended me to post my query on xda and I came here with lots of hopes. Unfortunately after couple of days no one from expert community has responded to this query.
Click to expand...
Click to collapse
you not being ignored, their is no real answer to your problem
you can flash stock recovery for 6.15.599.101 if you can find it
and try the factory reset from stock recovery (not bootloader)
If you have TWRP 2.6.3.3 or higher on the phone now you can choose to format data and then push / sideload a 6.xx.xxx.x rom to the phone. Their are no 6.xx RUU so that's not an option. If the phone died during the update theirs no telling what partitions are damaged so the format data option is your first step

clsA said:
you not being ignored, their is no real answer to your problem
you can flash stock recovery for 6.15.599.101 if you can find it
and try the factory reset from stock recovery (not bootloader)
If you have TWRP 2.6.3.3 or higher on the phone now you can choose to format data and then push / sideload a 6.xx.xxx.x rom to the phone. Their are no 6.xx RUU so that's not an option. If the phone died during the update theirs no telling what partitions are damaged so the format data option is your first step
Click to expand...
Click to collapse
Firstly loads of thanks.
I have tried hard to find 6.15.599.101 RUU but no success.
I should use the second option to push 6.xx.xx.x rom, can you advice where can I find it. I get confused between kernel & OTA, which one is a ROM or neither one?

htc1resetting said:
Firstly loads of thanks.
I have tried hard to find 6.15.599.101 RUU but no success.
I should use the second option to push 6.xx.xx.x rom, can you advice where can I find it. I get confused between kernel & OTA, which one is a ROM or neither one?
Click to expand...
Click to collapse
Use this >> http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_81.0.zip
adb push Android_Revolution_HD-One_81.0.zip /sdcard/
or adb sideload Android_Revolution_HD-One_81.0.zip

My device is already formatted and I can only access bootloader(TWRP recovery) and if I boot the phone it gives me white htc screen.
I have downloaded the Android_Revolution_HD-One_81.0 fastboot works fine however adb won't detect my device. I have sdk tools from adroid.development and the latest version of adt tools.

htc1resetting said:
My device is already formatted and I can only access bootloader(TWRP recovery) and if I boot the phone it gives me white htc screen.
I have downloaded the Android_Revolution_HD-One_81.0 fastboot works fine however adb won't detect my device. I have sdk tools from adroid.development and the latest version of adt tools.
Click to expand...
Click to collapse
boot into TWRP
from the PC command prompt
type adb devices
if it's blank you need to reinstall the htc driver
if your device serial number shows it's working normally

When I use the adb command- where should my phone be? adbsideload? fastboot?
The adb won't detect my device even with htc drivers re-installed. When I use the adb sideload button in the TWRP , it stays there for ever.
Can we use fastboot command to flash the ROM, the way we flash recovery?

htc1resetting said:
When I use the adb command- where should my phone be? <<< TWRP
The adb won't detect my device even with htc drivers re-installed. When I use the adb sideload button in the TWRP , it stays there for ever.
Can we use fastboot command to flash the ROM, the way we flash recovery? << NO
Click to expand...
Click to collapse
Go to post 2 of @nkk71 superguide to install the drivers correctly > http://forum.xda-developers.com/showthread.php?t=2541082

Finally I was able to sideload- adb sideload Android_Revolution_HD-One_81.0.zip
After the sideload was 100% my phone was black screen, was no more in recovery TWRP.
What next step to take?
When I restarted the phone, it will again show the white HTC screen , won't go ahead and boot.
I am s-on and with TWRP 2.8.0.1 recovery.

htc1resetting said:
Finally I was able to sideload- adb sideload Android_Revolution_HD-One_81.0.zip
After the sideload was 100% my phone was black screen, was no more in recovery TWRP.
What next step to take?
When I restarted the phone, it will again show the white HTC screen , won't go ahead and boot.
I am s-on and with TWRP 2.8.0.1 recovery.
Click to expand...
Click to collapse
use TWRP 2.6.3.3

Using twrp, 2.6.3- I sideloaded adb sideload Android_Revolution_HD-One_81.0.zip
By the time sideload= 100% on cmd
Phone recovery-twrp showed, zip sign verification failed.
Screen shows as follows:
Updating partition details...
Starting ADB sideload feature...
Installing 'dataa/media/sideload.zip
checking for md5 flile....
skipping md5 check: no MD5 file found
Verifying zip signature...
E: zip signature verification failed.
I unchecked zip file verification from settings and this time was able to complete, followed the step by step installation. After the installation was complete, cleared cache and dalvi and performed system boot. The phone restarts but its again stuck at white htc screen.

clsA said:
use TWRP 2.6.3.3
Click to expand...
Click to collapse
Using twrp, 2.6.3- I sideloaded adb sideload Android_Revolution_HD-One_81.0.zip
By the time sideload= 100% on cmd
Phone recovery-twrp showed, zip sign verification failed.
Screen shows as follows:
Updating partition details...
Starting ADB sideload feature...
Installing 'dataa/media/sideload.zip
checking for md5 flile....
skipping md5 check: no MD5 file found
Verifying zip signature...
E: zip signature verification failed.

htc1resetting said:
Using twrp, 2.6.3- I sideloaded adb sideload Android_Revolution_HD-One_81.0.zip
By the time sideload= 100% on cmd
Phone recovery-twrp showed, zip sign verification failed.
Screen shows as follows:
Updating partition details...
Starting ADB sideload feature...
Installing 'dataa/media/sideload.zip
checking for md5 flile....
skipping md5 check: no MD5 file found
Verifying zip signature...
E: zip signature verification failed.
Click to expand...
Click to collapse
your download is corrupt ..download it again and md5 check your downloads

clsA said:
your download is corrupt ..download it again and md5 check your downloads
Click to expand...
Click to collapse
Made another attempt to sideload and it was successful, phone booted and rebooted. Phone turned on but again restarted after few seconds, the same way it was behaving earlier. Any suggestions?
I was checking htc Dev site, it has download section with my OS version no. 6.15.599.101- is there something I can do with this file to get my phone working.? m7u-3.4.10-ga936d02.zip is the file.
What are options to get RUU for 6.15.599.101 ?

htc1resetting said:
Made another attempt to sideload and it was successful, phone booted and rebooted. Phone turned on but again restarted after few seconds, the same way it was behaving earlier. Any suggestions?
I was checking htc Dev site, it has download section with my OS version no. 6.15.599.101- is there something I can do with this file to get my phone working.? m7u-3.4.10-ga936d02.zip is the file.
What are options to get RUU for 6.15.599.101 ?
Click to expand...
Click to collapse
You still never tried the stock recovery / factory reset
maybe you can extract it from that file
maybe @Danny201281 could help you check and repair your partition's if he has time

I tried factory reset and stock recovery at my first step long time ago. Only after failing, I tried the TWRP recovery and Android Revolution.

htc1resetting said:
My device is already formatted and I can only access bootloader(TWRP recovery) and if I boot the phone it gives me white htc screen.
I have downloaded the Android_Revolution_HD-One_81.0 fastboot works fine however adb won't detect my device. I have sdk tools from adroid.development and the latest version of adt tools.
Click to expand...
Click to collapse
When you say it's formatted are you sure about that?
Format Data is not the same as Factory reset or Wiping partitions. You need to use the Format Data option in twrp to be sure. So in case you haven't already and probably wouldn't hurt to do it again anyway.
Boot into twrp recovery Select the Wipe option and then Format Data option. You will be prompted to type "yes" to confirm. This will wipe everything from your device including your Rom and internal storage. Reboot to recovery to restore a completely new file system to your device.
Now with the phone still in twrp recovery, Select the Mounts option and uncheck all the boxes to unmount the partitions. Return to the twrp home screen (you don't need sideload mode for this part) in the command line type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk35
e2fsck -fvy dev/block/mmcblk36
e2fsck -fvy dev/block/mmcblk37
exit
Once that's done you can push or Sideload your Rom. Personally I prefer the push method but which is easiest for you is fine.
Ideally you want to do a factory reset with Stock recovery also but since you can't find one unless you can extract it from the file on HTC dev just try the above.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Danny201281 said:
When you say it's formatted are you sure about that?
Format Data is not the same as Factory reset or Wiping partitions. You need to use the Format Data option in twrp to be sure. So in case you haven't already and probably wouldn't hurt to do it again anyway.
Boot into twrp recovery Select the Wipe option and then Format Data option. You will be prompted to type "yes" to confirm. This will wipe everything from your device including your Rom and internal storage. Reboot to recovery to restore a completely new file system to your device.
Now with the phone still in twrp recovery, Select the Mounts option and uncheck all the boxes to unmount the partitions. Return to the twrp home screen (you don't need sideload mode for this part) in the command line type
Code:
adb shell
e2fsck -fvy dev/block/mmcblk35
e2fsck -fvy dev/block/mmcblk36
e2fsck -fvy dev/block/mmcblk37
exit
Once that's done you can push or Sideload your Rom. Personally I prefer the push method but which is easiest for you is fine.
Ideally you want to do a factory reset with Stock recovery also but since you can't find one unless you can extract it from the file on HTC dev just try the above.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
I was using the format data option before as well.
This time, followed the step by step procedure and installed the OS, the phone booted again but it restarts after sometime as it was at the beginning of the problem. Any suggestions?

htc1resetting said:
I was using the format data option before as well.
This time, followed the step by step procedure and installed the OS, the phone booted again but it restarts after sometime as it was at the beginning of the problem. Any suggestions?
Click to expand...
Click to collapse
When the phone is booting, does it take longer than normal? And does it bootloop before finally booting.
Unfortunately this is starting to sound like a hardware problem. After formatting the memory, repairing partitions with e2fsck and flashing a new Rom there's not much else can be done. If your still getting random reboots then something is defiantly a miss.
You can check your supersu app to make sure is properly rooted, by opening supersu, it may ask you to update the Binary's.
Or just flash this in recovery to make sure your on the latest.
http://download.chainfire.eu/452/SuperSU/
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

only HTC logo in Bootet android

hi,
i have the M7 of a mate of mine here.
i have the problem that after i manged to flash android revolution rom the phone boots in android but only showing the HTC page (no bootloop. ist in android. ADB SHELL works, locksreen works, when try to pull down the notification bar it shows the bar but not pulls down)
can anyone help me?

etsch said:
hi,
i have the M7 of a mate of mine here.
i have the problem that after i manged to flash android revolution rom the phone boots in android but only showing the HTC page (no bootloop. ist in android. ADB SHELL works, locksreen works, when try to pull down the notification bar it shows the bar but not pulls down)
can anyone help me?
Click to expand...
Click to collapse
USE TWRP 2.6.3.3 and flash the rom again

i use 2.6.3.3 already and tried flashing the rom 4 times

etsch said:
hi,
i have the M7 of a mate of mine here.
i have the problem that after i manged to flash android revolution rom the phone boots in android but only showing the HTC page (no bootloop. ist in android. ADB SHELL works, locksreen works, when try to pull down the notification bar it shows the bar but not pulls down)
can anyone help me?
Click to expand...
Click to collapse
adb reboot recovery
wipe/advanced-cache, dalvik, data, system-wipe
reinstall rom or choose another rom.

already tried
and other roms wont flash

etsch said:
already tried
and other roms wont flash
Click to expand...
Click to collapse
If you have tried everything why are you asking us ?

because you maybe have an idea what i can do.

etsch said:
because you maybe have an idea what i can do.
Click to expand...
Click to collapse
Try a different rom

etsch said:
because you maybe have an idea what i can do.
Click to expand...
Click to collapse
TWRP / WIPE / Format Data / Type yes
then reboot the phone and sideload a rom
sideload this Rom to your phone
http://www.androidrevolution.org/downloader/download.php?file=Android_Revolution_HD-One_84.0.zip
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot

at flashing other roms i will get different error messages
cyanogen mod - mount: faild to mount /dev/block/platform /msm.......... succed (but nothing changed)
reflection rom - mount: faild to mount /dev/block/platform /msm.......... - succed (but nothing changed)
dirty unicorn - mount: faild to mount /dev/block/platform /msm.......... - failed

etsch said:
at flashing other roms i will get different error messages
cyanogen mod - mount: faild to mount /dev/block/platform /msm.......... succed (but nothing changed)
reflection rom - mount: faild to mount /dev/block/platform /msm.......... - succed (but nothing changed)
dirty unicorn - mount: faild to mount /dev/block/platform /msm.......... - failed
Click to expand...
Click to collapse
Look up ^^
TWRP / Wipe /Format Data / Type Yes
adb sideload rom.zip

same again

etsch said:
same again
Click to expand...
Click to collapse
That's pretty much it .. Find a RUU for your CID / MID

i looked after that but there is no ruu for the CID (O2___102)
and i did not found an s off that works (tried rumrunner,revone . didnt find firewater, moonshine)

etsch said:
i looked after that but there is no ruu for the CID (O2___102)
and i did not found an s off that works (tried rumrunner,revone . didnt find firewater, moonshine)
Click to expand...
Click to collapse
Sunshine s-off is the only option and it requires your phone to be working to use it
are you sure you format data / reboot and then pushed a rom and tried to install it ?
are you md5 checking your downlaods / have you tried a different usb port / different usb cable

yes iam sure
after feels like 100 tries getting cyanogen mod on it the same error

etsch said:
yes iam sure
after feels like 100 tries getting cyanogen mod on it the same error
Click to expand...
Click to collapse
yeah you don't flash CM with TWRP you use CWM did you read the first post?
RECOVERY:
IMPORTANT!
A recovery update beginning with the Nightly ROM 20140501 will be required!
Guidance & Instructions can be found here
The easiest way to flash recovery is to use Flashify from the Play Store
Recovery Downloads:
TWRP 2.7.1.2
CWM Touch 6.0.4.8
ROM & GAPPS Downloads:
Read this before you flash a Milestone Build!
Click to expand...
Click to collapse
Download and install the latest TWRP Recovery for Int'l, AT&T, TMobile HTC One, Sprint HTC One or Verizon HTC One if you haven't already.
Copy the CM12 zip and the Gapps zip to your Internal Storage
Then reboot into TWRP recovery
Before flashing you might want to back up your data (Optional)
Then wipe Data, Cache and Dalvik-Cache before flashing
Next, tap Install, locate the CM12 zip and install it
Once that's finished tap install again, locate the Gapps zip and install it
If you are S-OFF, simply reboot and enjoy CM12, no need to follow the remaining steps. If you are S-ON tap Power and Reboot to bootloader
Then open the CM12 zip on a Computer, copy the boot.img to your fastboot folder
Connect your phone to your computer then open a Command window, "cd" to your fastboot folder and type the following: fastboot flash boot boot.img
Now type: fastboot reboot
You are finished. Enjoy CM12
Click to expand...
Click to collapse

cwm wont work and twrp 2.7.1.2 neither

etsch said:
at flashing other roms i will get different error messages
cyanogen mod - mount: faild to mount /dev/block/platform /msm.......... succed (but nothing changed)
reflection rom - mount: faild to mount /dev/block/platform /msm.......... - succed (but nothing changed)
dirty unicorn - mount: faild to mount /dev/block/platform /msm.......... - failed
Click to expand...
Click to collapse
etsch said:
cwm wont work and twrp 2.7.1.2 neither
Click to expand...
Click to collapse
Go back to TWRP 2.6.3.3 and try flash ARHD again if it fails, Take a pic of your phone with the error on the screen and post it here :good:

Here the error