yashsingh1/xdaforums huggingface dataset:
[Nexus One Q&A, Help & Troubleshooting] ArcanaXVIII:
Same problem with the european stock shipping ROM (EPF21B).

Can't wait to be able to get Froyo without unlocking.
[Nexus One Q&A, Help & Troubleshooting] unleashed12:
my bootloader is unlocked..going to go ahead and try to flash pauls rooted version.
[Nexus One Q&A, Help & Troubleshooting] bluezz:
What a bummer! Yeah I have waited this long to preserve my phone's virgini.. I mean warranty so I guess I'll wait longer.

At least its good to know that the build for at&t and rogers is the same!
[Nexus One Q&A, Help & Troubleshooting] Kpow:
I have the AT&T N1, and earlier today I flashed and formatted my phone back to new. I now have Froyo and it's working fine.
[Nexus One Q&A, Help & Troubleshooting] MEGABYTEPR:
is your N1 rooted or stock?
[Nexus One Q&A, Help & Troubleshooting] pjcforpres:
Clearly rooted and unlocked bootloader, otherwise he wouldn't have been flashing anything.
[Nexus One Q&A, Help & Troubleshooting] e-dub:
thread title misled me.

eric b
[Nexus One Q&A, Help & Troubleshooting] xEM1x:
I have successfully flashed Froyo on my (AT&T) N1 with this:

http://android.modaco.com/content/g...com/309286/frf50-froyo-pre-rooted-update-zip/

I previously was on CM 5.0.6 with Amon RA Recovery v1.7.0.

I wiped and installed the update, it did flash a new radio. Rebooted and Froyo was waiting for me!

Hope this helps anyone that is not sure.
[Nexus One Q&A, Help & Troubleshooting] sassyness77:
confused...

Alright could I just get an answer as to why my t mobile nexus one had a build number of 54? I'm rooted and was running cyanogen, but I thought that should have shown a different build number if its the t mobile one? Well either way, I have froyo now, i just flashed pauls rooted update, but i was just confused...I'm probably just missing something or completly misreading this whole deal. :p
[Nexus One Q&A, Help & Troubleshooting] MENDEH:
what would make at&t more money?

1. making nexus one users pay more to tether

2. forcing every single iphone customer onto the correct $30/month plan

if it was just about business sense then i think at&t would probably do both 1 & 2. ;)
[Nexus One Q&A, Help & Troubleshooting] :
One thing is directly preventable, the other isnt?
[Nexus One Q&A, Help & Troubleshooting] MENDEH:
you dont think at&t could have their system strictly enforce iphone = mandatory $30 plan?

i just think its silly for at&t to think that nexus one users (who i would bet are mostly pretty tech savvy) would be willing to pay $60/month for tethering. most would not buy it and those that want tethering will find a way to tether for free.

thats probably enough to make a lot of people consider unlocking their bootloaders.
[Nexus One Q&A, Help & Troubleshooting] khaytsus:
er, they might *default* to isp.cingular but they aren't forced to use it.. I tethered on my WM phone infrequently but it worked fine.. Either BT DUN, BT PAN, or using WMWifiRouter.
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
There is absolutely nothing AT&T can do to stop it.
[Nexus One Q&A, Help & Troubleshooting] George Knighton:
I can't see them going through all that.

Nokia users have been tethering for many years, and no steps have been taken to stop us/them.
[Nexus One Q&A, Help & Troubleshooting] attn1:
Right. And hypothetically, even if they could (and they can't), they could not stop it from coming over Wifi connected to a completely different network.

The only way they can control updates is if they control the software on the phone. And they don't.
[Nexus One Q&A, Help & Troubleshooting] YettaVR6:
On the Samsung Epix it was forced. You couldn't even get into the Connections settings to change it. You would get a message similar to "These settings are preconfigured and cannot be changed". Only way to change it without a new ROM was through the registry. I'm pretty sure it was the same way on my Tilt. Don't remember how my Fuze was since i pretty much flashed it the day i bought it :)
[Nexus One Q&A, Help & Troubleshooting] krabman:
Yeah, I dont know what the noise over tethering is about. People have been doing it on unlocked smartphones for a long time on AT&T. I personally have been doing it for years. The new option to set up a hot spot is nothing new either, its been done for years on those same smartphones.

Actions speak louder than words and AT&T could have had unlocked smartphones users all forced onto smartphone plans and paying for tethering if they wanted at any time. IMEI numbers are publicly available and you can find them on the internet. They can also see that you are tethering simply by the quantity of data you pull down over time, they need not sniff it at all. Both are easily checked and all the tools to do so are already in place and accessible. People are making too much out of this, AT&Ts subbed android phones will have the option removed and unlocked smartphone users who make up a ridiculously small part of their business will go on as they always have.
[Nexus One Q&A, Help & Troubleshooting] :
ATT Nexus One

I have AT&T Nexus One with Froyo 2.2, but wifi is not working, sees SSID but scanning over and over... any else have this problem?

Used these methods to mod, everything else works great, just not wifi…

1. Unlocked

2. Modaco’s superboot

3. Paul's FRF50 with radio
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
Exactly!

The one error every one is commiting here is to say there is an "AT&T Nexus One". There is no such thing whatsoever!

What google has is a "TMo" compatible N1 (as in supporting 900/AWS/2100 MHz 3G networks) and an "AT&T" compatible N1 (as in supporting 850/1900/2100 MHz 3G networks). Just check the purchase link: bit.ly/aB15Z8

AT&T has no business over this firmware version! Me, for instance, have bought the 850/1900/2100 version (aka "AT&T N1") and I'm using it in Brazil with a local service provider, never having signed any contract with AT&T whatsoever! Of course, while roaming in the US, I must use AT&T since the phone is not compatible with TMo 3G frequencies (unless I'm in a region where the station works at 2100 MHz).

What everyone has commented about phones being blocked to use a certain proxy server is true for the case where you buy your phone from AT&T and that they have flashed their custom ROM on your phone, which is not the case here. On my N1, I had to manually configure all the data settings, since it doesn't have one by default, as it is an unblocked phone.

As a matter of fact, if you check the google.com/phone page I've linked above, you'll see there is not even a N1 AT&T plan yet, so they haven't even created their own ROM for N1. So, there is no way they'll remove tethering from EPE54B-compatible Froyo OTA.

And, finally, if AT&T wishes to block tethering when you're connected to their network, that's just too bad. Change to Sprint or any other provider that isn't that *****y about it.

Best regards,

Henrique.
[Nexus One Q&A, Help & Troubleshooting] Clarkster:
Yeah, I sure didn't buy the AT&T Nexus One. I bought the Rogers 'compatible' one, and Google shipped it straight to Canada for me. And Rogers/Fido offers free tethering with every data plan. There is no way AT&T will dictate the rom features I am getting.
[Nexus One Q&A, Help & Troubleshooting] MENDEH:
I hope you guys are right
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
We are, don't worry.
[Nexus One Q&A, Help & Troubleshooting] Xaositek:
Haven't had this problems. Thought I lost 3G access this morning, but found out we had a 3G tower in the area go dead. Locked onto an EDGE tower then tried another 3G access town without problem.
[Nexus One Q&A, Help & Troubleshooting] subramanianv:
I own a AT&T compatible N1 and I am pretty sure AT&T cannot enforce any kind of tethering restriction. I have not tried tethering on my N1. But I used to USB tether my old Nokia N85, it used to worked fine.

I believe AT&T or for that matter no Service Provider can differentiate whether you are using 3G on the phone or you are using it tether. Only by your rate of data usage you will be suspected.

Google's primary idea for releasing Nexus One was to keep it open and free from any restriction imposed by Mobile service providers. You can safely assume they are not going to bend their OS for AT&T now.
[Nexus One Q&A, Help & Troubleshooting] Xaositek:
I already suck down around 2gb a month WITHOUT tethering... I'm pretty sure if I sucked a little extra noone is going to notice.

The ONLY problem you might run into is if you go from pulling like 100mb a month to 4GB. You might set off one or two alarms at AT&T. Although it's probably unlikely. Google admitted somewhere that AT&T can't tell the difference between the Phone and a Computer, the packets are transmitted the same way.
[Nexus One Q&A, Help & Troubleshooting] bluezz:
You AT&T guys are lucky.

I wanted to mention that my Rogers gives me 500 MEGS a month. I am not at all excited about tethering :(
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
haha...Ive used 2GB in the past week alone.
[Nexus One Q&A, Help & Troubleshooting] walie:
rogers *gives* me 6 gigs, whats your point?
[Nexus One Q&A, Help & Troubleshooting] bluezz:
I mean Rogers data plans in Montreal are sh*t.
[Nexus One Q&A, Help & Troubleshooting] deprecate:
So the question is this...how long is the warranty on the phone? And since HTC is honoring honest hardware faults despite the unlocked bootloader, why get so bent out of shape over unlocking the phone?

It all just seems strange :)
[Nexus One Q&A, Help & Troubleshooting] attn1:
I don't care about the warranty issue. I just don't like the goofy looking lock on the initial boot up image. fuuuug-ly!
[Nexus One Q&A, Help & Troubleshooting] deprecate:
hahahahaha :p

fair enough :)
[Nexus One Q&A, Help & Troubleshooting] vipwoody:
exactly! I fukn hate the limitation we have on Rogers Montreal
[Nexus One Q&A, Help & Troubleshooting] foxyNinja7:
Aright, I'm giving in and doing it. I want me some Froyo! So what's the better option: downgrade to ere27 and then apply the official update, or use paul's update? I've never rooted or anything before.. thanks!
[Nexus One Q&A, Help & Troubleshooting] nDrg:
I'd suggest unlocking the bootloader, flashing AmonRa's recovery menu then apply Pauls update. Make sure to create a nandroid backup via the recovery menu just to be sure but it should work just fine :)
[Nexus One Q&A, Help & Troubleshooting] chromiumcloud:
I'm a total newb, and I found a great site yesterday. It had pictures of each step and gave PC/Mac/Linux directions for every step (which was a must for me!). Anyhow, I'm away from home now and I can't find the site, but will post the link later if you need it.

I flashed the one minus the radio. The jury is still out on what the new radio does to AT&T reception (I get no camcorder though without the new radio).
[Nexus One Q&A, Help & Troubleshooting] chromiumcloud:
Well AT&T got Google to keep PDAnet out of the AT&T-accessible Android market place!

Moving to the Nexus for me was initiated by AT&T's super control over what they allowed on the iPhone. I would NOT be surprised for them to at least try to do the same to the nexus.

I bit the bullet, am rooted and flying high with Froyo flashed over so I agree, that's pretty much what everyone will do should AT&T cripple the update.
[Nexus One Q&A, Help & Troubleshooting] attn1:
If you're on AT&T, there is no option to downgrade to ere27, no option for Froyo yet except unlock bootloader, install amon's recovery, install Paul's repacked version.
[Nexus One Q&A, Help & Troubleshooting] tjp888:
Hey, I would like to see this rooting walk through you found.
[Nexus One Q&A, Help & Troubleshooting] foxyNinja7:
I found this one which helped me..

ilikemygooglephone dot com/2010/01/06/complete-guide-with-images-unlock-bootloader-and-root-google-nexus-one-mac-windows-linux/
[Nexus One Q&A, Help & Troubleshooting] krabman:
A lot of people like this guide.... http://theunlockr.com/category/howto/android_how_tos/nexus-one-how-tos/
[Nexus One Q&A, Help & Troubleshooting] arcticreaver:
i'm receiving the nexus one tomorrow. i'm on ATT. is there a reason why the ATT version of 2.2 not out yet?
[Nexus One Q&A, Help & Troubleshooting] nexusonemeover:
so if i give in an unlock this thing, will i have to revert at some point to get future updates? or will i forever be updating from SD roms?
[Nexus One Q&A, Help & Troubleshooting] mickmel:
As per Twitter user @cyngus:

"Android 2.2 is being rolled out to a very limited test group. We expect a final build to be available for OTA updates shortly, stay tuned!"

Very few people have received OTAs at all, and apparently the test group was only for TMO users. I'm hoping "shortly" means later this week...
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
I think you still don't understand.

Accessing AT&T network through an AT&T compatible N1 has nothing to do with accessing any other 850/1900/2100 3G network with AT&T compatible N1. If AT&T blocks pdanet thru its network, I couldn't care less!!! Too bad for all AT&T customers (not my case).

They have all the rights to do it, IF you buy N1 from them, which, again, is not my case (and noone's, for that matter, since AT&T still isn't a N1 retailer).

Again, that's not gonna happen...
[Nexus One Q&A, Help & Troubleshooting] Clarkster:
Yes, there is a good reason. FroYo hasn't been officially released yet. It has only been sent out to a small group of testers. http://twitter.com/romainguy/status/14650964801 One of those testers checked his log and released the URL for the update. That is what everyone is using right now.
[Nexus One Q&A, Help & Troubleshooting] arcticreaver:
oh okay, so it hasn't been OFFICIALLY released.
[Nexus One Q&A, Help & Troubleshooting] maxawesome:
On the contrary, you can flash signed non-rooted images from the stock recovery console.

That's why my unrooted TMO phone is running Froyo as I type this. I don't have an unlocked bootloader, I don't have Amon_RA bootloader, and I don't have root.

Rename the image zip file to update.zip and copy to root of SD card

Power down

Hold Volume Down + Power on

Use Volume down key to select 'Recovery'

You will see a triangle with an exclamation point (!) and an Android icon, don't panic - this is the recovery screen

At the recovery screen, press and hold Volume Up and Power button

Use Trackball to scroll down and select 'Upgrade from update.zip' and click Trackball to begin the flashing

I don't see any reason why this wouldn't work from any previous version of Android, as the Froyo image is a full image.
[Nexus One Q&A, Help & Troubleshooting] lewy10:
Where's the N1 At&T EPE54B to Froyo 2.2 update going to roll out?
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
From Google's servers
[Nexus One Q&A, Help & Troubleshooting] foxyNinja7:
Just root man, I just did and it's totally worth it (and not that hard). Froyo is bomb.
[Nexus One Q&A, Help & Troubleshooting] lewy10:
I will wait.........
[Nexus One Q&A, Help & Troubleshooting] krabman:
You can unlock and root and still receive ota. Once you install a custom recovery you must go back to a stock recovery to install an ota since the ota will need a stock officially signed recovery to install itself with. Custom roms usually have ota blocked to prevent an ota from screwing anything up. This is why people on custom roms had to both revert to the stock rom and the stock recovery to get ota.

I'm assuming you mean that if you unlock/root/ install Pauls 2.2 rom will you be stuck forever installing custom roms? Doesn't matter. Once you have unlocked and are facing the potential for denial of warranty there is no reason not to reap the benefits and root it. Its all gravy from there and you may as well reap the rewards of owning your device. With amon ra installed you can pick and choose roms as suits you. Want to stay on stock roms just flash them as they are released. Want to try (and you're cheating yourself if you dont) cm or other custom roms, go ahead. Restoring a nandroid is quick and easy. Once you have unlocked you have crossed the line. There is absolutely no reason not to fully harvest all the goodies now available to you. You need not worry about getting the next update in a timely fashion. People who were rooted got 2.2 just as fast as those who were not. Installing it was as simple as doing a wipe and flashing, a matter of minutes.

Worrying over unlocking is a valid concern because of the warranty implications. Not doing so is a reasonable position to take. Any concerns after unlocking however are unfounded, all you face is good, better, and how did I ever live without this? Seriously.
[Nexus One Q&A, Help & Troubleshooting] krohnjw:
Carriers reserve the right to prevent certain apps from showing up in the market for users of their network - T-Mo did the same with tethering apps initially.

This is 100% independent of the ROM itself and in no way related.
[Nexus One Q&A, Help & Troubleshooting] x986123:
Should this even work? Who wants to try this?
[Nexus One Q&A, Help & Troubleshooting] URPREY:
Nope. It will only work on a like build - the AT&T compatible phones are EPE54B and CANNOT flash images without the same build.
[Nexus One Q&A, Help & Troubleshooting] webfrm:
OK then

Well here's my dilemma. I got the phone a week ago so I'm still making sure it works (no hardware issues) for me. That being said I don't want to root it just yet. However I'll give big blue a week to update to Froyo since it's lame that all that's different is the radio, how much code is really required to fix this? If they do a Froyo release by the end of the week (hence my 14 days will be up by then) can I still root my phone and pick the 2.2 custom ROM your all raving about if indeed their version sucks, or will the fact that my build changes become an issue? Please advise.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
It has nothing to do with big blue releasing the update. Google just hasn't released the update yet for any nexus ones, not the t-mobile or ATT version.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
But those were all phones sold by ATT, were they not? ATT had their own custom ROM on those phones they sold so they could do those things.

The nexus one is totally Google, ATT has no access to this ROM at all.
[Nexus One Q&A, Help & Troubleshooting] andjohn:
Works fine on mine

Lol, I forgot my phone was the Rogers version when flashing both my roommate's T-Mob version and they were identical. Both work fine. AND I can still get Rogers HSPDA speeds.
[Nexus One Q&A, Help & Troubleshooting] xboomer55:
Thank you for re-stating what is obvious to anyone paying attenton.
[Nexus One Q&A, Help & Troubleshooting] anangphatak:
Getting FROYO for at&t

Why is not possible for non-rooted AT&T users to

- get ERE27 stock & unrooted ROM and flash that

- update to FRF50

Should work in theory ?
[Nexus One Q&A, Help & Troubleshooting] krohnjw:
No, there is no signed update to go from EPE54B to ERE27 (an earlier release). Thus the upgrade path from ERE27 does not work. ERE27 checks build.prop to make sure you are running ERD79 - thus flashing on a phone running EPE54B fails this check. FRF50 checks build.prop to make sure you are running ERE27 (hence EPE54B fails).

You need to unlock the bootloader and load from a custom recovery to downgrade to ERE27 to flash the FRF50 update.
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
Actually, that is not accurate.

ERE27 and EPE54B are not in the same code branch, they are parallel.

Notice both ERE27 and EPE54B are related to the same firmware version, 2.1-update1, but they are different builds simply because they are intended for different hardwares (i.e. different radios). Functionality wise, they are the same (if they were CVS branches, they would be at the same level).

If you buy a new ATT compatible N1 today, it will come with EPE54B; if you buy a TMo compatible N1, it will come with ERE27.

So, there will never be an EPE54B-to-ERE27 update, simply because they don't apply to the same HW. As well, there will never be an update from EPE54B-to-FRF50, simply because FRF50 is for TMo compatible HW. The 2.2 firmware version for ATT compatible HW will be named different, since it will be a different build.

What the modders have probably done is to get the new functionalities from the application layer of FRF50 and use the same radio SW that was used in whatever version you had previously (e.g. it won't change the radio SW you use now).
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
Nope that's not right, the radio's are interchangable.
[Nexus One Q&A, Help & Troubleshooting] Requiem87:
Yea, they must be compatible, because i bought an unlocked N1 from google with ERD79 rom, upgraded to ERE27 by using update.zip method and updated to ERE36b (which is same branch as ere54b i think) using passimg.zip method. I am on Telenor carrier network and both radios work fine on my hardware. Hope for a froyo passimg.zip soon (full rom not update)...
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
You wont need a passimg.zip, the EPE54B N1's will get an OTA update, so you'll just need up update to that, and when the time comes, i'll do it's thing.
[Nexus One Q&A, Help & Troubleshooting] SooSpecial:
So when will we, AT&T folks, get the damn OTA update?
[Nexus One Q&A, Help & Troubleshooting] mutantblack:
What do you guys think about this article.

http://www.androidcentral.com/froyo-your-nexus-one-att-users-can-join-fun
[Nexus One Q&A, Help & Troubleshooting] bluezz:
I just read this. They don't mention either rooting the phone or unlocking the bootloader. I'll might try this once I get home.
[Nexus One Q&A, Help & Troubleshooting] Requiem87:
Possible to upgrade to froyo now with locked bootloader, or are androidcentral wrong?

http://www.androidcentral.com/froyo-your-nexus-one-att-users-can-join-fun

If anyone succeeds with this, I will upgrade to ere54b, and downgrade to ere27, then upgrade to frf50, immediatley! ^^
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
Well considering there has been no official release of the Froyo OTA yet...

We should see the official OTA for T-Mobile and AT&T in the next week or 2.
[Nexus One Q&A, Help & Troubleshooting] mutantblack:
I will try that if I can get my hands on EPE54B stock image eclaire so I can revert back if there's anything wrong. Do you guys know where I can get the image?
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
Interesting...I thought this was tried and proved that you cannot go to ERE27 without unlocking the boot loader. Doesnt make sense that the phone would allow you to go from EPE54B to ERE27...if anyone tries this, do share.
[Nexus One Q&A, Help & Troubleshooting] mutantblack:
that's what I thought too unless those folks from Android Central are wrong. They claimed they upgraded to froyo without unlocking the bootloader. Only if I can find the stock image then I don't mind testing it out.
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
http://xdaforums.com/showthread.php?t=642811
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
Then I don't understand why they need two code branches, because there are indeed two separate branches.

EDIT: actually, I do have a question. I doubt anyone that has flashed a TMo ROM in an ATT N1 has tested the full range of received frequencies to see if the phone works as expected. I mean, just because the phone was able to connect to the 3G network it doesn't mean that the complete range of frequencies are compatible. Remember that 2100 MHz is supported by both radios, so it might be the case that the interchange of TMo x ATT ROMs will cause your phone 3G to just work for this frequency (which is the frequency used by most of the new 3G stations). But unless someone make a real reception test in an isolated environment with proper measurement tools (e.g. an osciloscope to determine the frequency + phone's internal received signal level, in dB), it ain't possible to be 100% sure the radios are completely interchangeable, e.g. frequencies of 850/1900 MHz might stop working for ATT compatible phones.

Has such a test been ran yet?

If anyone has it, could I get a link please?
[Nexus One Q&A, Help & Troubleshooting] mutantblack:
dang it. I am at work and they block the rapidshare here. Guess I have to wait till I get back home to test this out.