Database Develop

[HELP] How to put US Donut 1.6 on UK Cupcake 1.5 T-Mobile G1?

Hi, currently my T-Mobile G1 is running the official UK cupcake 1.5 (CRC37) firmware.
How can I safely put the official US 1.6 Donut (DRC83) firmware on my phone without messing things up.
I have the HardSPL flashed already as I used to have my phone rooted and running cyanogenmod.

well you can flash emonthers 1.6 rom. its basically stock donut for root users

Do you know how I would go about loading the official 1.6 US firmware though? Or is it even possible on a UK model?

Even if it did work, I'm not sure if thats such a good idea to update to the official US version.
I live in Australia and i imported my g1 from the US only to realise that i needed to flash it over to the UK version because of a nasty little thing called "Myfaves" which sent international texts to the US periodically under-the-hood with no way of disabling it.
The UK firmware doesn't have "myfaves" hence the reason why i flashed over to it. It might not be a problem (money wise) if you're on t-mobile but its probably worth waiting 5 more days when the UK version gets released on the 19th.
From what i hear, its not really worth all the screwing about to get it early.

Thanks for your reply. I don't want it sending international texts.

lubu99 said:
probably worth waiting 5 more days when the UK version gets released on the 19th.
Click to expand...
Click to collapse
There's been no announcement of when the UK G1 1.6 update is coming out. The 19th is the date when the HTC Magic on Vodafone UK starts getting its OTA updates.

Does flash 10.1 work good rooted with froyo 2.2?

On the fence here guys. Trying to decide if its worth waiting for the OTA 2.2 or biting the bullet, rooting and testing a cooked rom. Any performance issues or problems with the current roms? How is flash 10.1 working? Like the idea of having full control of the phone and not too concerned with warranty issues. Want to be sure to select the right rom without too many glitches. On AT&T network.

Big_O said:
On the fence here guys. Trying to decide if its worth waiting for the OTA 2.2 or biting the bullet, rooting and testing a cooked rom. Any performance issues or problems with the current roms? How is flash 10.1 working? Like the idea of having full control of the phone and not too concerned with warranty issues. Want to be sure to select the right rom without too many glitches. On AT&T network.
Click to expand...
Click to collapse
you dont have to be rooted to be using 2.2, and the performance of Flash on the Nexus One is fantastic, especially with all the recent updates.

I'm on At&t and thought only tmobile didn't have to root, but At&t did. Anyone confirm this?

Big_O said:
I'm on At&t and thought only tmobile didn't have to root, but At&t did. Anyone confirm this?
Click to expand...
Click to collapse
I thought there was a way to get At&T version on froyo without root? Anyone can confirm?

Official FROYO announced by SFR

Hi,
I found this :
http://www.frandroid.com/51647/sfr-presentation-du-calendrier-des-mises-a-jour-des-androphones/
Basicly, it's a listing of every phones SFR (french vodafone) is going to update with dates.
Here's the thing :
Thanks FrAndroid for the news.
PS: it's written "(est.)" which is the short for estimation, just to be clear.
PS2: that means a stable froyo SenseUI rom in a near future

Thanks Sympnotic, but i'm more excited about gingerbread!

Thanks Sympnotic. Some light on Froyo tunnel for Wildfire !

http://www.frandroid.com/51788/htc-...ndroid-froyo-2-2-est-en-cours-de-deploiement/
SFR released the legend 2.2 OTA update, it was planned for the 17th december, we're only the 9.
I'll do *#*#checkin#*#* to see if something appears for our wildfires
edit: I might have been too excited but Legend had their updates one month ago, didn't read 17/11 but 17/12 as I don't see the point to include an already released update on a Roadmap.

Vodafone (NL) updated their Legends already 15/11, the unbranded phones are updating now. So 17/11 is the right date.
But that means that vodafone will give the update in about 4 days, and HTC maybe in less than 2 weeks?
Because they're busy with Legend right now.
I hope so

fifarunnerr said:
Vodafone (NL) updated their Legends already 15/11, the unbranded phones are updating now. So 17/11 is the right date.
But that means that vodafone will give the update in about 4 days, and HTC maybe in less than 2 weeks?
Because they're busy with Legend right now.
I hope so
Click to expand...
Click to collapse
Yep, I know but thanks for pointing it out here.
Well, if SFR release the update before HTC, it would be easy to grab just the SFR rom, purge it from their bloatwares (sfr wifi / tv / account - apps) and add more languages to make it a WWE rom.

The Wildfire from a friend of mine has recieved an update today.
unbranded htc in germany

OMG only 4 days, im so horny ;]

lazaj007 said:
OMG only 4 days, im so horny ;]
Click to expand...
Click to collapse
Yeah i'm horny too O.O xD

How do the updates work? Does your phone do it automatically? are you notified first?
I'm on 3 in the UK
Edit: But it's a Vodafone Wildfire which I had unlocked (if that makes a difference).

Mtl Evan said:
How do the updates work? Does your phone do it automatically? are you notified first?
I'm on 3 in the UK
Click to expand...
Click to collapse
3 UK won't get it for a bit yet. I have spoken to 3 on the phone and they say they will be rolling out the 2.2 update but have no idea of how long it will be.

hmm so lets say im using the wildpuzzle rom 7.3.1 right now. how would i update it to 2.2 if it came out?? can someone please give me a detailed instruction?

gryphynwing said:
hmm so lets say im using the wildpuzzle rom 7.3.1 right now. how would i update it to 2.2 if it came out?? can someone please give me a detailed instruction?
Click to expand...
Click to collapse
You can either reflash your phone with a RUU from Shipped roms (must have HTC Synch installed to use RUU's) or you could wait for Danne_jo to release a UK version of Froyo (as we all know he'll be the first(he he))

This is a lie
Today was 15

yuanvn said:
Today was 15
Click to expand...
Click to collapse
It's est. -.-

tuktukscotty said:
You can either reflash your phone with a RUU from Shipped roms (must have HTC Synch installed to use RUU's) or you could wait for Danne_jo to release a UK version of Froyo (as we all know he'll be the first(he he))
Click to expand...
Click to collapse
I tried to use
RUU_Buzz_HTC_WWE_1.37.405.1_Radio_13.53.55.24H_3.35.19.25_release_151892_signed.exe
Which I believe is a generic rom, on my phone which is H3G UK and I keep getting Customer ID Error
I can't use
RUU_Buzz_H3G_UK_1.16.771.2_Radio_13.45.55.24_3.35.15.31
_release_131501_signed.exe
as my phone has higher version 1.26.xxxxxxx
Is there anyway to bypass this error?

foxy6800 said:
I tried to use
RUU_Buzz_HTC_WWE_1.37.405.1_Radio_13.53.55.24H_3.35.19.25_release_151892_signed.exe
Which I believe is a generic rom, on my phone which is H3G UK and I keep getting Customer ID Error
I can't use
RUU_Buzz_H3G_UK_1.16.771.2_Radio_13.45.55.24_3.35.15.31
_release_131501_signed.exe
as my phone has higher version 1.26.xxxxxxx
Is there anyway to bypass this error?
Click to expand...
Click to collapse
U need to make goldcard
Sent from my HTC Wildfire using XDA App

you cant put lower software over higher even with goldcard. you need downgrade you system to lower or same as you want. and it is wrong topic

thanks for the info, though... I believe they are releasing 2.2.1 for wildfire? Since modaco and cyangen have somehow picked up a leaked froyo for wildfire.

krazykat said:
Since modaco and cyangen have somehow picked up a leaked froyo for wildfire.
Click to expand...
Click to collapse
Not cyanogen, they work on raw code released by Google. Hence cm is way different from other repackaged roms.

[Q] RE 2.3.3: AT&T Nexus One Users

Any AT&T Nexus One users successfully update with these files popping up? Is this like Froyo, where we have to wait for our version?

Yes, I just manually updated to Gingerbread. I can confirm that it works on the AT&T N1!

I can also confirm that it worked for me on my AT&T band Nexus One. I was complete stock 2.2.2 but needed to update my HBOOT to the newest one before it would accept the Gingerbread ROM

kwonger said:
Is this like Froyo, where we have to wait for our version?
Click to expand...
Click to collapse
LOLWHUT?
All N1's run the same rom. Stop it.

GldRush98 said:
LOLWHUT?
All N1's run the same rom. Stop it.
Click to expand...
Click to collapse
That wasn't always true... Anyone remember EPE54B? Good times...

GldRush98 said:
LOLWHUT?
All N1's run the same rom. Stop it.
Click to expand...
Click to collapse
I think the OP is referring to when Froyo was first released, it was available on the T-Mobile version first and us AT&T folks had to wait for some time before we got our Froyo version.
Sometime after that all N1's ended up on the same Froyo version and now we have the same GB version.

I have a 850 Nexus One (that works with AT&T) and i received the notification here in Mexico, so yes, Gingerbread working!!!

iboj007 said:
I think the OP is referring to when Froyo was first released, it was available on the T-Mobile version first and us AT&T folks had to wait for some time before we got our Froyo version.
Sometime after that all N1's ended up on the same Froyo version and now we have the same GB version.
Click to expand...
Click to collapse
Bingo
I guess I'll try updating HBOOT. Hopefully that's why mine isn't working.
Thanks all.

GldRush98 said:
LOLWHUT?
All N1's run the same rom. Stop it.
Click to expand...
Click to collapse
Not true. Ask any Vodafone user.

I'd rephrase it - "All N1s can run the same ROMs, starting with FRG33 - that includes both frequency variants and screen variants".

T-mobil MRA68K to MRA68X

I have a Nexus 6 bought directly from Motorola but with a T-mobil sim from my
last phone. I'm running the MRA68K factory image of 6.0., and have never been
offered an OTA update.
Let me tell you what I THINK I know.
Although MRA68K does include the T-mobile band 12 and wifi calling feature,
for some reason T-mobil was not happy with it due to some bug revealed
in testing. MRA68X is the release they are happy with, and is what T-mobil
users running 5.1.1 are getting OTA. This OTA is not usable for phones running
any of the 6.0 release. There currently is no factory image for MRA68X.
Here is what I don't know:
- Will MRA68X be eventually released as a factory image.? Usually that comes
before not after the OTA. If not it would seem the need to flash a 5.1.1 image
to be able to take the MRA68X OTA.
- Is the T-mobil specific release a one time thing, or will there be a sequence of
T-mobil specific releases as in 5.X?
- I presume that when the phone checks for an update it bases it on the carrier's
SIM. Just curious, is it Google downloading the update but subject to the carrier's
instructions?

kmandel said:
I have a Nexus 6 bought directly from Motorola but with a T-mobil sim from my
last phone. I'm running the MRA68K factory image of 6.0., and have never been
offered an OTA update.
Let me tell you what I THINK I know.
Although MRA68K does include the T-mobile band 12 and wifi calling feature,
for some reason T-mobil was not happy with it due to some bug revealed
in testing. MRA68X is the release they are happy with, and is what T-mobil
users running 5.1.1 are getting OTA. This OTA is not usable for phones running
any of the 6.0 release. There currently is no factory image for MRA68X.
Here is what I don't know:
- Will MRA68X be eventually released as a factory image.? Usually that comes
before not after the OTA. If not it would seem the need to flash a 5.1.1 image
to be able to take the MRA68X OTA.
- Is the T-mobil specific release a one time thing, or will there be a sequence of
T-mobil specific releases as in 5.X?
- I presume that when the phone checks for an update it bases it on the carrier's
SIM. Just curious, is it Google downloading the update but subject to the carrier's
instructions?
Click to expand...
Click to collapse
I have run all the MRA builds (K, N, R) on T-Mobile and they all support and have fully functioning WiFi calling, Band 12 support, and VoLTE. Not sure what's specific about X but I decided to switch to it just because it's "official".
Sent from my Nexus 6 using Tapatalk

nnorton44 said:
I have run all the MRA builds (K, N, R) on T-Mobile and they all support and have fully functioning WiFi calling, Band 12 support, and VoLTE. Not sure what's specific about X but I decided to switch to it just because it's "official".
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
How did you switch? Did you flash a 5.1.1 factory image and then take the OTA?

kmandel said:
How did you switch? Did you flash a 5.1.1 factory image and then take the OTA?
Click to expand...
Click to collapse
For X I flashed the factory ProFi 5.1.1 then sideloaded the 48I to 58X OTA.
T-Mobile and ProFi will both use X.
Sent from my Nexus 6 using Tapatalk

I hope there's a factory release. Please post here if anyone gets it

kmandel said:
I have a Nexus 6 bought directly from Motorola but with a T-mobil sim from my
last phone. I'm running the MRA68K factory image of 6.0., and have never been
offered an OTA update.
Let me tell you what I THINK I know.
Although MRA68K does include the T-mobile band 12 and wifi calling feature,
for some reason T-mobil was not happy with it due to some bug revealed
in testing. MRA68X is the release they are happy with, and is what T-mobil
users running 5.1.1 are getting OTA. This OTA is not usable for phones running
any of the 6.0 release. There currently is no factory image for MRA68X.
Here is what I don't know:
- Will MRA68X be eventually released as a factory image.? Usually that comes
before not after the OTA. If not it would seem the need to flash a 5.1.1 image
to be able to take the MRA68X OTA.
- Is the T-mobil specific release a one time thing, or will there be a sequence of
T-mobil specific releases as in 5.X?
- I presume that when the phone checks for an update it bases it on the carrier's
SIM. Just curious, is it Google downloading the update but subject to the carrier's
instructions?
Click to expand...
Click to collapse
Someone posted about this on the Android Central comments section: http://www.androidpolice.com/2015/1...etting-an-over-the-air-update-to-marshmallow/
Looks like if you are on K you will get the X updated OTA

blazinazn said:
Someone posted about this on the Android Central comments section: http://www.androidpolice.com/2015/1...etting-an-over-the-air-update-to-marshmallow/
Looks like if you are on K you will get the X updated OTA
Click to expand...
Click to collapse
According to the T-mobile document
https://support.t-mobile.com/docs/DOC-18109
It's only the L* releases that can be updated with the OTA.

kmandel said:
According to the T-mobile document
https://support.t-mobile.com/docs/DOC-18109
It's only the L* releases that can be updated with the OTA.
Click to expand...
Click to collapse
I don't see where it says *only* L releases get the update but it may just be a matter of semantics.
"To be able to update to the current software version, the below requirements must be met:"
^^^ I take this to mean that you must have at least L to get the update. If you are on M already then you still meet that requirement. That's just my thoughts though. Dez is always in the know and that's what he said. Guess we'll just have to wait and see.

i am completely unable to install mra58x no matter how i try to sideload the update from 5.1.1

Tmobile goes back to MRA58K
It confused me.
https://i.imgur.com/vQYNKiL.jpg

I got the ota today, from 28m
Sent from my Nexus 6 using XDA Free mobile app

joshtb86 said:
i am completely unable to install mra58x no matter how i try to sideload the update from 5.1.1
Click to expand...
Click to collapse
I noticed that your signature says "Nexus 6 rooted". If that is in fact the case, you will not be able to install any OTA. Neither via sideloading nor "over the air". The installer looks at the system file, and if there is ANY change from stock (including being rooted), it will abort the install. I've had it fail, even with a couple of apps frozen.

It looks like the document
https://support.t-mobile.com/docs/DOC-18109
has been updated. It now list MRA68K as eligible for the OTA to MRA68X. Earlier
it just listed the L* releases.

cam30era said:
I noticed that your signature says "Nexus 6 rooted". If that is in fact the case, you will not be able to install any OTA. Neither via sideloading nor "over the air". The installer looks at the system file, and if there is ANY change from stock (including being rooted), it will abort the install. I've had it fail, even with a couple of apps frozen.
Click to expand...
Click to collapse
yeah tried on a clean flash without root, still not luck
i installed mra58k clean rom from the andriod dev page until someone makes an X rom

Wow

And for those with MRA58N currently, there was a hint that TMO would OTA push MRA58X as well.

I am starting to think that was Des speaking before he had the details
Sent from my Nexus 6 using Tapatalk

Dougshell said:
I am starting to think that was Des speaking before he had the details
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Check their support web site
Sent from my Nexus 6 using Tapatalk

I see they added it. Well again, sitting here with a nexus device, waiting.
Sent from my Nexus 6 using Tapatalk

BigDig said:
Check their support web site
Click to expand...
Click to collapse
TMO's update site is questionable in and of itself.