Database Develop

[Q] Remove Revolutionary and install original HTC 2.3.5 firmware?

Hello,
I installed revolutionary on my phone and i installed vittorus ICS ROM and i want to revert back to original HTC 2.3.5 so i downloaded the RUU.exe and that didnt work so i extracted it and renamed it PG58IMG.zip and tried to install it, i got the progress bar then nothing, then i renamed it to PG32IMG.zip and it also did the same. Then i extracted the HBOOT and Android.txt from it and named it PG32IMG.zip and then it got stuck on 'Persing' or something like that.
So heres the point:
I have a HTC Incredible S thats been unlocked with HTCDev and S is ON and i have Revolutionary installed and i have the ROM (RUU) of 2.3.5 (Optus Australia) and i have no idea how to install it (Revolutionary couldn't install it).
Please help!
Thanks, Danz207

danz207 said:
Hello,
I installed revolutionary on my phone and i installed vittorus ICS ROM and i wanot sure hont to revert back to original HTC 2.3.5 so i downloaded the RUU.exe and that didnt work so i extracted it and renamed it PG58IMG.zip and tried to install it, i got the progress bar then nothing, then i renamed it to PG32IMG.zip and it also did the same. Then i extracted the HBOOT and Android.txt from it and named it PG32IMG.zip and then it got stuck on 'Persing' or something like that.
So heres the point:
I have a HTC Incredible S thats been unlocked with HTCDev and S is ON and i have Revolutionary installed and i have the ROM (RUU) of 2.3.5 (Optus Australia) and i have no idea how to install it (Revolutionary couldn't install it).
Please help!
Thanks, Danz207
Click to expand...
Click to collapse
Not sure how you managed to get revolutionary on an s-on phone... but here's a thread that might help you http://forum.xda-developers.com/showthread.php?t=1359555
Edit: what version is your hboot?

Nonverbose said:
Not sure how you managed to get revolutionary on an s-on phone... but here's a thread that might help you http://forum.xda-developers.com/showthread.php?t=1359555
Edit: what version is your hboot?
Click to expand...
Click to collapse
I used a cmd.exe prompt whilst on Fastboot, and 2.00

Nonverbose said:
http://forum.xda-developers.com/showthread.php?t=1359555
Click to expand...
Click to collapse
That doesnt work, it needs me to get the rom.zip and name it PG32IMG.zip and then go into HBOOT and let it install but i get an error saying 'Invalid image or file'

danz207 said:
That doesnt work, it needs me to get the rom.zip and name it PG32IMG.zip and then go into HBOOT and let it install but i get an error saying 'Invalid image or file'
Click to expand...
Click to collapse
If your hboot is 2.00, then you do not have revolutionary installed. Could you post the output of "fastboot getvar all"? Minus the imei and serial number.

Nonverbose said:
If your hboot is 2.00, then you do not have revolutionary installed. Could you post the output of "fastboot getvar all"? Minus the imei and serial number.
Click to expand...
Click to collapse
I do have HBOOT 2 AND revolutionary installed, and i have no idea what you want me todo in the second part.

danz207 said:
I do have HBOOT 2 AND revolutionary installed, and i have no idea what you want me todo in the second part.
Click to expand...
Click to collapse
Put the phone in FASTBOOT USB and then in a command window on your PC tpe that command and then post the output of that command for us to look at.
If you don't understand these instructions, I suggest you read and study before going on otherwise you cold really hose up your phone.

tpbklake said:
Put the phone in FASTBOOT USB and then in a command window on your PC tpe that command and then post the output of that command for us to look at.
Click to expand...
Click to collapse
C:\Users\NAME>fastboot getvar all
'fastboot' is not recognized as an internal or external command,
operable program or batch file.
I'm guessing thats not what you were after?
I'm not on my usual computer so i'll have to do it later maybe.

danz207 said:
I do have HBOOT 2 AND revolutionary installed, and i have no idea what you want me todo in the second part.
Click to expand...
Click to collapse
I believe you have Revolutionary confused with ClockworkMod recovery after I reread your OP.
As part of the HTCDEV unlock process you installed the Android SDK to your PC. You need to open a command window and change the working directory to that directory. That is where the Fastboot.exe is located.

tpbklake said:
I believe you have Revolutionary confused with ClockworkMod recovery after I reread your OP.
Click to expand...
Click to collapse
Oops :S
I guess i do have that installed. As i said i'll have to do that tomorrow or Friday. Sorry for the confusion

danz207 said:
Oops :S
I guess i do have that installed. As i said i'll have to do that tomorrow or Friday. Sorry for the confusion
Click to expand...
Click to collapse
Also, after I reread your OP, the problem with trying to run the RUU is that you have the bootloader unlocked, that is why the RUU fails.
You need to put the phone into FASTBOOT USB mode and then enter the command:
fastboot oem lock
Then you should be able to the RUU and get back to stock.

tpbklake said:
Also, after I reread your OP, the problem with trying to run the RUU is that you have the bootloader unlocked, that is why the RUU fails.
You need to put the phone into FASTBOOT USB mode and then enter the command:
fastboot oem lock
Then you should be able to the RUU and get back to stock.
Click to expand...
Click to collapse
Ok, so if i install Android SDK on this computer and get fastboot and that other file into another folder and point cmd at it and do that, does that mean i can just run the ruu.exe and it will revert it back to HTC firmware?

danz207 said:
Ok, so if i install Android SDK on this computer and get fastboot and that other file into another folder and point cmd at it and do that, does that mean i can just run the ruu.exe and it will revert it back to HTC firmware?
Click to expand...
Click to collapse
Yes once you relock the bootloader the RUU should run to completion and you will be back to stock.

tpbklake said:
Also, after I reread your OP, the problem with trying to run the RUU is that you have the bootloader unlocked, that is why the RUU fails.
You need to put the phone into FASTBOOT USB mode and then enter the command:
fastboot oem lock
Then you should be able to the RUU and get back to stock.
Click to expand...
Click to collapse
Ok, i did that then i got:
c:\Android>fastboot oem lock
...
(bootloader) Lock successfully...
FAILED (status read failed (Too many links))
finished. total time: 0.456s
My phone now says:
*** RELOCKED ***
*** Security Warning ***
And in reply to 'Nonverbose' i typed in fastboot getvar all and got:
c:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.00.0000
(bootloader) version-baseband: 3822.10.08.28_M
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.09.980.4
(bootloader) serialno: **********
(bootloader) imei: **********
(bootloader) product: vivo
(bootloader) platform: HBOOT-7630
(bootloader) modelid: PG3213000
(bootloader) cidnum: OPTUS001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4197mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-af9874be
(bootloader) hbootpreupdate: 12
(bootloader) gencheckpt: 0
all: Done!

danz207 said:
Ok, so if i install Android SDK on this computer and get fastboot and that other file into another folder and point cmd at it and do that, does that mean i can just run the ruu.exe and it will revert it back to HTC firmware?
Click to expand...
Click to collapse
tpbklake said:
Yes once you relock the bootloader the RUU should run to completion and you will be back to stock.
Click to expand...
Click to collapse
Which RUU are you going to try and run? That is the reason why nonverbose wanted you to run the Fastboot getvar all command to make sure you are trying to run the right one.

tpbklake said:
Which RUU are you going to try and run? That is the reason why nonverbose wanted you to run the Fastboot getvar all command to make sure you are trying to run the right one.
Click to expand...
Click to collapse
I'm going to run: RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185028_signed.exe
But i can't get into my phone now. Everytime i try to turn it on it goes straight to HBOOT... Help?

danz207 said:
I'm going to run: RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185028_signed.exe
But i can't get into my phone now. Everytime i try to turn it on it goes straight to HBOOT... Help?
Click to expand...
Click to collapse
That RUU is too old to flash anyway based on your current mainver value. It will fail. You need to flash the 3.11 405.2 RUU and will probably need a goldcard to do so.
Did you make a nandroid backup from Recovery before you flashed your custom ICS ROM?

tpbklake said:
That RUU is too old to flash anyway based on your current mainver value. It will fail. You need to flash the 3.11 405.2 RUU and will probably need a goldcard to do so.
Did you make a nandroid backup from Recovery before you flashed your custom ICS ROM?
Click to expand...
Click to collapse
I made some sort of backup in Clockworkmod but i had like 30 folders on my sd card so i deleted a few and only kept a folder called 'Backup'
Which is for Astro... so uhh.. no. And i have no idea what a 'Goldcard' is, so im pretty much stuffed huh?

danz207 said:
I made some sort of backup in Clockworkmod but i had like 30 folders on my sd card so i deleted a few and only kept a folder called 'Backup'
Which is for Astro... so uhh.. no. And i have no idea what a 'Goldcard' is, so im pretty much stuffed huh?
Click to expand...
Click to collapse
You'll need to unlock the bootloader again and then install ClockworkMod and then flash a custom ROM to get going again.

tpbklake said:
You'll need to unlock the bootloader again and then install ClockworkMod and then flash a custom ROM to get going again.
Click to expand...
Click to collapse
I already have a rom on there now, can i just flash the boot.img to get it working?
Also after i do this is there anyway to get HTC firmware back on?

Unable to unlock relocked hboot

I re-locked my phone with a custom recovery and attempted to unlock again and goes through successful though the unlock screen does not show up.(Probably because I have no OS installed?)
Code:
fastboot flash unlocktoken unlock_code.bin
target reported max download size of 1526722560 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check [COLOR="DeepSkyBlue"]successfully[/COLOR]
OKAY [ 0.003s]
finished. total time: 0.144s
My current information is:
*** Tampered ***
*** RELOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Code:
version: 0.5
version-bootloader: 1.54.0000
version-baseband: 4T.21.3218.21
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno: XXXXXXXXXXXX
imei: XXXXXXXXXXXXXX
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0712000
cidnum:[COLOR="DeepSkyBlue"]GOOGL001[/COLOR]
battery-status: good
battery-voltage: 4288mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: RUU
commitno-bootloader: dirty-5d4c562c
hbootpreupdate: 11
gencheckpt: 0
Ive tried the method below with a few RUU's though I keep getting the error "FAILED (remote: 12 signature verify fail)" Their must some RUU that I can flash that correlates to my above information?
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip <path to zip>
Code:
C:\Users\chanik\Desktop\adt-bundle-windows-x86_64-20130917\sdk\platform-tools>fa
stboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (388870 KB)...
OKAY [ 15.220s]
writing 'zip'...
(bootloader) signature checking...
[COLOR="Red"]FAILED (remote: 12 signature verify fail)[/COLOR]
finished. total time: 53.263s
If someone could confirm I have fully bricked my device that be great so i can move on with my life

I foundout that i dont have a mainvar... is tjis bad?

ronniereiff said:
I foundout that i dont have a mainvar... is tjis bad?
Click to expand...
Click to collapse
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk

nkk71 said:
Did you say custom recovery? Which one, I'll post instructions to unlock when I'm on my pc...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Twrp, though i am unable to use it due to being relocked..

ronniereiff said:
Twrp, though i am unable to use it due to being relocked..
Click to expand...
Click to collapse
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please

nkk71 said:
oh, just saw you're s-on, oops.
do you have the GPE bootloader or Sense bootloader? have you tried "fastboot oem unlock"
edit: also what are you trying to flash, link please
Click to expand...
Click to collapse
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread

ronniereiff said:
I have the GPE bootloader, really im trying to flash anything that will make my phone functional again.
Ive tried many zips from the htc one collection thread
Click to expand...
Click to collapse
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).

nkk71 said:
have you tried "fastboot oem unlock"?
also check this: http://forum.xda-developers.com/showthread.php?p=48195194#post48195194 (read through the thread, to make sure it applies to you).
Click to expand...
Click to collapse
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.

ronniereiff said:
Fastboot oem unlock does not work, ill try to flash an older hboot in ruu mode tomorrow though i have a feeling signiture check will fail.
Click to expand...
Click to collapse
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.

nkk71 said:
or use a same or higher version RUU, that should work; with s-on downgrade not possible, but same version or higher RUU will work.
Click to expand...
Click to collapse
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.

ronniereiff said:
When you say version im guessing you are referring to mainver, a varible that comes back empty in fastboot. Mmy phhone has no mainver and idk why.
Click to expand...
Click to collapse
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)

nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
I have successfully unlocked after flashing the 3.58.1700.5 kitkat firmware Just need to see how to get kitkat now

nkk71 said:
yeah i saw that, dont know why it keeps happening, but you can infer from hboot 1.54 that it should be a 4.2.2 based firmware.
I don't know about GPE, but for Sense it was:
hboot 1.44 -> 1.xx firmware
hboot 1.54 -> 2.xx firmware
hboot 1.55 -> 3.xx firmware
hboot 1.56 -> 4.xx firmware
you would have to check if GPE has the same progression.
PS: though radio "4T.21.3218.21" doesnt really help, cause that looks the 4.4 GPE radio.
Anyway, I would try several RUUs in sequence, always starting with the lowest one, go up one at a time, till you find one that goes through, without failing. (has to be an official signed ruu.exe or ruu.zip, since you're s-on)
Click to expand...
Click to collapse
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.

ronniereiff said:
So my current mainver is 3.06.1700.10, hboot 1.54.000, radio 4A.18.3263.15, cidnum: GOOGL001,modelid: PN0712000 with s-on
I tried installing roms on twrp recovery but everything is failing and cache unable to mount every time and i have to wipe it over and over to get it to mount. Any idea whats going on? ive tried formating everything.
Click to expand...
Click to collapse
Cache unable to mount is ok, it's because it's wiped, so don't worry about that.
To be able to flash a 4.4 ROM, you need TWRP 2.6.3.3 or above, but since you're S-On you cannot flash a GPE 4.4 ROM as they require S-Off.
Use adb sideload, adb push, or OTG cable to get a ROM to TWRP.
Hit the thanks button if i've helped

nkk71 said:
Hit the thanks button if i've helped
Click to expand...
Click to collapse
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff

ronniereiff said:
After finally getting my phone fully working with 4.4. I have came onto XDA Forms to do just that, you have helped me out a lot, thank you!
Ronnie Reiff
Click to expand...
Click to collapse
Can you post where did you get the rom you flashed?

Urgent Help needed With Flashing RUU - refer to Page 2 for details

I relocked my bootloader without flashing the stock recovery. I can't seem to unlock it because the custom unlock splash screen refuses to start up... I really need to se a RUU to restore to stock. Any suggestions much appreciated as always.

Mihir1997 said:
I relocked my bootloader without flashing the stock recovery. I can't seem to unlock it because the custom unlock splash screen refuses to start up... I really need to se a RUU to restore to stock. Any suggestions much appreciated as always.
Click to expand...
Click to collapse
start by posting a "fastboot getvar all" (excluding IMEI, and s/n) , and explain how / why you ended up in this situation (a clearer description of your situation would help too)

nkk71 said:
start by posting a "fastboot getvar all" (excluding IMEI, and s/n) , and explain how / why you ended up in this situation (a clearer description of your situation would help too)
Click to expand...
Click to collapse
OK, SO I wanted to flash RUU onto my phone. I needed back to stock because I plan to sell it (the M8 is in shipment :cyclops: )
I changed cid, mid
I locked bootloader
OOOPS forgot to restore the stock recovery, stuck with CWM,
tried to re-unlock the bootloader, but nope. The command is successful on my PC / mac (tried both) but it doesn't do anything on phone screen (the accept the unlock thingy that you get)
Tried to re-do the fastboot flash unlocktoken Unlock.bin but I get an error message that says FAILED (remote: loading custom splash failed)
No idea what to do, I think i perma bricked the hBoot/bootloader. I can boot into my CWM and custom rom fine, but IDK how to flash the RUU now since I have no stock recovery. On top of that, I don't know whether i can even flash any other (stock) rom on here because I have s-off but relocked bootloader...

Still need a fastboot getvar all, excluding imei
Sent from my HTC One using Tapatalk

nkk71 said:
Still need a fastboot getvar all, excluding imei
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Oh totally forgot that Here:
Code:
INFOversion: 0.5
INFOversion-bootloader: 1.56.0000
INFOversion-baseband: 4A.23.3263.28
INFOversion-cpld: None
INFOversion-microp: None
INFOversion-main: 4.19.401.8
INFOversion-misc: PVT SHIP S-OFF
INFOserialno:
INFOimei:
INFOmeid: 00000000000000
INFOproduct: m7_ul
INFOplatform: HBOOT-8064
INFOmodelid: PN0712000
INFOcidnum: BS_US001
INFObattery-status: good
INFObattery-voltage: 4169mV
INFOpartition-layout: Generic
INFOsecurity: off
INFObuild-mode: SHIP
INFOboot-mode: FASTBOOT
INFOcommitno-bootloader: dirty-4dab9d12
INFOhbootpreupdate: 11
INFOgencheckpt: 0
Hope that clarifies whatever I was too stupid to omit from my accounts of events...

Ah, s-off ... Easy to fix, just a bit later... Not on my pc at the moment...
Will post back...
Sent from my HTC One using Tapatalk

nkk71 said:
Ah, s-off ... Easy to fix, just a bit later... Not on my pc at the moment...
Will post back...
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Pm'ed
Thanks,

Mihir1997 said:
Pm'ed
Thanks,
Click to expand...
Click to collapse
I think to be in the same situation, I flashed a firmware stock without before go to firmware rom and now I stuck on bootloader and flashboot refuse to remote
I really need help, please pm me

Mihir1997 said:
Pm'ed
Thanks,
Click to expand...
Click to collapse
okay, back.. you online?
and just to confirm... do you have stock recovery or custom... if custom which one and version number please
let's start by unlocking bootloader

nkk71 said:
okay, back.. you online?
and just to confirm... do you have stock recovery or custom... if custom which one and version number please
let's start by unlocking bootloader
Click to expand...
Click to collapse
Hey, yeah its custom. CWM touch 6.0.4.8

Mihir1997 said:
Hey, yeah its custom. CWM touch 6.0.4.8
Click to expand...
Click to collapse
well, the time difference isn't helping, since i'm almost off for tonight, but with S-OFF, use:
http://forum.xda-developers.com/showthread.php?t=2475914
are you sure 6.0.4.8 (thought .6 was the last one).
to unlock.... basically reboot to CWM then type:
adb shell echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
adb reboot bootloader
and you should be unlocked.
the rest can wait till someone else picks it up, or till tomorrow

nkk71 said:
well, the time difference isn't helping, since i'm almost off for tonight, but with S-OFF, use:
http://forum.xda-developers.com/showthread.php?t=2475914
are you sure 6.0.4.8 (thought .6 was the last one).
to unlock.... basically reboot to CWM then type:
adb shell echo -ne "HTCU" | dd of=/dev/block/mmcblk0p3 bs=1 seek=33796
adb reboot bootloader
and you should be unlocked.
the rest can wait till someone else picks it up, or till tomorrow
Click to expand...
Click to collapse
Nope. didn't work.
I got this :
Code:
dd: /dev/block/mmcblk0p3: No such file or directory
Thanks though
EDIT: It worked now. Yay. Now I just need help with this RUU....
It is the zip-file type of RUU not the executable PC program. In either case, when I try to fastboot flash in the RUU mode (after oem rebootruu) I get this output
Code:
./fastboot flash zip /Users/chucklesthedragon/Downloads/PN07IMG_M7_UL_JB43_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.zip
sending 'zip' (1133421 KB)... OKAY
writing 'zip'... INFOrom parsing start ...
INFOrom parsing finish ...
INFOzip header checking...
INFOzip info parsing...
INFORead zipped android_info fail
ERROR: usb_read failed with status e00002e8
FAILED (status read failed (No such file or directory))

Mihir1997 said:
Nope. didn't work.
I got this :
Code:
dd: /dev/block/mmcblk0p3: No such file or directory
Thanks though
Click to expand...
Click to collapse
try following scotty's commands, open the adb shell etc...
where did you get that recovery from? are you sure it's m7_u/ul version?
sorry got to go, we can pick this up tomorrow if you don't mind.... and yes it will work! (I can even give you a [several] recovery that you can flash with a locked bootloader, but not just tonight, sorry mate)

nkk71 said:
try following scotty's commands, open the adb shell etc...
where did you get that recovery from? are you sure it's m7_u/ul version?
sorry got to go, we can pick this up tomorrow if you don't mind.... and yes it will work! (I can even give you a [several] recovery that you can flash with a locked bootloader, but not just tonight, sorry mate)
Click to expand...
Click to collapse
Nkk, thanks a ton. I got it working after followin the instruction in the link you reffered to. Now I just need to flash this RUU. I included the details in my previous post^^^
Don't worry, tomorrow is fine. As long as I get this working...
EDIT
I downloaded of the ClockwordMod/romanager website. I'm sure I gave you the right details unless they are wrong on the site...

Mihir1997 said:
OK, SO I wanted to flash RUU onto my phone. I needed back to stock because I plan to sell it (the M8 is in shipment :cyclops: )
I changed cid, mid
I locked bootloader
OOOPS forgot to restore the stock recovery, stuck with CWM,
Click to expand...
Click to collapse
Okay, so now that the phone is unlocked again, a few questions:
1- Do you need to set it back to S-On, or can you leave it S-Off
2- what were you're original MID and CID
3- do you need to just set it back to "any" kind of stock, or do you want to do the whole thing, and set it back to "out-of-the" box
4- what OS are you running

nkk71 said:
Okay, so now that the phone is unlocked again, a few questions:
1- Do you need to set it back to S-On, or can you leave it S-Off
2- what were you're original MID and CID
3- do you need to just set it back to "any" kind of stock, or do you want to do the whole thing, and set it back to "out-of-the" box
4- what OS are you running
Click to expand...
Click to collapse
I would like s on if possible since I'm selling or giving to my dad
Cid was bm___001 I don't remember the mid, but it is the bell Canada variant.
I'd like either bell Canada stock out of the box or developer edition. Basically any stock that can be used on bell Canada, or can be easily SIM unlocked.
Currently running maximushd 33.0 latest release.
Did you see the error that I get when I try to ./fastboot flash zip ruu.zip
Its in the post before the previous post.

Mihir1997 said:
I would like s on if possible since I'm selling or giving to my dad
Cid was bm___001 I don't remember the mid, but it is the bell Canada variant.
I'd like either bell Canada stock out of the box or developer edition. Basically any stock that can be used on bell Canada, or can be easily SIM unlocked.
Currently running maximushd 33.0 latest release.
Did you see the error that I get when I try to ./fastboot flash zip ruu.zip
Its in the post before the previous post.
Click to expand...
Click to collapse
Are you SIM-locked to Bell?

nkk71 said:
Are you SIM-locked to Bell?
Click to expand...
Click to collapse
Yes sir. That is fine since I only use the device on bell anyway.

Mihir1997 said:
Yes sir. That is fine since I only use the device on bell anyway.
Click to expand...
Click to collapse
Well if you're sim-locked, then (although a longer process), I would recommend you go back to 100% Bell, otherwise there's a high chance the unlock code will not work.
Take a look at my guide: http://forum.xda-developers.com/showthread.php?t=2541082
Post your "fastboot getvar all" (excluding IMEI and s/n), and mention you're on Bell, in my thread, and I'll post the links to which files you need.
Also post any questions you may have... you'll be using the CWM restore method (so post #1, #2, and #5)

[Q] I've fallen and I can't get up!

I've successfully played with custom roms for years, but I managed to completely corrupt my Sprint HTC One M7 and I'm having a hard time figuring out how to get it back to being a working phone.
It's rooted and unlocked. I think a bad download of a recovery or rom corrupted either the storage or firmware or both.
When I first rooted it, I did have some problems. However, I was able to recover and successfully ran the Revolution ROM for about a month. I wanted to try the Viper ROM and that action (not the ROM itself, of course) put the device into its current bricked state.
I can still flash different recoveries. I can install new ROMs. I've even attempted to flash stock recoveries and run a factory reset to completely reset the phone's partitions. However the phone is unusable. I even have a OTG cable to grab ROMS from a USB stick. TWRP doesn't recognize the internal storage of the phone, but it does recognize the USB stick on the OTG cable. ClockWork can see all of the storage on the phone.
I have tried relocking and running RUUs, but I think I am doing it incorrectly because my phone is still S-ON and if that is the case, you have to find the right version of RUU that is an upgrade rather than a downgrade of the phone. The RUUs always error out. Perhaps someone will be able to provide a correct link as I have screen pictures and Model ID info I can include.
Behavior: As I try to show in the pictures I've attached, I can install customer ROMS or alleged stock ROMS onto the phone. When the process completes, I am presented with the stock lock screen for the M7. When I swipe the screen I am presented with a white HTC screen that is similar to the boot screen, but note there is no other writing. This is not the boot screen. Rather, it is all you get.
If you are tethered to a PC, you can see the storage on your list of drives.
However, after about 90 seconds, the phone auto reboots, and you are in a loop.
The phone is 13 months old, so I don't think I can just relock it and walk into a Sprint store and ask for a replacement.
Moreover, I think this is fixable, I just don't know how quite yet.
Thanks for those pros out there who can help me get out of this mess of my own making.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.651.9
(bootloader) version-misc: PVT SHIP S-ON
(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: 4242mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.035s

It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904

There is no RUU for 4.06.651.9.
This guide will get you fixed up use either the 4.06.651.9 or 5.03.651.3 s-on firmware
http://forum.xda-developers.com/showthread.php?t=2503646

twisteddan said:
It's not bricked.....
Go Here and follow the instructions exactly===============>http://forum.xda-developers.com/showthread.php?t=2250904
Click to expand...
Click to collapse
That RUU won't work it's super old

BD619 said:
That RUU won't work it's super old
Click to expand...
Click to collapse
Oh ok.....Sorry about that.

twisteddan said:
Oh ok.....Sorry about that.
Click to expand...
Click to collapse
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
The question is, does such an RUU exist?
If it does not, is there a stock or custom ROM Zip that, while not packaged in an RUU, might work? Although if that were the case, the ROM's I've already tried to use might actually work.
Or, should I attempt to S-Off the phone (something I've never done before) in order to try an RUU to work?
Thanks for your initial answers. Sounds like I don't have enough to move forward quite yet.

BD619 said:
No harm no foul
Since he/she is s-on they need to run an RUU equal to or newer then their main version
Click to expand...
Click to collapse
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?

bethesdaadk said:
I googled the version number 4.06.651.9 and came up with this:
http://forum.xda-developers.com/showthread.php?t=2687690
What do you think?
Click to expand...
Click to collapse
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.

BD619 said:
This is not an RUU,it's firmware, the the guide I linked to will get you fixed up.
I'm actually surprised you were able to run ARHD for so long without issues, it's most likely the cause of the problems.
Edit: I noticed I did not include the 4.06.651.9 firmware in the rescue guide...it's now added.
Click to expand...
Click to collapse
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
I use this one http://forum.xda-developers.com/showthread.php?t=2651035

BD619 said:
I use this one http://forum.xda-developers.com/showthread.php?t=2651035
Click to expand...
Click to collapse
I've tried to parse out your directions to make sure I do this correctly. Can you please check to make sure I'm understanding you correctly?
First step is to flash the firmware:
I've downloaded 4.06.651.9 s-on firmware per your suggestion becuase that's the current version of my phone.
Then I need to rename it to just plain firmware.zip
Then on the phone:
Boot to bootloader and lock the bootloader by typing:
fastboot oem lock
in my ADB/Fastboot dos session.
Then use these commands:
Fastboot oem rebootRUU
Fastboot flash zip firmware.zip
Fastboot reboot-bootloader
which will flash the firmware.
Then: If you get this error after the second command (most likely will)
failed 90 hboot pre-update! please flush image again immediately
press the UP Arrow on your keyboard and press enter to issue the command again. Essentially, you are flashing the firmware a second time.
Then, unlock the bootloader again
fastboot flash unlocktoken Unlock_code.bin
Here's the part where I'm a little uncertain. You state:
8a. If you are using the 4.06.651.4 s-on firmware I would suggest you push this Stock Rooted Odexed Rom to your device or it may not boot.
8b. After flashing the 4.06.651.4 rom you will most likely need to flash the latest radio because the 4.06 firmware does not have a radio included find it HERE
Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Also, earlier in the guide, you state:
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Do I need to worry about that since I'm flashing the s-on firmware and not the s-off firmware?
Thanks for your help on this. If I were this careful the first time around, maybe I wouldn't have gotten to this point. Luckily, my old Evo4G is in good condition so I've put it into service while I try and fix the HTC One.

bethesdaadk said:
I have downloaded two firmwares from your guide. the 4.06.651.9 and the 5.03.651.3
The biggest problem I am currently having is downloading the TWRP recovery without an error. I'm even using download manager on one of my laptops and it sticks at 99%. This is probably how I got into trouble in the first place. I'm attempting 2.7.1.0
Is there a solid version of TWRP earlier that should try and download instead?
Click to expand...
Click to collapse
tdhite's 2.7.0.9 worked fine for me?

Since I am flashing the 4.06.651.9 s-on firmware and not the 4.06.651.4 s-on firmware, do I need to used that suggested Rom? Or can I use any other standard Rom?
Click to expand...
Click to collapse
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
If you are already on 4.06.651.4 or 4.06.651.9 you will have to flash the 3.05.651.6 s-off firmware first...reason being is the 4.06 s-off firmware does not have the latest radio included
Click to expand...
Click to collapse
This only applies to folks that are s-off.

BD619 said:
I would use this rom just to get you up and running and you can then make a backup of the stock rom.
This only applies to folks that are s-off.
Click to expand...
Click to collapse
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.

bethesdaadk said:
I will try and do this tomorrow and will let you know it goes.
Interestingly enough, I just saw someone with an HTCONE M7 tonight running Sense 6. I was floored at how different and sleek it looked. I hope that once I have a working phone again, I'll be able to get all the way to Sense 6.
But until then, I have to get this one working.
Thanks.
Click to expand...
Click to collapse
Well the 5.03.651.3 firmware and rom are sense 6

BD619 said:
Well the 5.03.651.3 firmware and rom are sense 6
Click to expand...
Click to collapse
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?

bethesdaadk said:
Ok. So I am reporting back. It's a good news / bad news kind of situation.
I relocked the device.
Flashed the 4.06.651.9_firmware
It took two times exactly as predicted and was successful.
I had a little trouble re-unlocking it again, because I needed to resubmit the device of a new unlock.bin. The process changed the token. I suppose that makes sense.
I then flashed TWRP. On a positive note, TWRP allowed me to mount selections that were previously un-mountable.
However, when I put the unit into ADB Sideload mode and then attempted to adb side load from my PC, adb still did not recognize the device. Fastboot does, but adb doesn't.
However, since I had an OTG cable, I merely used that to have TWRP install the stock ROM you suggested.
It finished. I rebooted.
And it's still un-usable. Boots with the nice Sprint screen. One difference, I get an error about htcdialer freezing. I get the stock lock screen. I unlock to a white HTC screen.
The device shows up in device manager as my HTC but I don't see it as a listed drive anymore.
And the device reboots after about 2 minutes.
So, like I said, some success, but it still isn't usable.
Suggestions?
Click to expand...
Click to collapse
Did you remember to flash the radio?

BD619 said:
Did you remember to flash the radio?
Click to expand...
Click to collapse
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.

bethesdaadk said:
I did not flash the radio. I may have been confused, but I thought I didn't need to because I was S-On, not S-Off. At this point, it doesn't matter though, so I'll try it.
Do I need to go through the same steps as flashing the firmware?
Relock.
rebootRUU
Or can I just fastboot flash the radio?
Thanks.
Click to expand...
Click to collapse
Nope just flash the radio from recovery

[Q] HTC One m7 Sprint no radio or main version after ROM install.

So I feel like I've pretty much shat on my myself here so now I'm finally coming for specific help.
Brand New Sprint HTC one m7 from the store after a purple camera replacement.
I unlock the bootloader, flash recovery. Still S-ON Somewhere along the way I can't get signal after I install the new ROM ( I assume from the wipe)
Try to manually input APN after I had to install an apk because APN wasn't a choice. Doesn't save.
Try installing a different rom. Either I can get into the rom and no signal or it will install and reboot after 5 min into the OS.
Restore from twrp recovery I moved to my PC before I did anything. Still nothing. possible cycling reboot.
Now here's the tricky part. (for me anyway)
So going into fasboot and inputting "getvar all" it returns with a version-main: none and version-baseband: N/A. Now trying to RUU the situation. With the windows program it gives me an error and when I "fastboot flash zip firmware.zip" it continually fails.
it says my CID is SPCS_001
RUUs i've tried:
1.29.651.10
1.29.651.7
4.06.651.4
I'm not exactly sure which one I'm meant to be using from this point because they all fail. I've them both locked and unlocked. And yes Inputted the flash command multiple times for each file.

what software version is currently installed in the phone? Post full pnone info
you must RUU the same version to get back to stock and eturn baseband if you are s-on.
I have had same situation. I was on 5.03.651.3. And i can only flash 5.03.651.30or newer (5.05.651.2), BUT NOT OLDER.
relock bootloader, enter fastboot usb, run AruWizard and wait. it may look loke process hangs while flashing, but just wait and be quiet. it can take 10-20 minutes

nick_fc said:
what software version is currently installed in the phone? Post full pnone info
you must RUU the same version to get back to stock and eturn baseband if you are s-on.
I have had same situation. I was on 5.03.651.3. And i can only flash 5.03.651.30or newer (5.05.651.2), BUT NOT OLDER.
relock bootloader, enter fastboot usb, run AruWizard and wait. it may look loke process hangs while flashing, but just wait and be quiet. it can take 10-20 minutes
Click to expand...
Click to collapse
So here's my problem now. The newest firmware I can find 5.05.651.2 the exe file from the HTC site loads the install wizard and nothing happens or the zip file from http://forum.xda-developers.com/showthread.php?t=2795856 the ARUwizard file gives me the side by side error. for some reason even after repairing c++ redistributable it still pops up the error. flashing the firmware portion also from the above thread fails locked and unlocked.

Synesthesis said:
So here's my problem now. The newest firmware I can find 5.05.651.2 the exe file from the HTC site loads the install wizard and nothing happens or the zip file from http://forum.xda-developers.com/showthread.php?t=2795856 the ARUwizard file gives me the side by side error. for some reason even after repairing c++ redistributable it still pops up the error. flashing the firmware portion also from the above thread fails locked and unlocked.
Click to expand...
Click to collapse
nobody can help you if you will not post full detailed phone info and detailed error description

Synesthesis said:
So here's my problem now. The newest firmware I can find 5.05.651.2 the exe file from the HTC site loads the install wizard and nothing happens or the zip file from http://forum.xda-developers.com/showthread.php?t=2795856 the ARUwizard file gives me the side by side error. for some reason even after repairing c++ redistributable it still pops up the error. flashing the firmware portion also from the above thread fails locked and unlocked.
Click to expand...
Click to collapse
We still have no idea what version your phone is ... if it just come back from servicing i would guess the updated it for you
What PC are you running the RUU from (OS / age of PC) ? what is the error you get when flashing just the firmware ?

Synesthesis said:
So I feel like I've pretty much shat on my myself here so now I'm finally coming for specific help.
Brand New Sprint HTC one m7 from the store after a purple camera replacement.
I unlock the bootloader, flash recovery. Still S-ON Somewhere along the way I can't get signal after I install the new ROM ( I assume from the wipe)
Try to manually input APN after I had to install an apk because APN wasn't a choice. Doesn't save.
Try installing a different rom. Either I can get into the rom and no signal or it will install and reboot after 5 min into the OS.
Restore from twrp recovery I moved to my PC before I did anything. Still nothing. possible cycling reboot.
Now here's the tricky part. (for me anyway)
So going into fasboot and inputting "getvar all" it returns with a version-main: none and version-baseband: N/A. Now trying to RUU the situation. With the windows program it gives me an error and when I "fastboot flash zip firmware.zip" it continually fails.
it says my CID is SPCS_001
RUUs i've tried:
1.29.651.10
1.29.651.7
4.06.651.4
I'm not exactly sure which one I'm meant to be using from this point because they all fail. I've them both locked and unlocked. And yes Inputted the flash command multiple times for each file.
Click to expand...
Click to collapse
post your getvar all here, remove your imei and serial number before posting.
No one can help you until we know exactly what firmware you already have on the device? And what Operating system you have on your pc? What recovery your using? and what Rom you tried to flash?
The side by side error can be addressed by installing a different or updated version of Microsoft c++ and your version main is missing because you used a version of TWRP recovery with the misc partition bug. But that's all I can tell you based on what you've shared already.

Danny201281 said:
post your getvar all here, remove your imei and serial number before posting.
No one can help you until we know exactly what firmware you already have on the device? And what Operating system you have on your pc? What recovery your using? and what Rom you tried to flash?
The side by side error can be addressed by installing a different or updated version of Microsoft c++ and your version main is missing because you used a version of TWRP recovery with the misc partition bug. But that's all I can tell you based on what you've shared already.
Click to expand...
Click to collapse
Ok to answer all the burning questions:
On the computer front I'm using a macbook pro with windows 7 Ultimate installed under bootcamp.
The phone is brand new. If it was serviced I'm not aware of it.
Recovery I'm currently using is TWRP 2.8.1.0. I was using 2.7 because I read a feint whisper in some other rom thread that the apn issue might be resolved that way. However since I was having intermittent OS cycling on reinstall to not have a mtp function during mount was frightening.
The first rom I tried to flash was ARHD 83.1 in an attempt to possibly s-off my device with firewater. Never got passed the rom flashing.
and for the big reveal:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4181mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e1af350
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse

Synesthesis said:
Ok to answer all the burning questions:
On the computer front I'm using a macbook pro with windows 7 Ultimate installed under bootcamp.
Click to expand...
Click to collapse
meh! I've no experiance with Mac, I don't know for sure but running Windows I assume as a VM could cause problems using the ruu.
The phone is brand new. If it was serviced I'm not aware of it.
Recovery I'm currently using is TWRP 2.8.1.0. I was using 2.7 because I read a feint whisper in some other rom thread that the apn issue might be resolved that way. However since I was having intermittent OS cycling on reinstall to not have a mtp function during mount was frightening.
Click to expand...
Click to collapse
Are you sure you flashed the Sprint compatible TWRP recovery. You can download them here http://techerrata.com/browse/twrp2/m7wls
The first rom I tried to flash was ARHD 83.1 in an attempt to possibly s-off my device with firewater. Never got passed the rom flashing
Click to expand...
Click to collapse
And here is what I believe is the root of your problem (hehe pun intended ) This Rom is definitely not Sprint compatible. Flashing this Rom would have messed up your partitions. It's for International Brand HTC one.
If your sure your recovery is the Sprint version. You probably just need to Format the device. With "Format Data" in TWRP then flash Sprint compatible Rom. Or if you think you need to, flash a TWRP from the above link.
Based on the fact your on Hboot 1.57 the latest Sprint RUU should work for you. But because your s-on you will need to relock your bootloader in order to flash it. Assuming you can get round the side by side error. But I think a proper Windows pc is whats required there. :good:
The Sprint Section of the forums here http://forum.xda-developers.com/sprint-htc-one is where you'll find roms for your phone. In Android Development and Original Android Development

Danny201281 said:
meh! I've no experiance with Mac, I don't know for sure but running Windows I assume as a VM could cause problems using the ruu.
Click to expand...
Click to collapse
bootcamp is a separate install. not a virtual machine
And here is what I believe is the root of your problem (hehe pun intended ) This Rom is definitely not Sprint compatible. Flashing this Rom would have messed up your partitions. It's for International Brand HTC one.
Click to expand...
Click to collapse
Yeah I realized that later but I even tried installing the Nocturnal Lollipop rom, the badboyz sense 6 rom which was what was on my last HTC one, viper, etc. with no good.
If your sure your recovery is the Sprint version. You probably just need to Format the device. With "Format Data" in TWRP then flash Sprint compatible Rom. Or if you think you need to, flash a TWRP from the above link.
Click to expand...
Click to collapse
going to try this part now. OK reformatted. so flashing 5.03.651.3 and 5.05.651.2 firmware full and modified gives me this:
sending 'zip' (25541 KB)...
OKAY [ 1.952s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.176s
I am locked again and in rebootRUU

Synesthesis said:
bootcamp is a separate install. not a virtual machine
Yeah I realized that later but I even tried installing the Nocturnal Lollipop rom, the badboyz sense 6 rom which was what was on my last HTC one, viper, etc. with no good.
going to try this part now. OK reformatted. so flashing 5.03.651.3 and 5.05.651.2 firmware full and modified gives me this:
sending 'zip' (25541 KB)...
OKAY [ 1.952s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.176s
I am locked again and in rebootRUU
Click to expand...
Click to collapse
Just flash a Sprint Rom with TWRP. The format will have sorted your partitions out. It should except a Sprint compatible Rom now.

Danny201281 said:
Just flash a Sprint Rom with TWRP. The format will have sorted your partitions out. It should except a Sprint compatible Rom now.
Click to expand...
Click to collapse
OK so I finally got to another computer last night. (which is a hassle since I travel all the time) and ran the ARUwizard that didn't work on my computer. THANK THANK THANK YOU YOU YOU.
And we're up and running with 5.03.651.3
So Now I'm back to square one. After the RUU it did removed the tampered flag which I thought was cool. But now I want to tamper again. :laugh:
So from this point any sprint based rom should be ok right? I feel like all this wasn't as hard when I was romstalling a year ago with my original phone or with the EVO.
Also what's this about the twrp partition error? What version of the recovery should I be using? I had been using CWM on the old phone because CM11 stopped installing correctly after a certain version of TWRP.

Synesthesis said:
OK so I finally got to another computer last night. (which is a hassle since I travel all the time) and ran the ARUwizard that didn't work on my computer. THANK THANK THANK YOU YOU YOU.
And we're up and running with 5.03.651.3
So Now I'm back to square one. After the RUU it did removed the tampered flag which I thought was cool. But now I want to tamper again. [emoji23]
So from this point any sprint based rom should be ok right? I feel like all this wasn't as hard when I was romstalling a year ago with my original phone or with the EVO.
Also what's this about the twrp partition error? What version of the recovery should I be using? I had been using CWM on the old phone because CM11 stopped installing correctly after a certain version of TWRP.
Click to expand...
Click to collapse
Ok cool, nice to hear your back up
You should be fine to flash any Sprint Compatible Rom also recovery must be Sprint Compatible. The reason is that Sprint HTC one's have a different partition layout the the International variants, so anything you flash must be specifically for your Sprint phone. Basically anything you find in the Sprint forums I linked previously should be fine :good:
The TWRP problem is that some version (unfortunately I don't know exactly which Sprint version) have a bug that inadvertently wipes the OS version information from the misc partitions. This is only a cosmetic bug and shouldn't cause any problems with your device but if your a little ocd like myself you'll preffer to avoid it. It can be rectified by flashing firmware.
For the International HTC One this happens with 2.7.x.x versions of TWRP with 2.7.1.1 being the worst offender. Best advice I can give is check in the Sprint forums use the search box to search for "blank os" or "blank version main" that should turn up something or ask your fellow Sprint users in the Sprint Q&A forums, they should be able to give you more direct advice on what versions to avoid