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?

[Q] No S-OFF methods working

I am trying to S-OFF my HTC One and I am running into lots of issues. I've tried revone and moonshine but they both fail. I already got it unlocked with htcdev. Rooting and installing CWM went smoothly.
Info:
HBOOT 1.44.0000
I have Ubuntu 12.10 and adb version 1.0.31
revone -P fails with error -6. I have tried terminal emulator and adb shell.
moonshine fails with a strange error at the 10th step:
Moonshining(10)........................"Error: Don't drink and shine!"
I'm kinda stuck here...Any ideas?

My experience with revone was to keep on trying and after about 20 attempts it suddenly worked.

I literally tried "./revone -P" 50 times and it failed with error code -6 each time.

Revone will work fine with 1.44 hboot.
So try and re-try.
Maybe lock the bootloader and retry

It tooks 3 hours for me repeating revone command until it worked.
What firmware date you have on boot screen?
Mike

Hi,
You can try this method: [GUIDE] S-Off without PC.
It worked for me on two One's at the first try with no issues...

Julian90090 said:
I am trying to S-OFF my HTC One and I am running into lots of issues. I've tried revone and moonshine but they both fail. I already got it unlocked with htcdev. Rooting and installing CWM went smoothly.
Info:
HBOOT 1.44.0000
I have Ubuntu 12.10 and adb version 1.0.31
revone -P fails with error -6. I have tried terminal emulator and adb shell.
moonshine fails with a strange error at the 10th step:
Moonshining(10)........................"Error: Don't drink and shine!"
I'm kinda stuck here...Any ideas?
Click to expand...
Click to collapse
My idea, if it's possible on ubuntu, is to run parallel desktop, install Windows, download an all in one toolkit (Hasoon2000, etc.) and let the program flash it for you. Or, however you can get the toolkit to run. I did exactly this with my mac and my phone is unlocked, s-off, rooted and running perfectly. I do, however, have the developer edition, so my bootloader was already unlocked, but the rest the toolkit took care of. After all of your trying, maybe this is the way to go, so you can relax a little from it. Hope this helps.
-Mike

Guich said:
Revone will work fine with 1.44 hboot.
So try and re-try.
Maybe lock the bootloader and retry
Click to expand...
Click to collapse
Unless he has a US model with an updated hboot dated after May.

Julian90090 said:
I am trying to S-OFF my HTC One and I am running into lots of issues. I've tried revone and moonshine but they both fail. I already got it unlocked with htcdev. Rooting and installing CWM went smoothly.
Info:
HBOOT 1.44.0000
I have Ubuntu 12.10 and adb version 1.0.31
revone -P fails with error -6. I have tried terminal emulator and adb shell.
moonshine fails with a strange error at the 10th step:
Moonshining(10)........................"Error: Don't drink and shine!"
I'm kinda stuck here...Any ideas?
Click to expand...
Click to collapse
You may have the patched 1.44, in which case s-off won't work. Check the date of your hboot in bootloader, if it's the July release then it's been patched.
Sent from my HTC One using xda app-developers app

nkk71 said:
You may have the patched 1.44, in which case s-off won't work. Check the date of your hboot in bootloader, if it's the July release then it's been patched.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Correct, May 2013 HBoot 1.44 is okay but if you're on 1.44 June 2013 or later then you're out of luck.

It looks like I have the June 2013 patched HBOOT. Ugh hopefully a new exploit will be found.

Julian90090 said:
It looks like I have the June 2013 patched HBOOT. Ugh hopefully a new exploit will be found.
Click to expand...
Click to collapse
I had never heard of different versions of hboot 1.44.
However, will it let you fastboot flash an earlier dated 1.44 hboot .
I know if you're on for example 1.54 it won't let you downgrade hboot, but does it check for version number or date when determining whether to allow to flash .
May be worth a try
Sent from my HTC One using xda app-developers app

paul_59 said:
I had never heard of different versions of hboot 1.44.
However, will it let you fastboot flash an earlier dated 1.44 hboot .
I know if you're on for example 1.54 it won't let you downgrade hboot, but does it check for version number or date when determining whether to allow to flash .
May be worth a try
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Do you have a link to the older dated HBOOT? I can't seem to find one. Would you use fastboot to flash it?

Julian90090 said:
Do you have a link to the older dated HBOOT? I can't seem to find one. Would you use fastboot to flash it?
Click to expand...
Click to collapse
I don't think that will work, as it's been asked several times on the S-Off thread. It does mention somewhere that a few ATT users were able to restore an older OTA, but I can't confirm that. Most people with 1.54 or the patched 1.44 were not able to achieve s-off.
Don't have a link to the particular instructions, but it was discussed on the s-off thread somewhere: http://forum.xda-developers.com/showthread.php?t=2314582
Good luck
EDIT: here's the ATT downgrade thread http://forum.xda-developers.com/showthread.php?t=2394155

Julian90090 said:
Do you have a link to the older dated HBOOT? I can't seem to find one. Would you use fastboot to flash it?
Click to expand...
Click to collapse
I have uploaded to my dropbox
http://db.tt/gfbzlX26
hboot_1.44_Apr2013.zip
Guide flash hboot.txt
http://db.tt/rRjJ2ebS
Sent from my HTC One using xda app-developers app

Getting this error when I try to flash the older HBOOT:
Code:
[email protected]:~/Downloads$ adb reboot bootloader
[email protected]:~/Downloads$ fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) TZ_HTC_SVC_DISABLE ret = 534642044 (0x1FDDFD7C)
(bootloader) Use PSHOLD to reset device.
FAILED (status read failed (No such device))
finished. total time: 6.159s
[email protected]:~/Downloads$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.039s]
finished. total time: 0.039s
[email protected]:~/Downloads$ fastboot flash zip hboot_1.44_apr2013.zip
< waiting for device >
sending 'zip' (2048 KB)...
OKAY [ 0.432s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 0.652s

I didn't suggest using oem relock .
Could you fastboot getvar all
Then post the output here please
Sent from my HTC One using xda app-developers app

paul_59 said:
I didn't suggest using oem relock .
Could you fastboot getvar all
Then post the output here please
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I tried it without using OEM relock and it still didn't work. I had heard that you have to be locked in order to flash HBOOT.
What happened without using oem relock:
Code:
[email protected]:~$ adb reboot bootloader
[email protected]:~$ fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.040s]
finished. total time: 0.040s
[email protected]:~$ cd Downloads
[email protected]:~/Downloads$ fastboot flash zip hboot_1.44_apr2013.zip
sending 'zip' (2048 KB)...
OKAY [ 0.431s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 0.672s
Heres the output of fastboot getvar all:
Code:
[email protected]:~/Downloads$ fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.27.531.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT37RW900975
(bootloader) imei: XXXXXXXXXXXXXXX // i don't want to share my IMEI
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4173mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Value too large for defined data type))
finished. total time: 5.039s
Hopefully this helps....

Julian90090 said:
I tried it without using OEM relock and it still didn't work. I had heard that you have to be locked in order to flash HBOOT.
Click to expand...
Click to collapse
You only need to relock to run a RUU when s-on. Has nothing to do with what you're trying to do here.

iElvis said:
You only need to relock to run a RUU when s-on. Has nothing to do with what you're trying to do here.
Click to expand...
Click to collapse
I am S-ON trying to get S-OFF. I heard in order to flash an RUU Zip I had to have a locked bootloader.
I had originally tried flashing the zip with an unlocked bootloader, then I proceeded to try it work a locked bootloader because it didn't work.

[Q] HTC One relocked after firmware updated now soft-bricked and unable to unlock!

Help!
I recently installed the 4.06.1540.3.zip firmware onto my HTC One in preparation to install Android Revolution HD 41. After installing the firmware, I have been unable to unlock the relocked bootloader. I am able to send commands via fastboot and can successfully send the unlock code but nothing shows up on the phone. I currently have no working OS on the phone and only have stock recovery, it seems, and obviously can't send over a custom recovery until I'm unlocked which I can't do =(.
Please help, I have no phone!

Why did you lock it?
Sent from my HTC One using Tapatalk

xcrazydx said:
Why did you lock it?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Mike's directions for updating firmware required a re lock.
How to flash?
(bootloader needs to be relocked)
Re-lock your bootloader (this will most probably wipe content of your device)
Copy downloaded .zip to fastboot.exe location (e.g. c:/SDK/platform-tools/fastboot.exe)
Re-name .zip file to firmware.zip
Open command prompt
Boot your device in fastboot mode (vol down + power ===> fastboot)
Connect device to the PC
In command prompt cd to fastboot.exe location
Make sure you have correct modeid and cidnum (type: fastboot getvar all)
Type: fastboot oem lock (if your device is not relocked yet)
Type: fastboot oem rebootRUU and wait for device to reboot
Type: fastboot flash zip firmware.zip and wait for process to complete
Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
Type: fastboot flash zip firmware.zip and wait for process to complete
Type: fastboot reboot
Unlock your bootloader and flash custom recovery if you are going to use custom ROM.
Click to expand...
Click to collapse

Whaines said:
Mike's directions for updating firmware required a re lock.
Click to expand...
Click to collapse
If u r s_off ..u dont need to relock bootloader mike clearly stated tht in his post read properly before u even proceed
Sent from my HTC One using xda app-developers app

vaibhav satam said:
If u r s_off ..u dont need to relock bootloader mike clearly stated tht in his post read properly before u even proceed
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
Yup. I am and was s-on and followed directions. So why can't I unlock again?

Whaines said:
Yup. I am and was s-on and followed directions. So why can't I unlock again?
Click to expand...
Click to collapse
Unlock boot loader using HTC Dev instructions again?
Sent from my HTC One using xda app-developers app

you will need a new unlock bin file from HTC

Jcc1dls said:
you will need a new unlock bin file from HTC
Click to expand...
Click to collapse
Yes, and I've received one (and then kept trying and got about 30 more). I can flash it just fine but the screen on my phone never pops up to accept the unlock. This is my issue. There is no error message on the flash. It just doesn't show up and I can't accept the unlock.

Whaines said:
Yes, and I've received one (and then kept trying and got about 30 more). I can flash it just fine but the screen on my phone never pops up to accept the unlock. This is my issue. There is no error message on the flash. It just doesn't show up and I can't accept the unlock.
Click to expand...
Click to collapse
S-On, right? :crying:
1- was that a signed firmware package
2- did the update go all the way (ie you flashed it twice in a row, first one came back with "flush again immediately" and you did)
3- you confirmed everything was updated by checking your "fastboot getvar all"
4- bootloader also shows the correct firmware
if yes to above, try a factory reset in bootloader and/or stock recovery, then try a new unlock token, and hope it works.

nkk71 said:
S-On, right? :crying:
1- was that a signed firmware package
2- did the update go all the way (ie you flashed it twice in a row, first one came back with "flush again immediately" and you did)
3- you confirmed everything was updated by checking your "fastboot getvar all"
4- bootloader also shows the correct firmware
if yes to above, try a factory reset in bootloader and/or stock recovery, then try a new unlock token, and hope it works.
Click to expand...
Click to collapse
Yes, S-ON since getting S-OFF on hboot 1.5 is a pain.
I'm almost certain it was a signed firmware otherwise it wouldn't have even be able to have been flashed.
The firmware update was successful, after flashing twice. I can successfully flash that firmware and ..1540.2
Getvar shows the new firmware, as does the bootloader.
Here's the getvar:
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.06.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***
(bootloader) imei: ***
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4283mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
I just don't understand why I can't get the popup on my phone. That's what I get for trying to do it the right way, I guess =(.
I'd like to at least get stock back on the phone so I can have a working phone but I can't find an RUU that will work, my firmware is too new for any that I've found. =(

Should have done s-off. No point in modding without it.
Sent from my HTC One using Tapatalk

No unlock acknowledgment
I had the same issue with my first HTC One, it was a tmobile version. I ended up having to RUU whick alligned the firmware, hboot, rom, and recovery to the same versions. Boot and go through the setup. shut down. reboot. shutdown. boot into fastboot. create a new user with HTC, submit your token. Reboot your PC. Send the bin file to the device. unlock. powerdown. flash recovery. powerdown. enter recovery. powerdown and accept the install of SU. boot into the stock ROM. powerdown. You should be set to go.

Jcc1dls said:
I had the same issue with my first HTC One, it was a tmobile version. I ended up having to RUU whick alligned the firmware, hboot, rom, and recovery to the same versions. Boot and go through the setup. shut down. reboot. shutdown. boot into fastboot. create a new user with HTC, submit your token. Reboot your PC. Send the bin file to the device. unlock. powerdown. flash recovery. powerdown. enter recovery. powerdown and accept the install of SU. boot into the stock ROM. powerdown. You should be set to go.
Click to expand...
Click to collapse
I can't find an RUU for 4.06.1540.X though. =( I believe that will fix my problem but the solution is not out there.
xcrazydx said:
Should have done s-off. No point in modding without it.
Click to expand...
Click to collapse
At the time I modded there was no solution for S-OFF for 1.5+.

As for now, the only thing I seem to be able to successfully flash via RUU are the two 4.06 firmwares from @mike1986. Unfortunately, it's just firmware and not a full RUU so I can't boot into anything but the bootloader. Any hints on where I can find a stock rom that it will let me install via fastboot since I don't have a custom recovery?

Run a ruu exe
Sent from my HTC One using Tapatalk

xcrazydx said:
Run a ruu exe
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (1103159 KB)...
OKAY [ 36.684s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 148.740s
=/ Can't seem to find one that passes the signature verification.

Whaines said:
Code:
target reported max download size of 1514139648 bytes
sending 'zip' (1103159 KB)...
OKAY [ 36.684s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 148.740s
=/ Can't seem to find one that passes the signature verification.
Click to expand...
Click to collapse
Your CID is still CWS__001.
Get the AT&T RUU from HTC and run it. Then start the bootloader unlock process all over.
Once you've got a working phone, then attempt to s-off using rumrunner with a live CD/USB of a Linux distribution.
Sent from my HTC One using xda app-developers app

ilal2ielli said:
Your CID is still CWS__001.
Get the AT&T RUU from HTC and run it. Then start the bootloader unlock process all over.
Once you've got a working phone, then attempt to s-off using rumrunner with a live CD/USB of a Linux distribution.
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I really appreciate all the help, but there either is no AT&T RUU that will run with the firmware on my phone (afaik you can't go backward when you're S-ON), or it's not where I'm able to find it on the internet. I've looked here and htc1guru.com.

Whaines said:
I really appreciate all the help, but there either is no AT&T RUU that will run with the firmware on my phone (afaik you can't go backward when you're S-ON), or it's not where I'm able to find it on the internet. I've looked here and htc1guru.com.
Click to expand...
Click to collapse
That might be the case then...
I ran this RUU:
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
I used it go return to stock for a warranty exchange and had the 3.62.401.1 firmware at the time, but I was s-off.
Hopefully someone knows a way to get a ROM back on the phone so that you can get the bootloader unlocked.
Sent from my HTC One using xda app-developers app

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] Unbricking Phone- Pleading for help.

Sprint US model. was S-On (and never ever changed. still is) Phone was rooted with CWM recovery. I decided to take it back to it's out of the box condition (unroot, lock, stock FW, etc) using the same all in one tool I used so easily before.
1. I used the superuser app to remove it's root permissions and uninstall itself.
2. Using the "One M8 All In One Toolkit v.2.x" I locked the boot loader. In adb it displayed the following....
...
(bootloader) [PGFS] partition_update_pgfs: pg1fs_security
(bootloader) TZ_HTC_SVC_ENC ret = 0
(bootloader) [PGFS] partition_update_pgfs: pg2fs_sec_recovery
(bootloader) Lock successfully...
(bootloader) deinit_lcd
(bootloader) mipi display off
(bootloader) mdp_clock_off
(bootloader) turn off fd8c2308 failed 1 times. Try again...
(bootloader) disable_mmss_clk done
(bootloader) pll1_disable done
(bootloader) TZ_HTC_SVC_DISABLE ret = -1610744452 (0x9FFDFD7C)
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [CRITICAL] SPMI write command failure: cmd_id =
0, error
(bootloader) = 4
(bootloader) [INFO] Rebooting device
FAILED (status read failed (Unknown error))
finished. total time: 1.249s​
So that seemed to work fine as when in the bootloader it stated it was relocked.
3. Next I used the same program to flash the stock RUU (which I believed due to matching model and version #'s as was existing on my phone. ) However this process failed.
...
(bootloader) Start Verify: 3
OKAY [ 0.016s]
finished. total time: 0.016s​
At this point it prompted to select my file. I selected my stock firmware 2.16.651.4 (which was verified as correct version.) and selected ok. adb window then showed this.....
target reported max download size of 1826418688 bytes
sending 'zip' (39248 KB)...
OKAY [ 2.436s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 5.189s​
I then tried this same process with a newer stock firmware 3.30.651.2 and that succeeded to a certain point. It changed from the Grey HTC logo to one with a progress bar, going through a few steps but failed giving a similar permissions error. Went back it into boot loader and saw it did do a partial flash as the hboot now said 3.19 vs 2.16 as before. as not the hboot and ver. are that of the second try.
And this is where I stand stuck at this spot, and when trying a normal boot of phone it never loads ROM and just stays on the screen with the green HTC logo w/ white background. I have pondered, read every page I could find everywhere on XDA forums and after several days of trying to figure this out, I am fatigued beyond belief with this stupid phone and have all but given up. I have absolutely no answers or clues to why this is happening much less how to go about fixing it. Desperately seeking any answers from anyone who can guide me to get it back operational. For now it's become a $600 paper weight. :confused :crying:

Get rid of the toolkit and run the RUU as an exe

Unbricking Phone- Pleading for help.
BD619 said:
Get rid of the toolkit and run the RUU as an exe
Click to expand...
Click to collapse
I tried that. Both with HTC and a generic exe And they both failed. (those were stock w/ root).
Where Can I get the FULL stock no root, etc RRU.exe I found nothing but zip files. for 2.16.651.4 and 3.30.651.2

cbandchikin said:
I tried that. Both with HTC and a generic exe And they both fail.
Click to expand...
Click to collapse
Is there an error when they fail?

cbandchikin said:
I tried that. Both with HTC and a generic exe And they both failed. (those were stock w/ root).
Where Can I get the FULL stock no root, etc RRU.exe I found nothing but zip files. for 2.16.651.4 and 3.30.651.2
Click to expand...
Click to collapse
Links to the official HTC RUU's can be found in the link below, in the first post.
http://forum.xda-developers.com/showthread.php?t=2729173
These are totally stock, without root.

Yeah as s-on it will fail to install anything modified

BD619 said:
Is there an error when they fail?
Click to expand...
Click to collapse
Im Re-downloading the RUU ( from the same place as Magnum Enforcer Links to in the next post.) When I run this I will post screenshot of error.

So Based on comments so far, to get this phone back to stock and working as it did out of box, I need to ....
1. Turn S-off and change CID to Super CID
2. Flash stock RUU
3. Change CID back to original Carrier CID and change back to S-on
4. profit
If this is the case, how do I turn S-off. As "Sunshine" (the only thing I've found that does this) is an apk, and since I cant boot to ROM ..... ? If I can figure that out then I think I might be able to do the rest just fine.

You don't need SuperCID to run a RUU

Magnum_Enforcer said:
You don't need SuperCID to run a RUU
Click to expand...
Click to collapse
So I ran the RUU I redownloaded. I was taking screenshots everytime there was a change in the status, waiting for it to error like it did last time and wouldn't you know it went through the entire process without error and now the phone is bad to it's old self. This is the exact things I've been doing with no positive results. Could I have managed SOMEHOW to ended up downloading the wrong RUU? I compared and verified the successful RRU with the 1st one I tried and they are indeed the exact same version. So that wasn't it.
and yes I did this all with S-On. At no point was it ever S-Off. Bootloader showed modified. Apparently you dont need S-off to run HTC's Stock RUU. My only guess is that during this troubleshooting the bootloader was showing "Tampered" (as expected) once that changed to modified, then it was able to run successfully.

Apparently you don't need S-off to run HTC's Stock RUU
Click to expand...
Click to collapse
Our phones come S-ON so why would it need to be S-OFF to RUU.

I don't trust ruu exec , flash the firmware manually in the ruu mode, should work even if s-on as long as you are flashing the correct version(sometimes it asks you to repeat flashing and you have to do it again)
Then flash recovery in fastboot, then ur good to flash anything in the recovery.
And don't worry as long you can boot into the bootloader your phone isn't bricked (at least 90% of the time)