yashsingh1/xdaforums huggingface dataset:
[Nexus One Q&A, Help & Troubleshooting] Requiem87:
I just tried the method they described over at androidcentral, but from ERE36B (again) and it still does not work for me anyways (signature verification failed). So, does this work from ere54b, or is it the same story there?
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
I assume its the same story. I feel like I tried to flash directly to ERE27 from EPE54B and it failed out. But I cannot remember. I was frantically trying everything I could to get FROYO on Saturday without rooting...no luck.
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
I really can't see it working, personally.
[Nexus One Q&A, Help & Troubleshooting] darkjedi:
Seeing as how the T-Mo version supports 2100/1700/900, you wouldn't get any reception on at&t if you flashed the T-Mo radio.
[Nexus One Q&A, Help & Troubleshooting] tjp888:
I just tweeted AndroidCentral and they are reviewing this procedure again.
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
Yeah, they pulled the post.
[Nexus One Q&A, Help & Troubleshooting] duwady:
I tried it, but could not flash down from 54b (ATT) to stock T-M (ER27). Guess it can not be done without rooting.
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
No, the TM radio works fine on AT&T and vice versa.
[Nexus One Q&A, Help & Troubleshooting] nexusonemeover:
nice response. thank you...
[Nexus One Q&A, Help & Troubleshooting] mlinz:
The process to get Froyo on a At&t/Rogers N1 right now isn't hard, but requires unlocking, which I believe this thread wasn't originally intended for. I think it should be pretty obvious that a rooted At&t N1 would be easy to upgrade. I highly doubt the radio's or the drivers for the radios are compatible between the Tmobile and Att version given they are different pieces of hardware and therefore should require a different driver/radio version.

Who cares anyway? The "leaked" build is just a tech preview for the Press, google even confirmed it. They even said tmobile users that ran the update aren't going to get OTA update for the final release build, which means they will need to Root their phone if they haven't and then install it.

Just wait another week until it comes out..
[Nexus One Q&A, Help & Troubleshooting] darkjedi:
I know that, I was responding to the previous guy who says he doesn't think that the radios are interchangeable. I was saying, if that were the case, the at&t version wouldn't get any signal after flashing Froyo.
[Nexus One Q&A, Help & Troubleshooting] lmarazzi86:
Make sure you used the correct Superboot. When I first did it, I didn't choose the correct build version and it disabled my WiFi. I went back and reflashed with the correct build and it is working perfectly.
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
Where did you see that those who updated to FRF50 will not get the final build OTA?
[Nexus One Q&A, Help & Troubleshooting] Jep4444:
thats only the radio for HSDPA (3G), the GSM radio (2G/Edge) on both phones is still the standard 850/900/1800/1900 so yes an AT&T phone will pick up reception on T-Mobile and vice versa
[Nexus One Q&A, Help & Troubleshooting] attn1:
Yes they are. All I had to do was restore my old APN settings after updating to Froyo, and all is fine. I am using the radio supplied with the T-mobile release.
[Nexus One Q&A, Help & Troubleshooting] attn1:
Yes you will. The radio software just interfaces the OS to the radio. The radio frequencies are not set by the radio software. I flashed the T-MO update with radio (Paul O' version) and it's fine.
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
Then why they needed 2 code branches at all???
[Nexus One Q&A, Help & Troubleshooting] darkjedi:
Sorry, I meant to say I wouldn't get 3G reception :).
[Nexus One Q&A, Help & Troubleshooting] attn1:
yes, you would. I do.

APN setting will be different, for one.

The cingular APN is optimized for edge on the T-MO FroYo build, because AT&T won't get 3g on that device. However, all I had to do was restore my APN backup (free market app APN Backup & Restore) and my 3g was working normally again. It always worked, but graphics were being compressed with the new APN setting, even though 3g was working. I have not noticed any other issues with the FRF50 build.
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
That's what I tried to say.

You could still get 3G at 2100 MHz, since both radios support that, but maybe not on the other frequencies.

Though I agree that it would strange to have HW-specific stuff in the OS (supposing the drivers are the same for both radios).
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
But any new devices, be it ATT or TMO compatible, don't have any APN settings at all!

I just bought my ATT compatible N1 and had to configure my APN from scratch.
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
Why? I have an AT&T N1 and did not configure any APN settings and was up and running without any issues.
[Nexus One Q&A, Help & Troubleshooting] attn1:
Odd, I did not have to do that.
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
I cant imagine you would have to manually configure your own APN settings...the average user would not know what that is or how to do it. it would not make sense.
[Nexus One Q&A, Help & Troubleshooting] darkjedi:
Again, I was inferring to a previous quote saying that the radios weren't interchangeable. I was saying if they weren't, I wouldn't get 3G reception at all, which I obviously do...thus the radios being interchangeable.
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
If you go to Settings -> Wireless & Networks -> Mobile network settings -> Access Point Names, you see one APN that was already configured when you first got your phone? Mine was completely empty.

Are you sure you didn't go thru any link to have AT&T text you the APN settings in a SMS message?
[Nexus One Q&A, Help & Troubleshooting] attn1:
Okay, I am (finally) with you.
[Nexus One Q&A, Help & Troubleshooting] mutantblack:
I have my AT&T compatible N1 and I don't have to set anything at all. The phone just picked up signal and set up all the apn by itself. Once I go into setting, it will search for network and found at&t and if you click that, it will also set up automatically.

I didn't have to go through anything else.
[Nexus One Q&A, Help & Troubleshooting] attn1:
Nope, don't remember any of that noise, though I got mine the day it came out. Maybe they cleared it in newer ones because the defaults would not work in Canada and just created more confusion than sending the user to the carrier for APN settings.
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
I didnt get my AT&T N1 until early April...All I had to do was pop in the SIM and away I went. Never configured anything. As soon as I was done with the initial setup tutorial, I began downloading apps and setting up my wifi. Never went in to the APN settings until about 30 minutes ago.
[Nexus One Q&A, Help & Troubleshooting] grifter13:
It didn't work for me. However if you get the pre-rooted Froyo from this forum it will flash without the validation error. However it will send you into a boot loop (android falling out of a box). When you get to that point, do a system recovery from fastboot and you will end up with Froyo. I found this quite by accident. Please note that alot of apps will not show up in Market because they block DEV and Rooted roms.

In my opinion, for AT&T users like us, just wait it out. Since without the apps, it just a Nexus One dumb phone.
[Nexus One Q&A, Help & Troubleshooting] logger:
Just to clarify a misnomer that has evolved with regard to "radios". For whatever reason it has become common practice to describe the software that drives/controls cell phone radio hardware as "the radio". When in fact, as we all know, it is not the radio at all. Perhaps this is where some confusion creeps in? You often read suggestions to "..update to a newer radio to fix problem X.." or similar. Of course you are only upgrading the software. The radio hardware remains unchanged. (Mechanics don't say "I replaced the engine in your car" when all they did was to update the ECU software.)

So while the radio software is interchangeable as Rusty says, the radio hardware is different and not in practical terms interchangeable between B and F handsets. I don't know how this effects the firmware. Just throwing this out there because I reckon it gives rise to confusion.
[Nexus One Q&A, Help & Troubleshooting] attn1:
Horsehockey.
[Nexus One Q&A, Help & Troubleshooting] mlemonds:
the only app that i have had to pull the sim out for is PDAnet.
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
I suppose ATT and TMO have some auto-configuration setting that the carriers in Brazil haven't done yet.

I think it is in the SIM itself, because now I remember the 1st time I tried my N1 I was in the US, roaming on ATT network.

So if it was a mere network thing, it would have configured itself.
[Nexus One Q&A, Help & Troubleshooting] Jesse6749:
I tell you pdanet sucks, even on my iphone 3G I used MyWi instead of pdanet as it worked much better than pdanet. That's why also I am waiting for the official OTA of Froyo to get the built in tethering on Froyo for my N1 :D:D:D.
[Nexus One Q&A, Help & Troubleshooting] attn1:
Because you're on AT&T, not because of your ROM or root access status.
[Nexus One Q&A, Help & Troubleshooting] attn1:
N1 was not available for sale in Brazil, so the APN wasn't configured. If I delete my APN info, I get no data, and it doesn't automatically config itself. I can add it back. Good ROM developers share a pretty extensive APN database that they include in their ROMs. You won't find that on most retail unlocked GSM phones, and ou will rarely find another carrier's APN installed on a branded phone they sell.
[Nexus One Q&A, Help & Troubleshooting] NyceWitIt:
Why even pull the sim card...unless that's just a turn of phrase. Just go into Airplane mode and connect via WiFi.
[Nexus One Q&A, Help & Troubleshooting] mlemonds:
i used it before i rooted and used the wifi tether from google code and now Froyo tether. How does AT&T block that app? just wondering.
[Nexus One Q&A, Help & Troubleshooting] dan1431:
If by "that" you mean the PDANET application, than simply at&t Mobility asks Google to block access to that specific application for all at&t Mobility subscribers.

"Google enters into distribution agreements with device manufacturers and Authorized Carriers to place the Market software client application for the Market on Devices. These distribution agreements may require the involuntary removal of Products in violation of the Device manufacturer’s or Authorized Carrier’s terms of service."

Dan
[Nexus One Q&A, Help & Troubleshooting] fidorulz:
But thats for officially distributed hardware by ATT like the Motorola Backflip its a condition ATT sets up upon selling the device.

Other providers do that too like rogers in canada. For the N1 it was never sold by the providers thus has no restrictions in terms of applications so apps are not regulated by the carriers terms of service
[Nexus One Q&A, Help & Troubleshooting] :
No it's not.
[Nexus One Q&A, Help & Troubleshooting] mlemonds:
thanks for the reply
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
If that were the case, I would have found a different APN set on the APN config view. Instead, it was completely empty.
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
Exactly, if it doesn't know what APN should be there, you get nothing. How stupid would it be if it just slapped a random one in place?
[Nexus One Q&A, Help & Troubleshooting] alurdun:
Are there still problems with this leaked ROM? I've heard some apps don't work, voice input doesn't work, etc.
[Nexus One Q&A, Help & Troubleshooting] mlemonds:
the only app that i have run into that does not work is Listen, but i have heard that there are other apps... just none that i use

Voice input works for me.
[Nexus One Q&A, Help & Troubleshooting] jaeisber:
Sure. There are plenty of apps out there right now that dont work. However, this is not because there are problems with Froyo, rather the developers have not updated their apps to work with Froyo.

Thats like assuming an application coded for Windows 3.x will just work on Windows 7...just doenst work that way. Some applications will work, but others will not.
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
My point being: if it was a "ROM for AT&T", as it has been implied, it would have the APN there anyway, wouldn't it?
[Nexus One Q&A, Help & Troubleshooting] SooSpecial:
Guys, i'm not meaning to be rude, but we come to this thread to read about Froyo for ATT, but I can see the the discussion has gone off topic about APN's and stuff.
[Nexus One Q&A, Help & Troubleshooting] dan1431:
That would be the conventional wisdom, except the agreement between Google and the mobile providers is based on subscribers, not handsets.

Thus, the minute I pop in my at&t Mobility SIM chip into my N1 I loose the ability to download/find certain applications in the market.

Dan
[Nexus One Q&A, Help & Troubleshooting] henriquesp:
As I had suspected, the protection seems to be at the SIM level.

So, it doesn't mean that ATT compatible ROM will have some missing features due to ATT interference.
[Nexus One Q&A, Help & Troubleshooting] kkiran:
Guys, think of the radio debate this way :

If you are into programming, a good programmer will not hardcode the values but make it dynamic to adapt to different values. The same way, the hardware changes, but the software latches to whatever hardware is available. T-Mo3GBands and ATT3GBands talk to the same variables in the software on different phones respectively. What say?
[Nexus One Q&A, Help & Troubleshooting] attn1:
APN backup and restore backs up over 100 APNs on mine. I see only one - the one that works with my sim.
[Nexus One Q&A, Help & Troubleshooting] webfrm:
Updates

OK so I'm strongly thinking about rooting the phone and installing Paul's ROM. I just need clarification that by doing that I will no longer receive OTA updates and will need to check XDA for them in the future. Is that correct?
[Nexus One Q&A, Help & Troubleshooting] lewy10:
don't do it. Just wait for the OTA update. By then the folks over at Google will have all the bugs fixed for the EPE54B 2.2 froyo update.
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
I believe you wont with Paul's, but if you want them, you just can to flash an entire ERE27 image, then use the 'official' FRF50 update.zip to update that.
[Nexus One Q&A, Help & Troubleshooting] webfrm:
Can't decide what to do.

I heard an issue with the ERE27 is the radio isn't compatible with att, so I didn't even consider it. Can I downgrade to that and still keep my 3G radios?

I am willing to wait (each article on the web and update on marketplace app is making it difficult) for official version. Do you know how long it could take? What is Google's typical update time for N1? Could it be months or are we thinking June? I heard folks on some devices just got 2.1 and we've had that on the N1 for months.
[Nexus One Q&A, Help & Troubleshooting] Rusty!:
Radio software is interchangeable, so you'll be OK. Worst case scenario would be you flash back to EPE54B anyway.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
we will have the update within a week or so. google said "in the next few weeks". so just sit tight, you will have the udpate before you know it. it will NOT take months...only a week or so.
[Nexus One Q&A, Help & Troubleshooting] webfrm:
Sitting tight

OK i can wait to the first heat wave (before July) till I need some Froyo to cool me off. But if Google isn't done cooking it by then I may need to take matters into my own hands LOL.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
now that i finally i rooted i'm thinking about trying out froyo, but i have some questions.

first, i understand froyo brings a new radio, but i am more than happy with my existing radio functionality. is this something i should worry about?

anyway since i'm using an ATT version, and running cyanogen 5.0.7, can i just update to froyo, then make a nand backup, and jump back and forth between froyo and cyanogen whenever i want?

will my market be screwed up once i do this?
[Nexus One Q&A, Help & Troubleshooting] superT0M:
I have an at&t n1 and i have manually updated using the leaked 2.2 ota update

i have posted instructions and the files needed to update on my website

oepete.com/n1update.htm
[Nexus One Q&A, Help & Troubleshooting] superT0M:
AT&T users can install ere27 if their bootloader is unlocked

once stock ere27 is loaded you can update to FRF50. instructions are here oepete.com/n1update.htm
[Nexus One Q&A, Help & Troubleshooting] pendo:
How does this work if I'm using OS X?
[Nexus One Q&A, Help & Troubleshooting] webfrm:
Two Weeks and my hand is not cold.

OK folks is anyone else annoyed at Google for not willing to send a release for ATT? Are folks finding alot more crashes (more so than they had on 2.1) with this "pre-release" version? Are all the froyo "rooted" users and pre-release doing OK? Are you not experiencing less FC issues than you had before?

Than I'm looking to say "FU to the warranty" sorry but if they don't explain what's the delay they are leaving me few options. I could ebay the damn device and get a Iphone 4g since Apple doesn't announce stuff and not send out the release immediately after. I'm so upset I didn't return the Nexus in the first two weeks at least I could have gotten my money back. Sorry Google but creating a "have and have nots" based on your carrier is just bull****.:mad:
[Nexus One Q&A, Help & Troubleshooting] :
People, there is no"delay", because the original "release" wasn't actual release but a mistake.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
you want to sell the device because you didnt get an update 2 weeks earlier than you're supposed to? i would just sell it now then. seriously the update will be out before you know it, and years from now you will look back and think how silly you were. "man was i THAT upset over some software something or other?"

besides you have a working device now. its not like we are all waiting with our non-functioning bricked phones until google gives us working software. 2.1 is here and works just fine.

anyway i rooted over the weekend finally and tried cyanogen, then tried froyo. then back to cyanogen, pimped it out and it rocks. but now i loaded back up to froyo and finally enjoying it and testing it.
[Nexus One Q&A, Help & Troubleshooting] Xaositek:
Well I made the hop almost immediately and haven't had any negative impacts.

I recently swapped to the following Froyo ROM:

[ROM] RoDrIgUeZsTyLe @ FroYo MCR R16 MOD 1.113Ghz OC/UV/XTRA/BTN/AUDIO/RAM/NEO KERNEL

Works great, even a slightly beneficial speed bump to 1.113ghz.
[Nexus One Q&A, Help & Troubleshooting] webfrm:
Still waiting patiently unlike most it seems

Well I'm looking in my drawer of old phones (6 of them) and smart phones (4 of them) so since on average I'm buying a phone every year I doubt I'll feel bad. But since Google is very vague on a release info then why did they release Froyo "accidentally" to the public? No offense to your idea but not really sure it was 2 weeks early. Seems every site from Gizmodo to Engadget and Blogger on Youtube has a Froyo on their N1, with no issues being cited. So again I'm annoyed on the delay with no information. So sorry but Apple never did that.

So your calling me out for being patient yet you already rooted and updated your device. Glad it's working so again my point is why the delay on the release if issues aren't there. If its a whole "let's see what Apple does" thing then it's lame. Folks buy Nexus phones cause we are techy, so a business power play thing is lame. Other android stuff is covered by the ads from Verizon and Sprint. They will more than make up the Ad fights with Apple going forward. So unless they are releasing Froyo on all devices and not the N1 then stop the delay. Sorry but wikipedia is already posting all the Gingerbread stuff so I would like my frozen treat by now.
[Nexus One Q&A, Help & Troubleshooting] RogerPodacter:
i used my phone stock for 3 months before i finally decided to root about 5 days ago. so yeah, i was pretty patient. i didnt root to get froyo, i rooted to get cyanogen 5.0.7, which was totally worth it.
[Nexus One Q&A, Help & Troubleshooting] texas-saluki:
thoughts

Anyone seen any movement on this front? Since everyone originally thought this was weeks away at the end of May and we are now at the end of june...
[Nexus One Q&A, Help & Troubleshooting] niematunikogo:
Since the OTA is being pushed to nexus one... I have a question:

Did anyone using AT&T nexus got the OTA?

thanks!
[Nexus One Q&A, Help & Troubleshooting] dewthat:
There has not been an EPE54B update issued yet that anyone knows about.
[Nexus One Q&A, Help & Troubleshooting] akey:
Judging from the way we were excluded from the initial release in May, I have a feeling we will be the last group (AT&T build EPE54B) to see the OTA.:(
[Nexus One Q&A, Help & Troubleshooting] kkiran:
Whatever happened to that Booker-T hack where you can root without unlocking the bootloader. If that surfaces, we can spring forward to rooting and getting Froyo'd!

I find it strange that Google is outright ignoring us, EPE54B folks. There must be some reason - poor sales numbers or something but for the same hardware, they have no reason to boot us out of the press releases or other builds from Google.
[Nexus One Q&A, Help & Troubleshooting] niematunikogo:
is there any confirmed HARDWARE difference between T-M and AT&T build?

I'm from Poland and it really makes no difference for me which build I would use (Polish 3g freq is supported by both). When buying N1 I've just made a random choice.. if there is no HW differences it would be possible to change software built?

can someone please clarify this for me? thanks!
[Nexus One Q&A, Help & Troubleshooting] kaiser_tytnii:
guys! why don't you try to root your EPE54B without unlocking the bootloader

i have been trying on mine but adb won't see my devices in recovery so i am pretty much stuck on step 4 or so...

can you guys give it a try if you want froyo so badly...

in that way, you keep your warranty while you gain root access to flash to any ROM of your choice.

http://xdaforums.com/showthread.php?t=710842

http://xdaforums.com/showthread.php?t=710351

hope we EPE54B user can achieve root without unlocking the bootloader as well!
[Nexus One Q&A, Help & Troubleshooting] jjss75:
I had a stock ATT EPE54B waiting for the Froyo OTA but finally gave up.

Checkin rumors on Froyo for us was making me sick.

so mine is rooted.

no more warranty i know.. but to come and think of it, N1 I believe was made to be rooted and a total geek phone. All the best custom roms, themes and updates are available at lightning speed for the N1 with great mods and extra features that the devs create.

Just wanted to give out a word those who are contemplating whether or not they should wait for the OTA.

Definitely backup first. everything will be wiped in the rooting process. flashed Paul's latest r19 rom from modaco straight from EPE54B and I had no problems of brick etc. Please just dont forget to update the radio, or else you wouldnt have wi-fi working.

Once uve got that done, you pretty much can flash any custom rom out there with wonderful themes/skins, tweak options you def cant do on official. and its so easy switching roms after doing the ONLY hard part.. rooting.

hope u guys do it.
[Nexus One Q&A, Help & Troubleshooting] niematunikogo:
well, my warranty is also lost now ;)

I bought my N1 1 month ago and have been patient till yesterday :)

I still dont have froyo but since i bought 32gb card I decidec that this is the best moment to follow wiki.cyanogenmod.com/index.php/Full_Update_Guide_-_Nexus_One_Firmware_to_CyanogenMod and now I'm waiting for CyanogenMod v6 which will be based on FroYo.

as for now I have this impression that v 5.0.8 (current) is a bit faster than Eclair and has more features.