Database Develop

[Q] Help!! Htc one bricked... Please HELP XDA

Hi! Everyone I recently got registered to XDA in order to get help as I now the devs are amazing and very friendly.
My problem is my Htc one got bricked when i tried to install a stock rom zip through CWM, phone was getting stuck at boot logo and was unable to get into recovery, but going through fastboot mode i managed to install twrp recovery. Major problem is that computer cannot detect my phone and the somehow my OS got deleted, in order to get RUU i cannot find the main version as it shows blank. I also tried adb push a custom carbon rom and zip install through twrp but it shows error. I dont know what to do...!!! Kindly help anyone.
bootloader data
M7_U PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.25.3263.21
OpenDsp-v32.120.274.0909
OS-
eMMC-boot 2048mb

Techcraze said:
Hi! Everyone I recently got registered to XDA in order to get help as I now the devs are amazing and very friendly.
My problem is my Htc one got bricked when i tried to install a stock rom zip through CWM, phone was getting stuck at boot logo and was unable to get into recovery, but going through fastboot mode i managed to install twrp recovery. Major problem is that computer cannot detect my phone and the somehow my OS got deleted, in order to get RUU i cannot find the main version as it shows blank. I also tried adb push a custom carbon rom and zip install through twrp but it shows error. I dont know what to do...!!! Kindly help anyone.
Click to expand...
Click to collapse
Wow, sounds like a headache! If I understand you, the problem may have started when you tried to install a .zip from HTC (a.k.a., RUU), instead of a custom ROM packaged as a .zip? (The formatting is very different, and I don't know what CWM/TWRP will do when given the wrong type.) Does this sound right? If so:
When the phone is booted into TWRP, can the computer detect it with "adb devices"? (You need to install the appropriate drivers, and install ADB, and run it properly so it doesn't just say "command not found".)
If I misunderstood your problem, have you tried using TWRP to back up your data, wipe data, wipe cache, and wipe dalvik cache, then reboot and wait 5 minutes for the phone to boot the first time?

fenstre said:
Wow, sounds like a headache! If I understand you, the problem may have started when you tried to install a .zip from HTC (a.k.a., RUU), instead of a custom ROM packaged as a .zip? (The formatting is very different, and I don't know what CWM/TWRP will do when given the wrong type.) Does this sound right? If so:
When the phone is booted into TWRP, can the computer detect it with "adb devices"? (You need to install the appropriate drivers, and install ADB, and run it properly so it doesn't just say "command not found".)
If I misunderstood your problem, have you tried using TWRP to back up your data, wipe data, wipe cache, and wipe dalvik cache, then reboot and wait 5 minutes for the phone to boot the first time?
Click to expand...
Click to collapse
Ya it happened something like that.
When the phone is booted into TWRP and by adb devices command I get the below
C:\fastboot>adb devices
List of devices attached
I have tried backingup by TWRP adn wiped data cache dalvik cache and reboot, but it gets rebooting into recovery
Computer doent detect the sdcard, TWRP shows no OS!
I tried ADB sideload to install custom rom but it shows error..

Techcraze said:
C:\fastboot>adb devices
List of devices attached
Click to expand...
Click to collapse
Seems like maybe you don't have the right drivers. Your phone isn't being detected. No ADB stuff (push or sideload) will work until you sort that out. (I don't use Windows, so I can't help much when it comes to driver info.)

fenstre said:
Seems like maybe you don't have the right drivers. Your phone isn't being detected. No ADB stuff (push or sideload) will work until you sort that out. (I don't use Windows, so I can't help much when it comes to driver info.)
Click to expand...
Click to collapse
I have installed all right drivers, i am able to push or sideload files but not able to execute as it shows error when installing zip through TWRP and shows no OS.
below is getvar all
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36JW9A0222
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4072mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 2.240s
Please anyone help!!

Techcraze said:
it shows error when installing zip through TWRP and shows no OS.
Click to expand...
Click to collapse
I don't know what it means when version-main is blank, but I'm more interested in the TWRP error.

Techcraze said:
I have installed all right drivers, i am able to push or sideload files but not able to execute as it shows error when installing zip through TWRP and shows no OS.
below is getvar all
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
Please anyone help!!
Click to expand...
Click to collapse
1- edit your post and remove IMEI, you shouldn't share that information publicly!!
2- then:
get TWRP from:
2.6.3.3: http://techerrata.com/browse/twrp2/m7
or 2.6.3.4: http://techerrata.com/browse/twrp2/m7ul
(make sure MD5 is correct, that site does not play nice with download managers)
2.7.0.4b: http://forum.xda-developers.com/showthread.php?t=2708134
in bootloader/FASTBOOT USB:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
enter recovery, now trwp, if adb devices doesn't show your phone, then go here: http://forum.xda-developers.com/showthread.php?p=52135024&postcount=2
and fix Windows Device Manager as mentioned in FAQ#2, then you can continue.

[Q] How do I get my phone operable again?

Hi Guys,
Sorry to start another thread like this, but I've read and tried everything I can find on here and nothing seems to be working, in fact I seem to have made things worse.
Long story short I did the whole HTC dev unlock thing and all was fine, then I installed TWRP and pushed SuperSU, after this my phone would boot up and run for about 1 minute then reboot and go through the same routine (I let this go on for a few hours before I gave up)
Since I have tried installing different ROMs and changed the Recovery several times but I am in a position where I can boot into recovery but nothing else, unfortunately I don't even seem to be able to install any ROMs any more, I just pushed ARHD to the phone but as soon as I try to install it TWRP comes back with a failed message.
I'm sure this situation must be recoverable as I can still access recovery and fastboot but I seem to be going round in circles at the moment and getting nowhere so any help or pointers would be greatly appreciated, if there is any specific information that you need then just ask.

dirkgently68 said:
Hi Guys,
Sorry to start another thread like this, but I've read and tried everything I can find on here and nothing seems to be working, in fact I seem to have made things worse.
Long story short I did the whole HTC dev unlock thing and all was fine, then I installed TWRP and pushed SuperSU, after this my phone would boot up and run for about 1 minute then reboot and go through the same routine (I let this go on for a few hours before I gave up)
Since I have tried installing different ROMs and changed the Recovery several times but I am in a position where I can boot into recovery but nothing else, unfortunately I don't even seem to be able to install any ROMs any more, I just pushed ARHD to the phone but as soon as I try to install it TWRP comes back with a failed message.
I'm sure this situation must be recoverable as I can still access recovery and fastboot but I seem to be going round in circles at the moment and getting nowhere so any help or pointers would be greatly appreciated, if there is any specific information that you need then just ask.
Click to expand...
Click to collapse
post the output of "fastboot getvar all' (exclude imei and serialno)
what recovery are you using? What version number?

dirkgently68 said:
Hi Guys,
Sorry to start another thread like this, but I've read and tried everything I can find on here and nothing seems to be working, in fact I seem to have made things worse.
Long story short I did the whole HTC dev unlock thing and all was fine, then I installed TWRP and pushed SuperSU, after this my phone would boot up and run for about 1 minute then reboot and go through the same routine (I let this go on for a few hours before I gave up)
Since I have tried installing different ROMs and changed the Recovery several times but I am in a position where I can boot into recovery but nothing else, unfortunately I don't even seem to be able to install any ROMs any more, I just pushed ARHD to the phone but as soon as I try to install it TWRP comes back with a failed message.
I'm sure this situation must be recoverable as I can still access recovery and fastboot but I seem to be going round in circles at the moment and getting nowhere so any help or pointers would be greatly appreciated, if there is any specific information that you need then just ask.
Click to expand...
Click to collapse
you'll most likely have to format data and push the file to the phone again. This will wipe the entire phone same as a RUU

alray said:
post the output of "fastboot getvar all' (exclude imei and serialno)
what recovery are you using? What version number?
Click to expand...
Click to collapse
Fastboot getvar all returns this :-
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.12.161.8
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: VODAP001
battery-status: good
battery-voltage: 4315mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Recovery is TWRP v2.8.0.2
Thanks for your response!

dirkgently68 said:
Fastboot getvar all returns this :-
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.28.3218.04
version-cpld: None
version-microp: None
version-main: 6.12.161.8
version-misc: PVT SHIP S-ON
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: VODAP001
battery-status: good
battery-voltage: 4315mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-6d8a0b9b
hbootpreupdate: 11
gencheckpt: 0
Recovery is TWRP v2.8.0.2
Thanks for your response!
Click to expand...
Click to collapse
Afaik ARHD must be installed using twrp 2.6.3.3 (higher versions of twrp are not compatible, or at least, they are not all compatible)
flash twrp 2.6.3.3
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then in twrp selsect "install", browse your phone storage to find your ARHD zip file, select it and then swipe to flash.
If this fail again, format data like cisa said above, but you'll have to push the rom to your phone storage again.

alray said:
Afaik ARHD must be installed using twrp 2.6.3.3 (higher versions of twrp are not compatible, or at least, they are not all compatible)
flash twrp 2.6.3.3
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
then in twrp selsect "install", browse your phone storage to find your ARHD zip file, select it and then swipe to flash.
If this fail again, format data like cisa said above, but you'll have to push the rom to your phone storage again.
Click to expand...
Click to collapse
Installed TWRP from your link fine, tried to install ARHD which failed so from TWRP I did Wipe / Format Data and now everytime I try and push the rom back to the phone I get the message protocol failure after about 3 minutes or so.

dirkgently68 said:
Installed TWRP from your link fine, tried to install ARHD which failed so from TWRP I did Wipe / Format Data and now everytime I try and push the rom back to the phone I get the message protocol failure after about 3 minutes or so.
Click to expand...
Click to collapse
What was the error code in twrp?
What is your adb version?
Do you have latest HTC drivers installed?
Are you using a usb 2.0 ports? Maybe try another usb port/cable.
Have you checked MD5 value of your rom/recovery files?

dirkgently68 said:
Installed TWRP from your link fine, tried to install ARHD which failed so from TWRP I did Wipe / Format Data and now everytime I try and push the rom back to the phone I get the message protocol failure after about 3 minutes or so.
Click to expand...
Click to collapse
After you done wipe/format data. Did you reboot the phone to recovery?
You have to do this to write the new file system.
If it's still failing after reboot. Disable HTC sync or better still uninstall it if you don't use it.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:

Thanks to all of you who responded, it turns out I've got 6 different versions of ADB on my PC due to various toolkits and things I've downloaded for my different devices, I also only have USB 3 ports on this machine but when I changed ADB version it worked, so again thanks to you all :good:

[Q] need to flash back to custom rom from RUU

After flashing a RUU via Aurora Installer, I am unable to flash any ROM.
I have tried flashing Carbon ROM with both TWRP and CWM Touch, but it boots, loads initial set-up and then boot loops.
I have also previously tried flashing Cyanogen mod and Paranoid Android but to no avail
I need to go back to a custom ROM as I am unable to charge with the RUU if the phone is on.
Bootloader
***UNLOCKED***
M7_UL PVT SHIP S-FF RH
CID-11111111
HBOOT-1.44.0000
OpenDSP-V32.120.2740909
eMMC-BOOT

parthami said:
After flashing a RUU via Aurora Installer, I am unable to flash any ROM.
I have tried flashing Carbon ROM with both TWRP and CWM Touch, but it boots, loads initial set-up and then boot loops.
I have also previously tried flashing Cyanogen mod and Paranoid Android but to no avail
I need to go back to a custom ROM as I am unable to charge with the RUU if the phone is on.
Bootloader
***UNLOCKED***
M7_UL PVT SHIP S-FF RH
CID-11111111
HBOOT-1.44.0000
OpenDSP-V32.120.2740909
eMMC-BOOT
Click to expand...
Click to collapse
What version of TWRP ? ... it's important that you use the version recommended by the rom your flashing

I have tried both 2.7.1.0 and 2.8.3.0 but sadly it still bootloops

parthami said:
After flashing a RUU via Aurora Installer, I am unable to flash any ROM.
I have tried flashing Carbon ROM with both TWRP and CWM Touch, but it boots, loads initial set-up and then boot loops.
I have also previously tried flashing Cyanogen mod and Paranoid Android but to no avail
I need to go back to a custom ROM as I am unable to charge with the RUU if the phone is on.
Bootloader
***UNLOCKED***
M7_UL PVT SHIP S-FF RH
CID-11111111
HBOOT-1.44.0000
OpenDSP-V32.120.2740909
eMMC-BOOT
Click to expand...
Click to collapse
Ok first off. An RUU is the program HTC uses to flash the OS to your device. It is not the OS. it sounds like you are not properly wiping the device before installing. Alos avoid any CWM recoveries. They are well known to be buggy and not the best option.
1. Use adb and fastboot to flash TWRP recovery
2. Format, system, data, cache and delvic cache
3. Flash the rom.
This will wipe all data on your device for apps and settings. So make sure you backup.

parthami said:
I have tried both 2.7.1.0 and 2.8.3.0 but sadly it still bootloops
Click to expand...
Click to collapse
are you doing all 3 steps ?
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
I see your on hboot 1.44 is your firmware still that old ?
post your fastboot getvar all and lets update your firmware

zelendel said:
Ok first off. An RUU is the program HTC uses to flash the OS to your device. It is not the OS. it sounds like you are not properly wiping the device before installing. Alos avoid any CWM recoveries. They are well known to be buggy and not the best option.
1. Use adb and fastboot to flash TWRP recovery
2. Format, system, data, cache and delvic cache
3. Flash the rom.
This will wipe all data on your device for apps and settings. So make sure you backup.
Click to expand...
Click to collapse
flashed twrp via fastboot, still having the same problem
clsA said:
are you doing all 3 steps ?
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
I see your on hboot 1.44 is your firmware still that old ?
post your fastboot getvar all and lets update your firmware
Click to expand...
Click to collapse
I was only doing the first step, will try the others
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *******************
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4223mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.136s

parthami said:
flashed twrp via fastboot, still having the same problem
I was only doing the first step, will try the others
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *******************
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4223mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.136s
Click to expand...
Click to collapse
not much help what was you CID and OS before you changed them ??
anyway this should work for you also
http://forum.xda-developers.com/showpost.php?p=57681938&postcount=4

HTC_001 and Paranoid Android

parthami said:
HTC_001 and Paranoid Android
Click to expand...
Click to collapse
yeah do the stuff i posted above

currently running the ruu
getting a error 170; usb connection
I think it might be to do with the phone as it is off with the charging animation but the text
"This build is for dev...." etc is also showing, which i have never seen before
Edit: reply failed again :/
EDIT 2 : Looks like ive got it to work with fastboot oem rebootRUU
EDIT 3: Nope,still have error 170, will keep trying
EDIT 4: When it get to checking headings, I get ERROR [171]: USB CONNECTION ERROR
Any help would be greatly appreciated, as I just have a paperweight now
never mind, going to re download to the RUU

parthami said:
currently running the ruu
getting a error 170; usb connection
I think it might be to do with the phone as it is off with the charging animation but the text
"This build is for dev...." etc is also showing, which i have never seen before
Edit: reply failed again :/
EDIT 2 : Looks like ive got it to work with fastboot oem rebootRUU
EDIT 3: Nope,still have error 170, will keep trying
EDIT 4: When it get to checking headings, I get ERROR [171]: USB CONNECTION ERROR
Any help would be greatly appreciated, as I just have a paperweight now
Click to expand...
Click to collapse
did you flash the firmware 1 and firmware 2 then the RUU ?

clsA said:
did you flash the firmware 1 and firmware 2 then the RUU ?
Click to expand...
Click to collapse
I'm pretty sure I had the wrong RUU, so I'm going to check and redownload it

parthami said:
I'm pretty sure I had the wrong RUU, so I'm going to check and redownload it
Click to expand...
Click to collapse
wrong RUU is not going to give you a USB Connection error ...a bad usb cable or a dirty port would

clsA said:
wrong RUU is not going to give you a USB Connection error ...a bad usb cable or a dirty port would
Click to expand...
Click to collapse
yeah thought I just mention it, I will clean out the ports and try again tomorrow, thanks for your help so far!

clsA said:
wrong RUU is not going to give you a USB Connection error ...a bad usb cable or a dirty port would
Click to expand...
Click to collapse
I have now tried 3 different ports, I cleaned the cable and flashed the firmwares again but I am still getting Error [171]: USB CONNECTION ERROR
Any ideas?

parthami said:
I have now tried 3 different ports, I cleaned the cable and flashed the firmwares again but I am still getting Error [171]: USB CONNECTION ERROR
Any ideas?
Click to expand...
Click to collapse
are you using windows 8 ? and are your drivers installed correctly ? Do you see My HTC in device manager

clsA said:
are you using windows 8 ? and are your drivers installed correctly ? Do you see My HTC in device manager
Click to expand...
Click to collapse
No, I am using Windows 7
Yeah, I installed HTC Sync so I should have all the drivers
Dont see My HTC since it is in bootloader mode

parthami said:
No, I am using Windows 7
Yeah, I installed HTC Sync so I should have all the drivers
Dont see My HTC since it is in bootloader mode
Click to expand...
Click to collapse
any driver installed when in the bootloader ?

clsA said:
any driver installed when in the bootloader ?
Click to expand...
Click to collapse
It just says Android 1.0 and HTC MTP Device Failed in driver installation

parthami said:
It just says Android 1.0 and HTC MTP Device Failed in driver installation
Click to expand...
Click to collapse
Here's what you should see in windows 7 with the phone in fastboot USB
{
"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"
}
https://www.dropbox.com/s/fwt164s3udcix2d/Screenshot 2014-12-23 13.39.37.png?dl=0

[Q] Messed up trying to wipe / update. Need a hand

Here's the details. Phone was rooted in 2013. I have my unlockcode.bin file saved from then.
I wanted to install a new ROM and reaslied I needed to be on a new kernal for it to work.
I tried to update using the standard options menu on the phone, didn't work, just looped.
So I backed up my media to PC, at present I can happily lose everything on the phone and go back to square 1.
I ended up looking at Team Win recovery project V2.6.3.3 which is what was used when I originally rooted it, I decided the best thing to do is was to select wipe all.
Looks like I removed the OS too as it just shows the logo when I boot normally, but I can access the bootloader menu and team win recovery menu.
Phone is connected to my PC and I have the Android SDK working and can connect to my phone using the CMD promt.
Please help, I'm computer literate but useless with phones.
Thanks

Is the phone s-off? Did you make any backups with twrp before you wiped?

ANGRY_robert said:
Is the phone s-off? Did you make any backups with twrp before you wiped?
Click to expand...
Click to collapse
I don't know what S-off means.
I did have backups on the phone but they've obviously been wiped. I have a file called backup.ab on my computer so I hope I can somehow use that

Look at your bootloader screen. At the very top under "unlocked" it will either say M7_Ux PVT SHIP S-ON or S-OFF.
You did have backups, but never copied any to a pc......

Niall44 said:
I don't know what S-off means.
I did have backups on the phone but they've obviously been wiped. I have a file called backup.ab on my computer so I hope I can somehow use that
Click to expand...
Click to collapse
download a rom and push it to your phone, then install it using twrp. Instructions posted below:
Originally posted by @alrayHTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
To open a command window prompt, in Windows go to Start Menu --> ''Run'' then type cmd. Change the directory to the ADB folder on your machine:
If using the default install location for the SDK:
Code:
cd C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools
If using the default install location of Minimal ADB and FASTBOOT:
Code:
cd C:\Program Files (x86)\Minimal ADB and Fastboot
Or hold left shift + right click a blank space inside the folder where adb and fastboot are located and select ''Open command window here'' from the contextual menu.
{
"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"
}
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
Unlock bootloader if not already unlocked:
Thanks to Electroz for the video tutorial
Flash TWRP Recovery:
Make sure the recovery.img file is in the same folder where adb and fastboot are located
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
reboot phone in bootloader mode
Flash the recovery:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
You need your HTC drivers correctly installed on your PC:
If not, follow this guide (thanks to nkk71):
originally from @nkk71: [GUIDE] [02-MAR-2014] nkk71's SuperGUIDE to returning 100% back to stock
follow the below instructions to fix
Open "Device Manager" -> select the unknown "One" -> right-click -> "Update Driver Software ..." -> "Browse my computer" -> "Let me pick" -> "Android USB Devices" -> select "My HTC ..." -> install that
just in case, HTC Drivers can be found here: [Drivers] HTC Drivers for Windows - Several Versions (credits to @mdmower)
though you should already have them since you have been using your phone anyways
for those who like a visual guide:
okay so I did a fastboot boot command, and as you can see it didnt install correct driver
Open "Device Manager"
there's the culprit
right click and Update Driver Software
select Browse my computer for driver software
select Let me pick from a list of device drivers on my computer
select Android USB Devices
select My HTC ... (if you have more than one version, choose the latest)
warning, select Yes
successful installation
now it looks better
and can confirm:
Code:
C:\ADB3>[B]adb devices[/B]
List of devices attached
HTxxxxxxxxxx recovery
Click to expand...
Click to collapse
​
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Here is a list of the HTC M7 roms. Some other roms can be found here.
Connect your phone to computer using usb cable
(if not using the official HTC USB calble, make sure
you are using a USB data cable and not only a charging
cable. Data cables have 4 contacts: 5V, GND, DATA+, DATA-.
Charging cable only have 5V and GND contact and will not work)
Reboot phone in recovery mode (TWRP):
If phone is booted in OS:
Code:
adb reboot recovery
if not booted or bootlooping, hold power button + volume down until phone boot in bootloader mode
then select BOOTLOADER then RECOVERY using volume up/down to navigate and power button to select.
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
Wait for the zip file to transfer, this can take several minutes (5-15) and there is no progress bar, the command prompt will be unresponsive for that duration. When the command prompt is responsive again and display how much bytes transferred in X seconds, the transfer is completed:
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone
Click to expand...
Click to collapse
Click to expand...
Click to collapse

ANGRY_robert said:
Look at your bootloader screen. At the very top under "unlocked" it will either say M7_Ux PVT SHIP S-ON or S-OFF.
You did have backups, but never copied any to a pc......
Click to expand...
Click to collapse
It says M7-UL PVT SHIP S-ON RH
I take it this is bad.
As for the backups, are you saying the backup.ab file on my PC is useless?

alray beat me to it. Follow the instructions in his post. S-ON is not bad, it's standard (security on). Just can be a bit limiting depending upon the situation.

alray said:
download a rom and push it to your phone, then install it using twrp. Instructions posted below:
​
Click to expand...
Click to collapse
Looks promising, I will try this now. Will my choice of rom be affected by the fact my phone was on an old kernal? Something like 4.1.1 iirc

Niall44 said:
Looks promising, I will try this now. Will my choice of rom be affected by the fact my phone was on an old kernal? Something like 4.1.1 iirc
Click to expand...
Click to collapse
I think you are not correctly using the term "kernel". Kernel is boot.img and is included in every roms (when speaking about the HTC one M7)
Maybe you are talking about your Firmware version? If a rom require the firmware to be updated to a specific version, then yes updated it.
Better to post the output of "fastboot getvar all" minus your imei/sn so we can help you determine what you need to do with your firmware before flashing roms.

When you say kernel 4.1.1, I think you mean android os jellybean and not kernel. I'm trying to not confuse you here. Try and find an older rom on here that is based off jellybean and go from there.
---------- Post added at 06:38 PM ---------- Previous post was at 06:36 PM ----------
alray beat me again. I think I'll leave you in his hands.

alray said:
I think you are not correctly using the term "kernel". Kernel is boot.img and is included in every roms (when speaking about the HTC one M7)
Maybe you are talking about your Firmware version? If a rom require the firmware to be updated to a specific version, then yes updated it.
Better to post the output of "fastboot getvar all" minus your imei/sn so we can help you determine what you need to do with your firmware before flashing roms.
Click to expand...
Click to collapse
ANGRY_robert said:
When you say kernel 4.1.1, I think you mean android os jellybean and not kernel. I'm trying to not confuse you here. Try and find an older rom on here that is based off jellybean and go from there.
---------- Post added at 06:38 PM ---------- Previous post was at 06:36 PM ----------
alray beat me again. I think I'll leave you in his hands.
Click to expand...
Click to collapse
Understood about kernals, I'm used to modded xbox's so I assumed the term would translate.
Having trouble reading the info, it keeps crashing or just hanging with "waiting for device".
I think it's more a problem my end with faulty USB ports. I'll have to try it on another PC

alray said:
I think you are not correctly using the term "kernel". Kernel is boot.img and is included in every roms (when speaking about the HTC one M7)
Maybe you are talking about your Firmware version? If a rom require the firmware to be updated to a specific version, then yes updated it.
Better to post the output of "fastboot getvar all" minus your imei/sn so we can help you determine what you need to do with your firmware before flashing roms.
Click to expand...
Click to collapse
Got it.
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.61.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4075mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s

Niall44 said:
Got it.
(bootloader) version-baseband: 4A.13.3231.27
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.28.61.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4075mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
Click to expand...
Click to collapse
There is not much useful files on the web fo orange (x.xx.61.x). If you want to update your firmware to the latest version to ensure the best stability with newer Roms, you could flash an older rom and s-off your phone using Revone. Then you'll be free to flash a newer firmware even if its not based on x.xx.61.x, the latest x.xx.401.x firmware should do the job ( I think its 6.09.401.11 or .12)

alray said:
There is not much useful files on the web fo orange (x.xx.61.x). If you want to update your firmware to the latest version to ensure the best stability with newer Roms, you could flash an older rom and s-off your phone using Revone. Then you'll be free to flash a newer firmware even if its not based on x.xx.61.x, the latest x.xx.401.x firmware should do the job ( I think its 6.09.401.11 or .12)
Click to expand...
Click to collapse
Thanks for looking, so I need to find a rom with x.xx.61.x or lower in the title and install that to get started?

Niall44 said:
Thanks for looking, so I need to find a rom with x.xx.61.x or lower in the title and install that to get started?
Click to expand...
Click to collapse
no and you won't find roms based on x.xx.61.x anyway there are usually based on x.xx.401.x (international version)
arhd 31.6 will work fine on your current firmware version,
Then if you want to achieve S-OFF, all you will need is to follow instructions in Revone thread.

alray said:
no and you won't find roms based on x.xx.61.x anyway there are usually based on x.xx.401.x (international version)
arhd 31.6 will work fine on your current firmware version,
Then if you want to achieve S-OFF, all you will need is to follow instructions in Revone thread.
Click to expand...
Click to collapse
Marvelous. I got the ROM installed and working. I'll start on the S-Off, updating and fancy new ROM tomorrow. But it's way past my bedtime.
Thank you very much for being patient

Glad we, uhm .... I mean alray could help.

ANGRY_robert said:
Glad we, uhm .... I mean alray could help.
Click to expand...
Click to collapse
your help is also appreciated mate :good: keep up good work

Can't seem to get Revone to work. File is in the correct directory but I'm getting error 1 when I try "./revone -P"
I saw in another thread that installing another ROM would help, but it didn't. So I've reflashed the arhd 31.6 ROM I was given but can't seem to get any headway into getting it to work.

Trying to achieve s-off has different methods. Each method is a little different. It all depends on what hboot version you are running. Your hboot version is displayed on the bootloader screen.
Examples: 1.44, 1.54, 1.56, 1.57
See what your version is and report back.

[SOLVED] Can anyone help me fix my htc one m7?

I recently acquired an htc one m7. i decided it would be cool to root it and put a custom rom ( i have had experience in this i have done it on my s3 my galaxy tab 2.0 and a galaxy express) so i unlocked my bootloader, flashed a custom rom and rooted my device and i decided (stupidly) to erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching. i tried to gain s-off but with every solution i need to be booted up but i dont have an os so i cannot. i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors. i tried fastboot flashing it but it wont verify it. i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either. i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit. this did not work. ive tried different recovery (but not different versions of these recoveries) everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.

sethdrak3 said:
(...)erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching.
Click to expand...
Click to collapse
This is the most common situation here, no worries, it can be fixed easily.
i tried to gain s-off
Click to expand...
Click to collapse
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
but with every solution i need to be booted up but i dont have an os so i cannot.
Click to expand...
Click to collapse
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors.
Click to expand...
Click to collapse
What is the error exactly? What is your TWRP recovery version? What rom exactly?
i tried fastboot flashing it but it wont verify it.
Click to expand...
Click to collapse
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either.
Click to expand...
Click to collapse
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit.
Click to expand...
Click to collapse
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.
Click to expand...
Click to collapse
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?

alray said:
This is the most common situation here, no worries, it can be fixed easily.
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
i thought i heard somewhere you needed s off to flash roms
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
What is the error exactly? What is your TWRP recovery version? What rom exactly?
my twrp is v2.6.0.1 and im trying to flash cm12
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i understand this now i was trying ever possibility and how do you get to RUU mode?
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35XW916185
(bootloader) imei: 354439055703575
(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: 3664mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
output from command "fastboot getvar all"
@alray
thank you for all your help. btw the toolkit is very useful for small things like writing new recoveries it makes it easier plus sometimes its less problematic
Click to expand...
Click to collapse

sethdrak3 said:
i thought i heard somewhere you needed s off to flash roms
Click to expand...
Click to collapse
No, you only need an unlocked bootloader + custom recovery installed.
my twrp is v2.6.0.1 and im trying to flash cm12
Click to expand...
Click to collapse
TWRP 2.6.0.1 is really outdated. Latest official version is 2.8.6.0 or (2.8.6.4 unofficial) and since 2014-05-01 you need at least twrp 2.7.0.8 to flash Cyanogenmod
i understand this now i was trying ever possibility and how do you get to RUU mode?
Click to expand...
Click to collapse
Code:
fastboot oem rebootRUU
but it won't help flashing roms, only for signed RUU and Signed firmware same or newer version that match your CID, MID and base version( x.xx.502.x) so 3.17.502.3 or above
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) security: on
Click to expand...
Click to collapse
If you want to flash CM12, update your recovery.
You might want to read this, this and this
TWRP can be downloaded from here and here

thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.

sethdrak3 said:
thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.
Click to expand...
Click to collapse
you're welcome, that's one example why we are not suggesting to use any toolkits.
can you edit your title to "[SOLVED] Can anyone help me fix my htc one m7?" (go to your first post, click "edit" then click "go advanced" change your title and click "save changes) thanks