Database Develop

[Q] Optus Incredible S Stock Rom for Hboot 2.00

I'm look for a Optus Stock rom to download for my Incredible S Hboot 2.00, i've tried installing the RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185028_signed it comes up error 155 that the ruu one the phone is newer then the one i'm trying to install. Is there a rom after this one, as this is the only one i can fined or is there any other way to installing a stock rom.

michaels0007 said:
I'm look for a Optus Stock rom to download for my Incredible S Hboot 2.00, i've tried installing the RUU_Vivo_Gingerbread_S_Optus_AU_2.12.980.2_R_Radio_20.2803.30.085AU_3805.04.03.12_M_release_185028_signed it comes up error 155 that the ruu one the phone is newer then the one i'm trying to install. Is there a rom after this one, as this is the only one i can fined or is there any other way to installing a stock rom.
Click to expand...
Click to collapse
You could run my script or downgrade the main version manually, then rerun the ruu.
Edit: you will also have to lock the bootloader after you downgrade main version and before you run the ruu.

Nonverbose said:
You could run my script or downgrade the main version manually, then rerun the ruu.
Edit: you will also have to lock the bootloader after you downgrade main version and before you run the ruu.
Click to expand...
Click to collapse
where do I find your script or how do i downgrade the phone. I have tried a couple a different downgrader but no luck.
The phone is locked.

Nonverbose's tool is a sticky on the general page
Sent from my HTC Incredible S using xda premium

michaels0007 said:
where do I find your script or how do i downgrade the phone. I have tried a couple a different downgrader but no luck.
The phone is locked.
Click to expand...
Click to collapse
What is the reason for needing an optus rom?

FallenSuisydal said:
Nonverbose's tool is a sticky on the general page
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
Will this still work with S-on, but the phone is unlocked.

michaels0007 said:
Will this still work with S-on, but the phone is unlocked.
Click to expand...
Click to collapse
Is the phone locked or unlocked?? You do not need to unlock.

Nonverbose said:
What is the reason for needing an optus rom?
Click to expand...
Click to collapse
that was the rom that was on the phone.
Nonverbose said:
Is the phone locked or unlocked?? You do not need to unlock.
Click to expand...
Click to collapse
ok, I can relock the phone. But how do i reinstall a rom as when the phone is locked it only starts in the boot menu.

I don't know what you're asking. If my script worked and your phone is bootloader locked, just run the ruu in any mode.

Nonverbose said:
I don't know what you're asking. If my script worked and your phone is bootloader locked, just run the ruu in any mode.
Click to expand...
Click to collapse
no i can't get the script to work. when the phone is locked it only loads in the boot menu.
Is there a way to run the script in the boot menu.

michaels0007 said:
no i can't get the script to work. when the phone is locked it only loads in the boot menu.
Is there a way to run the script in the boot menu.
Click to expand...
Click to collapse
Unlock phone, boot, run script, run ruu.

Nonverbose said:
Unlock phone, boot, run script, run ruu.
Click to expand...
Click to collapse
I have unlocked the phone, run the script & tried to reinstall the ruu with no luck. the script is not working giving me lots on errors.
what else can i try.

[Q] HTC One reboot into bootloader

Hi
My HTC One keeps rebooting into the bootloader every time i turn it on, but if i say reboot, it boots up normally.
I decided to unlock my bootloader and the root the device, but i regret after unlocking the bootloader, so i decided to lock it. But now it just says "relocked" and "security warning". The reason it annoys me, is that i can't install the latest OTA update, because it just reboots into bootloader, and when i say "reboot" it boots up normally and the update is NOT installed.
What do you think i should do?
BTW, sorry if my english isn't perfect...

FML1234 said:
Hi
My HTC One keeps rebooting into the bootloader every time i turn it on, but if i say reboot, it boots up normally.
I decided to unlock my bootloader and the root the device, but i regret after unlocking the bootloader, so i decided to lock it. But now it just says "relocked" and "security warning". The reason it annoys me, is that i can't install the latest OTA update, because it just reboots into bootloader, and when i say "reboot" it boots up normally and the update is NOT installed.
What do you think i should do?
BTW, sorry if my english isn't perfect...
Click to expand...
Click to collapse
Are you still using a custom recovery? You have to flash stock recovery for OTAs.

Cant help you in detail but...
-you can change "Unlocked" to "Locked" with revone S Off
-it seems like you dont have any rom installed... you should flash a stock nandroid backup.. you can found it in the general forum.

nkk71 said:
Are you still using a custom recovery? You have to flash stock recovery for OTAs.
Click to expand...
Click to collapse
Yes, and it is S-OFF, so nothing wrong there either. Should i run an ruu? And if so should where can i find the right one? BTW, it doesn't say "security warning".

FML1234 said:
Yes, and it is S-OFF, so nothing wrong there either. Should i run an ruu? And if so should where can i find the right one? BTW, it doesn't say "security warning".
Click to expand...
Click to collapse
Well custom recovery won't let you get OTA. But your are S-Off :good: excellent.
So first thing I would do, is use revone to get rid of "TAMPERED" and change "RELOCKED" to "LOCKED".
Keep S-Off !!
And finally run your RUU, that would reflash hboot, stock recovery, stock radio, stock ROM... all back to stock, and you should receive the OTAs.
(Remember keep S-Off, cause once you receive the OTA it has an updated hboot which will not allow you to S-Off again)

kehi said:
Cant help you in detail but...
-you can change "Unlocked" to "Locked" with revone S Off
-it seems like you dont have any rom installed... you should flash a stock nandroid backup.. you can found it in the general forum.
Click to expand...
Click to collapse
It is "relocked", and i have the stock rom, the problem is that whenever i run out of juice, and boot it back up, it boots into the bootloader.

nkk71 said:
Well custom recovery won't let you get OTA. But your are S-Off :good: excellent.
So first thing I would do, is use revone to get rid of "TAMPERED" and change "RELOCKED" to "LOCKED".
Keep S-Off !!
And finally run your RUU, that would reflash hboot, stock recovery, stock radio, stock ROM... all back to stock, and you should receive the OTAs.
(Remember keep S-Off, cause once you receive the OTA it has an updated hboot which will not allow you to S-Off again)
Click to expand...
Click to collapse
But my HBOOT is 1.54 and revone doesn't support that

FML1234 said:
But my HBOOT is 1.54 and revone doesn't support that
Click to expand...
Click to collapse
Are you still S-Off? If yes, then you can downgrade your hboot to 1.44 no problem. You can either use a RUU or look if you can find an hboot image to flash using fastboot.

nkk71 said:
Are you still S-Off? If yes, then you can downgrade your hboot to 1.44 no problem. You can either use a RUU or look if you can find an hboot image to flash using fastboot.
Click to expand...
Click to collapse
No, i am not, i thought i was sorry, but thanks a lot for the help. Where can i find the right RUU? I already have one, but it is not the right one.

FML1234 said:
No, i am not, i thought i was sorry, but thanks a lot for the help. Where can i find the right RUU? I already have one, but it is not the right one.
Click to expand...
Click to collapse
There are plenty of RUUs here: http://www.androidruu.com/?developer=M7
if you can't find one for your CID, just change it to SuperCID for the duration of the process; remember you'll only need to downgrade to be able to run revone successfully, after that you can reflash whatever ROM, firmware, etc you choose.
EDIT: nevermind the above, i misread and thought you still had s-off. my bad.
EDIT 2: did you at least flash back stock recovery? if you're still on custom recovery that will cause problems.

nkk71 said:
There are plenty of RUUs here: http://www.androidruu.com/?developer=M7
if you can't find one for your CID, just change it to SuperCID for the duration of the process; remember you'll only need to downgrade to be able to run revone successfully, after that you can reflash whatever ROM, firmware, etc you choose.
EDIT: nevermind the above, i misread and thought you still had s-off. my bad.
EDIT 2: did you at least flash back stock recovery? if you're still on custom recovery that will cause problems.
Click to expand...
Click to collapse
Yes, i have stock recovery.

FML1234 said:
Yes, i have stock recovery.
Click to expand...
Click to collapse
Ok, so I misunderstood a bit.
Back to the original problem:
The reason it annoys me, is that i can't install the latest OTA update, because it just reboots into bootloader, and when i say "reboot" it boots up normally and the update is NOT installed.
Click to expand...
Click to collapse
If I understand correctly after downloading the OTA, you try to install it. The OTA will reboot into bootloader during that process. Correct?
Can't really think of a reason it's doing that, but if it is try going to "recovery" from the bootloader menu not "reboot", and see if it starts installing.

nkk71 said:
Ok, so I misunderstood a bit.
Back to the original problem:
If I understand correctly after downloading the OTA, you try to install it. The OTA will reboot into bootloader during that process. Correct?
Can't really think of a reason it's doing that, but if it is try going to "recovery" from the bootloader menu not "reboot", and see if it starts installing.
Click to expand...
Click to collapse
I'll try that and tell you if it works.

nkk71 said:
Ok, so I misunderstood a bit.
Back to the original problem:
If I understand correctly after downloading the OTA, you try to install it. The OTA will reboot into bootloader during that process. Correct?
Can't really think of a reason it's doing that, but if it is try going to "recovery" from the bootloader menu not "reboot", and see if it starts installing.
Click to expand...
Click to collapse
It didn't work Guess im gonna wait until S-OFF is available on HBOOT 1.54 and then do it.

FML1234 said:
It didn't work Guess im gonna wait until S-OFF is available on HBOOT 1.54 and then do it.
Click to expand...
Click to collapse
Sorry to hear that. Maybe you can post a video, so that we can follow your steps.
Anyway, wish you good luck
Sent from my HTC One using xda app-developers app

nkk71 said:
Sorry to hear that. Maybe you can post a video, so that we can follow your steps.
Anyway, wish you good luck
Sent from my HTC One using xda app-developers app
Click to expand...
Click to collapse
I might consider doing that. I'm pretty newish to rooting and stuff like that, but i'll try

[Q] Bricked and RUU doesn't change anything

So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2

MacSkizzle said:
So I have bricked my phone and all I want is to go back to stock. I have tried flashing OMJ's 3.04.651.2 firmware through fastboot and it completes it successfully... so it says. When I proceed to reboot, I am yet again taken to the HTC screen, the screen then goes black, after a while the screen shows an HTC one with a red triangle in it. I am desperite, please help!
Relocked
S-on
HBOOT 1.55
Radio 1.00.20.0913_3
OS 3.04.651.2
Click to expand...
Click to collapse
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app

jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Can I get s-off? All I can access is my bootloader.

jab74101 said:
You need to be s-off. Use this.
http://forum.xda-developers.com/showthread.php?t=2496687
Sent from my HTCONE using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded, extracted, and ran the correct soju but I get an error. It says to run rumrunner again and READ... I don't know what I did wrong. I did this with my phone in fastboot usb mode, is that right?

MacSkizzle said:
Can I get s-off? All I can access is my bootloader.
Click to expand...
Click to collapse
I'm pretty sure that's all you need. But I could be wrong.

TriBeard said:
I'm pretty sure that's all you need. But I could be wrong.
Click to expand...
Click to collapse
When I run the rumrunner program, I type 'Yes' twice then I get an error telling me to run rumrunner again and READ. What did I do wrong?

Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.

ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
I'll try this tonight when I get home from work, thanks for the input.

ZHoob2004 said:
Recently I was working on returning my phone back to stock and I ended up using OMJ's encrypted 1.29.651.7 (http://forum.xda-developers.com/showthread.php?t=2250904). However, in order to flash an older ruu successfully I also had to trick the phone into believing that an older version was installed. I did it using dd through adb, but I can't find the thread with the info so I'll try to find that.
ok, so here's what I did:
first, I downloaded the encrypted 1.29.651.7 ruu
then, I used this trick to change the version recorded in the phone (I think I had to be root, but I don't remember) http://forum.xda-developers.com/showthread.php?t=2390821
I substituted 1.29.651.7 for the 1.29.651.10 shown in the link
then I relocked the bootloader and flashed the ruu according to the return to stock instructions.
Hopefully this helps you work it out, I'm not sure how much this will help you but it worked for me.
Click to expand...
Click to collapse
This didn't do it either. PLEASE SOMEONE HELP ME

I don't know if you can flash OMJ's firmware if your bootloader is set to "Relocked". I could be wrong but I think what you need to do is unlock it again first and install a recovery. Then flash OMJ's stock firmware from recovery. From there you can probably do the S-OFF process and RUU back to stock.
You do need to be able to boot into your ROM for S-OFF to work, as you start the S-OFF process while the phone is booted up and running.

MacSkizzle said:
This didn't do it either. PLEASE SOMEONE HELP ME
Click to expand...
Click to collapse
Look HERE

Telus RUU HTC One M7 Error??

Good Evening:
I have a HTC One M7UL with Telus (Canada). I have been having problems with the phone charging while it's on and my last ditch effort is to go back to stock and hope something that's wrong will correct itself.
I have HBoot 1.44, S-Off, returned recovery to stock, relocked bootloader, 1.29.661.
I tried using the RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe to update and return to stock.
Everything goes fine until the RUU asks me to upgrade from 1.29 to which I select "yes" and then I get an Error (158) and it tells me to find the correct RUU.
Anybody have an idea what I'm doing wrong or if they have a different RUU that I should be using?
Any assistance that gets this working might receive a "donation"
thanks in advance.

djbeck811 said:
Good Evening:
I have a HTC One M7UL with Telus (Canada). I have been having problems with the phone charging while it's on and my last ditch effort is to go back to stock and hope something that's wrong will correct itself.
I have HBoot 1.44, S-Off, returned recovery to stock, relocked bootloader, 1.29.661.
I tried using the RUU_M7_UL_K44_SENSE55_MR_TELUS_WWE_4.19.661.8_R_Radio_4T.24.3218.09_10.26.1718.01L_release_351500_signed_2.exe to update and return to stock.
Everything goes fine until the RUU asks me to upgrade from 1.29 to which I select "yes" and then I get an Error (158) and it tells me to find the correct RUU.
Anybody have an idea what I'm doing wrong or if they have a different RUU that I should be using?
Any assistance that gets this working might receive a "donation"
thanks in advance.
Click to expand...
Click to collapse
You posted in the wrong section bud and what cid and mid are you?

liam_davenport said:
You posted in the wrong section bud and what cid and mid are you?
Click to expand...
Click to collapse
Sorry, what section should I post in..... In any case, I changed my CID to TELUS001 and my MID is PN0712000.

djbeck811 said:
Sorry, what section should I post in..... In any case, I changed my CID to TELUS001 and my MID is PN0712000.
Click to expand...
Click to collapse
Q & A and hmm you could try this? http://www.htc1guru.com/dld/guru_reset_m7_3-22-661-1-zip/

liam_davenport said:
Q & A and hmm you could try this? http://www.htc1guru.com/dld/guru_reset_m7_3-22-661-1-zip/
Click to expand...
Click to collapse
Looks promising, do I flash this from recovery, or do I do an ADB push or is there an exe in the zip I can run from the PC?

djbeck811 said:
Looks promising, do I flash this from recovery, or do I do an ADB push or is there an exe in the zip I can run from the PC?
Click to expand...
Click to collapse
install from recovery, you'll have to unlock your bootloader again though :/ and re name it to rom and just use command adb push rom.zip /sdcard

liam_davenport said:
install from recovery, you'll have to unlock your bootloader again though :/ and re name it to rom and just use command adb push rom.zip /sdcard
Click to expand...
Click to collapse
Thanks, I'll give it a shot, I'll let you know how it goes.

djbeck811 said:
Thanks, I'll give it a shot, I'll let you know how it goes.
Click to expand...
Click to collapse
No problem and ok

liam_davenport said:
No problem and ok
Click to expand...
Click to collapse
I'm calling it quits for the night, it's late here. Now I can't get the PC or the MAC to see the adb device.....arrghhhhhh lol

liam_davenport said:
No problem and ok
Click to expand...
Click to collapse
Just want to make sure, I just go into recovery, wipe and then install the file via recovery? Seems to easy. I don't have to relock bootloader or flash the stock recovery first?

[CLOSED] Limitations/risks of downgrading HBOOT?

Hi all,
I'm considering downgrading my HBOOT from 1.55 to 1.44 in order to restore the 'fastboot boot' command (a bug that HTC admit to). What concerns me is whether a particular HBOOT version is compatible only with a certain range of firmware releases and so whether I risk bricking or bootlooping from a downgrade.
Another, related question. Is it safe to use, for example, an international HBOOT (*.*.401.*, likely from PN0710000) on my Rogers phone (*.*.631.*, PN0712000)?
Anyone know whether these kinds of dependency exist, or whether HBOOT and the contents of other partitions are completely independent of one another and no crosschecking is performed? It seems to me that HBOOT 1.44 is the real sweet spot given the simplicity of revone and the ability to boot from an image that's not on the device itself.
Full disclosure: I'm running an M7_UL on Rogers (PN0712000 and CID ROGER001), S-OFF, bootloader unlocked, no root with currently stock 3.22.631.1 firmware and ROM.
Thanks folks,
Ian

dr_diem said:
Hi all,
I'm considering downgrading my HBOOT from 1.55 to 1.44 in order to restore the 'fastboot boot' command (a bug that HTC admit to).
Click to expand...
Click to collapse
fastboot boot recovery.img was intentionally removed in higher hboot, not a bug.
What concerns me is whether a particular HBOOT version is compatible only with a certain range of firmware releases and so whether I risk bricking or bootlooping from a downgrade.
Click to expand...
Click to collapse
Not 100% sure but I have downgraded to 1.44 many time and it did not caused any issue.
Another, related question. Is it safe to use, for example, an international HBOOT (*.*.401.*, likely from PN0710000) on my Rogers phone (*.*.631.*, PN0712000)?
Click to expand...
Click to collapse
I used .401 1.44 hboot on a pn071200 dev edition .1540 and it did not caused any issue.
I don't really understand why you want to flash 1.44 back when you have s-off...? downgrade to 1.44 only if and when its needed.

Many thanks for the rapid and informative response alray!
alray said:
fastboot boot recovery.img was intentionally removed in higher hboot, not a bug.
Click to expand...
Click to collapse
Really?! All the more annoying
alray said:
Not 100% sure but a downgraded to 1.44 many time and it did not cause any issue.
Click to expand...
Click to collapse
That's really promising - thanks!
alray said:
I used .401 1.44 hboot on a pn071200 dev edition .1540 and it did not caused any issue.
Click to expand...
Click to collapse
That's the mustard right there! I don't know if anyone knows the definitive answer on all this, but my gut tells me that (for GSM single-SIM handsets at least) the further down the software->firmware chain you go the more generic the code becomes. Your findings seem to support that theory.
alray said:
I don't really understand why you want to flash 1.44 back when you have s-off...? downgrade to 1.44 only if and when its needed.
Click to expand...
Click to collapse
Yeah, it's because I would like to back up my stock recovery before rooting, so I want to boot a custom recovery via fastboot and use it to take a nandroid of the stock recovery. Again I don't know if stock recoveries are tied to a particular firmware or ROM release (any idea on that one?), but I'm trying to play safe!
In general I find there aren't too many Rogers images out there (HBOOT, firmware, OTA, RUU...) which makes the rooting dance that bit more tricky for us. I tried to grab the OTA file when I recently went stock to go 1.29.631.17 -> 3.22.631.1 but of course one needs to root in order to access /temp to go get the file and I didn't want to root before I took a vanilla backup - catch 22! I don't suppose you have a 3.22.631.1 stock recovery lying around do you? It'd save me a whole load of trouble
Cheers,
Ian

dr_diem said:
Yeah, it's because I would like to back up my stock recovery before rooting
Click to expand...
Click to collapse
stock recovery can be extracted from the ota package in the firmware.zip file.
so I want to boot a custom recovery via fastboot and use it to take a nandroid of the stock recovery.
Click to expand...
Click to collapse
You can't make a nandroid backup of the recovery image but you can pull it using "dd" commands
Again I don't know if stock recoveries are tied to a particular firmware or ROM release
Click to expand...
Click to collapse
yes, use the recovery that match the version of your phone firmware/software.
I don't suppose you have a 3.22.631.1 stock recovery lying around do you? It'd save me
Click to expand...
Click to collapse
no sorry
There is a recovery collection here: http://forum.xda-developers.com/showthread.php?t=2545227
but there is no 3.22.631.1 which is an old version btw...
---------- Post added at 03:45 PM ---------- Previous post was at 03:39 PM ----------
dr_diem said:
.
Click to expand...
Click to collapse
you might want to take a look at what I have done: http://forum.xda-developers.com/showpost.php?p=54167697&postcount=1095
look under "for reference, here is how the recovery was pulled:"

alray said:
stock recovery can be extracted from the ota package in the firmware.zip file.
Click to expand...
Click to collapse
Yeah it is unfortunate that I failed to obtain that
alray said:
You can't make a nandroid backup of the recovery image but you can pull it using "dd" commands
Click to expand...
Click to collapse
Oh? Bummer In order to dd from the hboot partition I thought I'd need to be rooted though? And wouldn't I need a custom recovery in order to root? Or am I wrong and I can dd from fastboot or adb without root? If I can then this'd be an ideal solution and I wouldn't need the HBOOT downgrade after all
Huge thanks for the edit and pointer to how to dd without root!
alray said:
yes, use the recovery that match the version of your phone firmware/software.
Click to expand...
Click to collapse
Understood, thanks.
alray said:
There is a recovery collection here: http://forum.xda-developers.com/showthread.php?t=2545227
Click to expand...
Click to collapse
Yes I've combed my way through every repository I can find, but like I say ROGER_001 is a poorly-served CID I guess if I was really pushed I could go SuperCID and use the TELUS one I see there!
alray said:
but there is no 3.22.631.1 which is an old version btw...
Click to expand...
Click to collapse
Yeah the reason I'm so keen to have a complete path to downgrade to stock 4.3 is because I'm not convinced I ever want to go beyond 4.3. 4.4 makes Google Search become the shell, which is a line I'm not sure I want to cross :laugh:
Ian

dr_diem said:
Oh? Bummer In order to dd from the hboot partition I thought I'd need to be rooted though? And wouldn't I need a custom recovery in order to root? Or am I wrong and I can dd from fastboot or adb without root? If I can then this'd be an ideal solution and I wouldn't need the HBOOT downgrade after all
Click to expand...
Click to collapse
Yes you'll need either root or to downgrade hboot to 1.44, boot a custom recovery (fastboot boot), use dd from the custom recovery shell to pull the stock recovery from mmcblk0p34 partition. look in my previous (edited) post. I have posted a link explaining how to do it.

That's stormin' alray! Now I finally have a viable route forwards.
Big thanks,
Ian

dr_diem said:
That's stormin' alray! Now I finally have a viable route forwards.
Big thanks,
Ian
Click to expand...
Click to collapse
just make sure to type the dd commands correctly, it could brick your phone if you make a mistake using dd commands...

alray said:
just make sure to type the dd commands correctly, it could brick your phone if you make a mistake using dd commands...
Click to expand...
Click to collapse
Hah, yeah, touch wood I've never yet bricked any device using dd, but I'm clear how powerful/dangerous it is as commands go

Okay so I just want to finish up this thread for those who might use it as reference later.
I followed alray's excellent advice and downgraded HBOOT to 1.44 (using a 1.29.401.12 file from here) - I've been running if for a few days now and all seems fine. The phone was slower to shut down for the first few reboots - it would hang on the 'HTC logo' page for around 10 seconds or so - but now even that has gone away and it behaves fine in every way. So then, complete success running HBOOT 1.44 sourced from a 1.29.401.12 RUU on a handset running 3.22.631.1 firmware and stock ROM, that originally came with HBOOT 1.55.
FWIW I also successfully copied out the stock recovery by fastboot booting a custom recovery and using dd.
Ian

dr_diem said:
Okay so I just want to finish up this thread for those who might use it as reference later.
I followed alray's excellent advice and downgraded HBOOT to 1.44 (using a 1.29.401.12 file from here) - I've been running if for a few days now and all seems fine. The phone was slower to shut down for the first few reboots - it would hang on the 'HTC logo' page for around 10 seconds or so - but now even that has gone away and it behaves fine in every way. So then, complete success running HBOOT 1.44 sourced from a 1.29.401.12 RUU on a handset running 3.22.631.1 firmware and stock ROM, that originally came with HBOOT 1.55.
FWIW I also successfully copied out the stock recovery by fastboot booting a custom recovery and using dd.
Ian
Click to expand...
Click to collapse
glad to know it worked fine! happy flashing