Database Users

The HTC seems not to unlock the hboot .v.

here!!
(In Traditional Chinese)
Only HTC doesn't seem to unlock the hboot now!!

For those wondering here is a google translate version of the text on the page - that is why it is in bad english
Sony Ericsson last month promotional offer for mobile phone unlocking Bootloader, as it were the entire mobile phone industry has some new territory like. Samsung announced soon also Twitter 『If Google does not oppose, they will also unlock the phone Bootloader』. Motorola has been silent today audible.
Motorola promised by the end of this year's Android device for its offer unlocking services, users can own brush from a ROM.
Now even unlock a Motorola also provides that only four brands in the Android HTC did not respond due to the unknown when it said it will adhere or surrender it.
Click to expand...
Click to collapse

Sounds like HTC made no commnet
So I would say this article is one way or another. Plus maybe something is lost in that translation a little.
HTC, to this point, seems pretty good with being unlocked. I've had my Evolution now since it came out and its fully customized. The new Evolution after it also looks that way. I really thing, aside from Motorola, that the carriers may start being he ones to ask to lock or unlock he bootloaders. ISPs in the US finally out caps on bandwidth last year, I would see locked bootloaders being next. Really time will only tell, but hopefully we get to keep our freedoms. The FCC approved a device is ours when we buy it, therefore we should be able to do what we want. Hopefully companies keep that in mind instead of trying to lock stuff down.
The big business rreason is that an unlocked device lets a user stay with that device longer, as it can be customized wig the latest software features. Unlocked devices really force companies to invest in research to give us better hardware now, costing them more money. As anyway can really developed the software that goes into the phones.
My thoughts anyway...
~Max
√ This Message Sent From CM7 Nightlies HTC-Evo4G ™

Who dictates when we get updates/bootloader? apparently not motorola

Who's to blame for delays on updates like gingerbread or bootloader? lawsuit reveals that google has a lot of control over moto and has final say as to when, how and if things get released. Check out the article below and give your opinions please. I personally refuse to let them keep getting data off of me for free and making money off of me, without atleast paying part of my data fees on my bill or giving me a discount. IMO droidwall/disable there data gathering and just use good old fashioned a-gps(like back on windows mobile) if you need to get a lock on your gps.
t h i s i s m y n e x t . c o m /2011/05/12/google-android-skyhook-lawsuit-motorola-samsung/

aerojoe420 said:
Who's to blame for delays on updates like gingerbread or bootloader? lawsuit reveals that google has a lot of control over moto and has final say as to when, how and if things get released. Check out the article below and give your opinions please. I personally refuse to let them keep getting data off of me for free and making money off of me, without atleast paying part of my data fees on my bill or giving me a discount. IMO droidwall/disable there data gathering and just use good old fashioned a-gps(like back on windows mobile) if you need to get a lock on your gps.
t h i s i s m y n e x t . c o m /2011/05/12/google-android-skyhook-lawsuit-motorola-samsung/
Click to expand...
Click to collapse
Google is not who dictates it generally goes in this order
Carriers
Manufacturers
Google
If you read about Google I/O this week then you know that google is creating a plan to allow phones to get updated for 1.5 years after release. Google encourages updates it is carriers that don't.

aerojoe420 said:
Who's to blame for delays on updates like gingerbread or bootloader? lawsuit reveals that google has a lot of control over moto and has final say as to when, how and if things get released. Check out the article below and give your opinions please. I personally refuse to let them keep getting data off of me for free and making money off of me, without atleast paying part of my data fees on my bill or giving me a discount. IMO droidwall/disable there data gathering and just use good old fashioned a-gps(like back on windows mobile) if you need to get a lock on your gps.
t h i s i s m y n e x t . c o m /2011/05/12/google-android-skyhook-lawsuit-motorola-samsung/
Click to expand...
Click to collapse
you might want to read the article a few times to make sure you understand it. google is not telling moto to not release gingerbread and to lock the bootloader

I may have misread it from what I gathered, they delay some updates because they tell moto/samsung that they need to pass the approval process if they want the google suite on them. they didn't approve the phones delaying there release because they had skyhook instead of googles data gathering stuff on it?
"Motorola wrote back to Skyhook, explaining that Motorola’s license to use Google’s apps requires those apps to collect location data, and that Motorola’s carrier contracts require Google’s Android apps be installed on its phones. If using XPS put Motorola out of compliance with Android and thus unable to license the Google apps, it would violate its carrier contracts.”
I'm not saying I'd rather have skyhook gathering data from me. It just seems to me that we'll never get the bootloader unlocked because of contractual agreements between carrier/moto/google and they all have there own agendas, in googles case they want you to have there data gathering software.

ATT has final say over bootloader issue. Moto has already said they will release it late this year, but with the disclaimer it would be up to the carriers to allow it for "their" phones. Will not happen through those channels. If the Dev's don't get it, then we don't.
It should be expected that almost every phone in the near future will be like this. The carriers are using this to protect what they consider to be their property. The bootloader is a direct and intentional way to stop "us" from doing all the hacks we do that circumvent things they either charge for, or capabilities they have crippled for whatever reason. Themes and apk files that allow personalization is all they want done. Yes they are watching, and looking for things they need to lock in future releases. They ain't playin no more.

I'd like to see accountability from all parties. There is far too much accepted complacency and slothfulness amongst all of the accused.
I don't want to hop on board with the Google devices just to get the latest updates. There may be other phones with certain specs or strong homebrew development communities that I'd like to participate in. It shouldn't take too much for OEMs to mangle the firmware with their "skins" and for carriers to lace these updates with bloatware.
As long as they can all hurry it up, I'll be happy. Right now I'm discontent and frustrated. And I'm sure I'm not alone with these sentiments... ugh...

benefits of a bootloader we could hack are??

you mean like opening the radio for the full functionality that has been crippled? They increased it to about half its capabilities on the last update. Or loading diff drivers at boot to fix problems some folks are having. Maybe loading a different version Droid. Need to do the whole rom, not just packages. Look at threads in Dev section to see the things we can't mod because some or all of the stuff needed is hidden inside. And the things that are hacked (webtop,tethering, etc.), might see them locked by the bootloader in the future. If they make or can make or save money by keeping it from dev's, this is going to be their path to lock it down.
The new sensation just released is "locked" also. part of the new world order,,lol.

HTC Explains Android Bootloader Unlock Process, Warranty-Voiding Tool

HTC Explains Android Bootloader Unlock Process, Warranty-Voiding Tool Coming Later This Month
It’s been a few months now since HTC CEO Peter Chou announced that the company will no longer be locking bootloaders on their devices, and enthusiasts have had nothing to show for it. Many of HTC’s recent devices are still locked up tight, prompting many to wonder when they would deliver on their promise. Thanks to an updated Facebook post and a well-timed tweet, though, we now have the answers we’ve been waiting for.
The process will begin with a web tool (due out later this month) through which you register an account and waive all liability in the event things go horribly wrong. That’s right folks, since unlocking the bootloader gives you a much greater level of control over how the device operates, you can kiss parts (or all) of your warranty goodbye. Once that’s done, you connect the Android device in question to computer with the SDK installed, and you’ll receive a “device identifier token” which gets plugged into the web tool to generate a unique unlock code.
Sounds simple enough, right? The first devices that are set to benefit from the unlocking treatment are the global version of the HTC Sensation, followed buy T-Mobile’s version of the device and the Sprint Evo 3D. Since unlocking the bootloader is one the of the first steps to running a custom ROM and really having some fun with your Android device, it’s heartening to see them focus on getting newer hardware opened up. Hopefully the floodgates will soon open, and we can start messing with our HTC toys with reckless abandon.
here is a section i took from their facebook post
Update on Bootloaders
by HTC on Tuesday, May 24, 2011 at 4:50pm
Thanks so much for providing feedback, we hear your concerns. Your satisfaction is a top priority for us and we're working hard to ensure you have great experiences with our phones. We're reviewing the issue and our policy around bootloaders and will provide more information soon. Thank you for your interest, support and willingness to share your feedback.
**UPDATE**
We’ve listened. Check out the statement from our CEO, Peter Chou on HTC bootloaders. Click the link for more info.
**UPDATE 7/10**
We wanted to provide an update on HTC’s progress with bringing bootloader unlocking to our newest phones. We know how excited some of you are for this capability, and we’ve put significant resources behind making this change as soon as possible. While we wish we could flip a simple switch and unlock all bootloaders across our device portfolio, this is actually a complex challenge that requires a new software build and extensive testing to deliver the best possible customer experience.
We’re thrilled to announce today that software updates to support bootloader unlocking will begin rolling out in August for the global HTC Sensation, followed by the HTC Sensation 4G on T-Mobile USA and the HTC EVO 3D on Sprint. We’re in the testing phase for the unlocking capability now, and we expect it to be fully operational by early September for devices that have received the software updates. We'll continue rolling out the unlocking capability over time to other devices as part of maintenance releases and new shipments.
HTC continues its commitment to unlocking bootloaders and supporting the developer community. Because of the importance of this community to us, please expect an update on this about every few weeks as we make progress toward launch. Thank you for your patience and continued support!
**UPDATE 8/3/2011**
Since our last update, many of you have asked how the bootloader unlocking process will actually work, and in particular why HTC's most recently released devices still have a locked bootloader. Rest assured we're making progress toward our goal to roll out the first software updates in August to support unlocking for the global HTC Sensation, followed soon by the HTC Sensation 4G on T-Mobile and the HTC EVO 3D on Sprint. Because unlocking the bootloader provides extensive control over the device and modifications may cause operation, security and experience issues, new devices will continue to ship locked but will support user-initiated unlocking using a new Web-based tool.
So how will this work? The Web tool, which will launch this month, requires that you register an account with a valid e-mail address and accept legal disclaimers that unlocking may void all or parts of your warranty. Then plug in your phone to a computer with the Android SDK loaded to retrieve a device identifier token, which you can then enter into the Web tool to receive a unique unlock key via e-mail. Finally, apply the key to your device and unlocking will be initiated on your phone.
We're excited to bring bootloader unlocking to developers and enthusiasts, and we feel this new Web tool will meet your needs and continue to provide customers with the best experience. Thanks to the community for supporting these efforts!

http://forum.xda-developers.com/showthread.php?t=1201270

clarification on updates

Hello,
I just got a Focus v.1.3 unlocked from AT&T.
I am living in Europe and my carrier is Vodafone.
It's unclear to me how updates work.
I currently have updated the phone to 7390 using Zune desktop app.
However no sign on the 7392, I've been checking about that.
I know that updates are delivered by the carrier and that AT&T doesn't deliver yet the 7392 update for Focus v.1.3
But, in the case of using the phone by Zune, shouldn't the updates be available?
Thanks in advance!

Anyone throw some thoughts?
Thanks

HKLM\System\Platform\DeviceTargetingInfo\MobileOperator
Edit it and instead of "ATT-US" (original value) leave blank
You will get an update. I did and I have Focus v1.3, originally on AT&T.
After that update you can revert back to the original value.
Also, read my post here.

Thanks for your comment EnderPsp.
But I don't get it really.
Since you update by Zune, why isn't the phone getting the updates?
This what I don't understand.

andreiuc said:
Thanks for your comment EnderPsp.
But I don't get it really.
Since you update by Zune, why isn't the phone getting the updates?
This what I don't understand.
Click to expand...
Click to collapse
Either take my word on it and do the suggested change in registry (you need to be unlocked for this) or wait until the carrier (AT&T) releases the update. Considering the nice timeframe they haven't yet, I'd say there is a good chance Mango will come directly before AT&T releases 7392 for v1.3
The phone isn't getting the update because the carrier has not relased it (for Focus v1.3). However, Microsoft has released it for all other unbranded phones and if you unbrand (modify the registry as I suggested), the phone will get the Microsoft update instead of AT&T update. There are two minor differences in AT&T/MS updates but the main bonus is you can update to Mango.
Btw, you don't need to say thanks, just hit the "Thanks" button

OK, let me get this straight.
So Zune is a desktop app written by Microsoft that talks to a phone with an OS written by Microsoft but Zune gets updates from AT&T ?
Why the heck do they do that?
OS updates doesn't have to do with the carrier.
I mean, it's not like if you have a AT&T branded phone you also have a branded WP7.
Why are the updates coming from AT&T anyway?
Why isn't the phone getting updates from Microsoft?
Please enlighten me!

andreiuc said:
OK, let me get this straight.
So Zune is a desktop app written by Microsoft that talks to a phone with an OS written by Microsoft but Zune gets updates from AT&T ?
Why the heck do they do that?
OS updates doesn't have to do with the carrier.
I mean, it's not like if you have a AT&T branded phone you also have a branded WP7.
Why are the updates coming from AT&T anyway?
Why isn't the phone getting updates from Microsoft?
Please enlighten me!
Click to expand...
Click to collapse
Partly correct.
Zune is an app that is an intermediary between the cloud and the WP7 phone. Imagine it like a supermarket.
Now, the updates are coming initially from MS but carriers are responsible for their phone's update, service, warranty, quality etc. So they will be the ones actually releasing the update IF the phone is branded by them. This is done to avoid possible issues (any customer service the carrier need to do it even if it's a potential OS problem). Otherwise the general update from MS applies for unbranded phones (ie prepay, free phones etc). The carriers even modify sometimes the update to include specific features. But this also means more QA time...
The carriers know which one is their phone because Zune reports the IMEI and then MS redirects the phone to the carrier corresponding to that phone's IMEI.

So carriers are doing QA job on how a specific phone work with OS?
It's pretty weird that carriers do more then just provide phone services(call, data, etc).
The fact that carriers are modifying the OS update is completely idiotic from my point of view.
They should not mess with OS at all.
I pretty sure that actually they are using some tools provided my Microsoft.
So it's even more idiotic.
I know that carriers have specific apps, but these should be just apps like any other apps.
I don't understand how Microsoft, which is very late anyway at the smart phone party, likes this situation.

andreiuc said:
So carriers are doing QA job on how a specific phone work with OS?
It's pretty weird that carriers do more then just provide phone services(call, data, etc).
The fact that carriers are modifying the OS update is completely idiotic from my point of view.
They should not mess with OS at all.
I pretty sure that actually they are using some tools provided my Microsoft.
So it's even more idiotic.
I know that carriers have specific apps, but these should be just apps like any other apps.
I don't understand how Microsoft, which is very late anyway at the smart phone party, likes this situation.
Click to expand...
Click to collapse
The carriers usually alter this not for their customer's benefit but their own MS provides guidelines and help on how to do the alteration and how to QA. Personally, I don't think MS likes it, but allows it. Pretty much the same as other phone manufacturers.
Also, personally I don't like this carrier update fiasco either, and I agree with you. But, carriers are the ones selling the phone so, MS had to cut a deal somewhere to penetrate the market.

I guess the next thing for Microsoft would be to buy or have some kind of strategic partnership with a carrier.
That would be new But it's highly unlikely it will happen.

andreiuc said:
I guess the next thing for Microsoft would be to buy or have some kind of strategic partnership with a carrier.
That would be new But it's highly unlikely it will happen.
Click to expand...
Click to collapse
I don't know if that will happen, considering iOS, Android and RIM
If they do it, they would do it in US, but no carrier would accept losing money and customers by signing exclusivity.
However, MS do have strategic partnerships with all major phone manufacturers: Samsung, HTC, LG, Nokia etc. THAT will help

Sometime in the future, as hardware advances, phone calls will be carried only over internet.
So these idiotic issues might stop.
And stupid carriers reign will end!

EnderPsp said:
HKLM\System\Platform\DeviceTargetingInfo\MobileOperator
Edit it and instead of "ATT-US" (original value) leave blank
You will get an update. I did and I have Focus v1.3, originally on AT&T.
After that update you can revert back to the original value.
Also, read my post here.
Click to expand...
Click to collapse
EnderPsp, why should I put back the original value anyway?

andreiuc said:
EnderPsp, why should I put back the original value anyway?
Click to expand...
Click to collapse
So you can get the NoDo update after 7392, also, otherwise you might not get some updates in Zune. If you get the update when unbranded, better!
That's how it worked before Mango. Not sure now, but if you're getting the updates unbranded, don't bother putting it back.

Who's responsible for security updates?

My X Style Pure (2015) was updated last Fall to the first version of Nougat (7.0) and has received nothing since October 2017. Moto/Lenovo isn't going to update the OS any further. I'd assumed that I'd still get the monthly security updates.
I know I can use an unofficial ROM to get the phone to Oreo. But will I get security updates? Is the carrier (Verizon) responsible or Moto/Lenovo? Would I have to do it myself, and if so, how?
Just curious as I don't think I've ever seen an answer to this.

The manufacturer is responsible for security updates for as long as they support the device. This assumes that there is no carrier interference with the process: something quite common in the US. Since this device is no longer supported, neither Lenovo nor the carrier is responsible for providing further updates. That now falls to the developer of the custom ROM you choose to use. Most developers are good about providing security updates, but they aren't required to do so either, unlike Lenovo or the carrier.

That's good to know--and a practice that needs to change. I think that the phone manufacturer should continue providing those updates far longer than they do.

TheHarbinger said:
That's good to know--and a practice that needs to change. I think that the phone manufacturer should continue providing those updates far longer than they do.
Click to expand...
Click to collapse
LoL...I agree but in the Android ecosystem, it is unlikely to change. You want consistent regular timely updates for at least 2 years on date of release, then a Google phone (Pixel devices) is the only way to go. Ultimately, it is all about getting people to upgrade and therefore increasing profit. While batteries being "built in and not user replaceable" does lead to slimmer devices, it also means people will upgrade more as their battery life depletes over time. It seems there are a lot of people experiencing sudden battery problems shortly after 2 years on the MXPE. Strange...