Database Users

Here it is again folks! Htc hd official upgrade

I am not sure what is up them but here is the official release again.
Get it while it is hot!
http://forums.t-mobile.com/t5/HTC-H...ate-Now-Available-on-T-Mobile-com/td-p/380116

Did you try this? better than the original one they put out? I'm wondering why it's the same version number. Seems like a good way to confuse people.

Supposedly there were issues with downloading the originial release, so they had to correct that. But, the version they put up is the same one as before.
I've got all 3 "versions" of the new ROM now (leaked, first official issue, and this new one now too) and they're all the same.
Confusing? Yes. Big deal? Not really

so basically this isn't going to fix any issues? you downloaded it and it's the same everything? Why would they bother?

crisisinthecity said:
so basically this isn't going to fix any issues? you downloaded it and it's the same everything? Why would they bother?
Click to expand...
Click to collapse
Well yes it's the same as the first release of the 2.13 ROM if that's what you mean. I think they just put it back up because there's people who didn't get it before they had to pull it temporarily for the downloading issues. I assume it'll stay available there from now on.

crisisinthecity said:
Did you try this? better than the original one they put out? I'm wondering why it's the same version number. Seems like a good way to confuse people.
Click to expand...
Click to collapse
I used the First release and still have it on my computer at home. I downloaded the leaked version and it was a godsend. I hear when they made it official on the 18th it caused people a lot of problem even bricking. according to the link they where having server issues and that is why they had to pull the official release but I guessed they fixed the issues now. It is the same ROM version as the one I have so your guess is as good as mine. I think sirphunkee has them all downloaded but has not implemented them and is still running 2.10xxx

toreone said:
I used the First release and still have it on my computer at home. I downloaded the leaked version and it was a godsend. I hear when they made it official on the 18th it caused people a lot of problem even bricking. according to the link they where having server issues and that is why they had to pull the official release but I guessed they fixed the issues now. It is the same ROM version as the one I have so your guess is as good as mine. I think sirphunkee has them all downloaded but has not implemented them and is still running 2.10xxx
Click to expand...
Click to collapse
Correct, and I should have made that clear...still on 2.10, haven't flashed any of the upgrade downloads.
Somewhere in one of the threads in this section about the upgrade, the leaked version and the first "official" releases were compared and found to match bit-for-bit. Also, T-Mobile forums had confirmation that the recent re-release is identical to the one they put up before the download issues. So, by the commutative property of Windows Mobile Mathematics (WMM), they're all the same
However, that's not to say that the end experience from those who have flashed any of the three doesn't vary greatly. Some report a near-magical cleansing of demons, others are suddenly needing an exorcism...and this is across all three "releases" of this ROM.

sirphunkee said:
Correct, and I should have made that clear...still on 2.10, haven't flashed any of the upgrade downloads.
Somewhere in one of the threads in this section about the upgrade, the leaked version and the first "official" releases were compared and found to match bit-for-bit. Also, T-Mobile forums had confirmation that the recent re-release is identical to the one they put up before the download issues. So, by the commutative property of Windows Mobile Mathematics (WMM), they're all the same
However, that's not to say that the end experience from those who have flashed any of the three doesn't vary greatly. Some report a near-magical cleansing of demons, others are suddenly needing an exorcism...and this is across all three "releases" of this ROM.
Click to expand...
Click to collapse
I forget where I read...but a lot of people where having issue when the flashed to a custom rom then flashed to the upgraded tmobile rom with out returning their phones back to stock. I guess that was a major issue. Or people had to factory reset then run the upgrade I didn't do either of those things when I flashed and it worked great. I mean I didnt have CHT or Editor on but I did have a bunch of apps.

I bought my HD2 last week and the rom it came with from the factory is 2.13.531.1. I have had the phone freeze on me 2 or 3 times in the week I have owned it. Even though the rom that was just released is the same version would it still be a good idea to flash it? I am coming from a G1 and on occasion have flashed a rom and the phone ran like crap. Then upon re flashing the same exact rom the phone ran like normal.

I upgraded last evening, despite my initial trepidation.
Everything seems smooth now--a lot of the hiccups when texting seem to be gone (out of order texts, highlighting of last text sent and lag when trying to write a text that is part of a longer thread).
Swype is working a 100x better.
So far, so good.

ReganH22 said:
I bought my HD2 last week and the rom it came with from the factory is 2.13.531.1. I have had the phone freeze on me 2 or 3 times in the week I have owned it. Even though the rom that was just released is the same version would it still be a good idea to flash it? I am coming from a G1 and on occasion have flashed a rom and the phone ran like crap. Then upon re flashing the same exact rom the phone ran like normal.
Click to expand...
Click to collapse
That happens with winmo as well as android....after flashing a ROM, sometimes either a re-flash, or an immediate hard-reset is needed to get it to "stick". In fact, most chefs recommend doing a hard-reset right after a new flash, just to be safe, and I've seen numberous times where a buggy install is fixed perfectly just by doing that. So, if you're fine with the effort involved, I would certainly suggest it...it certainly can't hurt

Cool. Thanks for the info sirphunkee.

Software Upgrade or ROM
I downloaded the update from T-Mobile and have it running on my HD2. Was this an update to my ROM, so a hard reset will reload this update? I talked with a T-Mobile rep on the phone who said a hard reset would remove the update and I would have to re-install it.

jwperez1 said:
I downloaded the update from T-Mobile and have it running on my HD2. Was this an update to my ROM, so a hard reset will reload this update? I talked with a T-Mobile rep on the phone who said a hard reset would remove the update and I would have to re-install it.
Click to expand...
Click to collapse
Good thing you asked here to be sure
No, a hard-reset will only "reload" whatever the currently flashed ROM is...whether it's an official update or a custom ROM.

Bell galaxy s data fix

hey guys i recently flashed my phone to froyo 2.2 and lost data connection, however my problem was not that i didnt have the reqquired band but my apn settings were reset. so if u flashed ur phone and lost data check ur apn settings first ... it should look like this
APN: pda.bell.ca
Proxy server: web.wireless.bell.ca
Port: 80
after i entered the info my data started working again
hope this helps...

did flash to official jpm via hacked kies? how's everything so far?

That may work but it's not the default settings. APN should be inet.bell.ca, not sure about the rest.

get ready for it to get bricked in the next couple of days

ya i flashed via kies, everything works well, feels alot snappier without lagfix..also the samsung task manager seems to work better as it kills programs that arnt running alot faster.

bimmerboii said:
get ready for it to get bricked in the next couple of days
Click to expand...
Click to collapse
i'm going to have to agree with this guy......a few days, and a few reboots, and you'll be bricked.

The apn settings should be like this:
name: Bell
APN: inet.bell.ca
rest , leave them empty and save and use. tried and tested.

Ya. I am alo on be and confirm its inet.bell
I retured a phone i updated to 2.2 cuz was verry unstable and keeps fc on multitasking.
Also when i flashed back to the stoxk bell jh2 i could not get the bell branding csc file to restore all the programs correctly. So i just gave up and doa the phone with new one
Good luck. And btw now that you have updated you will not get the update id any that bell givea the rest of us.
Sent from my GT-I9000M using XDA App

wang1chung said:
i'm going to have to agree with this guy......a few days, and a few reboots, and you'll be bricked.
Click to expand...
Click to collapse
Why would it be bricked? I just updated mine yesterday to froyo on bell.

i too am on bell, and have tried updating to jpk and jpm. it never turns out well, and if you start getting FC's and "can't mount" errors in recovery, i suggest you flash back to jh2 before your sdcard gets corrupted to the point where you can't flash it.
i'm just saying a lot of people were having this issue with the bell i9000m when flashing to froyo.

bassboy_pete said:
Why would it be bricked? I just updated mine yesterday to froyo on bell.
Click to expand...
Click to collapse
prepare yours to be bricked as well lol
wang1chung said:
i too am on bell, and have tried updating to jpk and jpm. it never turns out well, and if you start getting FC's and "can't mount" errors in recovery, i suggest you flash back to jh2 before your sdcard gets corrupted to the point where you can't flash it.
i'm just saying a lot of people were having this issue with the bell i9000m when flashing to froyo.
Click to expand...
Click to collapse
Spot on.. (based on observation and some other threads) most Bell i9000M get corrupted a few days after flashing i9000 roms. Once it gets corrupted you will have to send the phone for repairs.

Just wait for Bell's official 2.2...it wont be long

Out of the 3 SGS's I have , only one had a problem with the SD Card. All 3 were on JPK and are now on JPM. The only one that had this problem had a lagfix installed. The other 2 don't and are still alive since JPK was put on them on the day of it's release. JPM was put on all 3 of them last night. I only have the 850Mhz problem with the 3 of them. The SDCard problem is not related to Froyo as others have had it happen with 2.1 . The phone I had fixed got a brand new system board installed in it but the rest of the phone was my old one since I had marked both with a marker.

I noticed people were commenting on which APN is correct (inet.bell.ca or pda.bell.ca).
As shipped, the phones came set with inet.bell.ca as the APN. This is actually their APN for tethered connections. While it works fine for data, people on older plans without a tethering option were getting charged fees for tethering because of this.
pda.bell.ca is what all other phones use for on-device data, which is why most people suggest using that one. Both will work on the SGS.

ya i just noticed my phone getting alot of force closes, then when i rebooted it got stuck on the galaxy s screen. went into download mode and flashed back to jh2 with odin, phone works fine now...and as for not being able to update through kies, im not too worried about that as odin makes it easy to flash new firmwares...and i have a feeling bell is gonna slack on rolling out 2.2 anyways. and most of us that root out phones do not have much interest goin with stock roms anyways

bimmerboii said:
Spot on.. (based on observation and some other threads) most Bell i9000M get corrupted a few days after flashing i9000 roms.
Click to expand...
Click to collapse
labellee25 said:
The SDCard problem is not related to Froyo as others have had it happen with 2.1
Click to expand...
Click to collapse
Doesnt have to be 2.2... Happens as long as it's the i9000 rom

Weird, I have a bell i9000M (got it in august). Ive flashed to froyo using the kies registry hack and its been running flawlessly, havent experienced any force closes or lag

bimmerboii said:
get ready for it to get bricked in the next couple of days
Click to expand...
Click to collapse
This is not true have you looked at the SD thread?? look at the votes. http://forum.xda-developers.com/showthread.php?t=793404&page=32 its about 50% failed with 2.1 and 50% with 2.2

TriC_101 said:
This is not true have you looked at the SD thread?? look at the votes. http://forum.xda-developers.com/showthread.php?t=793404&page=32 its about 50% failed with 2.1 and 50% with 2.2
Click to expand...
Click to collapse
Did you even read this thread? OP already said his phone was starting to act up already and flashed it back.
And if you read my previous posts, i didnt limit the failure to 2.2 alone.

{C}Canada bell galaxy!!WARNING!! FLASING!FAIL REBOOTING!!VOODOO!!STUCK AT S LOGO..ETC

This issue only applies on Canada Bell Galaxy S Vibrant I9000m (not international i9000)
My experience:
installed Voodoo.. one day, my phone wouln't boot up..
Upgrade a lite version of firmware through odin and update.zip
cell phone stuck at S logo forever
I went to the bell store and got a replace one
I didn't learn my leason...
upgrade 2.2 version to my new device
works fine for 3 days and then fail to reboot
bell store sent my device for repair(i waited 10 days)
they said one of the components on the motherboard got replaced.....
SO please aware!!!!!!
First, DO NOT use odin to retore or upgrade your galaxy. This will cuze flashing(when rebooting), rebooting fail, and stuck at S log.
Reason: Since your model is i9000m not i9000, 99%of the firmwares will not support this model(basically you are using a wrong firmware)
Second: do not install OCLF or Voodoo!! if you feel your homesceen lagg!! you can install laungh pro or ADW(i prefer ADW, fast and easy)
Reason:For people who are using the international i9000, it is fine becasue they can restore the device via odin. Since bell i9000m has no compatible firmware!! DO NOT take the risk!!!!! wait untill 2.2 version which is coming at the end of Nov

I agree with you. Bottom line is dont mess around with the Bell Galaxy Vibrant. Just wait until Bell releases 2.2 for it. It's not the same as the regular i9000 where you can flash roms all you want.

This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.

TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
If you read around, you're actually one of the lucky ones. I'm on my 5th Bell SGS and of the failed ones:
A) Zero changed ROMs
B) Two I tried to lagfix
C) Three I tried root
My most recent one has survived a little over a month now... rooted, but I've never touched another rom/lagfix.
If you read the Bell SD issue thread, the worldwide 2.2 is a huge contributor to Bell SGS failures.

I agree i was researching about lag fix. When i look for bricking incidence by voodoo or ryanza, it's usually i9000m for some reason.....
But i say we are lucky ones because we dont face too much lag problem. Phone lags at times which i understand. It's been performing way better than my netbook.
Sent from my GT-I9000M using XDA App

ca7846 said:
I agree i was researching about lag fix. When i look for bricking incidence by voodoo or ryanza, it's usually i9000m for some reason.....
But i say we are lucky ones because we dont face too much lag problem. Phone lags at times which i understand. It's been performing way better than my netbook.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
The lag problem was not an issue for me running JH2 for about a month. Then the slow attacked, and it was lagging lagging lagging..
So it looks like about once a month I'll have to revert to a Nandroid backup to undo the lag mania.

TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
i know that there are some people, such as yourself, that aren't experiencing any issues, but other people, such as myself, have flashed froyo correctly, and have their phone die within a couple of days as a result. there has to be something else that is different, if the hardware is the same.
if you look at the two threads about sdcard failure, it's 12% for the i9000's and 30.97% for the i9000m's. clearly more than double the failure rate. i think there is definately something that is different between the two. i just wish someone could figure it out so i could safely flash international roms.

wang1chung said:
i know that there are some people, such as yourself, that aren't experiencing any issues, but other people, such as myself, have flashed froyo correctly, and have their phone die within a couple of days as a result. there has to be something else that is different, if the hardware is the same.
if you look at the two threads about sdcard failure, it's 12% for the i9000's and 30.97% for the i9000m's. clearly more than double the failure rate. i think there is definately something that is different between the two. i just wish someone could figure it out so i could safely flash international roms.
Click to expand...
Click to collapse
Spot on. Most threads here with the Bell i9000M are mostly seeking help to fix their bricked phones. And if you read them, the problem usually comes after applying lag fix or flashing a rom, etc. It wont come immediately, but the phone will start to "die" out. It may or may not happen to you, but the probability is quite likely.

I think the difference is.most of the euro 9 000 r 8gb.versions... the 9000m r 16gb versions... diff memory chip.
Sent from my GT-I9000M using Tapatalk

TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
I agree with you. We all know there were some 9000m with internal memory issues that caused some failures and flashing has its risks, no matter what phone you use.
I've flashed my i9000m now about umpteen times, I've run voodoo, oclf, among other things and haven't had any problems. So now I'm using JPK without any lagfix, and its running perfectly now.

wlz1028 said:
This issue only applies on Canada Bell Galaxy S Vibrant I9000m (not international i9000)
My experience:
installed Voodoo.. one day, my phone wouln't boot up..
Upgrade a lite version of firmware through odin and update.zip
cell phone stuck at S logo forever
I went to the bell store and got a replace one
I didn't learn my leason...
upgrade 2.2 version to my new device
works fine for 3 days and then fail to reboot
bell store sent my device for repair(i waited 10 days)
they said one of the components on the motherboard got replaced.....
SO please aware!!!!!!
First, DO NOT use odin to retore or upgrade your galaxy. This will cuze flashing(when rebooting), rebooting fail, and stuck at S log.
Reason: Since your model is i9000m not i9000, 99%of the firmwares will not support this model(basically you are using a wrong firmware)
Second: do not install OCLF or Voodoo!! if you feel your homesceen lagg!! you can install laungh pro or ADW(i prefer ADW, fast and easy)
Reason:For people who are using the international i9000, it is fine becasue they can restore the device via odin. Since bell i9000m has no compatible firmware!! DO NOT take the risk!!!!! wait untill 2.2 version which is coming at the end of Nov
Click to expand...
Click to collapse
Very good morning,
First I want to congratulate you for the support given from this site, second I would like to explain my problem
I have a Galaxy S GT19000 8 gb I have it with my operator Movistar, the problem is that for some reason I upgraded the firmware by mistake and now I get the logo type AT & T and I finally fails PANIC KERNEL, I tried to restore it but Unfortunately in any PC that connects Sea XP, VISTA, WIN7 recognizes me, I wonder if there is any solution to this problem and now I have to admit that only serve to throw.
Greetings and again good work that they are doing.

I don't have any issues with my i9000M.
I've rooted it, flashed 3 times with official firmware from Kies (no registry change) and also applied OCLF. My phone is still up and running! (*knock on wood*)

MaelstromXC said:
I don't have any issues with my i9000M.
I've rooted it, flashed 3 times with official firmware from Kies (no registry change) and also applied OCLF. My phone is still up and running! (*knock on wood*)
Click to expand...
Click to collapse
go flash jpm, and report back after 3 days and a few reboots.
the issue isn't with official bell roms, it's with international ones. if you flash jpm, you have a high chance of your phone bricking (unless you're one of the few lucky ones).

shadoslayer said:
I agree with you. We all know there were some 9000m with internal memory issues that caused some failures and flashing has its risks, no matter what phone you use.
I've flashed my i9000m now about umpteen times, I've run voodoo, oclf, among other things and haven't had any problems. So now I'm using JPK without any lagfix, and its running perfectly now.
Click to expand...
Click to collapse
well, if we are so sure the hardware is the same, the only thing left is the bml's, correct? if that is where the wear leveling is, why don't we extract and compare? i sent mine in, but i do have a backup of bml3 and bml6.

I had Darky's 2.2 ROM on my i9000m for two days before flashing back go JH2+Voodoo. I didnt specifically have any problems with the phone, but the ROM took away my 850MHz band so I reverted.

Hi,
I'm new here and I bought a Bell Galaxy last week. Yesterday, I installed OCLF on it and have no problem yet. Should I uninstall it to make sure?This thread put a doubt about my OCLF installation.
Any advice? If my phone bug, there will be a "factory reset" option for me?
Regards,
Snooze

I have the Bell Vibrant i9000m and have flashed about 5 times. Unlocked and running on Rogers. I've only had one problem and that was the phone restarting during a flash, went into download mode and restored to stock 2.1 via Odin3 1.3.

I have the GT-I9000M and never encountered a problem of flashing different firmwares, until I tried flashing voodoo. I believe the problem lies in the original F/W Kernal's not recognizing the partition of the internal SD since the Partition are in a different format. Creating a SD Card Failure when putting an original F/W without disabling voodoo first. Since it cannot mount the partition it cannot copy over files over to install a different F/W. I just wish there was a small Flash Kernal that would simple wipe the SDCard, partition and format to the original format for convenience sake of all these troubled i9000 users. I've just encountered this and is the only time I've ever encountered a problem with SDcard failures. I've flash numerous F/W without any problems. I've gone 2.1 to 2.2 back to 2.1 (UG8/JH2/JM8&Voodoo/JPA/JPK/JPM). From losing my 850 band just to get it back with the right procedure. All I can say RFS may not be the best file system but its the one I'll probably stick with when I get my phone back. Besides 2.2 was never that bad without a lag fix anyways just wanted to try something new. Also just in reference it has also shown in polls that it didn't matter whether you were on 2.1 with or without lagfix or 2.2 with/without lagfix either that the Sd Card could also fail. For now I'm just sharing my experience

Woolios said:
I have the GT-I9000M and never encountered a problem of flashing different firmwares, until I tried flashing voodoo. I believe the problem lies in the original F/W Kernal's not recognizing the partition of the internal SD since the Partition are in a different format. Creating a SD Card Failure when putting an original F/W without disabling voodoo first. Since it cannot mount the partition it cannot copy over files over to install a different F/W. I just wish there was a small Flash Kernal that would simple wipe the SDCard, partition and format to the original format for convenience sake of all these troubled i9000 users. I've just encountered this and is the only time I've ever encountered a problem with SDcard failures. I've flash numerous F/W without any problems. I've gone 2.1 to 2.2 back to 2.1 (UG8/JH2/JM8&Voodoo/JPA/JPK/JPM). From losing my 850 band just to get it back with the right procedure. All I can say RFS may not be the best file system but its the one I'll probably stick with when I get my phone back. Besides 2.2 was never that bad without a lag fix anyways just wanted to try something new. Also just in reference it has also shown in polls that it didn't matter whether you were on 2.1 with or without lagfix or 2.2 with/without lagfix either that the Sd Card could also fail. For now I'm just sharing my experience
Click to expand...
Click to collapse
totally agree...http://forum.xda-developers.com/showthread.php?t=793404...look at the number it doesnt matter if it is 2.1 2.2 or no lagfix....the amount of sd card failures are the same...it isnt the rom its just ur phone...numbers dont lie

TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
Exactly what I was thinking.

Note 2 - 4.3 Update coming soon:

Well instead of me writing, here is the link:
http://www.guru3d.com/news_story/galaxy_s4s3note_2_getting_4_3_gear_support_in_the_coming_weeks.html
I hope someone can leak out the final built for the n7105 section... I live in Australia, if America is getting it in a couple of weeks it means I'm getting it in a couple of years so we would appreciate the leak once it's released.

new thread, subsribed!!
via Note2

agreed mate
electroking said:
Well instead of me writing, here is the link:
http://www.guru3d.com/news_story/galaxy_s4s3note_2_getting_4_3_gear_support_in_the_coming_weeks.html
I hope someone can leak out the final built for the n7105 section... I live in Australia, if America is getting it in a couple of weeks it means I'm getting it in a couple of years so we would appreciate the leak once it's released.
Click to expand...
Click to collapse
im the same live in brissy been trying the at&t version seanz rom everything works but dont have wifi due to bootloader issues be sweet once that is sorted the rom is butter smooth but no wifi is the killer as vodafone data sucks nuts on 4g where i am

This is the update schedule for American carriers. Does that mean that unlocked phones will get it sooner? I hope so. I only just bought the note 2 (Best decision ever) and would love it to be running on 4.3 ASAP.

mattytheflasher said:
im the same live in brissy been trying the at&t version seanz rom everything works but dont have wifi due to bootloader issues be sweet once that is sorted the rom is butter smooth but no wifi is the killer as vodafone data sucks nuts on 4g where i am
Click to expand...
Click to collapse
I live in Brizzy too and I'll second or third that if its the only way we can get it? Sorry for the possibly stupid question, but is it true that if you have rooted and installed a custom rom, then you won't get the push update from your carrier anyway?... so.... the only way to get 4.3 on my (and I assume your rooted phone) is via custom rom download?

whokilledsanta said:
I live in Brizzy too and I'll second or third that if its the only way we can get it? Sorry for the possibly stupid question, but is it true that if you have rooted and installed a custom rom, then you won't get the push update from your carrier anyway?... so.... the only way to get 4.3 on my (and I assume your rooted phone) is via custom rom download?
Click to expand...
Click to collapse
or if you go back to stock.
have issues with the ota updater as soon as i root my device. The moment i do that i get the message that my device has been changed and i cannot use the updater then. if i flash stock withouth root i don't have this issue.
reckon its best to make a backup of your apps with TB or any similar program when the official update is available, then flash back stock (no root) and update, afterwards simply restore your normal (non-system) apps and your ready

I'm in Aus too, but the official story (courtesy of Telstra) is that there won't be any updates as of JB 4.1.2, unless there's sufficient backlash ...

morph000 said:
I'm in Aus too, but the official story (courtesy of Telstra) is that there won't be any updates as of JB 4.1.2, unless there's sufficient backlash ...
Click to expand...
Click to collapse
To answer you and the gentleman above... Australia will probably be the last country on earth to get the update as usual. So we might have to reside to getting it of some kind developer who uploads it here somewhere.
If you do wish to get updates you should go back to stock firmware (probably the first backup you made for your telstra 4.1.2) doesn't matter if it's rooted. Connect your phone to the PC and have KIES installed. Click update firmware and update (done, it will automatically unroot your phone and put back the stock recovery). You can easily update after that.
If anyone finds any android 4.3 working please update us here as soon as you can with a link to the page. If I find a working ROM for the official android 4.3 TW ROM I'll post it here too.

I don't think Aussie tel companies will well I don't have high hopes when it comes to Samsung I've always had HTC and Samsung and it's always the same get f all. I'm using 4.3.1 carbon I use GMD spen features for spen control and gestures don't use stock Sammy apps anyway.. just the 4.3 would be good because it's smooth as
Sent from my GT-N7105 using Tapatalk

I like the update 4.3 but ill want rom without knox. I need root
Sent from my GT-N7100 using xda app-developers app

Well now...I've been holding off playing with rooting my phone (as I'm new to 'droid and have an awful lot to learn, but have come a LONG way in 2 weeks) as I was expecting Telstra to release an update. Since that appears NOT to be forthcoming, Ill consider the various root options, none of which are particularly appealing at the moment mainly as it seems no-one has a stock ROM for this phone online and I can't backup mine without root. Catch 22 it seems. Information on locked bootloaders, Telstra ROM mods, rooting the 7105 "T" version is VERY limited
So...if anyone happens to have a link for a ROM copy please let me know.
(Or info on a rooting technique that works)

Ultimately every one on xda will be using the custom 4.3 rom for the note 3 goodies because Samsung will not be releasing those features in it's official release
Sent from my GT-N7100 using Tapatalk 2

morph000 said:
Well now...I've been holding off playing with rooting my phone (as I'm new to 'droid and have an awful lot to learn, but have come a LONG way in 2 weeks) as I was expecting Telstra to release an update. Since that appears NOT to be forthcoming, Ill consider the various root options, none of which are particularly appealing at the moment mainly as it seems no-one has a stock ROM for this phone online and I can't backup mine without root. Catch 22 it seems. Information on locked bootloaders, Telstra ROM mods, rooting the 7105 "T" version is VERY limited
So...if anyone happens to have a link for a ROM copy please let me know.
(Or info on a rooting technique that works)
Click to expand...
Click to collapse
Okay I will explain what I done for you...
When I first rooted my Galaxy Note 2 in May, I was a new-comer to android, I had an iPhone for a long time. What I done was root my phone, I Odin installed TWRP after rooting because I really don't like CWM (those are the names of the 'recoveries' available), they will replace the default Samsung recovery. Just make sure you get TWRP. I think it's up to TWRP 2.6.3
Well yeah let's get back to the topic, as soon as I rooted I used TWRP to make a backup of my default Telstra ROM (completely with EFS, MODEM, basically tick everything you can possibly backup).
I took that backup and put it on my laptop and on my PC and I kept a copy on my external card the whole time. That was the best idea, any time I ever had any problems with my phone I went back to that backup. I even soft bricked my phone once and after hours of panicking I realised I can just Re-install the default backup, and it fixed my phone.
Oh and I just recently un-rooted my phone to check for updates. All I done was use SuperSU to do an UNROOT. Then went into recover, restored the original backup I made of the Telstra ROM. Plugged my phone into the PC, and used Samsung KIES to check for firmware update. It just restarted my phone, removed TWRP recovery, re-installed the samsung one, and it removed the root completely and I'm basically went back to my original telstra ROM. I can go into settings and check for updates and everything. (I can confirm there is no update as of yet).
AS for your other QUESTION.
ALL THE ROMS in the N7105 Section will WORK with your N7105T Model. It's the same thing. JUST WATCH OUT and make sure you never install N7100 ROMS (They will soft-brick and could hard-brick your phone).

Thanks for the input.
I've been considering between 3, namely CF AutoRoot, Galaxy Note Toolkit And (exploit based) Framaroot, with a bias towards Toolkit so far ( as it specifies the 7105 "T" variant).
But if you've actually ODINed a GT-7105T (Telstra) with CWP without issues, I'll certainly consider that.
Any one else care to chime in on this (if you've done the same phone/telco only though !)
I've come far enough to understand rooting,boot processes, CWM/TWRP, exploits AND the importance of picking the exact model !:laugh:
I'll take the plunge when I get enough input to decide.

morph000 said:
Thanks for the input.
I've been considering between 3, namely CF AutoRoot, Galaxy Note Toolkit And (exploit based) Framaroot, with a bias towards Toolkit so far ( as it specifies the 7105 "T" variant).
But if you've actually ODINed a GT-7105T (Telstra) with CWP without issues, I'll certainly consider that.
Any one else care to chime in on this (if you've done the same phone/telco only though !)
I've come far enough to understand rooting,boot processes, CWM/TWRP, exploits AND the importance of picking the exact model !:laugh:
I'll take the plunge when I get enough input to decide.
Click to expand...
Click to collapse
It's not that hard really, you can't really mess it up if you follow the instructions... Hey root it whichever way you see fit, whatever you think is easier for you, don't listen to me. But I do highly recommend you get TWRP for backing up and formatting and installing your ROMS. Also I recommend PAC-MAN it's a good ROM, but it's not very stable at the moment (kind of).

electroking said:
It's not that hard really, you can't really mess it up if you follow the instructions... Hey root it whichever way you see fit, whatever you think is easier for you, don't listen to me. But I do highly recommend you get TWRP for backing up and formatting and installing your ROMS. Also I recommend PAC-MAN it's a good ROM, but it's not very stable at the moment (kind of).
Click to expand...
Click to collapse
Don't take offense at my asking for multiple inputs. I just don't want to brick at $600 phone needlessly
I've now sourced a ROM from Sammobile and downloaded it last night.
I'm backing up settings and stuff tonight and will run with Galaxy Note 2 Toolkit tomorrow (I went PRO) and go for option 3 - THE LOT !
Hopefully it'll all go ok.

morph000 said:
Don't take offense at my asking for multiple inputs. I just don't want to brick at $600 phone needlessly
I've now sourced a ROM from Sammobile and downloaded it last night.
I'm backing up settings and stuff tonight and will run with Galaxy Note 2 Toolkit tomorrow (I went PRO) and go for option 3 - THE LOT !
Hopefully it'll all go ok.
Click to expand...
Click to collapse
Haha you don't go pro over night my friend. Hope it all went all, if you have any issues or like to share your experience with the ROMS let us know.

electroking said:
Haha you don't go pro over night my friend. Hope it all went all, if you have any issues or like to share your experience with the ROMS let us know.
Click to expand...
Click to collapse
Well, I did the deed last night with Toolkit PRO and it all went smoothly. No Telstra or Samsung nasties reared their heads PLUS there wasn't a yellow triangle either !
That's the trouble with being in Oz. It's such a small market and REAL information is very hard to come by...so one is very cautious !
Anyway thanks for your assistance :victory:

morph000 said:
Well, I did the deed last night with Toolkit PRO and it all went smoothly. No Telstra or Samsung nasties reared their heads PLUS there wasn't a yellow triangle either !
That's the trouble with being in Oz. It's such a small market and REAL information is very hard to come by...so one is very cautious !
Anyway thanks for your assistance :victory:
Click to expand...
Click to collapse
I Odin flashed mine straight out of the box before I even set it up pulled backup and kept stock rom for warranty only.. these phones are pretty much unbrickable to an extent just don't go trying flashing n7100 roms and you'll be fine at&t roms are ok too just don't flash their bootloaders or even try to.. I change roms daily and have for like the last 2 years on my original note plus HTC's if your unsure on anything this place is helpful more than bloody Samsung
Sent from my GT-N7105 using Tapatalk

Sammobile: 4.3 is rolling out for the S3.

[Q] Weird problem; hoping I don't have to use warranty

Hey all,
So after flashing a bunch of custom ROMs I reverted back to stock. Once I had stock I ignorantly upgraded OTA...I now have that damn Knox crap. Fine. But all of a sudden I can't hear any sound, anywhere, I can't play any video (YouTube or browser embedded), my camera video recorder doesn't function at all, my phone doesn't work, and who knows what else.
I've flashed back to stock multiple times with Odin, as well as tried my custom ROM of choice (SlimBean) and it's always the same. I have no idea what could have caused this and don't know how to get back to a functioning phone.
With my warranty now void I don't know what to do. TriangleAway said it worked but it didn't, it remains 18...I tried twice. I'm thinking I might just have to say to Telus that after I upgraded with their OTA it got messed so I tried flashing back to stock 18 times lol
Ideas?

I just found out about the Best Buy Samsung centres. I'm going to go to them and see what happens!
UPDATE:
So the Samsung guy played with my phone for a bit and agreed it needed a flash, blah blah blah. He was about to do it and then asked if I rooted. I decided not to lie. He then went on to tell me it was against the integrity of his company to flash it for me. I tried a few different logical angles but he just kept saying no. Pretty lame since him helping wouldn't do anything except give me my phone back. If they don't want people flashing a phone that had previously been flashable then there should be some sort of front-facing warning for customers. If I had known that I would not be able to freely flash my phone I may have reconsidered Samsung.

I downloaded the new "stock" 4.3 and flashed that with Odin. Everything works again. Should I never flash a custom ROM again?!
EDIT:
The file I used was I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME

AZDJedi said:
I downloaded the new "stock" 4.3 and flashed that with Odin. Everything works again. Should I never flash a custom ROM again?!
Click to expand...
Click to collapse
Yeah don't, you now have a locked bootloader.

possible sound fix ?
AZDJedi said:
Hey all,
So after flashing a bunch of custom ROMs I reverted back to stock. Once I had stock I ignorantly upgraded OTA...I now have that damn Knox crap. Fine. But all of a sudden I can't hear any sound, anywhere, I can't play any video (YouTube or browser embedded), my camera video recorder doesn't function at all, my phone doesn't work, and who knows what else.
I've flashed back to stock multiple times with Odin, as well as tried my custom ROM of choice (SlimBean) and it's always the same. I have no idea what could have caused this and don't know how to get back to a functioning phone.
With my warranty now void I don't know what to do. TriangleAway said it worked but it didn't, it remains 18...I tried twice. I'm thinking I might just have to say to Telus that after I upgraded with their OTA it got messed so I tried flashing back to stock 18 times lol
Ideas?
Click to expand...
Click to collapse
i had the same issue, but i had no sound, no mic, no wifi, and no signal...
only way i got it back was to use the CDR-I337MUMUAMI1-20131121212713 mexican 4.3 update in odin,
then reflash the RWC-I337MVLUEMK6-20131125124040 canadian 4.3 rogers stock.
everything now works *but* its triggered the 0x1 knox BS..
Fyi... my counter is at 30 for trying everything under the sun i saw to get my phone back to "normal"
hope this helps...:good:

I think the issue with the Knox security crap is the ROM version. Once I flashed 4.3 stock (the one Telus released last week) everything worked fine; if I flashed 4.2.2 (the one that came with the phone) it didn't. After putting 4.3 on, and learning that by using that ROM I could always return to normal, I decided to try SlimKat again. It worked!
I'm happy to have my custom ROM back...it's way better .
I'm waiting until the hackers figure out how to get rid of Knox. It's only a matter of time IMO.

AZDJedi said:
I think the issue with the Knox security crap is the ROM version. Once I flashed 4.3 stock (the one Telus released last week) everything worked fine; if I flashed 4.2.2 (the one that came with the phone) it didn't. After putting 4.3 on, and learning that by using that ROM I could always return to normal, I decided to try SlimKat again. It worked!
I'm happy to have my custom ROM back...it's way better .
I'm waiting until the hackers figure out how to get rid of Knox. It's only a matter of time IMO.
Click to expand...
Click to collapse
yup.. if you mentioned you were canadian, could have helped you sooner. we have had the 4.3 odin files for a couple weeks now. ( add your location to your profile )
screw knox. its built into the bootloader. and its not stopping us from flashing, it is not a priority at all for anyone to hack. Bootloaders are a pain to hack, and there is no benifit to hacking this UNLOCKED knox bootloader.
my trigger is tripped, i dont care. i have the extended smartphone care plan from bell. if i crack the screen, loose the phone or drop it in water, i get a new phone (or upgrade) for 160$. kinda hard to tell if a phone is tripped its flash counter if you cant read the screen....

TRusselo said:
yup.. if you mentioned you were canadian, could have helped you sooner. we have had the 4.3 odin files for a couple weeks now. ( add your location to your profile )...
Click to expand...
Click to collapse
I figured having "Telus" as my provider would be enough info. I've added Toronto though, thanks for the pointer
Ya, I don't really care about the Knox flag either. I have the red and yellow warning when my phone boots, but who cares...as long as my custom ROM works, I'm happy!
You pay $5 a month for the priviledge of paying $160 to replace your phone, right?

missed the telus part.. lol
8 bucks but ya. already came in handy. broke my s3 screen after 8 months or so, got my s4 as a replacement for 160$ fee. a new screen off ebay for the s3 was 160$ plus risk of install to keep an s3.... ill upgrade.

TRusselo said:
missed the telus part.. lol
8 bucks but ya. already came in handy. broke my s3 screen after 8 months or so, got my s4 as a replacement for 160$ fee. a new screen off ebay for the s3 was 160$ plus risk of install to keep an s3.... ill upgrade.
Click to expand...
Click to collapse
That's 160 + (8*8+HST) = $232. Not bad I suppose.

Warranty fraud and discussions promoting it are NOT allowed on XDA. Telling someone tourposely bricking a phone to get a warranty replacement is promotion of warranty fraud.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app

See above...thread cleaned. ..
Consider this your final warning.

waranty
AZDJedi said:
Hey all,
So after flashing a bunch of custom ROMs I reverted back to stock. Once I had stock I ignorantly upgraded OTA...I now have that damn Knox crap. Fine. But all of a sudden I can't hear any sound, anywhere, I can't play any video (YouTube or browser embedded), my camera video recorder doesn't function at all, my phone doesn't work, and who knows what else.
I've flashed back to stock multiple times with Odin, as well as tried my custom ROM of choice (SlimBean) and it's always the same. I have no idea what could have caused this and don't know how to get back to a functioning phone.
With my warranty now void I don't know what to do. TriangleAway said it worked but it didn't, it remains 18...I tried twice. I'm thinking I might just have to say to Telus that after I upgraded with their OTA it got messed so I tried flashing back to stock 18 times lol
Ideas?
Click to expand...
Click to collapse
I hope this helps...
I got the update and it blew my sound and wifi. I flashed my i337m with stock 4.2 and it was still locked and showed void warranty so I rooted and used triangle away(Paid for on Goog) and it kept rebooting until I held volume up during one of the reboots and it went into stock recovery mode and SUCCESS counter reset. I still had the bootloader lock and no sound but my warranty was back. I updated to 4,3 again in hopes my wifi and sound would return but it did not. I took the phone back to koodo and five days later had it returned with 4.2.2 no bootloader lock!!!! The guy said they replaced the main board. But I'm not suggesting you do this....but this was what happened to me. I wish I took some pictures and documented it better, but I was so pissed at Samsung for yet another DOWNGRADE. We freakin buy these phones and Samsung acts like they still own it.
P.S. Don't forget to unroot.
and turn off the updates on your phone and kies!