Kernel requirements - HTC Desire S

Hi all,
I am interested in recording my all phone calls. I found that 2WayCallRecord modification is necessary inside phone kernel. Found also that UNITY v9 kernel include it(any other kernels known to public?).
My question is what exactly I need to install kernel? Is it same story and proceeding patch like installation of ROMs(means I need S-OFF and low 0.98 HBOOT)? So far I got ROOT and UNLOCKED bootloader.

kristopulo said:
Hi all,
I am interested in recording my all phone calls. I found that 2WayCallRecord modification is necessary inside phone kernel. Found also that UNITY v9 kernel include it(any other kernels known to public?).
My question is what exactly I need to install kernel? Is it same story and proceeding patch like installation of ROMs(means I need S-OFF and low 0.98 HBOOT)? So far I got ROOT and UNLOCKED bootloader.
Click to expand...
Click to collapse
It's not absolutely necessary, but it's better, if you could update your hboot (with this guide: [GUIDE] new HBOOT 2.00.2002 for sense 3.0 Android 2.3.5)
and after, just flash your kernel as a rom.
Don't forget to making a backup of all changes. Just in case

Related

[Q] A couple of questions concerning new Desire S

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

htcdev unlock vs S-OFF / downgrade

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

[Q] so many things, so insecure

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

[Q] First Time Rooting/Flashing. Help!

I've got a HTC Sensation XE.
Build Number - 3.33.720.106
Kernel version 3.0.16-g31a4fc7
HBoot version 1.29
I've spent about 3 hours reading about Rooting, flashing custom roms and I'm still confused as hell.
From what I've read, S-OFF is a pretty complicated process for users with HBoot version 1.27+
We have to use the wire trick, etc.
I'm not sure if I should S-OFF for two reasons:
1. First time flashing a custom Rom I want to keep it as simple as possible.
2. To S-OFF, I must use HTCdev's bootloader unlocker process as well and I read somewhere that once I do that, my phone's IMEI will be added to HTC's banned-list for warranty claims. I do not want to do that till I'm absolutely sure on how to do it.(Is this true?)
Click to expand...
Click to collapse
So I have a few questions and need some help/guidance.
I wish to install a Custom Rom(Jelly Bean) without HTC's Sense as it takes up too much RAM and I want my phone to run smooth without lag. That is the priority.
1. Is it advisable to Root/Flash phone with S-ON?
2. What am I missing out on if I do not S-OFF my device?
3. If S-OFF is pretty advantageous, I am willing to read/learn more before Flashing a Custom ROM.
4. Which is the most stable and lag-free Custom ROM(Jelly Bean, No Sense)
4.a. With S-ON?
4.b. With S-OFF?
5. When you go to HTCdev.com->Bootloader unlocker, there is no Sensation XE, should I choose option Sensation 4g or go with All other devices?
Click to expand...
Click to collapse
I'm sorry if my questions are silly but I'm very confused, I've read like 15+ different links in the last 3hours and its all messed up in my head.
Please help me understand clearly and/or refer me to a few Beginner guides(with advanced guides followed).
in simple words you have 2 options:
1)unlock your bootloader with htcdev unlock method
see here http://www.htcdev.com/
and then root your device
see here http://forum.xda-developers.com/showthread.php?t=1632553 or
2)use the juopunutbear method to S-OFF and root your device
see here http://forum.xda-developers.com/showthread.php?t=1661631
now to answer to your questions:
1)with S-ON involves the first option.but then before flashing a rom,flash first 4ext recovery
so you can use the smartflash feature from it(only for S-ON DEVICES)
2)with S-OFF you are completely unlock your device and have the ability to flash firmware,radios,rils(which you can not do with S-ON)
3)it is more advantageous.
but before flashing a rom the only thing you have to do is read carefully any installation instructions(the same goes for S-ON)
4)it is the same i assume
5)go with All other devices
rzr86 said:
...
now to answer to your questions:
1)with S-ON involves the first option.but then before flashing a rom,flash first 4ext recovery
so you can use the smartflash feature from it(only for S-ON DEVICES)
2)with S-OFF you are completely unlock your device and have the ability to flash firmware,radios,rils(which you can not do with S-ON)
3)it is more advantageous.
but before flashing a rom the only thing you have to do is read carefully any installation instructions(the same goes for S-ON)
4)it is the same i assume
5)go with All other devices
Click to expand...
Click to collapse
1. How is firmware different from ROM?
2. I thought firmware was the same as ROM?
3. After unlocking my bootloader with S-ON, I can install any custom ROM right? or Are there only certain ROMS that are available for S-ON phones?
thetearer said:
1. How is firmware different from ROM?
2. I thought firmware was the same as ROM?
3. After unlocking my bootloader with S-ON, I can install any custom ROM right? or Are there only certain ROMS that are available for S-ON phones?
Click to expand...
Click to collapse
2)no they are different.firmware is flashing in a different partition and the rom in a different too
3)you can install any custom rom you want but you must have the appropriate fw version to boot a rom
if you have a gingerbread fw version you can install only gingerbread roms,if you have 3.32fw or 3.33fw you can install any ics or jb roms
but remember for S-ON devices use 4ext recovery to flash any rom and before flashing enable smartflash from it
edit:actually for S-OFF devices too it is better to have 4ext(but no need for smartflash)
about the first question i am still thinking the right answer
maybe someone else can tell you
rzr86 said:
2)no they are different.firmware is flashing in a different partition and the rom in a different too
3)you can install any custom rom you want but you must have the appropriate fw version to boot a rom
if you have a gingerbread fw version you can install only gingerbread roms,if you have 3.32fw or 3.33fw you can install any ics or jb roms
but remember for S-ON devices use 4ext recovery to flash any rom and before flashing enable smartflash from it
edit:actually for S-OFF devices too it is better to have 4ext(but no need for smartflash)
about the first question i am still thinking the right answer
maybe someone else can tell you
Click to expand...
Click to collapse
technical definition of a rom: Rom stands for Read Only Memory and technically speaking it refers to the internal storage of a device which is supposed to contain the operating systems instructions.the instructions are stored in read only memory,, firmware is the read only operating systems that stay firmly inplace without modification access to the users of the device, firmware in computing is a software that is embedded in a hardware device. it is often provided on flash roms or is a binary image file that can be uploaded onto a existing hardware by a user. firmware is identified as the computer program in a read only memory or ROM integrated circuit.a hardware part number or other configuration identifier is usually used to represent the software. firmware is required for the rom. basically the firmware is the operating system containing the android operating system .hope this helps .best wishes

Questions about unlocking

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.

Categories

Resources