Related
Now we have S-Off for HBOOT 1.06 (CDMA)
This will allow you to use UNREVOKED 3.0 to root your phone. Enjoy!!!!
http://alpharev.nl/x/beta/
Do I miss something, but what new in it for Desire?
We already have S-OFF with Alpharev 1.80.
Why do we need AlpharevX?
dmatik said:
Do I miss something, but what new in it for Desire?
We already have S-OFF with Alpharev 1.80.
Why do we need AlpharevX?
Click to expand...
Click to collapse
Pretty simple : Those who had HBOOT > 0.93.0001 couldn't S-off their device before. Now, it seems they can. Then you won't need this unless you have this kind of HBOOT.
kev94 said:
Pretty simple : Those who had HBOOT > 0.93.0001 couldn't S-off their device before. Now, it seems they can. Then you won't need this unless you have this kind of HBOOT.
Click to expand...
Click to collapse
not true. I have been able to s-off with 0.93.0001. Thats not the point of it.
I also checked my Desire and I got S-Off with Alpharev 1.80 and HBOOT 0.093.0001.
So, whats the difference?
Should this NOT be in the dev-forum?
Sent from my bicycle with no wheels
i only updated with new HBOOT and never used alpharev beta tool (only the old one). Check my sign...
This is specifically for CDMA users and newer HTC devices. It also means you don't have to root as you're already S-OFF - you can just flash a new ROM after flashing a custom recovery
kev94 said:
Pretty simple : Those who had HBOOT > 0.93.0001 couldn't S-off their device before. Now, it seems they can. Then you won't need this unless you have this kind of HBOOT.
Click to expand...
Click to collapse
> = higher then hboot 0.93.0001.
So if your hboot is higher then 0.93.0001. You cant get s-off so his info is correct.
Scotsman828 said:
Now we have S-Off for HBOOT 1.06
This will allow you to use UNREVOKED 3.0 to root your phone. Enjoy!!!!
http://alpharev.nl/x/beta/
Click to expand...
Click to collapse
You don't even have to run unrevoked. Once they have S-Off some people have rooted by fastboot flashing a custom recovery, then flashing superuser as a zip. There's a tutorial thread over in AndroidForums (Desire All Things Root forum).
Presumably a pre-rooted ROM would also work at this point, but I guess this allows you to run Ti backup etc before doing that (or keep the current ROM).
Edit: Of course anyone doing it this way must make sure they flash the correct recovery for their device (GSM or CDMA). I believe that it's only (some) CDMA devices which have HBOOT 1.06, so most can just use unrevoked without this. And remember it's still in beta at the moment.
But it means that previously unrootable Desires can now be rooted
Yes this is for CDMA version of Desire. I tried Unrevoked before this came out and could not get root. After I ran the Alpharev to get S-Off, I got root with Unrevoked. Had to run Unrevoked so I could get ClockworksMod recovery. It was a really simple process, no need to create a special CD. I quickly canned the HTC ROM for CM7. Data worked without APN restore. Life is good
once you're s-off, you should to flash recovery through fastboot. Now you're able to flash any rom
Indeed ive just used revolutionary and it worked flawlessly on desire hboot 1.06
So I've tried about 5 different RUU's to get my phone back to 2.2 with no luck.
Either a signature error or bootload mismatch or something or another.
I have a Sprint HTC Evo with 2.3.3.
Can someone help me get this thing back and running on 2.2?
I recently tried to use Unrevoked on it...which caused some issues with the bootloader .
Thanks, guys/gals
If you aren't s-off then you can't run an RUU for an older version. If you are s-off, just flash a rooted stock 2.2 rom. You can try a different RUU if you're already s-off, just make sure that you follow the directions closely.
If you're trying to root by downgrading, it won't work unless the phone is already s-off. If the phone is s-off and you're trying to gain root access, just flash a PC36IMG of a recovery then flash a rooted rom from there.
If you're taking it in for repair, keep s-off so you can re-root if you get the phone back (if you're already rooted and want to stay that way).
Sent from my PC36100 using Tapatalk
plainjane said:
If you aren't s-off then you can't run an RUU for an older version. If you are s-off, just flash a rooted stock 2.2 rom. You can try a different RUU if you're already s-off, just make sure that you follow the directions closely.
If you're trying to root by downgrading, it won't work unless the phone is already s-off. If the phone is s-off and you're trying to gain root access, just flash a PC36IMG of a recovery then flash a rooted rom from there.
If you're taking it in for repair, keep s-off so you can re-root if you get the phone back (if you're already rooted and want to stay that way).
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
Hey, thanks for the reply .
I'm not sure what you mean by S-OFF/S-ON however .
Also, I've tried probably five or six different RUU's, none of them want to run.
Hi,
I'm very familiar with flashing ROMs on phones and have flashed a fair few in my time. I flashed my sisters Desire S a while ago but recently the phone has stopped detecting the SIM card and subsequently has to go back for warranty.
I've flashed a Stock rom over it - trouble is, I now have the locked HBOOT v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade HBOOT to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
I cannot for the life of me downgrade the HBOOT version - I've tried every method out there!
I am very familiar with working in command line on Windows and Linux so don't be afraid to get technical!
Any help is very much appreciated!
Daft question, but have you tried a different Sim?
Does she still have the box?
Swyped from my Desire S using XDA Premium
Haha I spent hours debugging the sim card issue and finally came to the conclusion it's a hardware fault!
Yes - tried several different sim cards from two different carriers (this household only uses 2 carriers!)
Also tried several different ROMs/Radios - she was happily using MIUI for months then she just told me it stopped detecting her SIM card - she certainly hasn't been playing with ROMs so I know it's nothing she has done.
Update: Box is long gone
I've flashed a Stock rom over it - trouble is, I now have the locked bootloader v 2.00.0002 with S-OFF!
Could someone verify if these steps are correct? I'm not too familiar with the Desire S.
1. Downgrade bootloader to earlier version - 0.98 i think it is.... or 0.68
2. Turn S-ON
3. Flash RUU Stock ROM
Can I skip the first step? I guess not.
What has me confused is that you flashed the 0.98 hboot and you said it was s on, now you ran the RUU, and its s off....
Did you use revolutionary to get s off or was it s off to start with?
The correct steps would be.. (if you use revolutionary)
1. Use fastboot to flash 0.98.2000 over the revolutionary one.
2. Run correct RUU.
Problem you could run into are cid's of the RUU (make a goldcard to avoid error) and two misc version being higher than RUU.
Thanks for the reply. I never said it was S-on, the phone was running a custom MIUI ROM with S-Off, I flashed a stock rom straight over the top of it by running the RUU (pretty sure I shouldn't have done!) now I have stock ROM with S-Off and locked HBOOT v2.00.0002
I cannot remember if I used revolutionary to get s off originally - it was many months ago, more than likely though. I remember the phone came with S-On and I had to make it S-Off.
I just want to get S-On again with stock rom but it's proving impossible!
So just to clarify, it is currently running stock rom with LOCKED HBOOT v2.00.0002 and S-Off.
I've tried manually overwriting the version with miscinfo, I've also tried the zerg method - all to no avail.
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
foX2delta said:
I have NEVER heard of a stock hboot that is s-off, only when the phone was s-off to start with (early models), or if you used a clip.
Flashing the RUU would bring the phone back to completely stock. (if it flashed correctly)
Click to expand...
Click to collapse
Haha want screenshots? I assure you that's what I've got.
Ran an older RUU which has downgraded my HBOOT to 0.98 or 0.68 (can't remember off top of my head) and am running stock rom, HBOOT says ***locked*** at top and also says S-OFF.
I think I'm getting there now.
Hi, guys, first of all I'm an absolute noob so bear with me if I didn't found all the answer even after having searched through the forum.
My big question is about the re-engineered HBOOT 2.00.002. I have a virginal Desire S, non s-off'ed and non rooted, HBOOT is the latest, that is 2.00.002. I want to load the latest official ICS rom from htc and, as I think I understood, HBOOT must be latest version, therefore non s-off since there is no way to s-off that version. But I also would like to just go to CM10 in the future.
Then I read about the re-engineered HBOOT 2.00.002. This HBOOT should give me s-off and the ability to load the ruu rom. Only catch is that you should re-partition the phone. And that's when things get weird. Does I need to do the re-partitioning before installing the ruu ICS rom after installing the re-engineered HBOOT? If so, in order to install the ruu ICS rom, does I need to have any working rom on the phone, that is, does I need to do the nandroid backup to have back my ginger bread 2.3.5 before installing the ruu ics rom?
And going on, currently there is any way to root the phone while on ICS htc stock rom?
But most important of all, what this re-enginnered hboot really is? The revoked/revolutionary mod only works on hboot versions before the 2.xxxx. Is this re-engineered hboot a 2.00.002 official hboot that has been modified to be s-off or is it a previous hboot s-off'ed via revolution but with a different version number?
Thank you all,
Vincent.
zipponap said:
Hi, guys, first of all I'm an absolute noob so bear with me if I didn't found all the answer even after having searched through the forum.
My big question is about the re-engineered HBOOT 2.00.002. I have a virginal Desire S, non s-off'ed and non rooted, HBOOT is the latest, that is 2.00.002. I want to load the latest official ICS rom from htc and, as I think I understood, HBOOT must be latest version, therefore non s-off since there is no way to s-off that version. But I also would like to just go to CM10 in the future.
Then I read about the re-engineered HBOOT 2.00.002. This HBOOT should give me s-off and the ability to load the ruu rom. Only catch is that you should re-partition the phone. And that's when things get weird. Does I need to do the re-partitioning before installing the ruu ICS rom after installing the re-engineered HBOOT? If so, in order to install the ruu ICS rom, does I need to have any working rom on the phone, that is, does I need to do the nandroid backup to have back my ginger bread 2.3.5 before installing the ruu ics rom?
And going on, currently there is any way to root the phone while on ICS htc stock rom?
But most important of all, what this re-enginnered hboot really is? The revoked/revolutionary mod only works on hboot versions before the 2.xxxx. Is this re-engineered hboot a 2.00.002 official hboot that has been modified to be s-off or is it a previous hboot s-off'ed via revolution but with a different version number?
Thank you all,
Vincent.
Click to expand...
Click to collapse
If I was you I would forget about the re-engineered HBOOT and just run the RUU and put ICS on your phone.
The re-engineered HBOOT is only for people who have S-Offed using the revolutionary method and have had trouble with the Android 4.0 Sense ROMs. You have absolutely no need to use it now.
If you want CM10 in the future then all you need to do is unlock your bootloader with htcdev, flash a new recovery (4EXT or CWM) and install CM10 from your custom recovery. You will be required to flash the boot.img file separately if you are S-On.
Hi Kavrocks, thank for your prompt answer. I'll surely follow your advice, it's the easiest way and my first goal is to get an easy ICS on my phone. My only doubt is about being able to get to cm10 or whatever else since no rooting hack has already been developed for the new ICS rom.
Do you think HTC will push updates on the new ICS rom or, being it for developer only, it will be just stuck to its original state?
Kavrocks said:
If I was you I would forget about the re-engineered HBOOT and just run the RUU and put ICS on your phone.
The re-engineered HBOOT is only for people who have S-Offed using the revolutionary method and have had trouble with the Android 4.0 Sense ROMs. You have absolutely no need to use it now.
If you want CM10 in the future then all you need to do is unlock your bootloader with htcdev, flash a new recovery (4EXT or CWM) and install CM10 from your custom recovery. You will be required to flash the boot.img file separately if you are S-On.
Click to expand...
Click to collapse
zipponap said:
Hi Kavrocks, thank for your prompt answer. I'll surely follow your advice, it's the easiest way and my first goal is to get an easy ICS on my phone. My only doubt is about being able to get to cm10 or whatever else since no rooting hack has already been developed for the new ICS rom.
Do you think HTC will push updates on the new ICS rom or, being it for developer only, it will be just stuck to its original state?
Click to expand...
Click to collapse
Original.
By what I understand, now that an official ICS ROM is out and thus binary drivers are available, we should expect a fully working non-original ROM in a short time. How much time do you think it will take for the CMx developer to integrate the binaries into the CMx ROM?
zipponap said:
My only doubt is about being able to get to cm10 or whatever else since no rooting hack has already been developed for the new ICS rom.
Click to expand...
Click to collapse
Don't tell this my Desire S, HBOOT 2.00.002, S-ON, unlocked with stock ICS and root
Just do this:
- unlock your phone: www.htcdev.com
- Install stock ICS
- install a custom recovery using fastboot
- install superuser using custom recovery
Ok, I've succesfully got ICS on my Desire, eventhough I had to do a 'fastboot oem lock' to get past a 155 error. Now, would you please be so kind to tell me the exact filename of the superuser exploit that you have applied on ICS? I'm asking this to you because I've tried the 3.1.3 on GB2.3.5 and it always hang on 'waiting root access right'.
Thank you.
Vincenzo.
esque said:
Don't tell this my Desire S, HBOOT 2.00.002, S-ON, unlocked with stock ICS and root
Just do this:
- unlock your phone:
- Install stock ICS
- install a custom recovery using fastboot
- install superuser using custom recovery
Click to expand...
Click to collapse
Ok, I'll answer to myself, use the CWM-SuperSU-v0.95.zip archive. It works with ICS.
zipponap said:
Ok, I've succesfully got ICS on my Desire, eventhough I had to do a 'fastboot oem lock' to get past a 155 error. Now, would you please be so kind to tell me the exact filename of the superuser exploit that you have applied on ICS? I'm asking this to you because I've tried the 3.1.3 on GB2.3.5 and it always hang on 'waiting root access right'.
Thank you.
Vincenzo.
Click to expand...
Click to collapse
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Edit 2013-07-10: I've solved my issues and am now on Hboot 2.15 with S-OFF (didn't lose it with the upgrade) and CM10.1! See the last post for details.
m1schi said:
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Click to expand...
Click to collapse
Since you are already S-OFF there is no need to upgrade your H-Boot. That does not effect the rom at all. With the Radio, when you flash the Rom it will automatically change the radio to the one preset by CM10.1 for the Rom. If you live in an area not covered by the radio, with S-OFF, you can flash any radio that you would like that is covered where you live and gives you the best service for your Provider.
m1schi said:
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Click to expand...
Click to collapse
Change your cid back to your og HTC one.
Supercid has lost most it value since your soff. You can change it whenever you want.
Ehh the low hboot you have has almost no added use since your s-off.
Forget about needing a new radio, who told you that? You can flash whatever radio you want.
You need a update hboot and firmware.
New kernels require that. Not radio.
Easiest way. Run latest ruu with your original unbranded HTC cid. No need to relock or s-on. Afterward custom recovery and start flashing.
Verstuurd van mijn One S met Tapatalk
Thanks for the answers!
Still I'm puzzled a bit: I need HBOOT 2.15 for the newer ROMS using the newest Kernel? Meaning I can just update the HBOOT version via the command line, because of my S-OFF and flash the ROM I want? No need to use all the procedures you find around here? I'll preserve my S-OFF?
m1schi said:
Thanks for the answers!
Still I'm puzzled a bit: I need HBOOT 2.15 for the newer ROMS using the newest Kernel? Meaning I can just update the HBOOT version via the command line, because of my S-OFF and flash the ROM I want? No need to use all the procedures you find around here? I'll preserve my S-OFF?
Click to expand...
Click to collapse
if flashing a ruu s-off will be preserved.
so
change to your original cid with fastboot command.
flash a ruu wich is/came originaly with your cid/device (lower version is no problem, if you cant find the jb one of your device),
then do otas till your on JB.
the flash stock recovery, then custom rom. finished.
m1schi said:
Right now I'm using the latest ViperROM 2.2.0 with S-OFF, Hboot 1.06 (flashed via S-OFF) and SuperCID 111111. The phone is an unbranded, european, unlocked, non-tmobile phone. Now I was looking into using the newest CM10.1, but for this I'd need to upgrade my radio (and Hboot?).
I haven't had the time to follow all the events. When trying to read what way I should follow, I stumbleupon bricked devices and people who don't have problems. So I actually don't know what to believe and what to do.
Could anyone point me out what I should do with my device do minimize the risk of bricking it while upgrading? Would have followed the instructions in this post http://forum.xda-developers.com/showthread.php?t=2322755, but the 2nd post makes me anxious.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=43400980&postcount=22
vatsaman said:
http://forum.xda-developers.com/showpost.php?p=43400980&postcount=22
Click to expand...
Click to collapse
That's what I'm wondering about: Everyone seems to tell me some other way to upgrade my phone.
You tried to upgrade your phone via RUU?
There seems to be a method without the RUU, just fastboot: http://forum.xda-developers.com/showthread.php?p=42985992#post42985992
This should get me onto the newest HBOOT and let me use AOSP ROMS with 3.4 Kernel, without loosing S-OFF or bricking my device?
Edit 2013-07-10: I've used this method to go from my hboot 1.06 to hboot 2.15, while still having S-OFF.
http://forum.xda-developers.com/showthread.php?p=42985992#post42985992