Database Develop

Unrooting failed

Recently just bought my one and never realised it was rooted till I got home with it. So I decided last night I would unroot it following a guide on youtube. Successfully relocked bootloader but when I try to flash a ruu I get 12 signature verify fail and a different ruu I get 43 main version check fail.
Hboot-1.54.0000
Radio-4a.17.3250.14
Os-2.24.401.8
Could someone tell me what ruu I should be using to make sure I have downloaded the correct one. I downloaded guru 2.24.401.8.
Thanks in advance.

The guru reset isn't a ruu.
However, you will re-turn to stock, right?
Are you in s-off? s-on?

Guich said:
The guru reset isn't a ruu.
However, you will re-turn to stock, right?
Are you in s-off? s-on?
Click to expand...
Click to collapse
Yeah I am trying to get stock.
How do I find out if S-on or sS-off? I am stuck in bootloader.

In bootloader there is write: s-off or s-on?
Or use the fastboot getvar all and post the result here, without your imei and s/n
Sent from One with Tapa4

Guich said:
In bootloader there is write: s-off or s-on?
Or use the fastboot getvar all and post the result here, without your imei and s/n
Sent from One with Tapa4
Click to expand...
Click to collapse
(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__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4191mV
(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!
finished. total time: 0.054s

Ok, the guru should work fine, have you flashed it from recovery? Which error did you get?
However, you can put your phone in s-off and port it to fully stock
Sent from One with Tapa4

Guich said:
Ok, the guru should work fine, have you flashed it from recovery? Which error did you get?
However, you can put your phone in s-off and port it to fully stock
Sent from One with Tapa4
Click to expand...
Click to collapse
The guru one gives me 12 signature verify fail. Should I be using 401.1 or 401.8? 8 is the one I have been using.
I thought I couldnt turn s-off due to hboot 1.54.0000.
I dont know how to flash it any other way apart from fastboot.

itsadogslife said:
The guru one gives me 12 signature verify fail. Should I be using 401.1 or 401.8? 8 is the one I have been using.
I thought I couldnt turn s-off due to hboot 1.54.0000.
I dont know how to flash it any other way apart from fastboot.
Click to expand...
Click to collapse
The guru zip need a custom recovery like twrp for flashing...
However, you can put in s-off your phone with 1.54 hboot, you've to ise the rumrunnes tool..
Sent from One with Tapa4

I have tried rumrunner, keep getting error.
What guru version do you suggest I use?

itsadogslife said:
I have tried rumrunner, keep getting error.
What guru version do you suggest I use?
Click to expand...
Click to collapse
The guru 2.24.401.8 should work fine because is the same of your version main.
However, which error do you have with rumrunner?

Guich said:
The guru 2.24.401.8 should work fine because is the same of your version main.
However, which error do you have with rumrunner?
Click to expand...
Click to collapse
401.8 is the version I keep trying but still 12 signature verify fail.
Rumrunner just says error: run rumrunner again and READ

itsadogslife said:
401.8 is the version I keep trying but still 12 signature verify fail.
Rumrunner just says error: run rumrunner again and READ
Click to expand...
Click to collapse
Mate, i think you're trying to flash the Guru zip as a firmware zip and this is wrong.
For flash the guru zip you've to install a custom recovery like TWRP, reboot in it and flash the file from the sd of the phone.
When the installation is finished, your phone will boot.
rumrunners give you an error because you've to use it when you're on android

Guich said:
Mate, i think you're trying to flash the Guru zip as a firmware zip and this is wrong.
For flash the guru zip you've to install a custom recovery like TWRP, reboot in it and flash the file from the sd of the phone.
When the installation is finished, your phone will boot.
rumrunners give you an error because you've to use it when you're on android
Click to expand...
Click to collapse
Yeah I am flashing the zip through fastboot, ie fstboot flash zip ruu.zip.
Do I install th custom recovery the same way?
Sorry for being a noob, htc one is more complicated than samsung galaxy.

itsadogslife said:
Yeah I am flashing the zip through fastboot, ie fstboot flash zip ruu.zip.
Do I install th custom recovery the same way?
Sorry for being a noob, htc one is more complicated than samsung galaxy.
Click to expand...
Click to collapse
There are guides for this.
you've to flash a custom recovery with
Code:
fastboot flash recovery nameofrecovery.img
and after boot in it and flash the guru zip.
If you don't have it on your sd, you've to push it with the code
Code:
adb push nameofrom.zip /sdcard/
Finally you can flash it through recovery

I think my phone has had it.
Tried flash recovey and same error, 12 signature verify fail.

itsadogslife said:
I think my phone has had it.
Tried flash recovey and same error, 12 signature verify fail.
Click to expand...
Click to collapse
Mate are you flashing the file in ruu mode? (fastboot oem rebootRUU)?
If yes, and i think yes, you're wrong.
Please, use this guide for flash a custom recovery... (don't check the points 7, 8 and 9, from 6 go to 10)

Guich said:
Mate are you flashing the file in ruu mode? (fastboot oem rebootRUU)?
If yes, and i think yes, you're wrong.
Please, use this guide for flash a custom recovery... (don't check the points 7, 8 and 9, from 6 go to 10)
Click to expand...
Click to collapse
I finally got it sorted mate. I had to unlock my bootloader again, once that was done the phone booted up straight away. Then I booted the ruu on the phone sd and installed from recovery. Thanks for all your help mate.

[Q] Conversion to GPE led to eternal boot loop. Fix?

Hi! I tried to convert my M7 to a GPE with OTAs, but this did not succeed. After that I tried to simply revert it back to stock, this also failed and I am now at a state where the phone boots up, as usual, to the homescreen, but turns off after 3 seconds only to repeat the process. I believe this to be a sort of boot loop.
I have tried pretty much everything I could think of. I tried using ADB, but found out that USB debugging is not on and I am not able to turn it on because of the boot loop.
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh", but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail). However, when flashed stock recovery it seems to succeed, but just as the CWM/ TWRP recovery, I am not able to access it, because it turns off and begins the boot loop.
I then tried flashing Cyanogenmod and CWM/ TWRP, but this did not do anything either. Tried to simply do a factory reset through the bootloader, nope.
My current state is S-ON, Bootloader Unlocked and the only way to interact with the phone is fastboot, because I can't access ADB in order to S-OFF...
So my first question is whether there is a way to S-OFF through fastboo? Since every thread and site I read requires ADB, which I cannot access.
If not.. What to do ?
Thanks in advance!

Sari95 said:
I tried using ADB, but found out that USB debugging is not on and I am not able to turn it on because of the boot loop.
Click to expand...
Click to collapse
ADB is only usable from a booted OS or from custom recovery. In bootloader mode, you can only use FASTBOOT.
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh" but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail).
Click to expand...
Click to collapse
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
However, when flashed stock recovery it seems to succeed, but just as the CWM/ TWRP recovery, I am not able to access it, because it turns off and begins the boot loop.
Click to expand...
Click to collapse
When you flash the recovery partition, also erase cache and reboot the bootloader before attempting to boot in recovery mode. Also make sure the recovery you are flashing is compatible with you variant (i.e M7_UL)
I then tried flashing Cyanogenmod and CWM/ TWRP, but this did not do anything either.
Click to expand...
Click to collapse
How? define "did not do anything either" any error message?
Tried to simply do a factory reset through the bootloader, nope.
Click to expand...
Click to collapse
factory reset only wipe /data of the rom currently installed on your phone, this will not magically revert all the mess you did
My current state is S-ON
Click to expand...
Click to collapse
You must be S-OFF to convert to GPE !!
Bootloader Unlocked and the only way to interact with the phone is fastboot because I can't access ADB in order to S-OFF...
Click to expand...
Click to collapse
you need a working rom to s-off. and again adb only works from recovery. Also from a booted OS with usb debugging ON
So my first question is whether there is a way to S-OFF through fastboo?
Click to expand...
Click to collapse
No
If not.. What to do ?
Click to expand...
Click to collapse
flash a sense based rom (doesnt require s-off)
achieve s-off
flash a gpe rom and do the full conversion (i.e with a GPE ruu)
never s-on and never relock your bootloader when converted to gpe or say goodbye to your phone

alray said:
ADB is only usable from a booted OS or from custom recovery. In bootloader mode, you can only use FASTBOOT.
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
When you flash the recovery partition, also erase cache and reboot the bootloader before attempting to boot in recovery mode. Also make sure the recovery you are flashing is compatible with you variant (i.e M7_UL)
How? define "did not do anything either" any error message?
factory reset only wipe /data of the rom currently installed on your phone, this will not magically revert all the mess you did
You must be S-OFF to convert to GPE !!
you need a working rom to s-off. and again adb only works from recovery. Also from a booted OS with usb debugging ON
No
flash a sense based rom (doesnt require s-off)
achieve s-off
flash a gpe rom and do the full conversion (i.e with a GPE ruu)
never s-on and never relock your bootloader when converted to gpe or say goodbye to your phone
Click to expand...
Click to collapse
Thanks for answering! I am now stuck at the first step :l I believe I've found the correct stock RUU for my device, HTC One M7 bought in Norway, but when I try to download it from htc1guru.com, it downloads a little bit and stops. I am not able to download the full .zip file in order to flash it. I have tested to see if it has anything to do with my internet connection to do, but it doesn't have anything to do with it.
I am now downloading Android Revolution for M7, hoping that it will work....
Do you know if this issue with htc1guru.com is common or not?
Btw, I think it is best if I explain to you the whole process:
1. I downloaded a google play Edition RUU.zip that I could flash to convert the device into GPE.
2. Unlocked and S-OFF'd the device, then I flashed the RUU.zip. After these steps, I had a GPE device. However, the RUU I downloaded was Kitkat 4.4, which I thought would automatically update to 4.4.3. This did not happen.
3. I read more and understood that my CID and modelid had to be changed to CID: GOOGL001 and modelid: PN0712000, and so I did. I did not take note of my original CID, of course, so I don't know what that was :/
4. After having changed those settings, I once again tried to update it with OTA, as one would do with a GPE device, without any luck.
5. Reading on, it became clear that the device had to have stock recovery, which I downloaded and flashed. Once again, no luck with the OTA update. After this point, I gave up the GPE dream and decided to return to stock.
6. Then I read a tutorial to return back to stock, which told me to lock the bootloader and S-ON in order to flash the stock rom. This is did, but the process failed and I was left with a device booting up to homescreen, turning off and on in this endless boot loop.
Hope this helps to clarify my situation

Sari95 said:
6. Then I read a tutorial to return back to stock, which told me to lock the bootloader and S-ON in order to flash the stock rom. This is did, but the process failed and I was left with a device booting up to homescreen, turning off and on in this endless boot loop.
Click to expand...
Click to collapse
Well, I don't know where this tutorial was from, but you don't have to s-on to flash a ruu., you don't even need to relock bootloader to flash a ruu when you have s-off. Never S-ON back unless you absolutely must (sending phone for repair under warranty).
post a fastboot getvar all
are you still able to unlock bootloader?

alray said:
Well, I don't know where this tutorial was from, but you don't have to s-on to flash a ruu., you don't even need to relock bootloader to flash a ruu when you have s-off. Never S-ON back unless you absolutely must (sending phone for repair under warranty).
post a fastboot getvar all
are you still able to unlock bootloader?
Click to expand...
Click to collapse
Yeah... stupid of me not to read several tutorials before trying to return to stock :l
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
I believe I am able to unlock bootloader, yes. A picture is attached, which shows my current bootloader.

Sari95 said:
no luck with the OTA update. After this point, I gave up the GPE dream and decided to return to stock.
Click to expand...
Click to collapse
with s-off, you can download and flash ota update manually.
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
Sari95 said:
Yeah... stupid of me not to read several tutorials before trying to return to stock :l
My getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4086mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.055s
I believe I am able to unlock bootloader, yes. A picture is attached, which shows my current bootloader.
Click to expand...
Click to collapse
thats a good thing you can unlock the bootloader again! many GPE users a stuck with unlockable bootloader with hboot 1.55+.
was you able to flash arhd? Then s-off the phone again and run the ruu you want again (stock or gpe)

alray said:
with s-off, you can download and flash ota update manually.
---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------
thats a good thing you can unlock the bootloader again! many GPE users a stuck with unlockable bootloader with hboot 1.55+.
was you able to flash arhd? Then s-off the phone again and run the ruu you want again (stock or gpe)
Click to expand...
Click to collapse
If by ARHD you mean Android Revolution HD, then no, I am not able to flash it. I get the error : FAILED (24 parsing failure), then nothing happens.
I also tried flashing stock Rug, but since I've changed my CID to CWS__001, while my MID is P0712000, they are in conflict and the RUU doesn't work either. Tried editing the info - Android. The, but no luck there either

Sari95 said:
If by ARHD you mean Android Revolution HD, then no, I am not able to flash it. I get the error : FAILED (24 parsing failure), then nothing happens.
I also tried flashing stock Rug, but since I've changed my CID to CWS__001, while my MID is P0712000, they are in conflict and the RUU doesn't work either. Tried editing the info - Android. The, but no luck there either
Click to expand...
Click to collapse
please post a picture when you got the FAILED error when attempting to flash arhd

alray said:
please post a picture when you got the FAILED error when attempting to flash arhd
Click to expand...
Click to collapse
ok.. so I tried flashing it now, there's a different error.

Sari95 said:
ok.. so I tried flashing it now, there's a different error.
Click to expand...
Click to collapse
ok.... so you are trying to flash a rom from fastboot
with fastboot, you flash recovery, ruu, and firmware only.
roms are flashed from custom recovery... not with fastboot
maybe you should have answered the question above from post #2:
I tried flashing the GPE.zip and stock GPE recovery in order to "start fresh" but this does not seem to have any effect.When flashing the GPE.zip I get the error: FAILED (remote:99 unknown fail).
Click to expand...
Click to collapse
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------
push the rom to your sdcard and flash it using twrp 2.6.3.3

alray said:
ok.... so you are trying to flash a rom from fastboot
with fastboot, you flash recovery, ruu, and firmware only.
roms are flashed from custom recovery... not with fastboot
maybe you should have answered the question above from post #2:
Wait, what is that GPE.zip file? A rom? A ruu? How did you tried to flash it? from recovery? using fastboot?
---------- Post added at 09:06 PM ---------- Previous post was at 09:04 PM ----------
push the rom to your sdcard and flash it using twrp 2.6.3.3
Click to expand...
Click to collapse
Sorry about that. The only recovery I have been able to flash is this one from this thread http://forum.xda-developers.com/showthread.php?t=2739126 . All "normal" CWM/TWRP recoveries will not boot up.
I just flashed ARHD, but when the Aroma installer finishes and I reboot the system this happens:
1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above
Any idea what this means?

Sari95 said:
Sorry about that. The only recovery I have been able to flash is this one from this thread http://forum.xda-developers.com/showthread.php?t=2739126 . All "normal" CWM/TWRP recoveries will not boot up.
Click to expand...
Click to collapse
why? do you have the active cmd line overflow error?

alray said:
why? do you have the active cmd line overflow error?
Click to expand...
Click to collapse
I do not, no, but after trying the usual CWM/ TWRP, the only recovery that actually would boot up was this one.

Sari95 said:
I do not, no, but after trying the usual CWM/ TWRP, the only recovery that actually would boot up was this one.
Click to expand...
Click to collapse
well try to download twrp 2.6.3.3 again from here
check md5: 72067aefb69541d40e8420d7aa46408d
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot the recovery

alray said:
well try to download twrp 2.6.3.3 again from here
check md5: 72067aefb69541d40e8420d7aa46408d
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then try to boot the recovery
Click to expand...
Click to collapse
All right, so now I am able to boot into proper TWRP through the steps, even though I have done the exact ones before anyway, I flashed ARHD again, but still no luck, as it does the same.
"1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above"

Sari95 said:
All right, so now I am able to boot into proper TWRP through the steps, even though I have done the exact ones before anyway, I flashed ARHD again, but still no luck, as it does the same.
"1. Screen turns off, then on.
2. A Google logo appears, turns off
3. Google logo appears, boots into the recovery I mentioned above"
Click to expand...
Click to collapse
have you wiped when you have flashed arhd?
and have you checked md5 value of the rom before flashing it?

alray said:
have you wiped when you have flashed arhd?
Click to expand...
Click to collapse
Of course. these are the steps after booting into recovery:
1. Wipe
2. Advanced Wipe --> check every box
3. Swipe to wipe
4. Install --> flash ARHD through USB OTG

Sari95 said:
Of course. these are the steps after booting into recovery:
1. Wipe
2. Advanced Wipe --> check every box
3. Swipe to wipe
4. Install --> flash ARHD through USB OTG
Click to expand...
Click to collapse
what version of arhd?

alray said:
what version of arhd?
Click to expand...
Click to collapse
The latest I believe:
"Android_Revolution_HD-One_71.1"

Sari95 said:
The latest I believe:
"Android_Revolution_HD-One_71.1"
Click to expand...
Click to collapse
have you checked md5 just in case?

[Q] Softbrick? Need working RUU

Hello,
Ill get right to the point. I need a working RUU, I've tried so many that I'm going to lose my mind!
Each time I get a 130 or 131 error and regularely a 155 error. I can go into recovery but side-load etc. don't work. I don't know why so don't ask me.
A little info about the phone:
bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 4292mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d2906a15
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Please help.

39 vieuws and nobody has even left a reply ._.

1gangstabob2 said:
Hello,
Ill get right to the point. I need a working RUU, I've tried so many that I'm going to lose my mind!
Each time I get a 130 or 131 error
Click to expand...
Click to collapse
Error 130 = wrong MID thats mean the ruu you are using isn't for your phone.
Error 131 = Wrong CID thats also mean the ruu isn't the right one for your phone
and regularely a 155 error.
Click to expand...
Click to collapse
error 155 = wrong image ruu, mean that you are not using the correct ruu for your phone
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-main: 3.63.111.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: T-MOB101
Click to expand...
Click to collapse
There is no RUU you can use on that phone with S-ON. What you can do is to s-off and then flash another version RUU, return back to stock using a nandroid backup or simply flash a custom rom.
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
1gangstabob2 said:
39 vieuws and nobody has even left a reply ._.
Click to expand...
Click to collapse
Do you prefer 39 persons posting random things to confuse you more? If someone visit this thread, it doesn't mean he know the answer...
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
btw what happened to your phone?

alray said:
Error 130 = wrong MID thats mean the ruu you are using isn't for your phone.
Error 131 = Wrong CID thats also mean the ruu isn't the right one for your phone
error 155 = wrong image ruu, mean that you are not using the correct ruu for your phone
There is no RUU you can use on that phone with S-ON. What you can do is to s-off and then flash another version RUU, return back to stock using a nandroid backup or simply flash a custom rom.
---------- Post added at 09:37 AM ---------- Previous post was at 09:36 AM ----------
Do you prefer 39 persons posting random things to confuse you more? If someone visit this thread, it doesn't mean he know the answer...
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
btw what happened to your phone?
Click to expand...
Click to collapse
I tried Android Revolution HD 82 ROM but it went in a bootloop. Now it doesn't boot anymore and I can only get to recovery and Hboot menu. Sideload doesn't work anymore and I don't know what to do anymore..... Also S-off wasn't possible because I had 1.55 or something like that. I don't know what to do....

1gangstabob2 said:
I tried Android Revolution HD 82 ROM but it went in a bootloop. Now it doesn't boot anymore and I can only get to recovery and Hboot menu. Sideload doesn't work anymore and I don't know what to do anymore..... Also S-off wasn't possible because I had 1.55 or something like that. I don't know what to do....
Click to expand...
Click to collapse
What recovery (name and version) are you using?
S-OFF can be achieved on hboot 1.55 but you'll first need a working rom.

alray said:
What recovery (name and version) are you using?
S-OFF can be achieved on hboot 1.55 but you'll first need a working rom.
Click to expand...
Click to collapse
I did give it a try sometime with Revone but it gave a weird error, also I was using TWRP but now clockworkmod, even if I flash TWRP bakc again it wont work... and when I try to go in recovery it says it cant mount data¿
EDIT: I just tried to go in recovery and it didnt gave any "cant mount" errors¿?¿

1gangstabob2 said:
I did give it a try sometime with Revone but it gave a weird error, also I was using TWRP but now clockworkmod, even if I flash TWRP bakc again it wont work... and when I try to go in recovery it says it cant mount data¿
Click to expand...
Click to collapse
I asked a simple answer: what recovery (name and version are you using)
example of answer: I have used CWM 6.?.?.? or TWRP 2.?.?.? to flash the rom.
---------- Post added at 03:08 PM ---------- Previous post was at 03:08 PM ----------
1gangstabob2 said:
I did give it a try sometime with Revone but it gave a weird error, also I was using TWRP but now clockworkmod, even if I flash TWRP bakc again it wont work... and when I try to go in recovery it says it cant mount data¿
EDIT: I just tried to go in recovery and it didnt gave any "cant mount" errors¿?¿
Click to expand...
Click to collapse
revone can only be used on hboot 1.44. for higher hboot version use others exploits.

alray said:
I asked a simple answer: what recovery (name and version are you using)
example of answer: I have used CWM 6.?.?.? or TWRP 2.?.?.? to flash the rom.
---------- Post added at 03:08 PM ---------- Previous post was at 03:08 PM ----------
revone can only be used on hboot 1.44. for higher hboot version use others exploits.
Click to expand...
Click to collapse
Clockworkmod Recovery 6.0.4.3

1gangstabob2 said:
Clockworkmod Recovery 6.0.4.3
Click to expand...
Click to collapse
arhd must be flashed using twrp 2.6.3.3. I would suggest you to flash that recovery version and try again to flash arhd:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery and try to flash arhd again
report back after you have tried this.

alray said:
arhd must be flashed using twrp 2.6.3.3. I would suggest you to flash that recovery version and try again to flash arhd:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
then boot in recovery and try to flash arhd again
report back after you have tried this.
Click to expand...
Click to collapse
But I don't have the file on my SD card anymore...How do I install it then?

1gangstabob2 said:
But I don't have the file on my SD card anymore...How do I install it then?
Click to expand...
Click to collapse
use adb push to copy to rom from your computer to the phone storage.
Code:
adb push name_of_rom.zip /sdcard
the rom must be in the same folder where you have adb and fastboot
phone must be booted in twrp main menu.

alray said:
use adb push to copy to rom from your computer to the phone storage.
Code:
adb push name_of_rom.zip /sdcard
the rom must be in the same folder where you have adb and fastboot
phone must be booted in twrp main menu.
Click to expand...
Click to collapse
I've already got it working, I flashed the TWRP and it sensed that some files were damaged and offered to recover them, so I let it recover them and enabled MTP via TWRP and litteraly the first thing I did was take a back-up. Now im on Maximus HD. Thanks anyway m8.
EDIT: Already got a bootloop from Maximu HD... What am I doing wrong? @alray

1gangstabob2 said:
I've already got it working, I flashed the TWRP and it sensed that some files were damaged and offered to recover them, so I let it recover them and enabled MTP via TWRP and litteraly the first thing I did was take a back-up. Now im on Maximus HD. Thanks anyway m8.
EDIT: Already got a bootloop from Maximu HD... What am I doing wrong? @alray
Click to expand...
Click to collapse
the rom is bootlooping after you have flashed it?
Have you cheked your md5 on both the rom and the recovery to make sure its not a bad download?

alray said:
the rom is bootlooping after you have flashed it?
Have you cheked your md5 on both the rom and the recovery to make sure its not a bad download?
Click to expand...
Click to collapse
They don't match...Does this mean I can't use this ROM?

1gangstabob2 said:
They dont match...Does this mean I cant use this ROM?
Click to expand...
Click to collapse
If the rom MD5 doesnt match the value from where you have downloaded the file, its a bad download. Download again

alray said:
If the rom MD5 doesnt match the value from where you have downloaded the file, its a bad download. Download again
Click to expand...
Click to collapse
This time it did match and now it isn't booting at all...Also said set_metadata_recursive some changes failed. What does it mean by that?

1gangstabob2 said:
This time it did match and now it isnt booting at all...Also said set_metadata_recursive some changes failed. What does it mean by that?
Click to expand...
Click to collapse
Are you using twrp 2.6.3.3 or another version?

similar problem
alray said:
Are you using twrp 2.6.3.3 or another version?
Click to expand...
Click to collapse
HI , i have similar but terrible problem in flashing custom ROM in HTC one M7 .
after unlocked the bootloader and install TWRP recovery , the phone works fine . However , when i was trying to flash ARHD ROM , after the successful installation and reboot system , i was directed back to the recovery again. I was suggested to change the recovery through the method from youtube video. and i was able to flash the ROM through CWM. However , when i was reboot the system , i was directed to the TWRP that doesn't work properly with flashing on the screen. I was trying to install the stock ROM back but error happened and installation was aborted. NO matter what recovery i used , no matter how i format the data , i'm still directed to TWRP that work / doesn't work properly . Any expert opinion are very very appreciated. Thank you .
the root access also missing as well. im using the latest TWRP and CWM.

yusiongng said:
HI , i have similar but terrible problem in flashing custom ROM in HTC one M7 .
after unlocked the bootloader and install TWRP recovery , the phone works fine . However , when i was trying to flash ARHD ROM , after the successful installation and reboot system , i was directed back to the recovery again. I was suggested to change the recovery through the method from youtube video. and i was able to flash the ROM through CWM. However , when i was reboot the system , i was directed to the TWRP that doesn't work properly with flashing on the screen. I was trying to install the stock ROM back but error happened and installation was aborted. NO matter what recovery i used , no matter how i format the data , i'm still directed to TWRP that work / doesn't work properly . Any expert opinion are very very appreciated. Thank you .
the root access also missing as well. im using the latest TWRP and CWM.
Click to expand...
Click to collapse
oh c'mon guys, this has been mentioned thousands and thousands of times, and it's even mentioned in the FAQ sticky!!
if you get set_metadata errors, you need to use TWRP 2.6.3.3 or 2.8.0.0 or 2.8.0.1 (if you have m7_u or m7_ul, not the other versions!!

alray said:
Are you using twrp 2.6.3.3 or another version?
Click to expand...
Click to collapse
2.8.1.0.
.
yusiongng said:
HI , i have similar but terrible problem in flashing custom ROM in HTC one M7 .
after unlocked the bootloader and install TWRP recovery , the phone works fine . However , when i was trying to flash ARHD ROM , after the successful installation and reboot system , i was directed back to the recovery again. I was suggested to change the recovery through the method from youtube video. and i was able to flash the ROM through CWM. However , when i was reboot the system , i was directed to the TWRP that doesn't work properly with flashing on the screen. I was trying to install the stock ROM back but error happened and installation was aborted. NO matter what recovery i used , no matter how i format the data , i'm still directed to TWRP that work / doesn't work properly . Any expert opinion are very very appreciated. Thank you .
the root access also missing as well. im using the latest TWRP and CWM.
Click to expand...
Click to collapse
Go to recovery and wipe everything. If you can't go into recovery then do a factory reset via the HBoot and if you have done the wiping flash a new recovery (I use the toolkit HTC one toolkit) and if you have succeeded go into recovery and the new recovery will fix the errors for you.
nkk71 said:
oh c'mon guys, this has been mentioned thousands and thousands of times, and it's even mentioned in the FAQ sticky!!
if you get set_metadata errors, you need to use TWRP 2.6.3.3 or 2.8.0.0 or 2.8.0.1 (if you have m7_u or m7_ul, not the other versions!!
Click to expand...
Click to collapse
I litterally never have seen this. But thanks anyway.
UPDATE: I somehow got the MaxHD working...I suspect it has to do with the separate boot.img file which I have flashed via Fastboot.
Thanks for all the help and may this thread help alot of others.

Cant get out from relocked state + cant flash recovery. Im locked in box with no key!

It happened when i was trying to flash a stock recovery img, so that i could update my htc one m7 with the official update from the phone "OTA_M7_UL_L50_SENSE60_MR_HTC_EUROPE_7.19.401.2-6.09.401.11_release_4217922wykl17vamtts1919.zip"
I cant do anything from the bootloader, beside i have my" Unlock_code" from past and can get that working allright, even that doesnt unlocks my phone anymore.
All though im able to use my phone, i want to update to the latest version.
So anyone out there in the big world, who can help me?

dukocuk said:
It happened when i was trying to flash a stock recovery img, so that i could update my htc one m7 with the official update from the phone "OTA_M7_UL_L50_SENSE60_MR_HTC_EUROPE_7.19.401.2-6.09.401.11_release_4217922wykl17vamtts1919.zip"
I cant do anything from the bootloader, beside i have my" Unlock_code" from past and can get that working allright, even that doesnt unlocks my phone anymore.
All though im able to use my phone, i want to update to the latest version.
So anyone out there in the big world, who can help me?
Click to expand...
Click to collapse
If you want to update your phone, why are you trying to unlock its bootloader? Do you have re-locked your bootloader with a custom recovery installed? Unlocking the bootloader will wipe /data/preload folder and preventing the ota update to install... I do not really understand what you are trying to do here because you are not giving much information about the actual state of your phone...
Is your phone running the stock rom?
You have relocked the bootloader with a custom recovery?
please post the output of "fastboot getvar all" (remove imei and serialno before posting)

alray said:
If you want to update your phone, why are you trying to unlock its bootloader? Do you have re-locked your bootloader with a custom recovery installed? Unlocking the bootloader will wipe /data/preload folder and preventing the ota update to install... I do not really understand what you are trying to do here because you are not giving much information about the actual state of your phone...
Is your phone running the stock rom?
You have relocked the bootloader with a custom recovery?
please post the output of "fastboot getvar all" (remove imei and serialno before posting)
Click to expand...
Click to collapse
i was trying to update it so i flashed a stockrecovery on it, else i wouldnt be able to update my phone with the OTA it gave me because i had a custom recovery on it before.
All i want is to update my phone with the stock rom, and then unlock it , so i can have a custom recovery again.
i messed it pretty good, so i have no recovery on it now i guess.
Its TAMPERED, RELOCKED and S-ON
my "fastboot getvar all" output is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3813mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s

dukocuk said:
i was trying to update it so i flashed a stockrecovery on it, else i wouldnt be able to update my phone with the OTA it gave me because i had a custom recovery on it before.
All i want is to update my phone with the stock rom, and then unlock it , so i can have a custom recovery again.
i messed it pretty good, so i have no recovery on it now i guess.
Its TAMPERED, RELOCKED and S-ON
my "fastboot getvar all" output is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 3813mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.108s
Click to expand...
Click to collapse
What happens when you try to unlock the bootloader?

alray said:
What happens when you try to unlock the bootloader?
Click to expand...
Click to collapse
i can do flash unlock_code.bin, then it just deletes everything and im starting a fresh htc. In bootloader it then says tampered and relocked + s-on, it wont unlock it and even that it is locked, it wont update it to the newest official OTA update (7.19.401.2 / 804.78MB).
When it tries to enter recovery it isay: TAMPERED, RELOCKED and Security Warning , it just goes in the bootloader and not recovery.

dukocuk said:
i can do flash unlock_code.bin, then it just deletes everything and im starting a fresh htc. In bootloader it then says tampered and relocked + s-on, it wont unlock it and even that it is locked, it wont update it to the newest official OTA update (7.19.401.2 / 804.78MB).
When it tries to enter recovery it isay: TAMPERED, RELOCKED and Security Warning , it just goes in the bootloader and not recovery.
Click to expand...
Click to collapse
do you have a custom recovery installed ?
if so, the only way you can unlock the bootloader is to flash the stock firmware to put stock recovery back on, you cant lock or relock the bootloader with custom software on your phone.
Stock firmware here: https://www.androidfilehost.com/?fid=95832962473395871

i had custom recovery, but i flashed stockrecovery on it. Must have bricked the recovery somehow, because now i have no reecovery. If i try to flash the recovery i get this, no matter if i try to flash custom or stock recovery:
D:\adb>fastboot flash recover recovery_6.09.401.5.img
target reported max download size of 1514139648 bytes
sending 'recover' (12570 KB)...
OKAY [ 1.519s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.767s
maybe because its locked, and i cant unlock it.

dukocuk said:
i had custom recovery, but i flashed stockrecovery on it. Must have bricked the recovery somehow, because now i have no reecovery. If i try to flash the recovery i get this, no matter if i try to flash custom or stock recovery:
D:\adb>fastboot flash recover recovery_6.09.401.5.img
target reported max download size of 1514139648 bytes
sending 'recover' (12570 KB)...
OKAY [ 1.519s]
writing 'recover'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.767s
maybe because its locked, and i cant unlock it.
Click to expand...
Click to collapse
yup, beacuse your bootloader is locked, only way to fix it is to flash the firmware, is there anything on the phone internal storage that you need to keep, pictures, musci, documents etc ?

Seanie280672 said:
yup, beacuse your bootloader is locked, only way to fix it is to flash the firmware, is there anything on the phone internal storage that you need to keep, pictures, musci, documents etc ?
Click to expand...
Click to collapse
the hel-l with my docs and stuff, how do you flash this .zip file? I cant reach my recovery, since its messed.

dukocuk said:
the hel-l with my docs and stuff, how do you flash this .zip file? I cant reach my recovery, since its messed.
Click to expand...
Click to collapse
with the phone in fastbootUSB mode and the zip in the same folder as adb and fastboot on your computer, issue these commands:
ps: its easier if you rename the download to just firmware rather than M7_UL_Firmware_6.09.401.11
fastboot oem rebootRUU (case sensetive) phone screen will go black with silver HTC logo
fastboot flash zip firmware.zip (first time it might say failed: please flush again) so issue the command again
fastboot flash zip firmware.zip
make sure it now says successful at the bottom - this is important
if so then,
fastboot reboot-bootloader
if not report back here first
when you get back to the bootloader, try and unlock it again, you may have to go back to HTCDev site and get a new unlock token.

Seanie280672 said:
with the phone in fastbootUSB mode and the zip in the same folder as adb and fastboot on your computer, issue these commands:
ps: its easier if you rename the download to just firmware rather than M7_UL_Firmware_6.09.401.11
fastboot oem rebootRUU (case sensetive) phone screen will go black with silver HTC logo
fastboot flash zip firmware.zip (first time it might say failed: please flush again) so issue the command again
fastboot flash zip firmware.zip
make sure it now says successful at the bottom - this is important
if so then,
fastboot reboot-bootloader
if not report back here first
when you get back to the bootloader, try and unlock it again, you may have to go back to HTCDev site and get a new unlock token.
Click to expand...
Click to collapse
im tampered and unlocked now after i did what you told, but i used my old Unlock.bin. Where do i go from here?

dukocuk said:
im tampered and unlocked now after i did what you told, but i used my old Unlock.bin. Where do i go from here?
Click to expand...
Click to collapse
ok follow these instructions I laid out for someone else if your looking to return to stock, they are exactly the same for your phone as your on the same firmware:
http://forum.xda-developers.com/showpost.php?p=59273464&postcount=4
ps. you dont need to lock or relock your bootloader to update, you only need locked or relocked whilst s-on to flash firmware or run an RUU.

Seanie280672 said:
ok follow these instructions I laid out for someone else if your looking to return to stock, they are exactly the same for your phone as your on the same firmware:
http://forum.xda-developers.com/showpost.php?p=59273464&postcount=4
ps. you dont need to lock or relock your bootloader to update, you only need locked or relocked whilst s-on to flash firmware or run an RUU.
Click to expand...
Click to collapse
so all you need is a stock recovery to update OTA? When do i use firmware and RUU? Sorry my noobish questions, did read the guides but didnt get the idea fully.

dukocuk said:
so all you need is a stock recovery to update OTA? When do i use firmware and RUU? Sorry my noobish questions.
Click to expand...
Click to collapse
use firmware for when you have problems like you did earlier or if your s-off, earlier RUU's are only if your phone is S-off and saves all this messing around, its full firmware and rom in one package, if you were s-off, then we could of just flashed the corrisponding firmware to an RUU, ran the RUU, you'd then be 100% factory stock, just boot and update from there.
theres a bit more to it than just stock recovery, your rom has to be 100% stock, no root, no custom kernals or anything like that, no removed stock apps.
trouble is, when you unlock the bootloader, it deletes a hidden folder (data/preload folder) its HTC's little way of say, now you've unlocked, you can never update with us again, that backup will put all of that back on your phone.

Seanie280672 said:
use firmware for when you have problems like you did earlier or if your s-off, earlier RUU's are only if your phone is S-off and saves all this messing around, its full firmware and rom in one package, if you were s-off, then we could of just flashed the corrisponding firmware to an RUU, ran the RUU, you'd then be 100% factory stock, just boot and update from there.
theres a bit more to it than just stock recovery, your rom has to be 100% stock, no root, no custom kernals or anything like that, no removed stock apps.
trouble is, when you unlock the bootloader, it deletes a hidden folder (data/preload folder) its HTC's little way of say, now you've unlocked, you can never update with us again, that backup will put all of that back on your phone.
Click to expand...
Click to collapse
So you gave me the firmware, its on the phone now.
I had Unlock.bin, but i can see it has supersu installed in it.
i flashed to stockrecovery from where you helped the other guy.
Im waiting for my download OTA update to finish (official).
Will i be able to update it even that i see its rootet (supersu)???

dukocuk said:
So you gave me the firmware, its on the phone now.
I had Unlock.bin, but i can see it has supersu installed in it.
i flashed to stockrecovery from where you helped the other guy.
Im waiting for my download OTA update to finish (official).
Will i be able to update it even that i see its rootet (supersu)???
Click to expand...
Click to collapse
try it, but I think you'll have to follow that whole post of mine that I linked you too, superSU modifies system files to root, so the OTA may error out.
if it does error, you'll have to start from here "what you need to do is flash TWRP 2.8.5.0 from here:" and follow every step, you wont need that firmware that you downloaded earlier again, just dont lock your bootloader.

Seanie280672 said:
try it, but I think you'll have to follow that whole post of mine that I linked you too, superSU modifies system files to root, so the OTA may error out.
if it does error, you'll have to start from here "what you need to do is flash TWRP 2.8.5.0 from here:" and follow every step, you wont need that firmware that you downloaded earlier again, just dont lock your bootloader.
Click to expand...
Click to collapse
you gave him https://www.androidfilehost.com/?fid=95832962473396067, what will it be on my phone? That other zip file you gave me? Is it that one i should install from recovery? If yes, why? Didnt i just installed it from RUU?

dukocuk said:
you gave him https://www.androidfilehost.com/?fid=95832962473396067, what will it be on my phone?
Click to expand...
Click to collapse
same files for your phone, have a look at the version main on your fastbootgetvar all on the first page 6.09.401.11 that download is the same version main, M7_UL_TWRP_Nandroid_6.09.401.11_(inkl._preload-Ordner).rar and this part means it contains the data/preload folder (inkl._preload-Ordner)
dukocuk said:
That other zip file you gave me? Is it that one i should install from recovery? If yes, why? Didnt i just installed it from RUU?
Click to expand...
Click to collapse
bin that firmware file, you wont need it again.

Seanie280672 said:
same files for your phone, have a look at the version main on your fastbootgetvar all on the first page 6.09.401.11 that download is the same version main, M7_UL_TWRP_Nandroid_6.09.401.11_(inkl._preload-Ordner).rar and this part means it contains the data/preload folder (inkl._preload-Ordner)
bin that firmware file, you wont need it again.
Click to expand...
Click to collapse
Thank, i followed the guide you made for that person, it helped me out too.
I appreciate it.

Stuck on Bootloader and can't access recovery.

Hi
I'm running XENON HD and tried to do an OTA upgrade. When I came back to my phone, it was in the bootloader screen. After every reboot, it goes there.
This wouldn't normally be a problem except that my volume keys are damaged and I can't select any option from the bootloader screen.
I tried a #fastboot boot twrp.img but it doesn't reboot the phone.
Is there any way I can access recovery another way? I did a backup (on the sd card ) so I really just need to get into recovery.
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
Any help/ideas is appreciated.
Thanks!

Perf_engineer said:
Hi
I'm running XENON HD and tried to do an OTA upgrade. When I came back to my phone, it was in the bootloader screen. After every reboot, it goes there.
This wouldn't normally be a problem except that my volume keys are damaged and I can't select any option from the bootloader screen.
I tried a #fastboot boot twrp.img but it doesn't reboot the phone.
Is there any way I can access recovery another way? I did a backup (on the sd card ) so I really just need to get into recovery.
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.61.0000
Any help/ideas is appreciated.
Thanks!
Click to expand...
Click to collapse
fastboot boot twrp.img was only working on hboot 1.44 back in 2013, this command was disabled with 1.54 and all newer hboot.
There is no command to make your phone reboot in recovery from the bootloader so i'm afraid you will not be able to go back in recovery. If at least your phone is in bootloader mode with "fastboot usb" in red you can relock your BL and restore using a RUU. Once the ruu is flashed the phone will reboot to the OS by itself.

alray said:
fastboot boot twrp.img was only working on hboot 1.44 back in 2013, this command was disabled with 1.54 and all newer hboot.
There is no command to make your phone reboot in recovery from the bootloader so i'm afraid you will not be able to go back in recovery. If at least your phone is in bootloader mode with "fastboot usb" in red you can relock your BL and restore using a RUU. Once the ruu is flashed the phone will reboot to the OS by itself.
Click to expand...
Click to collapse
Crap.. At least it isn't dead. Thanks for your help

alray said:
fastboot boot twrp.img was only working on hboot 1.44 back in 2013, this command was disabled with 1.54 and all newer hboot.
There is no command to make your phone reboot in recovery from the bootloader so i'm afraid you will not be able to go back in recovery. If at least your phone is in bootloader mode with "fastboot usb" in red you can relock your BL and restore using a RUU. Once the ruu is flashed the phone will reboot to the OS by itself.
Click to expand...
Click to collapse
Hi alray.
I downloaded what i thought was the right RUU but I am getting an error message saying it can't verify the signature.
How can I tell which RUU I should use? I don't care what goes on it as I will be unlocking the bootloader again and putting back on a custom rom.
Thanks
./fastboot flash zip RUU.zip
sending 'zip' (1463809 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)

Perf_engineer said:
Hi alray.
I downloaded what i thought was the right RUU but I am getting an error message saying it can't verify the signature.
How can I tell which RUU I should use? I don't care what goes on it as I will be unlocking the bootloader again and putting back on a custom rom.
Thanks
./fastboot flash zip RUU.zip
sending 'zip' (1463809 KB)... OKAY
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
Click to expand...
Click to collapse
Nevermind. I found the CID and MID of my phone. Downloading now. hopefully it will work

Perf_engineer said:
Nevermind. I found the CID and MID of my phone. Downloading now. hopefully it will work
Click to expand...
Click to collapse
Nope
Any thoughts?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3AHW902491
(bootloader) imei: 359405051005401
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4204mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
No version main.
I can't find an exe for my model. Apparently zip files won't work when you are missing the verison

Fastboot reboot
Fastboot flash recovery
Fastboot reboot
Fastboot reboot recovery
If you have a kik. Feel free to contact me under the same name for quick assistance

Tony the noob :D said:
Fastboot reboot
Fastboot flash recovery
Fastboot reboot
Fastboot reboot recovery
If you have a kik. Feel free to contact me under the same name for quick assistance
Click to expand...
Click to collapse
Thanks for the offer. Don't have kik unfortunately.
Current state I'm in is that I have relocked my phone, but the version_main is blank.
flashing from zip doesn't work in RUU.
I tried to flash the recovery again but keep getting the signature failed message

Perf_engineer said:
Thanks for the offer. Don't have kik unfortunately.
Current state I'm in is that I have relocked my phone, but the version_main is blank.
flashing from zip doesn't work in RUU.
I tried to flash the recovery again but keep getting the signature failed message
Click to expand...
Click to collapse
Your trying to do a HTC OTA Update?

pardon me for stealing the thread. In a related issue.
https://forum.xda-developers.com/htc-one-tmobile/development/recent-zip-ruu-t-mo-t3662241
which RUU or rom to install?

Perf_engineer said:
I can't find an exe for my model. Apparently zip files won't work when you are missing the verison
Click to expand...
Click to collapse
Yes zip version will work even if your version-main is blank, since you don't know your version-main, use the latest ruu for your cid/mid. If the latest version ruu isn't available in the ruu collection thread, you'll probably have to download it from easy-firmware.com or a similar website.
---------- Post added at 06:48 AM ---------- Previous post was at 06:46 AM ----------
Perf_engineer said:
Thanks for the offer. Don't have kik unfortunately.
Current state I'm in is that I have relocked my phone, but the version_main is blank.
flashing from zip doesn't work in RUU.
I tried to flash the recovery again but keep getting the signature failed message
Click to expand...
Click to collapse
you can't flash the recovery partition when the BL is locked. The BL must be locked to flash the ruu.

Tony the noob :D said:
Your trying to do a HTC OTA Update?
Click to expand...
Click to collapse
Is that possible? I can't load any rom at the moment.

Tony the noob :D said:
Fastboot reboot
Fastboot flash recovery
Fastboot reboot
Fastboot reboot recovery
If you have a kik. Feel free to contact me under the same name for quick assistance
Click to expand...
Click to collapse
I thought you can't fastboot into recovery?
At least I never could. If I can I could have solved this ages ago

alray said:
Yes zip version will work even if your version-main is blank, since you don't know your version-main, use the latest ruu for your cid/mid. If the latest version ruu isn't available in the ruu collection thread, you'll probably have to download it from easy-firmware.com or a similar website.
---------- Post added at 06:48 AM ---------- Previous post was at 06:46 AM ----------
you can't flash the recovery partition when the BL is locked. The BL must be locked to flash the ruu.
Click to expand...
Click to collapse
crap crap crap.
I just tried to unlock the bootloader again. Remember when I said the volume keys were damaged? I should have been more specific.. The phone fell and damaged the volume up key and it is pressed in. This doesn't allow me to use the power button to select. So I can't unlock the bootloader now :\ (unless I can give it a default acceptance?)
So I think my only options are to put on the stock and leave it as is
Or open the phone up so the case isn't pressing on the volume key.
This was the RUU I tried. It seems to be the latest and the right version.
PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_423416_combined_signed.zip
can anyone confirm?
Thanks

Perf_engineer said:
I thought you can't fastboot into recovery?
At least I never could. If I can I could have solved this ages ago
Click to expand...
Click to collapse
no you can't
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
Perf_engineer said:
crap crap crap.
I just tried to unlock the bootloader again. Remember when I said the volume keys were damaged? I should have been more specific.. The phone fell and damaged the volume up key and it is pressed in. This doesn't allow me to use the power button to select. So I can't unlock the bootloader now :\ (unless I can give it a default acceptance?)
So I think my only options are to put on the stock and leave it as is
Or open the phone up so the case isn't pressing on the volume key.
This was the RUU I tried. It seems to be the latest and the right version.
PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_423416_combined_signed.zip
can anyone confirm?
Thanks
Click to expand...
Click to collapse
use the 7.18.206.51 ruu, it's the latest one for o2

alray said:
no you can't
---------- Post added at 03:01 PM ---------- Previous post was at 03:00 PM ----------
use the 7.18.206.51 ruu, it's the latest one for o2
Click to expand...
Click to collapse
FAILED (remote: 02 data length is too large)

Update:
The data too large message was when I used the latest HTC fastboot Linux version.
I switched to Windows and it worked. Back at stock.
Thanks to everyone for their help, especially alray

Ok...so I'm never happy.. Anyway to unlock the bootloader again without the power button?

Perf_engineer said:
Ok...so I'm never happy.. Anyway to unlock the bootloader again without the power button?
Click to expand...
Click to collapse
sunshine

alray said:
sunshine
Click to expand...
Click to collapse
Thanks for the tip but it didn't work.
It was unable to get temporary root access.
I tried iRoot and towelroot but they also failed.
Guess I'm stuck