5,600,335 Members 34,110 Now Online
XDA Developers Android and Mobile Development Forum

Froyo OTA Finally!

Tip us?
 
JoelOFH
Old
#101  
Senior Member
Thanks Meter 0
Posts: 134
Join Date: Sep 2009
Quote:
Originally Posted by logger View Post
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.
manually flash 50 then this. it will work and you'll be up to speed!
Nexus One
 
attn1
Old
#102  
attn1's Avatar
Recognized Developer
Thanks Meter 1789
Posts: 2,542
Join Date: Mar 2010
Quote:
Originally Posted by phocusrs View Post
failed on verifying data... Recovery 1.7.0 on build FRF72
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.
Join the #burstroot IRC channel
 
mkment
Old
#103  
Junior Member
Thanks Meter 0
Posts: 3
Join Date: Jun 2010
Quote:
Originally Posted by uansari1 View Post
Precisely. This isn't the official update. End.
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.
 
iboj007
Old
#104  
Senior Member
Thanks Meter 32
Posts: 419
Join Date: Aug 2005
Location: Maryland
Quote:
Originally Posted by logger View Post
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.
Exactly what many of us are looking for.....
 
Mo_Nexus
Old
#105  
Mo_Nexus's Avatar
Senior Member - OP
Thanks Meter 3
Posts: 112
Join Date: Jun 2010
Location: Dallas, TX

 
DONATE TO ME
Quote:
Originally Posted by uansari1 View Post
Precisely. This isn't the official update. End.
why would it be done ota then?
flybyme Old
#106  
Guest
Thanks Meter
Posts: n/a
Quote:
Originally Posted by uansari1 View Post
Precisely. This isn't the official update. End.
donut was an incremental update fyi....

they could have made incremental updates for certain builds
 
iboj007
Old
#107  
Senior Member
Thanks Meter 32
Posts: 419
Join Date: Aug 2005
Location: Maryland
Quote:
Originally Posted by Mo_Nexus View Post
why would it be done ota then?
This looks like an incremental update for those already on Froyo....
 
sstang2006
Old
#108  
sstang2006's Avatar
Senior Member
Thanks Meter 62
Posts: 516
Join Date: May 2009
Quote:
Originally Posted by Mo_Nexus View Post
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
V/Telephony( 1182): getOrCreateThreadId uri: content://mms-sms/threadID?recipient=%2B18172052287
D/dalvikvm(* 185): GC_FOR_MALLOC freed 5642 objects / 439096 bytes in 80ms
V/Telephony( 1182): getOrCreateThreadId cursor cnt: 1
W/KeyCharacterMap( 1251): No keyboard for id 65540
W/KeyCharacterMap( 1251): Using default keymap: /system/usr/keychars/qwerty.kcm.bin
D/Mms:app ( 1182): getSmsNewMessageNotificationInfo: count=1, first addr=+18172052287, thread_id=1
I/AudioService(** 86):* AudioFocus* requestAudioFocus() from android.media.AudioManager@44c46a48
W/AudioFlinger(** 66): write blocked for 175 msecs, 3 delayed writes, thread 0xd7a8
I/AudioService(** 86):* AudioFocus* abandonAudioFocus() from
thank you Hanan
Evolution::
 
boesky
Old
#109  
Member
Thanks Meter 5
Posts: 70
Join Date: Jun 2010
Quote:
Originally Posted by Mo_Nexus View Post
why would it be done ota then?
Amen to that.
 
attn1
Old
#110  
attn1's Avatar
Recognized Developer
Thanks Meter 1789
Posts: 2,542
Join Date: Mar 2010
Quote:
Originally Posted by GenesysLV View Post
This must be some sort of incremental update. Wouldn't a real froyo release be for pre FRF50 builds?
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.
Join the #burstroot IRC channel

Tags
froyo, ota
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


XDA PORTAL POSTS

Intelligently Place Contacts on Your Home Screen with CallWho Widget

There are plenty of ways to get your contacts to show up on your … more

Control TWRP from within Android with TWRP Coordinator

You may recall that back when TWRP2 introduced a couple of years ago, it brought with … more

Keep Track of Everything Your Device Does with Event Logger

Regardless of their OS choice, computing power users generally share one common … more

A More Competitive Spin on the Addictive 2048 Puzzle

You may recall that a few weeks ago, we talked about a rather interesting take on … more