[Q] Flashing Desire XS version 1.1, S-On - HTC Desire S

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!

Related

[GUIDE] Get back to HTC Stock ROM (from anything) [UNDER CONSTRUCTION]

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.

[WARNING] Do not flash a new official RUU/ROM/OTA if you have root and/or S-OFF

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.

[Q] A couple of questions concerning new Desire S

hey there,
bought my gf a desire s to christmas. i, as a sensation user at the moment am very comfortable with development. flashing, adb, fastboot and things like that are working flawless.
as i don't have so much time to read atm, i have some questions concerning the way to set the desire s up. it was shipped with 1.47 rom, t-mobile branded, sense 2.1, android 2.3.1 and hboot 0.98.0002
i want to flash this rom: endymion sense v3.1 (android 2.3.5, sense 3.5)
i already achieved s-off with revolutionary, hboot is now 6.98.1002 with radio 3805.06.02.03_M. 4ext recovery 2.2.7RC5 is installed as well.
now i saw, that there is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe availble. i also read in the forum, that this ota brings some parts for firmware, which are not flashed with a custom rom.
so would you recommend to flash this ruu first? wouldn't i lose s-off then? would i be abled to achieve s-off again after flashing this? also, for my sensation i would have to supercid first - i didn't read about this here in the forums.
what i would want to do:
1. flash RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe
2. run revolutionary again
3. flash custom recovery
4. flash endymion v3.1
would it be possible this way? or would you recommend any other way to me? i want to have all firmware parts as up to date as possible before i flash the custom rom.
smint86 said:
hey there,
bought my gf a desire s to christmas. i, as a sensation user at the moment am very comfortable with development. flashing, adb, fastboot and things like that are working flawless.
as i don't have so much time to read atm, i have some questions concerning the way to set the desire s up. it was shipped with 1.47 rom, t-mobile branded, sense 2.1, android 2.3.1 and hboot 0.98.0002
i want to flash this rom: endymion sense v3.1 (android 2.3.5, sense 3.5)
i already achieved s-off with revolutionary, hboot is now 6.98.1002 with radio 3805.06.02.03_M. 4ext recovery 2.2.7RC5 is installed as well.
now i saw, that there is RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe availble. i also read in the forum, that this ota brings some parts for firmware, which are not flashed with a custom rom.
so would you recommend to flash this ruu first? wouldn't i lose s-off then? would i be abled to achieve s-off again after flashing this? also, for my sensation i would have to supercid first - i didn't read about this here in the forums.
what i would want to do:
1. flash RUU_Saga_S_HTC_Europe_2.10.401.8_Radio_20.4801.30.0822U_3822.10.08.04_M_release_225161_signed.exe
2. run revolutionary again
3. flash custom recovery
4. flash endymion v3.1
would it be possible this way? or would you recommend any other way to me? i want to have all firmware parts as up to date as possible before i flash the custom rom.
Click to expand...
Click to collapse
Cause you are already s-off I would say it's senseless to use the ruu first, because it would put you back to s-on like you suggested, but only if the revolutionary bootloader doesn't make problems.
There are many reports of problems with it and I would say you should replace it with the 2.00.2002 engineer bootloader.
before just flash a custom recovery (I would recommend 4ext touch) and if your done with the bootloader flash the ROM of your choice.
To get bootloader, recovery,... just look at the index thread at the development section, it's all in there.
The last step to achieve a full upgraded phone would be to update the radio to the latest version, this you will also find at the index thread.
Happy modding
Oh and welcome, sry^^
Swyped from my desire s running damn sweet ice cream
Tectas said:
There are many reports of problems with it and I would say you should replace it with the 2.00.2002 engineer bootloader.
Click to expand...
Click to collapse
is there a guide you are referring to? i already got 4ext recovery installed, but i don't find any post concerning 2.00.2002 bootloader. if i flash this one i would stay s-off? and it would bring me all parts which i would be missing without 2.10.401.8 RUU?
/edit:
now i found this one, you are referring to that?
Tectas said:
The last step to achieve a full upgraded phone would be to update the radio to the latest version, this you will also find at the index thread.
Click to expand...
Click to collapse
i guess you are referring to this? 20.4801.30.0822U_3822.10.08.04 with my sensation i would also have to flash a matching ril, isn't it recommended with desire s?
smint86 said:
is there a guide you are referring to? i already got 4ext recovery installed, but i don't find any post concerning 2.00.2002 bootloader. if i flash this one i would stay s-off? and it would bring me all parts which i would be missing without 2.10.401.8 RUU?
/edit:
now i found this one, you are referring to that?
Click to expand...
Click to collapse
Yes this guide is to "downgrade" (in fact it's an upgrade, even if the version number is lower).
Yes you would stay s-off.
No it not brings you all what is missing, just a part of it, the rest you get with flashing the radio and the rom.
smint86 said:
i guess you are referring to this? 20.4801.30.0822U_3822.10.08.04 with my sensation i would also have to flash a matching ril, isn't it recommended with desire s?
Click to expand...
Click to collapse
It's not really needed, you can do it if it's in the zip (or better said if it's there it's done at the flashing procedure), but you're also good to go without it.

Phone locked again after unlocking/rooting?

Hello!
After a freak accident during which my DHD landed in our heater (see attached photo - mind you, still works perfectly!!!), I got myself a nice SXE. Proceeded to gutting it, installed Revolution HD ROM, then tried to update the radio but it wouldn't do it.
Curious, I checked the bootloader. Where it said something like UNLOCKED at the top (??), now it says LOCKED... The full text:
Code:
***LOCKED ***
PYRAMID PVT SHIP S-OFF RL
HBOOT-1.23.0000
RADIO-11.19.3504.29_2
OpenADSP-v01.6.0.2226.00.1227
eMMC-boot
Dec 26 2011,12:14:25
My question is, what exactly has been LOCKED again, and how did it happen?
Thanks so much...
[EDIT]
...and, of course, I found this minutes after posting, even though I had searched like a madman:
[09Jan]Helo my HBOOT says **Locked** when I updated to the new firmware
Ignore it, its fine, your still S-off and the bootloader is still unlocked. The only thing thats locked with the new firmware is the ability to perform advanced fastboot commands so flashing splash screens, pushing a radio. It wont affect most normal users, so no need to worry
Click to expand...
Click to collapse
Still, strange I couldn't flash the radio... file was pushed, but writing was denied...
With the Hboot "Locked", your phone can react to some adb or fastboot commands (push, reboot commands for example), but it's impossible to write any img on it.
If you want to change your radio, I think you must downgrade your Hboot by executing an older RUU (2.08** or 1.73**) and then, you will be back on an Hboot "unlockable" (Hboot 1.18** or less).
I didn't try to change radio, 'cause this one, RADIO-11.19.3504.29_2, is the last one and it seems Ok for my usage on ICS 4.3.1.
Things seem to have changed a bit since the days I was unlocking my DHD...
First things first: how do I make sure hboot (thanks - this was my initial question, I didn't know what LOCKED referred to!) is locked? Because, as I quoted,it seems that when you update the fw it says 'locked' even though it's unlocked.
But, if I downgrade through a RUU, if I update the fw again in order to flash Mike's ROM, I guess the same will happen?
Thanks for your reply!
Yep, if after downgrading by RUU, you flash Mike's firmware, you will have again the problem, because this RADIO-11.19.3504.29_2 is included in the FW.
To confirm your Hboot is really locked (for writing), you can try to flash any radio.img, with fastboot command.
You will see in your terminal, the img is send but it stays impossible to be written.
Interesting. So, basically, you need to flash the radio before updating the fw and before flashing the ROM... ok, staying with the one I have right now
Thanks again!
NO, it's useless to flash any radio before, 'cause when you'll update with Mike's FW, you'll get this Radio version 11.19.3504.29_2 again !!!....
So the simplest way is to keep this Radio version !!!
IMO, it is a good radio, but if you want to flash any GB custom rom, you will need the RiL files corresponding.
you will find it HERE.
Heh, that's what I thought, and it seemed weird to me... then how come Mike recommends another radio though (the one I tried to flash)?
Anyhow, thanks for the input, really appreciate it!
For his ICS based ROMs (ARHD v6.0.x), Mike recommends "11.65.3504.00U_11.19.3504.29_2 radio".
wideopen4ever said:
For his ICS based ROMs (ARHD v6.0.x), Mike recommends "11.65.3504.00U_11.19.3504.29_2 radio".
Click to expand...
Click to collapse
Yeah, but flashing his ICS/3.5 ROM (6.02) apparently gave me 11.19.3504.29_2?
Can the updated version be unlocked via HTC's online unlocker thing?
This one...
Skipjacks said:
Can the updated version be unlocked via HTC's online unlocker thing?
This one...
Click to expand...
Click to collapse
No. I tried doing it with the Revolutionary tool, which supposedly uses the same method and it told me it does not support this version...
Not sure if it will work with HTC's tool directly, though.
Skipjacks said:
Can the updated version be unlocked via HTC's online unlocker thing?
This one...
Click to expand...
Click to collapse
When I upgraded to hboot 1.20 used htcdev to unlocked it. Then upgraded to hboot 1.23 and it remained unlocked
Sent from my Kindle Fire using Tapatalk
krakout said:
Yeah, but flashing his ICS/3.5 ROM (6.02) apparently gave me 11.19.3504.29_2?
Click to expand...
Click to collapse
yes that is the newest radio for ICS, when you flashed the ICS UPdate it gave you everything ICS from hboot to radio, now all you had to do is find and 4.0.3 rom and flash and everything would match the ril/radio and hboot needed to keep it stable

[Q] Some general rooting questions

Hello,
I have finally decided to go down the path of custom roms. Have read around quite a bit and decided that the best idea would probably be to root using the downgrade method instead of using the HTC unlock method so that I would also get S-OFF (to be able to change kernel and radio).
Q1: Do you think this is a good choice?
Q2: If I indeed use the downgrade method, would it then in som way be possible to flash 4ext recovery and do a system backup of my current setup before downgrading?
Q3: Do I actually need to be able to change kernel/radio? Will many custom roms need a change of kernel?
Q4: Is it possible to return to stock recovery/rom from both of these methods in case need of warranty?
Many thanks!
/Neorth
1) Hell Yes. Best thing i did to my phone.
2) On your current setup, you'll need to flash the boot.img file from each ROM via fastboot after you flash it. If you use downgrade, This step is not needed. I reccomend you downgrade.
3) Every ROM has a built in kernel (boot.img) which will automatically change when you flash it. Do not mess with your radio, changing it does not make a lot of difference and it's risky. (if you don't downgrade, you can't change radio at all)
4) From downgrade, yes. From HTC Dev unlock, only partially. You can restore ROM an recovery, but your bootloader will only say Re_locked.
Thanks for your answers!
shrome99 said:
2) On your current setup, you'll need to flash the boot.img file from each ROM via fastboot after you flash it. If you use downgrade, This step is not needed. I reccomend you downgrade.
Click to expand...
Click to collapse
I think you missunderstood me on this one. My current setup is stock (S-ON, unrooted). What I want to do is to backup before I wipe the current rom, would that be possible?
shrome99 said:
3) Every ROM has a built in kernel (boot.img) which will automatically change when you flash it. Do not mess with your radio, changing it does not make a lot of difference and it's risky. (if you don't downgrade, you can't change radio at all)
Click to expand...
Click to collapse
I think I will downgrade but would this work even if I use the HTC unlock method? Think I read that you can't change kernel if you're only root with S-ON.
shrome99 said:
4) From downgrade, yes. From HTC Dev unlock, only partially. You can restore ROM an recovery, but your bootloader will only say Re_locked.
Click to expand...
Click to collapse
Then I guess downgrade it is!
Oh yes i did To answer question 2, yes you can. Unlock your phone Via HTCDev.com, flash 4ext recovery.img from fastboot and nandroid backup.
Ok, so if I want a backup I'll still have to unlock via HTCDev.com. Guess I better start to write down my current settings..
Now I've downgraded! Have also run revolutionary but not quite there yet as I have some questions so I won't do anything stupid
Q5. I want 4ext recovery instead of the clockwork mod so I answered no when revolutionary asked me to install that one. After that I've become a little nervous because I don't know if it's safe ro reboot without flashing a custom recovery, is it?
Q6. Can I reboot and install 4ext recovery from the phone (from market or apk)?
Q7. Why does revolutionary has it's own hboot (6.98.1002) and am I supposed to stick with it?
Thanks again!
Neorth said:
Now I've downgraded! Have also run revolutionary but not quite there yet as I have some questions so I won't do anything stupid
Q5. I want 4ext recovery instead of the clockwork mod so I answered no when revolutionary asked me to install that one. After that I've become a little nervous because I don't know if it's safe ro reboot without flashing a custom recovery, is it?
Q6. Can I reboot and install 4ext recovery from the phone (from market or apk)?
Q7. Why does revolutionary has it's own hboot (6.98.1002) and am I supposed to stick with it?
Thanks again!
Click to expand...
Click to collapse
You should rerun rev and install cwm then u can replace it with 4ext by downloading the app from market and flashing it from within the app
You'll need to flash superuser using cwm first though.
Yes you should replace the rev hboot with a standard engineering hboot. There are advantages as in some instances the rev hboot cannot be overwritten.
Sent from my HTC Desire S using xda premium
Is it really possible to run revolutionary on hboot 6.98.1002?
I rebooted without problem. So I guess the problem is that I don't have su access? Any walk around for this?
Yes, but you need CWM first, that'll give you EVERYTHING you want. Follow this to get CWM and get root access - http://forum.xda-developers.com/showthread.php?p=14693680 Then, download the 4Ext recovery control app (it needs root) and flash 4ext recovery.
Sent from my iPod touch using Tapatalk
Ah, perfect! I'm working my way through the different guides and are now in this stage:
SAGA PVT ENG S-OFF
HBOOT-0.98.2000 (PG8810000)
RADIO-3805.06.02.03_M
Have also got 4ext as recovery so all is great so far
Now I just have to decide on which custom ROM to start with. Think Quattro, Endymion and Reaper are the top candidates
Btw, do you think I should upgrade to the latest hboot-2.00.2002? And should I upgrade to the latest radio? And should I in that case do that before or after ROM?
No need for touching your radio or hboot. I've never flashes an hboot and the one time i flashed a radio, my phone almost got bricked.
Sent from my iPod touch using Tapatalk
Thanks for your help shrome99!
I'm now running Reaper v.1.5 and it runs smooth

Categories

Resources