Dear HTC, can we have our phone back - HTC One X

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.

Related

A few questions... (Android! Omnia!)

* Mod EDIT *
Thread closed until moderation team has had an opportunity to properly review as a result of soliciting donations.
Hey everyone,
As you may all know, there’s a fairly large demand to put Android on the Omnia. After researching it myself, I decided since no one else is doing it I’ll take the incentive and give it my best shot. Don’t get too excited, since I may not get very far. But before I begin, there’re three questions I have to ask:
*NOTE: I own a Verizon i910 Omnia*
1. How do I extract the bootloader, kernel, and rom from the device? I’ve tried all sorts of rom kitchens and utilities and the things I get are either useless or work but only with i900 roms I downloaded and therefore not very helpful.
2. I need to disassemble WM’s device drivers (for the screen, touchscreen, buttons to start), and port them to a custom Linux kernel (that’s what Android will be placed on top of). What software do you recommend (for disassembling WM drivers for ARM in PE format)? A day’s worth of google searching turned up little to nothing.
3. This will involve flashing my one and only Omnia with bootloaders, kernels, and roms that, in all likelihood, will brick my device as I test it. I read in certain places something about a “jtag” cable. Can I use this to flash data directly to the chips without any kind of software running on the phone? If so, what kind of information can you provide? I don’t really care about my warranty, considering what I’m going to do to it To rephrase the question, what options (besides returning the phone) do I have to recover it if it gets bricked?
If anyone wants to offer their support I’d really appreciate it. I need people experienced with the inner workings of a WM device and also people experienced in Linux, specifically device drivers.
it would be great if you could install the Android OS. but i think we need to wait for the official drivers for Android, even if they would be released by Samsung. i start thinking it is impossible.
I honestly doubt Samsung will go the extra mile for a single product (even one as awesome as the Omnia) and port an entirely different operating system to just one of their products. This is one we're gonna have to do ourself. It is possible to do, I'm just stuck right now because I don't know how to dump the i910's rom, which contains all the device drivers I need to make a full-featured port of Android possible. This is what I need help with. It's really not that impossible, it just takes a bit of work.
Mods, could you move this thread to "development and hacking"? It would probably be seen by the people I want it to be seen by there. Thanks.
hey..dude.. checkup this from this group of ppl @
forum.xda-developers.com/showthread.php?t=431329
may be u can join ..
Hey Guys, I've got an Omnia as well and really really want Android on it. Although I am unable to script. I thought of a way to contribute a bit as well. I set up a website to raise money for the first person or organisation that pulls it off to run Android on the Omnia.
Have a look here:
I chipped in a €100 myself as well to make a start. I hope you guys can contribute some money as well so that it motivates the developers even more.
For the developers out there: "We know you can do it!"
* Mod EDIT *
Link Removed
How can an project be real. If Basics are unknown?
Qualcomm, QCT Tools, Firmware structure etc...
For study:
http://www.4shared.com/file/108584795/bb49ee52/I900_090226.html
Big thanx to barisyalcin.
For Android on Omnia. Good Luck.
The way is the Destination.
Best Regards
Why even bother installing a shell?
the android on the omnia only installs a shell compound, it does not actually convert the omnia into a full fledged Android phone.
I would just scrap it and pick up an actual android phone.

Can non-dev's help in getting Root?

What can us mere mortals do to help get root on the Incredible? Is there something that we should be on the watch for? Many of us, although not devs, have varying degrees of sophistication with this technology.
Check refurbished Inc's coming back with special manufacturer only software?
Watch for certain odd behavior on Inc?
Distributed computing crunch of some kind?
Release the email that was sent to me from an insider at VZW on how to root the Incredible (JUST KIDDING! They snail mailed it to me).
Seriously, I don't know what we can do as a group, but I for one would love to help.
The vetting process among the developer community here must be extremely close to the vest.
I have more than 30 years' experience developing applications, including business apps, middleware, communitcations, web, and mobile devices.
I offered a couple devs a couple of possible leads I found while snooping around. And the offers were either ignored or dismissed out of hand. Because I wasn't "anointed", I guess.
paulhoop said:
What can us mere mortals do to help get root on the Incredible? Is there something that we should be on the watch for? Many of us, although not devs, have varying degrees of sophistication with this technology.
Check refurbished Inc's coming back with special manufacturer only software?
Watch for certain odd behavior on Inc?
Distributed computing crunch of some kind?
Release the email that was sent to me from an insider at VZW on how to root the Incredible (JUST KIDDING! They snail mailed it to me).
Seriously, I don't know what we can do as a group, but I for one would love to help.
Click to expand...
Click to collapse
Patience is all us "comoners" can have to help. I'm afraid that there's really nothing in your list that will help.
Ed Zachary said:
The vetting process among the developer community here must be extremely close to the vest.
I have more than 30 years' experience developing applications, including business apps, middleware, communitcations, web, and mobile devices.
I offered a couple devs a couple of possible leads I found while snooping around. And the offers were either ignored or dismissed out of hand. Because I wasn't "anointed", I guess.
Click to expand...
Click to collapse
1) Newer Kernel Exploits
Status: ???
2) Zip File Fuzzing (Bootloader overflow)
Status: ???
3) Root Level things running
Status: ???
4) Mount internal storage and modify OS
Status: ???
5) Trick from the Desire
Status: We need a signed ROM from HTC to get that to work.
6) Let's put an image on the SD and see if it will boot that
Status: No. It doesn't work
7) Trick from the Evo
Status: No. The Evo depends on some specific stuff that Incredible doesn't have.
8) Fastboot oem unlock
Status: Everyone and their mom tried, doesn't work
9) Flash a new image
Status: No, you and what root?
10)Shoryuken ptrace() exploit.
Status: No. It's been patched.
All of these and more have been tried multiple times by multiple people. If any of your suggestions are on this list then that is why they were ignored. If you truly think you may have a method with any validity that may get us somewhere then irc.freenode.net, ##incredibleroot is where you'll find some of the unrevoked team and some other talented people. Please don't join and ask about root or progress every 1/2 hour either cause that gets old quick.
You got to understand how locked down these devices are...if we don't get a leaked root rom like the Desire and the Evo (Toast's method, not unrevoked which relies on Sprint native software so it won't work on our inc's) root may take a VERY long time.
SoCalMiles said:
there's really nothing in your list that will help.
Click to expand...
Click to collapse
So not even the leaked mail? haha.
Really my list was just a noob's attempt to ask, didn't really think that any of them were legitimate. I was looking for direction from more powerful beings in what to watch for. i.e. the leaked ROM you mention.
Felt like I needed to offer to help. I hate not being able to contribute.
Do folks think that this will be a cat and mouse game with HTC/VZW kinda like with the EVO and a patch being issued so quickly to close the first root method?
Ed Zachary said:
The vetting process among the developer community here must be extremely close to the vest.
I have more than 30 years' experience developing applications, including business apps, middleware, communitcations, web, and mobile devices.
I offered a couple devs a couple of possible leads I found while snooping around. And the offers were either ignored or dismissed out of hand. Because I wasn't "anointed", I guess.
Click to expand...
Click to collapse
I'm sure that wasn't the case (well, depending on who it was... heh). A lot of methods have been tried already and the people coming up and trying new ideas really know the inner-working of the Android platform and how it interacts with the hardware. I could (and have =p) come up with some high-end/low-resource techniques for specific hardware (last worked with the iPhone 3GS/iPod Touch 3rd gen) including AA (almost got up to 4x =p), bit/bump mapping, dynamic lighting and other very boring things to see in code but are pretty looking when used.
Now if someone asked me tomorrow to root those 2 devices, I wouldn't have a clue where to begin. Now your situation may be different, if so don't be discouraged and start posting your ideas here. Now they may still be outright dismissed or ignored, but at least you will get credit for coming up with good ideas =).
SoCalMiles said:
You got to understand how locked down these devices are...if we don't get a leaked root rom like the Desire and the Evo (Toast's method, not unrevoked which relies on Sprint native software so it won't work on our inc's) root may take a VERY long time.
Click to expand...
Click to collapse
I've been wondering about this. Is it possible for a device to be created that is unrootable? Not saying the incredible is but I wonder if it will get to that point or is it like computers where there is no 100% secure computer system and there's always a way to get inside.
Sent from my ADR6300 using Tapatalk
A smartphone is just a compact computer... I mean the Android OS is even a modified version of Linux, so there will always be ways/methods to crack the device somehow. However without insider information/data (and even sometimes with such data) we are all left on the outside, trying to find a way in that can be easily repeated among a vast userbase.
Idk how many of you had an Eris but the only reason the Eris got root is because some guy claimed to work for HTC and he posted a 2.1 Rom on xda, who knows the incredible may be the same way.
most of us want root but have no idea how to achieve it. I think our best chance is some inside help
Sent from my ADR6300 using Tapatalk
I want to know how the hell the evo was rooted before it was even released, yet we are still waiting. It would seem us incredible owners are getting shafted. Now all I see is evo evo evo.
-------------------------------------
Sent via the XDA Tapatalk App
Close thread?
Since the Incredible has been rooted; perhaps this thread should be closed.
http://unrevoked.com/rootwiki/doku.php?id=public:adb_in_recovery

HTC opposing modding, but sure as hell they are willing to take your money!!!

I've been enjoying the custom ROM features for a short while, but when I came across the HTC's desicion to put shipped-roms down, I had to make a statement.
I've contacted HTC about the matter, and the answer I got did not please me, at all. They just ignored the fact that the success(and their money) comes greatly because of the open Android platform, and the eager programmer communities contributing to it. Which is the reason and soul, to promise, for the platform, to get success and long life, in the future.
Their claim stands on the corporate ignorance on that fact I mentioned. As the original binaries are not to be used in any other way, than to give a rescue route, if some customization route takes the wrong turn, and ends in bricking the device. In those occations we could take the step back and restore the original image, into a device, and keep hunting the bug's in custom cooked roms.
So I hope that more people will get in touch directly to HTC, and make them understand that keeping the binaries out in the open, does not steal any money or intellectual property from them, in any way, but is solely to keep supporting the device sales, and the life of the platform as a whole.
Yours truly
sawe
P.S. Sorry for the bad language, I'm not a native english speaker.
I personally think that response is reasonable. They can't guarantee that anything won't go wrong with ROMs other than their own and therefore won't support it.
They don't however try to actively stop it which is why there is such a great community of developers.
Sent from my HTC Desire using XDA App
They don't actively stop modding. They just want to keep their own ROMs safe.
I think they are not reasonable on the matter. Reasonable would be if they give us the possibility to download released ROMs from their web servers.
By taking that possibility away, they deny us to revert back to official version, and by that put a much bigger risk in testing the new mods.
No intellectual property is at risk because official packages are .exe binary files, so no way to missuse them, only ability to flash the device back to factory defaults.
Aren't they taking issue with the fact that the HTC Roms include their copyrighted Intellectual property? THe sense UI and the other apps the HTC develop to go with their devices for example? I don't agree with the HTC tactic here, but just wondering if thats their whole issue?
badgerarc said:
Aren't they taking issue with the fact that the HTC Roms include their copyrighted Intellectual property? THe sense UI and the other apps the HTC develop to go with their devices for example? I don't agree with the HTC tactic here, but just wondering if thats their whole issue?
Click to expand...
Click to collapse
Those binary coded .exe files are only usable to flash the device they are ment. You cannot use the file in any other way.
this thread is aload of crap, htc have the right to take whatever steps they feel are justified to protect there work, if you dont like it dont buy htc simple, but we all know people will buy htc because whatever you think of them they are that best smartphone manufacturer
HTC have more rights than they actually use, agreed this thread is pointless.
Xda could drown under 2 meters of dung and htc wouldn't even notice, or maybe they would just be happy to do away with all the idiots bogging down customer support with questions about froyo and then moaning it's not ready a split second after the android team released it.
not sent from an iToilet
saweboy said:
Those binary coded .exe files are only usable to flash the device they are ment. You cannot use the file in any other way.
Click to expand...
Click to collapse
Sorry, but that just isn't true!
When you run an HTC Android RUU it extracts a file called ROM.ZIP into a temp directory before it starts to flash the phone and you can pull this out and do pretty much whatever you like with it.
Regards,
Dave
foxmeister said:
Sorry, but that just isn't true!
When you run an HTC Android RUU it extracts a file called ROM.ZIP into a temp directory before it starts to flash the phone and you can pull this out and do pretty much whatever you like with it.
Regards,
Dave
Click to expand...
Click to collapse
thats true ive done that using ms process manager when i wanted the stock htc bootanimation.zip
I wonder how much information HTC have syphoned off these and other similar forums without acknowledging it? Essentially we are provided a beta testing service for them at no risk to themselves. They could just look through all the problems folks are reporting with various ROMs and RADIO files and use that info to make them stable.
SimonCraddock said:
I wonder how much information HTC have syphoned off these and other similar forums without acknowledging it? Essentially we are provided a beta testing service for them at no risk to themselves. They could just look through all the problems folks are reporting with various ROMs and RADIO files and use that info to make them stable.
Click to expand...
Click to collapse
I sincerely hope they don't, since 90% of the supposed beta testing here is unscientific at best and plain wrong at worst
not sent from an iToilet
I think HTC would have much more sophisticated testing methods than relying on comments like....
ZOMG!!! THE CAMERA APP FORCE CLOSES, THIS ROM SUX!!!
HTC have every right to protect their intellectual property. In fact they're being very nice with the modding community. If they full exercised their rights then there roms including HTC Sense would be illegal.

The Junkheap – Experimental Device Donations

I've noticed that a some developers (myself included) would be substantially aided in their efforts if they had access to one or more Galaxy S test devices.
I don't know how successful this will be however I've created this thread as a central place for developers to “apply” for device donations and for members to put their (presumably broken) devices up for donation.
My phone is broken, can someone fix it?
If your phone is broken and you want it fixed then a Samsung Service Centre or your place of purchase is the place to get it done. However if for some reason Samsung won't fix your phone then you can list it here and it might inadvertently get fixed, but please make sure you read this whole post very carefully!
Deciding to donate... zero liability!
If you do decide to list a device here regardless of whether you're donating or lending it to someone the developer that you donate/lend it to is in no way liable for what happens to your phone. The purpose of this thread is so users can donate devices for experimental development. As such there is definitely a chance devices could get bricked or permanently damaged (if they're not already). If your warranty isn't already voided then it certainly will be. If you're not willing to accept this then do not donate!
I would like to think that developers who have been donated devices will return the device to the donator upon request, regardless of whether the phone was donated or lent. However, just in case I would like “donators” to make clear what they expect in regards to their donation, whether they intend to donate, lend, donation time-frame etc.
Which developer gets which phone?
I think it should be up to the donator to decide what projects are more worthy or more relevant to the donator. I'm not going to assign phones to projects unless the donator requests that I do so.
How are broken devices useful?
Obviously that depends on what the developer is doing. To some developers a bricked device may be totally useless. However, for developers working on low-level interfacing (JTAG etc.) then bricked devices are basically the perfect test subject.
Shipping the device and costs.
I think it's only fair that people donating their phone shouldn't have to pay the cost to ship the phone to the developer. However, the return shipping costs (if the donator wants the phone returned) should be negotiated on per donation basis.
If the phone turns on the donator MUST disable all security features, in particular the mobile tracker functionality!
Applying/Listing
Developers or donators should fill out the following forms respectively.
--- Developer Application ---
Project Title:
Project Description:
Device Requirements:
Example 1. A Bell I9000M that in the past had access to download mode.
Example 2. Any device that charges.
Location:
Extra Information:
--- Donator Application ---
Donation Type: [Donating/Lending]
Phone Type:
Phone Status:
Example 1. Stuck in boot loop. Never had access to 3-button download mode... even tried the oven!
Example 2. Doesn't respond to power button or charger... it's dead!
Location:
Developer Requirements:
Example 1. Need the device back in a month.
Example 2. If the device gets fixed I would like it returned.
Extra Information:
----------------------------------- Developers -----------------------------------
Benjamin Dobell < celtichazard* (Returned)
dagentooboy
----------------------------------- Donators -----------------------------------
celtichazard -> Benjamin Dobell* (Returned)
Bold - Assigned
Regular - Unassigned
* - Lent
Project Title: Heimdall (and JTAG Research)
Project Description:
Heimdall is an open-source, cross-platform replacement for Odin. It is currently in alpha and is in need of testing. For more detailed information refer to the Heimdall thread.
I'm also interested in doing some JTAG research that will hopefully help bring "fully bricked" phones back to life.
Device Requirements:
Any Galaxy S (or derivative) phone in any state what-so-ever.
Location:
Melbourne, Australia
Extra Information:
I'm good with being lent or donated devices. I'm also happy to return donated devices if I'm able to fix them.
It might be worth also having "qualifications" as one of the things. Because otherwise, even 10 year olds can request phones...
I am concerned about the liability statement though honestly.. I live in Melbourne, but I am concerned that there isn't a reasonable expectation that the mobile will be working when it is returned (but yes, I'd love to see Heimdell succeed). Also, there isn't any clauses which ensure that provide leverage for mobile's to be returned.
andrewluecke said:
It might be worth also having "qualifications" as one of the things. Because otherwise, even 10 year olds can request phones...
Click to expand...
Click to collapse
I don't think it should be up to me to decide who is qualified. However I will add something to the original thread that makes it clear it is the donators choice as to who they donate to (I'm not going to automatically assign phones to people).
Lending
--- Donator Application ---
Donation Type: Lending
Phone Type:Samsung Galaxy S i9000 european version
Phone Status:
Stuck in boot loop. Never had access to 3-button download mode... even tried the oven!
Location: Country : Mexico State: Chihuahua City: Juarez
Developer Requirements:
If the device gets fixed I would like it returned.
Extra Information: The device was flashed with AT&T Rom
celtichazard will be lending me his bricked phone so that I can perform some JTAG research into unbricking Galaxy S phones.
If anyone is interested in this research and would like to donate to help cover the cost of shipping, JTAG adapters, wires, components, solder etc. that would be very much appreciated.
The Junkheap sounds like a really good idea .
The JTAG research you are talking about; I have no clue what it is. Is it also related to your Heimdall project? Because that did sound interesting.
Also, I checked out your website at the donate link, and the subjects are so horribly technical, I have no clue what that is about either. So I guess it must be really low-level high-tech ^^.
Edit: donated a little bit. Heimdall could potentially be very practical for all of us .
jjwa said:
The Junkheap sounds like a really good idea .
The JTAG research you are talking about; I have no clue what it is. Is it also related to your Heimdall project? Because that did sound interesting.
Also, I checked out your website at the donate link, and the subjects are so horribly technical, I have no clue what that is about either. So I guess it must be really low-level high-tech ^^.
Edit: donated a little bit. Heimdall could potentially be very practical for all of us .
Click to expand...
Click to collapse
First of all, thank you very much for the donation.
The research that I'll be doing with celtichazard's phone is in regards to finding a way to unbrick any bricked Galaxy S phone. The research is not immediately related to Heimdall. However, if I do manage to work out how to unbrick a phone it will definitely be beneficial for everyone. It will also have a positive effect on the development of Heimdall, as it will allow me to try more experimental functionality without worrying about having to send my phone off to the UK for repair if something goes wrong.
Project Title: JTAG
Project Description:
Trying to figure out a way to unbrick "fully bricked" phones.
Device Requirements:
Any Galaxy S (or derivative) phone in a "fully bricked" state.
Also a fully working one would be nice so I can dump the bootloader.
Location:
Madrid, Spain
Extra Information:
JTAG can bring a bricked phone back to life. If I figure out how to make this work your phone will be fully working. If not then it will still be bricked. I would be willing to return the phone in whatever state it is in when I am done. If you are in the United States a USPS flat rate priority mail box to me is $15. If you have a device that you want to ship let me know and if I need it I will pay for shipping one way.
andrewluecke said:
I am concerned about the liability statement though honestly.. I live in Melbourne, but I am concerned that there isn't a reasonable expectation that the mobile will be working when it is returned (but yes, I'd love to see Heimdell succeed). Also, there isn't any clauses which ensure that provide leverage for mobile's to be returned.
Click to expand...
Click to collapse
I only just realised you edited your post.
The liability statement is mostly in place to ensure developers aren't held responsible for damage (which may or may not have been their fault) or postage related issues.
I understand your concerns in regards to having the device returned, but quite simply there is absolutely no way to enforce such a policy. International law is largely a myth so attempting to enforce any such clause would be near impossible. If you're donating to someone within the same country then you certainly could write-up a contract. I'm not a lawyer, but if a donator wants to organise such a contract with a developer then they're certainly free to do so.
The best thing you can do is to make sure you donate to a reasonably well known developer. If the person you're donating to has a reputation to uphold then you've definitely got some leverage if things get nasty.
Regardless I sincerely hope that we won't see that sort of situation here.
dagentooboy is still looking for someone to donate or lend him a phone. His JTAG research is similar to the work I'll be doing and is extremely important. The more people we have working on it the more likely we'll come across a fix.
If someone has a bricked phone they are willing to donate/lend that would be fantastic.
I suggest to link the developer requests and the donator offers in the first post.
This should help to get a faster overview what is needed/offered.
The link to each post is in the upper right corner of each post.
And i would suggest to use this junkheap for all SGS phones (captivate, vibrant, epic 4g, fascinate & i9000), because most of rom/kernel mods could easily be ported to all sgs phones and development would be faster if developers could have access to all sgs phones.
neldar said:
I suggest to link the developer requests and the donator offers in the first post.
This should help to get a faster overview what is needed/offered.
The link to each post is in the upper right corner of each post.
Click to expand...
Click to collapse
Great idea, I just finished updating the first post.
neldar said:
And i would suggest to use this junkheap for all SGS phones (captivate, vibrant, epic 4g, fascinate & i9000), because most of rom/kernel mods could easily be ported to all sgs phones and development would be faster if developers could have access to all sgs phones.
Click to expand...
Click to collapse
Yeah all phones are accepted depending on what particular developers are after. However thus-far I believe myself and dagentooboy have been willing to accept any SGS phone (including derivatives).
yeah any GSM galaxy s phone would be fine... if it is CDMA I won't be able to test the cell side (to make sure I didn't break it).
Project Title: UnBrickable Mod
Project Description:
An end user solution to unbricking fully bricked phones with only a wire and soldering skills
Device Requirements:
an i9000 device which can have the processor removed and not replaced.
Location:
Louisiana, USA
Extra Information:
UnBrickable Mod has been performed on the Captivate and I'd like to get this modification out to you guys in the i9000 sector. This mod allows you to flash bootloaders and not think twice. Thereby increasing development and allowing for repurposing of our phones at the end of their lives as a Ubuntu device, or similar.
This modification will be fully documented and open-source. It will help the entire community get out of a jam without any additional hardware if they have the skills to solder two points on the board. I must locate these points and it requires removal of the processor. I can return the device which will be inoperative if required.
See video for explanation of how easy it will be to unbrick with UnBrickable Mod.
The execution of a single device will allow resurrection of all others.
Project Title: Thor (an alternative to Heimdall)
Project Description:
Thor is aiming to be more stable and up-to-date.
Here is an XDA thread about it.
Here is a list of new features that I want to test:
1) Ability to flash from BL/AP/CP/CSC .tar archives directly
2) Ability do download latest firmware and flash it automatically
3) Ability to flash compressed (.lz4) files directly (newly discovered)
4) You can shut down the device from GUI immediately (no reboot)
5) PIT viewer built-in, with more accurate information
6) Ability to do NAND Erase All (actually it just erases userdata)
7) Ability to do DevInfo (information about the device: model, carrier id, region, serial code)
Device Requirements:
1) Any Samsung device with Odin v3 protocol
2) Lending only, as my parents would tell me to **** off
Location:
Obviously you don't need this.
Extra Information:
None
Project: PostmarketOS, UBPorts on galaxystmd
Old device: but I have multiple. Willing to send one to device to multiple developers with experience and desire to port for proof-of-concept and/or restoring functionality to this device via mainline Linux (PMOS).
UBTouch would be a secondary effort: as it had been ported during the initial launch, but did not get migrated to the UBPorts project.
3rd effort would be porting latest Lineage, modded/optimized ROM, stripped down/optimized kernel. "One final rodeo."
1 Device per person Per Effort.
So realistically I would give each person up to three devices.

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

Categories

Resources