Mytouch 3G Official TMO (US) 1.6 Donut file? - myTouch 3G, Magic Android Development

I was wondering if anyone came across the the official T-mobile 1.6 Donut OTA file? I am trying to get my phone back to the official ROM because of the bad experiences I was having with Cyanogen latest ROM. I just want something to be stable and not asking me every time to "force quit" an application and just being so damn slow going from one application to another. It would be greatly appreciated if someone can tell me where I can dl that file so i can manually upgrade. I know that they are doing the PTA pushes now but i i dont know if I will get since I am running Cyanogen ROM. Please help!!

Seek and ye shall find...
http://forum.xda-developers.com/showthread.php?t=549754

I looked in and downloaded the file that was for the mt3g but the file itself does not have the "work email" application in the update. and to make things more confusing it says under my phone settings that model number of my phone is a G1. plus the wifi and bluetooth does not work either. is this suppose to be?

I don't think so, but in any case I recommend you ask in enomther's thread.

Just follow the instructions to UN-Root and wait for the OTA.

Related

changing tmobile extended rom for vodafone

Ok, i have spent ages trying to do something that i am sure is possible but i just can't get my head round it.
I have installed the latest t-mobile rom, no problems.
I know how to view the extended rom but i want to change this for the vodafone extended rom,
I know that ican install the voda rom cabs afterwards to remove the tmobile stuff but i want to do it permantly so that everytime i do a hard reset its all done automatically.
Should i be able to download a rom that is already altered like this anywhere?
If this makes any sense to anyone i would appreciate any help because i just don't know where i am going wrong...
Thanks
Why don't you install vodafone version instead ? (the german version)
Hi
check this http://forum.xda-developers.com/viewtopic.php?t=36220
i did the same but with a Qtek EXT Rom, download the latest Vodafone Update you can find, then just replace the EXT Rom file from the Tmobile or other update and replace it for the one you want, run normal update procedure and voila
Thanks for the replies, compumad, i can't seem to see your file on the ftp site?
I understand what you are saying etc but i'm afraid i don't understand how to do this at all.
What i need is some very friendly and clever person who is not so lazy as me :wink: to make the rom for me (it is christmas after all).
Failing that i might just give in and buy a new phone on contract and stop playing about with them!! lol.
cheers

Getting confused, I have RC30 (Rooted), Going to update

Hey all, Ill only ask this once, (Since after this time, Ill know for future updates and be on the right path =) )since this G1 is so new dev wise, its getting confusing when im studying everything all at once and only updated rooted once to the custom RC30. I saw the newer update is RC33, now when I apply that, is it required EACH TIME to wipe the device? Im asking cause it would be a pain to reinstall each app I had installed there to begin with. I know I wiped the 1st time I rooted and updated. So just wanted to check.
Also whats the new additions in these updates? Any good changelogs out there? I kinda like keeping the Tmobile US stuff on mine, but root access is awesome. =)
Thanks for any update tips out there atm.
Edit, My G1 is still on Firmware 1.1 is that a seperate update or how is everyone updating that with the custom stuff? Thanks. (And do I need that FW update before going RC33?)
Nope, you won't lose anything when you upgrade the firmware normally. Going from JF RC30 to JF RC33 should be fine
Check the stickied topic on the top of the forum to find out more:
http://forum.xda-developers.com/showthread.php?t=475381
The changelog is somewhere in there.
Thank you. =) I didnt read that one since it was talking about for UK users. Heh. Least it explained things a lil more. =DDD
What about the firmware? Seems Ill have to do the new radio too, but wondering.. is that radio one for US too or only uk? Since its in a UK thread. =/
Nah, it's not a UK topic. He just modifies the title when he adds something new. The radio should be for the US version. Just download the radio and JF RC33 and throw them on your microSD (one at a time obviously, named update.zip).
Firmware 1.1 is just like the base firmware number, you can ignore that. Firmware 1.5 (I think) is cupcake, so you get the idea.
Ok so the firmware is nothing major atm to update or would you still upset it? I havent looked into cupcake yet.
No, completely ignore the firmware number, the only numbers you want to look at are RC30, 33, etc...
Ok this is odd. I updated fine to RC33, however when I try to get back in recovery mode to apply the radio rom, it wont go into the recovery mode. It just keeps rebooting to the G1 screen when im holding the home button. Anyone seen that before or how to get back into the recovery mode?
Anyone have any ideas?

Some help needed adding root+tethering to a ROM

I haven't found any solutions to my problem on here, so I figured I'll have to try and make my own solution. Basically I want to take the MT3G stock, vanilla, retail COC10 build, and add root and tethering. That's the probably number 1 requested feature that people want, and I'm trying to find the solution for at least myself, if not to help others. I don't want all the extras and, no offense, garbage that is in all these other ROMs. I understand there's a need for that for some people, but I'm looking for just a clean, retail image for my MT that is very similar to the JF builds. Add root and netfilter/iptables. I'm aware JF added other things, but I don't want those. So here's my ideas for a solution...
I've got an obsession with this new 1-click Root program. I was able to get Cyanogen's 1.4 Recovery on my MT3G without flashing anything else, it's quite a nice trick for now. I've downloaded the original MT3G shipping COC10 image/update.zp and know that as long as i'm not off flashing Radio and SPL i'm pretty much safe. I did a nandroid backup anyway.
I'm going to for the first time try and dabble in ROM development/tweaking. I found in a thread on here someone mentioned how easy it was to add root on the stock ROM. Link to that particular post: http://forum.xda-developers.com/showpost.php?p=4333604&postcount=38
I haven't tried that just yet as i'm on a PPC Mac so no easy way to do it except trying VirtualPC with XP which isn't perfect. So, here starts my questions...
If the assumption of a "rooted" recovery image could work to put the SuperUser apk in, I should be able to do this, right? Again, remember I'm on Cyanogen's 1.4, but still have my stock, retail myTouch COC10.
Most of the commands listed to do over the ADB could probably be done in the recovery's console, correct? I will have no computer to do anything today, but I will have VNC/RDP access to my Mac with VPC/XP to do anything that may require a computer to compile. I figure then i can package it up and email it to myself, should I need to do that.
Now if that takes care of the root half of what I'm doing, how about the tethering... I understand haykuro has compiled a kernel that pretty much everyone is using in their ROMs that has netfilter enabled in it. How would I get access to that particular kernel so that I could use it as say a simple Update.zip much like the one for the Dream/ADP/G1 that is here: http://code.google.com/p/android-wifi-tether/wiki/ADP15KernelUpdate
If that is something in these forums, I haven't found it yet. So please, point me in the right direction. Assumably, with a kernel update and the root added, I would have everything I need, right? I'm not saying I want to break into the MT3G official update and start compiling it as an all-in-one ZIP that could be easily flashed to. That's out of my knowledge. But I would like to at least have the steps so that maybe it can be reproduced for the (apparently) minority out there that would like to stay as vanilla as possible.
UPDATE:
Okay, so I found a boot.img here (http://cluster.physik.uni-freiburg.de/~kuhnen/android/android.html) and I thought to myself what exactly IS the boot.img? That's not the SPL, right? or is it? Is it just the kernel? I never thought about it before, I was always flashing it, but never knew WHAT it did. If the file I found that is for vodafone works fine with the myTouch system, then I may have solved the other half of my problem. Seriously, anyone able to help? Or at least let me know what BOOT.IMG is.
Or even better yet, can't I just yank the BOOT.IMG/kernel out of haykuro's ION R2? Is it a hard task to do that? I would assume that the Ion was just the myTouch rebranded before the myTouch came out. So the kernel couldn't have changed much, if at all, since then. And since haykuro did enable tethering on that kernel, I could assumably use that, right?

[RUU] RUU_Hero_C_Sprint_1.56.651.2_signed_release.exe

Today I was reminded that being nice to people can pay off! I was lucky enough to get my hands on the new Sprint RUU thanks to syscrasher13!
What is this?
RUU (radio unit upgrade) is the way that our phones are flashed at the factory. It flashes all the factory images on to your phone.
The 1.29 RUU has always been available, however people that purchased phones that came with 1.56 on them were unable to use that RUU: http://geekfor.me/news/sprint-ruu-fails/
This is the updated version for those people that have "with Google" branded phones that came with software version 1.56 on them.
What can I do with it?
You can use this to "unroot" your phone before sending it in for warranty work.
Use it to flash back to stock if you are having any random issues on your phone that you can't fix.
It can 100% flash your phone back to how it came from the factory. As long as your phone turns on at all (even if it's not booting) then you should be able to save it by using this.
This means your phone is virtually unbrickable, unless you go flashing a radio or SPL or something that you shouldn't.
You can flash this on a phone that originally came with 1.29 on it, just know that once you do you will no longer be able to use the 1.29 RUU. You will have to use this one.
How do I use it?
Download the file below and run the exe.
Go in to the folder that the exe created and run ARUWizard.exe
What else do I need to know?
The phone is still rootable. I tested it successfully using the auto-rooter in the pre-kitchen.
Fresh ROM still works just fine (as should any 1.56 based rom)
You will not be able to use the 1.29 RUU after this one, but I don't know of any reason that you would want to
Although some img's in the RUU have different dates than the original it appears that they are identical other than system.img
You don't need to run this unless you are trying to return your phone to stock. You won't get anything special from running it.
Download here: http://geekfor.me/news/sprint_ruu_156/
Thank you so much flipz!! As always sharing the goods with the comunity!!!
Amazing work
thanks for sharing!
appreciate this very much!
thanks flipzmode....always a chance this could come in handy at some point
THANKS! was worried about having a with Google phone until now
thanks flipz
Many thanks!
Now, with this file on hand, I think it might be time to go ahead and root my new phone. Mostly I just want proper control over the device -- not likely to flash any ROMs until they evolve a little more -- but your work looks real solid and I plan on keeping up with it. Good show!
(on a side note, fwiw -- jumping ship from the Touch Pro to the Hero, after being with WinMo since the i730, has been my most satisfying smartphone experience, ever)
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Ooops: You did - on this page. Sorry.
johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
I think a RUU file deserves this, don't you?
JohnP
Click to expand...
Click to collapse
I've included md5 values on my releases since fresh 1.0. It's not in this post but if you click the link to go to the download page you'll see it there.
This definitely needs to be stickied...I know myself and others have often referenced the RUU in many troubleshooting posts throughout my (admittedly short) stay at xda so far.
Thank Flipz for getting and posting this stuff!
Thanks for this! Looks like we can root non Sprint CDMA Heroes now. (Cellular South, Bluegrass Cellular)
Any idea exactly how we managed to get this? From HTC? From Sprint?
I really want to find one for Cellular South and might as well try for Bluegrass Cellular since it has its own CID as well.
Doesn't look like the different version radio will be an issue, but would be nice to have the RUU around just in case.
johnp2343 said:
Hey, Thanks!
One minor request, though: Could you include the md5 values to your file releases from now on?
While it does not increase security, it gives assurances that the file has not been altered... and it allows us to verify downloaded files.
Click to expand...
Click to collapse
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.
posguy99 said:
It's been modified, it won't match Sprint's (or HTC's) md5sum in any case. So having the md5sum for this one doesn't buy you much.
Click to expand...
Click to collapse
Sprint and HTC aren't exactly providing an md5 on a file that hasn't been officially released. But I did create an md5 when I uploaded it so you know the file downloaded is the same one I uploaded.
Additionally the zip of the images located inside of the RUU are unmodifiable which is why we couldn't modify the old RUU to work with the new phones. When you start the RUU it will push the files to your phone and then check them. If they aren't what they are supposed to be, it will fail.
someone share the direct download link(eg, rapidshare link) to me?
i live in China and i cannot use the bit.ly services(because the gov blocked it)
fyi to those who are wondering this will work on a non google branded phone...however it does not fix the Rev 0 Rev a problem as it does not appear to update the pri to match that of the "with google" phones.
I dont care what sprint says and what htc says. My non google and my wifes google phone have two different speeds...
im exchanging mine for a with google phone today
Thanks!
this saved my phone. I was about to throw it away.
USB Connection Error
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.
nemesys504 said:
Tried running the RUU and got ERROR [170]: USB CONNECTION ERROR. Got in on a Windows XP and 7 laptop. Need help.
Click to expand...
Click to collapse
Just because we always have to ask to rule out the obvious...did you run it as administrator? (Right click on the file, select "Run as Administrator")
Same Problem
I am having same issue as above on Win 7 64 bit. However everything else works from this machine to my phone. Rooting it, usb mount of SD, screen shots, etc. Please help me. I want to flash back to starting point and start over.
Thanks.
Jamie

Rogers! Downgrade your device if you're stuck!

WHAT THIS IS FOR:
This is for those of you that upgraded to the newest rogers rom, and caught yourselves with an unrooted device.
IMPORTANT NOTE: Emergency phone calls are broken in this version (the whole reason for the upgrade), so see to it that you switch to a rom / boot.img that doesn't suck. (thanks a lot rogers >_>)
http://haykuro.polygonize.com/ROGERSDREAM.nbh.zip
Steps to take:
1. Download the file
2. Extract and rename to DREAIMG.nbh
3. Place on root of SD card (your SD card has to be formatted as FAT32 if it fails to find it in the next step!)
4. Power off, hold camera button, power on. This will boot into SPL and prompt you to install. Proceed.
5. After your phone is done flashing, it will prompt you to press another key to reboot the phone. Do so.
6. Use flashrec, and follow procedures to root again.
Haykuro strikes again! I didnt put the update on but im sure this will be put to good use.
wow dat was quick, so downgrade and follow the rooting process again is it ?
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Sejanus said:
What is this supposed to do? Should this be applied if we've already updated to the new Rogers rom?
What will this do if we haven't updated yet, but are still using something like CM 4.2.13?
Click to expand...
Click to collapse
if u havent update to the new rogers rom and having CM 4.2.13 then forget abt this,
if u flash rogers rom u will lose your root as i did
so better not to if u like the root, cos there is nothing special with the rogers update,
but the Magic update is awesome
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
I get the same thing! arrgghgh
Haykuro: can we use goldcard for this???
dotster said:
Gonna be the first guinea pig then...
------
UPDATE: REJECTED!!! Shiat!
Message:
"Main Version is older!"
Update Fail!
Do you want to reboot device?
<ACTION> Yes
<POWER> No
Btw, I think someone already tried this.
Somehow, it's got to be higher than the build 1.89 that Rogers/HTC gave us.
Any other ideas?
Click to expand...
Click to collapse
Get the same thing. Thanks for the effort Haykuro. Anything else up your sleeves?
ok update failed
dammm... was hoping for a fix!
Dropped the nbh file in my goldcard....nada....failed the same way.
I even ran the 1.89 RUU and replaced the rom.nbh file in the temp folder with the old one we all downloaded and named it rom.nbh.... just to see what would happen....failed
I'll have to try another goldcard....I might have messed up somewhere.
Can someone please try this with a goldcard and see if it works?
Thanks haykuro for getting on the ball on this....
Rogers.....karma is gonna be a B*&%$......for you guys one day....
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
weird, I have lost all the signal ever since trying to flash the nbh file
copolii said:
I already tried the older rom and it failed. I also tried with a goldcard and got the same response.
maybe I made a booboo, so if someone can make a goldcard image and send it to me ([email protected]) I'll give it another try.
This is my cid:
Code:
cat /sys/devices/platform/msm_sdcc.2/mmc_host/mmc1/mmc1:a32a/cid
0353445355323536802111d32400892e
Click to expand...
Click to collapse
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
alan090 said:
lol I find your signature funny
your the one who chose to run the ruu
you can only blame yourself
also htc makes the software not rogers
Click to expand...
Click to collapse
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
copolii said:
I actually spoke to HTC customer service on the phone. They said Rogers wanted it this way (a 1.5 build with no other fixes besides the 911 fix). So yes, HTC makes it, but Rogers wanted it this way.
Even without all this, still **** Rogers. They're still spineless sacks of ****.
Click to expand...
Click to collapse
... and that is even though HTC would be perfectly happy to make a 1.6 for them.
I assume that the 1-click-root vulnerability is gone, anybody try it?
Annoyances
So, I called Rogers tech support on Monday morning after they turned off my 3G and told the tech guy there that I've been running a ROM with the 911 fix since last September or so, and could they please turn my 3G back on. He did something on his end to re-provision my phone. I had to take out the battery for a little while and then boot my phone, and 3G came back up for me.
This wasn't good enough for Rogers. They have been sending me two text messages a day (one English and one French) and then calling me (twice) with recorded messages warning me about the 911 problem and that I need to 'upgrade'. This is a serious customer satisfaction issue with me. So, I figured it'd set me back for a few days, but I did the following to downgrade my phone from Cyanogen to the Rogers Donut-Hole release:
1) Installed Windows XP mode on my Windows 7 64 Bit OS, because the HTC Sync program wouldn't work on Windows 7 64-bit.
2) Downloaded and installed the HTC Sync program on my Windows XP virtual machine.
3) Dug around and found an old JACxHERO 1.0 ROM and I flashed it, hoping that the Rogers updater wouldn't detect this as a violation and abort.
4) Rebooted the phone, and joy of joys was able to get HTC Sync to connect to my virtual machine. The JACx HERO ROM has HTC Sync inside it, which was enough to fool the installer.
5) Ran the Rogers downgrader. This ran successfully... I just had to babysit the USB 'Attach' menu. If you're not on a virtual machine, you shouldn't need to worry about it.
6) Now I have the updated Radio image, and a downgraded 1.5 Android image.
I miss 1.6 terribly already. I wonder how long it'll be before Rogers detects that I've performed the upgrade so that I can try out this new Hakuro goodness (thanks Man!) and get my phone to a decent OS again. Anyone know how Rogers is detecting the upgraded version? Are they simply looking at the Radio image version? Or do they also know what OS Build I'm running?
I also upgraded my wife's phone. I hope the SMS and Recorded message abuse will now go away.
My message to Rogers would be: Get out of my life. I already pay you far too many dollars for the privilege of holding and using an HTC Dream on your golden network. It is super nice that you regard my safety above all else, however I have never in my life called 911, and really my safety is not your responsibility. I already know about the 911 bug, and had it fixed before you decided to meddle with all of your Canadian customers by removing their network connectivity and abusing them with myriads of reminders. Get out and stay out of my life!
Have a nice day.
I've tried all the usual methods with fastboot. Flashrec doesn't work. Logging in via adb doesn't give me shell access. Someone's tried the goldcard method.
Sigh.
Haykuro, what was your process for initially rooting the Magic? Didn't we send you one and you had to hook up some wires to it to get some port #s or something? (Sorry, it was long time ago.)
If need be, I'm getting an Magic upgrade once they are in stock and I'd be willing to lend you my Dream to hack at.
Sorry to here that you did that but as of now you are fooked.
There were steps in 1 of the 5 threads that told you how to perform the upgrade without flashing the "perfected perfect" spl but it's too late now.
sorry for your luck.
Same issue as everyone else, unable to flash old image...
My phone has been unusable since the update, reception has dropped to emergency calls only in my house, and 1 bar outside.
Every hour or so I have to reboot the phone, I get some ".process" error that keeps popping up in an infinite loop.
I need the droid from telus to be released, I have to ditch this garbage.

Categories

Resources