Database Users

Looking for T-Mobile offical 1.6 update for mytouch

Hello I just received a un-rooted mytouch but it is stuck on 1.5 even though the previous user has been using it on the network for the past few months. Is there somewhere I can download the latest official 1.6 update to flash onto this device?

just one click root it and flash a donut rom. It will only take like 15 minutes, and with everything else that you will be able to do with it, it would definitely be worth it.

Manually install 1.6 update on mytouch:
http://theandroidsite.com/2009/10/0...-1-6-update-yet-heres-how-to-manually-update/

tazz9690 said:
just one click root it and flash a donut rom. It will only take like 15 minutes, and with everything else that you will be able to do with it, it would definitely be worth it.
Click to expand...
Click to collapse
I have my G1 rooted
auvi said:
Manually install 1.6 update on mytouch:
http://theandroidsite.com/2009/10/0...-1-6-update-yet-heres-how-to-manually-update/
Click to expand...
Click to collapse
I tried these instructions but get an error when attempting to flash. Also the ROM he has linked is only 20mb?

is that link the REAL official t-Mobile Donut 1.6 update?? I dont understand why there are not numerous links and sources to the update, I need the real update cause i am test driving the phone, I wanna root it and try it thaqt way, but eventually in a few days im gonna have to give it back to my buddy, he already was buggin about my rooting it, i mean i guess if decide to buy it thats one thing, but i would like to bring it back to Official 1.6 status if not
Its weird usually when anykind of firmware or operating system is releaseed everyone has tons of dwnload links and various sources to get it, but i mean its weird i can only find that one link thats posted above?? I see there is a stock build here in XDA, but says a few tweaks but generally stock, im curious if I need to have the phone rooted to even install that ROM?? this ROM here http://forum.xda-developers.com/showthread.php?t=549755

go to the t-mobile forums there is a guide for this, here is a link DIRECTLY TO THE GUIDE FOR MANUALLY UPDATING TO 1.6
http://forums.t-mobile.com/t5/Opera...o-modify-your-Android-phone/m-p/200730#M17823

Rooting the New Update for Leaked 2.1

Since the 2.1 new update was released, I figured it would be a higher version number than our leaked 2.1. That means we could hboot it to our phones to update.
But wait, could some developer root this update (maybe in a similar to the way they rooted 1.5 to 2.1 root) so the leaked 2.1 people could hboot to this new update for 2.1 except it would be rooted.
Sorry if that was confusing.
Here's where the update was found:
androidforums.com/htc-droid-eris/55898-you-dont-need-root-new-leak.html

As far as I understand it, the reason that 2.1 OTA can be installed for users running leaked 2.1 is because it has a higher subversion number and it is SIGNED. That is the tricky part. Because your SPL / HBoot is S-ON, meaning that it will only install signed zips, you are still unable to install a rooted 2.1. The reason that the exploit worked on 1.5 is because the PB00IMG.zip IS a signed package, but the versioning only puts it ahead of 1.5, not Leaked 2.1 or OTA 2.1. Once the PB00IMG.zip is installed, it turns S-OFF so that unsigned (e.g. rooted) packages. From what I have read in other posts, devs are moving toward trying to find exploits in the new 2.1 OTA for users who have already upgraded without root. I would personally recommend doing the 2.1 OTA and hanging tight for the next exploit.

Thank you man. So, would it not be possible to turn S-OFF in this new update? I understand that would require going in and tampering with the files, which could break the signature on the package, possibly?

Precisely, if you change one bit of a signed file, the signature changes completely. As I understand it, the PB00IMG.zip file that is used to root 1.5 phones was "stumbled upon" already signed by HTC. For any future rooting for people with 2.1, this file is unusable because the versioning of this convenient package is older than what leakers and official 2.1 adopters have. It is impossible to modify the 2.1 update without breaking the sig. We now have to hope that devs can find an exploit or broken code in the new 2.1 update that allows for rooting by another means.
If you are desperate, feel free to try to socially engineer Verizon. That has met with considerable success from some other early adopters. If not, play the waiting game. In the mean time, feel free to upgrade to the OTA 2.1 leak. It fixes some things like Google relogin.

shickfaced said:
Precisely, if you change one bit of a signed file, the signature changes completely. As I understand it, the PB00IMG.zip file that is used to root 1.5 phones was "stumbled upon" already signed by HTC. For any future rooting for people with 2.1, this file is unusable because the versioning of this convenient package is older than what leakers and official 2.1 adopters have. It is impossible to modify the 2.1 update without breaking the sig. We now have to hope that devs can find an exploit or broken code in the new 2.1 update that allows for rooting by another means.
If you are desperate, feel free to try to socially engineer Verizon. That has met with considerable success from some other early adopters. If not, play the waiting game. In the mean time, feel free to upgrade to the OTA 2.1 leak. It fixes some things like Google relogin.
Click to expand...
Click to collapse
So, I installed the first 2.1 leak. Can I install this new one that just came out in the last couple days? Sorry, guess I'm not seeing the answer here

If we were able to find a way to modify the update to include root with a valid signature, we would also be able to modify the version number to a higher number than the current 2.1 leak. I'm pretty sure upgrading to the "official" 2.1 won't hurt our chances of finding root, it'll just make the wait less buggy
jearl75:
Yeah, you can install the new leak over the old one, no worries.

so should us people on the first 2.1 leak upgrade to the newest one or stay on the first one??

theboo7 said:
so should us people on the first 2.1 leak upgrade to the newest one or stay on the first one??
Click to expand...
Click to collapse
I reckon that depends on if you're experiencing the Google login bug or not. My wife's Eris with the first leaked 2.1 is not. And if you are experiencing that bug, which is more hassle...logging into Google repeatedly, or rebuilding your phone (apps, contacts, etc) from scratch??

Dangerous Dave said:
I reckon that depends on if you're experiencing the Google login bug or not. My wife's Eris with the first leaked 2.1 is not. And if you are experiencing that bug, which is more hassle...logging into Google repeatedly, or rebuilding your phone (apps, contacts, etc) from scratch??
Click to expand...
Click to collapse
its not that bad since i rarely restart my phone, i guess my real question would be would it make it longer until i get root? or are devs trying to root the NEW 2.1 instead of the old 2.1

I apologize if this gets old, but I am trying to be cautious so I don't brick my phone...
I downloaded the following leaked 2.1 version a few weeks ago, and have this installed:
Baseband version: 2.40.00.01.22
Kernel version: 2.6.29-5898f66b / [email protected] #1
Build number: 2.19.605.1 CL12345 test-keys
Software number: 2.19.605.1
I have a problem installing the new version of Google Maps. Phone dial can be sluggish and/or unresponsive at times, but it is manageable. Overall, the installation of the leaked ROM went fine, and I feel like I am pushing my luck if I try to download the latest ROM. Does anyone know if the latest release addresses the issues above? I am not experiencing any of the login issues to Gmail that others are experiencing.
My question is this: Should I just leave well enough alone and wait for the OTA at this point?
Thanks for any suggestions.

mdeavers said:
I apologize if this gets old, but I am trying to be cautious so I don't brick my phone...
I downloaded the following leaked 2.1 version a few weeks ago, and have this installed:
Baseband version: 2.40.00.01.22
Kernel version: 2.6.29-5898f66b / [email protected] #1
Build number: 2.19.605.1 CL12345 test-keys
Software number: 2.19.605.1
I have a problem installing the new version of Google Maps. Phone dial can be sluggish and/or unresponsive at times, but it is manageable. Overall, the installation of the leaked ROM went fine, and I feel like I am pushing my luck if I try to download the latest ROM. Does anyone know if the latest release addresses the issues above? I am not experiencing any of the login issues to Gmail that others are experiencing.
My question is this: Should I just leave well enough alone and wait for the OTA at this point?
Thanks for any suggestions.
Click to expand...
Click to collapse
I Know that when I installed the new Leak, the dialer lag was MUCH improved, as was the phone signal and general stability, Gmail doesn't make you log back in every reboot, and on my phone my "get more HTC widgets" link is fixed. But I heard on others phones it wasnt. It Does wipe all your apps even though its 2.1 -> 2.1. But Just like last time the SD card is untouched.
The installation process is exactly the same. I recommend it.
EDIT- Actually I just noticed the build you have installed is test keys signed and to my knowledge only the root rom was test key signed. This being the case if you want to keep root I would flash a custom cooked ROM... Since your lucky enough to have the chance to do so... Sigh..

Wait, test keys signed means what exactly? My Eris reads that but I only installed the two leaks AFAIK?
Does it just mean signed by HTC?

thawkth said:
Wait, test keys signed means what exactly? My Eris reads that but I only installed the two leaks AFAIK?
Does it just mean signed by HTC?
Click to expand...
Click to collapse
So you only installed the 2.1 non-root Leaks??? I may be mistaken, but both times I flashed the leaks, 2.1a +2.1b, both had builds signed with release keys... I was under the impression that only the 2.1 leak+root was signed with test keys.
Shed some light developers?

Whitepaint said:
So you only installed the 2.1 non-root Leaks??? I may be mistaken, but both times I flashed the leaks, 2.1a +2.1b, both had builds signed with release keys... I was under the impression that only the 2.1 leak+root was signed with test keys.
Shed some light developers?
Click to expand...
Click to collapse
You are exactly correct: Both of the leaked 2.1 roms have release keys, while the 1.5->2.1 root rom (and any rom based on that upgrade) will have test keys.

my girl has a rooted 2.1 with release keys. download Grdlocks ota rom

ahjee said:
my girl has a rooted 2.1 with release keys. download Grdlocks ota rom
Click to expand...
Click to collapse
Interesting...can you post the software version/info from your phone settings?

ahjee said:
my girl has a rooted 2.1 with release keys. download Grdlocks ota rom
Click to expand...
Click to collapse
Thats most probably because Grdlocks ota rom is based on just that, the 2.1 ota leak, not the 2.1+root rom. The Beauty of custom roms...

Sorry no one has been clean on this before:
The 2.1 leak was leaked from HTC by riverrunner. We actually don't care about the hboot version, radio version is the main thing updaters look at (we've found that out since root).
The 2.1 update that had root built in was also an HTC leak. It contained SU. That was the difference. We didn't do ANYTHING to get root. ABSOLUTELY NOTHING. It was leaked by someone at HTC. Simple enough. So, we CANNOT redo this, becuas we did NOTHING.
Hope this clears it up. Thanks!

zifnab06 said:
Sorry no one has been clean on this before:
The 2.1 leak was leaked from HTC by riverrunner. We actually don't care about the hboot version, radio version is the main thing updaters look at (we've found that out since root).
The 2.1 update that had root built in was also an HTC leak. It contained SU. That was the difference. We didn't do ANYTHING to get root. ABSOLUTELY NOTHING. It was leaked by someone at HTC. Simple enough. So, we CANNOT redo this, becuas we did NOTHING.
Hope this clears it up. Thanks!
Click to expand...
Click to collapse
I'm glad this was finally publicly admitted. I got kind of tired of the devs going around pretending they actually did something besides getting lucky with a leak.

12134567890

Important: Do not update to 2.1 from htc!!!

Please listen up!
When the 2.1 is released;
Do not update your phone with the RUU from htc website or OTA because it will most likely lock up your bootloader and make you unable to downgrade, root and it will replace/delete you custom recovery boot menu and therefore UNABLE TO ROOT,DOWNGRADE AND FLASH ANY CUSTOM ROM!
I recommend waiting for a 2.1 based villain version or MODACO 4
YOU'VE BEEN WARNED; YOUR PHONE MAY BE "WRECKED"
if you goto modaco htc hero forum you'll find a similar thread with more information.
OFFICIAL SOURCE
www.villainrom.co.uk/viewtopic.php?f=9&t=28

Thanks for the informations dude!
so when modaco 4 will release? waiting for.....

Thanks Yeah i planned on waiting for a rooted 2.1 update-hero-generic-x.xx.xxx.xx-release-rooted rom for flashing with recovery.

where is this discussed??
Link please

Dan330 said:
where is this discussed??
Link please
Click to expand...
Click to collapse
OFFICIAL SOURCE!
www.villainrom.co.uk/viewtopic.php?f=9&t=28

Thanks for pointing out my little 'article' over on VillainROM.co.uk
As we approach the end of the week, and the point where something interesting might appear at any time, please make sure everyone knows not to flash an RUU.
To re-iterate what I said over there, if you get access to the official RUU in your country or from your provider, please let one of the admins or moderators on VillainROM.co.uk know (you can identify us with the red and green nametags, or by clicking 'the team' at the bottom of the home page. We will then provide you with temporary login details to FTP the file to our server, and the update will be re-released within hours (probably within minutes of uploading)
Cheers, and don't go RUU-ing

Please make it a stickie.

Hertus said:
Thanks for the informations dude!
so when modaco 4 will release? waiting for.....
Click to expand...
Click to collapse
I assume modaco 4 will be released shortly after the official 2.1 RUU, but it will always be well.. alpha and betas before the "real" modaco 4 is finished and we also have to wait until Teknologist releases his tweaked kernel to get the real modaco as we know from 3.2

Thank you!.... I was planning on installing the official one as soon as it is available under the assumption I could just flash a custom over the top of it once they had been tweaked.
You've saved me some heartache.
Assumption is definitely the mother of all f'ups.
Thanx again.

ddotpatel said:
Thank you!.... I was planning on installing the official one as soon as it is available under the assumption I could just flash a custom over the top of it once they had been tweaked.
You've saved me some heartache.
Assumption is definitely the mother of all f'ups.
Thanx again.
Click to expand...
Click to collapse
Glad someone's been saved... Perhaps we should get a viral tweet going I'll start one tonight if I remember...
Pass the message on, folks...
Tweeted via. my user below. Feel free to add me and RT to android users etc. Spread the word, and hopefully we won't even need to find a way to root the new update

hehe before i look at this post i was thinking "the official 2.1 must be out any time soon,should i flash it or wait for the customs..?"....question solved

So.. Even other downgrading (like GoldCards) methods wont work..?

How
I can solve this problem
Because it happen yo my
I was rooed my hero
on day i run .exe file for htc ruu
it work at first but un the end it but me error
What i can do
sorry i but my broke English

harsha_aithal said:
So.. Even other downgrading (like GoldCards) methods wont work..?
Click to expand...
Click to collapse
think about this: you are htc. you don't want people to root their phones. you get a major upgrade out there, and you know about the methods how to crack the security of the phone. would you fix them or not?

If somebody have SPL 1.76.2007 installed and wish to try official 2.1 form HTC you can do it in the following way:
1. Get rom.zip from 2.1 RRU
2. Unpack it on you hard disk
3. Make new archive HEROIMG.zip with following files from rom.zip:
- android-info.txt
- splash1_Hero_320x480.nb0
- boot.img
- radio.img
- system.img
- userdata.img
DO NOT INCLUDE recovery file (recovery.img) and SPL file (with name like hboot_7200A_1.76.0007_090804.nb0) into HEROIMG.zip.
4. Flash HEROIMG.zip
In this case you will able to root, downgrade or install custom rom.

FYI:
VillainROM will really come into life when we have the official 2.1 update.
But on topic - he's right. Remember those that used the official update last time and had to use the goldcard method to flash recovery?
We don't want that all over again.
Agreed: Sticky.

Al936 said:
4. Flash HEROIMG.zip
Click to expand...
Click to collapse
flash through recovery image? would that work?

kendong2 said:
flash through recovery image? would that work?
Click to expand...
Click to collapse
well surely you would have to sign it?

Making a ROM out of an RUU is a piece of piss
As soon as we have it, it's a battle of the upload speeds.
There will be a lot of ROMs out there, all based on the same build; too similar to differentiate.

Lennyuk said:
well surely you would have to sign it?
Click to expand...
Click to collapse
yes, but it is still lacking an update-script, and contains only .img files. from what i know that is not suitable for the recovery... it might work with the unlocked bootloader, that is correct, but for that you need to flash every partition with the corresponding image...

Okay, someone explain to me why people can't update to FroYo

If you've debranded, you can't upgrade...? Is that the issue?
I've read through the big thread and it doesn't really explain much to me

From what can be gathered so far:
The non-branded HTC Legend FroYo up date checks the phones CID to a list that HTC know are debranded. If the CID is not on that list of the update script, it fails the update. Vodafone and other carrier phones that have been de-branded still have the original CID. In my case, mines is something like VODAF001. This is not on the installer scripts list. Hence the update fails even if we have a debranded 2.1 ROM.
We cannot change, yet, the orginal HTC Update Script as the *.zip file has a signature that cannot be re-signed without knowing HTC's private key. Think of it as encryption - the files are visable, however, the phone checks the signature against what it should be for the contained files. If the files are changed (like changing the supported CID's) then the signature does not match and the phone fails to continue with the update.
There's no way way to change your phones CID or re-sign the FroYo installation rom to accept the diffierent CID's.
So far, we're stuck.

YoungPretender said:
There's no way way to change your phones CID or re-sign the FroYo installation rom to accept the diffierent CID's.
So far, we're stuck.
Click to expand...
Click to collapse
Very helpful information there m8 and granted there is no free way to change your phones CID but it is very possible do a quick search for riff box you can change the legend CID with that. Not much use to most people due to it costing £100. Maybe some devs would work on a software CID change, not even sure if it is possible with just software but you never know.
Or what about changin the file in the update to accept your CID then using a goldcard to flash it? Does a goldcard not let you flash unsigned zips?

So corrrect me if I am wrong, I have my Bell Legend Rooted with MCR I also have Rom Manager installed, so, If I edited the froyo update to include my cid, then flashed the rom with Rom Manager, that, as I understand things, should work, since we can flash unsigned roms with Clockwork. Or am I way off base?

bwilliams1 said:
So corrrect me if I am wrong, I have my Bell Legend Rooted with MCR I also have Rom Manager installed, so, If I edited the froyo update to include my cid, then flashed the rom with Rom Manager, that, as I understand things, should work, since we can flash unsigned roms with Clockwork. Or am I way off base?
Click to expand...
Click to collapse
Im not sure I dont even have a phone atm waiting on my legend to turn up but it sounds about right to me. That doesnt mean it will actually work tho best off waiting for someone with more experience with these thhings to post.

I bought a Vodafone Spain one, and have debranded it. I use a Cyanogen mod froyo. So i can't update to the official one ? If i put the 2.1 From Vodafone Spain, can't i update to the Vodafone Spain Official 2.2 ?

xnotte said:
I bought a Vodafone Spain one, and have debranded it. I use a Cyanogen mod froyo. So i can't update to the official one ? If i put the 2.1 From Vodafone Spain, can't i update to the Vodafone Spain Official 2.2 ?
Click to expand...
Click to collapse
From what I understand if you put the vodafone rom on you can update to vodafone 2.2 but people are having problems getting the wwe 2.2 on de branded handsets

I've got a single idea that I'm trying the now to get working.
Not going to post any details until I know wether it'll fail or work. Fingers and toes crossed through :O

YoungPretender said:
I've got a single idea that I'm trying the now to get working.
Not going to post any details until I know wether it'll fail or work. Fingers and toes crossed through :O
Click to expand...
Click to collapse
Good luck let us know how you get on.

FeaRThiS said:
Good luck let us know how you get on.
Click to expand...
Click to collapse
Not very well
I'm pretty new to all this anyway, but I thought my techie background would help playing catchup.
Basically, I found my CID of my phone. VODAF001.
Then I went through the official unbranded FroYo rom and replaced supported CID's in the installation script and the android.info text file in the frimware.zip folder with my CID. Resigned the package.
I then rooted my phone (took a few hours - never did it before, but it was a success) then attempted to install the modified and resigned package.
It verifies ok, but I get a Status 7 error. I think this was the same error I had when trying to install the FroYo update from the very start.
Not too happy, but I had to give it a go. Anyone have any other ideas at modifying the original rom file? At least I got the thing to verify after modding it onto a rooted rom. Maybe, just maybe we're 30% there.

YoungPretender said:
Not very well
I'm pretty new to all this anyway, but I thought my techie background would help playing catchup.
Basically, I found my CID of my phone. VODAF001.
Then I went through the official unbranded FroYo rom and replaced supported CID's in the installation script and the android.info text file in the frimware.zip folder with my CID. Resigned the package.
I then rooted my phone (took a few hours - never did it before, but it was a success) then attempted to install the modified and resigned package.
It verifies ok, but I get a Status 7 error. I think this was the same error I had when trying to install the FroYo update from the very start.
Not too happy, but I had to give it a go. Anyone have any other ideas at modifying the original rom file? At least I got the thing to verify after modding it onto a rooted rom. Maybe, just maybe we're 30% there.
Click to expand...
Click to collapse
At least you ruled out one possibility I think the best way would be to change the phones CID that way you would never have to worry about it again and all updates would work as if it was a sim free phone. I remeber a few years back there was a app for the original iphone that would allow you to change the imei (i know this is illegal in most places) the point is the CID needs the same level access. If we have enough access a dev could probably make an app or script to run to change the phones CID to one of a sim free phone. I have posted the question in the dev section no replys yet.

FeaRThiS said:
At least you ruled out one possibility I think the best way would be to change the phones CID that way you would never have to worry about it again and all updates would work as if it was a sim free phone. I remeber a few years back there was a app for the original iphone that would allow you to change the imei (i know this is illegal in most places) the point is the CID needs the same level access. If we have enough access a dev could probably make an app or script to run to change the phones CID to one of a sim free phone. I have posted the question in the dev section no replys yet.
Click to expand...
Click to collapse
Agreed. It would be the best solution.
I'm still looking at this script file. I reckon that re-writing the entire thing could also be a possibility - and probably quicker to a solution to the CID problem in the short term.

Trying again taking all the checks out at the begining of the script... see what happens, lol.

Well, different error. Status 4 - whatever that means...
It could be anything. My ROM version currently installed could be too old for the update as well (V.1.xxxx).
Anyway, it's twenty to two here, time for my bed I think...

YoungPretender said:
Trying again taking all the checks out at the begining of the script... see what happens, lol.
Click to expand...
Click to collapse
good luck im sure there is a way as with clockwork mod you can flash unsigned roms so just a case of trying as many ways as possible. As for the CID change im guessing that would be a lot of work and would take a long time but would prevent future problems with new updates ect ect.

Not sure why people are freaking out about this. So the Voda Phone one came out early.. I'm sure it's just a matter of days or weeks before the WWE is released. Just chill

skinnypupp said:
Not sure why people are freaking out about this. So the Voda Phone one came out early.. I'm sure it's just a matter of days or weeks before the WWE is released. Just chill
Click to expand...
Click to collapse
I think you are missing the point a legend that was locked to vodafone can not be updated to the wwe. the voda legend has a different cid which is stopping people who debranded there phones from getting the wwe 2.2 update.

skinnypupp said:
Not sure why people are freaking out about this. So the Voda Phone one came out early.. I'm sure it's just a matter of days or weeks before the WWE is released. Just chill
Click to expand...
Click to collapse
So you mean the official FroYo update for non-branded phones? it is! We know the Vodafone one is out.
The problem lie in people who have de-branded. They can't update to the non-branded FroYo that was released today.
(And Yes, I'm still up because I'm a persistant little bugger, lol)

YoungPretender said:
So you mean the official FroYo update for non-branded phones? it is! We know the Vodafone one is out.
The problem lie in people who have de-branded. They can't update to the non-branded FroYo that was released today.
(And Yes, I'm still up because I'm a persistant little bugger, lol)
Click to expand...
Click to collapse
haha still tryin post up everythin you try just so people dont have to try things we know dont work.

FeaRThiS said:
From what I understand if you put the vodafone rom on you can update to vodafone 2.2 but people are having problems getting the wwe 2.2 on de branded handsets
Click to expand...
Click to collapse
but if i put the vodafone rom back again, it's no longer debranded! right ?
So i can update to the Vodafone ROM 2.2 via OTA right ?

Froyo OTA for the 1.2 & Fender to start on 1/12/11

Looks like Froyo for 1.2 & Fender users is on it's way! As posted on the T-Mobile forums.
http://forums.t-mobile.com/t5/myTouch-3G/Ladies-and-Gentlemen-Froyo/m-p/505229/highlight/true#M63410

budney said:
Looks like Froyo for 1.2 & Fender users is on it's way! As posted on the T-Mobile forums.
http://forums.t-mobile.com/t5/myTouch-3G/Ladies-and-Gentlemen-Froyo/m-p/505229/highlight/true#M63410
Click to expand...
Click to collapse
Nice find! I'll sticky this for a couple weeks and we'll see where it goes from here.

Yes, hopefully we will get a proper version of the 2708 Radio for the 1.2

Cool, I'll be unrooting the wife's phone for this.

O.T.A. for My Touch 3g Fender/1.2
Okay this thread is for the My Touch 1.2/Fender OTA to be released 1/12/11. If you have any insight as to what we need to do to "catch" this update please post here. I know a lot of people are going to say the Magic OTA has already been released but this is a different phone that was not included in the first update and I'm sure the Magic forum Moderator knows this better than most. Does anyone know for sure if we can just be on the stock Fender ROM with root and still receive the OTA? Any information regarding this topic is welcome please post for the rest of us!
JeffakaJeff and I have custom build of this update for people who want root and the update go here.

fender/1.2 i the same as 32A?

Fender 32a
tass0s said:
fender/1.2 i the same as 32A?
Click to expand...
Click to collapse
They are not the same the Fender/1.2 is a 32a but they use the EBI0 kernel like the 32b Dream. From what I have seen the 32a Magic use the EBI1 kernel (correct?).

Edubyah said:
They are not the same the Fender/1.2 is a 32a but they use the EB0 kernel like the 32b Dream. From what I have seen the 32a Magic use the EB1 kernel (correct?).
Click to expand...
Click to collapse
yes its eb1

Edubyah said:
Okay this thread is for the My Touch 1.2/Fender OTA to be released 1/12/11. If you have any insight as to what we need to do to "catch" this update please post here. I know a lot of people are going to say the Magic OTA has already been released but this is a different phone that was not included in the first update and I'm sure the Magic forum Moderator knows this better than most. Does anyone know for sure if we can just be on the stock Fender ROM with root and still receive the OTA? Any information regarding this topic is welcome please post for the rest of us!
Click to expand...
Click to collapse
tass0s said:
fender/1.2 i the same as 32A?
Click to expand...
Click to collapse
Edubyah said:
They are not the same the Fender/1.2 is a 32a but they use the EB0 kernel like the 32b Dream. From what I have seen the 32a Magic use the EB1 kernel (correct?).
Click to expand...
Click to collapse
tass0s said:
yes its eb1
Click to expand...
Click to collapse
You guys must have issues reading and searching. Not only has this been discussed... but I started an entire new thread just for this phone. And because I knew that would not be enough... I started a WHOLE new thread dedicated to the update just for this phone. Hell, I even made them stickies! Yet... here we are.
I merged your thread in with the appropriate topic already in discussion.

Un-rooting
DonJuan692006 said:
Cool, I'll be unrooting the wife's phone for this.
Click to expand...
Click to collapse
Does anyone know for sure that's necessary? I've heard that being on Binary's deodexed fender with root would suffice to receive the update. Anybody know for sure?
I know nobody want's to talk about it but that damn keyboard is the only reason I'm doing this to begin with.
Something else look at the tags this thread won't show up in a search NO TAGS!!!

Logcat to get update links
Edubyah said:
If you have any insight as to what we need to do to "catch" this update please post here.
Click to expand...
Click to collapse
Use logcat (search this forum) to capture the download link(s).
Expecting three separate zip files we collectively need links for. First should be new hboot/radio package. Second will be the ROM package for each device (one for for 1.2 and one for Fender.)
Edit: No more than two files, we already have hboot and a radio update (if any) would be packaged with the ROM itself. - K
Now what I want to know is will this keep my phone from rebooting when I get a Gmail or SMS notification while using Google Nav and Pandora radio at the same time?
Kind Regards,
Kevin

kpetrie77 said:
Use logcat (search this forum) to capture the download link(s).
Expecting three separate zip files we collectively need links for. First should be new hboot/radio package. Second will be the ROM package for each device (one for for 1.2 and one for Fender.)
Now what I want to know is will this keep my phone from rebooting when I get a Gmail or SMS notification while using Google Nav and Pandora radio at the same time?
Kind Regards,
Kevin
Click to expand...
Click to collapse
So being hooked to ADB running DDMS will give you the links?

I unrooted the wifes phone to make sure it catches the update. I'll be sticking with CM 6.1. I'm going to have her not do the updates when she gets prompted so I can pull the links. I don't imagine we'll see an SPL update, but I'm thinking we might get the new radio. We'll see, unless its in that announcement from T-Mobile already.
Sent from my HTC Magic using Tapatalk

DonJuan692006 said:
I unrooted the wifes phone to make sure it catches the update. I'll be sticking with CM 6.1. I'm going to have her not do the updates when she gets prompted so I can pull the links. I don't imagine we'll see an SPL update, but I'm thinking we might get the new radio. We'll see, unless its in that announcement from T-Mobile already.
Sent from my HTC Magic using Tapatalk
Click to expand...
Click to collapse
I'm going to try the stock Fender w/root. A while back I un-rooted and re-rooted but with the UniversalAndroot this time, so I should show up as stock if I am on 1.6 and my build.prop is right. Anybody know of an app that would store logcat on sdcard?

DonJuan692006 said:
I unrooted the wifes phone to make sure it catches the update. I'll be sticking with CM 6.1. I'm going to have her not do the updates when she gets prompted so I can pull the links. I don't imagine we'll see an SPL update, but I'm thinking we might get the new radio. We'll see, unless its in that announcement from T-Mobile already.
Sent from my HTC Magic using Tapatalk
Click to expand...
Click to collapse
I'm going to try the stock Fender w/root. A while back I un-rooted and re-rooted but with the UniversalAndroot this time, so I should show up as stock if I am on 1.6 and my build.prop is right. Anybody know of an app that would store logcat on sdcard?
I found a nice one in the market and the best thing about is after testing the logcat won't start when I start the app it will have information from long before the app starting point so this should work nicely.- See the update message start the logcat and it should go back far enough to include when the message was sent and any temporary cache download links (lets hope) This should get me the first one till I get home and hook to my computer-will running the ddms during the update process get any subsequent links?

Edubyah said:
Does anyone know for sure that's necessary? I've heard that being on Binary's deodexed fender with root would suffice to receive the update. Anybody know for sure?
I know nobody want's to talk about it but that damn keyboard is the only reason I'm doing this to begin with.
Something else look at the tags this thread won't show up in a search NO TAGS!!!
Click to expand...
Click to collapse
I'll add some tags in a few minutes.
If you are just using the stock just for the Swype keyboard you can look into SlideIT. Can't remember how much it costs but it's pretty much the same thing. Really. Some may even argue that it's better.
Regarding the update for the rooted stock roms... you should be able to get the update still. My theory is that the rom, spl and radio would be the only thing to get the update. Rom (stock), SPL, (1.33.0013), radio (2.22.23.02) possibly kernel. If any of these are different then you may not get the update. Another theory of mine is that it may require a certain build.prop file. It's been a while but I'm pretty sure that I used the same build.prop file in my rooted stock rom. So either way I don't see why you wouldn't still get the update.

Looks like I need to find a flashable 2.23.XX radio I switched to the 2708 radio when it came out.

Edubyah said:
Looks like I need to find a flashable 2.23.XX radio I switched to the 2708 radio when it came out.
Click to expand...
Click to collapse
And I bet that you didn't notice any difference, did you?

Anything to read a logcat will work. Download links should look something like below:
I/SystemUpdateService( 358): starting download of http://android.clients.google.com/packages/ota/tmobile_opal/package-name-here.zip
Just so I don't get a reply about this link not working... Again, just an example of what you are looking for.
Kind Regards,
Kevin

kpetrie77 said:
Anything to read a logcat will work. Download links should look something like below:
I/SystemUpdateService( 358): starting download of http://android.clients.google.com/packages/ota/tmobile_opal/package-name-here.zip
Just so I don't get a reply about this link not working... Again, just an example of what you are looking for.
Kind Regards,
Kevin
Click to expand...
Click to collapse
Hey i dunno wat da problm is but dat link isnt workn 4 me!!!!!!!!!!!!!
(Just kidding. Only giving you an example of what I have to go through on a daily basis.)