[Q] S-off One X+ - HTC One X+

i have been reading about the new HTC One X+. so far i have understood S-off is still unavailable, so was wondering can you still change roms with s on. i have rooted my phone. i seen people say you have to update your hbootloader to 1.36 is that true? trying to avoid bricking my phone lol if that was to happen. id like to be ready for the cm10 for att when it is released, or would international owrk in the us on att carier?

rorreo said:
i have been reading about the new HTC One X+. so far i have understood S-off is still unavailable, so was wondering can you still change roms with s on. i have rooted my phone. i seen people say you have to update your hbootloader to 1.36 is that true? trying to avoid bricking my phone lol if that was to happen. id like to be ready for the cm10 for att when it is released, or would international owrk in the us on att carier?
Click to expand...
Click to collapse
Its almost impossible to brick an HTC phone if you know what your doing. The basic rule is make sure your flashing for the correct device because in each market each phone is a little different. On the original One X, the international versions partitions were different than the XL's partitions so if you flashed the wrong recovery it wouldn't boot because the recovery partition would be where root should be (just an example and on top of the HOX and HOXL had different hardware). On the X+ its more or less the same. I don't know anything about updating HBOOT but I would strongly discourage it. With every update there is the possibility of loosing the possibility to root; also flashing a new bootloader is VERY risky.. Yes, you can flash new ROMS without S-OFF however depending on the HBOOT version you have to flash the kernel or BOOT.IMG in the zip separately via fastboot. There are programs to do this or you just use adb/fastboot. CM for international won't work on out AT&T devices because of issues with the differences in the radio.
Hope I helped! Press 'thanks' if I did.
-Irish

well i am pretty new at this dev experience and i would like to know more wish i new more and didnt have to ask stupid questions. i dont understand "by however depending on the HBOOT version you have to flash the kernel or BOOT.IMG in the zip separately via fastboot. There are programs to do this or you just use adb/fastboot."
my hboot is 1.32 and bootloader is unlocked and i am rooted. did it a few nights ago. boot img is in any new rom correct? cant stand sense roms. looking forward to using cm10 when its released for att. just thought id prep my phone for it

I think what he's saying is that before you could just copy the rom.zip to your phone and then flash from recovery(because the kernel stuff was included in the rom.zip) but now, because of various things, you have to flash the kernel stuff seperately(usually by extracting it from the rom.zip then running the fastboot cmd as he said). Once you've copied the rom over and flashed the kernel, then you can flash the rom from recovery like usual.
I think that's pretty much it and you don't really need to mess with anything else. But, of course, I'm not an expert by any stretch, so take it with a grain of salt.

What S-ON means for us is that we cannot flash the BOOT partition directly from the phone. This means, that Kernels (boot.img files) need to be flashed via fastboot. S-ON/OFF has nothing to do with changing ROMs, just Kernels.
The reason why we cannot use the same ROMs on ATT/Telus and Intl version of the HOX+ is that the US version has LTE support, which means it has a different radio.
Also i think the newest HBOOT you can get for the HOX+ is 1.35 but be careful with that and make sure you have the right file and correct md5 sum.

I flashed maximus Rom for the one x+ didn't have issue using tarp. The kernel was updatin with the new rom
Sent from my HTC One X+ using xda premium

It worked because it was unlocked by htcdevs
Sent from my HTC One X+ using xda premium

Related

[Q] Help catch a Moto kid up

Alright so I'm coming from a Droid 2. I come from the land of CWR and having to SBF before I could go back to a FroYo ROM from Gingerbread because we couldn't flash kernels.
Basically, this is my very first HTC phone and although its similar to a Moto phone, I am realizing more and more that things are much different. I'm unlocked and rooted running Bamf ICS but I have absolutely no idea what I'm doing lol. With S-OFF now, I want to be careful not to screw up my device and know exactly what I'm doing.
So my questions are...
What is an RUU?
What all is flashable through a recovery with S-Off?
If I don't have S-Off, what is this p(something)img.zip file that I'm always flashing?
Anything else you feel is important lol.
Sorry if this has been well explained somewhere else. I have just been reading through a lot of forums on here and it seems that most people are coming from HTC phones and already know the processes. If someone also coming from a Moto phone has any insights or explanations they would be greatly appreciated
GetRipped said:
Alright so I'm coming from a Droid 2. I come from the land of CWR and having to SBF before I could go back to a FroYo ROM from Gingerbread because we couldn't flash kernels.
Basically, this is my very first HTC phone and although its similar to a Moto phone, I am realizing more and more that things are much different. I'm unlocked and rooted running Bamf ICS but I have absolutely no idea what I'm doing lol. With S-OFF now, I want to be careful not to screw up my device and know exactly what I'm doing.
So my questions are...
What is an RUU?
What all is flashable through a recovery with S-Off?
If I don't have S-Off, what is this p(something)img.zip file that I'm always flashing?
Anything else you feel is important lol.
Sorry if this has been well explained somewhere else. I have just been reading through a lot of forums on here and it seems that most people are coming from HTC phones and already know the processes. If someone also coming from a Moto phone has any insights or explanations they would be greatly appreciated
Click to expand...
Click to collapse
a RUU is a rom update utility that returns you to stock factory settings that is flashed through the bootloader or by .exe file.
With s-off you can flash radios,hboots,splash screens,firmware,recoverys (through bootloader). And in recovery i think just kernels without having to flash the boot.img through adb
Not sure since i dont have this device. But i believe it is the firmware needed to run ICS roms without problems
The PH .img thing is the kernel. If you try to flash a Rom with an incompatible kernel it won't boot. Likewise, if your going between say to gb roma that use the stock kernel, you don't need to mess with the ph thing.
Sent from my ADR6425LVW using xda premium
great to have you here man!! and s-off is great now that we have it. give the devs time and everything will be flashed in a one step process (kernel, rom, boot screens etc)
ph98img.zip is not the kernel ...but it can be...
ph98img.zip's are anything from kernels, spash screens, radios now, etc.
the new ics leaked firmware for example came in ph98img.zip format
it had included a new, ... well everything
so ph98img's are updates you run in the bootloader and dev's package different things in them.
Ok thanks, I'll be getting this phone sometime soon and coming from Moto the process of doing things seem way, way more confusing and more time consuming when it comes to backups and what not. Do you guys recommend when I first get the phone before even setting it all up to unlock BL, perm root, S-Off and flash my Rom of choice then doing a backup? Also are the backups the same as moto, just one click and it makes a zip to flash whenever?
RoryHe said:
ph98img.zip is not the kernel ...but it can be...
ph98img.zip's are anything from kernels, spash screens, radios now, etc.
the new ics leaked firmware for example came in ph98img.zip format
it had included a new, ... well everything
so ph98img's are updates you run in the bootloader and dev's package different things in them.
Click to expand...
Click to collapse
Your right but he's talking about the ones you need to flash with roms, which are all kernels. But right nonetheless could be a 3mb kernel or 600mb ruu
Sent from my ADR6425LVW using xda premium

New to Rezound/ help with rooting

okay well verizon is sending me a certified replacement rezound for my thunderbolt tomorrow (or this morning whatever), and i am wanting to root it and flash newts sense 4 rom (or any sense 4 rom, suggestions?), but im finding it to be a whole lot more complicated than the root/s-off for both my thunderbolt and dinc2. Everywhere I look theres a different method and none of them seem to be as simple as im used to with the rooting of multiple replacements of my other phones. I'm wondering which method is the best to us, http://forum.xda-developers.com/showthread.php?t=1504824, which is the all in one tool, or http://androidforums.com/rezound-al...ys-noob-friendly-root-guide-start-finish.html, which is a manual method. Also, i may be seeing this wrong but neither of these give s off so should i use http://unlimited.io/juopunutbear-public-beta-0-1/ which is a beta s off for the rezound. any help with this would be greatly appreciated.
Also, a question with flashing, is it the same process as the tbolt and dinc2, because in newts dl it has a bootimg to flash and i have seen where other people who say to flash another zip that is old firmware patch, and i never had to do anything with either or those on my old phones.
Basically i just want to be able to flash ROMs so yeah the best way would be great to know. Thanks in advance and sorry for citing a different site than xda
Basically First of all you have to go to HTC Dev and unlock your bootloader and install amon-ra recovery. Flash a SuperSu or SuperUser .zip via recovery to gain root on the stock rom. Make sure USB Debugging is enabled and you can attempt S-OFF.
S-OFF is not complicated at all just time consuming because of the wire trick which has to be timed just right. Once you have gained S-OFF flash one of the ICS radios ... I posted the last two new ones in the radio thread (under the development section). Once you have updated your radio go into recovery and flash which ever sense 4 rom you like. Then if your sdcard/internal are being recognized you flash either oldfirmware or gb fix to change the mount points.
All the files you need to download are
ADB
HTC Sync Drivers
unlock token from HTC
Amon-RA
Su flashable zip (Superuser/SuperSU)
JuntoBear zip
Radios
ROM
SDCard Fix if you have those issues (old firmware or GB fix)
Since the OTA ICS firmware 3.14.605.12 10RD is on my phone, i wont need to flash any ICS radios correct? and also the JuntoBear has a file for the (3.14.605.5 ICS Leak) but not the official update, should i use it anyway?
xxtsxx said:
Since the OTA ICS firmware 3.14.605.12 10RD is on my phone, i wont need to flash any ICS radios correct? and also the JuntoBear has a file for the (3.14.605.5 ICS Leak) but not the official update, should i use it anyway?
Click to expand...
Click to collapse
.5 and .12 have the same firmware, so the JuntoBear software is the same for them.
thanks to you guys im running sense 4! thank you guys so much for all the help. I had a bit of a scare when getting s off but it ended up all good!

[Q] Plan to Flash ROM query....

Apologies in advance but a bit of a newbie question......
I am the recent new owner of an HTC One X+ on the UK Vodafone network and am keen to get Andorid Revolution HD 6.2 running on it rather than the stock setup.
My system as it stands is as follows:-
Android version: 4.1.1
HTC Sense version: 4+
Software number: 1.14.161.18
Kernel version: 3.1.10-g262c6aa
HBOOT: 1.30.0000
CID (Via CID Getter): VODAP001
I have unlocked the bootloader (S-ON) via htcdev.com and gained SuperSU status and flashed TWRP International thanks to hasoon2000's excellent All-In-One Toolkit v2.1 (http://forum.xda-developers.com/showthread.php?t=1994961) and am now a little worried about taking the next step I guess!
I have the ARHD 6.2 rar file downloaded, the flash_boot_6.x_0.1.rar to flash boot.img and I have also downloaded the firmware (1.17.401.1.zip) as per the requirements according to mike1986. from here (http://forum.xda-developers.com/showthread.php?t=1995685).
My plan is to use hasoon2000's Toolkit to flash the boot.img, run the wipe command via TWRP (do I also need to upgrade the firmware using the 1.17.401.1.zip via TWRP - and how do I go about that with no writeable SD card) and then ADB sideload the Android Revolution HD 6.2 ROM but I am hanging fire on this process until I can get a little reassurance that this is the correct approach and will work, I think it's the virtual SD card and the fact I cannot actually have the files sat on an SD card that is making me a little apprehensive.
I hope I'm on the right lines because I was very happy with my Desire HD with Android Revolution HD on it prior to my upgrade and am looking forward to getting back to using the most popular ROM on my new phone!
Any help would be muchly appreciated......and please tell me if any of the above is likely to cause me problems!!
you can not use the firmware zip from mike1986.
you have a Vodafone branded Phone. there are no Updates for hboot.
(Check the CIDs at the thread)
skdubg said:
you can not use the firmware zip from mike1986.
you have a Vodafone branded Phone. there are no Updates for hboot.
(Check the CIDs at the thread)
Click to expand...
Click to collapse
Thanks skdubg,
yeah i had looked at that and that was my main concern.
so since mike's rom requires hboot 1.35 i have to wait for vodafone to release a software update from hboot 1.30 to 1.35?
were this to happen would i then be in a position to flash a custom rom (provided the CID appeared on the list of course) or is the fact it's a branded phone a complete sticking point?
pablihno said:
Thanks skdubg,
yeah i had looked at that and that was my main concern.
so since mike's rom requires hboot 1.35 i have to wait for vodafone to release a software update from hboot 1.30 to 1.35?
were this to happen would i then be in a position to flash a custom rom (provided the CID appeared on the list of course) or is the fact it's a branded phone a complete sticking point?
Click to expand...
Click to collapse
As long as you have the latest hboot you can flash any custom rom. It's not your CID preventing it. Problem is vodaphone does not usually release RUU's and if you flash a custom rom and end up with glitches/errors because you have an older hboot. There is no way to return to stock (except a nandroid).
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
As long as you have the latest hboot you can flash any custom rom. It's not your CID preventing it. Problem is vodaphone does not usually release RUU's and if you flash a custom rom and end up with glitches/errors because you have an older hboot. There is no way to return to stock (except a nandroid).
Click to expand...
Click to collapse
Thanks for the explanation AndroHero, I was under the impression if things didn't match up entirely then there was a risk of bricking.
So my best plan of action would be:-
1. Create a full nandroid of my system as it stands from TWRP
2. Flash the boot.img relating to the custom rom
3. Sideload and flash the custom rom through the All-In-One Toolkit
4. See how I get on!
Either that or stick with stock I guess...
Yeah you shouldnt run into too many issues doing it that way. There is a million in one chance of bricking your phone flashing a rom with any hboot. Infact while S-On doing anything wont "brick" your phone. As long as you have a backup to return too. You'll be fine
You dont need to "sideload" the rom, just boot into android on your voda rom, connect to pc, and copy the rom .zip to the root of the device that appears.
Sent from my HTC One X+ using Tapatalk 2
AndroHero said:
Yeah you shouldnt run into too many issues doing it that way. There is a million in one chance of bricking your phone flashing a rom with any hboot. Infact while S-On doing anything wont "brick" your phone. As long as you have a backup to return too. You'll be fine
You dont need to "sideload" the rom, just boot into android on your voda rom, connect to pc, and copy the rom .zip to the root of the device that appears.
Click to expand...
Click to collapse
Cool, well that makes me feel a bit more confident about going further, thanks.
I would usually take that route but with the "virtual sd" i seem to be having issues writing directly to the device through windows explorer despite the device appearing it tells me the "Device has either stopped responding or been disconnected" every time I attempt to copy straight to the internal storage - that's the only reason why I'm thinking I need to "sideload" the rom.zip

Confused about rooting

Hey guys,
I'm a long time android user,I've dealt with HTC mytouch 4g and evo then moved on to Motorola droid razr and then the gs3,I came back to HTC because their phones feel more better in the hand and have better specs in my opinion. I've rooted plenty of phones and I have one question,I'm seeing a lot of instructions of how to unlock,s-off but one thing that doesn't make sense is loading a boot.img for every rom? If I'm correct,I have to flash any given Rom and then flash a boot.img and then do a different method for a custom kernel? I thought I could load a custom Rom and a custom kernal in a custom recovery? Please forgive me for asking a lot of questions but it seems the whole custom Rom methods has changed for specifically HTC phones? Is all this due to locked bootloaders?
Sent from my HTC6435LVW using xda premium
ali87va said:
Hey guys,
I'm a long time android user,I've dealt with HTC mytouch 4g and evo then moved on to Motorola droid razr and then the gs3,I came back to HTC because their phones feel more better in the hand and have better specs in my opinion. I've rooted plenty of phones and I have one question,I'm seeing a lot of instructions of how to unlock,s-off but one thing that doesn't make sense is loading a boot.img for every rom? If I'm correct,I have to flash any given Rom and then flash a boot.img and then do a different method for a custom kernel? I thought I could load a custom Rom and a custom kernal in a custom recovery? Please forgive me for asking a lot of questions but it seems the whole custom Rom methods has changed for specifically HTC phones? Is all this due to locked bootloaders?
Sent from my HTC6435LVW using xda premium
Click to expand...
Click to collapse
yeah the whole s-on and off creates some confusion but you can have s-on and still flash custom recoveries and kernels,
I havent really found a need to achieve s-off yet (probably when the unofficial cm10 release is complete i will), but i would leave s-off.
Having to flash roms is easy and pretty straightforward. I also had trouble with flashing kernels in which case you flash the boot image and then flash the zip. It also depends how they are packaged, because the boot.img is sometimes packaged in the zip in which case you have to unzip it to get the img and the zip and then flash the new zip after the img.
I've also been an android user a decent amount of time but it seems like htc devices are slightly more complicated.
almo40192 said:
yeah the whole s-on and off creates some confusion but you can have s-on and still flash custom recoveries and kernels,
I havent really found a need to achieve s-off yet (probably when the unofficial cm10 release is complete i will), but i would leave s-off.
Having to flash roms is easy and pretty straightforward. I also had trouble with flashing kernels in which case you flash the boot image and then flash the zip. It also depends how they are packaged, because the boot.img is sometimes packaged in the zip in which case you have to unzip it to get the img and the zip and then flash the new zip after the img.
I've also been an android user a decent amount of time but it seems like htc devices are slightly more complicated.
Click to expand...
Click to collapse
I think a lot of people (like me) got into rooting phones where the phone we owned already had s-off and as such all the roms we were flashing were made while that was true. The DNA has only recently had s-off so most of the roms were made with s-on being the only option.They needed the boot image flashed seperately to work. My understanding now is even with s-off, if the rom was made prior to s-off, you still have to flash an image file. Probably soon enough most will not need that extra step.
In a simple nutshell, the s stands for security flag, and prevents access of the boot partition from recovery, as well as low level stuff like firmware.
Turning security off, known as s off, allows a user to write to the boot partition (like a boot.img) and write firmware such as the radios (telephony and modem firmware) from recovery.
So s off has pros and cons. It's there as a protective measure, and being s on slows the HTC Dev bootloader tool to be a reality and still have a safety measure in place for the general public that doesn't know squat and doesn't follow the forums or keep up with their device's software.
Sent from my ADR6425LVW using Xparent Red Tapatalk 2

[Q] HTC Amaze wont boot up!!!!

Hello
I have an Amaze 4G x715e
Yesterday i unlocked the bootloader and installed twrp recovery. Then i went to install cm10 rom. First i took nandroid backup of my stock and when cm10 finished installing it hangs at "welcome- select language" and then restarts !!!
how can i restore my backup if I m on s-on. there is no disc image file in backup folder as all are win files. when i restore same thing happens phone keeps on restarting!! but doesnt boot.
my Hboot version is 1.92.000
S-on
Pls help what should i do ?????
thanx
I had this exact same problem.
It is because you are S-ON and do not have SuperCID
Use this thread to get your device working again!!!!!!
http://forum.xda-developers.com/showthread.php?p=46376931#post46376931
I would suggest trying to get S-OFF using Ubuntu and then doing SuperCID
If you cannot attain S-OFF, there is a rom that worked for me perfectly I will link you to.
http://forum.xda-developers.com/showthread.php?t=2482651
I still highly suggest that you get S-OFF and SuperCID before you flash any more roms.
Here is a full guide on how to get it
http://forum.xda-developers.com/showthread.php?t=2167596
help me out please
Darin_Ram said:
I had this exact same problem.
It is because you are S-ON and do not have SuperCID
Use this thread to get your device working again!!!!!!
http://forum.xda-developers.com/showthread.php?p=46376931#post46376931
I would suggest trying to get S-OFF using Ubuntu and then doing SuperCID
If you cannot attain S-OFF, there is a rom that worked for me perfectly I will link you to.
http://forum.xda-developers.com/showthread.php?t=2482651
I still highly suggest that you get S-OFF and SuperCID before you flash any more roms.
Here is a full guide on how to get it
http://forum.xda-developers.com/showthread.php?t=2167596
Click to expand...
Click to collapse
Hello,
I am currently downloading Sultan ROM 2.0 because i am S-on and forgot to backup the original OS. (basically empty phone, I think) However, I managed to get TWRP 2.6 on for recovery. After I get the ROM and move it on to the SD card, I should install it from TWRP, right? (removing cache, dalvik etc) Hope I get back and running so I can get build out of source codes.
My question is, is kernel compile(from source) for HTC amaze x715e (the asian HTC amaze?) is possible or not.
I believe the kernel source that HTCdev site provides is only for HTC amaze 4G. (or is it the same?)
Thanks in advance.
spencerjang90 said:
Hello,
I am currently downloading Sultan ROM 2.0 because i am S-on and forgot to backup the original OS. (basically empty phone, I think) However, I managed to get TWRP 2.6 on for recovery. After I get the ROM and move it on to the SD card, I should install it from TWRP, right? (removing cache, dalvik etc) Hope I get back and running so I can get build out of source codes.
My question is, is kernel compile(from source) for HTC amaze x715e (the asian HTC amaze?) is possible or not.
I believe the kernel source that HTCdev site provides is only for HTC amaze 4G. (or is it the same?)
Thanks in advance.
Click to expand...
Click to collapse
You're asking many things that can easily be found on the threads that are pinned to the top of the the various forums here. Before proceeding I strongly suggest you read them first, because judging by the content of your post you are getting ahead of yourself and are already heading for serious problems. If you are s-on with an Asian or unbranded Amaze you will soon find yourself with an expensive paperweight if you continue along your current path.
You must first attain s-off and SuperCID before flashing an ICS ROM, and you must first flash a factory ICS ROM image before you can flash an after-market ROM like Sultan. This is because none of the after-market ROMs have radio basebands, and without an ICS radio you won't have communication or data with any ICS and newer ROMs you may flash. Also TWRP is practically useless on an S-on handset because it will be unable to flash a kernel image, so it won't boot-up.
As I said, read all of the pinned threads located at the top of the various forums here, all of the info you seek is located there, including links to other posts with important information. In a nutshell you will need to proceed as follows: You will have to flash back to the appropriate GB ROM for your handset. Then if you haven't already, go to the HTC-dev site and get the binary unlock blob and save it (you will need it again). Attain s-off and SuperCID. Once these have been successfully accomplished you must flash a factory ICS image to get the radio. Once you have the proper ICS radio and you're s-off you can flash any ROM you like.
Cutting corners will only cause problems for you later, then your next post will be a cry for help in the Amaze unbricking project thread.
Good luck.
spencerjang90 said:
Hello,
I am currently downloading Sultan ROM 2.0 because i am S-on and forgot to backup the original OS. (basically empty phone, I think) However, I managed to get TWRP 2.6 on for recovery. After I get the ROM and move it on to the SD card, I should install it from TWRP, right? (removing cache, dalvik etc) Hope I get back and running so I can get build out of source codes.
My question is, is kernel compile(from source) for HTC amaze x715e (the asian HTC amaze?) is possible or not.
I believe the kernel source that HTCdev site provides is only for HTC amaze 4G. (or is it the same?)
Thanks in advance.
Click to expand...
Click to collapse
Okay so as @Odysseus1962 said, you need to get S-OFF and SuperCID first.
And TWRP is useless in this scenario because it does not have smartflash, which like Ody said, can flash kernel images.
Really there's limitations to what you can do right now. I think if you find an Asian GB RUU to flash you would be back to your original phone but if you want to be on ICS you need to do everything we told you in the previous post. Otherwise you will be very sad for a bricked phone.
Again, follow this thread step by step to get back to a working phone.
http://forum.xda-developers.com/showthread.php?p=46376931#post46376931
Get the phone working first, that is priority. ICS can wait. It is not running away.
Thanks!
Darin_Ram said:
Okay so as @Odysseus1962 said, you need to get S-OFF and SuperCID first.
And TWRP is useless in this scenario because it does not have smartflash, which like Ody said, can flash kernel images.
Really there's limitations to what you can do right now. I think if you find an Asian GB RUU to flash you would be back to your original phone but if you want to be on ICS you need to do everything we told you in the previous post. Otherwise you will be very sad for a bricked phone.
Again, follow this thread step by step to get back to a working phone.
http://forum.xda-developers.com/showthread.php?p=46376931#post46376931
Get the phone working first, that is priority. ICS can wait. It is not running away.
Click to expand...
Click to collapse
Yes you are right, I need to get it back to working before I have ICS or anything. I really don't have any preference about GB or ICS anyways.
I spent about 2 weeks looking for information about this phone but then I found out that this one was the asian version, not the 4G. (Do they have much difference from HTC Amaze 4G?!)
As a newbie, I got confused and understood something wrong and went off to a wrong direction.
Anyways I'll follow with the thread that you've posted.
Thanks again.
New question
Thank you I now have it back to normal.
What I want to do is, I would like to compile the kernel for this device from source. I see that there are several versions of kernel sources in HTCdev site. Should I grab T-Mobile version and compile accordingly? and flash it using Hasoon's Kit?
Compile it from source and thats just it, no more.
Or do I have to go with what @Odysseus1962 said and get SuperCID, S-off and etc??? AND THEN go ahead with kernel compile?
It doesn't matter if the android is GB or ICS. (I think I'll go with GB though)
Thank you.
spencerjang90 said:
Thank you I now have it back to normal.
What I want to do is, I would like to compile the kernel for this device from source. I see that there are several versions of kernel sources in HTCdev site. Should I grab T-Mobile version and compile accordingly? and flash it using Hasoon's Kit?
Compile it from source and thats just it, no more.
Or do I have to go with what @Odysseus1962 said and get SuperCID, S-off and etc??? AND THEN go ahead with kernel compile?
It doesn't matter if the android is GB or ICS. (I think I'll go with GB though)
Thank you.
Click to expand...
Click to collapse
There's an excellent article at xda university about kernel compilation, as well as, several excellent threads in the main development forum on the main board. The HTC sources are a good place to start however you'll need to prepare your build box correctly. This is where the info threads I mentioned come in handy. Compiling the kernel for android requires cross-compilation and installation of the proper toolchain since you're more than likely planning on building from an x86 or amd64 based machine.
As to which sources to select, there are several versions on the HTC-dev site that are directly compatible with the Amaze. However IIRC there is only one that includes the sources for the TI chipset which is required for Bluetooth functionality. That source is the one that's considerably larger than the others and is the one you should use for your build.
You don't need s-off to build kernels since that's done on your PC. You might run into problems installing on your device, but I'm not sure. This is because of a CID mismatch with your build (no CID) and what is expected by the ROM you have installed. It's just a generally accepted idea that if you plan on developing for an HTC device you should be unlocked, s-off, SuperCID, and in the case of the Amaze, on the latest ICS radio baseband. This gives you the freedom to install anything you want, without external limitations on your handset.
The only time this isn't an absolute requirement is if you own a version that came with an ICS image on it or where one is available to install. Since they have the proper radio they can flash any ROM, provided they flash with 4ext recovery with smart-flash enabled. I hope this helps.
Good Luck.
Odysseus1962 said:
There's an excellent article at xda university about kernel compilation, as well as, several excellent threads in the main development forum on the main board. The HTC sources are a good place to start however you'll need to prepare your build box correctly. This is where the info threads I mentioned come in handy. Compiling the kernel for android requires cross-compilation and installation of the proper toolchain since you're more than likely planning on building from an x86 or amd64 based machine.
As to which sources to select, there are several versions on the HTC-dev site that are directly compatible with the Amaze. However IIRC there is only one that includes the sources for the TI chipset which is required for Bluetooth functionality. That source is the one that's considerably larger than the others and is the one you should use for your build.
You don't need s-off to build kernels since that's done on your PC. You might run into problems installing on your device, but I'm not sure. This is because of a CID mismatch with your build (no CID) and what is expected by the ROM you have installed. It's just a generally accepted idea that if you plan on developing for an HTC device you should be unlocked, s-off, SuperCID, and in the case of the Amaze, on the latest ICS radio baseband. This gives you the freedom to install anything you want, without external limitations on your handset.
The only time this isn't an absolute requirement is if you own a version that came with an ICS image on it or where one is available to install. Since they have the proper radio they can flash any ROM, provided they flash with 4ext recovery with smart-flash enabled. I hope this helps.
Good Luck.
Click to expand...
Click to collapse
Thanks again for the quick reply.
I am now done with S-off (wire trick took me like 20 tries ) and getting SuperCID.
Now my bootloader shows LOCKED, hboot 1.92, S-OFF. Then I am going for kernel compile for the exact stock sources.
ruby-gb-crc-2.6.35-4a1059e. (and of course cross-compiled it) Now I have a zImage with me but won't flash with 'fastboot boot zImage'. I'll look for the solutions in the forum.
I have to say sorry for not reading the main threads and making you bothersome.
Thanks again.

Categories

Resources