Develop Bugs

[Q] S-OFF and Stock RRU

Hi,
If I run the Stock RRU for my HTC Desire will it reflash my bootloader and return to the stock HBOOT? (so S-ON returns)?
If not, how do I do this safely?
Thanks

Running an RUU will put EVERYTHING back to stock - you need to be rooted to have S-OFF

So if I run the Rru. My soff root and flash all go back to stock.
Wondering if that will put back for warranty claim
Sent from my HTC Desire using XDA App

EddyOS said:
Running an RUU will put EVERYTHING back to stock - you need to be rooted to have S-OFF
Click to expand...
Click to collapse
See my other post

Yes, it puts EVERYTHING back to stock. S-Off returns to S-Off, you become unrooted, your partition tables return to normal (I guess so since it rewrites the Hboot), EVERYTHING!!! I don't see why not for putting it in a warranty claim. To be honest I don't think they will be fussed, as long as you have the stock rom untouched.

[Q] Can I use any RUU for any DHD?

What does the RUU replace exactly?
Can I brick my phone by flashing the wrong RUU?
Why do people downgrade instead of flashing an older RUU?

The RUU replaces everything. Radio, bootloader, ROM, recovery. So you'll loose root and ENG S-OFF but you'll keep radio S-OFF.
You cant flash an older RUU if you don't have S-OFF.
And no, it doesn't matter which RUU you flash.
Sent from my Desire HD using Tapatalk

Flussen said:
The RUU replaces everything. Radio, bootloader, ROM, recovery. So you'll loose root and ENG S-OFF but you'll keep radio S-OFF.
You cant flash an older RUU if you don't have S-OFF.
And no, it doesn't matter which RUU you flash.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
is the radio S-OFF flag hidden that deep? even an RUU wont reset it!
so basically if I have radio S-OFF I can flash any RUU I like. that's cool
btw what's ENG again? and what's the different between ENG S-OFF (or ON) and radio S-OFF (or ON)?
my understanding is that if you have radio S-OFF then everything is S-OFF and you can mess with the device as bad as you like

the way i understand, you could say Eng S-OFF is a "security off" placed after bootloader and Radio S-OFF is a "security off" placed before it, so even a normal bootloader see it as a S-OFF... please, someone correct me if i'm wrong.
Radio S-OFF isn't THAT deep, it's just stay in a place not touched by flashing officlal RUU.
So when you are Radio S-OFF and flash a RUU, bootloader and everything beyond it is replaced; you keep with a Radio S-OFF (cause it stays before bootloader), but lose Eng and Root (cause it stays after bootloader).
you can't flash a older RUU without Radio S-OFF and to achieve it, you need eng s-off and for that you need root. So, if you have a 1.7xxxxxx RUU, you can't simple flash a older RUU...
i hope it could be understood, my english is not quite good when i need so much adverbs, past sentences and whatever more! =o)
Edit: you should see this thread, helps a lot in beginning: http://forum.xda-developers.com/showthread.php?t=846248

Revert to stock hboot but with broken touchscreen?

I need to get back to stock hboot for warranty, but can't find a way to flash it without using the touschscreen. All the ways I have found use terminal emulator once booted so I can't use them. Is there a way to flash it from fastboot?
Thanks,
Rory

rorydaredkign said:
I need to get back to stock hboot for warranty, but can't find a way to flash it without using the touschscreen. All the ways I have found use terminal emulator once booted so I can't use them. Is there a way to flash it from fastboot?
Thanks,
Rory
Click to expand...
Click to collapse
Doesn't flashing an RUU overwrite HBoot with stock one? I know it will leave radio S-OFF but I'm pretty sure that it overwrites HBoot, I could be completely wrong and please correct me if I am.

Doktaphex said:
Doesn't flashing an RUU overwrite HBoot with stock one? I know it will leave radio S-OFF but I'm pretty sure that it overwrites HBoot, I could be completely wrong and please correct me if I am.
Click to expand...
Click to collapse
Nope, did RUU update and stayed with eng hboot with S off

Running the 1.32.405.6 RUU will restore Ship S-ON.

Running a 1.32.405.6 RUU will revert hboot (ENG to SHIP) to stock, but it will not revert S-OFF to stock S-ON if you have Radio S-OFF.

Unrooting

Hi!
My phone broke and now I want to try to get it fixed with warranty. I'm not sure if warranty still is available if I use root so I want to unroot.
I have read that all I need to do is flash the RUU, but which one? http://forum.xda-developers.com/showthread.php?t=824357
And what will flashing it do? Will it remove CWM and everything else I was using to root? I remember that I flashed radio 2 times, had S-OFF and E-ON.
And then I will simply run System Update? Because it seems that RUU are firmwares that phones are shipped with.

yea, just flash a RUU.
Make sure you install the original RUU for the type of your DHD (i.e. WWE, Voda,T-Mobile...)
and if your phone is S-OFF, make it S-ON - S-OFF / S-ON GUIDE (guide for S-ON is at the end of the 1st post). Go into bootloader and make sure you have S-ON
--your recovery will be restored to original HTC recovery

Oh, but which RUU I need to flash? I remember I needed to do a downgrade and I think it was 1.72.405.3, not the R2, but I'm not sure.

Well, when you had your phone, was it branded?
if so, you need to find a brand-specific RUU.
If not, then WWE RUU is fine.
i would suggest the 1.32 FW (because S-ON requires temproot from Visionary+), then follow the guide to S-ON

What about radio? I have flashed the leaked gingerbread radio, wouldn't they be able to see that I have flashed a newer radio? Or the RUU flashes radio also?

RUU flashes radio too. But after flashing the RUU have a look into the bootloader, the device might still be S-Off. For S-On you need to root again and Use the easy radio tool to make S-On again. Then use the RUU again.

It still was S-OFF, but used Visionary and Easy Radio Tool to get S-ON. A brand new phone
Thanks!

Does it work the RUU to flash even if I come from an ext4 ROM (ARHD 5.1.9)?
Or do I need to format first by cwm 3.0.2.6 so that it is ext3 again?

No one any advice?

[Guide] EVO Revert to stock + S-ON after Gingerbread

This took me all day to figure out so I'm making a guide. The 2 Big problems I had were getting the S-on patch to work and the newer Hboot that came with gingerbread refusing to downgrade to an older PC36IMG.zip.
The main reason I wanted to return to stock was for a repair, last time i did everything except s-on and the guy noticed it and black listed my esn.
Make sure you are prepared before you continue! Once you flash your radio your phone wont boot into the OS.
First, you need to flash an older radio for the S-ON patch to even work. I found flashing EVO_Radio_2.15.00.07.28.zip worked best. Do this in your custom recovery
Follow djR3Z's guide to turn S-ON but do not go past step 7!
Download this file I got this off a youtube video for the incredible and replaced the files with their EVO specific counterparts
Open the zip and move flash_image and mtd0.img to your sdk/tools/ folder
boot into your custom recovery and mount /system/
open up a command prompt in your tools folder
(in windows7 hold shift and right click on /tools/ there will be an option to "open command window")
Run the commands in the commands.txt file. FYI you can paste into command prompt with right click.
adb push flash_image /data
adb push mtd0.img /data
adb shell
chmod 777 /data/flash_image
cd /data
flash_image misc mtd0.img
exit
adb reboot oem-78
Click to expand...
Click to collapse
After this you can move your stock PC36IMG.zip to the root of your SD card and reboot into your Hboot Bootloader. If everything was done correctly it should now accept PC36IMG and downgrade to stock.

Great job! Do you think there will be an easier way in the future? I don't think I would be able to do this.
Sent from my PC36100 using Tapatalk

If you run the 3.70 RUU while still s-off, will it replace the hboot with an older version? It seems like it should, but I'm confused by the 6.16 hboot.
I haven't actually ran revolutionary, so this is all theory, but I thought unrooting/s-on would work like this:
Run the RUU for 3.70. I don't have much experience with RUUs, but if they don't include radios, you would then need to reflash recovery and downgrade the radio. After reflashing etc, then flash the s-on zip. Then rerun the RUU for 3.70 to get rid of your custom recovery, or run the RUU for 4.24, since once you're s-on you can't downgrade & every RUU will be a downgrade from 6.16 hboot.
Now this may be entirely wrong, but I was just curious if it would work. I've been rooted for a while, and unrooting and s-on would be much easier for me. Even though it sounds like a pain, it still sounds more noob friendly than the version in the OP.
Either way, great job on putting this together. I know that a lot of people are curious about unrooting from revolutionary, so hopefully you've cleared some confusion.
Sent from my PC36100 using Tapatalk

Sfork said:
First, you need to flash an older radio for the S-ON patch to even work. I found flashing EVO_Radio_2.15.00.07.28.zip worked best. Do this in your custom recovery
Follow djR3Z's guide to turn S-ON but do not go past step 7!
Click to expand...
Click to collapse
I can't get this step to work, try as I have to get S-ON back, it won't go. Doesn't the Revolutionary HBOOT prevent this from working?
The unrevoked-son zip flashes fine, and says it worked, but I'm still S-OFF. What did you do to get it to work?
@plainjane
HBOOT will not update to an older version. If that were possible, the GB OTA wouldn't have had to be rooted at all, since everyone would've been able to downgrade to a rootable HBOOT version.
It's that fact that makes me wary of this method working at all. Can the steps after the "S-ON" portion be completed (which I assume finds a way to downgrade HBOOT), and then run the S-ON tool & flash the stock PC36IMG? I think that's what I'll try now, since I can't get it working in the order specified here.

Captain_Throwback said:
I can't get this step to work, try as I have to get S-ON back, it won't go. Doesn't the Revolutionary HBOOT prevent this from working?
The unrevoked-son zip flashes fine, and says it worked, but I'm still S-OFF. What did you do to get it to work?
@plainjane
HBOOT will not update to an older version. If that were possible, the GB OTA wouldn't have had to be rooted at all, since everyone would've been able to downgrade to a rootable HBOOT version.
It's that fact that makes me wary of this method working at all. Can the steps after the "S-ON" portion be completed (which I assume finds a way to downgrade HBOOT), and then run the S-ON tool & flash the stock PC36IMG? I think that's what I'll try now, since I can't get it working in the order specified here.
Click to expand...
Click to collapse
You can downgrade via RUU if you're s-off. My suggestion was to run the RUU while still s-off, because s-on won't allow you to downgrade. Or, if the RUU won't replace the bootloader, then flash an older hboot.
Then, if you're still s-off, flash the s-on tool. I don't know if this root method uses unrevoked forever or if it's just an always s-off hboot. I do know that it's a different hboot version.
If anyone has a chance to try to run the 3.70 RUU and see if it downgrades the hboot, I'd like to know. If it doesn't, but the RUU completes, then you should be able to flash recovery and then flash an older hboot - I believe 2.10 is the one that shipped with 3.70. Mine is 2.02, and I never updated to 3.70 (I believe it was 3.30 when I rooted).
Again, it's just a theory. If I get curious enough then I may unroot and update just to try revolutionary and try to unroot again, but I'd rather not get stuck with a horrendously obvious 6.16 hboot that can't be replaced/unrooted if I don't have to.
Sent from my PC36100 using Tapatalk

plainjane said:
You can downgrade via RUU if you're s-off. My suggestion was to run the RUU while still s-off, because s-on won't allow you to downgrade. Or, if the RUU won't replace the bootloader, then flash an older hboot.
Then, if you're still s-off, flash the s-on tool. I don't know if this root method uses unrevoked forever or if it's just an always s-off hboot. I do know that it's a different hboot version.
If anyone has a chance to try to run the 3.70 RUU and see if it downgrades the hboot, I'd like to know. If it doesn't, but the RUU completes, then you should be able to flash recovery and then flash an older hboot - I believe 2.10 is the one that shipped with 3.70. Mine is 2.02, and I never updated to 3.70 (I believe it was 3.30 when I rooted).
Again, it's just a theory. If I get curious enough then I may unroot and update just to try revolutionary and try to unroot again, but I'd rather not get stuck with a horrendously obvious 6.16 hboot that can't be replaced/unrooted if I don't have to.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
What I was saying is, at least with the Revolutionary HBOOT (6.16), it will not downgrade, either using the 3.70 Froyo RUU or the 4.24 GB RUU or PC36IMG.zip files flashed through Fastboot. It bypasses the Bootloader update every time.
Have you somehow gotten HBOOT to downgrade while S-OFF?

Captain_Throwback said:
What I was saying is, at least with the Revolutionary HBOOT (6.16), it will not downgrade, either using the 3.70 Froyo RUU or the 4.24 GB RUU or PC36IMG.zip files flashed through Fastboot. It bypasses the Bootloader update every time.
Have you somehow gotten HBOOT to downgrade while S-OFF?
Click to expand...
Click to collapse
Hboot 6.16 will not downgrade or flash S-ON currently.