yashsingh1/xdaforums huggingface dataset:
[Nexus One General] Mo_Nexus:
does this help??

D/dalvikvm(* 555): GC_EXPLICIT freed 6245 objects / 303088 bytes in 55ms

I/CheckinTask(* 211): Checkin success: https://android.clients.google.com/checkin (1 requests sent)

D/dalvikvm(* 211): GC_FOR_MALLOC freed 4126 objects / 417032 bytes in 46ms

I/CheckinService(* 211): From server: Intent { act=android.server.checkin.FOTA_CANCEL }

D/alogcat ( 1251): stopping ...

D/alogcat ( 1251): resumed

I/ActivityManager(** 86): Displayed activity org.jtb.alogcat/.LogActivity: 471 ms (total 471 ms)

D/dalvikvm( 1251): GC_FOR_MALLOC freed 2091 objects / 177048 bytes in 59ms

D/dalvikvm( 1251): GC_FOR_MALLOC freed 2153 objects / 230952 bytes in 35ms

D/dalvikvm( 1251): GC_FOR_MALLOC freed 1897 objects / 462080 bytes in 32ms

D/dalvikvm( 1251): GC_FOR_MALLOC freed 2579 objects / 239976 bytes in 34ms

D/dalvikvm( 1251): GC_FOR_MALLOC freed 2903 objects / 454168 bytes in 36ms

D/dalvikvm( 1251): GC_FOR_MALLOC freed 2728 objects / 499432 bytes in 34ms

D/MobileDataStateTracker(** 86): hipri Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default,supl,mms

D/MobileDataStateTracker(** 86): replacing old mInterfaceName (rmnet0) with rmnet0 for supl

D/MobileDataStateTracker(** 86): replacing old mInterfaceName (rmnet0) with rmnet0 for mms

D/MobileDataStateTracker(** 86): default Received state= CONNECTED, old= CONNECTED, reason= (unspecified), apnTypeList= default,supl,mms

D/NetworkLocationProvider(** 86): onDataConnectionStateChanged 3

D/dalvikvm(* 818): GC_EXPLICIT freed 88 objects / 8016 bytes in 112ms

D/dalvikvm(* 636): GC_EXPLICIT freed 49 objects / 2232 bytes in 81ms

W/AudioFlinger(** 66): write blocked for 175 msecs, 3 delayed writes, thread 0xd7a8

I/AudioService(** 86):* AudioFocus* abandonAudioFocus() from
[Nexus One General] GenesysLV:
:confused: Log? Nice. Now everyone will be calling you.
[Nexus One General] MrNameless:
here is a proof from FrAndroid:

i'm not sure that it is real, because you can simply edit the build.prop file
[Nexus One General] wesbalmer:
Nope, can you pm me the whole logcat
[Nexus One General] IamJAX:
Great news guys. I found the url from my logcat file. It is indeed FRF83. Here is it. Enjoy.

http://android.clients.google.com/packages/passion/signed-passion-FRF83-from-FRF50.38d66b26.zip
[Nexus One General] :
thanks ! ths it
[Nexus One General] wesbalmer:
I edited my post on the first page to reflect the address. OP, please change your original post to include the update link

http://android.clients.google.com/packages/passion/signed-passion-FRF83-from-FRF50.38d66b26.zip
[Nexus One General] xsnipuhx:
Great success!
[Nexus One General] tr.slate:
this is for frf50? ****, im on frf72!
[Nexus One General] daeshawn:
booooooooooom
[Nexus One General] rori~:
Cool!! - only 8 pages to get that :D
[Nexus One General] Markdental:
Great job. Got it downloaded. But it likely wont work on custom recovery.
[Nexus One General] dwd3885:
i got checkin: success as well. but i'm not sure what to do after that.
[Nexus One General] erikiksaz:
Same problem, what to do? :eek:
[Nexus One General] IamJAX:
Yea it is from FRF50.

But the OP can probably help you. He is on FRF72 when he got the new update notification. I hope he soon finds the url from his logcat file.
[Nexus One General] G1-evolve:
1.78 MB?

(omgsrs?)
[Nexus One General] TFJ4:
XDA claims another winnnn :D
[Nexus One General] MrNameless:
only few bug fixes i think
[Nexus One General] knightnz:
FRF83 and FroYo AOSP both out today, Cyanogen & his team are working hard, CM 6.0 is imminent people! :)

Once again, thanks to all those helping the cause. Looking forward to having trackball-wake once again.
[Nexus One General] tr.slate:
meh, im going to try to reflash to frf50 then upgrade to frf83.
[Nexus One General] insomnia:
should this 1.8 MB file update be tried on Kang o Rama 09b2?
[Nexus One General] JoelOFH:
has anybody tried to flash this over frf72? what happens?
[Nexus One General] :
you cant...build.prop doesnt allow it
[Nexus One General] phocusrs:
failed on verifying data... Recovery 1.7.0 on build FRF72
[Nexus One General] Katadare:
Hmm, it's smaller than the FRF72 from FRF50

Guess they trimmed some stuff out...
[Nexus One General] JoelOFH:
shoot. well, im waiting for my ota... or something to post the link... or cm6! come on, world!
[Nexus One General] mkment:
This. Stock FRF72 and stock recovery, update fails.
[Nexus One General] tr.slate:
yeah, doesnt work over frf72. And i tried reflashing frf50, but i think you have to be coming from eclair for that one to work. so im stuck on frf72 right now...
[Nexus One General] G1-evolve:
Think I can flash over CM508?
[Nexus One General] rodigezstyle:
It´s a Joke right...?!
[Nexus One General] G1-evolve:
of course.
[Nexus One General] IamJAX:
According to attn1, the update needs to repacked in order to be flashed via custom recovery image. I guess that is why it doesn't update for me even though I got the OTA.

All of us on custom recovery should wait for someone to repack this update.
[Nexus One General] GenesysLV:
This must be some sort of incremental update. Wouldn't a real froyo release be for pre FRF50 builds?
[Nexus One General] Katadare:
Have you tried reverting to Eclair with the PASSIMG method?
[Nexus One General] logger:
So it should flash over my bog standard 2.1-update1 (EPE54B)? If anyone gets it to load on a stock non-rooted 850mhz N1 - PLS report back.
[Nexus One General] uansari1:
Precisely. This isn't the official update. End.
[Nexus One General] JoelOFH:
manually flash 50 then this. it will work and you'll be up to speed!
[Nexus One General] attn1:
you must have stock recovery to run OTA updates.

You will either have to flash back to stock or else wait for a repacked ROM you can flash with custom recovery.

I don't suppose anyone noticed a new recovery in the FRF083 update.
[Nexus One General] mkment:
I seem to recall google saying the pre-release froyo builds would still get the final OTA update when they confirmed that FR50 was not the final build. This would be perfectly legit in that case.
[Nexus One General] iboj007:
Exactly what many of us are looking for.....
[Nexus One General] Mo_Nexus:
why would it be done ota then?
[Nexus One General] :
donut was an incremental update fyi....

they could have made incremental updates for certain builds
[Nexus One General] iboj007:
This looks like an incremental update for those already on Froyo....
[Nexus One General] sstang2006:
thank you Hanan
[Nexus One General] boesky:
Amen to that.
[Nexus One General] attn1:
it is definitely an incremental. It would be nice to get a link to the Eclair updates - those should be full ROMs.

In the Incremental - no radio - so it looks like the FRF50 radio firmware is final.
[Nexus One General] DroidRC1:
can someone please make a Update.zip for a custom recovery for us rooted people :D
[Nexus One General] jimbob_me:
Just to confirm, i just tried flashing this FRF83 1.8mb zip on my nexus with RA nexus 1.6.2 recovery and the installation was aborted and unsucessfull. Im currently on built FRF50.

Jim
[Nexus One General] Daneshm90:
Im confused cant u just sign this with testkeys or w/e n then ur recovery will let u flash ?

Another thing would be this wont work on deodexed builds, as it applies the patches onto the odex's.
[Nexus One General] DroidRC1:
I don't know how to...so I'm hoping a dev or someone who knows how to, to do it for us..
[Nexus One General] mlemonds:
ya this ^^^

... but it failed to install with custom recovery
[Nexus One General] uansari1:
Sorry guys, I meant this was not the "full official" build of Froyo. This is just an incremental, as you all have pointed out, just like FRF72. So we'll have to wait patiently for the complete update to the complete Froyo build.
[Nexus One General] Daneshm90:
Lol its actually quite easy. But w/e,

Here try this its signed with testkeys, remember u gotta have a odexed build otherwise it'll fail.

Link
[Nexus One General] DroidRC1:
I'm running stock Frf72..Will this still work..heard u have to b running frf50
[Nexus One General] Daneshm90:
Im not sure, ur best bet as always is to nandroid before proceeding. :D

Hmm it patches recovery as well, i wonder if i should remove that.
[Nexus One General] UNICORN025:
i just tryed it with stock n1 with frf72 and it did not work quess we have to wait for the official froya update
[Nexus One General] uansari1:
It'll just fail to flash. No harm. So no.. we have to wait for the complete Froyo build.
[Nexus One General] Daneshm90:
What is the error u get ? is it an assert failed or verification crap ?
[Nexus One General] spidermonkeyrob:
Could it be possible that FRF83 is the final build, but the particular download they found was for people coming from FRF50 and there's another download for those coming from 2.1 u1?
[Nexus One General] Katadare:
Can anyone who is on FRF83 comment on protected apps in Market?

ie. are they back?
[Nexus One General] DroidRC1:
That sucks! :( I was just going to try it..thanx for the heads up!
[Nexus One General] nakadm:
If I do a fresh install of FRF50, update to FRF83, then backup (nandroid) and upload, can the backup image be useful to others?
[Nexus One General] phocusrs:
@Daneshm90

Yes

assert failed: file_getprop("/system/build.prop" ....
[Nexus One General] rodigezstyle:
yesyesyes... do it...
[Nexus One General] Daneshm90:
Ah i see, so thats where it checks wht build u have by checking the md5 on the odex u have in system/app. I cud remove the checks but its prolly best i dont cuz then those with the build it was meant to be flashed on will be able to tell us. But it seems ur failing at ur build.prop. This is wht it checks for

assert(file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "google/passion/passion/mahimahi:2.2/FRF83/42295:user/release-keys");
assert(getprop("ro.product.device") == "passion" ||
getprop("ro.build.product") == "passion");
assert(getprop("ro.bootloader") == "0.33.2012" ||
getprop("ro.bootloader") == "0.33.0012");
[Nexus One General] chowlala:
FRF83 IS THE FINAL FROYO BUILD.

It's been pushed to AOSP already!

That means the friggin code had been frozen and is read to be shipped out to us via OTA. If you don't know jack about the codes don't speculate it as not final or as another test build. Wtf guys, seriously.

You can't update if you're on FRF72.

You've have to do a simple downgrade by reflashing FRF50 and then you're ready to go on FRF83.

Jeez.

And stop bloody begging/whining/screaming for OMG PLZ SOMEONE SEND OUT A ROOT UPDATE.

IT WILL COME JUST SIT BACK AND CHILL!
[Nexus One General] rmagruder:
Okay, I was running FRF72.

I reflashed FRF50 and restored the stock recovery image, then renamed FRF83 to update.zip and flashed it.

Came up just fine. I'm in FRF83 per the About screen.

Went to Market, immediately did a search for Vlingo (because I remembered it was a protected app I couldn't see). It shows up.

So it looks like Google has 'thrown the switch'. If you need me to check for the presence of any other particular app that you don't think would show up otherwise, let me know and I'll look.

Cheers all!

Randy
[Nexus One General] Daneshm90:
Yup he's correct. As u can see it checks whether ur build is frf50 in ur build.prop
[Nexus One General] uansari1:
Can you downgrade from FRF72 to FRF50 if you're not rooted? The final build (i.e. the complete update for people on 2.1) is not this file...
[Nexus One General] G1-evolve:
lol....... :rolleyes:
[Nexus One General] nakadm:
Simple question,

Stock Recovery from ERD79?
[Nexus One General] uansari1:
Are you rooted or running an unlocked bootloader?
[Nexus One General] chowlala:
Should be able to, just re-update the using the FRF50?
[Nexus One General] uansari1:
IIRC, you can't downgrade from a lower build without an unlocked bootloader and maybe a custom recovery. I'm fairly certain that if I'm stock and running FRF72, it will throw an error if I try to downgrade to FRF50 when it checks to see if it's a valid update file. Someone please correct me if I'm wrong...until then, I'm sticking to my original position.
[Nexus One General] DroidRC1:
People on Frf83..has anything changed??
[Nexus One General] tr.slate:
if you are on frf72 youll have to use the passimg method to go back, then you can do frf83. im too lazy though to reset my system so imma wait a minute.
[Nexus One General] j.bruha:
So, wait, am I understanding this correctly? As long as you're running FRF50 with stock recovery, FRF83, the final build, is showing up as an OTA update? REALLY?! :eek:
[Nexus One General] rmagruder:
Gosh, I don't remember which stock recovery image it was. It was one that I had backed up before installing Amon-Ra awhile ago. Apologies for not documenting that :(

As for the bootloader, yes it's been unlocked for some time.

All I'm tryin' to figure out now is whether I need to just 'chill out' and wait for someone to tell me how to root this puppy :)
[Nexus One General] rmagruder:
Answered, but I'll repeat, since i know the posts are flying in hot n heavy.

I did a search for VLingo, a $9.99 protected app, and it came right up. So at this time I believe Google has thrown the switch.
[Nexus One General] shaunm1989:
so does this mean because my phone is not rooted/no unlocked bootloader, and im on FRF72, theres no way i can get to 83 now?
[Nexus One General] uansari1:
For the moment. I'm guessing Google will also start sending OTA updates to those on FRF72 and 2.1-update 1.
[Nexus One General] tr.slate:
no, you will need to use the passimg method.

http://xdaforums.com/showthread.php?t=687795&page=5
[Nexus One General] erikiksaz:
Google's not going to leave you out, don't worry.

I'm sure all these incremental updates weren't meant for the masses, otherwise they would have been mass OTA'd. I'm thinking that all the pre-release froyos so far have only been meant for a very select number of individuals.
[Nexus One General] shaunm1989:
Hopefully OTA goes out today/soon :D

Ill wait and see if i get a OTA before trying this PASSIMG thing
[Nexus One General] JeepFreak:
I was on FRF72, rooted, and I saw FRF83 in ROM Manager so I decided to give it a try. Well, for some reason, it brought me back to FRF50, obviously not rooted. i then rooted with SuperBoot and used ROM Manager to install the FRF83-FROM-FRF50 file linked on the first page of this thread. One last root with SuperBoot and I'm in business! I never had to revert to the stock recovery image... Clockwork Mod the whole way.

HTH!

Billy
[Nexus One General] grandmasterethel:
I don't know if this is of any use to anyone

Claims to be a passimg for frf83, but I don't have my N1 to hand to test it out.

http://www.androidpolice.com/2010/06/23/latest-nexus-one-froyo-rom-leak-frf83/

EDIT: Sorry, missed the third post on the first page.
[Nexus One General] topace13:
Hey guys. One of the people on twitter claiming to have received the OTA update says he got it from 2.1 (t-mo build)

Can't post link, but he's @steven2328

Hmm...
[Nexus One General] mnlk2:
FRF83 apps and fw deodexed except for Bluetooth.apk , just zipped not flashable http://www.scepterr.info/FRF83_Deodexed.zip

from Scepterr on cyanogen IRC
[Nexus One General] cristianossilveira:
What's new?!

Hey guys, i'm the ones who is stuck at FRF72 :(

But tell me, what's new in this 83?....FM radio?!...........i'm begging for this!
[Nexus One General] Daneshm90:
I cud do bluetooth.apk if u give it to me (bluetooth.apk and odex) ;)
[Nexus One General] rmagruder:
Whoa...hang on. You said "one last root with superboot". Which superboot? the page that I see for that has specific versions up to and including FRF50. Did you use the FRF50 Superboot to root a FRF83 Install?

REVISION: I Tried the FRF50 SuperBoot. Worked. HOWEVER: No Wi-Fi. It gets an error . I recall this happened with Cyanogen's Froyo Rooter until someone patched up a new one for FRF72. Are you getting Wi-Fi?
[Nexus One General] mnlk2:
you need just these 2 files? i pull them and upload it :)
[Nexus One General] JeepFreak:
oops... well, my WiFi is down. I'll let you guys know what I figure out about that. the same thing happened when flashing FRF72 earlier.

Billy
[Nexus One General] Daneshm90:
Yup, guy was just missing a jar file in his classpath. javax.obex.jar i believe.

Yea i just need those 2 files.
[Nexus One General] mnlk2:
both are in attachment :)
[Nexus One General] gmonterrosa82:
FRF83

please excuse my ignorance but Im not understanding this, so Im on FRF72 right now but I can't upgrade to FRF83? Why? And would it be done as a update.zip method? Should I just factory reset my nexus one and install the FRF83?
[Nexus One General] Daneshm90:
Here u go.

Link
[Nexus One General] dampit07:
You are currently not allowed to update due to the update checking to see if your build.prop is FRF50. If it is not then you will not be able to update. That is just the current way Google has put out FRF83.

So...now for my question. Is everything there that they said would be?
[Nexus One General] robwscott83:
......+1^^ (edit) nvm.....
[Nexus One General] JeepFreak:
yeah, it worked for FRF72 but i was thinking that might be the problem with WiFi on FRF83.

Billy
[Nexus One General] SoberGuy:
Another n00bish question... can one go from 54 to 50? Not sure why the OTA is only for 50, or how long it will be for the rest of us.

Sent from my Sexy Nexy, courtesy of the fine developers of Tapatalk
[Nexus One General] rmagruder:
I think you're right. I don't see an updated rooter that puts in the new Wi-Fi drivers, so I guess I'm at the mercy of those smarter than me to get an updated rooter or fixes etc to get wi-fi back. With this lot, I give it no more than 2 hours ;)
[Nexus One General] gmonterrosa82:
Thanks so I already Downloaded FRF83 and changed it to update.zip couldn't I just factory reset my nexus one and go from 2.1 to FRF83? Is this possible???
[Nexus One General] thecheatiscool:
As far as I know, you MUST be on FRF50 in order to update...if you're not, it won't work.
[Nexus One General] rmagruder:
IF you are already rooted, I suggest using ROM Manager from the Market to restore to FRF50, and then, if you were forward-thinking enough to have saved a stock recovery.img on your PC, use ADB to push it down. That gets you stock FRF50 and Stock Recovery and you can flash.

If you didn't save a recovery.img, you can probably find a stock recovery image with a few google searches.
[Nexus One General] JCAndroid87:
I been reading everything you guys have said about how you cant get to FRF72 to FRF83. One of my friends that has, well had FRF72 and he did i update his froyo manually, well his friend that works for nokia updated his nexus to FRF83. Was it because first he came from FRF50 To FRF72 and it worked? or it wasn't suppose to work because he was on FRF72? but he updated manually to FRF83.
[Nexus One General] gmonterrosa82:
So here is my question: I have a nexus one non rooted, on T-Mobile. I have in my SD card the FRF83 already changed to "update.zip" I'm on 2.2. Can I just factory reset my nexus one and then install FRF83????
[Nexus One General] Geo411m:
Okay guys I was able to take the deodexed that mnlk2 and daneshm90 posted and rooted it. It worked fine and updated from FRF72. I'll post it up if you guys want.
[Nexus One General] justinhub2003:
Stupid Question.. but I've been out of the hackery since I had my G1 and mytouch but... I have a Stock Nexus One on FRF72, can I flash back to FRF50 or will it not work because Im running stock firmware? I really would like to get paid apps back...
[Nexus One General] rmagruder:
THIS is an interesting development.

So there I was with FRF83, rooted with FRF50 superboot, but getting an error with Wi-Fi.

So, I figure, hm, I'd like the nice Samsung live wallpapers from here:

Android Police Samsung Wallpapers

I need root to install them and they have to be flashed from Recovery, so I download, put the zip on my sd card, go into ROM Manager and Flash Clockwork Recovery using this very nice app.

Selected "Reboot into recovery".

Used Clockwork to flash the live wallpapers and rebooted.

Boots up:

- I have FRF83 - checked

- I have live wallpapers from Samsung - checked (very cool!)

- I have Root (loaded Root Explorer to verify)

- and...I HAVE Wi-Fi!

Don't know why it started working. How could flashing Clockwork or the Samsung wallpapers fix it? I don't know. But they did.

I have it all, peeps ;)
[Nexus One General] SphericalPuma:
Check that it was some sort of glitch.
[Nexus One General] Markdental:
Sure that would be great, this keeps root, and allows update.zip to be run from recovery to update from FRF72 to 83?
[Nexus One General] Katadare:
There have been some questions regarding going to FRF83 from FRF72...

You have 2 options for putting FRF83 onto your phone if you have FRF72

a) Wait for an official OTA update

b) Use the PASSIMG method to get back to STOCK 2.1 then FRF50

Notes:

I am not responsible for what happens to your phone

This will wipe all data, please back up your stuff

It's all STOCK stuff, so... not rooted

I did this one my T-mo (AWS) N1 only

If you can't wait for an official OTA update, you can do the following...

---

For the PASSIMG method to get back to STOCK 2.1:

Get the stock shipping ROM.

Rename file to PASSIMG.zip

Format SD card and Factory Reset your N1

Power Down your phone

Pop out the SD card and put PASSIMG.zip on it

Put the SD card into your phone

Hold Vol Down + Press Power

Bootloader will read passimg

Follow instructions to flash phone

When complete, you will be back at ERD79 (The shipping ROM)

Incremental Updates:

Get ERE27 from ERD79 ROM

Power Down your phone

Pop out the SD card and put rom on it and rename it to update.zip

Put the SD card into your phone

Hold Vol Down + Press Power

Press Vol Down until RECOVERY is highlighted

Press Power

Wait for Android "!" screen

Press Power + Vol Up

Select Apply:update.zip

Reboot when complete

Rinse and repeat Incremental Updates steps with the following ROMs:

FRF50 from ERE27

FRF83 from FRF50

You might also want to wipe data and cache when you get to FRF83 just so you have a fresh start.

I'll see if I can find links to the roms...

GL

---

Oh yeah, I noticed that booting and shutting down was slow and the live wallpaper was laggy when I was on the 2.1 ROM, I think I have been spoiled running froyo since the first FRF50 hit. :-p
[Nexus One General] saint327:
ummm...if your running stock frf72, can't you just flash frf50 and then flash frf83 back on top of that?

Edit: nevermind frf50 from ere27 doh!
[Nexus One General] erikiksaz:
Apparently FRF72 users are being updated to 83 as well, according to androidandme and one of our users here in the General forum.

The androidandme guy mentioned that he was about to downgrade to frf50, but right before he began he was given the OTA notification. 72->83 looks like a 6xx kbyte file. The guy's got a screen shot.

Somebody save the logcat for god sakes!
[Droid Incredible Themes and Apps] n0-0ne:
now that we have an easy way to push update.zip files I was wondering if there was any way to push the host file that adfree android downloads to the sdcard. I know that it doesn't have write access to the system partition when booted but in recovery we do right?

So it should be as simple as creating an update.zip that overwrites the old host right?

I'm going to try to get this working :D

EDIT: Here's how to get this working

1. Search for Adfree Android on the market

2. Install and run

3. allow it to download and install new hosts file, it will copy it to your sdcard and try to replace /system/etc/hosts but fail (it should reboot the phone shortly)

4. Power off the phone and hold Volume Down and power.

5. Use volume down to select recovery

6. In clockwork recovery volume down to "partitions menu" and hit the track pad to select

7. Select "mount /system" and "mount /sdcard" "mount /data"

8. Plug in your usb cord and open a command line on your pc

9. enter adb shell and type the following commands

cp /sdcard/hosts /data/data/hosts

rm /system/etc/hosts

ln -s /data/data/hosts /system/etc/hosts

10. Reboot your phone and enjoy adfree android.

Thanks to all for help in getting this running.