Related
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
This post for anyone who knows how to root the new updated Rogers HTC Magic with the new:
32A
HBoot - 1.76.0010
Radio - 6.35.10.18
Please post any comments or suggestions if they are applicable.
Thank you.
Rogers HTC Magic (32A)
HBoot - 1.76.0010
Radio - 6.35.10.18
I'm in the same boat. Updated my phone with the Rogers updater, and 1.76.0010 seems to be a perfected SPL. I'm going to attempt the gold card method once I get the necessary hardware this weekend. I'm just concerned I might brick my phone, since all the gold card tutorials are pretty old...
+1
Any results?
Diddo, same problem. Tried the "One Click Root", no joy.
I thought that the data connection issue was b/c of the new radio so I foolishly listened to Rogers. Last time I make that mistake.
I am also in dire ned of a method to root this, or even reverse Rogers....
Maybe try the full version of the Relenless Rooter plus (the one for perfected SPL) software? It seems that 1.76.0010 is a perfect SPL.
Thankfully, I read all over the web and decided not to use the security patch that Rogers suggested and did not update. I kept the 1.33.0009 SPL and was able to use the normal Relenless Rooter software. Don't know it the full software will work for the 1.76.0010 SPL but why don't give it a try.
i'm pretty sure it has already been tried, and doesn't work
i too, am in the same boat
rogers kind of bullied us into this update, and i feel really stupid for falling for it.
i hope someone is working on a fix, tho i am yet to read one post saying that someone is.
Not to be mean or rude or a troll, but there were several warnings against updating with the official RUU.
In fact the "Rogers Mandatory Update Thread" many people mentioned many times to just wait till it was rooted then flash the rooted ROM.
But some people had to be hasty...
Taknarosh said:
Not to be mean or rude or a troll, but there were several warnings against updating with the official RUU.
In fact the "Rogers Mandatory Update Thread" many people mentioned many times to just wait till it was rooted then flash the rooted ROM.
But some people had to be hasty...
Click to expand...
Click to collapse
Yes and no. What do you expect when Rogers cut off your data if you don't update. If you went to Android forums or here, you'll find what kind of saga people with rooted phones went in order to obtain data back.
So, at that time, people with the original cupcake had three choices: Root the phone and go through curse droid's complicated process to get his rom, root and find another Rom + patch so as to trick Rogers into believing that the phone has been updated, or just go ahead and flash the official rom (and then hope someone can root it).
visitador02 said:
Yes and no. What do you expect when Rogers cut off your data if you don't update. If you went to Android forums or here, you'll find what kind of saga people with rooted phones went in order to obtain data back.
So, at that time, people with the original cupcake had three choices: Root the phone and go through curse droid's complicated process to get his rom, root and find another Rom + patch so as to trick Rogers into believing that the phone has been updated, or just go ahead and flash the official rom (and then hope someone can root it).
Click to expand...
Click to collapse
Complicated procedure? You are mixing up two methods that made it possible to keep root. For cursor, all u needed to do was flash spl and radio, then his Rom, that's it. There is another method that allows u to keep original radio and. Spl, this one uses a script after applying a new rom. Just giving the facts, I do feel sorry for those that jumped the gun though, i was really close myself
visitador02 said:
Yes and no. What do you expect when Rogers cut off your data if you don't update. If you went to Android forums or here, you'll find what kind of saga people with rooted phones went in order to obtain data back.
So, at that time, people with the original cupcake had three choices: Root the phone and go through curse droid's complicated process to get his rom, root and find another Rom + patch so as to trick Rogers into believing that the phone has been updated, or just go ahead and flash the official rom (and then hope someone can root it).
Click to expand...
Click to collapse
Rogers cut off my data. I rooted phone and applied CursorSense ROM and now i'm good.
I would be happy to help any Roger customers who want to apply this ROM. The steps are pretty straight forward as long as you have some computer knowledge.
how do you root your phone after it has been updated? or how do you undo the update to root it? any help would be appreciated
crystalbellaboo said:
how do you root your phone after it has been updated? or how do you undo the update to root it? any help would be appreciated
Click to expand...
Click to collapse
That's the reason for this thread. The update includes a new radio and no developer have found a way around it. Maybe the main developers (aka chefs) have moved on to newer and more exciting devices, like the Nexus One.
Who knows, maybe you guys can band together and pay a developer to do this?
visitador02 said:
That's the reason for this thread. The update includes a new radio and no developer have found a way around it. Maybe the main developers (aka chefs) have moved on to newer and more exciting devices, like the Nexus One.
Who knows, maybe you guys can band together and pay a developer to do this?
Click to expand...
Click to collapse
It's the SPL that's perfected. Not the radio. And most devs for the 32A are still here. It's mostly G1/Dream devs namely Cyanogen who have moved on to the Nexus One.
Amon_RA is still giving updates to the G1/Dream and MT3G/Magic and Hero.
crystalbellaboo said:
how do you root your phone after it has been updated? or how do you undo the update to root it? any help would be appreciated
Click to expand...
Click to collapse
I didn't update my phone. I didn't realise that this was a problem. Sorry to get your hopes up.
Taknarosh said:
It's the SPL that's perfected. Not the radio. And most devs for the 32A are still here. It's mostly G1/Dream devs namely Cyanogen who have moved on to the Nexus One.
Amon_RA is still giving updates to the G1/Dream and MT3G/Magic and Hero.
Click to expand...
Click to collapse
You are right about the SPL. I meant that too. I mixed Radio and SPL because Rogers is scanning for the new radio even for those who have root, as the developers page show.
Anyway, best of luck to those who upgraded and got the perfected SPL. Maybe someone can ask a favor from one of the developers?
Some help with rooting the 32A magic from rogers
Already asked for help via PM, no dice. I suspect that after the update the devs are inundated with requests. I'm happy to pay for someone to figure this out, but don't really know who to approach. Anyone?
So still no luck on anyone rooting this update... This is taking a lot longer then I thought it would. I only did the update because I was sure someone would be willing to jump right on and root this new SPL but no dice.
FoTwoZero said:
So still no luck on anyone rooting this update... This is taking a lot longer then I thought it would. I only did the update because I was sure someone would be willing to jump right on and root this new SPL but no dice.
Click to expand...
Click to collapse
I know what you mean... hopefully someone comes through for us.
novadoc said:
I know what you mean... hopefully someone comes through for us.
Click to expand...
Click to collapse
If we dont get root within the month then I'm calling Rogers and complaining to them about random misc stuff that I'll make up about the phone to get rid of it and get a new(better) phone.
now im just guessing through trial and error but i believe that if you go to the new damage rom then you WILL NOT be able to go back to any roms that will change the PRI because i and others have been noticing that when getting the damage rom and we dont like it and want to wait for a faster stable version we try to go to the previous version and it freezes on boot screen, and in fact i just tried this with a few eris build that have been reported to change PRI and even the modded version of damage and that's what my phone has been doing any one else try and notice this or can confirm this?
rulyskull said:
now im just guessing through trial and error but i believe that if you go to the new damage rom then you WILL NOT be able to go back to any roms that will change the PRI because i and myself have been noticing that when getting the damage rom and we dont like it and want to wait for a faster stable version we try to go to the previous version and it freezes on boot screen, and in fact i just tried this with a few eris build that have been reported to change PRI and even the modded version of damage and that's what my phone has been doing any one else try and notice this or can confirm this?
Click to expand...
Click to collapse
I have been on the new v2r2 and gone back to 1.5 and damagev1 2.1. My pri is the same. It changed last night but was able to get it back to the right one using the MSL fix.
rulyskull said:
...because i and myself have been noticing that when getting the damage rom and we dont like it...[/B]
Click to expand...
Click to collapse
Multiple personality much?
Wasney said:
Multiple personality much?
Click to expand...
Click to collapse
my bad meant others lol thanks for pointing that out
Last night when all the PRI issues popping up, I was a flashing fool trying to simulate what was going on!
And I can tell you that the only thing that affected it was the ERIS builds!
I should say it was the Eris build and user error!
You gotta wipe after everything, if ya did it do it again!
Have you read the sticky threads on how to fix the issue???
if not, do it...thanks!
redram38 said:
I have been on the new v2r2 and gone back to 1.5 and damagev1 2.1. My pri is the same. It changed last night but was able to get it back to the right one using the MSL fix.
Click to expand...
Click to collapse
you have? so this is probably a different error but does your phone have the with google on the back? because mine doesn't and i know that the with google has a higher sense version (by like .55) and they fixed some problems with the ones without with google when changing sense so what im thinking now is that its not the pri its something different and going to be a pain to find out
Roman G said:
Last night when all the PRI issues popping up, I was a flashing fool trying to simulate what was going on!
And I can tell you that the only thing that affected it was the ERIS builds!
I should say it was the Eris build and user error!
You gotta wipe after everything, if ya did it do it again!
Click to expand...
Click to collapse
see i did this at least 8 times and still has this issue
The cause of the change of the PRI is not Damages latest ROM.
I was one of those that had to get their MSL to reset the phone, but I went
and re flashed Damages latest and the PRI stayed good.
So I'm pretty sure is not his.
There is people testing around trying to find which was the ROM that caused
it, but not sure if they have found out yet.
Okay this is what I did!
I am rooted and running a stock sprint ROM, this morning I flash this damage 2.0, bluethooth audio still does not work, but everything else was working great though. I nandroid back to 1.5!
Fast forward to this evening and all the problems everyone else has, and damage new version, I figure I will flash again to try it out! Then everyone starts talking about the PRI, so I jump in and start flashing other ROMS to try to get a different PRI#(Mine is 1.70_003).
So I go to the eris leak and flash PRI, it is still the same, but I have unknown operator and no sprint on my lock screen. Just for ****s and giggles I decide to flash back to the newest damage build without a wipe and what do ya know!
Now I have unknown OP and my PRI has changed to 2.11_002!
So now I am going to wipe and try to flash the newest damage build and see if it changes back!
I am wondering somewhere along the way some of you did not wipe first before flashing all these ROMS!
So it seems not doing a wipe causes this to change and stick for some unknown reason!
I am now back to rooted but stock and I still am stuck with the same bad PRI 2.11_002.
That was lastnight!
So this morning I did the PRI fix and got back to 1.70_003, and downloaded the legend leak ROM, did a wipe and flashed and verified my PRI was 1.70_003, then I nandroided like I did before without a wipe back to stock with root and my PRI is the same, so it is without a doubt related to the ERIS leak, and I also think that not wiping first has something to do with it as well!
I KNOW WITHOUT A SHADOW OF A DOUBT THE ERIS LEAK CAUSES THIS!
AND THAT IS REALLY THE ONLY ONE THAT WOULD AS THE PROBLEM DID NOT POP UP UNTIL THIS CAME OUT!
rulyskull said:
you have? so this is probably a different error but does your phone have the with google on the back? because mine doesn't and i know that the with google has a higher sense version (by like .55) and they fixed some problems with the ones without with google when changing sense so what im thinking now is that its not the pri its something different and going to be a pain to find out
Click to expand...
Click to collapse
yes, it has with google, but I still changed to the bad PRI last night for some reason. I got back the right one using the fix and it has stayed there even though I have had 3 diff Roms on my phone today, one being the new Damage v2r2. I am on v1 right now due to needing apps2sd. The only thing I did diff last night was forgot to wipe when flashing from one rom to the next once. I somehow think that is part of the issue.
You also have to remember that alot of builds that came out after the Eris leak were for the most part based on or contained part of the Eris leak!
So even if it did not say Eris leak it prolly had aspects of it in!
Roman G, I dont know if you are aware of this yet, but only way to get your old PRI 1.70_003 is to get the MSL and do a phone reset.
Flashing a RUU or any other Rom won't do the job.
MjPayne said:
Roman G, I dont know if you are aware of this yet, but only way to get your old PRI 1.70_003 is to get the MSL and do a phone reset.
Flashing a RUU or any other Rom won't do the job.
Click to expand...
Click to collapse
I not sure if your aware of this yet, because obviously you have not read anything I have posted, but I have done this 4 times already!
Thanks for the advice though!
I went back to my nandroid backup after installing damage's rom and I still don't have protected apps in the market. At least one other person has reported this so I know it's not just me.
I tried running the RUU back to a stock 1.5, still no protected apps.
I tried the pri fix that everyone is talking about. Called Sprint to get my number and followed the steps. Everything seemed to work ok but still no protected apps.
Anybody got any ideas?
I am wondering if there will be any issues returning my phone to sprint with the flipz01 PRI and this thread seems the best place to ask.
trying to clean sand from under my screen I blew out the microphone and can not use voice. I used Flipz tool to flash back to a stock ROM, however I noticed today that for PRI it says Flipz01. Sprint has already ordered me a replacement phone, but when I do give this phone back is there any way Flipz PRI can come back and penalize me?
Thanks in advance!
I'm new to the forum and I'm not a developer but I thought I would give out some information regarding the recent update I did for 2.2. Just a few issues since the update (build ERE27):
*I've had to reboot my phone a couple of times to restore 3G
*Had to reboot my phone to get the Gmail icon to open Gmail (instead it would open a browser that wouldn't load)
*The trackball has been lighting up without any notifications
Those are the only issues I've noticed so far. Aside of that, 2.2 has been great.
beaniejones said:
I'm new to the forum and I'm not a developer but I thought I would give out some information regarding the recent update I did for 2.2. Just a few issues since the update (build ERE27):
*I've had to reboot my phone a couple of times to restore 3G
*Had to reboot my phone to get the Gmail icon to open Gmail (instead it would open a browser that wouldn't load)
*The trackball has been lighting up without any notifications
Those are the only issues I've noticed so far. Aside of that, 2.2 has been great.
Click to expand...
Click to collapse
Hmm don't have any of these issues.
Maybe you didn't wipe properly when flashing froyo? I'd say try to reinstall it, looks like it's not FroYo problems, but something went wrong upon flashing/configuration.
Side note, did you originally have ERE27 or did you have to download it? (I see in your signature that you have the ATT version)
beaniejones said:
Side note, did you originally have ERE27 or did you have to download it? (I see in your signature that you have the ATT version)
Click to expand...
Click to collapse
I am Nexus One AT&T user could you tell me how to upgrade to Froyo. I dont really know anything about Androids. Im a newbie I got it on Friday
josuetenista said:
I am Nexus One AT&T user could you tell me how to upgrade to Froyo. I dont really know anything about Androids. Im a newbie I got it on Friday
Click to expand...
Click to collapse
Seriously? Don't. Do a lot of reading, and then read some more. Once you're done, read more again. Once you've read all you can, and you feel you know enough to not call yourself a noob, you're almost there. Now start reading all over again.
If you really really want to do something, don't go for froyo. Flash a custom rom like cyanogen, and get acquainted with the flashing process. The froyo release is more of a beta/pre-release version, and a noob shouldn't want anything to do with it. Wait for the OTA if you really want froyo.
flash froyo. Then wait for cyanogen to make a froyo rom, then flash that. Or, you can just wait for the OTA update. IF you need to know how to flash, there are wikis and tutorials at the beginning of forums. Read those b/c if you just ask, you will be destroyed.
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.)