Database Info

Bought a Nexus One; totally, completely baffled by tethering

I'm a professional programmer, and I'm baffled. It seems that there is a whole "smartphone scene" and it's intimidating. I'm a Java expert and am comfortable with the Android SDK in Eclipse. However I'm completely baffled by the prospect of getting tethering to work on my Nexus One.
One thing that baffles me, for example, is the concept of a "ROM". Is there a ROM on the N1? I thought that ROMs haven't been used for 10 years. I was under the impression that the N1 is basically a little PC running Linux, which means that it should only have a bare minimum of a BIOS and everything else would be on "disk", or flash.
Another thing that baffles me is the concept of "rooting" the N1. It's running Android, which is an open-source mobile operating system. And, as far as I know, I have the permission to change all bits of the phone. Heck, that's part of the appeal! To say that you have to "root" your N1 is like saying that you have to "root" your Ubuntu box - it just doesn't make sense.
Complicating matters is the release of Froyo. I simply don't know enough to judge whether the actions required to upgrade the N1 to Froyo are compatible with the actions required to install a tethering app.
And that's the thing: I'm not just interested in installing tethering. I want to understand what I'm doing and why. I'd like to understand the options choose intelligently between them. There are so many resources online which are trying so hard to be helpful, but which don't really answer these simple questions.
I really appreciate your help.
-Ablation

search the correct forum for your phones model here on xda. some roms provide tethering preinstalled
check this thread for more info
http://forum.xda-developers.com/showthread.php?t=668090
while that targeted at g1, its the same concept. again search xda for the n1 section

Thanks for the link. However, I think I need a more conceptual introduction to the scene. The essential question is: what are the bits? On a PC you have:
1. BIOS
2. Disk
3. Peripheral firmware.
The disk is further broken down:
1. Bootloader
2. Operating system
3. Drivers
4. Applications
When you say ROM I assume you mean some combination of BIOS and Peripheral Firmware?

[Q] Can Rapiconfig can be used on WP7.x?

Ok, so basically what I am trying to achieve is configuring the security policies on a WP7 device. Currently at WP7, but will be moving up to 7.1/7.5 to try and figure this out for all platform variations.
I've some experience with Rapiconfig on WM6.5 devices, basically configuring the policies listed here but as yet I haven't found a way to push XML direct to the device to update these on WP.
Another route here is to unlock via Chevron and use the registry editor - the issue there is knowing which registry keys are applicable to which security policy - which I know others are also trying to figure out at the moment, but without a full mapping as yet.
Any help here would be great - and if anyone could point me to a Provxml tutorial I would also appreciate it - having trouble deciphering the many guides available.
Thanks as always, this forum is a wealth of positive information and an example of community support at its best.
Cheers,
Mark

http://forum.xda-developers.com/showthread.php?t=936235
that's the most complete tut which is customized to the windows phone.

Yes we use this on samsung devices.
Can you contact me? I might need some help. But we use it to provision xml's

mark14 said:
Ok, so basically what I am trying to achieve is configuring the security policies on a WP7 device. Currently at WP7, but will be moving up to 7.1/7.5 to try and figure this out for all platform variations.
I've some experience with Rapiconfig on WM6.5 devices, basically configuring the policies listed here but as yet I haven't found a way to push XML direct to the device to update these on WP.
Another route here is to unlock via Chevron and use the registry editor - the issue there is knowing which registry keys are applicable to which security policy - which I know others are also trying to figure out at the moment, but without a full mapping as yet.
Any help here would be great - and if anyone could point me to a Provxml tutorial I would also appreciate it - having trouble deciphering the many guides available.
Thanks as always, this forum is a wealth of positive information and an example of community support at its best.
Cheers,
Mark
Click to expand...
Click to collapse
Yes we use rapiconfig, but when we use it it's an on-device version of it which resides in the \Windows directory and so far the only arguments that have been tested to work with it are provxml filenames. Marvin_S, you're a perfect resource for this .

Does the 2nd generation WP7 handset can unlock or not?

I found there is a great deal of the new devices of LG,JIL SANDER Mobile LG-E906 ,only 199.99 on expansys.
If there is a way to unlock /jb these devices, it's the cheapest 2nd wp7 that I have found...

Moved to WP7 Q&A
No questions in the development section!!
Please refer to the read before posting for guidelines.
Take it easy
O_G

original_ganjaman said:
Moved to WP7 Q&A
No questions in the development section!!
Please refer to the read before posting for guidelines.
Take it easy
O_G
Click to expand...
Click to collapse
Thanks ,I just want to know are there any other way to JB it ,such as flash the Romer's rom,because I just know the HTC has difficulties to rewrite the SPL.I dont know whether LG is the same as HTC?

I don't believe there are any custom ROMs available for LG Windows phones, though that may be incorrect.
You can certainly developer-unlock the phone; this is possible and supported on all Windows Phone models, whether you use the developer tools or the ChevronWP7 Labs unlocker.
Assuming LG hasn't removed the built-in registry editor from their new ROMs, you can also interop-unlock your phone. This allows installing high-privilege apps. It's not a "full unlock" (and the term "jailbreak" is far too vague) but it does allow some useful capabilities.

GoodDayToDie said:
I don't believe there are any custom ROMs available for LG Windows phones, though that may be incorrect.
You can certainly developer-unlock the phone; this is possible and supported on all Windows Phone models, whether you use the developer tools or the ChevronWP7 Labs unlocker.
Assuming LG hasn't removed the built-in registry editor from their new ROMs, you can also interop-unlock your phone. This allows installing high-privilege apps. It's not a "full unlock" (and the term "jailbreak" is far too vague) but it does allow some useful capabilities.
Click to expand...
Click to collapse
So I can install the XAP which is not verify through the MS, right?
I want to know is it difficulty to make this device's ROM?

If the Jill Sander have the MFG Menue so i think this one is possible.
http://forum.xda-developers.com/showthread.php?t=974874

[Q] interop unlock on lg 7 for other oem market?

hello everybody, I really can't get modding with windows phone, sorry I've been with android so long and now is all different.
So I have a LG 7 with mango, I want to install the nokia market xap. I just can interop-unlock modifying the registry with the mgf app?
Is a reversible operation?
Thank you

Hi, I'm actually the author of the Nokia Market (and Samsung/LG/HTC/Dell marketplace) XAP. You don't really need interop-unlock; normal developer-unlock works fine.
That said, to answer your question directly:
Yes, you can use the MFG app to dev-unlock (and interop-unlock, if you want) your phone. The steps are available on the Dev&Hacking forum, in multiple places including the interop-unlock thread.
The difference between dev-unlock and interop-unlock from your perspective is the MaxUnsignedApp value - if you put it at 10 (the default for a normal dev unlock) you can install up to 10 homebrew apps (XAP files), and they can't use ID_CAP_INTEROPSERVICES (access high-permissions drivers to break out of the sandbox). If you set it over 300 (most people go for 2,000,000,000 or so) you can install more homebrew apps than you'll ever need to, and they can use ID_CAP_INTEROPSERVICES (which enables some cool hacks, for example the MultiTaskToggle app linked in my signature - it's still compatible with LG just fine). This is referred to as "interop-unlocking" the phone, and must be done after "dev-unlocking" (which is just tweaking a few other registry values).
The whole thing is completely reversible. You can reverse it using the MFG app again, for example. I think you can reverse it using the Developer Registration tool (part of the WP7 SDK, this is the program normally used to dev-unlock a phone). You can, for the "nuclear" option, reverse it by wiping / hard-resetting the phone.
Hope that helps!

a big thank goes to you

How did android reach this point?

As advanced android users, we quickly became obsessed with rooting, unlocking, and controlling our phone. On the other side of the poker table, we have device manufacturers and carriers trying to lock the ecosystem down. It's curious to me how this came to be.
Looking at personal computers: I wanted to install linux on my personal computer because I am a developer by trade, so I installed linux. I took a USB, loaded the linux ISO, and followed the installer (actually I didn't, arch btw). I did not need to get unlock codes from my device manufacturer or my internet company, I just did it and no one complained (aside from windows who was glitching out as I tried to reboot)
This computer ecosystem feels healthy, it's my computer, and I can use it as I wish. I'm curious how and why android got to this point where 90% of manufacturers:
1. Don't allow unlocking
2. Make you jump through hoops to get an unlock code
3. Have hardware root checks
Of course, before we even start talking about verizon (they forgot to lock my pixel )
Is the fact that mobile devices are harder to unlock and modify them computers a flaw in android? Is there some actual reason life is like this?
That's even before we start talking about update cycles. I used my old computer for 10 years, going from god knows what to windows 10 before finally deciding that I just could not. My device manufacturer did not control the updates I got, they just came. Why is it the case that updates come from the manufacture, not directly from modifications to the android codebase? Shouldn't the manufacture just add "drivers" to the device to handle the peripherals?
I presume in some way google is complient with this, because android is based on linux, and linux has no such problems.

Many times, consumers that bootloader unlock their devices have no clue that they will lose features such as banking and Widevine D1; these users are oblivious as to what rooting truly does to their device and instinctively contact their OEM's support to get a device replacement as many times relocking the bootloader is impossible.
Verizon's thought process is somewhat similar, but there is likely a darker undertone to their practices: preventing bootloader unlocks and processes of the sort could aid them when blacklisting their devices, as there is no way to circumvent something tagged to a permanent IMEI kept by the same bootloader and firmware. There is a reason why T - Mobile requires you to have your device completely paid off before you can make any modifications to the system firmware.
Compared to laptops and computers, it is, generally, a one - time purchase and not an investment; carriers depend on their consumers to keep paying their devices off time and time again to make money.
Drivers are essentially non - existent on Android; the only thing that comes somewhat close is the kernel and any OEM modifications to the firmware.

Xryphon said:
Many times, consumers that bootloader unlock their devices have no clue that they will lose features such as banking and Widevine D1; these users are oblivious as to what rooting truly does to their device and instinctively contact their OEM's support to get a device replacement as many times relocking the bootloader is impossible.
Verizon's thought process is somewhat similar, but there is likely a darker undertone to their practices: preventing bootloader unlocks and processes of the sort could aid them when blacklisting their devices, as there is no way to circumvent something tagged to a permanent IMEI kept by the same bootloader and firmware. There is a reason why T - Mobile requires you to have your device completely paid off before you can make any modifications to the system firmware.
Compared to laptops and computers, it is, generally, a one - time purchase and not an investment; carriers depend on their consumers to keep paying their devices off time and time again to make money.
Drivers are essentially non - existent on Android; the only thing that comes somewhat close is the kernel and any OEM modifications to the firmware.
Click to expand...
Click to collapse
This explains why carriers do do this, and it makes sense, but how can they do this? The fact that should someone in the black box want to, loose control over my device no matter what I do is frankly scary. Could a laptop manufacturer do the same thing if they wanted to? (Ignoring the fact they could not because of the outrage). I had always thought somehow android as an operating system was connected to this, somehow complient, but perhaps it is really just a choice by the manufactures that android has nothing to do with. (Google could enforce this via GMS I think, but I don't expect them to)

Scaledish said:
This explains why carriers do do this, and it makes sense, but how can they do this? The fact that should someone in the black box want to, loose control over my device no matter what I do is frankly scary. Could a laptop manufacturer do the same thing if they wanted to? (Ignoring the fact they could not because of the outrage). I had always thought somehow android as an operating system was connected to this, somehow complient, but perhaps it is really just a choice by the manufactures that android has nothing to do with. (Google could enforce this via GMS I think, but I don't expect them to)
Click to expand...
Click to collapse
Chromebooks are a prime example of locking down the bootloader. So is the same with macOS laptops and related devices - albeit Apple lets you boot into other operating systems, the process to do so requires jumping through quite a bunch of loopholes due to Apple's Secure Boot, file system, etc.

Just to play devil's advocate for a moment (because in reality, I, too, prefer to own my equipment).....
Security can be a lot more critical on mobile devices than stationary devices like desktop computers. Even in *some* respects, compared to rackmount servers. This is because it can be pretty simple to grab someone's phone and do what you want with it. Having physical access to a piece of equipment is 99.999% of the task of breaking into it. Its relatively far fetched for someone to break into your home or a high security datacenter in order to gain physical access to your equipment, so the need to have it protected against the kinds of intrusions that become possible through physical access is much lower than it is on a phone, which you just might accidentally leave on the counter at a coffee shop.
And that is about the only part of the move towards lockdowns that I actually understand. The rest of it is either ill-conceived "security" or coercion to separate you from your money.