Hi there,
This is a guide under construction that gather different ways to get (back) to HTC stock ROM from almost everything : branded ROM, custom ROM, ROOTed/S-OFFed/etc. DHD.
Whatever you do with your phone, I cannot be responsible for it. Don't blame me if you brick it. I'll try to keep this up to date.
How to read this ?
Colors :
This answer is known and working
This answer still needs some testing/feedback
This answer is probably wrong or untested, help me correcting it
Letters : This is a change of situation. Multiple case possible, choose your path and skip the others
Numbers : This is a step or a question, go through them one by one
Here we go for the GUIDE part :
I have never ROOTed/S-OFFed/Radio S-OFFed/CWMed my phone
In this case you have either a stock HTC ROM or a branded ROM (SFR/Vodaphone UK/T-Mobile/...)
1) How do I know that I have a branded ROM or an HTC stock ROM ?
HTC Stock ROMs are often up to date if you do all the OTAs so, update your phone OTA and check your version number, it should be the last one. Moreover, branded ROMs often have a custom boot screen (with awful logo) and custom (unremovable) apps.
1.A) I have DHD with stock ROM !
You have nothing to do in this thread then. Bye bye
1.B) Damn, I have a branded ROM...
Don't cry, we'll go through it together
1.B.1) Will RUUs work ?
Sometimes it will, sometimes it won't, the best thing to do is to try. The worst that could happen is... nothing.
Warning : At this point, if RUU works, you'll have a stock ROM on your HTC and you won't be able to go back to your branded ROM (except for T-Mobile phones as a RUU is available for them). No turning back ! Anyway, that shouldn't be a problem for warranty as RUUs are "public and official".
1.B.2) Why RUUs wouldn't work ?
HTC allow brands to put their own custom firmware that we call here a "branded ROM". Those include brand promotional items such as specific apps and boot screen. Plus, they have their specific OTA that could be on a very different schedule than official ones (from HTC). For this reason and to avoid county-specific (chineese) to be converted in WWE phones, HTC RUUs check for a specific number in your phone called CID. This CID tells if you can use RUUs and if yes, wich one (WWE, chineese, etc.)
1.B.3.a) RUU worked !
Lucky boy, we're done with you. Bye bye
1.B.3.b) RUU didn't work...
Please, hold you're tears, we're still not done here. (More to come)
1.B.3.b.1) Now you have a few solutions
The zip trick :This is a method that uses a test RUU (that doesn't check for the CID). Then you fake it replacing the test ROM by the one of your choice (here an official one). This method is described here but not tested on branded phone. This may not allow OTAs (need feedback).
ROOT & Radio S-OFF/SuperCID/Unlock your phone :By changing the Radio with this guide you will be allowed to flash all RUUs. No revert tool so far to restore the Radio but this is coming soon.
The F.A.Q. part :
1) Is that possible to find a stock ROM extracted from RUU without any cooking and flash it with CWM ?
Yes
2) Where can I find the zip to use with CWM ?
Here (link needed)
Glossary :
CWM or CM : ClockworkMod
Random stuff :
http://forum.xda-developers.com/showthread.php?t=835595 : Maybe a way to flash a RUU without changing the CID ? Need confirmation
http://forum.xda-developers.com/showthread.php?t=841890 : Same here
http://forum.xda-developers.com/showthread.php?t=835595&page=4#edit9551194 : Working exemple without goldcard ?
Working on this thread... Any help is welcome
Please submit your questions/answers in this thread, i'll add them.
If giving answers, please, also give a source or guide (link) if possible and the color (green or orange, no red accepted as red cannot be trusted)
for later use
same as above
I can confirm that with Radio S-OFF it is possible to flash a RUU and get OTAs work. Everything will go back to stock except the Radio S-OFF, which will remain. If the device had also a bootloader S-OFF (ENG hboot), it will be replaced with the stock one.
If a device has only bootloader S-OFF, flashing a RUU is not recommended, as it will fail at version checking (because of no SuperCID). Eng bootloader has a higher version number than stock bootloader, and without Radio S-OFF the system will not allow downgrading.
jkoljo said:
I can confirm that with Radio S-OFF it is possible to flash a RUU and get OTAs work. Everything will go back to stock except the Radio S-OFF, which will remain. If the device had also a bootloader S-OFF (ENG hboot), it will be replaced with the stock one.
If a device has only bootloader S-OFF, flashing a RUU is not recommended, as it will fail at version checking (because of no SuperCID). Eng bootloader has a higher version number than stock bootloader, and without Radio S-OFF the system will not allow downgrading.
Click to expand...
Click to collapse
Is there a way to flash back the Radio S-OFF to the original one ? As far as I know, Radio S-OFF creates a backup of the partition it changes but I didn't see any tool that can change back this partition.
Edit: Seems I'm not the only one asking this question : http://forum.xda-developers.com/showpost.php?p=9642351&postcount=64
Also, when you say "not recommended" it's because it'll always fail or it has a little chance to fail ?
If you are S-OFF (not radio) there is no way to flash RUU again ? What about extracting the ROM from the RUU and flashing it with CWM ? same problem ?
Thanks
As stated in my Radio S-OFF thread somewhere in the last few pages (forum search is recommended), tools for Radio S-OFF removal are coming, but you just have to wait a bit longer. The backup that has been made is vital for the process, so do not lose it!
Not recommended, as it will most likely (probably always) fail. Without Radio S-OFF RUU is indeed not possible, unless you manually flash back the original bootloader using the original way of getting it in there (wpthis.ko + dd image). You would have to be in the stock ROM for that to work. Extracting a ROM should be possible, but I am not a ROM chef, so do not believe me
See my thread here for how to extract the rom.zip [i.e: update.zip] out of an RUU. RUU will write practically all partitions, but won't overwrite a radio-set S-OFF (i.e done through radio, not through hboot)
ivolol said:
See my thread here for how to extract the rom.zip [i.e: update.zip] out of an RUU. RUU will write practically all partitions, but won't overwrite a radio-set S-OFF (i.e done through radio, not through hboot)
Click to expand...
Click to collapse
Thanks, will add this to the FAQ/GUIDE
ivolol said:
See my thread here for how to extract the rom.zip [i.e: update.zip] out of an RUU. RUU will write practically all partitions, but won't overwrite a radio-set S-OFF (i.e done through radio, not through hboot)
Click to expand...
Click to collapse
ivolol said:
note: This is mainly for stock phones, for vendor-derived ones (e.g Vodafone DHDs in Australia) you will also need a goldcard.
Click to expand...
Click to collapse
I understood that it'll wipe everything except Radio S-OFF but what if this is done (method A or B) with a vendor-derived DHD ? Will that work ? Why wouldn't it ? Will OTAs be possible ?
Thread re-open. Follow the OP's rules and suggestions please.
Cheers,
M_T_M
jkoljo said:
As stated in my Radio S-OFF thread somewhere in the last few pages (forum search is recommended), tools for Radio S-OFF removal are coming, but you just have to wait a bit longer. The backup that has been made is vital for the process, so do not lose it!
Not recommended, as it will most likely (probably always) fail. Without Radio S-OFF RUU is indeed not possible, unless you manually flash back the original bootloader using the original way of getting it in there (wpthis.ko + dd image). You would have to be in the stock ROM for that to work. Extracting a ROM should be possible, but I am not a ROM chef, so do not believe me
Click to expand...
Click to collapse
Are there any issues with the wpthis.ko + dd image method to write the original hboot over the engineering? I've returned system, boot, recovery, etc. to their branded originals. I don't see why there would be a problem but just seeing if anyone's tried this.
The other option is 'fastboot flash hboot'. With this method, I'm not sure if I'd have to 'fastboot erase hboot' first and frankly doing that seems a bit risky because if the fastboot flash fails, you're really screwed.
No, dd can overwrite it just fine.
BUT I would do it like this (now that my tool can do radio s-on):
Radio S-OFF (if not already)
Run stock RUU
Do stock cid and radio s-on with my tool
And your device is stock.
jkoljo said:
No, dd can overwrite it just fine.
BUT I would do it like this (now that my tool can do radio s-on):
Radio S-OFF (if not already)
Run stock RUU
Do stock cid and radio s-on with my tool
And your device is stock.
Click to expand...
Click to collapse
I was thinking about this solution which works flawlessly it seems. I made this guide for ppl that wanted their HTC Stock for real and your tool wasn't able to S-ON ^^
Anyway, still missing the feature to restore the CID as it was BEFORE your tool makes radio S-OFF.
I follow your thread and so far, as I understood, there's a field where we can put the string we want but nothing to restore as it was before. Right ?
For ppl who want to restore to their branded ROM (if they made a backup with CWM) what do they have to do ?
My guess :
1) Root + Radio S-OFF
2) Remove S-OFF if any (not Radio S-OFF !) by flashing any RUU
3) Root again (as root is lost by flashing RUU)
4) Reinstall CWM
5) Now the phone is still S-OFF and SuperCID, right ?
6) Restore ROM via CWM (does this restore the S-OFF we had when we made the backup via CWM ?)
7) Remove S-OFF if still here (how ?)
8) Radio S-ON with the tool (with previous CID)
9) Done, happy branded stock ROM fully functional
Diaoul said:
6) Restore ROM via CWM (does this restore the S-OFF we had when we made the backup via CWM ?)
7) Remove S-OFF if still here (how ?)
...
9) Done, happy branded stock ROM fully functional
Click to expand...
Click to collapse
6) CWM/Nandroid doesn't backup/restore hboot so we'll still have stock S-ON hboot from RUU.
7) See above
9) Except you still have CWM recovery as this would have been flashed when you made the ROM backup (either replace recovery.img in CWM backup with stock recovery before restoring? or overwrite with dd after?). Also, the ROM you restored might still be rooted (unroot with Visionary?).
dazweeja said:
6) CWM/Nandroid doesn't backup/restore hboot so we'll still have stock S-ON hboot from RUU.
7) See above
9) Except you still have CWM recovery as this would have been flashed when you made the ROM backup (either replace recovery.img in CWM backup with stock recovery before restoring? or overwrite with dd after?). Also, the ROM you restored might still be rooted (unroot with Visionary?).
Click to expand...
Click to collapse
As far as I understand, people with branded phones will still have the recovery from CWM. And, so far, no easy way to replace it.
It seems like a tool to do that would be welcome here. What do you think jkoljo?
Diaoul said:
My guess :
1) Root + Radio S-OFF
2) Remove S-OFF if any (not Radio S-OFF !) by flashing any RUU
3) Root again (as root is lost by flashing RUU)
4) Reinstall CWM
5) Now the phone is still S-OFF and SuperCID, right ?
- Yes
6) Restore ROM via CWM (does this restore the S-OFF we had when we made the backup via CWM ?)
- Does not restore s-off
7) Remove S-OFF if still here (how ?)
- Radio S-ON has to be removed, see next step
8) Radio S-ON with the tool (with previous CID)
9) Done, happy branded stock ROM fully functional
- You should do visionary remove permroot, then the system is full stock
Click to expand...
Click to collapse
If you have non branded device, my tool will automatically restore the stock cid. Otherwise a user has to check the cid from the bootloader himself before doing s-off.
Sent from my Desire HD using Tapatalk
I'm testing all this stuff on my branded phone.
I started with a Rooted + S-OFFed DHD with AR 1.9 :
1) Radio S-OFF
2) RUU
3) Trying to temproot gets stuck on "rooting device, please wait"... Any clue ?
Edit : I grabed another copy of VISIONary here and it worked.
I had r14 before, downloaded r14 but files were slightly different in size... Anyway, package installation worked for both and I even successfully root my device with the first one long time ago. Weird
Are you still radio S-OFF? In which case, do you need to root again? The Vision wiki says you only need radio S-OFF for permanent root:
"If you are only interested in permanent root you only need radio S-OFF"
http://forum.xda-developers.com/wik...cess_.28Permanent_Root_.2F_.22Permaroot.22.29
Maybe install Superuser.apk and busybox and then see if you can install ROM Manager/CWM.
Edit: Or try typing 'su' into a terminal app like ConnectBot or Terminal Emulator.
I've returned to the dark side with a stock Sense rom (instead of CyanogenMod), because I'd like to OTA update to HTC's gingerbread rom when it comes (hopefully soon).
I installed the signed HTC rom.
I'm not sure, but I think it's a good idea to follow the instructions for radio S-OFF, superCID and simunlock (from Apache14 himself: http://forum.xda-developers.com/showthread.php?t=857444) before installing a signed rom.
The signed rom was courtesy of xmoo's thread: http://forum.xda-developers.com/showthread.php?t=824357
Yes, there will be a CyanogenMod 7 based on Gingerbread probably soon after HTC releases their rom, and I'll be back then.
I still have root, Eng-Hboot and the official clockworkmod recovery installed. I re-installed eng-hboot and clockworkmod just to be sure, after installing the signed rom using the HTC installer
I believe that my carrier won't have anything to do with it (i.e. I won't need to wait for them to modify the Gingerbread rom), as I I'm using a plain brown HTC rom. Although someone could tell me I'm wrong.
Walker Street said:
I've returned to the dark side with a stock Sense rom (instead of CyanogenMod), because I'd like to OTA update to HTC's gingerbread rom when it comes (hopefully soon).
Click to expand...
Click to collapse
You'll probably find that LeeDroid, Android Revolution, and the other ROMs which are based on the stock HTC ROM will be upgraded within a few days of the Gingerbread HTC ROM being released. I find those to be a little better than stock as they have a lot of the crap removed. I found LeeDroid very easy on the battery too.
I'm not sure, but I think it's a good idea to follow the instructions for radio S-OFF, superCID and simunlock (from Apache14 himself: http://forum.xda-developers.com/showthread.php?t=857444) before installing a signed rom.
Click to expand...
Click to collapse
jkoljo's Windows program is a front-end for the same program that Apache14 uses (gfree) so you get the same result with less hassle.
I believe that my carrier won't have anything to do with it (i.e. I won't need to wait for them to modify the Gingerbread rom), as I I'm using a plain brown HTC rom. Although someone could tell me I'm wrong.
Click to expand...
Click to collapse
Yes, that's right. SuperCID will let you install any signed ROM. S-OFF will let you install any ROM at all.
The issue some of us are facing is trying to get back to an untouched branded ROM (for warranty purposes). It can be done a number of ways, just trying to discern the safest. I think it's probably:
1) Radio S-OFF
2) Flash RUU
3) Install CWM
4) Restore ROM via CWM
5) Restore original recovery with 'dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p21'
6) Radio S-ON with the tool (with previous CID)
7) Done
I'm going to test this over the weekend.
Related
NOT COMPATIBLE WITH DEVICES SHIPPED WITH GINGERBREAD 2.3
One click Radio S-OFF tool
YouTube videoHTC - Quietly Unlocked
About:
This tool will make a Desire HD Radio S-OFF after it has been permrooted with Visionary. After running this tool, you can flash any ROM and kernel to your device using ClockworkMod. No bootloader S-OFF needed! You use this tool at your own risk!
What's the difference to other methods?
First of all, this is easy. The steps are straightforward, you do not need to tinker with complicated command line stuff. Radio S-OFF is the way these devices are meant to be made S-OFF, it is a safe way. If you use this method, reverting to stock is very easy! Unfortunately without ENG bootloader (my other tool) you cannot use fastboot commands (advanced stuff) and, for example, my Kernel Update Utility. To make a raw comparison, this tool is for everybody including new users and the eng hboot S-OFF version is for enthusiasts. Many experienced users have both, because having both allows supreme flexibility.
I recommend to use Radio S-OFF instead of traditional bootloader ENG S-OFF, because this can be more easily removed and is much much safer!
System requirements:
Windows XP SP2 or higher
.NET Framework 4.0
HTC Sync (or ADB drivers)
Desire HD with stock kernel (or Apache14's 1.0.7 / 1.1.4 Sense)
It will not work on 1.72.405.3 or higher build, or new radio (12.28b.60.140e_26.03.02.26_M is ok). Downgrade first!!
So, in detail, the Root & S-OFF process goes like this:
Install Visionary
Open Visionary and tap temproot, then attempt permroot now. Your device will reboot.
Connect your phone to a computer (make sure you have USB Debugging enabled. Connect charge only!)
Download the Radio S-OFF tool and place it in the root of your hard drive (c:\[tool folder goes here])
Open my "Desire HD easy radio tool.exe" (Windows 7, right click & run as administrator), choose the first option, click "Do it"! There may be a SuperUser request on your phone, allow it.
Done. (Remember to click the thanks button)
But you might want to continue if you are a new user:
If you want to flash a radio (to improve signal and battery life) some day, do ENG S-OFF (no need to use Visionary again, just run the tool)
To flash a custom rom: Get Rom manager from the market, which will install a ClockWorkMod recovery for you. Just open it up and tap "Flash ClockworkMod recovery"
Download a custom ROM, put it to your SD, and flash it using Rom manager or ClockworkMod itself. You can access ClockworkMod through Rom manager. It is recommended to do "wipe data / factory reset" in ClockworkMod before installing ROM from SD card.
It will create a backup of your phone partition 7 (radio config) to the root of your sdcard, I recommend to keep that somewhere really safe!
To go back to S-ON:
Flash stock ROM (RUU, not over 1.7)
Temproot using Visionary
Use my tool, do Stock CID and S-ON (enter brand CID if you had a branded device, see second post)
Enjoy your factory-state phone
If you like my work, please consider: (or just hit the thanks button )
Thanks: Paul O'Brien for visionary, scotty2 and others who found the method to patch P7, Guhl and everyone else who has worked on the G2 root, gfree and wpthis, link to the source code, those have been released under GPL
Download link is in the end of the second post
[TOOL][VIDEO] One click Radio S-OFF, SimUnlock (Easy Root Guide)
FAQ:
Q: Why is this Radio Tool, does it flash a radio?
- From end user's view, it has nothing to do with radios, the name comes from the S-OFF technique this tool uses.
Q: I cannot find "System Info" in SHIP bootloader
- That is normal, just refer to the CID list when reverting to stock.
Q: How can I revert to full stock, I have ClockworkMod and/or ENG S-OFF too?
- Just follow the S-ON instructions.
Q: Can I use ENG S-OFF with this one? Which one first?
- Yes you can, it does not really matter, but I would do Radio S-OFF first.
Q: Does no fastboot stuff mean slow device startup (no HTC Fastboot)?
- No, I am talking about issuing commands to the bootloader through USB.
Q: Is this Radio S-OFF permanent, does it go away if I flash RUU/factory reset?
- It is permanent until you remove it using this tool.
Q: I already had ENG S-OFF and I ran the tool, how do I find out if it worked?
- If you used the first option, see bootloader system info. There should be CID-11111111.
Q: I have now ENG S-OFF and Radio S-OFF, how do I get to stock?
- Just follow the S-ON instructions, everything will be back to stock.
Q: I have 1.72 or higher system, what should I do??
- Downgrade using this guide, or flash Raidroid if you already have ENG S-OFF & ClockworkMod.
Q: I tried to flash a radio, but it says not allowed!
- You will also need ENG S-OFF to flash radios, because ENG S-OFF enables fastboot commands.
Q: I want to make my device stock, I cannot find the RUU but I have a backup of the stock rom.
- Follow these instructions.
Click to expand...
Click to collapse
Checking the device state:
- Go to the bootloader (turn fastboot off, turn off phone, hold vol- and power)
- If it says ACE PVT SHIP S-OFF in the first line, your device is Radio S-OFF
- If it says ACE PVT ENG S-OFF, you have ENG S-OFF, go to System info
- If system info CID is 11111111, your device is SuperCID
- And if you can verify either Radio S-OFF or SuperCID (and you did both), it worked fine and you have both of them
- You can check your original CID by going to radio tool folder with cmd and typing: "adb shell getprop ro.cid"
Click to expand...
Click to collapse
CID list:
- Unbranded: "HTC__001"
- O2: "O2___102"
- Orange: "ORANG001"
- German T-Mobile: "T-MOB101"
- Vodaphone UK: "VODAP001"
- More here
Click to expand...
Click to collapse
Troubleshooting:
- "Unknown error, probably connection"? See here, try with WiFi enabled.
- If that^ did not help, open a command window, go to the tool folder, and type: "adb shell" and "su". Then leave the window in the background, and run the tool again.
- "SD card failed"? When phone is connected to PC, check with some file manager that SD is accessible and works. Try another SD.
- Make sure you are rooted by downloading Terminal emulator from the market, write "su", '#' should appear.
- Check all the requirements. Twice. HTC Sync is mandatory!
- Keep your phone awake when you are running the tool, a superuser window might appear. You have to allow.
- Check your SD card, and tell us in the thread if a p7backup appeared on it.
- If it says Done and the CID does not change in ENG bootloader, you have most likely flashed too new radio.
Click to expand...
Click to collapse
Downloadcount:
v1: 1402 downloads
v2: 322 downloads
v2.1: 2396 downloads
Please do not re-upload the file anywhere.
WHOA! i just used your last tool to get s-off!
is this better? will it work over the previous one?
It will work over the S-OFF bootloader, I tested it myself
jkoljo said:
It will work over the S-OFF bootloader, I tested it myself
Click to expand...
Click to collapse
I can confirm that.
Hi,
how can i back to original?
My previous attempts have failed.
with friendly greet
starbase64
You will have to wait until Apache14 releases his kernel, which allows you to use command line to flash back the backup that is on your sdcard. The kernel works, so it is just a matter or time
Hi,
can not flash clockworkmod also.
with friendly greet
starbase64
So, this patches radio?
So if we run an oficial RUU or OTA, it overwrites the radio, thus restoring back to S-ON?
ttav said:
I can confirm that.
Click to expand...
Click to collapse
Yep, right on !
Eddie1506 said:
So, this patches radio?
So if we run an oficial RUU or OTA, it overwrites the radio, thus restoring back to S-ON?
Click to expand...
Click to collapse
Nope, will still be S-OFF, it will be 'ACE PVT SHIP S-OFF'
afrcom15 said:
Nope, will still be S-OFF, it will be 'ACE PVT SHIP S-OFF'
Click to expand...
Click to collapse
There is a partition 7 backup. Just restore that!
Sent from my Desire HD using XDA App
afrcom15 said:
Nope, will still be S-OFF, it will be 'ACE PVT SHIP S-OFF'
Click to expand...
Click to collapse
How's that possible?
Sorry I'm confused what this is. What difference to the other s-off tool ?
Sent from my Desire HD using XDA App
vimto25 said:
Sorry I'm confused what this is. What difference to the other s-off tool ?
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
yes tell us pls
This is permanent radio S-OFF as opposed to just ENG HBOOT S-OFF which can be wiped if you flash a standard ROM/RRU.
Flash this and you'll keep S-OFF no matter what you flash
JonnyFoxtrot said:
This is permanent radio S-OFF as opposed to just ENG HBOOT S-OFF which can be wiped if you flash a standard ROM/RRU.
Flash this and you'll keep S-OFF no matter what you flash
Click to expand...
Click to collapse
wow thanks
cool story!
THIS ROCKS!!!!!!!
If you use this one, you cannot use fastboot commands. If you like to play with your phone, then use the another one. This one is somewhat safer, however. In worst case scenario it is not possible to brick a device by using this tool, although to be honest, the other one has very very strict safety measures, too.
Jonny, the ENG bootloader will also survive a RUU if you do not have radio s-off.
jkoljo said:
If you use this one, you cannot use fastboot commands. If you like to play with your phone, then use the another one. This one is somewhat safer, however. In worst case scenario it is not possible to brick a device by using this tool, although to be honest, the other one has very very strict safety measures, too.
Jonny, the ENG bootloader will also survive a RUU if you do not have radio s-off.
Click to expand...
Click to collapse
so should we flash yes or no?
and why?
I have a backup with my stock ROM but when I go back to it everything still these such as root,s-off,Rom manager . So if I downloaded a clean stock ROM it will take everything off like it was when I first started phone up? And if I use this tool I can use stock ROM and my device is always s-off no matter what I do? Ifso how would you take s-off if needed for warranty issue. Thanks
Sent from my Desire HD using XDA App
DO NOT FLASH A NEW RUU OR OFFICIAL ROM IMAGE UNLESS YOU *REALLY* KNOW WHAT YOU ARE DOING !
The title says it all!
Doktaphex said:
As the title suggests, this is warning against flashing the new RUU_Ace_HTC_WWE_1.72.405.3_R_Radio_12.28e.60.140f_ 26.04.02.17_M2_release. It contains a new version of HBoot that breaks root and standard S-OFF! Please refer to these threads for more info:
http://forum.xda-developers.com/showthread.php?t=879375
http://forum.xda-developers.com/showthread.php?t=875099
You may be safe if you have full radio S-OFF and SuperCID but this is unconfirmed, and I would steer well clear until the DEVs have cracked open this latest HBoot.
Click to expand...
Click to collapse
Confirmed:
Only if you have full radio S-OFF you can 'downgrade' to 1.32xxxxxx and root
Yes, I can confirm that, too. You have to have Super-CID (Radio S-OFF) to downgrade. Rooting is not possible in this new one. Yet.
Can please someone explain me what's the real difference between ENG S OFF But CID 11111 and SHIP S OFF and CID HTC....?
ENG S-OFF: It is engineering bootloader S-OFF (may include Radio S-OFF). Allows custom bootloader commands, for example radio flashing, also allows to install custom roms.
SHIP S-OFF: Radio S-OFF, does not allow radio flashing, but allows ClockworkMod flashing. Usually comes together with SuperCID.
CID 11111111: Super-CID, Super Carrier ID, allows you to downgrade, and flash really anything to the phone without the phone saying "no thanks".
CID HTC__xxx: HTC Carrier ID, does not allow downgrading via RUU, but you can still flash through ClockworkMod if you are S-OFF.
Thank you very much for this answer..I ask because i cannot find this information somewhere in one post!
I am with ENG S-OFF and CID 11111111
So i can flash the new RUU and i am able to revert back to 1.32xxxxxx and root again.Correct?
Looks like its been rooted.
http://forum.xda-developers.com/showpost.php?p=9936625&postcount=91
At least it has if you flash just the system.img
Yeah but it needs clockworkmod, which goes away if people use the actual RUU. Also flashing system.img does not replace the bootloader, so S-OFF stays in fine (also hboot S-OFF).
How can you tell what your CID is?
madindehead said:
How can you tell what your CID is?
Click to expand...
Click to collapse
Bootloader > Fastboot > System Info (or something like that)
If you are SuperCID then it is 11111111 if not, then it begins with HTC_xxxx
looks like also this RUU_Ace_Orange_ES_1.75.75.2_Radio_12.28e.60.140f_2 6.04.02.17_M2_release also seems to stop you gaining root and fix's patched Hboot as someone saying he flashed the rom and can't gain root.
joners said:
Looks like its been rooted.
http://forum.xda-developers.com/showpost.php?p=9936625&postcount=91
At least it has if you flash just the system.img
Click to expand...
Click to collapse
can you tell how to extract the system.img from rom?
all i get is a [0] file. dont know what to do with it.
[HOW TO SAFELY FLASH THE NEW ROM AND BE ABLE TO REVERT BACK]
Currently, the new ROM (1.72.405.3) has a new HBOOT (so you can't install ENG HBOOT S-OFF) and is difficult to root (not as simple as it is with previous ROMs). However, it also has a better radio, and a faster ROM with various bugfixes. This ROM is also Android Froyo v2.21. If you want to try out the new ROM, whilst maintaining the ability to 'revert' back to your older, hackable state then follow the below instructions carefully. Also, do not worry about extracting system.img files and whatnot.
*It is recommended to do a NANDROID BACKUP first
*All RUUs can be obtained from www.xdafil.es/DesireHD/RUU/
*If you don't do steps 1-3 properly and flash the new ROM, you will not be able to revert back
*Radio S-OFF and SuperCID can be obtained by following instructions in this thread: http://forum.xda-developers.com/showthread.php?t=857537
*Tutorial for flashing RUUs (needed for steps 4 & 8): http://forum.xda-developers.com/showthread.php?t=841890
1. Install Radio S-OFF (NOT ENG HBOOT S-OFF) and SuperCID
2. Go to bootloader, then System Info. (If System Info is not there, but you have SHIP S-OFF skip step 3 and proceed to step 4)
3. Make sure CID is 11111111 *AND* the bootloader shows S-OFF. If not, repeat step 1
4. You can now flash the new ROM (1.72.405.3)
5. This will remove ENG HBOOT (if you had it) and ClockworkMod
6. If you did steps 1-3 correctly, your Desire HD should still be S-OFF. Go to bootloader and check. If not, you did not do steps 1-3 correctly and will have to wait for the new HBOOT to be cracked.
When you are done with the new ROM and want to go back, follow the instructions below:
7. Download the HTC RUU 1.32.405.6 of your choice (Since you are SuperCID you can flash any RUU)
8. Flash it to your Desire HD
9. Root your ROM using Visionary, and install ROM Manager and flash ClockworkMod. You can optionally install ENG HBOOT S-OFF now if you like.
If you made a NANDROID Backup, you can restore this now from ClockworkMod
joners said:
Looks like its been rooted.
http://forum.xda-developers.com/showpost.php?p=9936625&postcount=91
At least it has if you flash just the system.img
Click to expand...
Click to collapse
I can't get this to work myself, unfortunately.
joners said:
Looks like its been rooted.
http://forum.xda-developers.com/showpost.php?p=9936625&postcount=91
At least it has if you flash just the system.img
Click to expand...
Click to collapse
I have this working. The supplied .zip file does not include Superuser.apk. After following the instructions and then installing Superuser from the market I now have root on this rom.
Look forward to testing it over the next couple of days while I lay in hope of some custom roms based off this version.
EDIT: Superuser keeps force closing
My bootloader says
ACE PVT ENG S-OFF
HBOOT-0.85 2007 (PD9810000)
and system info says
CID-11111111
Am I good to go or shall I do something else?
Thank you for sharing info.
doh!
being used to the days of winmo I flashed this rom over my cyanogen taking a backup first.
Now I can't revert back to the old stock rom, any way of doing this (easily ish)?
Hi, I'm ENG S-Off but my CID is not 1111111, what's the safest way to do the Super-CID?
I'm stucked abroad using a **** phone cos I can't use another sim in my DHD
Sent from my Desire HD using Tapatalk on Revolution 1. 92
ninja.rogue said:
My bootloader says
ACE PVT ENG S-OFF
HBOOT-0.85 2007 (PD9810000)
and system info says
CID-11111111
Am I good to go or shall I do something else?
Thank you for sharing info.
Click to expand...
Click to collapse
Also on the same boat...
Anyone??
ninja.rogue said:
My bootloader says
ACE PVT ENG S-OFF
HBOOT-0.85 2007 (PD9810000)
and system info says
CID-11111111
Am I good to go or shall I do something else?
Thank you for sharing info.
Click to expand...
Click to collapse
looks like you are, you have superCID.
So, i have updated my phone ota by htc so that now i have hboot 1.29 and ics installed with sense 3.6
I have no wifi/bluetooth anymore (MAC adres missing and bluetooth ID missing), so i was thinking in installing a custom rom/kernel whatever necessary to get my phone working properly again.
I think i read all the big guides and tutorials to be found in the sensation forum here. :good:
But that made me even more insecure.
What is it with the tools like the super utility from kgs1992, or the all-in-one toolkit.
i find threads about S-off, Super CID root, dev unlock and so on.
so, maybe someone here can give me one clear answer what i need to do in what order to exactly get my phone in a custom rom (let's say elegancia sense 4.1 themed?)
question one, what should i do first and what next?
first unlock over HTC dev (this i also a factory reset, isn't it?)
S-off (wire trick) (there are enough video's in youtube i guess)
then flash/install recovery (which one?)
Is this all correct?
at this point, am i rooted? and if not what comes next?
So what then? customrom? (how, what)? perm root? super cid? what do i need in what order?
in more than one place i read about rom as a file with the extension .img. But the elegancia download is a zip file.
what about the super tool, there they talk about a kernel, not a rom to flash.
And what about radio, is that a total different game? or is flashing a custom rom doing the interface, the kernel AND the radio in one go?
I hope i don't ask to much from anyone. I know there is a LOT of tutorials to be found already, but they are not all the same and often written to cover all versions and stuff. I can't see through all these things and hope to get some confidence by asking for my specific situation. :angel:
I'll try to explain stuff briefly ..hoping that it will solve other confusions too
well here it goes ...
1. First...Sensation by default is completely locked device (internal memory is locked )..so to either root the phone or run a custom rom ..you need to first unlock it.
2. Remember rooting the device and running custom rom are different
rooting: by doing this you will have complete control of the rom you are running be it stock or custom rom (its like administrative privileges in WIndows 7)
custom rom: this is changing the rom itself (like changing the OS From windows 7 to linux on PC )...and all custom roms comes pre rooted ..so once you flash/install a custom rom no need to root it again
3. Now The unlock procedure can be done in two different ways
3.1. HTC-DEV unlock : a process provided by HTC itself to support rooting of devices and running custom roms
(its a semi unlock...confused? will explain the difference later ..read on )
3.2. S-OFF: it means Security-off ..which implies unlocking the device completely (complete internal memory is unlocked)
S-OFF in turn has couple of ways to achieve it
3.2.1 S-OFF using revolutionary...It will only work on old bootloaders ..i.e. upto 1.18 HBOOT/BOOTLOADER (to put it simply it's for the sensation devices on gingerbread version of Android I.e. 2.3 version)
3.2.2 S-OFF using juopunutbear ..it will unlock even the current hboots (1.27/1.29 etc etc) (this method is primarily for sensation devices on ICS version of Android I.e. 4.0)
This juopunutbear inturn has two more ways
3.2.2.1. using juopunutbear after doing HTC-DEV unlock ..this process wipes the phone (because of HTC-DEV unlock) but the wire-trick (most imp step) is easier
(why juopunutbear ..if you already unlocked your device using HTC-DEV ? ..explained later ..read on )
3.2.2.2. using juopunutbear without HTC-DEV unlock required ..this process is harder at wire-trick part (comparatively)
4. Difference between HTC-DEV unlock and S-OFF:
to explain this ..I'll try to give a pictorial representation of Sensation Device
Sensation as a whole has different partitions (or blocks ) ..so the whole device can be divided like this
Recovery --------firmware--------ROM (or OS)
Recovery: its a recovery mode ..the name says it all ..we change/tweak/modify rom from here ..(remember only ROM ..not firmware)
eg: stock recovery, 4EXT recovery, CWM recovery, TWRP recovery etc etc (the later 3 are custom recoveries for flashing
custom roms
Firmware: all the lowest level stuff comes here ...typically bootloader, radio etc etc
we flash/install Recovery and stock ROMS from bootloader.
stock roms are ..called RUU's (Rom Update Utility) and are provided by HTC ...they are in .exe format and the actual stock ROMS are extracted from the RUU which will be in "img" format
ROMS: the actual custom/stock rom comes here ..this typically has three partitions/areas
1. data partition: all your apps/app data and all the phone data you eneter goes here
when you factory reset your device this partition is erased so that phone gets resetted to factory state
2. system partition: all the system apps and system stuff will lie here
(in case of carrier locked Sensation ..like T-Mobile all the T-Mobile junk apps reside here)
this area is locked in general ..rooting typically means getting this region unlocked ..so that you can change
anything in the rom
3. boot partition: your kernel lies here along with other stuff (this region is responsible for the phone to boot) Now it should be obvious that Radio aka a part of Firmware wont be there in a custom ROM and typical custom roms comes in zip format
Now HTC-DEV process only unlocks Recovery and ROM partitions (which are more than enough for installing custom roms or rooting)
This way of unlocking is safer as tinkering with Firmware is not really needed and if mistakes were made in changing the firmware the device can get bricked permanently.
but SOFF provides unlock on every partition of the Device ..thus complete unlock..thus more ease also more risks
Now the big question -> why SOFF needed if HTC-DEV is safer ?
Reasons:
1. Firmware and Rom partitions are dependent ..to be more clear
Ginger Bread (GB) firmware (1.17 firmware) ..supports only GB roms ...ICS or above roms wont boot
and
ICS firmware(3.32/3.33 firmware) ...supports only ICS and above ROMS (Jelly Bean(JB) roms are supported too )
thus if you do HTC-DEV unlock when on Ginger Bread you can only boot GB custom roms as you can't change/modify firmware over HTC-DEV unlock.
if you did HTC-DEV unlock over ICS rom..you are good to go with all the latest ICS/JB custom roms
2. Flashing/installing ROM from custom recovery with HTC-DEV unlock...requires an extra step...and if that extra step is not done ..phone wont boot (literally around 90% threads in Q&A section are about this problem as people didn't knew about the extra step )
3. some people require a change in radio ..to improve phone/data signal which isn't possible if you did just HTC-DEV unlock (as radio is part of firmware )
Another question that might come to your mind... What is the advantage of rooting the device on stock rom ..before installing a custom rom?
Answer:
people might say ..why root the device before installing custom rom when the custom rom comes pre-rooted
well here is the answer ..."to backup your phone and its data"
Remember this when installing a custom rom ..you need to wipe the phone(all the internal memory ..sdcard wiping is not needed) ..thus you will lose all data
but before wiping if you root the phone..you can backup all the user apps and its data ..also call logs, messages/MMS, wifi access points, bluetooth pairings. contatcs etc etc to your sdcard using a root app (an app which requires root permission to work ) ...and once you install the custom rom ..you can restore all the backup
..(makes things easier ..isn't it ? )
5. Miscellaneous terms:
Supercid:
CID -> carrier identification ..its a 8 characterterm used in the device to identify the proper Firmware or stock rom (RUU ..remember?)
as sensation is a global device ..there are different variants of firmware and stock Roms which are uniquely identified by this cid ..
eg: T-Mobile US locked sensation has CID: T-MOBO10, europe unbranded sensation has cid HTC__001 etc etc
so when flashing firmware/stock rom ..you need to find the proper one based on your phone cid ....
but if you do a supercid (i.e changing CID to 11111111) ..you can flash any firmware/stock rom (in form of RUU )
supercid can only be done ..over SOFF and wont/might not work over HTC-DEV unlock
also now there are Universal Firmwares ..aka Firmwares which can be flashed over ( SOFF) device having any CID ..thus Supercid is now kinda obsolete
hoping that things are clear now ..
few threads that are much detailed
1. "flashing roms while SON" by askickar in sensation general section ...(which explains flashing rom with just HTC-DEV unlock together with the extra step needed (remember ?) )..thread here
2. SOFF process threads ...for soff with HTC-DEV unlock ..thread here
3. SOFF without HTC-DEV unlock ...look in my signature for the thread
4. General way of flashing ROMS with Firmware flashing ..with ARHD Rom as reference...by joaquinf ..thread here
Happy flashing
Damn! now that is an explanation! Really really thanks for that! :victory:
I learned to always give feedback in your own words to check if you understood everything correctly.
If it is only for changing the 'interface'/running system part of the phone (that's called a ROM ), i can do with devunlock and flash a recovery, then flash a custom rom that is compatible for my version
(android 4.0.3 ICS/htc 3.6 sofware build 3.33.401.154/hboot 1.2900/kernel 3.0.16)
so any rom that has version 3.33 i can use it.
i don't need S-off per sé. (correct?)
doing above is already rooting, because i get (partially) access (or full access when S-off) to otherwise locked part of the system.
i have to flash a recovery to get influence when installing a new rom. so that means i NEED to flash a recovery to the phone before i flash a rom?
in short for my situation:
1. Do devunlock.
2. flash a recovery.
3. flash a custom rom to my phones specs as above.
so before or after step 1 i CAN do S-off using juopunutbear and the wiretrick
The easiest way to do all above is using the 'sensation all in one kit'
super CID i don't need, perm root is also optionally what can do as in the super tool kit is offered
But my fear is that the mac adres/wifi and bluetooth problems are from the 'lower level' of the system called firmware/kernel. (correct? or will flashing any custom rom already help me with solving my hardware part of the problems on the phone? besides giving me a much newer and cleaner installation with lot's of nice things, of course)
Main question still is? will a custom rom solve my wifi and bluetooth problems, or do i need more than above?
and ps, where does superswipe fit in all this? i read it's needed for instance at some versions of elegancia.
WOW Ganesh,what are you on?
@klimpetje
Wifi and bluetooth are on the "Radio" level.
Use an app from the market called "Getril"
This will show if you have the best radio/ril combination for your area.
Custom ROM MAY solve this problem.
Do not use "Superwipe" scripts.
Install 4 EXT recovery,and use the "Format all partitions (except sd card)"
doing above is already rooting, because i get (partially) access (or full access when S-off) to otherwise locked part of the system.
Click to expand...
Click to collapse
this ..is partially true ...once you do SOFF/HTC-DEV unlock ..the system partition can be unlocked ..and to actually make it unlock ..you need root
so that means i NEED to flash a recovery to the phone before i flash a rom?
Click to expand...
Click to collapse
yes
But my fear is that the mac adres/wifi and bluetooth problems are from the 'lower level' of the system called firmware/kernel. (correct? or will flashing any custom rom already help me with solving my hardware part of the problems on the phone? besides giving me a much newer and cleaner installation with lot's of nice things, of course)
Click to expand...
Click to collapse
the wifi and bluetooth modules are part of the ROM and drivers are part of radio ..so flashing CUSTOM ROM might/might not solve the issue
the chances of drivers getting corrupted are less ..as those areas are locked even when the OTA was applied...so custom ROM might solve your issue
superwipe -->as malybru said "not needed "..use the inbuilt wipe options present in recovery (this is done ..before flashing custom rom )
@malybru
WOW Ganesh,what are you on?
Click to expand...
Click to collapse
too much routine work/port im doing ...bored and came across this post
Nice guide ganeshp!
@ganeshp
Wow, that was really a nice and quick, yet thorough explanation! Cudos for being so helpful!
I was just wondering, is there any good reason to upgrade firmware after having S-OFF, custom recovery and flashed a working JB ROM?
Actually, I don't even know which firmware I have, but my last stock ROM before going custom was ICS.
My bootloader says:
Code:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34
I can't really figure out which firmware it is - wasn't it supposed to be either 3.32 or 3.33?
PS: I'm currently on Paranoid v.21.
tachylatus said:
@ganeshp
Wow, that was really a nice and quick, yet thorough explanation! Cudos for being so helpful!
I was just wondering, is there any good reason to upgrade firmware after having S-OFF, custom recovery and flashed a working JB ROM?
Actually, I don't even know which firmware I have, but my last stock ROM before going custom was ICS.
My bootloader says:
Code:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34
I can't really figure out which firmware it is - wasn't it supposed to be either 3.32 or 3.33?
PS: I'm currently on Paranoid v.21.
Click to expand...
Click to collapse
based on the radio ..you have i can safely say that the firmware is 3.32
but to confirm it ..the output of this command gives you the firmware
(the command should be typed in PC ..by opening the terminal where the adb/fastboot files are there ...with phone connected to PC from bootloader (phone says FASTBOOT USB if connected properly ))
fastboot getvar version-main
tachylatus said:
@ganeshp
Wow, that was really a nice and quick, yet thorough explanation! Cudos for being so helpful!
I was just wondering, is there any good reason to upgrade firmware after having S-OFF, custom recovery and flashed a working JB ROM?
Actually, I don't even know which firmware I have, but my last stock ROM before going custom was ICS.
My bootloader says:
Code:
=JuopunutBear=
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.27.1111
RADIO-11.22.3504.07_M
OpenADSP-v02.6.0.2226.00.0131
eMMC-boot
Jan 13 2012, 17:33:34
I can't really figure out which firmware it is - wasn't it supposed to be either 3.32 or 3.33?
PS: I'm currently on Paranoid v.21.
Click to expand...
Click to collapse
the only difference between 3.32fw and 3.33fw is radio upgrade
but you can check your fw version by doing this:
from bootloader connect your device to pc
open a command prompt and do
fastboot getvar version-main
then it will show you your firmware version
Thanks guys
My version is apparently 3.24.401.1.
I wonder if an upgrade will improve stability/performance.
Would you recommend following this guide, or should I just stay with the current version?
*edit*
I think I might give this a shot
Firmware information thread
The guy says something about most people reporting their devices to become noticeably faster after flashing.
tachylatus said:
Thanks guys
My version is apparently 3.24.401.1.
I wonder if an upgrade will improve stability/performance.
Would you recommend following this guide, or should I just stay with the current version?
*edit*
I think I might give this a shot
Firmware information thread
The guy says something about most people reporting their devices to become noticeably faster after flashing.
Click to expand...
Click to collapse
the only difference between 3.32fw and 3.33fw is radio ugrade
but in order to flash the latest ARHD rom probably requires 3.32 or 3.33(not so sure maybe it boots with 3.24 otherwise flash a higher fw version)
Great succes! :good:
I installed universal firmware 3.33.
Wouldn't boot ROM, so I used recovery to wipe cache, dalvik and battery stats, then reflash Paranoid v.21.
Works like a charm! Lightning fast
Sent from my HTC Sensation using xda app-developers app
ganeshp said:
I'll try to explain stuff briefly ..hoping that it will solve other confusions too
well here it goes ...
Click to expand...
Click to collapse
Really good stuff Ganeshp, wish I'd come across this earlier it's just what one needs when you enter this world fun trying to piece together all the terms being banded around. A huge time saver to have the 'glossary' and explanations in one place allowing the research time to go to the meat of the matter rather than sorting out the confusion that naturally occurs when starting up.
ganeshp said:
I'll try to explain stuff briefly ..hoping that it will solve other confusions too
well here it goes ...
Click to expand...
Click to collapse
Awesome Ganeshp, I am also new to this forum and this clears pretty much everything! I love how this Sensation forum is soo helpfull, thanks guys Im glad I bought my Sensation
I have a couple questions.
I am on the 1.16 hboot with cid111111 and s-off unlocked tampered. twrp and maximus rom.
I finally did super cid and s-off on my one-s. Shortly after I recieved a notification that ota update 3.16.401.8 (612.27 mb) was available.
I was wondering if it would even work if i attempted to update. or would i have to update manually. Or would it brick it.
The main reason i would want to update is because the JB Sense roms just dont seem to run smoothly on my phone.
I was thinking this would update everything so the custom roms run smoother.
And Should i even update my hboot. does it make a difference.
I would usually be against it(ive had to downgrade other phones before).
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
impostle said:
Never take an OTA if you are on a custom rom with a custom recovery. Especially if you have SuperCID, unless you want a paperweight. If you want that OTA, you need to get you original CID, flash stock recovery, relock bootloader, then flash an RUU for your carrier.
Click to expand...
Click to collapse
Ok. ill look into that. sounds easy enough. last time i tried to update, i couldnt because of my cid. now i guess since there is an official t-mob i can do it?
You cant flash an ruu with super cid?
Oh and also, Once i update my hboot am i able to install the older ICS roms like maximus. thats just the most stable one i have found for my particular phone.
One more. Will i be able to restore my cid with s-off
ruu update
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
myphonesbetter said:
i relocked, then changed my cid to HTC__001
I triedto update via ruu exe file. but i got an error 155.
Im not sure how to update via the zip of the ruu. if its possible.
Also cant find any instruction or files for the original recovery.
I will try to install ota. hopefully i dont end up with a new frisbee.
If i were to extract the framwork.zip frim the ruu zip then install it via fastboot. would that give me the latest hboot. then maybe i could install the updates.
Click to expand...
Click to collapse
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
impostle said:
If you update your Hboot that kind makes it more difficult to flash custom roms. You should just find a nice custom jellybean rom, there are some good ones out there.
Click to expand...
Click to collapse
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
real187 said:
updating your hboot makes no significant difference (its a myth that its more difficult to flash custom roms on a later hboot).
im on latest hboot and can flash all things i want.
and if your device is S-off dont bother to relock your device/reinstall stock recovery. It will get overwritten anyways.
only thing important is to change the cid. you can always install a older hboot if s-off
have you tried the ruu.exe while in fastboot-usb?
Click to expand...
Click to collapse
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
EDIT: Thats what I get for watching too many threads, I miss stuff.
impostle said:
When I said it was more difficult I meant it was more work, having to flash the boot.img separately. If you are on a lower Hboot you don't have to do that. Also if you are going to suggest he do S-Off you should at least give him a warning about some of the issues people have ran into after doing it.
Click to expand...
Click to collapse
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
real187 said:
he is already S-off. (see first post)
but anyways, if you dont do research before you do something, and it fuks up your device, its still gonna be your own fault.
what issues your talking about?
Click to expand...
Click to collapse
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
impostle said:
I saw a thread about people losing 3g/4g data after an S-Off.
With S-Off you are made in the shade, you can downgrade your Hboot just by running the appropriate RUU. But you have to change your CID back to what is was before you try to flash the RUU.
Click to expand...
Click to collapse
I have seen the tread. But im scepitical, because if it really was only because of the s-off more people should have it. Might be hardware related.
Eh you do not have tot change back your Cid to original (if its a branded Cid the ruu still wont run), just a valid HTC Cid.
Verstuurd van mijn One S met Tapatalk
He could flash from recovery or fastboot flash any hboot he wants with s-off. No RUU needed for downgrade or upgrade. That's only needed to go back to stock for warranty purposes.
@myphonesbetter
If you want the red warning text overlay to be gone as well choose any of the files here and flash it within recovery. S-Off needed to do so!
To remove ***Tampered*** as well download hboot 1.140004. You will need to come from a lower hboot version so if you're already on >1.140004 flash one <1.140004 first.
--- edit ---
You can lock/unlock your phone as well by flashing. Read more in [how to] reset your lock status flag. Also it's in the Droid DNA forums it's valid for One S. Remember: You need s-off for this to work.
--- and one more ---
You can change your CID pretty simple on rootet devices. Just enter fastboot mode and type:
'fastboot oem writecid HTC__001'
Reboot bootloader then. You can find a collection of HTC ONE S CID's here
^^^^^Very helpful post. thank you. I wouldve never found that.
When you run the ruu .exe, do you have to be in fastboot or in android? The install app told me just to turn the phone on so i figured it would automatically go into bootloader. but it did nothing at all to my phone and gave me an error 115.
When i tried the ota it tells me that I am runnning an altrered OS and i will have to install it a different way.
Sorry for the easy questions. but i just cant seem to find any threads that say how to. I found the ruu and a zip of the ruu. but not how to install it.
The best sense rom has instructions on flashing a newer hboot. .but i want to install a completely stock rom.
myphonesbetter said:
^^^^^Very helpful post. thank you. I wouldve never found that.
.
Click to expand...
Click to collapse
guess you run out of thanks, no?
Never even noticed the thanks meter. I have more of a direct thank you approach.
I tried to flash the ruu .exe in fastboot. and it actually rebooted into the black htc screen, so i figure thats the way to do it.
Unfortunately I got another error. image error (159) use the correct rom and flash again.
I am attempting to flash 3.16.401.8 onto hboot 1.16 (relocked) i am s-off and i changed my cid to HTC__001 via fastboot.
Is there another way. or can i flash the zip in twrp or cwm? Again i just want an oem jelly bean with the proper hboot and radio and everything that the OTA would change. so i can be up to date before i move on to the JB roms.
Ive tried all of the custom ones, and the wifi cuts in and out. i used the wifi partition fix. and i flashed the latest radio. nothing helped for more than a few hours.
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
ultimul said:
don't know what to say; normally you can flash whatever rom you want without problems;
guess 99% of users here did it.
however I can not understand what do you want to be full stock? warranty problems?
Click to expand...
Click to collapse
Yah thats usually how it works for me. if it works for 99% of people with one step. ill have to do it manually with 20 steps. I guess its made me learn alot about adb and fastboot. I could never get adb to work untill i upgraded to windows 7 recently. until then i had to exract everything to my sdcard via terminal emulator and then drag it to my computer form the card and modify things. but ive been forced to learn quite a bit.
Its weird. I bought my phone off of craigslist from someone who had no idea how to root. But when i opened it into hboot it said Tampered and locked. with no signs of ever being unlocked. completely stock rom and no red warning text on the splash screen.
The reason i want to be stock it so i know all the correct partitions and everything are set up right. (that part i dont understand yet).
I know that a normal system wipe in twrp or cwm doesnt wipe everything. If i wipe and install the same rom i am using(just to clear it up and start over) it doesnt even wipe the app data. (at least on my phone)
Im thinking that its because i am installing a euro rom with a HTC__001 cid and mine was originally TMUS T-MOB010 .
one thing i noticed also is that windows could not verify either of the ruus i downloaded from shppied roms
How do i flash the ruu.zip that i downloaded? Do i need to rename it update.zip like the older phones? Its been a while.
Ok so i know im pretty much helping myself here but i hate when i come across threads with no conclusion.
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Any help would be appreciated.
Ahh, things go on here! Nice! :laugh:
It's not quite clear if the RUU is the right one on this phone as many people report problems... So let's go OTA.
To flash the 3.16 OTA update your hboot needs to be < 2.15, your recovery needs to be the HTC stock one , your device needs to be relocked (not totally shure as mine wasn't at that time and it worked, but please remember that) and you need to have HTC stock system/ and stock data/ (ICS) files on your phone (you'll have to unroot as well, if rootet), as the OTA seems to check if certain files are present before working.
All that is quite a pain in the ass, isn't it?! So do one the following:
- Just make shure your bootloader version is lower 2.15, else flash a lower one.
- Click here and you'll have access to one of my google drive folders.
- Download the 2.31 zip. Unpack and copy these nandroid backup files into the appropriate TWRP folder on your phone, reboot into recovery and restore. Once done, you'll be able to flash the 3.16 OTA update after reboot. Remember to change CID before if you're on 11111111.
- Or download the 3.16 zip, unpack and restore. You'll have stock htc sense JB without the OTA. You don't even need to downgrade your bootloader in case. CID doesn't matter here.
- To root simply download SU_Bbox file and flash in recovery.
Important: With the JB update HTC invented disk write protection by default. This simply means that files deleted within stock sense JB will be back after rebooting the phone, also root was granted and working (still grats to htc for this one!!!). Check out for elemental x kernel at this point, as flar2 is the one offering additional modules for the stock kernel working around this. So you can be on stock JB as close as possible with write protection disabled.
--- edit ---
I nearly forgot: If you're experiencing WiFi troubles afterwards search for flashing wifi partitions.
--- and one more ---
myphonesbetter said:
I was able to succesfully update with the t-mob 2.35 ruu .exe thats on shipped roms .com so i know its not a problem with my computer.
still on hboot1.14 (thought i was on 1.16).
I changed my cid back to t-mob010.
Im just not sure why i cant update with the htc__001 with the 3.16 update.
Click to expand...
Click to collapse
Cause you're on 2.35 US. You need to be on 2.31 EU before, because 3.16 is EU and there is still no JB update to 2.35 US. 3.16 OTA will work with htc__001 (htc worldwide).
The OTA determined my OS was modified.
I could not restore the folder i took directly out of the zip.
There was a folder inside the folder that contained the same files. I was able to flash this.
My hboot is still at 1.14 my cid is not htc--001 relocked. the update was 650 mb of which i could not use wifi for becauese it just said error.
so 650 mb through tmobile. only took a few minutes but used almoast half of my months dl limit.
IDK. i found instructions on how to update the hboot in best sense roms thread. i will try that.
Edit: the restore for 3.16 worked in twrp. shouldve tried that first.
I may still update my hboot. I cant really find any instructions. Apparently the search just finds every thread and lists it.
If you are on the latest TWRP 2.4.3.0 go back to 2.4.1.0 (the latest one seems to have restore problems).
The folder contained in the zip needs to be copied to /TWRP/BACKUPS/HT23whatever/
You should be able to restore then.
--- edit
hehe, ok then.
You can flash any of these hboots from within TWRP. Up or down, it doesn't matter - you're s-off.
---------- Post added at 10:43 AM ---------- Previous post was at 10:32 AM ----------
CID should be HTC__001 not htc--001. Maybe a typo.
Hi,
I'm totally new in the rooting/customROM business. I want to flash the Desire XS version 1.1 on my desire s, since the 2.3.5 is a little old now...
I just chose this ROM, because it looked good, no idea... good choice?
I tried to avoid having to ask questions, but I reached a point where I can't get the Inforamtions just from reading anymore and am scared of causing irreperable damage to my phone.
I wanted to ask in the Desire XS version 1.1 directly, but wasn't allowed to.
Well I followed this guide:
http://forum.xda-developers.com/showthread.php?t=1525100
and unlocked my bootloader via HTCdev. I'm still on HBOOT 2.00.0002 and S-On
After having done this, I want FIRST do a full recovery of my system, to be able to go back to 2.3.5 if the new ROM doesn't work. Or is this not necessary?
Furthermore I don't want Reaper v2.1, but Desire XS version 1.1. So I downloaded this and copied on the SD. Now, I "have to copy boot.img into the folder where I have adb and fastboot ". But where can I find boot.img within the ROM? I found it 2 times in \Kernel\b2b and \Kernel\patched. Is one of them the right one?!
Also in the Desire XS version 1.1 thread it is says "I recommend that all users be on radio 20.76.30.0835U_3831.19.00.110 before installing this rom"
But I couldn't find any information to switch to this specific radio (just others).
Some information on my phone:
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2. 00. 0002
RADIO-3822.10.08.04_M
eMMC-boot
Somewhere in the Desire XS-Thread I found this:
Quote:
Originally Posted by roman_kaczynski View Post
Can i use this rom with hboot 2.02.0002 S-ON and radio 3831.19.00.110?
Yes, you have the last radio.
You are s-on, flash boot.img whit fastboot.
Click to expand...
Click to collapse
I'm sorry for opening a new thread, for the many questions and the long explanation, but I tried to make my problem as clear as possible and wasn't allowed to post in the developer's thread about radio and boot.img...
Thanks for the help!
While flashing the rom you have a choice of 2 kernels (b2b and patched). Use the boot.img of the kernel you will be choosing.
If you want to upgrade the radio (while still s-on) you need to relock your bootloader, flash the Ics RUU, unlock your bootloader again. (some users reported camera issues on desire xs with an older radio version, you could try it first with your current radio).
teadrinker said:
While flashing the rom you have a choice of 2 kernels (b2b and patched). Use the boot.img of the kernel you will be choosing.
If you want to upgrade the radio (while still s-on) you need to relock your bootloader, flash the Ics RUU, unlock your bootloader again. (some users reported camera issues on desire xs with an older radio version, you could try it first with your current radio).
Click to expand...
Click to collapse
Thanks. I guess I'll take the b2b kernel then, since it's the one mentioned in the description. or is the other better?!
Also when flashed is there a way back to the version I have now?! (since you didn't answer my question regarding a recovery of the current system) Can I afterwards just recover via a RUU?!
I'm still scared of ending up with a broken phone
You can make a backup in recovery before flashing, just remember to flash the boot.img from your backup as well if you restore it.
The main difference is, the patched kernel supports overclocking and undervolting, the b2b doesn't.
but how can I do a recovery? My phone is not rooted yet and S-Off (it's just unlocked), is it possible to create a recovery like that?
edit: I found my exact system (2.10.166.3) on htcdev, I guess in the worst case I'll be able to get it back from there. I hope just hope for the best! =)
eggerph said:
but how can I do a recovery? My phone is not rooted yet and S-Off (it's just unlocked), is it possible to create a recovery like that?
edit: I found my exact system (2.10.166.3) on htcdev, I guess in the worst case I'll be able to get it back from there. I hope just hope for the best! =)
Click to expand...
Click to collapse
You have to flash the recovery.img in fastboot. (fastboot flash recovery recovery.img)
Them you can choose recovery from the bootloader.
it worked all good. New system is stable and fluent! lot's of fun, thanks!