Develop Bugs

Why we are going to fail.

There are a few reasons why we aren't going to port another os to this phone and why we aren't going to see Apps on this phone.
1. How many SKILLED programmers/developers do we actually have willing to put the time and effort into this phone. Not many, if any at all.
2. We are lacking some type of structured development process. Everyone running around trying to do things on their own isn't going to work.
3. Lack of Kin owners. How many people honestly own a Kin? Not too many.. Most likely explains the lack of programmers/devs who want to put work into this. None of them own this phone.
Honestly I love this phone, and as much as I'd hate to see it die, we should admit defeat to Microsoft and give up. Unless some skill gets into these communities I'm throwing in the towel.

Also, the developers that we do have don't want to brick their phones... it seems that even a used gen 1 Kin is $100+ on ebay... I don't understand why

Yeah, I'd hate to brick my phone...but my goal isn't to replace the OS...that is what I like about the phone...I would like to be able to develop for the existing OS...how can we make that happen (does anyone know anyone who knows anyone inside Microsoft to hear our plea)? Would be nice to have an SDK or at least upgrade to WP7.

Porting Android to Wave (Replace Bada)

Has anyone tried it yet, what was the outcome?
Is it possible?
Please share your ideas, views and suggestions here.

I think i read somewhere about it, but the project is not continue, unfortunatelly :/
search, maybe you'll find something

Hey Abhishek...
Why do you need to create another thread...??
There are two ongoing threads on the same topic... And if you are interested please head on to those to find out the info about porting android on bada..
Dont create unnecessary threads.... I suggest delete this... or after sometime all we will see in the Bada Section is useless threads....

*facepalm*
Read other topics WWW.ANDROIDPORT.NEt there is the wavedroid project.

Go away and come back when you have some progress for us wavedroid.

Still wondering if wavedroid is a money making exercise or a genuine attempt at getting Android over. The delays don't help the impression this is an exercise being led by folks more eager than actually having the skills to accomplish the task.
I'll be the first to eat my hat if this ever comes to fruition, but I won't be donating anything to something that at this point seems to have only updates on various delays.
Hows this for an interesting post on the JetDroid website...
Not sure why you need the expensive software, it is nice and would help but 95% of the works is already completed for you guys.
To start:
Look for phones with same hardware then use that parts from their android and put the parts into a custom version. You can reuse the /sbin and /system folders from the android sdk virtual machine or if you want better performance use the /sbin and /system of a similar hardware phone android version and just add your init , init.rc , zimage and package this into a rom or dual boot like we do.
CPU:
The wave / Samsung-Intrinsity S5PC110 cpu is much more supported than our s3c6410 and used even by Apple so look at idroid , samsung crespo , HTC 4G android , samsung i9000 for sources for your android files to start from.
Screen:
The screen is possibly the same as S8000 or Spica, wave 3.3" the rest is in other samsung opensource files you just need to mix and match parts.
Obstacles:
The biggest problem might be the cpu and screen + andreno or powervx or Mali display driver but android.so will work until you get to the video driver.
Camera:
Camera is in M910 samsung opensource files / other 5MP camera, there is only a few 5MP camera from that samsung uses so might need to work on the code if you can not find it from a same camera android phone version that is already working.
Now make a good WaveDroid version:
Once you have all this and have it working then you can build a clean custom version of android optmized for your phone. CM for HTC 4G phones might work with almost no or little changes possibly just in the kernel.
The samsung opensource website has the SCH-W850 / SPH-W8500 / SPH-W8550 , this could share some hardware with Samsung Wave as well, similar number codes. Look for a recent code release nov/dec 2010 or later.
Click to expand...
Click to collapse
After reading that, I felt I could almost make an android port myself lol. Clearly there are some very knowledgeable and experienced persons out there.
What really bugs me is the Wavedroid folks have been asking for money for months, yet have shown not a shred of proof they have accomplished anything. Secondly, folks have been asking (rightfully so), why you have not implemented a Paypal widget so people can see just how much money you have raised so far. I know you are using illegal software and thus don't want to let everyone into your inner circle to see the progress, but you have shown and proved absolutely nothing. There are more doubts than positive feelings at the moment.

Please don't let this thread grow to one of two-three pages which is worth nothing, there is already another one just for this purpose

Android port is stuck because programmers dont have any programm to edit the bootloader of wave,so they can not do the port...
If anyone knows any free programm to edit ARM 7 files (like IDA 5.7) please give it to them.
But if nobody knows any programm for this case the have to wait until they have enough money form donations to buy the IDA 5.7
(sorry for my english)

This is outrageous, the fact that you need commercial tools to do what your looking to do clearly denotes your level of incompetence. Look at idroid. i didnt see them asking people for money to buy tools?? And i would say that Apple did a much better job locking down the i range then samsung did with the Wave. If you have stumbled at the starting block just forfeit the race.
Prove to us that you know what the f**k your doing and then you can have your donations.
Generally i supported this project, but then you asked for money. Money changes everything.

sabianadmin said:
This is outrageous, the fact that you need commercial tools to do what your looking to do clearly denotes your level of incompetence. Look at idroid. i didnt see them asking people for money to buy tools?? And i would say that Apple did a much better job locking down the i range then samsung did with the Wave. If you have stumbled at the starting block just forfeit the race.
Prove to us that you know what the f**k your doing and then you can have your donations.
Generally i supported this project, but then you asked for money. Money changes everything.
Click to expand...
Click to collapse
I agree with U

Asking for money, without providing any scrap of proof that anything is even going on, is what irks people here. Not even a simply paypal donation widget exists so folks can see what the $ count is too.
Too many red flags on this one. I know I'm not the first to ask for proof, or even just something other than "we are working it, it'll be done soooooon, give us all your moneys roflwtflolbbq"
So many other android ports happened without need for this software. And also may I point out what seems total ineptitude on the wavedroid team's part. The Galaxy S contains pretty much the identical hardware as the Wave does. In fact you find me a phone that has identical hardware, one running android, the other something else, and tell me we already have as near an android phone as you're going to get. Compared to other port projects, this should have been done in a weekend to be honest.
wavedroid are bogus, and will accomplish nothing just like all the so called Android to Wave projects and groups previously.

I agree with sabian. I don't know a **** about how difficult or easy is this, but i'm pretty sure that there are good developers around here. Why couldn't you start a new project?

I aggre with you guys,it is very odd that they ask for money without doing anythink...
I just posted that if you know any free software that works with ARM7 files it would be good to inform then...
But they have a very good reason to ask for money because if they can not edit the bootloader they can not load anythink else from bada...if they do that the project it would be almost done because wave and galaxy s have similar hardware so with some fixes to scripts they will have a very good androidport to wave..

Hacking WP7 - any REAL beginner guides?

Hi
I'm pretty sure this hasn't been covered off already - well - not to the level of detail I need anyway.
I came to the xda forums after a friend of mine suggested that there were hacks available.
It's clear that 'something' is available, but what I am not finding is:
A) A SIMPLE guide that shows us people totally new to phone 'hacking' how to do it, from start to finish, with minimal lingo and acronyms.
B) An clear and simple explanation on the different 'hacking' options available
C) The reason you would want to do it? From what I can see, the only benefit seems to be a few pointless homebrew apps that you can download - and for the risk involved...why would you chance it?
Don't get me wrong, tinkering in itself is the reason you would want to do it - it's fun - but I can't help thinking that the WP7 side of 'hacking' doesn't offer much reward.
Would really appreciate any advice/help/links with my questions.
Thanks

Did not know whether to bother answering or not but okay. First welcome to XDA, uhhh in easy laymens terms hacking is not for the inexperienced and it is not totally idiot proof so you should have some fair knowledge of the systems and what they do. Don't hack if you need a kindergarten book to explain it all out for ya simple as that. WP is closer too iOS than Android main point being it is the most secure as far as I personally care of the 3, and the system is just as smooth and fluid as iOS. No there are not alot of Homebrew available at the moment, but if you happen to have a phone able to be fully unlocked then you have the option to use many functions that were not available before.
Device specific is where you should such that search block is your best friend, nobody here is going to write a full guide to the whole forum section for every single new hack and crack that comes out. If you want to you are more than welcome.

Thanks pal
I'm ok with the concepts of hacking, just not specifically this OS.
I'm technically minded and do a lot of similar stuff elsewhere, but when it comes to the phone that I use daily, and comntracted for another 12 months with and have no experience with tinkering WP7 - Im slightly more nervous.
I guess my main issue was the d&h forum for WP7. Every sticky/thread is far too long and they all contain a lot of acryonyms that a new WP7 hacker wouldn't understand. So my forum instinct is to look for the sticky that says "start here - everything explained" - but there isn't one?!
It's almost like "where do people start if there is no starting point"?

As far as covering a good amount of info, this post is a good one:
http://forum.xda-developers.com/showthread.php?t=1299134
Don't really think there is a way to avoid all the jargon though, if there is something that isn't explained well it should be simple to find information to fill in the gaps. The terms used are very specific to the environment, so anything returned in a search would probably be relevant.
The most common homebrew option is Interop Unlock, Samsung models of phone are the easiest to unlock. This allows you to use native code that has not been wrapped in a tidy c# class.
The benefit of all this is that your phone is a full fledged computer that by default is locked down like an appliance. Developing additional homebrew apps allow you to get further phone customization out of your device, and therefore the most value out of your purchase.

I for myself thought about unlocking my device considering the risks involve. but I weighed the consequences. Thus, I end up now, having a fully unlocked HTC 7 Mozart with a custom rom. I am happier with my device now, I can do BT transfers, explore the folders within my device, install more applications than the usual apps/games from the marketplace, and tweak my device. One more thing, when my device was still running on stock rom, battery life is shorter, now I have 1.5x the battery life.
MY CONCLUSION: unlock your device's potential
as for the guides, yes it is not really like spoon feeding, but contents of the guides/tutorials are somehow progressive. one can learn from them, so that on the next development, we can do the "hacking" easier since we understood how the process goes. This is why it is called development. Cheers!

before i can give you advice on what hack that you can use, what is the name your device that way there are more specific hacks that we can talk about.

Hi
Thanks for the helpful replies.
I have a HTC Trophy. I'm doing the SD card upgrade next week to start with, so I can finally put all my music on it, so thought i'd look at hacking it at the same time.
Cheers
Sent from my 7 Trophy using Board Express

look at the HTC part of this guide, http://forum.xda-developers.com/showthread.php?t=1271963

lovenokia said:
look at the HTC part of this guide, http://forum.xda-developers.com/showthread.php?t=1271963
Click to expand...
Click to collapse
Looks like a good guide but how am I meant to know if I have a first or second gen phone....there's no definitive list?! And I can't remember what updates I have.
This is a nightmare - I'll give it a miss

check your processor, as far as i know, if your phone has 1.5GHz then it's a gen2, otherwise, it's just gen1

Let me at least give the "legitimate" talk about unlocking your phone:
For $99/year, sign up for a developers account with Microsoft (create.msdn.com). You can unlock up to 3 separate devices officially for app development. Then you can build and deploy all kinds of .xaps to your phone. To top it off, you can get the betas and early OS upgrades (had Mango almost 6 months before my friend got it from his vendor). Ultimately, you can even release your own apps to the marketplace for sale or for free.
sounds like, since this is a phone you use every day, this might be an investment worth considering. Its an easy and legitimate way for someone not too experienced with the phone's innards to get it unlocked and get exposed to how things work. Plus if you back up your phone vefore you unlock it, and something goes wrong, you haven't done anything thats voided a warranty. If the OS crashes, try returning to the "pre-unlocked" backup and bring it back to the store saying it crashed. They'll replace it. Nice deal, considering most Windows phones run around $500 to replace.
Now as for unlocking it via other means: maybe you dont want to sell apps. Maybe you dont really want to give microsoft a credit card for $100 every year. Maybe you want to just do more than a developer unlock will get you - like load a whole new aspect of the operating system. Or maybe you just dont want to pay to unlock your phone. Understandable, i suppose (though for MOST people, a developer unlock is more than sufficient). There are options, but they will require a lot of time and investigation (maybe even translation) to get it right, because the WP7 is new. The devices are many - its not like having a single hardware baseline to crack - like the iPhone. And to throw another monkey in the wrench, they did a full-fledged update to the OS not 6 months ago. So - no - not a a lot of "beginners" guides out there. Even for experienced people, an unofficial unlock is still a tricky feat. Take a look at the number of posts that have to do with phones randomly "re-locking" themsleves. Hell, I'm a legit developer and my phone "re-locked" itself last night. (turns out MS has a "lease" on deve unlocks that you need to physically update every year by un-registering and re-registering the device)
hope this was informative and helps.

I found exactly the same problem. Today I saw this post in the HTC Titan forum which helped me understand all the different unlocks that you hear mentioned on the web.
Hope this helped

[Q] Replacing Android

So, I've been looking around pretty hard recently and I have yet to see an answer on this that either applies to my phone or is not out of date.
My question is: Is a dev willing to attempt to replace android with Windows Mobile (6.1-6.5) or Windows Phone? Or is this not possible? ( Had seen previous answers stating we needed an unlocked bootloader for this to be an option...which we now have.)
Now some of you may be asking why the hell I'm wanting to replace the OS, and that comes down to the new privacy policy of Google's services and that there are no WM devices w/in the past two years that have a physical keyboard which use the 1700 MHz band for data.
Thanks so much for the help.

hobbiteer said:
So, I've been looking around pretty hard recently and I have yet to see an answer on this that either applies to my phone or is not out of date.
My question is: Is a dev willing to attempt to replace android with Windows Mobile (6.1-6.5) or Windows Phone? Or is this not possible? ( Had seen previous answers stating we needed an unlocked bootloader for this to be an option...which we now have.)
Now some of you may be asking why the hell I'm wanting to replace the OS, and that comes down to the new privacy policy of Google's services and that there are no WM devices w/in the past two years that have a physical keyboard which use the 1700 MHz band for data.
Thanks so much for the help.
Click to expand...
Click to collapse
It is very hard to port a different OS. Possible, but very hard.
But as for the privacy policy, you understand that it basically makes Google have the SAME policy as Microsoft and Apple right? And you can opt out of many of the changes?
The media got that story and turned it into something it wasn't. Google can use your data to improve your experience in its other services. Just like Microsoft says it does.....only difference is they hide it in a wall of text, Google came out and told you.

Also, think that Windows Mobile/Windows Phone are closed-source OSes, while Android is Open Source. Even though, look how hard it is to port Ice Cream Sandwich to our device - an Android OS.
Porting another system with no drivers or access to source code would be next to impossible.

This has been asked a bunch and always answered with either no it can't work or why would you want to.
Don't think its possible
And its not that ics is super hard to port..its the fact that it hasn't been released for more than a couple devices. As soon as htc releases the official dhd ics things should go a lot smoother
Sent from my HTC Vision using xda premium

Nospin, I do know that the policy is basically the same for Google as it is for Microsoft or Apple. And i really do like that they came out and said it as opposed to the EULAs of the others. I am also aware I can opt out of Google's services by not signing in on my desktop, but not on Android. I am required to be logged in to use things on the device like the market. Even for free apps, I have to be signed in to download them. Then, most of them also only provide downloads via the market, so I can't go to their site and buy them or get them (or updates.)
I am well aware it is difficult to port a different OS to a device, but I also know it's not impossible (just next to it.) I also know the question had been asked multiple times. I found 4 different threads under 4 different devices. All of them had different answers. Either "we need an unlocked bootloader", "yes it can be done", or "not possible." Were the answers. With each of the threads being years old I figured asking was the easiest way to get an updated answer.
If open source is the issue, how about loading memo 5, or even a full on version of Linux (vnc solutions don't count.)
I appreciate the responses so far, but I'd also like to hear from a dev on the subject if possible.

HTC HD2 is multiplatform (android,WM 6.5, WP7, ubuntu, meego) but doesn't have keyboard (only bluetooth)

Oh god, the mention of WM 6.X on our device made me throw up in my mouth a little. So obsolete, laggy and unstable. I don't know why you would go anywhere near that garbage.
Porting WM or WP, not "impossible" per se. But so much would have to be built from scratch. No hardware drivers for WP to work on our device, so they would have to be written from scratch. It would be a huge effort, and the fact that WP is closed source, makes it all the more difficult. "Impossible", technically no. But hundreds, probably thousands of hours worth of work. Nobody is really interested in putting that much effort into such a project. And for the reason that you just don't like Google's privacy policy? Sorry, not going to happen.

Dear HTC, can we have our phone back

Before you start to think I am about to scream "GPL, GPL, GPL," stop for a second, take a deep breath, and sympathize with the thousands of power users and developers who have been left in the dark and/or ignored in regard to their device being partially unlocked with a seeming false advertisement. This is an opinionated piece in the regard of actually getting what we asked for and were promised to receive.
Not long ago, users and developers alike relied heavily on hackers and logic to achieve S-OFF to get the full experience of their desire for a great(er) experience on their Android phone. Some people buy an overlay device like HTC with Sense, Motorola with Blur, and so on, knowing what entails when they get it, but they anticipate running a stock experience or a heavily optimized build from one of the developers in this community. Recently we took a moment to talk with ToastCFH and Dees_Troy from TeamWin, who are responsible for HTC Dumlock. HTC Dumlock makes the unlocked device further accessible for a few more phones.
Last week we purchased some T-Mobile One S units for our developers and one of them was chosen to go for a test drive and to try out HTC Dev Bootloader Unlock. This is where we got to know each other and a bit more about HTC's online utility, which nonetheless has disappointed thousands more than just a bit. I am going to let everyone know now: do not plan on just stopping at rooting this and calling it a day, I tried to remove bloat with Root Explorer and came to a brick wall of denial. I found out you also cannot flash custom kernels in recovery mode.
"What is affected in retrospect when I unlock?" Let me answer that: It actually cripples your phone. It's probably less risky to take a chance and go for an S-OFF method that could potentially brick your device. As per numerous reports, and some insight from ToastCFH and Dees_Troy, there is a plethora of issues with this process and many gripes and speculation just coming from myself.
A cobb without a Kernel: Flashing a kernel is similar to trying out walking on coals. You have to do the following (coming from ToastCFH at XDA):
fastboot boot recovery alternaterecovery.img
Here's some thought: If you flash a crap/test kernel that doesn't boot, not only can you not pull the battery you have to relentlessly use your power button to get yourself out of the mess to get the phone to shut off (HTC One series). The reason you can do it through "booting" recovery as opposed of using the one you flashed: The boot method is actually using the boot/temp partition, which in the end, is not really the boot partition.
HTC, why are you doing this? Aren't you supposed to be trying to deter users from chasing exploits and trying to gain S-OFF? It sure doesn't seem like it. From this perspective, it seems you will be are pissing off and running away potential customers instead. The image you see above is the warning you receive in HBOOT after unlocking the device via HTC Dev. Note that it doesnt say "unlocked" but a very menacing "Tampered," a word that carries a different set of connotations altogether.
All your system are belong to HTC: ROM Manager uses a script to replace your recovery while in Android. The slight issue is, it requires root. Root is the center of the development universe when it comes to ROMs, kernels, mods and the likes of the bunch. HANDS DOWN, most of the alterations you make to your phone while booted in Android utilize root and the system partition. This is not only a P.I.T.A., it can be a deal-breaker. I will get to that point in a bit. First, let's take a look: How do I tinker with something if the manufacturer tells me I can but in reality I can't? Conundrums. It's amazing: You cannot remove the bloat from your phone, you cannot replace the recovery and you sure cannot replace the boot image while booted in Android/Sense.
Radio killed the kernel dev star: Yes, radio. Those cool P*IMG.zip files you flash in HBOOT, that's out the window... Unless you get an RUU (ROM Update Utility) and go back to the stock firmware. With older HTC devices with S-OFF, you could slap a P*IMG.Zip (essentially a firmware/radio update in HTC's update.zip format) on the SD card and boot into HBOOT. It would check and flash it for you. That whole proces is gone; this entire process of being able to do this on the mobile side is now gone. You will now need a computer to flash the file.
To need or not to need... That is the question: Toast brings up another excellent point: If these measures have to be in place (maybe due to carrier request) why not provide the proper documentation to support the device? We're pretty sure when someone unlocks this device they understand they are giving up any firmware support from HTC.
Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
- ToastCFH
An excellent point, and most of you will probably agree with his bomb of logic. At the end of the day, he is right; the unlock method is crap and we find it more of a hinderance and crippling intent rather than a compliance to the developer community who has made them the number one development device for so long. Recently Samsung has taken the torch and led its dedicated developers with fulfilled promises and standards.
HTC, why would you do this? That is far too easy. Clarification, reason, justification, etc., it isn't needed. It's about doing the right thing. HTC has kept the proverbial sprinklers on and now the unlock tool is watered down. My advice for the power user/modder/dev is that this tool is essentially useless. We have been the number one spot for developer support by giving free devices to developers and UI designers to make the device even more fun and unique. We will continue to support, drive, and advocate open development on a supposedly open platform and follow those who make it what it is today. With that being said, it makes us skeptical in giving devices to people that HTC seems to have set a navigation route to Failure Avenue, and know that the developer on hand won't feel shorted. HTC, let us own our devices. Some love the hardware, some love the software, but in the end we love Android.
Lastly, GPL. It is is not made to stretch the maximum time available and take your time. It is probably a good suggestion to set up an HTC gitweb or something of the nature to ensure that when the device is available, the developers that you "support" so much can have free reign at improving your device and moving forward at their own pace. That making the final connection to the developer house, letting the user and developer free you from providing software support. Release the source, fully alert and vigilant. We know it takes time to clean code, but the One X (international) community could really use some tasty kernel source code right about now.
One last note: HTC may not be able to further assist with the firmware/software/OS once unlocked, but you can still support your hardware by giving some documentation on how to proceed with an unlocked device. Giving someone a flashlight with no batteries in a dark house isn't an ideal method of answering our call.
Sincerely,
Your Customer.
If you read this, please take a moment and support your developers and modders that enhance your phone life everyday, by tweeting, sharing or posting on Facebook the following quote:
" @HTC we want our phones back! http://tinyw.in/LNSn "
Thanks to everyone who has read and contributed to this piece.
****
My contribution.

I made it about 60% through and I still don't see s-off released. ;p

acer73 said:
Before you start to think I am about to scream "GPL, GPL, GPL," stop for a second, take a deep breath, and sympathize with the thousands of power users and developers who have been left in the dark and/or ignored in regard to their device being partially unlocked with a seeming false advertisement. This is an opinionated piece in the regard of actually getting what we asked for and were promised to receive.
Not long ago, users and developers alike relied heavily on hackers and logic to achieve S-OFF to get the full experience of their desire for a great(er) experience on their Android phone. Some people buy an overlay device like HTC with Sense, Motorola with Blur, and so on, knowing what entails when they get it, but they anticipate running a stock experience or a heavily optimized build from one of the developers in this community. Recently we took a moment to talk with ToastCFH and Dees_Troy from TeamWin, who are responsible for HTC Dumlock. HTC Dumlock makes the unlocked device further accessible for a few more phones.
Last week we purchased some T-Mobile One S units for our developers and one of them was chosen to go for a test drive and to try out HTC Dev Bootloader Unlock. This is where we got to know each other and a bit more about HTC's online utility, which nonetheless has disappointed thousands more than just a bit. I am going to let everyone know now: do not plan on just stopping at rooting this and calling it a day, I tried to remove bloat with Root Explorer and came to a brick wall of denial. I found out you also cannot flash custom kernels in recovery mode.
"What is affected in retrospect when I unlock?" Let me answer that: It actually cripples your phone. It's probably less risky to take a chance and go for an S-OFF method that could potentially brick your device. As per numerous reports, and some insight from ToastCFH and Dees_Troy, there is a plethora of issues with this process and many gripes and speculation just coming from myself.
A cobb without a Kernel: Flashing a kernel is similar to trying out walking on coals. You have to do the following (coming from ToastCFH at XDA):
fastboot boot recovery alternaterecovery.img
Here's some thought: If you flash a crap/test kernel that doesn't boot, not only can you not pull the battery you have to relentlessly use your power button to get yourself out of the mess to get the phone to shut off (HTC One series). The reason you can do it through "booting" recovery as opposed of using the one you flashed: The boot method is actually using the boot/temp partition, which in the end, is not really the boot partition.
HTC, why are you doing this? Aren't you supposed to be trying to deter users from chasing exploits and trying to gain S-OFF? It sure doesn't seem like it. From this perspective, it seems you will be are pissing off and running away potential customers instead. The image you see above is the warning you receive in HBOOT after unlocking the device via HTC Dev. Note that it doesnt say "unlocked" but a very menacing "Tampered," a word that carries a different set of connotations altogether.
All your system are belong to HTC: ROM Manager uses a script to replace your recovery while in Android. The slight issue is, it requires root. Root is the center of the development universe when it comes to ROMs, kernels, mods and the likes of the bunch. HANDS DOWN, most of the alterations you make to your phone while booted in Android utilize root and the system partition. This is not only a P.I.T.A., it can be a deal-breaker. I will get to that point in a bit. First, let's take a look: How do I tinker with something if the manufacturer tells me I can but in reality I can't? Conundrums. It's amazing: You cannot remove the bloat from your phone, you cannot replace the recovery and you sure cannot replace the boot image while booted in Android/Sense.
Radio killed the kernel dev star: Yes, radio. Those cool P*IMG.zip files you flash in HBOOT, that's out the window... Unless you get an RUU (ROM Update Utility) and go back to the stock firmware. With older HTC devices with S-OFF, you could slap a P*IMG.Zip (essentially a firmware/radio update in HTC's update.zip format) on the SD card and boot into HBOOT. It would check and flash it for you. That whole proces is gone; this entire process of being able to do this on the mobile side is now gone. You will now need a computer to flash the file.
To need or not to need... That is the question: Toast brings up another excellent point: If these measures have to be in place (maybe due to carrier request) why not provide the proper documentation to support the device? We're pretty sure when someone unlocks this device they understand they are giving up any firmware support from HTC.
Then why not give us documentation or utilities to flash fimware.zips from recovery like HTC does? When HTC was the proud Nexus device there was full support and documentation available on how to flash firmware on their devices. This made anyone choosing an HTC device blessed with knowing that their device was not only open and unlocked, but when flashing firmware that it was being flashed correctly to Google and HTC's standards. This code has now been moved out of recovery since right before the move to edify scripting and moved to vendor/htc/ (not arguing this choice as thats where it belongs from a maintaining point of view). But the problem is that vendor/htc is proprietary now. Which means Documentation and support for flashing firmware correctly is not available and left to developers of recoveries for the community to figure out. One would think if HTC was standing behind us that they would step up and give us a PROPER/OPEN/REAL unlock, or if they cant for the lame excuse of security concerns, then give us the documentation and utilities to flash the boot and firmware partitions properly. I mean really... what is there to lose there?
- ToastCFH
An excellent point, and most of you will probably agree with his bomb of logic. At the end of the day, he is right; the unlock method is crap and we find it more of a hinderance and crippling intent rather than a compliance to the developer community who has made them the number one development device for so long. Recently Samsung has taken the torch and led its dedicated developers with fulfilled promises and standards.
HTC, why would you do this? That is far too easy. Clarification, reason, justification, etc., it isn't needed. It's about doing the right thing. HTC has kept the proverbial sprinklers on and now the unlock tool is watered down. My advice for the power user/modder/dev is that this tool is essentially useless. We have been the number one spot for developer support by giving free devices to developers and UI designers to make the device even more fun and unique. We will continue to support, drive, and advocate open development on a supposedly open platform and follow those who make it what it is today. With that being said, it makes us skeptical in giving devices to people that HTC seems to have set a navigation route to Failure Avenue, and know that the developer on hand won't feel shorted. HTC, let us own our devices. Some love the hardware, some love the software, but in the end we love Android.
Lastly, GPL. It is is not made to stretch the maximum time available and take your time. It is probably a good suggestion to set up an HTC gitweb or something of the nature to ensure that when the device is available, the developers that you "support" so much can have free reign at improving your device and moving forward at their own pace. That making the final connection to the developer house, letting the user and developer free you from providing software support. Release the source, fully alert and vigilant. We know it takes time to clean code, but the One X (international) community could really use some tasty kernel source code right about now.
One last note: HTC may not be able to further assist with the firmware/software/OS once unlocked, but you can still support your hardware by giving some documentation on how to proceed with an unlocked device. Giving someone a flashlight with no batteries in a dark house isn't an ideal method of answering our call.
Sincerely,
Your Customer.
If you read this, please take a moment and support your developers and modders that enhance your phone life everyday, by tweeting, sharing or posting on Facebook the following quote:
" @HTC we want our phones back! http://tinyw.in/LNSn "
Thanks to everyone who has read and contributed to this piece.
****
My contribution.
Click to expand...
Click to collapse
Done
Sent from my HTC Desire HD using Tapatalk

Done

I would share it but its got to many bad grammatical mistakes that makes its a hard read plus doesn't specifically request things like S-OFF. The sentiment surely is right though.