[Q] Downgrading unlocked hboot? - Legend Q&A, Help & Troubleshooting

Hello is it possible to downgrade to hboot 0.43 or 0.93 (any under 1.0) with the unlocked bootloader from the HTC dev site?
I tried to flash the attached HBoot 0.43 file with:
Code:
fastboot flash hboot hboot_7227_0.43.0003_100430.nb0
But it says signature error. Is there a way to sign those images or does it just means that it doesnt allow downgrading? I have S-OFF (Unlocked HTC Bootloader, wich is 1.02)
The reason why I want this is if I have HBoot 0.93 or 0.43 I can flash the Alpharev bootloader. Wich is COMPLETELY unlocked so it allows me to reflash the original stock HBoot for warranty purposes.
QUBiCA
(Edit: Forgot to upload the hboot 0.43 DL link: http://dl.dropbox.com/u/33521967/hboot_7227_0.43.0003_100430.nb0)

Ability to downgrade hboot 1.02 would negate the warranty problem. Wouldn't you agree on that? So if this is possible, I don't really see a point in why would HTC need ones approval of voiding warranty after unlocking.
The only sane and logical answer to your question would therefor be NO.
Sent from my HTC Legend

Well, Vodafone Support told me that HTC will not repair the device for free with a custom ROM. I had to flash the stock Vodafone branded ROM to make it free for me. They told me HTC will blame the custom ROM then (I have Newsense RC4B). The problem was that the USB port on my device was broken. It said connected to PC when it was on the AC adapter.

BUMP, and another reason for downgrade to 0.43: Total Unlock. HTC Dev unlocked bootloader only allows writing to /system but nothing else! it even checks signatures! True unlocking = Alpharev

I don't think this will ever be possible. Alpharev would have to unlock the whole bootloader to make this possible, and they already repeatedly said this would probably never happen. The legends hboot is a glitchy mess of code. I don't see why anyone would really want a fully unlocked hboot. What are the real advantages?..

@QUBiCA: Pretend for a sec or two that you are HTC. You have bootloader that can't be downgraded. Then you release its successor which can be partially unlocked. In a process of unlocking you demand from end user to agree on warranty voiding. So why would you allow one to overwrite (downgrade) this very bootloader and regain his/her device its warranty, since after overwriting it one can never tell it was unlocked once?
If they wanted to give you a bootloader that can be downgraded, they would give you a full unlocked S-OFF one in the first place and they wouldn't be bothering you with warranty voiding, since after all downgrading would gain it back.
Sent from my HTC Legend

I have got Legend and Gratia. I have downgraded Gratia htcdev 1.03 hboot patching misc partition + relock + goldcard + Froyo RUU
(detailed in http://forum.xda-developers.com/showpost.php?p=23381950&postcount=21)
and then, I applied revolution S-OFF succesfully. However, using this method applied to Legend, it installs Eclair RUU 1.31 sucessfully, but without hboot downgrading, keeping in htcdev 1.02 hboot. Why with Gratia is possible, being a more modern phone? Is it because Froyo downgrades hboot and Eclair does not?

HBOOT 1.02 downgrade succeded!
@BlaYo, I agree in your conclusion on your retorical question.
But nevertheless i succeded in doing just that.
The short version:
make Goldcard (GoldCardTool-0.0.5, klutsh.com)
unpack hack4legend-v5 in your C:\android-sdk-windows\platform-tools
temproot (visonary+R14, MoDaCo)
ADB Shell
su
/data/local/flash_image misc /data/local/misc1-2.img
now to RUU
RUU_Legend_HTC_WWE_1.31.405.5_R_Radio_47.26.35.04_7.05.35.26L_release_126592_signed
You will still be on HBOOT 1.02
RUU_Legend_Froyo_S_HTC_WWE_3.15.405.6_Radio_47.51.35.17_7.13.35.05_release_222317_signed
Now you are on HBOOT 1.01.0000
So now there are no traces of Rooting at all. ie back to stock.

Related

[Q] Returning to S-ON

Hi,
I have rooted HTC Legend with Alpharev S-OFF.
I want to return the phone to the carrier because I have a problem with the touch screen.
I understood that S-OFF cancels the warranty, but when I return to stock ROM (RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.exe) the HBOOT remains Alpharev S-OFF.
Anyway to flash the original 0.43 HBOOT over it?
Thanks.
amoskas said:
Hi,
I have rooted HTC Legend with Alpharev S-OFF.
I want to return the phone to the carrier because I have a problem with the touch screen.
I understood that S-OFF cancels the warranty, but when I return to stock ROM (RUU_Legend_HTC_ISR_2.05.461.52_Radio_47.39.35.09_7.08.35.21_release_140015_signed.exe) the HBOOT remains Alpharev S-OFF.
Anyway to flash the original 0.43 HBOOT over it?
Thanks.
Click to expand...
Click to collapse
since you have alpharev hboot now (1.00) you can't downgrade, you can however upgrade to 1.01, just download the latest ruu and try installing that
According to the warranty, any software update I make, which is not made by the carrier, revokes the warranty, so either way - having S-OFF HBOOT 1.0 or having S-ON HBOOT 1.01 (The option you gave) - I can't repair it through the carrier..
Thanks anyway
amoskas said:
According to the warranty, any software update I make, which is not made by the carrier, revokes the warranty, so either way - having S-OFF HBOOT 1.0 or having S-ON HBOOT 1.01 (The option you gave) - I can't repair it through the carrier..
Thanks anyway
Click to expand...
Click to collapse
you can install the one i gave you so you have hboot 1.01 S-ON, and then you install the one of your carrier
should be possible
It will work, but the HBOOT will remain 1.01, and not 0.43.. So they will probably see that I did install a software on the phone.
amoskas said:
It will work, but the HBOOT will remain 1.01, and not 0.43.. So they will probably see that I did install a software on the phone.
Click to expand...
Click to collapse
Since we can't downgrade our hboot, you are stuck on S-OFF alpharev (1.00) or on
S-ON hboot 1.01
If you are going to send in your phone do it with s-on, i bet they dont even look at the hboot version, but if they do you better have s-on
Sent from my HTC Legend using XDA App

[Q] Going back S-ON

Desire has Downgrade HBOOT, so you can return to stock completely. How is possible with complete access to the system to have pure HBOOT, aka not relocked? Can be the same be done with E3D as well?
Terepin said:
Desire has Downgrade HBOOT, so you can return to stock completely. How is possible with complete access to the system to have pure HBOOT, aka not relocked? Can be the same be done with E3D as well?
Click to expand...
Click to collapse
If by "pure HBOOT, aka not relocked" you're meaning after "relocking" the bootloader having it NOT display "relocked", this is only possible using the Revolutionary method.
The official HTC unlock method does not allow this, at least on the CDMA version of the EVO 3D. On the GSM version, the limitation of the official unlock method can be bypassed, probably very similar to the Desire method by downgrading the Hboot, then using the revolutionary method.
If that isn't clear enough, or the question is different, please add more detail.
Hope that helps clarify!
Yes, I unlocked bootloader with HTC tool, then downgraded HBOOT and S-OFFed. After using both RUU and manual update, the "relock" status was back. Why?
Terepin said:
Yes, I unlocked bootloader with HTC tool, then downgraded HBOOT and S-OFFed. After using both RUU and manual update, the "relock" status was back. Why?
Click to expand...
Click to collapse
The CDMA device doesn't have this option and that is generally the crowd I hear from the most. You're the first GSM user to confirm that after downgrading and being s-off with revolutionary, once bootloader is upgraded and re-locked, it will display as "relocked".
Off the top of my head, there aren't too many divergent paths to take, but more details to your process would help.
While running Revolutionary and S-OFF, directly upgrade either via RUU or flashing an updated bootloader. At this point, does the updated bootloader show Relocked?
If not, is the internal memory still unlocked? If so, is the internal memory locked?
Depending on this outcome, we can formulate the next steps. At this point, we would want to know:
1) what is displayed on the bootloader, locked, unlocked or relocked?
2) what is the *real* status of the internal memory, write protected or write unprotected?
The question really hangs on how the latest stock bootloader determines the lock, unlocked and relocked status which it displays. This can be considered fairly low level and there is not a lot of publicly posted information or research on this specific topic.
Any feedback or testing you want to provide would be help and informative! The CDMA version of the EVO 3D can't perform these tests, only the GSM version is able to downgrade, as far as we've seen.
Hope that helps!
Version of HBOOT is irrelevant, when I replace it with ship HBOOT it says *unlocked*, yet still S-OFF. Only ENG HBOOT will remove it, but after replacing it will bring it back.
But you gave me an idea. I'm going to try to replace HBOOT, then unlock it, S-OFF again and then to re-flash stock ROM.
EDIT: I still have access to NAND memory.
Yeah, that didn't help.
I have a theory that it must be something outside HBOOT.
Odoslané z môjho HTC Evo 3D with Beats Audio X515m cez Tapatalk

[Q] Re-rooting Hboot 1.5 after flashing 2.17

I seem to have developed a habit of asking here alot (the evo 3d isnt really my phone i have a Sensation, just doing a favor)
I've re-locked the phone, installed 2.17 (from 2.08) and im wondering if there are other methods of unlocking with Hboot 1.5 S-On (says RELOCKED on recovery) other than having to do the whole HTC Unlock method again?
I wanted to try MeanROM so i pretty much re-locked, upgraded to 2.17 and now i have to reroot just for this ROM (and also got a new radio...)
If not, do i just have to follow the HTC unlock method all over again from Scratch? The process is identical even if i have relocked it?

[Q] Removal of *** RELOCKED ***?

As I had the unfortunate pleasure of receiving my phone with 1.5 already on it I had used HTC's unlock method. However now, I was able to downgrade my HBoot to 1.40 with this amazing guide by Unknownforce and was able to finally attain S-OFF.
To get back to the latest radios and everything I ran the 2.17 RUU knowing I'd keep S-OFF through it and would downgrade my HBoot afterwards. However, I noticed that I still have the mark of *** RELOCKED *** above S-OFF (I had to relock it to use the RUU to brick).
I downgraded (again) back to 1.40 HBoot but I'm curious if it's possible to hide the fact that I've unlocked in case I ever have to turn my phone back into Sprint.
I would have thought that replacing the HBoot partion with the stock 1.40 image with the emmc_recover tool would have overwritten that. I take it that means that the locked/unlocked/relocked flag is stored elsewhere?
If you did HTC unlock then sprint has your serial numbers on file that you did it so dont worry about it
Sent from my PG86100 using Tapatalk

[Q] HBOOT and Unlocking

So I recently got a hold of a rezound and it came with S-OFF and an unlocked 2.25 HBOOT. I have a couple of questions about upgrading:
1. Does keeping the HBOOT unlocked have any benefits besides extra fastboot commands (which I'll never use)?
2. How can I upgrade to the 2.27 HBOOT with my phone's current status (unlocked with S-OFF).
3. Are there any benefits to having the unlocked 2.27 HBOOT that vinylfreak released over the stock HBOOT?
Thanks in advance for the help. I've been paging through this forum and there is a lot of fragmented information floating around that's both new and old so it can be hard to make sense of it all.
polarEskimo said:
So I recently got a hold of a rezound and it came with S-OFF and an unlocked 2.25 HBOOT. I have a couple of questions about upgrading:
1. Does keeping the HBOOT unlocked have any benefits besides extra fastboot commands (which I'll never use)?
2. How can I upgrade to the 2.27 HBOOT with my phone's current status (unlocked with S-OFF).
3. Are there any benefits to having the unlocked 2.27 HBOOT that vinylfreak released over the stock HBOOT?
Thanks in advance for the help. I've been paging through this forum and there is a lot of fragmented information floating around that's both new and old so it can be hard to make sense of it all.
Click to expand...
Click to collapse
1. You can flash kernels in recovery and not HBOOT, you can also install a different splash screen logo (downside. you can brick the phone because there is zero security now. "S" in on or off means security)
2. you can update the HBOOT to 2.27 without any problems by downloading one from the develop section and it wont hurt the phone. link
3. HBOOT 2.27 was meant for the global update. if you dont plan on leaving the U.S. or use the phone for gsm then there isnt a need to update.
polarEskimo said:
So I recently got a hold of a rezound and it came with S-OFF and an unlocked 2.25 HBOOT. I have a couple of questions about upgrading:
1. Does keeping the HBOOT unlocked have any benefits besides extra fastboot commands (which I'll never use)?
2. How can I upgrade to the 2.27 HBOOT with my phone's current status (unlocked with S-OFF).
3. Are there any benefits to having the unlocked 2.27 HBOOT that vinylfreak released over the stock HBOOT?
Thanks in advance for the help. I've been paging through this forum and there is a lot of fragmented information floating around that's both new and old so it can be hard to make sense of it all.
Click to expand...
Click to collapse
I would run newest ruu with 2.27 hboot and flash a custom rom.
Damasterjj said:
I would run newest ruu with 2.27 hboot and flash a custom rom.
Click to expand...
Click to collapse
Can I run it with S-OFF and unlocked? I read somewhere that if you use an official RUU on an unlocked HBOOT that you could brick your phone. Will running the RUU re-lock the bootloader after upgrading? Thanks for the help
You can't ever brick your phone running an ruu unless its a bad ruu. To ruu though.. your phone must be relocked using fastboot. What you're thinking of is if you s-on with a modified hboot then you brick. You're good though.
1. Relock with fastboot oem lock
2. Run RUU
3. Honestly there's not much reason to unlock again
Sent from my ADR6425LVW using Tapatalk 2
polarEskimo said:
Can I run it with S-OFF and unlocked? I read somewhere that if you use an official RUU on an unlocked HBOOT that you could brick your phone. Will running the RUU re-lock the bootloader after upgrading? Thanks for the help
Click to expand...
Click to collapse
OK so unlocked and locked boot loaders mean you can use fast boot commands. If you ruu to the newest you will loose fast boot commands unless you unlock or flash an engineering hboot.
If you ever wanted to update after you have unlocked, you must relock the boot loader before updating. Ie never ruu on an unlocked hboot
Sent from my iPhone...
Don't bother updating hboot, it will net you nothing. I've been running 2.25 hboot with the new radios since the 4.03.605.2 leak. 0 issues and runs VERY well. Also unlocked on a patched/eng hboot means nothing, can run the same commands the same way with it being locked. Although a stock hboot may need to be unlocked to get access to some of those commands, of which will probably be of no use to you anyways.
@Syn
S-off shouldnt need a re-lock/unlock to update ANYTHING in hboot with a ph98img.
Snuzzo said:
Don't bother updating hboot, it will net you nothing. I've been running 2.25 hboot with the new radios since the 4.03.605.2 leak. 0 issues and runs VERY well. Also unlocked on a patched/eng hboot means nothing, can run the same commands the same way with it being locked. Although a stock hboot may need to be unlocked to get access to some of those commands, of which will probably be of no use to you anyways.
@Syn
S-off shouldnt need a re-lock/unlock to update ANYTHING in hboot with a ph98img.
Click to expand...
Click to collapse
Learned something new. Thanks.
Sent from my iPhone...

Categories

Resources