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.
THIS IS FOR UNBRANDED 401 PHONES ONLY! IT MIGHT WORK FOR OTHERS BUT I WOULD RATHER NOT TRY...
Update 2011/08/14
Added more information and details
Renamed thread into GUIDE
Using this guide will reset your device into a vanilla 2.3.4 HTC Sensation phone. Your SD-Card wont be touched and you will have S-OFF and root. This will lock your bootloader but that should not be a problem since you are still S-OFF and can flash whatever you want - except the bootloader. I tested these steps and i have a 2.3.4 401 Sensation with Locked HBOOT, S-OFF and root.
If you want S-OFF & ROOT on the latest HTC 2.3.4 ROM follow the steps:
1) Backup
2) Get S-OFF on 2.3.3 (Guide Thread)
3) Recover your phone with original 2.3.3 Update
http://www.filefactory.com/file/cc03797/n/RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.900 7.00U_10.51.9007.27_M3_release_198179_signed.exe
4) Update to 2.3.4 via "Over The Air" (OTA) or using OpenRecovery (OR). I did not use the OR-Method but you can find a lot of information about here. I do not advertise any guides for the OR-method since i did not test them myself.
4) Execute step 2.1 to 2.6 from the Sensation Guide (Guide Thread)
5) Get root again: Sensation Guide 3.1 to 3.12 (Guide Thread)
Have fun!
dacleric said:
....
4) Update to 2.3.4 via ...... using recovery.
Have fun!
Click to expand...
Click to collapse
How? Can some please explain step by step?
Thanks
anyone have a change log? google failed me for once in my life
The 2.3.4 update include an new hboot Version 1.18...
Are u sure that u can install cwm and root the phone again after applying the update?
I think u will be s-on again after the hboot get changed...
Everything I'm reading (the two other threads about this update) says the above method will NOT work. I don't think the OP even tried. Wait for a real dev to cook this up.
dacleric said:
THIS IS FOR UNBRANDED 401 PHONES ONLY! IT MIGHT WORK FOR OTHERS BUT I WOULD RATHER NOT TRY...
Using this guide will reset your device into a vanilla 2.3.4 HTC Sensation phone. Your SD-Card wont be touched and you will have S-OFF and root.
If you want S-OFF & ROOT on the latest HTC 2.3.4 ROM follow the steps:
1) Backup
2) Get S-OFF on 2.3.3 (Guide Thread)
3) Recover your phone with original 2.3.3 Update
http://www.filefactory.com/file/cc03797/n/RUU_Pyramid_HTC_Europe_1.35.401.1_Radio_10.43a.900 7.00U_10.51.9007.27_M3_release_198179_signed.exe
4) Update to 2.3.4 via OTA or using recovery.
4) Execute step 2.1 to 2.6 from the Sensation Guide (Guide Thread)
5) Get root again: Sensation Guide 3.1 to 3.12 (Guide Thread)
Have fun!
Click to expand...
Click to collapse
All perfect....but...my HBOOT shows ***LOCKED***..... What`s that?
^^ see the thread in the general section about this.
http://forum.xda-developers.com/showthread.php?t=1214707
Around page ten or so.
And this:
http://forum.xda-developers.com/showpost.php?p=16585832&postcount=123
A little more:
http://forum.xda-developers.com/showpost.php?p=16582890&postcount=31
eloyloy said:
All perfect....but...my HBOOT shows ***LOCKED***..... What`s that?
Click to expand...
Click to collapse
Oh boy Some of use knew this was gonna happen
do not flash this to a stock rooted rom - it will **** it up - wait for your favourite dev to update their rom
flashing this will give you the new locked htc bootloader and you will not be s-off anymore (even though it still says you are)
it's taken me nearly 3 hours to get back to normal
EddyOS said:
When I say I'm S-OFF again, I mean I'm back to my old 2.3.3 ROM before I flashed the new update.
Everyone, DO NOT TRY AND FLASH THIS OVER YOUR ROOTED PHONE - WAIT FOR YOUR ROM TO BE UPDATED BY THE DEVS
Click to expand...
Click to collapse
xxxxxxxxxxx
Ledroid will tell us
Sent from my HTC Sensation Z710e using XDA Premium App
Hi all,
I've just done this update
Backup with Titanium
Reflash with 2.3.3 stock ROM (my Sensation was already S-Off)
OTA update to 2.3.4
ClockWork Recovery
Root
Restore with Titanium
Reboot and that's it
No OTA
I did exactly like shown in the first post, but i wont get the update ota. It sais that my phone is actually actual.
Could I have done something wrong?
Got the Sensation from T-mobile -> debrandet it like this:
http://forum.xda-developers.com/showthread.php?t=1193033
And used the RUU version from the first post.
Thanks
done as suggested - works fine for me!
I was off this weekend.
I posted this howto cause i did it with my phone. Whyever would i post a guide when it does not work?!
Using this guide will lock your bootloader but that should not be a problem since you are still S-OFF and can flash whatever you want - except the bootloader.
At least thats the case for me.
dacleric said:
Using this guide will lock your bootloader but that should not be a problem since you are still S-OFF and can flash whatever you want - except the bootloader.
Click to expand...
Click to collapse
Are you sure you can't flash the eng hboot too?
dazweeja said:
Are you sure you can't flash the eng hboot too?
Click to expand...
Click to collapse
no - i did not try to.
I am pretty happy with my phone right now. Fast and long battery pack - replaced Sense with LP.
When testing the early (pre-soff) custom roms and test recoverys I had to flash stock RUUs a couple of times.
To get the phone back into a decent state I needed to pg58 flash eng&unsecured boot then root and fastboot recovery.
Can't for the life of me think why anyone would s-off their phone then install stock/ota for any reason (bar repair). It's like buying a track day race car, shouting "look what I've got" then pushing it around rather than thrashing it.
dazweeja said:
Are you sure you can't flash the eng hboot too?
Click to expand...
Click to collapse
If you just flash the new hboot, it will say lock at the top of the bootloader screen. But you should be able to flash eng hboot, cause I just tried it.
Sent from my HTC Sensation Z710e using XDA App
d3vilskid said:
If you just flash the new hboot, it will say lock at the top of the bootloader screen. But you should be able to flash eng hboot, cause I just tried it.
Click to expand...
Click to collapse
Thanks. That's what I thought. I removed the hboot from the OTA before flashing it so couldn't confirm for myself. There's been a lot of conflicting information about whether phones are still S-OFF after running the unmodified OTA but it appears that they are. I only ran the RUU then OTA so I could have a backup of a stock 1.45 system.img.
dazweeja said:
Thanks. That's what I thought. I removed the hboot from the OTA before flashing it so couldn't confirm for myself. There's been a lot of conflicting information about whether phones are still S-OFF after running the unmodified OTA but it appears that they are. I only ran the RUU then OTA so I could have a backup of a stock 1.45 system.img.
Click to expand...
Click to collapse
Np, i was trying to figure out how to flash pg2fs_spcustom.img and I found out that the only way to do it was to flash the new hboot first than it would read that pg2fs img.
Sent from my HTC Sensation Z710e using XDA App
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 two HTC Sensation Device ---
1) Locked hboot1.27.XXXX, ICS (From Official OTA), S-ON, Non-rooted
2) Locked hboot1.18.XXXX, GB (As no Official OTA Received for ICS), S-ON, Non-rooted, Orange-United Kingdom
I have successfully unlocked and rooted both the devices with 4EXT Touch Recovery Installed in both the mobiles (Still S-ON for both devices).
Now my Device status are as below:
1) Unlocked hboot1.27.XXXX, ICS (Custom ROM), S-ON, Rooted
2) Unlocked hboot1.18.XXXX, GB (Slightly Customed ROM), S-ON, Rooted
I have tried to install different ICS based custom roms using Smart Flash of 4EXT Recovery with S-ON.
In first device, ROM installation was successful in every try
But in second device, ROM installation failed and boot-loop problem occurred (tried with 5~6 custom ROMS but failed all the time with similar problem). Then I have flashed GB ROM on second device with hboot 1.18.XXXX.
Can anyone answer my following queries, Please--
1) I think, as the custom ROMS requires hboot version 1.27.XXXX+, it failed to flash. Please confirm whether my assumption is ok or not. Please be noted that custom ROMS are flashing my first device with S-ON with ease.
2) Can I upgrade to 1.27.XXXX hboot version without S-OFF?
3) Can I flash/push by hboot.img through (fastboot flash hboot hboot.img) command with version 1.27.XXXX? If yes, can anyone provide me a proper link to download that hboot.img file?
4) Can anyone provide me download link for RUU so that I can update my hboot version by official ICS ROM (Orange, United Kingdom)
5) Can anyone suggest any better method to install custom ROMS with S-ON?
6) Can anyone suggest me how to S-OFF easily (I have tried Revolutionary.exe, but this program never opens in my PC although I have the beta Key)?
7) With S-OFF, will the problem will be solved with hboot version 1.18.XXXX? If not, please suggest...
I would be really happy if my problem is solved by any of yours' help
in the first device you completely fine:good:
in the second one indeed you need to S-OFF in order to upgrade firmware to ics(will upgrade also your hboot version)
that's why the device is bootlooping(not running in gb firmware)
you mentioned that you tried revolutionary method and it didn't work
so try this guide
http://forum.xda-developers.com/showthread.php?t=1672425
search for the correct ruu.exe
by the way what kind of problem do you face with revolutionary method?
RE:
rzr86 said:
in the first device you completely fine:good:
in the second one indeed you need to S-OFF in order to upgrade firmware to ics(will upgrade also your hboot version)
that's why the device is bootlooping(not running in gb firmware)
you mentioned that you tried revolutionary method and it didn't work
so try this guide
http://forum.xda-developers.com/showthread.php?t=1672425
search for the correct ruu.exe
by the way what kind of problem do you face with revolutionary method?
Click to expand...
Click to collapse
In fact revolutionary.exe is being crashed whenever I tried to open it either in Windows XP (Office Laptop) or in Windows 7 (Home PC). So, I have failed to use this tool. Can u suggest any idea?
If you can't use revolutionary for s-off, then your only hope is RUU.EXE on your PC.
Sent from my HTC Sensation
Hi
With these specifications, Can I flash any rom to my htc one sv ?
I have TWRP v2.6.3.2 Recovery
Please , Help me.
*** Tampered***
***Unlocked***
K2_UL PVT SHIP S-ON RL
HBoot - 2.21.000
Radio - 1.18.40a.00.05
OpenDSP-v13.2.0268.0620
OS- (Wiped)
CID - HTC_J15
Thanks.
Better would be S-Off, but yes, you should be able to flash a rom with this.
But don't forget to flash boot.img from your rom with fastboot, every time you flash a new rom.
old.splatterhand said:
Better would be S-Off, but yes, you should be able to flash a rom with this.
But don't forget to flash boot.img from your rom with fastboot, every time you flash a new rom.
Click to expand...
Click to collapse
Thanks, but I can't find any rom for my region, icm:HTC_J15. Could you give me a link to download a rom for my region ?
Don't mix it with official updates from HTC!
A (custom) rom is made not by HTC, this you can use.
A update by HTC don't have a rom.zip inside.
A RUU has a rom inside, but this is cid related.
So better clarify, what you are searching or what you want to do!
old.splatterhand said:
Don't mix it with official updates from HTC!
A (custom) rom is made not by HTC, this you can use.
A update by HTC don't have a rom.zip inside.
A RUU has a rom inside, but this is cid related.
So better clarify, what you are searching or what you want to do!
Click to expand...
Click to collapse
I don't have any rom in my cellphone and my system wiped,
Now, I want to flash a new rom.
Can I flash a stock rom or I must flash a custom rom ?
Can you give me a link to download a rom for flashing properly (Stock or Custom) ?
Thanks.
Try stock k2ul rom from here.
old.splatterhand said:
Try stock k2ul rom from here.
Click to expand...
Click to collapse
Thank you very much,
Can I make my phone S-Off before flashing this rom ?
Or firstly I should flash this rom and then try to make S-Off ?
If yes, which method ? facepalm or moonshine ?
I Apologize, This was my last Q today ?
Bye.
Your phone must have android running, then you can try rumrunner.us
Facepalm or moonshine are for previous software versions.
But as it seems, the side is down at the moment.
old.splatterhand said:
Try stock k2ul rom from here.
Click to expand...
Click to collapse
I tried this rom and it worked for me.:good:
Thank you very much.
Nice to hear
old.splatterhand said:
Your phone must have android running, then you can try rumrunner.us
Facepalm or moonshine are for previous software versions.
But as it seems, the side is down at the moment.
Click to expand...
Click to collapse
Hi,
I used rumrunner.us and now my device is S-OFF. Therefore I must be able to flash other roms after changing my cid and hboot version. Is it right ?
And another question is,
I've flashed Superuser-3.1.3-arm-signed.zip and superuser.apk has been installed but those programs that want to get root access, can't do this like Root Explorer, and in RootValidator as you can see in the picture below, shows "Root was denied to this app!", and from ADB I can to get root access, but why programs don't have any root access ?
Thanks.
my_amin said:
Hi,
I used rumrunner.us and now my device is S-OFF. Therefore I must be able to flash other roms after changing my cid and hboot version. Is it right ?
Click to expand...
Click to collapse
Depends on, if we are talking about official HTC roms/updates or custom roms. For custom roms you usually don't need to change CID.
I've flashed Superuser-3.1.3-arm-signed.zip and superuser.apk has been installed but those programs that want to get root access, can't do this like Root Explorer, and in RootValidator as you can see in the picture below, shows "Root was denied to this app!", and from ADB I can to get root access, but why programs don't have any root access ?
Click to expand...
Click to collapse
You should use SuperSu, because i'm not sure that Superuser is still in development (especially for newer Android versions).
Grab the zip file here and flash in recovery (should also remove Superuser you have already flashed).
old.splatterhand said:
Depends on, if we are talking about official HTC roms/updates or custom roms. For custom roms you usually don't need to change CID.
You should use SuperSu, because i'm not sure that Superuser is still in development (especially for newer Android versions).
Grab the zip file here and flash in recovery (should also remove Superuser you have already flashed).
Click to expand...
Click to collapse
Thank you again, my device was rooted completely and now programs have root access.