Related
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.
Hello,
i am totally newbie here. Spent last 2 nights studying forum threads, but im still confused.
What is better to unlock via htcdev and remain S-ON and HBOOT 2.00.0002 or to downgrade HBOOT ?
I would like to tryout AOKP, Cyanogen and Fallout roms. Alternatively i want to try official ICS ASAP.
remusator said:
Hello,
i am totally newbie here. Spent last 2 nights studying forum threads, but im still confused.
What is better to unlock via htcdev and remain S-ON and HBOOT 2.00.0002 or to downgrade HBOOT ?
I would like to tryout AOKP, Cyanogen and Fallout roms. Alternatively i want to try official ICS ASAP.
Click to expand...
Click to collapse
Unlocking via HTCdev leaves the phone S-ON. Therefore you always have to flash the the kernel (boot.IMG) from a PC via FASTBOOT when you flash a new rom with a different base. E.G. CM and Fallout. If the base hasn't change you don't need to.
If you downgrade and S-OFF your device you don't have to do that. Plus you can flash different radios (barely necessary).
HTCdev unlock is easier to do and gives you a lot of possibilities.
S-OFF is a little more advanced and there is a little more danger to brick your phone when you don't do it carefully.
Nevertheless I prefer the hard way since HTCdev is not the way I would go. Plus HTC knows that my device is unlocked.
Gesendet von meinem HTC Desire S mit Tapatalk
Agreed. Although if you're changing ROMs often then HTCDev is not the easier way. Flashing the boot.img can be quite a pain if you're doing it often.
There was a nice text about that in another thread.
http://forum.xda-developers.com/showthread.php?p=27511649
Gesendet von meinem HTC Desire S mit Tapatalk
Ok,
so what you guys are basically saying is, that when i unlock my phone thru HTC-Dev, the company knows about it.
From this point of view, it's better to downgrade hboot and S-OFF.
I have one more question - if original ICS for DS will be realeased, how can i install it ? Do i have to revert to original hboot and original sense rom to find the update and install then ?
You'll find it here ...
Finally i temprooted this way
Zergush & misc - to temp root and prepare phone to be downgrade
Downgrade to RUU with 0.98.0000
S-OFF & install ClockWorkMod Recovery
Install Cyanogen 7.2
As rom i chose Cyanogenmod 7.2 stable. I am unexperienced with custom roms and dont want to be disappointed by semi-functional ICS roms by now.
If you're going for gingerbread take a look at reaper as well. It's basically a much faster version of CM7
For now, i am going to stick with ginger till the kernel will be released and the roms fully functional.
In future i would like to test ICS roms, but after new kernel. And of course Jelly Bean, if someone port it.
Basically if i want to change ROM, i just put it in root of SDcard, boot revolutionary, wipe and install from ZIP ? Is that simple now, after S-OFF ?
Thanx for the tip to check out reaper, btw
Yep that's all you need to do. I have to say though don't be afraid to just make a backup of your current ROM in CWM and try out other things.
Dan-fish, thanks for all your help
But i have one more question. What is all that mess around eMMC chip ? How can it happen to me ? Often flashing, installing from zip or ?
No the most common reason is pulling the battery out while the phone is on.
Check this thread
http://forum.xda-developers.com/showthread.php?t=1284196
Sent from my Desire S using Tapatalk 2
remusator said:
Finally i temprooted this way
Zergush & misc - to temp root and prepare phone to be downgrade
Downgrade to RUU with 0.98.0000
S-OFF & install ClockWorkMod Recovery
Install Cyanogen 7.2
As rom i chose Cyanogenmod 7.2 stable. I am unexperienced with custom roms and dont want to be disappointed by semi-functional ICS roms by now.
Click to expand...
Click to collapse
Dear remusator..
I'm trying downgrade hboot from 2.00.0002 to 0.98.00000 but I could not.
Can you explane how you make downgrade?
My device is "UNLOCKED"
Hboot - 2.00.0002
RADIO - 3822.10.08.04_M
eMMC - boot
Thanks..
Mine was locked. Check the first post. I didn't unlock via htc dev, maybe that's the problem.
I followed these tutorials :
1, Downgrade ruu and hboot to make root possible
sw 2.10<= http://forum.xda-developers.com/showthread.php?t=1399331
sw 2.11>=http://forum.xda-developers.com/showthread.php?t=1443636
2, S-OFF
http://forum.xda-developers.com/showthread.php?t=1186401
section How To: S-Off your device with Revolutionary: S-OFF & Recovery Tool (For HBOOT 0.98.0000, 0.98.0002)
3, Choose rom you like and flash via recovery. First i tried was cyanogenmod 7,2. Then i made backup, wiped again and installed AOKP. I'm not going back )
While browsing forums, i found topic about downgrading while UNLOCKED. Search forums, i can't find it anymore.
Btw, check your software version - tutorials differ from sw version.
PS: don't be afraid. In my case, everything went just fine.
Stock Rom needed
Hi remusator, which stock ROM did you use?
I'm mostly finding a lot of dead links and very few live ones for stock Desire S Roms.
I have used quite - Fallout / AOKP / Cyanogen 7.2
But i returned back to Stock. I used pre-rooted. I don't need root at the moment, but the prerooted rom can run on custom bootloader.
I use 2.10.401.9 sw version, take a look here
http://forum.xda-developers.com/showthread.php?t=1480576
Before root my official rom was 2.10.401.8 - but the link here on forum is dead, so i decided to use newer 2.10.401.9 instead. I haven't found any bug yet. It seems to work fine.
remusator said:
Before root my official rom was 2.10.401.8 - but the link here on forum is dead, so i decided to use newer 2.10.401.9 instead. I haven't found any bug yet. It seems to work fine.
Click to expand...
Click to collapse
2.10.401.9 contains a minor bugfix for the Russian region. I doubt that you will notice any significant difference compared to 2.10.401.8
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!
hello, i am new to HTC One S and my device is completely stock now. I have hboot 2.15..
I want to lock the bootloader, install a custom recovery, s-off and install a custom rom.
I have some questions now:
1. Is it possible to install a 4.4.2 rom with this hboot?
2. Why do i need s-off for sense 5.x?
3. Why do i have to flash boot.img? And why do i not have to flash a boot.img with s-off? Where do i get the boot.img for the rom i flashed?
MICH_** said:
hello, i am new to HTC One S and my device is completely stock now. I have hboot 2.15..
I want to lock the bootloader, install a custom recovery, s-off and install a custom rom.
I have some questions now:
1. Is it possible to install a 4.4.2 rom with this hboot?
2. Why do i need s-off for sense 5.x?
3. Why do i have to flash boot.img? And why do i not have to flash a boot.img with s-off? Where do i get the boot.img for the rom i flashed?
Click to expand...
Click to collapse
1: I run CM11 which is 4.4.
2: Don't know but not sure if there is a 4.4 ROM with Sense 5.
3: The boot.img is in the ROM zip - just unzip it and the boot.img is there. When you are S-OFF the boot.img is flashed with the zip. Otherwise you have to do it manually if you are not S-OFF.
I am no expert but one thing I know - life got a lot easier being S-OFF with the HTC ONE S.
808phone said:
1: I run CM11 which is 4.4.
2: Don't know but not sure if there is a 4.4 ROM with Sense 5.
3: The boot.img is in the ROM zip - just unzip it and the boot.img is there. When you are S-OFF the boot.img is flashed with the zip. Otherwise you have to do it manually if you are not S-OFF.
I am no expert but one thing I know - life got a lot easier being S-OFF with the HTC ONE S.
Click to expand...
Click to collapse
Are you on hboot 2.15 too? Did you update your firmware?
No but there are sense 5.5 roms with android 4.3....
How did you get S-OFF? And which tutorial did you use to unlock etc?
MICH_** said:
hello, i am new to HTC One S and my device is completely stock now. I have hboot 2.15..
I want to lock the bootloader, install a custom recovery, s-off and install a custom rom.
I have some questions now:
1. Is it possible to install a 4.4.2 rom with this hboot?
2. Why do i need s-off for sense 5.x?
3. Why do i have to flash boot.img? And why do i not have to flash a boot.img with s-off? Where do i get the boot.img for the rom i flashed?
Click to expand...
Click to collapse
Let's take one by one...
1. Yes. Currently only AOSP ROMs are with Android 4.4.2, there's no Sense based one (but it's been working on it)
2. Well, that's a tricky question...You don't need S-Off for sense 5.x BUT...only ROM with sense 5.5 is Liberty (by bilal_liberty). If you're not S-Off you can't flash radios. If you can't flash radios, you will not have HSPA/HSPA+ mobile data connection with that ROM (and probably with sense 6 and 4.4.2 ROM also). You will get maximum 3G (UMTS) mobile data with your current radio. On the other hand, if you decide to try an AOSP ROM, you won't have that problem there. You can be S-On and have everything working
3. You have to flash boot.img only if you're S-On. Maybe it's better if you read what S-On/S-Off means. On short, if you're S-On, some partitions are read only and you cannot write to them in recovery...most important the radio partition and the kernel/boot partition. So if you're S-On you can't flash the radio and you can't flash the kernel. Kernel has several components (I try to make a simple explanation not entering in the details): modules, ramdisk and the kernel itself. I'll take them one by one:
- modules: most are incorporated in the ROM and have the extension .so. These files are flashed on the device in the /system partition along with the ROM, in recovery. You don't need to be S-Off to have those installed
- ramdisk & kernel: they're both packed in that boot.img and they're generically referred to as "kernel". These are written in a special partition that is read-only for S-On devices while in recovery. Kernel partition is in write-mode only in fastboot. Therefore you must be S-Off to be able to write kernel from recovery OR, you have to write it from fastboot if you're S-On
So, when you flash a ROM ZIP, the install script writes the modules along with the rest of the ROM since those resides on the /system partition then tries to write also the boot.img. But in case you're S-On, it can't. So the only way to do it is from fastboot where you separately flash the boot.img
Now as I give you some info, take some time and read it (TWICE). Then take some time and look for the tutorials here. First thing you should do is to unlock your bootloader via HTC Dev site. Then you can install a recovery and make S-Off (I personally used for that Rumrunner but it's your call)
Before doing anything, install Android SDK and make sure it's properly installed and the drivers are working. You should have a functional ADB/fastboot for any of the above.
Rapier said:
Let's take one by one...
1. Yes. Currently only AOSP ROMs are with Android 4.4.2, there's no Sense based one (but it's been working on it)
2. Well, that's a tricky question...You don't need S-Off for sense 5.x BUT...only ROM with sense 5.5 is Liberty (by bilal_liberty). If you're not S-Off you can't flash radios. If you can't flash radios, you will not have HSPA/HSPA+ mobile data connection with that ROM (and probably with sense 6 and 4.4.2 ROM also). You will get maximum 3G (UMTS) mobile data with your current radio. On the other hand, if you decide to try an AOSP ROM, you won't have that problem there. You can be S-On and have everything working
3. You have to flash boot.img only if you're S-On. Maybe it's better if you read what S-On/S-Off means. On short, if you're S-On, some partitions are read only and you cannot write to them in recovery...most important the radio partition and the kernel/boot partition. So if you're S-On you can't flash the radio and you can't flash the kernel. Kernel has several components (I try to make a simple explanation not entering in the details): modules, ramdisk and the kernel itself. I'll take them one by one:
- modules: most are incorporated in the ROM and have the extension .so. These files are flashed on the device in the /system partition along with the ROM, in recovery. You don't need to be S-Off to have those installed
- ramdisk & kernel: they're both packed in that boot.img and they're generically referred to as "kernel". These are written in a special partition that is read-only for S-On devices while in recovery. Kernel partition is in write-mode only in fastboot. Therefore you must be S-Off to be able to write kernel from recovery OR, you have to write it from fastboot if you're S-On
So, when you flash a ROM ZIP, the install script writes the modules along with the rest of the ROM since those resides on the /system partition then tries to write also the boot.img. But in case you're S-On, it can't. So the only way to do it is from fastboot where you separately flash the boot.img
Now as I give you some info, take some time and read it (TWICE). Then take some time and look for the tutorials here. First thing you should do is to unlock your bootloader via HTC Dev site. Then you can install a recovery and make S-Off (I personally used for that Rumrunner but it's your call)
Before doing anything, install Android SDK and make sure it's properly installed and the drivers are working. You should have a functional ADB/fastboot for any of the above.
Click to expand...
Click to collapse
2. So i have to update my firmware, right?
3. okay, i understood everything.. thank you
Why do i need the complete SDK? Doesn´t it work just with the adb and fastboot drivers?
MICH_** said:
2. So i have to update my firmware, right?
3. okay, i understood everything.. thank you
Why do i need the complete SDK? Doesn´t it work just with the adb and fastboot drivers?
Click to expand...
Click to collapse
You don't have to upgrade the firmware since you're on the latest official one. 2.16 is an unofficial leaked firmware and you only need it if you want to flash MaximusHD or MagioRom
You don't need entire SDK but I thought it's easier since is an install package for that. Of course, if you don't build for Android, you don't need the libraries, just the tools
Sent from nowhere over the air...
Rapier said:
You don't have to upgrade the firmware since you're on the latest official one. 2.16 is an unofficial leaked firmware and you only need it if you want to flash MaximusHD or MagioRom
You don't need entire SDK but I thought it's easier since is an install package for that. Of course, if you don't build for Android, you don't need the libraries, just the tools
Sent from nowhere over the air...
Click to expand...
Click to collapse
could you give me a good tutorial for unlocking the bootloader, s-off, flash this leaked firmware and super-CID please?
Okay, i unlocked the bootloader, installed TWRP, flashed a custom rom and now i am trying to get s-off...
MICH_** said:
could you give me a good tutorial for unlocking the bootloader, s-off, flash this leaked firmware and super-CID please?
Okay, i unlocked the bootloader, installed TWRP, flashed a custom rom and now i am trying to get s-off...
Click to expand...
Click to collapse
For firmware ZIPs you can flash in recovery AFTER you make S-Off, check HERE. For S-Off I used Rumrunner cause it seems to me much easier and without so many steps...it's something like a one-click operation
Rapier said:
For firmware ZIPs you can flash in recovery AFTER you make S-Off, check HERE. For S-Off I used Rumrunner cause it seems to me much easier and without so many steps...it's something like a one-click operation
Click to expand...
Click to collapse
Rumrunner is running now
I will update my firmware tomorrow i think..
If i update the firmware with this tutorial from Maxiums 10.0 rom. Do i have hboot 2.16? Am i still able to run roms for 2.15 hboot?
MICH_** said:
Rumrunner is running now
I will update my firmware tomorrow i think..
If i update the firmware with this tutorial from Maxiums 10.0 rom. Do i have hboot 2.16? Am i still able to run roms for 2.15 hboot?
Click to expand...
Click to collapse
I didn't checked the MaximusHD tutorial but I strongly suggest you to just flash the firmware zip if you want to do an upgrade/downgrade of the firmware. Most tutorials assume you're initial S-Off and include also some steps for how to acquire this or going through RUUs.
OK..I've read the MaximusHD tutorial, it's pretty much identical with the one made by Flashalot...so the answer is YES, you can use it and after that you would have hboot 2.16. Please also note that a different recovery must be used with 2.16 ROMs. But you'll have that in the MaximusHD instructions as well
NO, you can't run or flash ROMs made for 2.15 firmware after doing this. You should downgrade the firmware to 2.15 first, by using the instructions and the firmware ZIP from the thread I've linked
Rapier said:
I didn't checked the MaximusHD tutorial but I strongly suggest you to just flash the firmware zip if you want to do an upgrade/downgrade of the firmware. Most tutorials assume you're initial S-Off and include also some steps for how to acquire this or going through RUUs.
OK..I've read the MaximusHD tutorial, it's pretty much identical with the one made by Flashalot...so the answer is YES, you can use it and after that you would have hboot 2.16. Please also note that a different recovery must be used with 2.16 ROMs. But you'll have that in the MaximusHD instructions as well
NO, you can't run or flash ROMs made for 2.15 firmware after doing this. You should downgrade the firmware to 2.15 first, by using the instructions and the firmware ZIP from the thread I've linked
Click to expand...
Click to collapse
could you please give me a link to a recovery that is compatible with 2.16? TWRP would be perfect
After installing the new hboot i have still a rom for 2.15 running on my phone. does this work? Does updating the firmware wipe internal storage?
Why do some sense 5 roms work with hboot 2.15 and others not?
MICH_** said:
could you please give me a link to a recovery that is compatible with 2.16? TWRP would be perfect
After installing the new hboot i have still a rom for 2.15 running on my phone. does this work? Does updating the firmware wipe internal storage?
Why do some sense 5 roms work with hboot 2.15 and others not?
Click to expand...
Click to collapse
Oh...you like to ask soo many questions don't you? All these questions are already answered in the threads, why don't you check them?
The main difference between 2.15 and 2.16 hboot/firmware is the partition map. On 2.16 there is no separation between the sdcard and data and you get a single big space for both. This makes more space available to data and sdcard looks bigger (12 GB instead of 10 GB). That's a brief description not entering in details. ROMs made for 2.15 will work on 2.16 and the other way around BUT with issues. Mainly it is about the sdcard size that is not available at all or has an incorect size (48 MB instead of 12/10 GB). So even if your 2.15 ROM is working...try to check if the sdcard is mounted and what space you have on it
So all these being said, your understanding of the word "works" is different from the one of the devs. For them (or for anyone else), a "working" ROM does not mean only it boots, but it's also have all the parts available including sdcard mountable and available on it's entire space, not truncated to 48 MB or not mountable at all.
Now about why some sense 5 ROMs work with 2.15 and some don't. Because some ROMs are based on the leaked 2.16 firmware and those ROMs need the new partition map to properly work. The ones that are working on 2.15 are usually ports or builds made for the standard official HTC firmware.
Link for recoveries compatible with 2.16 hboot you can find in the OP of each 2.16 ROM
Rapier said:
Oh...you like to ask soo many questions don't you? All these questions are already answered in the threads, why don't you check them?
The main difference between 2.15 and 2.16 hboot/firmware is the partition map. On 2.16 there is no separation between the sdcard and data and you get a single big space for both. This makes more space available to data and sdcard looks bigger (12 GB instead of 10 GB). That's a brief description not entering in details. ROMs made for 2.15 will work on 2.16 and the other way around BUT with issues. Mainly it is about the sdcard size that is not available at all or has an incorect size (48 MB instead of 12/10 GB). So even if your 2.15 ROM is working...try to check if the sdcard is mounted and what space you have on it
So all these being said, your understanding of the word "works" is different from the one of the devs. For them (or for anyone else), a "working" ROM does not mean only it boots, but it's also have all the parts available including sdcard mountable and available on it's entire space, not truncated to 48 MB or not mountable at all.
Now about why some sense 5 ROMs work with 2.15 and some don't. Because some ROMs are based on the leaked 2.16 firmware and those ROMs need the new partition map to properly work. The ones that are working on 2.15 are usually ports or builds made for the standard official HTC firmware.
Link for recoveries compatible with 2.16 hboot you can find in the OP of each 2.16 ROM
Click to expand...
Click to collapse
now i have everything i wanted to know tanks
I think i will stay on 2.15 and install ViperOne S 3.1.3 now. This will work on my current setup, right?
I will update the radio. Should i just flash the one attached in the ViperOne S thread in recovery?
MICH_** said:
now i have everything i wanted to know tanks
I think i will stay on 2.15 and install ViperOne S 3.1.3 now. This will work on my current setup, right?
I will update the radio. Should i just flash the one attached in the ViperOne S thread in recovery?
Click to expand...
Click to collapse
Good choice, Viper is a fine ROM and close to the original since it's sense based...also has extra customization that the original ROM doesn't have.
For the radio, well I've answered to you in the Viper thread. I would advice not to flash another radio just now. Flash the ROM, play with it for a few days then decide. If you have no issues with signal reception, wifi and so on, you don't have real reasons to change it.
I had initially (when I bought the device) radio 1.06es (I think)...since then alot of newer versions came out including the 1.20 from the leaked 2.16 firmware and the newest 1.35a from the One XL. To be honest, after several days with each, I've switched back to 1.15 that was the best radio for me.
The only ROM for which you MUST flash a different radio will be Liberty by bilal_liberty. That is based on Android 4.3 and Sense 5.5 and the newest 1.35a radio is needed in order to get H/H+ (HSPA) mobile data connection. If you don't use that radio you'll get maximum 3G (UMTS) connection. The rest will work tho
I still don't understand why I had so many problems with Viper. Dropped calls, random reboots etc...
Once I got CM11 running - never looked back in terms of reliability.
Its been a while since I've done anything on my AT&T HTC One. I'm still on 1.14 unlocked bootloader and an old ViperVL 3.2.2 Rom. I want to upgrade to Lollipop CM12 so I've done a lot of research and I wanted to make sure I'm doing it right before starting.
This is what I believe I need to do:
1. Update TWRP to v2.7.1.0 or higher to support new ROM
2. Get s-off in the bootloader using firewater
3. Once S-OFF is done, put phone in fastboot mode and run the RUU 3.18 JellyBean update (Its my understanding we need the JB bootloader for Lollipop custom ROM to work?)
4. Flash TWRP v2.7.1.0 back via fastboot
5. Go into recovery and flash New Rooted CM12 Rom
Before I start this method I also have a few questions:
1. Does my above steps seem right?
2. I'm having a hard time finding a working 3.18 RUU link. Most of the links on here are dead now. Is the RUU update a required step to jump from ViperXL 3.2 (bootloader v1.14) to Lollipop based roms? If its required, I found the OTA JB 3.18 update. Can I use the OTA version instead?
3. I've read that as long as the bootloader is already unlocked with S-OFF, I won't lose S-off or the unlocked bootloader from the RUU. Is this correct or will I need to unlock bootloader (Via HTC's dev site) and root again after using the JB RUU?
Thanks in advanced for the help with my questions.