Hi guys,
I did one really stupid thing, I attempted to flash firmware to the HTC One m7 but I completely forgot that I have S-On. Now my phone is in a reboot loop. I can get to the HBOOT and FASTBOOT, however my sdcard is not accessible (Can't mount). Is there a way to recover from this situation?
koanry said:
Hi guys,
I did one really stupid thing, I attempted to flash firmware to the HTC One m7 but I completely forgot that I have S-On. Now my phone is in a reboot loop. I can get to the HBOOT and FASTBOOT, however my sdcard is not accessible (Can't mount). Is there a way to recover from this situation?
Click to expand...
Click to collapse
Flashing firmware is generally no problem with s-on. But it will have restored your Stock Recovery and boot.img. After flashing and unlocking the bootloader (FYI Unlocking the bootloader will wipe internal storage and user data) you would need to flash your custom recovery and the boot.img for your rom.
Were you running a custom rom when you updated your firmware?
Did you Relock your bootloader before flashing the firmware?
Was the firmware flash successful or did it fail?
Sent from my SM-T230 using Tapatalk
Danny201281 said:
Flashing firmware is generally no problem with s-on. But it will have restored your Stock Recovery and boot.img. After flashing and unlocking the bootloader (FYI Unlocking the bootloader will wipe internal storage and user data) you would need to flash your custom recovery and the boot.img for your rom.
Were you running a custom rom when you updated your firmware?
Did you Relock your bootloader before flashing the firmware?
Was the firmware flash successful or did it fail?
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Thanks for your response Danny201281!
- I was running Cianogenmod 10.2
- bootloader was unlocked
- firmware flash failed
koanry said:
Thanks for your response Danny201281!
- I was running Cianogenmod 10.2
- bootloader was unlocked
- firmware flash failed
Click to expand...
Click to collapse
Ok so if the bootloader was unlocked the flash failing is inevitable. But it shouldn't have damaged your device. Since s-on should protect from flashing anything wrong. So the good news is it should be fairly simple fix.
I'm assuming you flashed the firmware with fastboot and not with recovery?
So Internal Storage not mounting could be due to a number of things. Do you have a working recovery? If so which recovery? Name and version please :good:
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Ok so if the bootloader was unlocked the flash failing is inevitable. But it shouldn't have damaged your device. Since s-on should protect from flashing anything wrong. So the good news is it should be fairly simple fix.
I'm assuming you flashed the firmware with fastboot and not with recovery?
So Internal Storage not mounting could be due to a number of things. Do you have a working recovery? If so which recovery? Name and version please :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Cool, I'm really happy to hear that
Recovery: ClockworkMod Recovery v6.0.4.8 touch
koanry said:
Cool, I'm really happy to hear that
Recovery: ClockworkMod Recovery v6.0.4.8 touch
Click to expand...
Click to collapse
Thanks one last question. Can you please post the output of
Code:
fastboot getvar all
For security please remove your imei and Serial numbers. :good:
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Thanks one last question. Can you please post the output of
Code:
fastboot getvar all
For security please remove your imei and Serial numbers. :good:
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Code:
(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.8
(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: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(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!
koanry said:
Code:
(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.8
(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: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4306mV
(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
Your firmware is pretty old so updating it wouldn't be a bad idea but let's focus on getting it booting again.
To get your sd storage to Mount you can try to repair it with e2fsck or you can format it. Formatting will wipe it's contents though.
To format go to Mounts and Storage options in CWM, and select Format Sdcard.
To attempt to repair with e2fsck. Boot to CWM go to Mounts and Storage and make sure all partitions are UN-Mounted. While still in recovery connect the usb to your pc and open an adb/fastboot command window. Enter these commands
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p37
exit
Once your sdcard is mounting you can install a Rom.
You can also use adb in recovery to copy a Rom to the device if you need to.
Put the Rom in your adb/fastboot folder and rename it something simple like rom.zip
Then push the Rom with
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push is complete. When it's done install it with CWM.
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Your firmware is pretty old so updating it wouldn't be a bad idea but let's focus on getting it booting again.
To get your sd storage to Mount you can try to repair it with e2fsck or you can format it. Formatting will wipe it's contents though.
To format go to Mounts and Storage options in CWM, and select Format Sdcard.
To attempt to repair with e2fsck. Boot to CWM go to Mounts and Storage and make sure all partitions are UN-Mounted. While still in recovery connect the usb to your pc and open an adb/fastboot command window. Enter these commands
Code:
adb shell
e2fsck -fvy dev/block/mmcblk0p35
e2fsck -fvy dev/block/mmcblk0p36
e2fsck -fvy dev/block/mmcblk0p37
exit
Once your sdcard is mounting you can install a Rom.
You can also use adb in recovery to copy a Rom to the device if you need to.
Put the Rom in your adb/fastboot folder and rename it something simple like rom.zip
Then push the Rom with
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push is complete. When it's done install it with CWM.
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
It's alive! Thanks a lot!!!
Had to do
Code:
adb push rom.zip /data/media/
because push to /sdcard was just replacing an existing symlink with the file .
Could you please point me to some up to date firmware and firmware install guide? It all started when I decided to upgrade my old cyanogen with a new viperone and couldn't install it because of old firmware .
koanry said:
It's alive! Thanks a lot!!!
Had to do
Code:
adb push rom.zip /data/media/
because push to /sdcard was just replacing an existing symlink with the file .
Could you please point me to some up to date firmware and firmware install guide? It all started when I decided to upgrade my old cyanogen with a new viperone and couldn't install it because of old firmware .
Click to expand...
Click to collapse
Cool, good news So now your able to boot you should consider gaining s-off. With s-off it will be much easier to update firmware. Also right now you can do it with rumrunner which is free to use. If you update your firmware then decide to s-off later you will have to use Sunshine App which costs $25 to use.
So it's better to do it now.
If you flashed Cyanogen Mod again then you will need to flash a stock Rom for rumrunner to work so it means a little more tinkering but it will be worth it in the end.
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
Cool, good news So now your able to boot you should consider gaining s-off. With s-off it will be much easier to update firmware. Also right now you can do it with rumrunner which is free to use. If you update your firmware then decide to s-off later you will have to use Sunshine App which costs $25 to use.
So it's better to do it now.
If you flashed Cyanogen Mod again then you will need to flash a stock Rom for rumrunner to work so it means a little more tinkering but it will be worth it in the end.
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Thanks Danny! I did everything like you suggested and it worked out great .
koanry said:
Thanks Danny! I did everything like you suggested and it worked out great .
Click to expand...
Click to collapse
So your device is now s-off? What about firmware did you manage to update it?
Sent from my M7 ARHD 84-Kitkat
Danny201281 said:
So your device is now s-off? What about firmware did you manage to update it?
Sent from my M7 ARHD 84-Kitkat
Click to expand...
Click to collapse
Yep, everything is fine. I s-offed the phone with rumrunner like you suggested, then relocked it and flashed new firmware. After that I was able to install viperone without any issues. Thanks!
koanry said:
Yep, everything is fine. I s-offed the phone with rumrunner like you suggested, then relocked it and flashed new firmware. After that I was able to install viperone without any issues. Thanks!
Click to expand...
Click to collapse
Excellent glad you got it sorted. But for the record, with s-off there is no need to Relock the bootloader to flash firmware. Or anything for that matter. It's one of the many advantages of having s-off
Sent from my M7 ARHD 84-Kitkat
Related
Had cyanogenmod installed but wanted to revert back to stock. I am now unable to install any roms and only have access to bootloader and CWM. I have tried running RUU_M7_UL_K44_SENSE55_MR_Cingular_US_4.18.502.7_R10_Radio_4T.24.3218.09_10.26.1718.01L_release_356565_signed_2 from my pc but the program closes after the terms and conditions, and my attempts to flash a rom or sideload from cwm have failed as well.
M7-UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4T.24.3218.09
OpenDSP-v32.120.274.0909
OS-4.18.502.7
eMMC-boot 2048MB
Jan 28 2014. 09:32:41.0
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT39MW903199
(bootloader) imei: 354439057262075
(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: 4320mV
(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
You must first extract the boot.img for whatever rom you are trying to flash and fastboot flash that first before trying to install the rom.
Cyanogen is a non sense rom and uses a different kind of boot, that's why your experiencing the problem you have.
Seanie280672 said:
You must first extract the boot.img for whatever rom you are trying to flash and fastboot flash that first before trying to install the rom.
Cyanogen is a non sense rom and uses a different kind of boot, that's why your experiencing the problem you have.
Click to expand...
Click to collapse
What the heck are you talking about .?? :silly:
OP.. You need to sideload a custom rom, or restore a nandroid backup from ATT firmware matching the main-version.. 4.18.502.7
There are a few restore threads around detailing this, so please help yourself!
Seanie280672 said:
You must first extract the boot.img for whatever rom you are trying to flash and fastboot flash that first before trying to install the rom.
Click to expand...
Click to collapse
@SaHiLzZ
I remember having to flash the boot.img manually each time you flash a custom rom on the endeavoru (One X) but this is not required for the M7
SaHiLzZ said:
OP.. You need to sideload a custom rom, or restore a nandroid backup from ATT firmware matching the main-version.. 4.18.502.7
Click to expand...
Click to collapse
Ive tried sideloading but it doesnt work, idk if Im just not trying to load the right file or what.
So the error is. ?
SaHiLzZ said:
So the error is. ?
Click to expand...
Click to collapse
* failed to write data 'protocol fault (no status)' * usually gets to about 80-90% then gives me this
nwmn9386 said:
* failed to write data 'protocol fault (no status)' * usually gets to about 80-90% then gives me this
Click to expand...
Click to collapse
HAve you tried adb push instead of side load, I suggest you wipe internal memory first if possible though.
Put the rom in your fastboot / adb folder, open a command windows there, Control + Shift + right mouse click and select open command window here then type
adb push (filename).zip /sdcard/
EDIT: sorry forgot to add you must be in recovery main screen to do this obviously with the phone plugged into the computer too.
Seanie280672 said:
HAve you tried adb push instead of side load, I suggest you wipe internal memory first if possible though.
Put the rom in your fastboot / adb folder, open a command windows there, Control + Shift + right mouse click and select open command window here then type
adb push (filename).zip /sdcard/
EDIT: sorry forgot to add you must be in recovery main screen to do this obviously with the phone plugged into the computer too.
Click to expand...
Click to collapse
Keep getting the error "E:Can't mount/SD card" whenever i try to run it on my phone
fixed this error, just needed to format the /sdcard. the rom that i pushed ran but didnt install correctly so i think i may just be trying to install the wrong file
nwmn9386 said:
Keep getting the error "E:Can't mount/SD card" whenever i try to run it on my phone
fixed this error, just needed to format the /sdcard. the rom that i pushed ran but didnt install correctly so i think i may just be trying to install the wrong file
Click to expand...
Click to collapse
Yes, I said you may have to wipe the internal storage, ie sd card.
Try and push and install a custom Rom, pretty much anyone from the M7 android development thread as you have an M7UL, however I would recommend viper one or ARHD.
However the ruu that you are trying to flash seems to be the right one, just checked the details against your output, same radio and firmware, you could always try and get the guru reset Rom zip for your device, just go to www.htc1guru.com and see if there is one there.
my htc one was stuck in bootloop i try a ruu with no success after that by fastboot unlocked the bootloader, flash a custom recovery (TWRP) and accidental wipe the phone, now i cant flash any zip give me the message unable to mount /data/
i try many roms by push fastboot and by otg cable no success
this is the result of fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: erased by me
(bootloader) imei: erased by me
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thanks in advance
mendek said:
my htc one was stuck in bootloop i try a ruu with no success after that by fastboot unlocked the bootloader, flash a custom recovery (TWRP) and accidental wipe the phone, now i cant flash any zip give me the message unable to mount /data/
i try many roms by push fastboot and by otg cable no success
this is the result of fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: erased by me
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thanks in advance
Click to expand...
Click to collapse
I would also remove your serialno! Follow the steps in this post. You can use TWRP 2.6.3.3 or TWRP 2.7.1.2 as well as the one in the post.
majmoz said:
I would also remove your serialno! Follow the steps in this post. You can use TWRP 2.6.3.3 or TWRP 2.7.1.2 as well as the one in the post.
Click to expand...
Click to collapse
thank you but where i can find a ruu to my device ? because i have the last ota update before brick
mendek said:
thank you but where i can find a ruu to my device ? because i have the last ota update before brick
Click to expand...
Click to collapse
I couldn't find a RUU for your phone, but here is a nandroid backup use Method 2. If you need the stock firmware you can get it here to run it your bootloader must be LOCK/RELOCK.
majmoz said:
I couldn't find a RUU for your phone, but here is a nandroid backup use Method 2. If you need the stock firmware you can get it here to run it your bootloader must be LOCK/RELOCK.
Click to expand...
Click to collapse
I Flash firmware, unlock the bootloader and restore a nandroid, clear cache, when reboot after HTC logo It makes a horrible noise, White screen and turn off
mendek said:
I Flash firmware, unlock the bootloader and restore a nandroid, clear cache, when reboot after HTC logo It makes a horrible noise, White screen and turn off
Click to expand...
Click to collapse
If I am following you correctly these are the steps you took:
First you flashed the firmware. Which firmware did you flash?
Then you unlocked the bootloader and installed a custom recovery. Which recovery?
Then you restored the nandroid from the post. Did you select root after the nandroid installed?
Then you cleared cache? Why?
majmoz said:
If I am following you correctly these are the steps you took:
First you flashed the firmware. Which firmware did you flash?
Then you unlocked the bootloader and installed a custom recovery. Which recovery?
Then you restored the nandroid from the post. Did you select root after the nandroid installed?
Then you cleared cache? Why?
Click to expand...
Click to collapse
hi flash the last firmware from the ota i has before.
after that flash twrp recovery 2.7.1
select root when restore
clear cache for no reason
but now i can enter in recovery always stuck in entering recovery, tried many versions of twrp and cwm and nothing, try fastboot erase cache no results
now only enter fastboot
already try relock the bootloader and flash firmware, unlock again flash custom recovery but still the same
i really dont know what do next...
mendek said:
hi flash the last firmware from the ota i has before.
after that flash twrp recovery 2.7.1
select root when restore
clear cache for no reason
but now i can enter in recovery always stuck in entering recovery, tried many versions of twrp and cwm and nothing, try fastboot erase cache no results
now only enter fastboot
already try relock the bootloader and flash firmware, unlock again flash custom recovery but still the same
i really dont know what do next...
Click to expand...
Click to collapse
I think the firmware you are using is not a compete package, generally firmware removed from OTA don't have all of the elements just those needed to run the OTA. Get a .401 stock firmware from this Placeholder of HTC One Firmwares.
majmoz said:
I think the firmware you are using is not a compete package, generally firmware removed from OTA don't have all of the elements just those needed to run the OTA. Get a .401 stock firmware from this Placeholder of HTC One Firmwares.
Click to expand...
Click to collapse
which firmware ? i try many but always failed in signature verification
mendek said:
hi flash the last firmware from the ota i has before.
after that flash twrp recovery 2.7.1
select root when restore
clear cache for no reason
but now i can enter in recovery always stuck in entering recovery, tried many versions of twrp and cwm and nothing, try fastboot erase cache no results
now only enter fastboot
already try relock the bootloader and flash firmware, unlock again flash custom recovery but still the same
i really dont know what do next...
Click to expand...
Click to collapse
Hello, i'm sorry i don't know what to say because i have almost the same problem, my htc one m7_UL won't start...is shutsdown sometimes at boot time, when i take photos with it...and sometimes what ever else, but in recovery mode it can still houers and houers. yesterday i brought it to s-off then i installed an RUU...but still the same problem !!! is it a material issue ??? thank you.
Within TWRP you should wipe data (not custom) to recreate data, system, and etc. folders. This will also wipe whats on you sdcard so, you'll have to adb push new files to your sdcard to flash a rom.
ZikoMikoo said:
Hello, i'm sorry i don't know what to say because i have almost the same problem, my htc one m7_UL won't start...is shutsdown sometimes at boot time, when i take photos with it...and sometimes what ever else, but in recovery mode it can still houers and houers. yesterday i brought it to s-off then i installed an RUU...but still the same problem !!! is it a material issue ??? thank you.
Click to expand...
Click to collapse
my start exactly like yours random restarts etc, after unlock bootloader works for another week and when i playing a game turn off and never can put it work again, now even cant enter recovery
mendek said:
which firmware ? i try many but always failed in signature verification
Click to expand...
Click to collapse
5.11.401.10
majmoz said:
5.11.401.10
Click to expand...
Click to collapse
i flash this firmware, unlock bootloader flash twrp now when is enter in recovery i see the twrp logo and after that reboot and stay in a bootloop
mendek said:
i flash this firmware, unlock bootloader flash twrp now when is enter in recovery i see the twrp logo and after that reboot and stay in a bootloop
Click to expand...
Click to collapse
after flashing a recovery, you also need to
Code:
fastboot erase cache
majmoz said:
5.11.401.10
Click to expand...
Click to collapse
now i can access the recovery, if i restore whe it pass the htc logo stucks with some stripes in the screen and turn off, try flash cyanogen it turn on but some times stucks and reboots i dont what to do maybe hardware fault?
mendek said:
now i can access the recovery, if i restore whe it pass the htc logo stucks with some stripes in the screen and turn off, try flash cyanogen it turn on but some times stucks and reboots i dont what to do maybe hardware fault?
Click to expand...
Click to collapse
Try to get back into TWRP, in TWRP flash this stock ROM Method 1. I am guessing that when you say you restore that you are talking about the nandroid backup you got from the site.
Hi guys,
I have a big problem with my HTC One. I wanted to give it to the service, but it costs a lot of money, maybe I will find some help on XDA hopefully.
My bootloader info looks like this:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT- 1.57.0000
RADIO- 4T.27.3218.14
OpenDSP-v32.120.274.0909
OS-5.11.401.10
eMMC-boot 2048MB
May 5 2014,23:16:29.0
I deleted my system partition in twrp recovery. I can get only to bootloader and recovery. I am S-ON all the time, cannot get S-OFF, I get errors all the time using rum runner or firewater. When I type fastboot oem lock, I am stuck in bootloader, cannot enter recovery. Then the bootloader says ***TAMPERED*** ***RELOCKED*** ***SECURITY WARNING***. I really don't know what to do, I'm stuck. Please help :C !!!
Thanks
My fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(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: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s
GalaXxXx said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: removed
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4332mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.099s
Click to expand...
Click to collapse
You should remove your imei and serialno in your previous post. You can use this stock rom zip to go back to stock. It is the same version that you have. Your bootloader must be LOCKED or RELOCKED. Move the file to your adb/fastboot folder and rename it rom.zip. Open a command window on the same folder then type the following:
Code:
[B][I]adb reboot bootloader[/I][/B]
After that, type:
Code:
[B][I]fastboot oem rebootRUU [/I][/B]
NOTE: You should see a silver HTC logo come up on your phone after executing this command.
NOTE: if this command freezes, just disconnect the USB cable and hold the power and volume down buttons until the device reboots. Then, repeat the steps above again.
Finally:
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
Repeat the same command: IMPORTANT
Code:
[B][I]fastboot flash zip rom.zip[/I][/B]
NOTE: The green bar on the phone may not go to 100% of the bar ... but If you see completed on your computer command window, wait for a few seconds and move on.
Last Step:
Code:
[B][I]fastboot reboot[/I][/B]
Click to expand...
Click to collapse
Thanks a lot @majmoz
I'm downloading zip file now (slow internet 2 hours remaining). I will try your method, and let you know how it went.
doesn't work ;/
@majmoz , it doesn't work .
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)". Did this command 2 times as you instructed.
The second thing is that the "adb reboot bootloader" command didn't work, cmd said that device not found.
What should I do ?
GalaXxXx said:
@majmoz , it doesn't work .
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)". Did this command 2 times as you instructed.
The second thing is that the "adb reboot bootloader" command didn't work, cmd said that device not found.
What should I do ?
Click to expand...
Click to collapse
Does you bootloader still say "Relocked"? Let try to run the stock firmware 5.11.401.10 using the same method, just rename the download to firmware.zip change the rom.zip in the procedure to firmware.zip.
For adb not working take a look at FAQ Q#2.
My bootloader says TAMPERED RELOCKED SECURITY WARNING
I don't think adb works in bootloader, right ?
The firmware.zip worked, (there was the green bar etc.), but the phone is still not rebooting into system.
hmm... there is no custom recovery anymore, just a phone with red sign. And in bootloader it says only tampered and relocked. Without security warning. @majmoz
GalaXxXx said:
My bootloader says TAMPERED RELOCKED SECURITY WARNING
I don't think adb works in bootloader, right ?
The firmware.zip worked, (there was the green bar etc.), but the phone is still not rebooting into system.
hmm... there is no custom recovery anymore, just a phone with red sign. And in bootloader it says only tampered and relocked. Without security warning. @majmoz
Click to expand...
Click to collapse
You are correct adb does not work in bootloader. When the firmware completed it installed the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
majmoz said:
You are correct adb does not work in bootloader. When the firmware completed it installed the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
Click to expand...
Click to collapse
There is an unbrick service here in the forum
I would imagine that's what he's referring to
You are correct adb does not work in bootloader. When the firmware completed it INSTALLED the stock recovery. Since you erased the system partition there is no OS installed. You can try to run the RUU again and it will probably pass now since you have the correct firmware. If this is successful, you will have stock rom and stock firmware on your phone.
What did you mean by give to service?
Click to expand...
Click to collapse
There is an unbrick service here in the forum
I would imagine that's what he's referring to
Click to expand...
Click to collapse
No no, I have a service nearby here in my town. They said they can restore the phone for $30.
I will try the RUU file now, hope it works. I'll be informing what is the status of my "operation" @majmoz @ajbiz11
P.S. How to quote ? You know (Originally Posted by etc.)
GalaXxXx said:
I did everything you said and when flashing it says "FAILED (remote: 12 signature verify fail)".
Click to expand...
Click to collapse
@majmoz I don't think this zip can be flashed using "fastboot flash zip rom.zip", with s-on he can only flash signed ruu from HTC and afaik, htc never released any 5.11.401.10 signed ruu
There is a flashable aroma zip (guru reset) for his version here: https://www.androidfilehost.com/?fid=23501681358543706
to be flashed with a custom recovery (require to unlock the bootloader again)
Yeah @alray , I need to have a 5.11.401.10 signed RUU, but there is no such file avaible to download.
Now, I will unlock my bootloader again, flash custom recovery (TWRP) , and try flash guru reset in this recovery.
Well, I don't really remember, but I think I tried this (maybe with not the same version of guru reset), but I was stuck on "Installation procces" It was 0 % all the time. Let's see how it works out this time with this version of guru.
@alray
I unlocked my bootloader, flashed TWRP, I used adb to push the .zip to sdcard, but the problem now is that the phone says that unable to mount '/data' and unable to mount internal storage. When I click mount in recovery the "data" box doesn't wanna tick .
What should I do ? I'm tired of this ...
Ok, what happened next... I finally did what @alray told me to do. I managed to fix the corrupted data partition, but as I said earlier, when I flash the guru reset in recovery, and start the installation process, it is stuck on 0.00%.
I unlocked the bootloader in order to do this.
No more ideas ? @majmoz ?
GalaXxXx said:
Ok, what happened next... I finally did what @alray told me to do. I managed to fix the corrupted data partition, but as I said earlier, when I flash the guru reset in recovery, and start the installation process, it is stuck on 0.00%.
I unlocked the bootloader in order to do this.
No more ideas ? @majmoz ?
Click to expand...
Click to collapse
What version of TWRP are you using? 2.6.3.3 or 2.8.0.1? I'm pretty sure you checked the MD5 of the files you downloaded.
I'm using TWRP v2.8.0.2. What do you mean by saying you're pretty sure I checked the MD5? I didn't .. @majmoz
GalaXxXx said:
I'm using TWRP v2.8.0.2. What do you mean by saying you're pretty sure I checked the MD5? I didn't .. @majmoz
Click to expand...
Click to collapse
You should always check the MD5 of downloaded files to ensure they did not get corrupted during the downloading process. The MD5 is generally noted on the download site. Here is a how to check the MD5.
I also recommend to use 2.6.3.3 instead of 2.8+
Ohh my god, finally did it !!! Thank you a lot guys !!! I was trying guru reset earlier with unlocked bootloader too, but the twrp version was wrong... ohh, everything because of this new version of twrp.... But thanks, I have my system back . I will be able to do OTA updates now ?
@majmoz @alray
GalaXxXx said:
Ohh my god, finally did it !!! Thank you a lot guys !!! I was trying guru reset earlier with unlocked bootloader too, but the twrp version was wrong... ohh, everything because of this new version of twrp.... But thanks, I have my system back . I will be able to do OTA updates now ?
@majmoz @alray
Click to expand...
Click to collapse
you should be able to do ota if you have selected to install stock recovery in the aroma installer.
hello
I have the htc one model PN07100
i got a stock rom without google apps so I tried to install a custom rom.
i have the TWRP installed and I tried to flash a few roms like android revolution and others, the installing success but when I reboot after the install it's brings me back to the fastboot mode.
here is the fastboot info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.06.651.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ************
(bootloader) imei: **********
(bootloader) meid: **********
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3840mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-371c4f408e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thanks!
MasteRoi said:
hello
I have the htc one model PN07100
i got a stock rom without google apps so I tried to install a custom rom.
i have the TWRP installed and I tried to flash a few roms like android revolution and others, the installing success but when I reboot after the install it's brings me back to the fastboot mode.
here is the fastboot info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.06.651.4
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ************
(bootloader) imei: **********
(bootloader) meid: **********
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3840mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-371c4f408e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thanks!
Click to expand...
Click to collapse
You have the Sprint version of the HTC One. are you sure your using the Sprint version of the roms your flashing ? the GSM roms wont work and be careful cos if you keep flashing them they will kill your phone, the partition layouts are different.
Also make sure your using the recommended version of recovery for the flashes, on the GSM version its TWRP 2.6.3.3
Your HTC One is Sprint M7-wls, you should only be flashing Software for Sprint phones, The Roms you've tried are for International HTC One M7_ul.
Download TWRP from here and flash it with fastboot http://techerrata.com/browse/twrp2/m7wls To be certain you have a Sprint compatible recovery.
[
Code:
fastboot flash recovery name-of-recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot to TWRP, Select "Wipe" then "Format Data" You will be prompted to type Yes to continue. When its done Reboot Recovery.
Download a Sprint Rom from here http://forum.xda-developers.com/sprint-htc-one/development put the rom file in your fastboot folder and rename it rom.zip.
With the phone on the TWRP home screen connect usb and push the rom to the phone
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes. When its done install the rom with TWRP.
Danny201281 said:
Your HTC One is Sprint M7-wls, you should only be flashing Software for Sprint phones, The Roms you've tried are for International HTC One M7_ul.
Download TWRP from here and flash it with fastboot http://techerrata.com/browse/twrp2/m7wls To be certain you have a Sprint compatible recovery.
[
Code:
fastboot flash recovery name-of-recovery.img
fastboot erase cache
fastboot reboot-bootloader
Boot to TWRP, Select "Wipe" then "Format Data" You will be prompted to type Yes to continue. When its done Reboot Recovery.
Download a Sprint Rom from here http://forum.xda-developers.com/sprint-htc-one/development put the rom file in your fastboot folder and rename it rom.zip.
With the phone on the TWRP home screen connect usb and push the rom to the phone
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push completes. When its done install the rom with TWRP.
Click to expand...
Click to collapse
thanks for the answer Seanie280672 and Danny201281
I did the all steps, i success to install a rom but now it's stucked in the opening screen (the screen that you have to slide up to continue)
and when i slide the phone rebooting...
MasteRoi said:
thanks for the answer Seanie280672 and Danny201281
I did the all steps, i success to install a rom but now it's stucked in the opening screen (the screen that you have to slide up to continue)
and when i slide the phone rebooting...
Click to expand...
Click to collapse
Is that with all ROM's ? Just try a different one, maybe the one you tried is just a little unstable.
MasteRoi said:
thanks for the answer Seanie280672 and Danny201281
I did the all steps, i success to install a rom but now it's stucked in the opening screen (the screen that you have to slide up to continue)
and when i slide the phone rebooting...
Click to expand...
Click to collapse
Seanie280672 said:
Is that with all ROM's ? Just try a different one, maybe the one you tried is just a little unstable.
Click to expand...
Click to collapse
This ^^^^
It's worth trying a different ROM, but if all else fails you should be able to return to stock using the RUU and Firmware from here http://forum.xda-developers.com/showthread.php?t=2795856
You will probably need to flash the firmware first to downgrade your hboot before the RUU will flash. I'm not 100% sure how that works for Sprint phones. It certainly won't do any harm so best to do it anyway. If the problem continues after the RUU then Unfortunatly it probably means you've damaged your flash memory some how. Does the device still have warranty?
thanks a lot friends!
I've installed the viper rom and it's works fine!
thanks again!
I'm trying to flash the new recovery to my HTC One but it just says waiting for device. I don't think my PC recognizes my phone. Its stuck in a bootloop also. On the bootloader it says fastboot usb though.
MattFromElkford said:
I'm trying to flash the new recovery to my HTC One but it just says waiting for device. I don't think my PC recognizes my phone. Its stuck in a bootloop also. On the bootloader it says fastboot usb though.
Click to expand...
Click to collapse
What OS do you have on your PC?
Danny201281 said:
What OS do you have on your PC?
Click to expand...
Click to collapse
Windows 8
MattFromElkford said:
Windows 8
Click to expand...
Click to collapse
Windows 8 can be a bit finicky when it comes to fastboot. Is your device on hboot 1.44? Windows 8 is in no way compatible with hboot 1.44 if its anything higher you probably just need to play with the drivers.
What is the device listed as in Device Manger on the PC? It should be "My HTC"
Danny201281 said:
Windows 8 can be a bit finicky when it comes to fastboot. Is your device on hboot 1.44? Windows 8 is in no way compatible with hboot 1.44 if its anything higher you probably just need to play with the drivers.
What is the device listed as in Device Manger on the PC? It should be "My HTC"
Click to expand...
Click to collapse
That is exactly the hboot I have (1.44.0000). Can i try that with a windows xp pc? I have one lying around I can try?
MattFromElkford said:
That is exactly the hboot I have (1.44.0000). Can i try that with a windows xp pc? I have one lying around I can try?
Click to expand...
Click to collapse
XP is a little old but it should work with hboot 1.44. Alternatively you can use a Linux USB Pen drive
MattFromElkford said:
That is exactly the hboot I have (1.44.0000). Can i try that with a windows xp pc? I have one lying around I can try?
Click to expand...
Click to collapse
XP is a little old but it should work with hboot 1.44. Alternatively you can use a Linux USB Pen drive. I have a mini guide here for that http://forum.xda-developers.com/showthread.php?p=54272479
I managed to get the new TWRP flashed on my phone, Im just trying to sideload or push the Android Revolution HD rom onto it. Do i need to install the Android SDK?
MattFromElkford said:
I managed to get the new TWRP flashed on my phone, Im just trying to sideload or push the Android Revolution HD rom onto it. Do i need to install the Android SDK?
Click to expand...
Click to collapse
If fastboot and adb is working then no. I assume you flashed twrp with fastboot ?
Danny201281 said:
If fastboot and adb is working then no. I assume you flashed twrp with fastboot ?
Click to expand...
Click to collapse
They both appeared to have worked. I pushed the rom to my phone and installed it successfully, however when I went to reboot the phone it got to the beats audio htc start up screen, and appears to be frozen.
Any ideas there? I have a telus phone and I used the international Android Revolution HD rom from the newest version.
MattFromElkford said:
They both appeared to have worked. I pushed the rom to my phone and installed it successfully, however when I went to reboot the phone it got to the beats audio htc start up screen, and appears to be frozen.
Any ideas there? I have a telus phone and I used the international Android Revolution HD rom from the newest version.
Click to expand...
Click to collapse
Its M7_ul right? The rom should work with your device. Try flashing TWRP 2.6.3.3 then reinstall the rom :good:
Danny201281 said:
Its M7_ul right? The rom should work with your device. Try flashing TWRP 2.6.3.3 then reinstall the rom :good:
Click to expand...
Click to collapse
Do I have to wipe anything or just try to install over the other rom? Thanks a ton by the way!
Edit: I wiped the cache and data so I'm trying another install.
MattFromElkford said:
Do I have to wipe anything or just try to install over the other rom? Thanks a ton by the way!
Edit: I wiped the cache and data so I'm trying another install.
Click to expand...
Click to collapse
Yeah that's fine. No wipe required but won't hurt. And your Welcome I think that will do it. i'm not sure ARHD has been tested with the latest TWRP recovery
Danny201281 said:
Yeah that's fine. No wipe required but won't hurt. And your Welcome I think that will do it. i'm not sure ARHD has been tested with the latest TWRP recovery
Click to expand...
Click to collapse
It seems to be stuck at that same screen again, is it supposed to take a long time (>15mins) to boot the first time? I don't want to boot into recovery if it needs to set up or something. The phone is almost at capacity memory wise.
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