Database Users

Perfect spl on magic vodafone

hi all
i've magic vodafone with a perfect spl, with the normal way to root not work...
can someone help me or tell us how to have root with my magic?
thanks so much

i don't know anything about the vodafone version, but my Rogers version (1.33.0010 Perfect SPL) got rooted just fine with the one click root (http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/). Download the .apk, copy onto your SD card, and open it using Astro/Linda File manager. Then in the program backup your current ROM, then flash using either the default Cyanogen Recovery ROM (already in the the text box) or with the one you want (type in the path to the other Recovery ROM).

mastakebob said:
i don't know anything about the vodafone version, but my Rogers version (1.33.0010 Perfect SPL) got rooted just fine with the one click root (http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/). Download the .apk, copy onto your SD card, and open it using Astro/Linda File manager. Then in the program backup your current ROM, then flash using either the default Cyanogen Recovery ROM (already in the the text box) or with the one you want (type in the path to the other Recovery ROM).
Click to expand...
Click to collapse
but this method is good for magic vodafone?

Don't see why it wouldn't be. They're both HTC Magic's. Either 32B or 32A. Either way, there's recovery ROMs for it. Read that RyeBrye link in my previous post, has a lot of good information.
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
I know one click root works for the 1.33.0010 SPL, which is a perfected SPL. Assume it works for other Perfect SPLs.

Go ahead with it, it works
Just remember to backup your originar recovery before flashing the new one: you will need to flash it back if you send your handset to HTC for repair.

mastakebob said:
Don't see why it wouldn't be. They're both HTC Magic's. Either 32B or 32A. Either way, there's recovery ROMs for it. Read that RyeBrye link in my previous post, has a lot of good information.
http://www.ryebrye.com/blog/2009/08/16/android-rooting-in-1-click-in-progress/
I know one click root works for the 1.33.0010 SPL, which is a perfected SPL. Assume it works for other Perfect SPLs.
Click to expand...
Click to collapse
thank's so much for your help...but this guide, its very hard to understand for me....not for language, but for what to do with htc magic.....

[REQ] Root 1.33.0007 SPL 32B $$$

So it seems that for the MT3G this SPL cannot be rooted. I was hoping to shake this up abit since no info has come up yet new for this and I know a couple of people who have this same SPL. I am willing to donate $20 to anyone who can find a way to root this. I know its not alot but its something.
Yes its on 1.6, tried various .nbh files and .zip files as listed in the forum with a gold card. Please dont flame, I just want to enjoy a rooted MT3G.

sorry, i'm not entirely familiar with this problem: what doesn't work - can you flash something like Engineering SPL1.33.2010 onto it? what happens when you try flashing a recovery via flashrec?

I started with "Hboot-1.33.0007(SAPP10000)" and now i have EngineeringSPL + Cyanogen, an other Splash than the vodafone one ... So why shouldn´t this be possible?

Follow this guide:
http://theunlockr.com/2009/10/15/how-to-root-a-donut-phone-android-1-6/
If you have Cupcake installed you can skip the first step

buggy1024 said:
I started with "Hboot-1.33.0007(SAPP10000)" and now i have EngineeringSPL + Cyanogen, an other Splash than the vodafone one ... So why shouldn´t this be possible?
Click to expand...
Click to collapse
What SPL are you currently using?

Sorry for not putting all the info before...
SAPPHIRE PVT 32B SHIP S-ON G
HBOOT-1.33.2007 (SAPP30000)
CPLD-10
RADIO-2.22.19.26I
Jul 31 2009, 15:49:25
I have tried the following methods...
sappimg.zip + goldcard
Model ID incorrect!
Update Fail!
SAPPIMG.nbh
Main Version is older!
I cannot use flashrec.apk for obvious reasons, I always get an error since I'm on 1.6. Anyone got any better suggestions?

@skhell: Reboot for you "Engineering SPL 1.33.2005"

If you are on Android 1.6 - flash sappimg.nbh with Android 1.5 first. The one you need can be found in this forum. Search for the post with this title:
"sappimg.nbh for Vodafone PVT 32B Devices"
(sorry, I am not allowed to post any links apparently )
It's a Vodafone image with spl 1.33.0007 - so it's same as yours, and it will flash with no errors - no gold card needed.
Then use one click method as decribed in theunlockr.com or elsewhere.
Then you can flash "Engineering SPL 1.33.2005"
It worked very well with my HTC Magic from Vodafone Germany
PVT-32B HBOOT-1.33.0007 (SAPP10000)
Radio - 2.22.19.26I
Good luck!

Arvycka said:
If you are on Android 1.6 - flash sappimg.nbh with Android 1.5 first. The one you need can be found in this forum. Search for the post with this title:
"sappimg.nbh for Vodafone PVT 32B Devices"
(sorry, I am not allowed to post any links apparently )
It's a Vodafone image with spl 1.33.0007 - so it's same as yours, and it will flash with no errors - no gold card needed.
Then use one click method as decribed in theunlockr.com or elsewhere.
Then you can flash "Engineering SPL 1.33.2005"
It worked very well with my HTC Magic from Vodafone Germany
PVT-32B HBOOT-1.33.0007 (SAPP10000)
Radio - 2.22.19.26I
Good luck!
Click to expand...
Click to collapse
I tried the one from this link...
http://forum.xda-developers.com/showthread.php?t=580631
And no luck, Model ID incorrect, update fail

Same Issue
I have the exact same hboot info on a replacement MT3G running factory 1.6 build DRC92.
From what I have read it is unrootable at this time. Others have said that we have to wait for a later build with a non-perfect SPL.
1.33.0007 is a perfect SPL, which normally isnt a problem, but combining that with the DRC92 build makes it troublesome.

windowsx said:
I have the exact same hboot info on a replacement MT3G running factory 1.6 build DRC92.
From what I have read it is unrootable at this time. Others have said that we have to wait for a later build with a non-perfect SPL.
1.33.0007 is a perfect SPL, which normally isnt a problem, but combining that with the DRC92 build makes it troublesome.
Click to expand...
Click to collapse
he actually wrote that he has : HBOOT-1.33.2007
isnt that an eng spl ?

xepergod said:
I tried the one from this link...
And no luck, Model ID incorrect, update fail
Click to expand...
Click to collapse
I am sorry it did not work for you. I was surprised it worked for me, despite everyone saying that there is no rooting solution for spl 1.33.0007 with DRC92. Maybe I was just lucky.

windowsx said:
1.33.0007 is a perfect SPL, which normally isnt a problem, but combining that with the DRC92 build makes it troublesome.
Click to expand...
Click to collapse
Okay, i had that at begin:
Sapphire Unknown 32B Ship S-On G
Hboot-1.33.0007(SAPP10000)
CPLD-10
Radio-2.22.19.261
Jul 31 2009, 15:49:25
Click to expand...
Click to collapse
and also Android 1.6 Stock (DRC92)
So why was it so easy for me too flash Cyanogen and more?
Downgraded with right nbh (sappimg.nbh), then installed flashrec.apk ... With that app i get a modified recovery-image installed and then i could flash rom/spl with modified recovery
Really easy

Kind of off topic, but I'm picking up a MT3G this weekend, and I didn't know there's such a thing as unrootable. Is this true? I thought they've all been figured out by now.

Supposedly there isnt such a thing as an unrootable MT3G but I sure am stuck.
I root'd my original MT3G but ended up with a replacement that I just cant get root on.
I think I am going to start a new thread. Apparently I overlooked that the thread was corrected to read 2007, not 0007.
In any case I get same errors, incorrect model id, main version older, etc.
People say they used sappimg.nbh to root the 1.33.0007 (SAPP30000) DRC92 but no one ever posts a link to the sappimg.nbh that they used. There are more than one out there, just in case people didnt notice that.
I have tried roughly 10 different .nbh's, made sure the md5 matched when applicable, tried each with and without the Goldcard, and even found the default recovery mode where I tried them again as .zip's (hold home + power until the exclamation then hit the home + power again).
I even did a hard reset and tried again. Nothing...
I do have the sdk, adb and fastboot working. Able to connect via usb, issue some commands, and list the devices. Try to push an install and get remote not allowed.
I am getting used to no-root but I dont like it. I want my old rootable phone back...

Im in the same boat as you are..
Cant seem to root my 1.33.0007/DCR92. I have tried about everything in this forum..
Hopefully something will hit soon.

can someone clarify a way to break this spl or root correctly

kaiya215 said:
can someone clarify a way to break this spl or root correctly
Click to expand...
Click to collapse
I used the instructions from the cyanogen wiki. they worked perfectly. i used the files from there as well.

Infinite76 said:
I used the instructions from the cyanogen wiki. they worked perfectly. i used the files from there as well.
Click to expand...
Click to collapse
tried no dice....

buggy1024 said:
Okay, i had that at begin:
and also Android 1.6 Stock (DRC92)
So why was it so easy for me too flash Cyanogen and more?
Downgraded with right nbh (sappimg.nbh), then installed flashrec.apk ... With that app i get a modified recovery-image installed and then i could flash rom/spl with modified recovery
Really easy
Click to expand...
Click to collapse
How about posting a link to the sappimg.nbh you used?

[NEW] [Official] [2.1] RUU - "Downgrade"

The reason is because when you updated the 2.1 RUU the HBoot was also updated and you need to first flash with an unlocked SPL for the hero.
THIS IS ONLY FOR THE HTC HERO (G2)
NOTE: Please note that flashing the wrong SPL can render your device useless.
I got the error 140: and could not find a way to downgrade until now....
Step 1: I have uploaded an unlocked SPL (hboot-1.76.2007) for the hero, which can be flashed through update.zip via recovery. The recovery can be flashed via running 'runindos.bat'. Make sure you copy the recovery files into the SDK\tools folder where adb.exe is.
Step 2: Then what you can do there is flash using the RUU you want, this will then allow you to get the 2.1 OTA update.
# MD5 checksums generated by MD5summer (http://www.md5summer.org)
# Generated 10/08/2010 19:59:11
0567f3c6260f64afaf58ae23f67891b9 *update-hero-hboot-1.76.2007-signed.zip
f8917e4173238d4f20f45b839ffb97d0 *Recovery.zip
Click to expand...
Click to collapse
- I am sitting here with a smile on my face! as I have gone from 2.73 T Mobile to 2.73 WWE to 2.1 OTA to 2.1 RUU to 2.73 to 2.1 OTA all through the above tools!
P.S I am the one who choked his hero (upgraded to 2.1) for the members to root!

You got an MD5 for the file? Just as it's an SPL, and the brick hazard is an issue

pulser_g2 said:
You got an MD5 for the file? Just as it's an SPL, and the brick hazard is an issue
Click to expand...
Click to collapse
Added to the main post.

OMG finally god bless you man after about 5 days of trying every ruu with goldcard and some other tricks even some other bootloader version i stumbled over your post and it finally worked with no errors, thank you sir now i can finally send my hero to waranty without problems .

wow, thank you, been trying to go back to RUU to sell my Hero to a phone company and been googling for over 7 hours, this is the only thing that worked, downgraded to Android 1.6 now!

I am using elelinux 6.2.0 speedmachine v5 and I am not able to apply any RUU (I always get error 140 - even with a goldcard) so this could come in quite handy.
Does it make a difference if I apply this update.zip from the recovery (RA-hero-1.6.2) that is installed on my hero?

I think there is no difference.

[REQUEST] Can anyone write a guide for Unrooting

Its only going to be a matter of time before people will need to send phones back under warranty for whatever reasons so a guide for unrooting will be needed.
Any takers?
G2 already has one, but obviously we will need different rom/hboot etc to go back to our stock.

Not just unrooting, but going completely back to stock, i.e. S-ON and stock ROM.
As you say, we should be able to base it on this - http://forum.xda-developers.com/showthread.php?t=835971
Although we have several different stock ROMs, e.g. European, Asian, Vodafone UK, etc.

this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2

gtrab said:
this is already covered in the FAQ (easy tutorial @ dev forum)
http://forum.xda-developers.com/showpost.php?p=9143411&postcount=2
Click to expand...
Click to collapse
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.

steviewevie said:
That just says to use Visionary to turn off rooting. Or did I miss something ?
As I said, I think we need to cover how to return a phone completely to stock, and I don't think it includes all that you'd really need to do, or if you didn't use Visionary in the first place, e.g. the kind of stuff in the G2 post that I linked.
Click to expand...
Click to collapse
It does say to flash an RUU to S-ON which in the past I would have said would work, but seeing how the G2 forums are not suggesting that its that simple my guess would be that its not that simple.

I had to flash the PC10img thing taken from the stock ROM to restore root and s-on. But no idea how to extract that PC10img thing, not that I have looked into it either.
That info was from one of the guides in the dev section I'm sure.
Sent from my HTC Vision using XDA App

What might work now will probably not work once an OTA update comes out for the DZ though, as per the problem on the G2 they've had which has led to quite a few semi-bricks (possibly full bricks in some cases ?).

Done some research, it would seem that flashing an RUU would work fine for those of us already rooted, if an OTA were to come out those who rooted after the OTA would have issues unless an RUU for the same OTA was released as well. (this is basically because the RUU's currently available will be older than the software the phone is on so the RUU would fail leaving you with a semi-bricked phone as described above, basically it would flash stock hboot and recovery then fail to flash the /system so you would be left with no root or recovery and no rom.
Flashing the ruu would give rise to accepting the OTA too, if you really wanted to do that, but it might block root.

you just need the RUU for your correct original phone version
OR use a gold card
eg. I have debranded mine from bell NAM 1.34.666.5 to euro generic 1.34.405.5
To go back to stock, I can:
1.- grab the bell 1.34.666.1 RUU (its slightly previous, but is the correct original version for my phone)
OR
2.- run the euro generic 1.34.405.5 with a golcard inserted

gtrab said:
you just need the RUU for your correct original phone version
Click to expand...
Click to collapse
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?

steviewevie said:
Isn't that dangerous though once we get any OTAs, and could lead to this ?
http://forum.xda-developers.com/showthread.php?t=838484
Or am I missing something ?
Click to expand...
Click to collapse
Yes thats what I was getting at in my post above, any RUU you flash needs to be of the same or newer version of what your previously flashing. You cannot GoldCard to flash an RUU to S-ON or you get left with the semi-brick where you have stock recovery and hboot, but no rom installed.
So if an OTA comes out, you can't accept it, s-off then use an older RUU to s-on again. You would have to flash an RUU of that OTA version (if one is released).
Basically its best to not accept any OTA if you can avoid it and just wait for a custom rom of the same, that way we can always use the older RUU's to s-on if we need it.

I successfully downgraded my rooted/S-OFF'd phone to an earlier ROM last night. I simply followed this method - http://forum.xda-developers.com/showthread.php?t=832503
I'm of the firm belief that this is the onyl way to do it if you are at S-OFF. If you have S-OFF, then flashing an older RUU will probably brick your phone.

Well yesterday I perm root and s-off my european Desire Z with World/Euro generic 1.34.405.5. Somehow everything went bad after flashing recovery mode, so I decided to unroot it and bring it back to original settings.
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Then entered to bootloader, and the phone recognize the archive, I simply apply it, and now I am back again to original stock.
However now I tried again and I am happily root, and S-Off following the amazing gtrab guide (http://forum.xda-developers.com/showthread.php?t=835777)

buzmay said:
I found there are 2 methods, one is to run the original ruu, and the other one was to copy the exact World/Euro generic 1.34.405.5 PC10img.zip to the root of my sd card.
Click to expand...
Click to collapse
That's the thing I keep saying though, flashing the original RUU worked for you because you weren't trying to downgrade the ROM, it was the same version that you already had on (just S-OFF etc). If you had a later version on your phone (e.g. via an OTA update) and were trying to flash to an earlier one, you would have bricked it trying the straight RUU method.

So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
By the way - that's a fake RUU

DanWilson said:
So what should be done is download and install an RUU - say 1.234.987, so you're on 1.234.987 - then root / S-OFF / custom ROM the phone. If anything goes wrong, reinstall the 1.234.987 RUU.
Click to expand...
Click to collapse
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.

steviewevie said:
During that process, if the stock HBOOT/recovery that is installed by that RUU decides that what you're trying to flash is "older" than your custom ROM, you're screwed though. That's why the "debranding" guide has extra steps in it, i.e. gold card and editing the misc partition.
Click to expand...
Click to collapse
I hate HTC.
Love the phones, love the Sense, hate the security.
Why not give us a command like the N1? WHY!?
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)

DanWilson said:
So you should backup the system partition before S-OFF and so on? Like so a dd? (Following on from previous post)
Click to expand...
Click to collapse
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).

steviewevie said:
The system partition isn't changed in S-OFF, that's the boot partition (just allows writing to the system partition).
The gold card and editing of the misc partition should work fine, as per this thread - http://forum.xda-developers.com/showthread.php?t=832503
It worked for me last night to flash to an older stock ROM (which also gave me S-ON again, removing my S-OFF).
Click to expand...
Click to collapse
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Nice

DanWilson said:
Cool. Confused. I believe you though.
But you are saying just to make a gold card, and edit the misc partition?
Click to expand...
Click to collapse
Following that guide that I linked worked for me. Yes, I turned my SD card into a gold card and edited the misc partition. Then it is fooled into thinking you're restoring a ROM of the same version that it already is running, so it lets you do it.
Actually, I do wonder whether both steps are necessary (i.e. gold card *and* editing misc), because I thought the whole point of the gold card was that it avoided those checks, so perhaps you can do one or the other ? I am only thinking out loud here, and may well be missing something, so I don't suggest trying it other than as in that guide.

[Q] Can anybody tell me which is the official rom for wildfire ?

Hello All, hope you all are ok
i bought my wildfire 3 months ago and that mean time i had so little knowledge about android and unfortunately i moved stock rom to cm7. and now i want to back in my stock rom (official)
it notice you that i have tried some rom (ruu...exe based) but i think these are not official (i am not sure)
anyway can anybody tell me which one it the official stock rom for hTC wildfire

RUU's are official.

3xeno said:
RUU's are official.
Click to expand...
Click to collapse
Thanks
ok , can you please give me the latest version RUU download link
by the way i have installed "RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed_2.exe" is this one latest RUU and official ?
if yes then where is the defaults wallpapers for android which i saw first time

AlphaRev/Revolutionary breaks some functions of official ROM's. So you have two ways to get back:
1) Sense Fix
http://forum.xda-developers.com/showthread.php?t=1156713
2) Remove AlphaRev / Revolutionary S-OFF HBoot and go back to S-ON
http://forum.xda-developers.com/showthread.php?t=1160251
Both will give you back your wallpapers, initial setup wizard, and default homescreens.

but i dont have root

Then use option 2. If you don't have root, I assume you don't wish to install custom ROms and stuff anymore. Going back to S-ON doesn't need root.

3xeno said:
Then use option 2. If you don't have root, I assume you don't wish to install custom ROms and stuff anymore. Going back to S-ON doesn't need root.
Click to expand...
Click to collapse
C:\fastboot>fastboot oem mb 9C068490 1
< waiting for device >
... FAILED (status malformed (1 bytes))

Are you sure you have specifically seletced Fastboot in the HBoot menu? It doesn't look like it.

3xeno said:
Are you sure you have specifically seletced Fastboot in the HBoot menu? It doesn't look like it.
Click to expand...
Click to collapse
ok, thanks i have now s-on
but these wallpapers and sense are not fixed yet...
and i am trying to reinstall the rom but now i am getting
Error 131 Customer ID
on ruu installation...boss please help me

Create a Goldcard and try flashing the RUU again
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
OR, if you want an app that automates most of the process listed above, use this:
http://android.modaco.com/topic/308798-pc-application-goldcardtool/

Dear 3xeno
Plz Short out my problems, currently i'm on CM7 and want to switch over to original ROM
Plz suggest me simple method to roll back on same.
should i go for "RUU version" from shipedrom.com Or Directly go for this
1) Sense Fix
http://forum.xda-developers.com/show....php?t=1156713
Or any other help will be much Appreciated.
Thanks

Sense fix is only for fixing the original ROM's wallpapers and widgets (Which don't display if you have S-OFF'ed using Revolutionary). To go back to your original ROM, you have to install the RUU, or, alternately, flash this ROM like you flashed CM7:
http://forum.xda-developers.com/showthread.php?t=877977
(If you are claiming warranty, then definitely go the RUU way)

Thanks dear for fast reply !
i'ill go for flash the Rom link provided by you.
b/w suggest me that how to save the contacts before going to Flash.

3xeno said:
Create a Goldcard and try flashing the RUU again
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
OR, if you want an app that automates most of the process listed above, use this:
http://android.modaco.com/topic/308798-pc-application-goldcardtool/
Click to expand...
Click to collapse
i have followed the steps to get goldcard and success ( how i know am i right ? )
by the way same problem in installing RUU
Error 131 Customer ID

3xeno said:
Create a Goldcard and try flashing the RUU again
http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
OR, if you want an app that automates most of the process listed above, use this:
http://android.modaco.com/topic/308798-pc-application-goldcardtool/
Click to expand...
Click to collapse
unfortunately i am success in goldcard ...now what to do ?

3xeno Man you ROCKS ...many many thanks...i am done

oh..i have another request ...
i want to back 2.1 ( i have the RUU) , last time when i wanted to back 1.6 it was successfull
but now i cant install 2.1...!
it said
Error [140]: Bootloader version error

shemulweb said:
oh..i have another request ...
i want to back 2.1 ( i have the RUU) , last time when i wanted to back 1.6 it was successfull
but now i cant install 2.1...!
it said
Error [140]: Bootloader version error
Click to expand...
Click to collapse
Now you can't. If you wanted Eclair, you should have flashed an Eclair RUU when you were on CM7. To go to 2.1, you have to go the long way, get S-OFF using Revolutionary again, and then, downgrade and get back S-ON. (Basically, the entire thing of rooting again, downgrading, and unrooting)
BUT, There is an alternate method, I am listing the post, but remember, its complex:
http://forum.xda-developers.com/showpost.php?p=13114319&postcount=29
---------- Post added at 11:25 PM ---------- Previous post was at 11:23 PM ----------
Hunk03 said:
Thanks dear for fast reply !
i'ill go for flash the Rom link provided by you.
b/w suggest me that how to save the contacts before going to Flash.
Click to expand...
Click to collapse
There are a lot of ways. If you had your contacts backed up on your Google Account, then you need not save it again. Simply re-sync your phone after installing the new ROM, and it will re-add all your contacts.
Alternately, go to Contacts, Press Menu Key, Select Import/Export, then select Export to SDCard, this will create a VCF file on your SDCard with all contacts. To restore, select Import, and select this VCF File.
Lastly, there are a ton of 3rd party apps available to do this. Just perform an Android market search for "Contact Backup".

well, now i am s-off and installed cm7 again.. successfully now what ?

Now flash the Eclair RUU (WWE 1.37.405.1) and repeat the same steps to get back S-ON. Remember to use the HBoot.nb0 file from your specific RUU.