Some info about the hardware unlocked ADP1

by » Sat, 28 Feb 2009 02:46:58 GMT

Sponsored Links
 I have ADP1 and want to flash it with the holiday version, because
waiting the official ADP 1.1 is an unofficial waste of time.
My question is can I lock my phone if I flash it with a software
version which is for locked phones? And how the hardware unlock works?
I know that one of the difference of G1 and ADP1 is that ADP1 is
hardware unlocked and you can install anything, but how does this
work? Is there a chance to lock my phone with some software flash?

Some info about the hardware unlocked ADP1

by Jean-Baptiste Queru » Sat, 28 Feb 2009 03:11:22 GMT

 The locking happens at two levels: the bootloader (i.e. whether the
fastboot protocol is enabled or disabled) and the keys used during
recovery (i.e. whether recovery recognizes secret keys or known "test"

Replacing both of those with locked versions would lock you out of
your phone. The bootloader that the ADP1 ships with prevents you from
updating the bootloader for that specific reason.

You'll be at risk if you flash your device with a build that looks
close enough to a "locked" consumer build, as that could later cause
an automatic update to overwrite your build, and if that update
replaces both your bootloader and your recovery keys you'll be stuck.
If you flash it with a build that looks close enough to an unlocked
build, the worst that an automatic update is likely to do would be to
update you to a newer version of a similarly unlocked build, but
there's of course no guarantee.

Of course, you understand that working with builds from unknown
sources instead of official builds carries an additional level of


Jean-Baptiste M. "JBQ" Queru
Android Engineer, Google.

Please don't contact me directly.


Sponsored Links

Other Threads

1. And drawPath is faster and many invocations of drawLine (between points) in Overlay ?

Didn't understand your question...Could you clarify a bit more?


2. File Upload Website Interaction

I posted this in beginners and got no response, but it appears this
group is far more active; I hope this doesn't offend anyone.

I have been reading a lot of documentation, and I'm looking to start
building my application very soon. However, I'm not sure how I want to
handle a key aspect of it, and I want to get it straightened out
before I get too far in the development process:

I want users to be able to upload a file from their handset to my
webpage. I have a shared hosting plan (at least now), and I'm mainly
working in PHP and MySQL serverside. What would be the best way to
handle this transaction? I'm flexible and I'm open to any options.
I have very limited experience with file transfers, and I'm not sure
how to best jump this hurdle. I'd like to not have to rely on them
using the browser and a form, but keep the entire upload within the
application itself on Android. But then I'm not sure how I would set
this up with my website.

I did find this here:
It shows both the webserver and android end to uploading a file. Any
other input is still appreciated, although this may be what I
was looking for. So I know it's possible, just need to dissect the
code and make sure this is the most efficient and best way to do

Any and all feedback is appreciated, and even
something to suggest for me to research on my own would be great.
Thanks in advance for your time and consideration.


3. Moving files from one machine to another and getting eclipse to read it

4. MapController.centerToMap(Point, boolean) is not applicable for the arguments (Point, boolean)

5. problem with Manifest Editor

6. Error in xml file "No resource identifier found "

7. SQLite interface: hell slow?