Hi everyone. I maintain reference pages at http://www.randomphantasmagoria.com containing links to all stock firmware for the Nexus S, Xoom, and Galaxy Nexus. I am beginning to work on a page for the Nexus One as well. The problem is...I never owned a Nexus One, so I need someone to help with build history. From searching, it seems like the N1 has had the following firmware builds:
2.1/ERD79
2.1-update/ERE27
2.2/FRF50
2.2/FRF72
2.2/FRF83
2.2/FRF85B
2.2/FRF91
2.2.1/FRG83
2.2.1/FRG83D
2.2.2/FRG83G
2.3.3/GRI40
2.3.4/GRJ22
2.3.6/GRK39F
Now onto my questions:
1. Did I miss any builds?
2. Were there separate builds for the AT&T variant?
3. If there were, did the AT&T builds use different radio images than the T-Mobile version, or were they universal?
3. What was the original stock build that first shipped on the AT&T variant?
4. I saw some references to builds beginning with EPE. What were those about?
5. Does anyone know all the various bootloader versions over the course of the N1's lifetime, and what updates contained a bootloader update?
Any info you could provide would be very helpful. Thanks in advance!
Sent from my Xoom using Tapatalk 2
Anyone?
some helpful links : link1 link2 link3
cant help you with the us stuff i'm from europe.
About hboots, there were only two, i guess, 0.35.0012 and 0.35.0017. But i'm not sure.
All radios are universal.
lacus88 said:
some helpful links : link1 link2 link3
cant help you with the us stuff i'm from europe.
About hboots, there were only two, i guess, 0.35.0012 and 0.35.0017. But i'm not sure.
All radios are universal.
Click to expand...
Click to collapse
Thank you!
Sent from my Xoom using Tapatalk 2
oldblue910 said:
Anyone?
Click to expand...
Click to collapse
Yeah, you are missing a few. I'll try to get a list for you tomorrow.
P.S. The two shipping boot loaders were 0.33.0012 and 0.35.0017, not what was mentioned above. There was also an engineering bootloader or two floating around. 0.35.2017 was one for sure. I think there was 0.33.2012 as well.
As well, there were 3 different build versions if not more: WWE, VF, and KR
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
Yeah, you are missing a few. I'll try to get a list for you tomorrow.
P.S. The two shipping boot loaders were 0.33.0012 and 0.35.0017, not what was mentioned above. There was also an engineering bootloader or two floating around. 0.35.2017 was one for sure. I think there was 0.33.2012 as well.
As well, there were 3 different build versions if not more: WWE, VF, and KR
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks. I'll look forward to your list!
Sent from my Xoom using Tapatalk 2
oldblue910 said:
Thanks. I'll look forward to your list!
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
Sorry, wanted to write 0.33.0012 for the first bootloader. Anyway, glad somebody is helping you. Efrant knows better than me, that's for sure. Looking forward to your n1 section, bookmarked your site.
Here is something to get you going.
OTA update packages
(This is only a very partial list. The Nexus One had quite a few different OTA updates.)
http://android.clients.google.com/p....signed-passion-GRJ22-from-GRI40.71d2f9ec.zip
http://android.clients.google.com/p...signed-passion-GRI40-from-FRG83G.81304b2d.zip
http://android.clients.google.com/p...signed-passion-GRI40-from-FRG83D.4c11eaf5.zip
http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip (FRG33 to GRI40)
http://android.clients.google.com/p...igned-passion-FRG83G-from-FRG83D.2854b06b.zip
http://android.clients.google.com/p...signed-passion-FRG83D-from-FRG83.ecb21b75.zip
http://android.clients.google.com/p...signed-passion-FRG83D-from-FRF91.7957af1a.zip
http://android.clients.google.com/packages/ota/passion/signed-passion-FRF91-from-FRF85B.db99fdf1.zip
http://android.clients.google.com/packages/ota/passion/signed-passion-FRG83-from-FRF91.c8847c98.zip
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-FRF50.836691a1.zip
http://android.clients.google.com/packages/passion/signed-passion-FRF91-from-ERE27.e410116a.zip
http://android.clients.google.com/p...R_FRF91-1.13.1700.1_EPF21B_release_signed.zip
There were also a bunch of updates that contained full roms, so you could update any build to the current one. I think this was the one for GRI40:
http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip
Bootloaders
0.33.0012 Shipping <= can be found in some of the older shipped ROMs, like EPF30
0.33.2012 Engineering
0.33.3012 Developing
0.35.0017 Shipping: http://android.clients.google.com/packages/ota/passion/d6096cac5e9f.signed-hboot-0.35.0017.zip
0.35.2017 Engineering: http://forum.xda-developers.com/showpost.php?p=18141273&postcount=116
0.35.3017 Developing
Models
AMOLED (microp 0b15)
SLCD (microp 0c15) <== needs the 0.35.0017 booloader or higher to function
3G frequency bands
T-Mobile (International) version: 900/1700/2100
AT&T version: 850/1900/2100
Roms
Most ROMs and shipped images can be found here: http://www.shipped-roms.com/ and here: http://htcdev.com/devcenter/downloads
Rom versions
WWE (world Wide English) <== is the "yakju" equivalent...
VF (Vodafone??)
KT_KR (Korean)
Build numbers
(This is only a very partial list. The Nexus One had quite a few different builds.)
EPE54B (WWE)
EPE68 (WWE)
EPE76 (WWE)
EPF30 (WWE)
ERD79 (WWE, original N1 shipping ROM)
ERE27
ERE36B (WWE)
FRF50 (KT_KR only)
FRF72 (KT_KR only)
FRF85B
FRF91 (all versions)
FRG33
FRG83 (all versions) 2.2.1
FRG83D
FRG83G
GRI40 (all versions)
GRJ22
GRK39F
Radios
(I don't remember which shipped image package they came from, but it's easily found on xda or google.)
4.06
5.08
5.12
Amazing. I'll be working on my Nexus One pages tonight.
Now, one question for you...did the new bootloaders come in OTA updates or did they have to be applied independently? I only ask because I noticed you included a link to one.
oldblue910 said:
Amazing. I'll be working on my Nexus One pages tonight.
Click to expand...
Click to collapse
Good luck with that, you're gonna need it! I don't think doing a page up for the Nexus One will be as straightforward as the GS or GN.
oldblue910 said:
Now, one question for you...did the new bootloaders come in OTA updates or did they have to be applied independently? I only ask because I noticed you included a link to one.
Click to expand...
Click to collapse
The 0.35 bootloader was a requirement for Gingerbread. It was push out independently (around the FRG33-83G time frame) AND, if I am not mistaken, bundled together with some of the newer packages. I guess to know for sure, you would have to download all the OTA's from FRF91 and newer and see if any of them contained a bootloader.
I deleted most of my Nexus One files once I replaced it with the GNex, so I can't give you all the info you're looking for.
I still see that N1 daily (I gave it to my son) and I soo miss holding on to a metal device instead of Samsung's garbage plastic.
efrant said:
Good luck with that, you're gonna need it! I don't think doing a page up for the Nexus One will be as straightforward as the GS or GN.
The 0.35 bootloader was a requirement for Gingerbread. It was push out independently (around the FRG33-83G time frame) AND, if I am not mistaken, bundled together with some of the newer packages. I guess to know for sure, you would have to download all the OTA's from FRF91 and newer and see if any of them contained a bootloader.
I deleted most of my Nexus One files once I replaced it with the GNex, so I can't give you all the info you're looking for.
I still see that N1 daily (I gave it to my son) and I soo miss holding on to a metal device instead of Samsung's garbage plastic.
Click to expand...
Click to collapse
Yeah that Nexus One felt great in the hand. One of my coworkers got one the day it was available on the Web Store. I remember feeling quite envious even though I had a brand new T-Mobile/HTC G2, which was a beast in its own right at that time.
This might help you as well.
Continuing our discussion from
[REF] Nexus 4 Stock OTA URLs pages 21-23+ and
[REF] [HOW-TO] [GSM & CDMA] Official Google OTA update URLs -- Latest: JDQ39 / 4.2.2 pages 206-207+ and
IAN67K from IAN67H OTA? pages 1-2+
Following the success of finding update urls for the N4/7/10/NQ, I am expanding the search now to old devices.
I would like to ask for volunteer(s) to try and grab all update urls for their device.
While they may already have most of there update urls found, I would like to request someone to take the time to try and recheck for any missing updates.
As these devices (ADP2/Droid1/N1/NS/xoom) no longer recieve updates anymore, this will only ever need to be done once.
TheManii said:
If you would like to help, here's what you can do:
Reflash to a stock google rom (as it will only work on a stock rom)
Root your device
Change the following lines in build.prop:
SEE LIST BELOW
Check for updates
Post the name of the update zip it downloads
Click to expand...
Click to collapse
List of timestamps and fingerprints:
START FROM THE BOTTOM OF THE LIST!
As google no longer hosts the update zips for builds older then FRG83D anything before #16 may not return anything.
If you are unable to get the updates for 2 seperate roms before #16 you do not have to do the rest, the entire list before that likely will not return anything.
Code:
ro.build.date.utc=1268185808
ro.build.fingerprint=google/passion_eu/passion/mahimahi:2.1-update1/EPE68/27821:user/release-keys
Code:
ro.build.date.utc=1260567348
ro.build.fingerprint=google/passion/passion/mahimahi:2.1/ERD72/22132:user/release-keys
Code:
ro.build.date.utc=1261182874
ro.build.fingerprint=google/passion/passion/mahimahi:2.1/ERD79/22607:user/release-keys
Code:
ro.build.date.utc=1264643580
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE27/24178:user/release-keys
Code:
ro.build.date.utc=1265400343
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/ERE36B/24827:user/release-keys
Code:
ro.build.date.utc=1266976997
ro.build.fingerprint=google/passion/passion/mahimahi:2.1-update1/EPE54B/26040:user/ota-rel-keys,release-keys
Code:
ro.build.date.utc=1268867752
ro.build.fingerprint=google/passion_eu/passion/mahimahi:2.1-update1/EPE76/29009:user/release-keys
Code:
ro.build.date.utc=1272670056
ro.build.fingerprint=google/passion_vf/passion/mahimahi:2.1-update1/EPF30/35377:user/release-keys
Code:
ro.build.date.utc=1274384271
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF50/38042:user/release-keys
Code:
ro.build.date.utc=1276282627
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF72/40830:user/release-keys
Code:
ro.build.date.utc=1277249370
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF83/42295:user/release-keys
Code:
ro.build.date.utc=1277421628
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF85B/42745:user/release-keys
Code:
ro.build.date.utc=1277930906
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF91/43546:user/release-keys
Code:
ro.build.date.utc=1280785520
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRG33/48579:user/release-keys
Code:
ro.build.date.utc=1285103843
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83/60505:user/release-keys
Code:
ro.build.date.utc=1289367572
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.1/FRG83D/75603:user/release-keys
Code:
ro.build.date.utc=1294972077
ro.build.fingerprint=google/passion/passion/mahimahi:2.2.2/FRG83G/91102:user/release-keys
Code:
ro.build.date.utc=1297306326
ro.build.fingerprint=google/passion/passion:2.3.3/GRI40/102588:user/release-keys
Code:
ro.build.date.utc=1303507677
ro.build.fingerprint=google/passion/passion:2.3.4/GRJ22/121341:user/release-keys
Related
I have a factory unlocked n1 that ive only owned for about 3 months.
I noticed its still on FRG83 (not the latest FRF91).
Will I have to do anything special to get the 2.3 update? (Im in the UK if that makes a difference).
FRG83D is the latest, not FRF91.
mcrosmar said:
FRG83D is the latest, not FRF91.
Click to expand...
Click to collapse
Ok, well im still running FRG83 (not FRG83D)...
maxppp said:
Ok, well im still running FRG83 (not FRG83D)...
Click to expand...
Click to collapse
hopefully this will solve your problem
http://forum.xda-developers.com/showthread.php?t=844464
maxppp said:
Ok, well im still running FRG83 (not FRG83D)...
Click to expand...
Click to collapse
to get the latest available update for your phone, dial
Code:
*#*#2432546#*#*
flybyme said:
to get the latest available update for your phone, dial
Code:
*#*#2432546#*#*
Click to expand...
Click to collapse
Thanks, it came up with 'check in succeeded', but nothing else (this was 5 mins ago).
I take it that it doesnt matter that the nexus one wasnt ever offered on my network (o2 uk), and the phone actually polls google servers?
It doesn't matter at all, just have to wait patiently, or force it (as above).
Rusty! said:
It doesn't matter at all, just have to wait patiently, or force it (as above).
Click to expand...
Click to collapse
But 83D came out two and a half weeks ago, isnt that abit too long to wait?
maxppp said:
But 83D came out two and a half weeks ago, isnt that abit too long to wait?
Click to expand...
Click to collapse
Can't you just update using the link provided above?
Im in the uk, running FRG83D and expecting the 2.3 update today. (also on o2)
Could it be my simcard? It works with 3g but its quite old still...
Also do I need to register my IMEI or anything?
Rest of the phone says this.
Code:
android version
2.2.1
baseband version
32.50.00.32u_5.12.00.08
kernel version
2.6.32.9-ge9111ea
[email protected] #1
build number
FRG83
Poolmunch said:
expecting the 2.3 update today. (also on o2)
Click to expand...
Click to collapse
Good luck with that
maxppp said:
Could it be my simcard? It works with 3g but its quite old still...
Also do I need to register my IMEI or anything?
Rest of the phone says this.
Code:
android version
2.2.1
baseband version
32.50.00.32u_5.12.00.08
kernel version
2.6.32.9-ge9111ea
[email protected] #1
build number
FRG83
Click to expand...
Click to collapse
You've got a weird kernel there? And the Korean baseband... my guess is your phone has had the KT FRF91 passimg flashed at some point, which would explain your lack of update.
That is very weird!
Are there any instructions on how to flash the kernel and baseband back to UK defaults?
Also what is the KT FRF91 passimg about, is it anything dodgy / something I should be concerned about?
Edit: I sent my phone to HTC last week and it's come back with a different IMEI...i guess that explains the korean part.
It's not really dodgy, or anything to worry about, it was an easy way for European N1 owners to update to Froyo without unlocking the bootloader back in the day. It does mean you'll lag behind with updates though.
I don't think you'll be able to get back to the proper Google firmware without rooting/unlocking your bootloader due to the 0.35 HBOOT (you can check if you have this or not by turning the phone off, holding in the tackball and powering on, the second line will say either HBOOT-0.33.0012 or HBOOT-0.35.0017).
Ive got the Hboot 0.35.0017 on FRG83D, i got the FRG83 -> FRG83D OTA update when everyone else did. I dont think this is his problem
It's not a problem as such, but it will prevent downgrading to get onto the Google version.
Ok its says HBOOT 35.0017.
If i root the bootloader, can I then flash my way back to 'Default' kernels / radios?
Yes, easily, you might not even have to wipe it in fact.
You use fastboot to flash the system.img and boot.img from the FRG33 image on shipped-roms.
Ok thats great, thanks for all your help.
Just to re-cap, install android sdk / fastbook on my pc, then flash boot.img then system.img from FRG33?
Exactly, although I lied, you will have to wipe.
I forgot that unlocking automatically wipes the phone.
Here is what I pulled off my phone
http://www.multiupload.com/OFWXQJCXBZ
This is the logcat as well
http://www.multiupload.com/JKGT5YYAVH
Here are the radio hashes contained in the OTA:
radio.img -> aa5ab6837c5ef4fe602ea8b5ee6ae544
mdm9k.img -> 373745d310240a57b8e360a40e648178
They match exactly to the leaked 1.13.605.7 radios.
So radio version, 1.16.00.0402w_1, in this OTA update and the leaked release is the same?
Here:
http://twitter.com/#!/TeamAndIRC/status/68719544964882433
And here:
http://twitter.com/#!/TeamAndIRC/status/68717365759709184
List of differences
just because the numbers are same.. it may not mean they are the same. Remember one was never officially released. Unless they are taken apart.. one can't really say if they are the same.
Either way a flashable zip with the officially released OTA should be put out to flash over.
Another update:
http://twitter.com/#!/TeamAndIRC/status/68729302467883008
http://twitter.com/#!/TeamAndIRC/status/68729389340295168
If you're too lazy to click the links then here:
@TeamAndIRC ✔ jcase
Root version of the OTA will not come from us, as we released it two weeks ago already
@TeamAndIRC ✔ jcase
OTA == our leak ... LAME #Thunderbolt
Tekk I can't see your links since Twitter's blocked here at work but I got this from another site:
Recent TeamAndIRC tweets:
Root version of the OTA will not come from us, as we released it two weeks ago already
Posted on May 12, 2011
OTA == our leak ... LAME #Thunderbolt
Posted on May 12, 2011
kriskmk said:
just because the numbers are same.. it may not mean they are the same. Remember one was never officially released. Unless they are taken apart.. one can't really say if they are the same.
Either way a flashable zip with the officially released OTA should be put out to flash over.
Click to expand...
Click to collapse
I'm sorry, but are you serious? Do you know what an MD5 sum is?
Ha thanks Tekk!
Well, that's disappointing.
I would agree since I run rooted RUU leak and I got random reboots. So if VZW pushes the leak as official OTA, then I don't see how they won't get ton of support calls on this from non-rooted customers.
Funny...after looking at the thunderbolt_instructions.pdf from Verizon's Support site, it shows the size of the update at 22.277 MB, but the other screenshots from droid-life are showing it at 35.649 MB...wonder what the difference could be?
wraithdu said:
I'm sorry, but are you serious? Do you know what an MD5 sum is?
Click to expand...
Click to collapse
My comment was to the guy who referenced the radio numbers..I didn't even see your post. Still curious why the OTA is about 10 MB larger.
kriskmk said:
Still curious why the OTA is about 10 MB larger.
Click to expand...
Click to collapse
They supposedly did some updating to Backup Assistant and a few other software peices but it looked like mostly bloat (at least from the pdf description.)
From the PDF:
SOFTWARE UPDATE
GET THE MOST OUT OF YOUR THUNDERBOLT BY HTC.
Verizon Wireless is pleased to announce a new software update,
Build Number: 1.13.605.7 Baseband: 1.16.00.0402w_1,
for your ThunderBolt™ by HTC.
Verizon Wireless and HTC encourage you to download this update.
Web Browsing and Data Access
+ Enhanced data connectivity when accessing the Verizon 3G network.
Email and Messaging
+ SMS and MMS messages are stored properly in the Messaging
Application (Inbox, Sent, etc.).
Additional Device Features
+ Timing for device activation has been improved.
+ “Backup Assistant” is correctly displayed in the Application menu.
+ Stability improvements for data centric applications such as
Facebook, KAYAK, Yahoo! Mail, My Verizon and more.
+ Accurate location is displayed when accessing the Weather Widget.
+ Quickly load GPS updates for Google Maps and VZ Navigator
100% byte for byte the same as our last leak.
Thanks j for verifying this.
I for one am excited for the OTA. Now everyone elses phone can reboot randomly just like ours.
kriskmk said:
My comment was to the guy who referenced the radio numbers..I didn't even see your post. Still curious why the OTA is about 10 MB larger.
Click to expand...
Click to collapse
Ah, understood.
@jcase
Good to hear!
jcase said:
100% byte for byte the same as our last leak.
Click to expand...
Click to collapse
Good to know. Thanks J!
THIS THREAD IS FOR GPE OWNERS TO DISCUSS OTA UPDATES. IT IS NOT FOR DISCUSSION OF HOW TO CONVERT A REGULAR M8 TO A GPE, NOR IS IT FOR DISCUSSION ON HOW TO FLASH ROMS.
Hi Everyone,
As I do with all Nexus and GPE devices, I intend to maintain a thread here with links to all the stock OTA updates for the HTC One M8 Google Play Edition. Each time there is an OTA update, its direct link on Google's servers will be posted here for reference and posterity. I also mirror these files at http://www.randomphantasmagoria.com/htc-one-m8/m8_google.
Any questions about flashing these OTA updates can be discussed and answered here as well. In addition, if you get an OTA update, please pull the URL from logcat so it can be posted here.
Current firmware (m8_google): Android 5.1/LMY47O.H10
LMY47O.H10 from LMY47O.H9 - http://android.clients.google.com/p...E_4.04.1700.10-4.04.1700.9_release_453088.zip
LMY47O.H9 from LMY47O.H6 - http://android.clients.google.com/p...WE_4.04.1700.9-4.04.1700.6_release_449381.zip
LMY47O.H6 from LRX22C - http://android.clients.google.com/p...WE_4.04.1700.6-3.11.1700.5_release_430318.zip
LMY47O.H6 from LMY47O.H5 - http://android.clients.google.com/p...WE_4.04.1700.6-4.04.1700.5_release_430317.zip
LMY47O.H5 from LMY47O.H4 - http://android.clients.google.com/p...WE_4.04.1700.5-4.04.1700.4_release_429773.zip
LMY47O.H4 from LRX22C - http://android.clients.google.com/p...WE_4.04.1700.4-3.11.1700.5_release_428195.zip
LRX22C from KTU84P - http://android.clients.google.com/p...WE_3.11.1700.5-2.12.1700.1_release_403384.zip
KTU84P from KTU84L - http://android.clients.google.com/p...WE_2.12.1700.1-2.10.1700.4_release_381457.zip
KTU84L from KOT49H - http://android.clients.google.com/...E_2.10.1700.4-1.16.1700.16_release_378258.zip
SPECIAL THANKS
LlabTooFeR
Graffixnyc
EthanFirst
SpaceCadetWilliam
EagerestWolf
Isotopes
olahj
Has anyone preordered one yet?
Sent from my Z Ultra Google Play Edition using Tapatalk
oldblue910 said:
THIS THREAD IS FOR GPE OWNERS TO DISCUSS OTA UPDATES. IT IS NOT FOR DISCUSSION OF HOW TO CONVERT A REGULAR M8 TO A GPE, NOR IS IT FOR DISCUSSION ON HOW TO FLASH ROMS.
Hi Everyone,
As I do with all Nexus and GPE devices, I intend to maintain a thread here with links to all the stock OTA updates for the HTC One M8 Google Play Edition. Each time there is an OTA update, its direct link on Google's servers will be posted here for reference and posterity. I also mirror these files at http://www.randomphantasmagoria.com/htc-one-m8/m8_google.
Any questions about flashing these OTA updates can be discussed and answered here as well. In addition, if you get an OTA update, please pull the URL from logcat so it can be posted here.
Since we do not currently have any OTA updates nor does anyone have the device yet, I'm merely waiting for someone to get the actual device and provide the following information:
1. HBOOT version (can be retrieved from the bootloader screen)
2. Baseband version
3. The values of ro.build.date.utc and ro.build.fingerprint from /system/build.prop.
Please make sure to get this information before applying any out-of-the-box OTA update that might be available for the phone. At that stage, you can feel free to apply any OTA update that's available, then please get this information again post-update.
Thank you!
Click to expand...
Click to collapse
Here you go...
ro.bootloader: 3.18.0.0000
ro.baseband: 1.14.21331931.LA02_2G
gsm.version.baseband: 1.14.21331931.LA02_2G_20.30A.4145.01L
ro.build.date.utc: 1395410996
ro.build.fingerprint: htc/m8_google/htc_m8:4.4.2/KOT49H.H16/326432:user/release-keys
ro.build.description: 1.16.1700.16 CL326432 release-keys
LlabTooFeR said:
Here you go...
ro.bootloader: 3.18.0.0000
ro.baseband: 1.14.21331931.LA02_2G
gsm.version.baseband: 1.14.21331931.LA02_2G_20.30A.4145.01L
ro.build.date.utc: 1395410996
ro.build.fingerprint: htc/m8_google/htc_m8:4.4.2/KOT49H.H16/326432:user/release-keys
ro.build.description: 1.16.1700.16 CL326432 release-keys
Click to expand...
Click to collapse
You, sir, are awesome. Thank you! Just out of curiosity, is this the actual shipping firmware that the first round of devices will ship with or is that prerelease?
Sent from my Z Ultra Google Play Edition using Tapatalk
oldblue910 said:
You, sir, are awesome. Thank you! Just out of curiosity, is this the actual shipping firmware that the first round of devices will ship with or is that prerelease?
Sent from my Z Ultra Google Play Edition using Tapatalk
Click to expand...
Click to collapse
Well, I'm quite sure this is ship version coz kernel source was released for this base...
You are indeed correct with all your info. It matches perfectly to the device that Android Central got for unboxing and hands-on. Thanks again for your help!
Hey guys,
Today is Nexus OTA day, Android 4.4.3/KTU48F. So, if history holds up, we'll be seeing GPE OTAs in about 2 weeks. This will obviously be the first OTA for the M8 GPE. I just want to put it on everyone's radar that if you get the OTA, please post the filename here. You can get it from logcat. If you get the OTA, but don't know how to get the filename, let me know and I'll help you out.
Thanks!
So, I'm hoping someone here on XDA actually owns an M8 GPE (a real one, not a converted one) and will be able to help get the OTA URLs. Do I have any volunteers? Thanks in advance!
oldblue910 said:
So, I'm hoping someone here on XDA actually owns an M8 GPE (a real one, not a converted one) and will be able to help get the OTA URLs. Do I have any volunteers? Thanks in advance!
Click to expand...
Click to collapse
What's the difference if it's a real one or converted one? The ota will be the same.. The URL will be the same... The file will be the same.. It shouldn't matter if it's a real one or a converted one (which in the system's eye there is no difference between a converted one and "real" one.)
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
What's the difference if it's a real one or converted one? The ota will be the same.. The URL will be the same... The file will be the same.. It shouldn't matter if it's a real one or a converted one (which in the system's eye there is no difference between a converted one and "real" one.)
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
By "converted", I meant people who are just running a GPE ROM. If there's a full conversion that allows you to use the bootloader and radio as well, and allows you to accept OTAs, then yeah, by all means, help a brother out!
oldblue910 said:
By "converted", I meant people who are just running a GPE ROM. If there's a full conversion that allows you to use the bootloader and radio as well, and allows you to accept OTAs, then yeah, by all means, help a brother out!
Click to expand...
Click to collapse
Ahh OK.. Yeah, I did the full conversion (my thread is in dev) I have a fully converted gpe (radio, bootloader, recovery etc..) So when the ota drops I'll post a link for ya if someone doesn't beat me to it.
Sent from my HTC One_M8 using Tapatalk
graffixnyc said:
Ahh OK.. Yeah, I did the full conversion (my thread is in dev) I have a fully converted gpe (radio, bootloader, recovery etc..) So when the ota drops I'll post a link for ya if someone doesn't beat me to it.
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Much appreciated.
hey guys. So I have a "real" GPE from google. I've been reading a lot around here as my only past experience is with samsung and nexus devices so this is a bit different.
It's also hard cause there is much more info on the carrier devices and hard to sift through and see what applies to the GPE variant.
So I've learned my system partition is different. I can look into that further I'm pretty good on samsung on messing with stock images and adjusting them.
Bootloader unlock is trivial on GPE, fastboot oem unlock.
I flashed twrp and rooted.
Last thing is s-off. Is s-off easier on GPE like bootloader unlock or would I still need firewater for it?
To the point of this thread, when an OTA comes out will that effect s-off? I imagine it'd remove root but I believe I can edit the image to retain root and flash with TWRP easy enough, I've done it on samsung and nexus devices enough.
How's the gpe radio compared to tmobiles?
Sent from my HTC One_M8 using Tapatalk
mrRobinson said:
hey guys. So I have a "real" GPE from google. I've been reading a lot around here as my only past experience is with samsung and nexus devices so this is a bit different.
It's also hard cause there is much more info on the carrier devices and hard to sift through and see what applies to the GPE variant.
So I've learned my system partition is different. I can look into that further I'm pretty good on samsung on messing with stock images and adjusting them.
Bootloader unlock is trivial on GPE, fastboot oem unlock.
I flashed twrp and rooted.
Last thing is s-off. Is s-off easier on GPE like bootloader unlock or would I still need firewater for it?
To the point of this thread, when an OTA comes out will that effect s-off? I imagine it'd remove root but I believe I can edit the image to retain root and flash with TWRP easy enough, I've done it on samsung and nexus devices enough.
Click to expand...
Click to collapse
It definitely shouldn't affect S-OFF, but as with any OTA with any device known to man, it will kill root. But since you have an unlocked bootloader, you can just reroot after the OTA flashes. :good:
Sent from my Z Ultra Google Play Edition using Tapatalk
PunishedSnake said:
How's the gpe radio compared to tmobiles?
Click to expand...
Click to collapse
I'm on wifi only right now. I ordered an isis sim so i'm waiting on that before moving my number from the nexus 5.
oldblue910 said:
It definitely shouldn't affect S-OFF, but as with any OTA with any device known to man, it will kill root. But since you have an unlocked bootloader, you can just reroot after the OTA flashes. :good:
Click to expand...
Click to collapse
and for s-off I still need firewater then... gpe doesn't make that any easier correct?
I really dont mind s-on currently, I have xposed, and modules running just fine. I just feel like I should do it, just in case.... I'll have more options in the future.
mrRobinson said:
I'm on wifi only right now. I ordered an isis sim so i'm waiting on that before moving my number from the nexus 5.
and for s-off I still need firewater then... gpe doesn't make that any easier correct?
I really dont mind s-on currently, I have xposed, and modules running just fine. I just feel like I should do it, just in case.... I'll have more options in the future.
Click to expand...
Click to collapse
Correct. The GPE only allows unlocking the bootloader. S-OFF is not available through officially sanctioned channels.
Sent from my Z Ultra Google Play Edition using Tapatalk
4.4.3 is rolling out. If anyone gets the OTA, please pull the filename and post it here!
filename is 690c696fc4ad38107536cc3a32f262f5d18d8073.OTA_M8_UL_K44_STOCK_UI_MR_Google_WWE_2.10.1700.4-1.16.1700.16_release_378258
graffixnyc said:
filename is 690c696fc4ad38107536cc3a32f262f5d18d8073.OTA_M8_UL_K44_STOCK_UI_MR_Google_WWE_2.10.1700.4-1.16.1700.16_release_378258
Click to expand...
Click to collapse
Thank you!
Sent from my Nexus 7 using Tapatalk
Hi Everyone, my Developers Edition M9 just got updated to 5.1 version 2.8.617.4.
Happy 4th.
Chingonazo
Yep. I believe this is the OTA URL for the dev edition (from 1.32.617.30 to 2.8.617.4) if anyone wants it.
It looks like the firmware isn't up on HTC's download page yet, but I think the Sprint one is.
Mine too
Initial thoughts after just a few minutes of playing with the camera and a few other things, camera launches much faster and pictures look more detailed and consistent. Phone feels smoother and more responsive when double tapping to wake it. If people continue complaining about the M9 after this update then there is no pleasing them. This is why I keep coming back to HTC. I will not fall for the gimmicks that other brands are selling. I will report back if I find anything else of significance.
Chingonazo
I don't have the developer edition of the M9, but I do have the Unlocked edition from HTC and I can confirm I just got the same update about 30 minutes ago.
Mine will not finish update . It keeps aborting. Can someone please be kind enough to make an ruu zip ? The exe way don't work on my PC. I have to do the sd card/0PJAIMG.zip way. Thanks
Edit
Just seen this post
Charwinger21 said:
Yep. I believe this is the OTA URL for the dev edition (from 1.32.617.30 to 2.8.617.4) if anyone wants it.
It looks like the firmware isn't up on HTC's download page yet, but I think the Sprint one is.
Click to expand...
Click to collapse
Edit #2
Going to need full ruu zip when available
BR7fan, be patient, it takes a long time for the update to install, I almost made the mistake to stop it.
Chingonazo
Chingonazo said:
Initial thoughts after just a few minutes of playing with the camera and a few other things, camera launches much faster and pictures look more detailed and consistent. Phone feels smoother and more responsive when double tapping to wake it. If people continue complaining about the M9 after this update then there is no pleasing them. This is why I keep coming back to HTC. I will not fall for the gimmicks that other brands are selling. I will report back if I find anything else of significance.
Chingonazo
Click to expand...
Click to collapse
That is the answer we need ? HTC is improving & listening ?
Sent from my HTC One M9 using Tapatalk
BR7fan said:
Mine will not finish update . It keeps aborting. Can someone please be kind enough to make an ruu zip ? The exe way don't work on my PC. I have to do the sd card/0PJAIMG.zip way. Thanks
Edit
Just seen this post
Edit #2
Going to need full ruu zip when available
Click to expand...
Click to collapse
All my Developer Edition files are here: Including the 2.8.617.4 system_image.emmc.win, Stock Recovery and Firmware.
https://www.androidfilehost.com/?w=files&flid=28824
Sent from my HTC One M9 using Tapatalk
Dang, still no update for the International .401 version willing to get here already
clsA said:
All my Developer Edition files are here
https://www.androidfilehost.com/?w=files&flid=28824
Sent from my HTC One M9 using Tapatalk
Click to expand...
Click to collapse
Thank u so much . I got all my updates
Will sunshine s-off work on 5.1?
biswasd said:
Will sunshine s-off work on 5.1?
Click to expand...
Click to collapse
Why don't you try it and let us know
Sent from my HTC One M9 using Tapatalk
I want to turn my M9 Int.S-OFF Device to Dev.Edition ? Do I have to change my MID to 0PJA11000 or is it only enaugh to change CID ?
Anyone know why there're two different version number? One as 2.6.651.11 and another is 2.8.617.4? Since I'm DevEd phone, don't know why I got 2.6.651.11 update notification.
frankcck said:
Anyone know why there're two different version number? One as 2.6.651.11 and another is 2.8.617.4? Since I'm DevEd phone, don't know why I got 2.6.651.11 update notification.
Click to expand...
Click to collapse
Sprint version maybe?
Andrewbud said:
Sprint version maybe?
Click to expand...
Click to collapse
Yep, that's Sprint version. But my phone is DevEd, shouldn't I be supposed to get DevEd version?
it's really confusing me now.
EDIT: Well, after updated, my software number shows 2.8.617.4..... NVM
I have a Sim unlocked m9
Bootloader is unlocked unlocked
I have twrp on it.
What do I have to do next to make it a Dev device?
BriniaSona said:
I have a Sim unlocked m9
Bootloader is unlocked unlocked
I have twrp on it.
What do I have to do next to make it a Dev device?
Click to expand...
Click to collapse
The answer is here. Flash the RUU from the OP, then the one from this post. Be sure to use ADB to flash the OP RUU. The Dev Edition one can be run on a windows machine as an .exc.
After upgrading I cannot send MMS anymore. Did not have that problem when I was on Maximus 5.01. Anyone having mms sending issues?
Sent from my HTC One M9 using XDA Free mobile app
On Google developer sight. MOB30I. Link below.
https://dl.google.com/dl/android/aosp/shamu-mob30i-factory-21357b09.tgz
Edit: MOB30I includes new bootloader.
Edit 2: Two new images posted today. MMB30G also. Not a clue as to why...
Looks like they also posted MMB30G. Any idea in the difference between the two?
Encryptable boot/kernel IMG for MOB30I:
https://www.androidfilehost.com/?fid=24530981327208519
MrBrady said:
Looks like they also posted MMB30G. Any idea in the difference between the two?
Click to expand...
Click to collapse
MOB30G was posted about April 10th. MOB30I was posted today and is newer, includes May security updates and new bootloader.
Edit: MOD30D was posted mid April. Above information is incorrect.
cam30era said:
MOB30G was posted about April 10th. MOB30I was posted today and is newer, includes May security updates and new bootloader.
Click to expand...
Click to collapse
The one posted on mid april was MOB30D. I'm pretty sure two new ones were posted today.
blanco2701 said:
The one posted on mid april was MOB30D. I'm pretty sure two new ones were posted today.
Click to expand...
Click to collapse
You are correct. Two updates posted today. I do not know why. With no info posted by Google, they are confusing us.....
cam30era said:
You are correct. Two updates posted today. I do not know why. With no info posted by Google, they are confusing us.....
Click to expand...
Click to collapse
Same radio of 05.34 as Preview 2 of N.
cam30era said:
You are correct. Two updates posted today. I do not know why. With no info posted by Google, they are confusing us.....
Click to expand...
Click to collapse
Flashed the MOB30I image, hope i made the correct choice
gee2012 said:
Flashed the MOB30I image, hope i made the correct choice
Click to expand...
Click to collapse
I did the same thing. Honestly, I do not understand why Google posts two images, simultaneously, and gives us no information on what's different. At least last year, with all of the confusion on the multiple images, they posted a little bit of direction....
gee2012 said:
Flashed the MOB30I image, hope i made the correct choice
Click to expand...
Click to collapse
Please let us know if there is something new, or just the security update.
gothy.gothy said:
Please let us know if there is something new, or just the security update.
Click to expand...
Click to collapse
Only the security update + new bootloader.
gothy.gothy said:
Please let us know if there is something new, or just the security update.
Click to expand...
Click to collapse
New bootloader , boot.img and radio (same as the 2nd N preview) it seems if i`am correct. From what i read here and there one of the images is supposedly a T-Mobile version.
gee2012 said:
New bootloader , boot.img and radio (same as the 2nd N preview) it seems if i`am correct.
Click to expand...
Click to collapse
The "new" radio was included previously in MOD30D, about April 11th. No need to flash it for anyone running that version.
cam30era said:
The "new" radio was included previously in MOD30D, about April 11th. No need to flash it for anyone running that version.
Click to expand...
Click to collapse
Aah oke, i stand corrected
Yup, It's my understanding that MOB contains a new radio vs MMB. They will be updating MMB until all the carriers get around to approving the new radio. Because I have an at&t sim dropped in my nexus 6, it will most likely OTA to MMB30G(with May security updates). This knowing at&t never gets in a hurry when it comes to approvals.
phoenixms said:
Yup, It's my understanding that MOB contains a new radio vs MMB. They will be updating MMB until all the carriers get around to approving the new radio. Because I have an at&t sim dropped in my nexus 6, it will most likely OTA to MMB30G(with May security updates). This knowing at&t never gets in a hurry when it comes to approvals.
Click to expand...
Click to collapse
Good info. I haven't heard that previously. For the record, I just flashed the MOB30I on my VZW Nexus 6 and it's working fine. Did the whole fastboot flash-all deal.
will wait for the official changelogs.. hopefully
reyscott1968 said:
will wait for the official changelogs.. hopefully
Click to expand...
Click to collapse
There's this: http://source.android.com/security/bulletin/2016-05-01.html
https://source.android.com/source/build-numbers.html
MOB30D android-6.0.1_r30 Marshmallow Nexus 5, Nexus 6, Nexus 7 (flo/deb), Nexus 9 (volantis/volantisg), Nexus Player, and Android One
MMB29X android-6.0.1_r20 Marshmallow Nexus 5, Nexus 6, Nexus 7 (deb), Nexus 9 (volantisg)
its probably the same thing. consolidation.
So MOBxxx is newer than MMBxxx, because of r30 against r20?
But, why there are two updates, and not only MOBxxx?
Regards.
Sent from Nexus 6