Database Info

[S-OFF] Unrevoked Forever for radio 2.15.00.11.19

STOP STOP STOP STOP STOP STOP STOP STOP STOP STOP
If you're not an expert user, stop reading now. The unrevoked
release that supports the new OTA will be coming soon.
STOP STOP STOP STOP STOP STOP STOP STOP STOP STOP
Hi folks.
I have a build of Forever for radio 2.15.00.11.19; it worked on my phone. So, for the adventurous amongst you who don't want to wait for the new unrevoked release (coming soon, I swear; we now all finally have a moment to breathe, so we're getting moving on this one), but are somehow stuck on the new radio, I have a new build for you -- get it at the usual place.
Have fun!
joshua
unrevoked

Really looking forward to this release. Have a refurb coming in this tuesday and I'm hoping I won't need to use this, but glad its here if I do.
Sent from my PC36100 using XDA App

Fantastic, thank you

Quick question Joshua, Quite a while ago I Rooted my EVO with UnRevoked 3.21 and have S-Off and all is well. Back at that time should I have also flashed UnRevoked Forever, or does 3.21 also cover that?
Thanks.

thekenster said:
Quick question Joshua, Quite a while ago I Rooted my EVO with UnRevoked 3.21 and have S-Off and all is well. Back at that time should I have also flashed UnRevoked Forever, or does 3.21 also cover that?
Thanks.
Click to expand...
Click to collapse
Same question here, I only ran 3.21 and it put me in S-OFF. I've even flashed a couple of RUU's in the past and re-rooted, and the phone never went back to S-ON.

I had eng hboot with soff, but applied the new soff successfully to the radio after updating to the 2.15.00.11.19 radio.

This works flawlessly
Just wanted to let everyone know how I achieved full root with the newest OTA.
1) download newest S-OFF Patch that works with new radio while still rooted on older SW version. Install S-OFF.zip through recovery.
2) Use 3.29 ruu to restore phone back to stock, s-off will still be on. Download OTA update directly to phone after you finish initial setup.
3) Install downloaded OTA immediately. Let it do its thing. Once you reboot, place clockwork recovery (Amon-RA probably works too but I haven't tried it yet) on the root of your sdcard and make sure it is named pc36img.zip.
4) power off phone, hold volume down and power... phone will turn on and ask if you want to apply update , press volume up for yes.
5) you now have root and nand unlock with all the newest radio versions and a custom recovery to flash zips as you wish. I installed a stock de-odexed version of the newest OTA already as I wait for devs to release custom ROMS based on 3.70...
Have fun!!
Everything I used was downloaded right from here.
http://unrevoked.com/rootwiki/doku.php/public/forever
THIS WAS DONE ON AN 003 HARDWARE PHONE. I CAN NOT GUARANTEE THIS WILL WORK ON 004!!!

Thanks. The Unrevoked site now shows support for 11.19.
Infinite loop duration: user-defined (good)
Brinell hardness: 35-45 (good)
Viscosity: SAE 20 or equivalent (good)
Votages: Plates=+350VDC (good)
------------Filament=+12VDC (good)
------------Grid=-2.4VDC (good)
Operating environment: Yes (good)
Microcode verified CFC-free (good)
LOL

thekenster said:
Quick question Joshua, Quite a while ago I Rooted my EVO with UnRevoked 3.21 and have S-Off and all is well. Back at that time should I have also flashed UnRevoked Forever, or does 3.21 also cover that?
Thanks.
Click to expand...
Click to collapse
If the phone says S-OFF, and it DOESN'T say "ENG" at the top, then you don't need to run Forever; you're already S-OFF. (It was included in all unrevoked releases since, I think, 3.2.)

Josh I have original eng boot with s-off and I flashed unrevoked forever just in case I decided to upgrade the hboot later . My hboot still shows eng s-off and flash said it was successful. Should I see still see eng in my hboot?
joshua_ said:
If the phone says S-OFF, and it DOESN'T say "ENG" at the top, then you don't need to run Forever; you're already S-OFF. (It was included in all unrevoked releases since, I think, 3.2.)
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

starkillers said:
Josh I have original eng boot with s-off and I flashed unrevoked forever just in case I decided to upgrade the hboot later . My hboot still shows eng s-off and flash said it was successful. Should I see still see eng in my hboot?
Click to expand...
Click to collapse
If you flashed Forever, it will still say ENG; there isn't an easy way to tell if it's a hard-S-OFF or soft-S-OFF if you have the ENG loader. But yes, if you flashed Forever, you are now hard-S-OFF, and it's OK if it still says ENG -- you just have to remember that you did flash Forever!

Cool, yeah it put a log on my SD card that said successful. Figured I would forever flash as some people lost s-off updating hboot.
joshua_ said:
If you flashed Forever, it will still say ENG; there isn't an easy way to tell if it's a hard-S-OFF or soft-S-OFF if you have the ENG loader. But yes, if you flashed Forever, you are now hard-S-OFF, and it's OK if it still says ENG -- you just have to remember that you did flash Forever!
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App

Will this help downgrade HBoot for those that had Unrevoked Forever and upgraded HBoot to 2.10? or is the Hboot still locked!?

m3Jorge said:
Will this help downgrade HBoot for those that had Unrevoked Forever and upgraded HBoot to 2.10? or is the Hboot still locked!?
Click to expand...
Click to collapse
Follow my instructions on page 1 and you will be just fine!!

ok, i got s-off but can boot into recovery. i use pc36img, just cant get into recovery.

phat_red said:
ok, i got s-off but can boot into recovery. i use pc36img, just cant get into recovery.
Click to expand...
Click to collapse
Okay, so u lashed zip and got s-off... Place pc36img.zip onto root of sdcard and then powered off the phone... The you hold down power and volume down button at same time... Hboot should pop up and search for pc36img.zip automatically... It should find it and then ask if you want to proceed to update... Then you press volume up key and it will update.... Boot phone regularly, attach to computer.... Remove pc36img.zip from root of sd card... Shut phone down.... Hold down power and volume down at same time. Hboot will pop up again and look for pc36img.zip / since u removed it it will find nothing press volume down until recovery... when recovery is highlighted press power button.. you will be in recovery.... Just make sure you get the pc36img.zip file from unrevoked site... I downloaded the one for clockwork as I have never had a problem with it.

joshua_ said:
If you flashed Forever, it will still say ENG; there isn't an easy way to tell if it's a hard-S-OFF or soft-S-OFF if you have the ENG loader. But yes, if you flashed Forever, you are now hard-S-OFF, and it's OK if it still says ENG -- you just have to remember that you did flash Forever!
Click to expand...
Click to collapse
Flashed forever, says s-off but no ENG... is that normal?
Edit: Disregard that. Answer was already answered.
Sent From My HTC Evo 4G Using Tapa Talk Pro!

So if I use unrevoked forever, I won't be able to unroot it in case I need take it back to sprint?
Sent from my PC36100 using XDA App

Got a question. I rooted using the original method from reginaw when 2.2 first got rooted using the long adb method. I also flashed unrevoked forever and the eng.76 boot loader. Since I just recently flashed the new radio but I'm still showing s-off, do I need to reflash unrevoked forever? Thanks for any help u can give.
Sent from my PC36100 using XDA App

Is there any benefit of the newest Hboot? I originally rooted my phone back in Sept with unrevoked 3.21. It had hboot .92 i believe, but then i flashed the eng .76 bootloader. Everything has been great. But recently I flashed caulkulin's all in one PRI, PRL, WIMAX, and RADIO. My phone has been booting, but I noticed it stays on the flash screen for a good amount of time, sometimes it will even hang up on the flash screen and I have to do a battery pull. Would it benefit me to flash the latest s-off, update OTA to 3.70 and follow the rest of the directions? Thanks for any help you can spare.

[Q] T-Mobile UK - Sensation Rom Dump?

Hi folks,
I've got a T-Mobile branded Sensation, no idea how long they will take to get the 2.3.4 update out, probably months.
I want to S-OFF, Super CID etc and flash something else or just use a Euro RUU.
Problem is, for warranty purposes, I need to back up my current rom or obtain the T-Mobile RUU.
Is there anyway I can dump this rom first?
I've checked the big list of roms for the Sensation, lots of US ones there but nothing for T-Mobile Uk.
Thanks

Backup stock ROM:
1. S-OFF
2. Install CWM
3. Backup with CWM
Job Done!
Restore stock ROM:
1. Restore backup
2. Flash stock recovery
3. Flash stock HBOOT
4. Run S-ON command via adb
Obviously the ROM you restore will have all your personal data so a hard reset after making sure it boots up would be wise to go back to a 100% 'out the box' state

i,m uploading the official TMO uk 1.34 RUU now link to follow
link
http://dl.dropbox.com/u/38694724/RU...0U_10.51.9007.27_M3_release_196473_signed.exe

Where'd you get that?

west2cool said:
i,m uploading the official TMO uk 1.34 RUU now link to follow
Click to expand...
Click to collapse
That's excellent, cheers!!! Definately UK?

It would have to be as the T-Mobile US ones are 1.27/1.29

EddyOS said:
It would have to be as the T-Mobile US ones are 1.27/1.29
Click to expand...
Click to collapse
Would make life alot easier if it is the real deal.

Very true but I'd still backup your ROM as it stands anyway before flashing anything new

EddyOS said:
Where'd you get that?
Click to expand...
Click to collapse
got it off a chinese website, i was hunting around

One i'm specifically after is 1.34.110.1
If you give me a link I can re-host it pretty quick, i've got an 8Mbit upload speed.

Arthur Hucksake said:
One i'm specifically after is 1.34.110.1
If you give me a link I can re-host it pretty quick, i've got an 8Mbit upload speed.
Click to expand...
Click to collapse
link in my first post, dont forget thank

Thanks dude.
If this is the real deal, legit one, then we're onto a winner.

I got a "communications were interrupted" error when using Revolutionary.
Rebooted with vol down, it's showing me as SHIP S-OFF
Ok to assume that it's all ok anyway?

I had this too, run it 3 times and eventually it will say it's done. I did report this on their feedback on the website as well

When I boot up with vol down, it is showing Revolutionary at the top and S-OFF.
Copied the PG58IMG 4.0.1.4 updated over, went into HBoot and it flashed.
Reboot, deleted the PG58IMG off the SD card.
Reboot, back into the bootloader screen and it's allowed me to run clockwork, so now done a full back up which has just finished.
All I want to do next is install the stock European 2.3.4 rom (RUU_Pyramid_HTC_Europe_1.45.401.2), so I assume the next step is to change CID?
Thing is, I want to be able to use future OTA updates with this rom. Am I right in saying that whatever ID I set it to is what updates I will get?
Cheers

Yeah, change CID to HTC__001 and then you're completely unbranded. OTA's should also go through without issue too

Awesome. Job done. CiD change, installed the european rom and i'm now 2.3.4
Bootloader is showing ***locked*** but I aint worried about that.

That's the new HBOOT, you can still use Revolutionary to S-OFF it again if need be (I personally re-flashed the 1.17.0011 HBOOT back as I didn't like the LOCKED message)

EddyOS said:
That's the new HBOOT, you can still use Revolutionary to S-OFF it again if need be (I personally re-flashed the 1.17.0011 HBOOT back as I didn't like the LOCKED message)
Click to expand...
Click to collapse
I don't understand why it still says S-OFF at the top. lol

Because it does, but it's not technically S-OFF - I tried to flash a different HBOOT and it didn't work until I re-ran Revo

Hboot 2.00.0002 ** S ON ** NOT rooted STUCK! what to do?

hello guys! i am completely clueless now... ive been wandering around this forum for more than 4 hours. and i just can't find any help.
my situation is as following:
i tried to unroot my desire s to get the warranty back with this guide: http://forum.xda-developers.com/showthread.php?t=1460713
at some point i accidently flashed hboot 2.00.0002. than i was stuck with the ruu update's error: 140..
i have a goldcard but it just wouldn't let me downgrade to this ruu: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed i am pretty sure that this is the right one...
i got my desire s at an o2 shop here in germany and it comes unbranded.
i tried so many guides, but i can't get out of this misery.
although i was able to get to the recovery (4ext touch), unlocked via htcdev, but unrooted and S-ON.
now my phone boots and gets stock at the ics fallout "htc one" bootscreen.
is there a way to get my desire s to be stock again?

Wierd you can access recovery!!!
Well All I can say is that never try to downgrade from any ics rom to stock ginger bread rom without downgradin your misc version mate.And unfortunately, i think you have to wait for official stock ICS rom.

UmairAhmad said:
Wierd you can access recovery!!!
Well All I can say is that never try to downgrade from any ics rom to stock ginger bread rom without downgradin your misc version mate.And unfortunately, i think you have to wait for official stock ICS rom.
Click to expand...
Click to collapse
yea, very wierd, isn't it?
i tried to fake a misc-version downgrade via adb cmd and i was able to do it once, but it was still higher than the ruu version.

WhatWouldJesusDo said:
yea, very wierd, isn't it?
i tried to fake a misc-version downgrade via adb cmd and i was able to do it once, but it was still higher than the ruu version.
Click to expand...
Click to collapse
Actually I myself encountered this problem using exactly the same guide but somehow i was able to find the higher RUU which did the trick for me. Try to find some higher RUU.
Otherwise go for jtag or xtc clip if u can't wait..
BTW update is just around the corner if you dont want to apply hardware methods

UmairAhmad said:
Actually I myself encountered this problem using exactly the same guide but somehow i was able to find the higher RUU which did the trick for me. Try to find some higher RUU.
Otherwise go for jtag or xtc clip if u can't wait..
BTW update is just around the corner if you dont want to apply hardware methods
Click to expand...
Click to collapse
that's great news! hope is rising
hardware fixes are no option for me, yet. the hole point is to get my phone replaced, so i don't want to eff around too much.
you probably don't know the ruu file anymore, do you?
thanks again.

WhatWouldJesusDo said:
that's great news! hope is rising
hardware fixes are no option for me, yet. the hole point is to get my phone replaced, so i don't want to eff around too much.
you probably don't know the ruu file anymore, do you?
thanks again.
Click to expand...
Click to collapse
RUU_Saga_S_hTC_Asia_India_2.15.720.3_Radio_20.4801 .30.0822U_3822.10.08.04_M_release_226809_signed.exe
As my phone was shipped for India..
I very much doubted that it will help even!!!!
Try to look out for OS 2.3.5 with sense 3.0 for your region...

somehow i managed to install a ruu with a miscversion downgrade.
i did the same thing "nenad_l" did here: http://forum.xda-developers.com/showthread.php?t=1604255
and now i am at 68% completion. i'll report when it's done.
___
it's done!
i appreciate your support umair! thank's a lot!

WhatWouldJesusDo said:
somehow i managed to install a ruu with a miscversion downgrade.
i did the same thing "nenad_l" did here: http://forum.xda-developers.com/showthread.php?t=1604255
and now i am at 68% completion. i'll report when it's done.
___
it's done!
i appreciate your support umair! thank's a lot!
Click to expand...
Click to collapse
Dats nice to hear it

Having unlocked the bootloader and having a functional custom recovery, all you had to do was to run misc_version script from recovery, reboot to bootloader, lock it and proceed with RUU flash. Nothing more.

Got your same problem. I was stuck at the bootloader because I had my desire s unlocked with HTCdev.com. Relocked it and flashed with a previous RUU like 1.47... it worked and then flashed hboot and radio...

u shd hv just unroot n den lock ur bootloader with the token provided when u did htc dev unlock
run d misc ver. changer n zergrush
and den run RUU ...

Correct 1.85RUU / Downgrade?

Will someone post the correct 1.85 RUU for this phone, or send a link to it? Having a little trouble trying to find it. Or maybe I did?
RUU_Evita_Cingular_US_1.85.502.3_R2_Radio_0.71.32.09.12_10.86.32.08L_release_262092_signed
I'm trying to downgrade via this guide: http://forum.xda-developers.com/showpost.php?p=33914948&postcount=65
Edited the mmcblk0p23 just fine, placed it back on my phone and tried to run the RUU but it says that it wasn't able to run, which leads me to the conclusion it's the wrong RUU.
Any input would be fantastic.
Edit: just tried again and this is the error that I am getting.

Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).

redpoint73 said:
Here: http://forums.team-nocturnal.com/showthread.php/1005-RUU-One-X-XL-LTE-RUU-s
Here: http://forum.xda-developers.com/showthread.php?t=1670238
Or also here: http://forum.xda-developers.com/showthread.php?t=1671237
I believe that since you are editing the version number on your phone, it shouldn't matter what RUU version, as long as the CID is correct (which SuperCID should also render a moot point).
Click to expand...
Click to collapse
Well, quick on the draw with 3 links... I have the correct one. Now it's just a matter of finding out why it's not working. I'll look at my CID and see what's going on.

Did you reboot into fast boot and relock the boot loader after applying the edit?

Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?

absolutelygrim said:
Did you reboot into fast boot and relock the boot loader after applying the edit?
Click to expand...
Click to collapse
Yeah. Ran the 2.20 RUU just fine

mlaws90 said:
Im trying this right now but my hex file is all zeros? Why is this and what should I do to resolve this?
Click to expand...
Click to collapse
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.

Myrder said:
The place you have to edit will be on the right side, You'll find the line 0x0a0 on the left.
Click to expand...
Click to collapse
Screenshot:
Is this all I do?:

mlaws90 said:
Is this all I do?
Click to expand...
Click to collapse
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?

Myrder said:
Yeah
Wait, that's your mmcblk0p23? That's wrong, that should have your CID and Clearimage what not above the 0x0a0 line...
Grim, what do?
Click to expand...
Click to collapse
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.

mlaws90 said:
I only have the unlocked bootloader, not SuperCID, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
Oh, that makes sense.. I got the phone two weeks after release, and finally decided to root about 3 weeks ago-ish? so me being dumb I didn't even think to look here before I did the OTA update from AT&T. So I had to do the x factor exploit to get rooted. That might be why yours isn't like mine...? I'm not 100% sure on that one.

mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day. Could this be why? I am getting an RUU Error 154 or 155 I think why I do try it it will go about 2 min then fail.
Click to expand...
Click to collapse
That was the same way mine was. I got the 155 error. Going to run some errands after I get my phone back working again.. and give it another go later.

mlaws90 said:
Yeah, I only have the unlocked bootloader, not SuperCID, I THINK, I did it a long time ago, I got the phone on release day.
Click to expand...
Click to collapse
You can't have an unlocked bootloader without SuperCID on the AT&T branded version. Or possibly another CID besides the AT&T CID, since AT&T's CID is not allowed on HTCDev.com.

Should look like this

absolutelygrim said:
Should look like this
Click to expand...
Click to collapse
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.

mlaws90 said:
But why doesnt mine look like that , can someone upload a mmcblk0p23 for me to use, if that is possible. Mine is all Zeros and I get the 154 or 155 error on RUU.
Click to expand...
Click to collapse
Try extracting p23 with your phone plugged into a computer and USB debugging on

I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.

Myrder said:
I'll give this another go later tonight, If it doesn't work I'll just downgrade my hboot and leave it alone. lol.
Click to expand...
Click to collapse
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.

mbh87 said:
I drowngraded hboot, changed main version and then ran the RUU just now with no problems. Weird that it isn't working for you.
Click to expand...
Click to collapse
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.

Myrder said:
First time I got ahead of myself and didn't save the mmcblk0p23... The next time, idk wtf happened. I'll downgrade hboot in a bit and then try again to see what that will do.
Click to expand...
Click to collapse
If you tried running it over the top of 2.20 without downgrading hboot then that would be a problem too.

[Q] Updated to Jellybean -> Flashed custom ROM -> Have issues

So after having Jellybean updated on my Telstra One XL I decided to much around with recoveries and custom ROMs to see if I could get them running. I realised that this was going to cause issues, but I was fine with mucking around with it.
I unlocked the phone and got a recovery installed and of course the touchscreen didn't work in recovery. So I mucked around with it and managed to get ROMs installed via manual boot.img flashing and manual ROM flashing via:
Code:
adb shell recovery --update_package=/sdcard/rom.zip
My test was with CM10 and it got up and running. The only issue is that touchscreen doesn't work. Which made any progression through the setup phase impossible
If anyone has any clues as to how to get this up and going again I'm all ears.
I tried to use JET to roll back the HBOOT and try to roll back the firmware, but the RUUs wanted none of it.
Thanks in advance,
Anthony

Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135

twistedddx said:
Did you also fix the version number on mmcblk0p23 before attempting an older RUU?
eg:
http://forum.xda-developers.com/showthread.php?t=1671135
Click to expand...
Click to collapse
No I didn't, must've missed that. Thanks, I will try that.

Didn't work with any RUU either.
EDIT: Got the RUU installed, thank you very much. I was an idiot and forgot to relock my bootloader again

I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium

Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?

DESERT.TECH said:
I would use twrp on the hoxl for recovery. Its not failed me yet
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
Not really relevant.
twistedddx said:
Hooray first success story of a downgrade.
Was this 3.17 and down to what ruu?
Click to expand...
Click to collapse
RUU_Evita_UL_Telstra_WWE_1.81.841.1_R_Radio_0.17a.32.09.03_2_10.85.32.16L_release_259804_signed.exe
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Tried the unbricking process, but it won't work. Going to get it replaced now.

Antonioffaxii said:
Not really a success though. Once it pushed through the RUU, it bricked the phone. No power LED, won't start etc.
Click to expand...
Click to collapse
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.

twistedddx said:
Dam!
Did you try Jet again to get back to hboot 1.09 a second time?
Does it allow you to RUU again or just nothing?
I would have tried a newer RUU also, like 2.42.
Click to expand...
Click to collapse
I couldn't restore it in anyway, I had work so I took it with me and had it replaced.
Now I have one that works again!